RFC Editor Website Revamp, Study Guides, Projects, Research of Design

Functional Requirements a. Standards and Security. The website front end must be built with HTML5 and other open web standards. The resulting website will ...

Typology: Study Guides, Projects, Research

2021/2022

Uploaded on 09/27/2022

ralphie
ralphie 🇬🇧

4.8

(8)

214 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
RFC$Editor$Website$Revamp$
!
1. Project!Overview!
!
The!website!revamp!project!will!update!the!public9facing!website!for!the!RFC!Editor!
(http://www.rfc9editor.org),!providing!a!"front!door"!to!the!RFC!Series!and!a!more!
easily!maintained!presence!to!the!community.!The!RFC!Editor!website!needs!
provide!an!easy!and!accessible!interface!to!the!RFC!Series.!!
!
In!addition!to!migrating!the!static!content,!the!various!PHP!scripts!used!on!the!
existing!site!need!to!be!migrated!into!the!WordPress!framework.!!Internally,!the!
static!content!will!be!held!in!a!content!management!system!(again,!WordPress),!
which!aids!in!maintaining!the!content!and!creating!a!cohesive!site.!!The!scripts!that!
create!dynamic!content!will!be!reorganized,!which!makes!the!site!more!secure!and!
portable!for!the!long!term.!!There!will!be!an!internal!cleanup!that!removes!
deprecated!content!from!the!site.!
!
This!work!has!already!started!within!the!RFC!Production!Center.!
!
2. Project!Goals!
!
The!RFC!Editor!website!redesign!will:!
!
a.!Improve!ease!of!navigation,!
b.!Modernize!the!website!visual!design,!
c.!Make!the!website!work!better!for!all!classes!of!devices,!including!smart!
phones!and!those!with!low9bandwidth!and!high9latency!connections.!
d.!Incorporate!current!best9practices!in!website!design!and!implementation!
(such!as!responsive!design!and!accessibility),!and!
e.!Improve!the!content!maintenance!processes.!
!
3.!!Audiences!
The!website!will!be!redesigned!with!these!groups!in!mind!as!key!users:!
!
a.!Consumers!of!RFCs!
b.!Individuals!interested!in!the!workings!of!the!RFC!Editor!
c.!The!RFC!Editor!staff!
!
!
4.!!Process!
The!redesign!project!will!be!informed!by!review!and!input!from!by!the!RFC!Series!
Editor!and!the!RFC!Production!Center!staff,!and!will!take!into!account!input!from!the!
community!and!special!advisory!groups!(i.e.,!RSAG,!rfc9interest!mailing!list!
participants).!!
!
pf3

Partial preview of the text

Download RFC Editor Website Revamp and more Study Guides, Projects, Research Design in PDF only on Docsity!

RFC Editor Website Revamp

  1. Project Overview The website revamp project will update the public-­‐facing website for the RFC Editor (http://www.rfc-­‐editor.org), providing a "front door" to the RFC Series and a more easily maintained presence to the community. The RFC Editor website needs provide an easy and accessible interface to the RFC Series. In addition to migrating the static content, the various PHP scripts used on the existing site need to be migrated into the WordPress framework. Internally, the static content will be held in a content management system (again, WordPress), which aids in maintaining the content and creating a cohesive site. The scripts that create dynamic content will be reorganized, which makes the site more secure and portable for the long term. There will be an internal cleanup that removes deprecated content from the site. This work has already started within the RFC Production Center.
  2. Project Goals The RFC Editor website redesign will: a. Improve ease of navigation, b. Modernize the website visual design, c. Make the website work better for all classes of devices, including smart phones and those with low-­‐bandwidth and high-­‐latency connections. d. Incorporate current best-­‐practices in website design and implementation (such as responsive design and accessibility), and e. Improve the content maintenance processes.
  3. Audiences The website will be redesigned with these groups in mind as key users: a. Consumers of RFCs b. Individuals interested in the workings of the RFC Editor c. The RFC Editor staff
  4. Process The redesign project will be informed by review and input from by the RFC Series Editor and the RFC Production Center staff, and will take into account input from the community and special advisory groups (i.e., RSAG, rfc-­‐interest mailing list participants).

Key milestones and deliverables during the redesign process (e.g. site architecture, technology, wireframes, page design, content updates) should be identified in the proposal. These items will be reviewed and approved by the RFC Series Editor.

  1. Project Scope This project is limited to the www.rfc-­‐editor.org website only. The following elements are included in the scope of the web redesign project:
    • Reorganize and update scripts that publish to the website to use relative paths and function in their new locations.
    • Update dynamic pages to match new site (involves CSS and WordPress configuration).
    • Add search functionality on front page.
    • Create a 'combined search' box that accepts a RFC/subseries number OR title/keyword as input.
    • Replace the WordPress site search box with the new 'combined search' box.
    • Change the WordPress settings and/or CSS to get specific look & feel as needed.
  2. Functional Requirements a. Standards and Security The website front end must be built with HTML5 and other open web standards. The resulting website will be accessible via both HTTP and HTTPS, and will encourage the use of HTTPS. Functions requiring a user login will only be available over HTTPS. b. Search Users will be able to use the site search for content on the RFC Editor web presence at www.rfc-­‐editor.org using the search functionality at http://www.rfc-­‐editor.org/search/rfc_search.php. d. Accessibility i. The site will be coded in compliance with the Web Content Accessibility Guidelines (WCAG) 2.0: ii. Text equivalent will be available for all non-­‐text content. This will involve providing alternative description in the alt attribute for image tags or in-­‐element content. iii. All information displayed in color will also be accessible without color. Pages will be readable without a style sheet. iv. Row and column headers will be identified on pages with tabular data. v. Pages with forms that require a timed response will display a message making users aware of this. vi. For pages that require the use of applets, a link to the page where the user can obtain the plug-­‐ins will be provided.