Skip to content

Add theMenu pilot at /themenu with facts-first menu ingestion - #1

Draft
ExtraDeadFred wants to merge 1 commit into
mainfrom
feature/themenu-pilot
Draft

ExtraDeadFred wants to merge 1 commit into
mainfrom
feature/themenu-pilot

Conversation

@ExtraDeadFred

Copy link
Copy Markdown
Contributor

Adds theMenu as a Trinity Research component intended for https://trinity-research.com/themenu/. The generated site is under themenu/; editable data, code, brand materials, and tests are under themenu/source/.

The component stays on a feature branch for refinement before a separately approved merge. Existing homepage, CNAME, root robots/sitemap, datasets, HNTED pages, and existing workflows are unchanged. The new validation workflow uploads a static preview artifact and does not deploy.

Included behavior:

  • Compact Utility/Cobalt directory and a tighter 2px the/MENU gap.
  • Search, optional location, native menus, stable HTML menu URLs, JSON/Markdown exports, and structured data.
  • Visible price/change disclaimers and explicit source, date, stale, missing, and excerpt states.
  • Facts-first imports for chains and independent restaurants without a blanket owner-opt-in requirement; descriptive text and media retain separate review requirements.
  • Configured future /themenu/ canonical base and correction issue destination, with noindex retained for the development pilot.

The canonical directory is currently empty. ?demo=1 is explicitly fictional and does not enter public discovery feeds. The ingestion proposal is in themenu/source/docs/INGESTION_PLAN.md.

Validation:

  • 55 local tests pass (41 Python, 14 Node), plus build/brand/disclosure checks.
  • Component source/output integrity check passes, including the exported source checkout.
  • Remote blob audit verified all 88 additions and preserved every pre-existing repository file byte-for-byte.
  • Screenshot capture and actual 200% browser zoom remain pending as documented in QA.md; no screenshots or consumer-test results are claimed.

Do not merge as part of this draft. The existing Pages publishing branch is main, so merging is the live-publication step.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant