Nav Unification - Main Issue

[obenland]

Note: this Issue has been updated by @getdave to be focused on the work required to implement the final version of the nav unification project.

This Issue is organised into Issues for two phases of work:

1. The Final version
2. The Prototype (complete - archived).

With the completion of the prototype (see pbAPfg-VL-p2) phase only #1 is relevant. This is further broken down into the key sections that will need to be completed in order for the project to be put into Production.

Version 1 Tasks/Issues

The following sections represent the work that is necessary to be completed in order to launch the final version of the unified navigation. This is based on the sections identified by @Automattic/ajax as posted in pbAPfg-VL-p2. The aim is to provide an "at a glance" overview of where we are with the project at any given time.

As new issues are discovered please add them here and also check them off when complete.

🖼 Design

For v1 the visual appearance will be guided by "Nav Unification Project Design i2" - We aim to implement the "Nav Unification Project Design i2" which closely resembles core wp-admin. Future design explorations will be addressed in a v2 and/or will likely involve a core-first approach.

🙋🏽‍♂️ User Experience Issues

This section is for UX Issues which don't fit nicely into any other section.

• [x] Implement conditionals for static fallback nav data.
• [x] Determine best UX route for managing menu section open/closed state
• [x] Allow sidebar to be scrolled (while maintaining flyout menus)
• [ ] Transition from the site-switcher back to the menu animation
• [x] (Re)position flyout menus based on available screen space
• [x] Fix menu-item active state
• [x] Refine positioning of sidebar items so that they are 1:1 between calypso:wp-admin
• [x] Nav Unification: Check domain notices
• [x] Collapse Sidebar, like wp-admin does
• [x] Collapse Sidebar, keep the same state across wp-admin / calypso
• [x] Clicking on sections causes UI to "jump" and triggers other sections to close.
• [x] Feedback: Allow Calypso to change menu icon color
• [x] Texturize menu titles before sending them through the API
• [x] Method to opt out of Calypso links.

🚀 Jetpack

All tasks relating to Jetpack green branded version of Calypso - https://cloud.jetpack.com/. Note that @davemart-in agreed extensive work on this should not form part of our version 1 launch.

• [ ] Test that we have not visually broken "green Calypso".

🤖 🕵🏼‍♂️ Quality Assurance and Automated Testing Issues

Only for issues relating to ensuring ease of maintenance and error handling/reporting.

• [ ] Add high-level e2e tests to validate expected Navigation behaviour across Calypso and WPAdmin.
• [ ] Fix admin-menu so that data layer only accepts numeric values for siteID
• [ ] Handle admin-menu request errors via action dispatch in data layer .
• [ ] Add full unit test coverage for data-layer and state.
• [ ] Add component integration tests for Nav Unification components.
• [ ] Visual Regression Testing? Efforts in core https://github.com/WordPress/wordpress-develop/pull/209. See also p1604327788116600-slack-e2e-testing-discuss and https://github.com/Automattic/wp-e2e-tests/pull/1425.

🏎 Performance

This section is for Issues relating directly to work to improve the performance of the navigation on both the front and backend.

• [x] Clicking on sections causes UI to "jump" and triggers other sections to close.
• [ ] Add REST API endpoint caching.

🎓 WP on Atomic

This section is for Issues relating directly to work on making the navigation work on WoA.

• [x] Move REST API code to Jetpack repo.

📚 Reader integration

This section is for Issues relating directly to work on the navigation shown in the Reader section.

• [x] Improve Reader sidebar markup

👩🏽‍💼 Me integration

This section is for Issues relating directly to work on the navigation shown in the Me section.

🎨 Color Scheme Issues

This section is for Issues relating directly to work on Color schemes. For the approved direction please see https://github.com/Automattic/wp-calypso/issues/45675#issuecomment-714664414.

• [x] Make new colors available to customers ahead of nav unification launch
• [x] Determine best way to match calypso scheme and wp-admin scheme colors
• [x] add Classic Dark color scheme (default ready); prepare Classic Blue for default theme change
• [x] Port over WP Admin color schemes as new options in Calypso /me section.
  • [x] Ectoplasm - #47122
  • [x] Sunrise - #47171
  • [x] Ocean
  • [x] Rename the Ocean color scheme to Aquatic; update user preferences accordingly
    • [x] Phase 1 #47273
    • [x] Phase 2 D52536-code
    • [x] Phase 3 #47333
  • [x] Midnight - Update Calypso Midnight to match WP-Admin
  • [x] Coffee - #47173
  • [x] Blue - #47204
  • [ ] Submenu highlight doesn't match; wp-admin only changes text to be brighter, calypso changes background
  • [x] Modern - #47208
  • [x] Light - #47209
  • Default - Not porting. Reference
  • Helper Issues
  • [x] Selected submenu color is chosen by variable #47291
  • [x] Submenu colors are controlled by variable #47249
  • [x] Flyout indicator arrow uses submenu background color #47250
  • [x] consolidate color-sidebar-menu-hover and -text variable #47294
  • [x] consolidate color-sidebar-menu-hover-heading-background with non-"heading" version #47300
  • Bugs
  • [x] Ported wp-admin schemes issues on site selector badges #47295
  • [x] Nav Unification: Site Switcher Loading Indicators are incorrect color #47303
• [x] Hide option to select Admin Color Scheme in profile.php.
  • Waiting on a way to control features inside Atomic sites.
• [x] Add note to WPAdmin profile.php page that points folks to the (new) respective setting in Calypso.
  • Waiting on a way to control features inside Atomic sites.
• [x] Make Color Schemes apply account wide (not site-specific) across WPAdmin and Calypso (remove setting and have WPAdmin inherit from Calypso setting).
• [x] update Calypso color schemes for nav-unification
• [x] Add the necessary wp-admin styles to support all color schemes available in Calypso.
  • [x] Classic Bright
  • [x] Classic Dark
  • [x] Classic Blue
  • [x] Nightfall
  • [x] Sakura
  • [x] Aquatic (i.e. former Calypso Ocean)
  • [x] Sunset
  • [x] Powder Snow
  • [x] Contrast
• [x] Ensure new color schemes apply to Gutenberg

🚦Release Process

• [x] Research internal testing mechanism for within A8c. How will this work without having ?flag=?
• [x] How to sync with Jetpack release process? What's the plan?
• [x] A / B testing - light touch research and confirmation as to whether possible. Can we A/B test nudges only?
• [x] Research incremental rollout mechanic and outline options.
• [x] We’ll also show a modal to customers the first time they log in to help orient them to the change.
• [x] Decision on incremental rollout target user groups.
• [ ] Cleanup code after feature is fully released to 100% of users

Documentation

• [x] Write Fieldguide entry on the Unified Navigation.

---

---

---

Version 2 Issues

Following launch of an v1 of this project the following items are known to be issues that will need to be addressed as part of a v2:

• [ ] Notices and Nudges - these don't work on WPAdmin.

---

---

---

🗝️ (Old) Prototype Completed Issues

These items were completed during the Prototype phase of work.

• [x] Create data layer integration for /admin-menu endpoint

• [x] Create Redux state tree for admin menu

• [x] Update admin-menu reducer to be keyed by siteID

• [x] Create selectors to retrieve admin-menu data from state

• [x] Decide on sidebar menu fallback experience and implement

• [x] Render my-sites sidebar from data off the /admin-menu endpoint

• [x] Persist menu state to browser storage to ensure quicker render of menu.

• [x] Nav Unification - create visual "loading" state for the menu.

• [x] Reuse existing Nav components where possible ensuring standards compliant markup.

• [x] Refactor Unified Nav to expect API to return data as array

• [x] Fix HTML entities shown in menu items.

• [x] Calypso: Clicking Nav items doesn’t correctly navigate to route. #45973

• [x] Calypso: Top level menu items don’t link they only “unfold” the sub menus. #45963

• [x] API: Testimonials menu item missing from API response - D50275-code

• [x] wp-admin: Include stats “graph” image in stats menu item - D50280-code

• [x] wp-admin: Currently selected site icon - use correct SVGs (p1601306196200900-slack-CJS75TX3R) #45965

• [x] wp-admin: Flag persistence missing - D50310-code

• [x] Nav Unification: Left Nav submenu hover / active

• [x] Fix layout "jumps" in sidebar as new items load.

• [x] Update Ad Control to AdControl in static admin menu data.

• [x] Multiple admin menu items in "selected" state.

[getdave]

I've updated the Issue with a list of sub tasks as I see them. Please feel free to amend.

[getdave]

@Automattic/ajax Please note that as of this merge https://github.com/Automattic/wp-calypso/commit/ebde236ec9b21ea9621c0b0523bd5ea185523731, we are now persisting adminMenu state to IndexDB. Therefore any changes to the shape of the data coming back from the REST API endpoint needs to be updated in the corresponding schema.js file.

I'd recommend a quick read up on this documentation to ensure you're up to speed.

I added r214400-wpcom to WPCom API which adds comments which attempts to make devs aware of this when changing the API endpoint.

[getdave]

I've updated the description of this Issue to catalogue the required work remaining to be able to launch the nav unification feature across WordPress.com.

[getdave]

@Automattic/ajax FYI I added a Version 2 Issues section to this Issue to track any items that have been removed from v1 on the grounds of scope. Please move items there as required.

[frontdevde]

FYI added the following decision (see https://github.com/Automattic/wp-calypso/issues/45675#issuecomment-724604005) to the issue to make sure we're all on the same page:

🖼 Design

For v1 the visual appearance will be guided by "Nav Unification Project Design i2" - We aim to implement the "Nav Unification Project Design i2" which closely resembles core wp-admin. Future design explorations will be addressed in a v2 and/or will likely involve a core-first approach.

[obenland]

Let's consider this finished.