Navigation options (like having all pages show up in footer) for many pages

[Sihemgourou]

Overview

We need to add all of the HfLA website's page links to the footer to help improve user navigation.

Action Items

Design

• Compile links to all of the HfLA website pages
• Research footer examples with links on other websites
• Duplicate current footer design in Figma and ideate new version with page links, Test different alternatives (should we put all the live pages on the footer?)
• Show a few new options for footer with links to design lead/PM and get approval

Development

• Update website footer with new design with page links

Resources/Instructions

http://civictechindex.org/home

HfLA Sitemap on Figma (current in pink rectangle) - for links
HfLA footer design in Figma (current in pink rectangle)

Example of Shopify footer with links (image taken from Bonnie's comment here):

[kristine-eudey]

@SaashaG Please provide an update on this issue:

• Progress
• Blockers
• Availability
• ETA

[SaashaG]

Progress: Starting the comp analysis
Blockers: n/a
Availability: varied
ETA:Update at next design meeting

[github-actions]

@SaashaG

Please add update using this template (even if you have a pull request)

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) ask for help at a Tuesday or Sunday 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 Tuesday, August 3, 2021 at 7:53 AM.}

---

Note: This comment was created as part of a GitHub Action during its trial phase. If you find this GitHub Action to be disruptive/unhelpful, or if you believe there might be a bug, please leave a comment on this issue. All feedback will be used to further improve it. Thank you for your time.

[kristine-eudey]

Hi @SaashaG, thanks for working on this! Please comment on this issue to add these things as discussed in our last Thursday meeting:

• Any updates
• A link to your competitive analysis
• Your design work to the Figma footer page

[SaashaG]

Progress: Competitive Analysis complete here, moving on to design ideation
Blockers: n/a
Availability: varied
ETA: 8/14/21

[Sihemgourou]

Hey @SaashaG just compiled a similar issue into this one, please feel free to ask me any question if needed :)

[SaashaG]

Progress: Design Ideation
Blockers: n/a
Availability: varied
ETA: TBD
See design option screenshots and linked here. Let me know your thoughts before I can move on.

[kristine-eudey]

Footer design versions are ready for feedback by product & dev.

[ExperimentsInHonesty]

@SaashaG I left a note in the figma file about preferring a version without the part that looks like this

words

Caps or no caps up to team and UX Research

How to order menu (either using top menu or making a new sort order) to be determined by user testing.

[kristine-eudey]

@SaashaG Feedback from all-team meeting on 8/15/21:

• The preference is for either option 1 or 2, the simplest versions (those without the top horizontal nav.) No top nav, no divider line, keep it as simple as possible.
• Add “About us” and “Press to main menu
• “Project team meetings” and “Our Locations” should be replaced with “Events” page
• Design two different versions and user test these to see which organizational structure is preferred by users:
  • One with pages organized as they are on the Sitemap / Current top menu on site (Saasha’s version)
  • Another that uses a different organizational structure that doesn’t follow sitemap but tries to group information based on prioritization of information and main themes. (Kristine's version on bottom of Figma)

[github-actions]

@SaashaG

Please add update using this template (even if you have a pull request)

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) 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 Tuesday, August 17, 2021 at 12:02 AM PST.}

[github-actions]

@SaashaG

Please add update using this template (even if you have a pull request)

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) 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 Tuesday, August 24, 2021 at 12:03 AM PST.}

[SaashaG]

Progress: Design options linked. let me know for the final ok then I can work on mobile versions
Blockers: n/a
Availability: Varied, on vacation until Sep 12
ETA: TBD
See design options here: https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3417%3A3

[github-actions]

@SaashaG

Please add update using this template (even if you have a pull request)

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) 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 Tuesday, August 31, 2021 at 12:02 AM PST.}

[github-actions]

@SaashaG

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) 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 Tuesday, September 7, 2021 at 12:02 AM PST.}

[kristine-eudey]

The design portion of this issue is completed and can be found in the red box here: Figma - Footer.

As per team discussion and vote, we're moving forward with the navigational structure highlighted in the red box and listed as "version 2". This design moves away from grouping pages based on the current menu options in the current top nav and groups content into sections based on what we believe will be more easily navigable to users. The goal was to create more natural groupings of information which can encompass all the site’s current content and can more easily accommodate the addition of new pages to the site. It will also pave the way for an update to the top nav #1256

Moving to UAT. Dependency for development would be all pages listed in the footer going live (I believe, correct me if I'm wrong)

[ExperimentsInHonesty]

@abuna1985 have a true/false flag for displaying the new content, and the content is driven by a markdown file.

[abuna1985]

Created #2393 for dev implementation of the footer