Perform site audit of mobile navigation

[kristine-eudey]

Dependency

We need to determine how we will add this audit of navigation elements to the design system. An issue will be created to improve the design system and determine if we need a navigation component menu added to it.

Overview

We need to audit all the current mobile navigation on the site and create documentation for them in the design system so that the design team is able to pull from these options and design future mobile pages with greater ease and consistency.

Action Items

• Create new page in Figma titled "Mobile Menus Audit"
• Go through all mobile pages in Figma, copying all instances of menus and navigation patterns used across the site.
• Copy each instance to the "Mobile Menus Audit" page, noting which page on the site it came from
• Analyze findings: did you notice any inconsistencies or issues? Do you see any room for improvement, or recommend any changes based on what you found?
• Present to the larger team to share the findings.

Resources/Instructions

Hack for LA - Figma Mobile audit
Basic patterns for mobile navigation: Pros and Cons (Smashing Magazine)

[ashleylin1]

Progress: Finished adding navigation component menu
Blockers: None
Availability: Weekends
ETA: Finished
Pictures:

[kristine-eudey]

Thank you @ashleylin1! Issue complete. Mobile navigation audit can be found here: Figma - Mobile Navigation Audit

[IsaacDesigns]

Progress: I have determined the next steps in this issue is to identify if there's anything in this audit that isn't represented in the Design System. Anything found that isn't represented in the Design System should then be assessed to determine if it should either be added to the DS.
Blockers: None
Availability: 3 hours
ETA: 5 days

[ExperimentsInHonesty]

The navigation elements should be added to the design system if they are not there and if they are there, then the mobile views needed to be added as a context example. In order to accommodate that, add two more columns
Desktop context example, Tablet, Mobile

[github-actions]

@IsaacDesigns

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, January 10, 2022 at 11:19 PM PST.}

[IsaacDesigns]

Progress: Bonnie and I have determined that the navigation elements should be added to the design system if they are not there and if they are there, then the mobile views needed to be added as a context example. In order to accommodate that I will add two more columns for Desktop, Tablet, and Mobile context example.
Blockers: None
Availability: 4 hours
ETA: 1/21/2022

[IsaacDesigns]

Finished adding components to Design System. We will need to create an issue to add two more columns for Desktop, and Tablet context examples.

[ExperimentsInHonesty]

I am moving this back to new issue approval column to indicate that the new design lead, or product team will have to make an issue for the changes needed to expand the design system.