UXD - Desktop Header / Footer Updates

[Joy-Truex]

Overview

We need to update our header and footer components to ensure they are up to date with the current product and UX standards.

Action Items

• Design Action Items
  • remove social media icons from the Desktop's footer (Facebook, X)
  • remove "Data last updated MM/DD/YY" from the Desktop's Footer
• Bookkeeping
  • Update component in design system library
  • Update the Hand Off section of this ticket with the final iteration of this design

---

Design Iterations

Please move ticket between In Progress and In Review to assist PM team

Iteration 1

Link to notes: REPLACE WITH COMMENT URL

REPLACE WITH SCREENSHOT UPLOAD

---

Hand Off Materials

Figma Section Name: REPLACE WITH SECTION NAME

Before Screenshot

REPLACE WITH SCREENSHOT UPLOAD

After Screenshot (Finalized)

REPLACE WITH SCREENSHOT UPLOAD

Designer Resources

Iteration Dropdown Copy/Paste

<details><summary>Iteration X</summary>
<p>

Link to notes: `REPLACE WITH COMMENT URL`

`REPLACE WITH SCREENSHOT UPLOAD`

</p>
</details> 

Instructions for Engineering Hand Off

To Start Engineering Hand Off...

1. Ensure all Hand Off Materials are filled in
2. Add the "ready for dev lead" label
3. Leave a comment saying "This ticket is ready for engineering hand off."

[ryanfchase]

Notes per PM + Design planning:

• Design lead was thinking post-launch, however Dev + Content are in alignment that this is a candidate for pre-launch
• meeting on 2025-10-28 to discuss

Q: Per line 2, is anything fundamentally changing about the way we ingest data?

• A: no the city updates their data daily and we ingest the latest data as we get it. This was always how our data pipeline worked

Q: Per socials...

• A: similarly stated on the spreadsheet, we should remove socials that we are not maintaining. If we were to use a social, my guess is that HfLA's LinkedIn page would be the most maintained social in the org

• "Powered by volunteers from Hack for LA" must appear on the screen (per Bonnie's previous instruction)

• we can take this action item out because we are keeping the action items limited in scope for pre-launch