design: about-mega-menu - Rebuild the About mega menu to match the content doc #116

Design Summary

Rebuild the About mega menu to match section “5. About (Mega Menu)” of the referenced content document: a three-column menu titled “Get to know us”, focused on trust, transparency and internal governance.

The current menu has two columns and six links, without the specified column headings.

Linked Stories/Tasks/PRs/Design Files / Related Epics

Related: LSA-125 — About page patterns.

Project repository candidate: https://github.com/lightspeedwp/ls-theme
Relevant files: parts/about-mega-menu.html and parts/mobile-menu.html.

The source references PR #115 and a content document; their exact links remain to be confirmed. No native relationships are proposed.

Milestones & Timeline

No milestone or deadline specified.

Design Summary

Use three columns:

• Company: Our Story (History), Team, Careers
• How We Work: Our Culture, Community & Events
• Governance & Policies: Publishing Principles & AI Ethics, Diversity (Content & Staffing), Privacy Policy & Terms of Service

Set the title to “Get to know us”. Link the Governance & Policies heading to /policies/.

Retain the existing mega-menu panel shell, header row and “Prefer to talk?” footer. Reuse existing item groups, icon wells, H5 links, muted descriptions and arrow icons. Add column headings using the existing small uppercase label style.

Update the mobile menu and About header navigation to match. Do not introduce CSS, tokens or theme.json changes.

Designs / Mockups

Content-document link required. Use its supplied descriptions for History, Team, Careers, Culture and Community & Events.

Descriptions for the three governance items require confirmation.

Accessibility Considerations

Verify navigation usability and accessibility across desktop, tablet and mobile, including light and dark modes.

Acceptance Criteria

• Design artefacts and specs are attached
• Accessibility standards reviewed/met
• Documentation/changelog updated
• PR uses correct branch prefix (design/)
• Stakeholder/maintainer reviewed
• PR description updated with relevant details
• Changelog entry prepared for PR (if applicable)
• Labels/types match org standards
• Three columns display the agreed items and headings
• Title reads “Get to know us”
• Every item links to an existing page without 404s
• Governance & Policies heading links to /policies/
• Light/dark modes and tablet/mobile layouts work
• Mobile menu and header navigation match
• No new CSS, tokens or theme.json changes
• Schema validation and the Playwright standing suite pass, including the mobile-menu spec

Dependencies

Confirm URLs for Careers, Community & Events and the three governance items. Supplied paths are /about/history, /about/team, /about/culture and /policies/.

Confirm whether Our process remains, and resolve /about/process/ versus /about/our-process/.

Decide whether Why LightSpeed, Getting started, AI governance, Guarantees and Accessibility should move elsewhere rather than disappear.

Confirm “from 2003 to today” wording against the content brief.

Sibling About pages and policy pages must exist before internal-link validation can pass.

Testing/Validation Steps

Run npm run schema:validate and the repository’s Playwright standing suite, including the mobile-menu spec. Check internal links, responsive navigation, accessibility and light/dark modes.

Additional Context

The supplied write-up describes the current implementation; it has not been independently audited. The project-linked ls-theme repository contains both named menu files, but the content-document link is still missing.

Definition of Ready (DoR)

• Design goal/scope defined
• Artefact/objective listed
• Accessibility criteria mapped
• Dependencies mapped
• Estimate added (if applicable)

Definition of Done (DoD)

• All design acceptance criteria met
• Documentation/changelog updated
• Design reviewed and approved
• PR uses correct branch prefix (design/)
• Branch deleted after merge
• Documentation/changelog updated if needed
• Linked issue(s) updated with latest status and closed after merge,
• The related epic should not be closed, instead updated with a comment to reflect the closed issue