Editorial Navigation Redesign

kevwalsh commented 4 years ago

Problem statement

The OOTB admin menu in the Drupal CMS is designed to support the needs of engineers, not content editors. The Content editors and other user segments should have access to navigation that works for them and helps accomplish their top tasks with minimal friction.

Hypothesis or Bet

A navigation designed to serve the needs of various user groups within the CMS will help users accomplish their top tasks faster, with less friction and frustration.
A navigation needs to be specific to user segments, which will include groups by role, section, etc.

We will know we're done when... ("Definition of Done")

Research has been completed to inform usable navigation design.
Navigation is redesigned and usability is validated with CMS users.
New navigation design is implemented and serves various user segments in the CMS.
Navigation standards, guidelines and patterns are documented in the VA.gov CMS Design System.

Known Blockers/Dependencies

none

Acceptance Criteria

[ ] CMS IA audit
[ ] Research to arrive at usable navigation
[ ] Navigation is redesigned to serve various user segments in the CMS
[ ] Redesign validate through usability testing
[ ] Navigation pattern is developed as a part of VA CMS Design System
[ ] Navigation redesign implemented

va.gov-team product directory

https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/cms/product-outlines/navigation-redesign

### Tasks
- [ ] https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17763
- [ ] https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17764

jefflbrauer commented 2 years ago

Hey team! Please add your planning poker estimate with ZenHub @ElijahLynn @indytechcook @ndouglas @olivereri @timcosgrove