Implement PatternFly Website Navigation Redesign

[edonehoo]

trafficstars

Follow-up to https://github.com/patternfly/pf-roadmap/issues/242

Problem statement UX Designers and Developers struggle to consistently, successfully, and confidently locate information on PatternFly.org. Data from the PatternFly Navigation Study shows that they are successful in locating information 70.7% of the time, after 27 seconds on average, with a confidence rating of 3.62/5, and 52% of successes being indirect.

Goal / Impact statement

• A new PF.org navigation will make it easier for our users to confidently use the main site navigation and page context to successfully find the resources they need. It could improve task finding success rates to >76%, with a finding time of <20 seconds, and a confidence rating of >4/5.
• An updated PF.org navigation structure will better support content design and docs scalability.

Acceptance criteria

• A new PF.org navigation is merged to staging.
• (if possible) The org file structure in GitHub is aligned with the new nav structure.
• Notes/a plan for any specific docs updates, including new docs or major edits to existing docs

Issues

• [Created] Nav design (visual & the tree)
• [Created] Implement nav changes (rearrange and add new visual designs, also update links in docs?)
• [Created] Update existing landing pages across website
• [Multiple issues TBD] Add new pages as decided within the team (for example, FAQ or Contact)

Risks

• If any technical limitations prevent planned nav changes.
• We probably will want to clean up / align the file organization within GitHub to match the new nav structure (for easier contribution).

Relevant links [Research study] https://issues.redhat.com/browse/UXDR-3908

Level of effort ~5-6 sprints, primarily 1 content designer with additional dev support as needed

Open questions Can we feasibly add nav section group headers and dividers? Are there accessibility/mobile considerations?