Skip to content

feat(nav): surface Meetings + Decisions as top-level nav entries#33

Open
ronaldtse wants to merge 2 commits into
mainfrom
feat/surface-meetings-decisions-nav
Open

feat(nav): surface Meetings + Decisions as top-level nav entries#33
ronaldtse wants to merge 2 commits into
mainfrom
feat/surface-meetings-decisions-nav

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Promote Meetings and Decisions out of the 'Model' dropdown into top-level nav slots, matching the default chrome shipped in @edoxen/astro (PR edoxen/edoxen-js#14).

…Item URN

- ContactCollection/VenueCollection pages renamed to
  ContactRegister/VenueRegister (model rename)
- new: body.md, body-register.md, entity-resolution.md
  (three-tier inline/local_ref/ref + Edoxen::EntityResolver)
- contact.md/venue.md: ref/local_ref/urn fields, Meeting.contacts[]
- agenda.md: AgendaItem.urn + Edoxen::UrnFor; decision_ref fix
- meeting-collection.md: committee/committee_group are Body
- schema.md: register root docs, three-tier URN pattern, lychee fix
- cli.md: validate-meetings/normalize-meetings coverage
- public/schemas re-synced from edoxen-model@main
- sidebar nav updated
Per the user request — Meetings and Decisions (Resolutions) are the
two primary concepts and should be discoverable in the top nav,
not buried inside the Model dropdown.
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