-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorder items under "ABOUT [SYSTEM NAME]" in VAMC menus to match CAIA guidance #16233
Comments
police and policies on adjacent lines is not great for scanning and recognition as they only differ by an 'i' (least visibly distinct character there is) |
Related upstream module issue https://www.drupal.org/project/codit_menu_tools/issues/3406650 |
ready for Drupal refinement, will need Dave P. to review along the way |
Upstream issues completed:
I will create a new release of the module in the morning after one final round of testing. |
There are some menu naming anomalies that I fixed on prod.
|
Yep Leavenworth was coalesced to kansas and the menu was never removed. #4943 I'll have to remove the menu from config as part of this PR :( Need to remove topeka too :( |
Menus that are already correct, to be used to validate they don't break:
Menus that are currently out of order:
|
Running the script (CMS Devops) and fixing Lovell by hand (Facilities engineer) are covered by #17202 |
Have pinged on #17202 to clarify whether the CMS Team has run the required script in prod yet or not. If so: this ticket will be unblocked. |
Sort of a duplicate of #17202, which was verified as completed in prod as following the menu order |
User Story or Problem Statement
When getting IA guidance for Police Transparency, we also got a request to standardize the order of VAMC menu items in the ABOUT [SYSTEM NAME] sub menu.
ABOUT [SYSTEM NAME]
Private Zenhub Image
Acceptance Criteria
The text was updated successfully, but these errors were encountered: