Skip to content

docs: read passport dates from the core catalog - #40

Merged
LKSNDRTMLKV merged 3 commits into
stagingfrom
docs/passport-dates-from-core
Oct 27, 2026
Merged

LKSNDRTMLKV merged 3 commits into
stagingfrom
docs/passport-dates-from-core

Conversation

@LKSNDRTMLKV

Copy link
Copy Markdown
Member

Summary

Every passport date on both sites is now read from dpp-core's instrument catalog instead of being typed into a page. The docs' regulatory pages carried 14 of them by hand, and the landing carried 8 more outside /regulations, which already read the catalog. The org style guide (DOCS-STYLE.md) says regulatory dates live in code.

Changes

  • chore(docs): vendor the acts from dpp-core: core-source.json gains a second destination for the instrument records, site/dpp-docs/src/data/instruments. The pin, the sync script and check:core are unchanged and cover both copies. The copy sits inside the docs folder so a pin bump changes files the docs Pages project watches. Reading the landing's copy would have left the docs stale after a bump. check:core is proven to fail when the docs copy drifts.
  • docs: render passport dates from the catalog: a <PassportDate act="<id>" /> component (src/lib/acts.ts) replaces the 14 dates on the battery, ESPR, toys, detergents and acts-and-standards pages. A short form keeps "23 Sep 2029" in tables, spelled out because current ICU data abbreviates September as "Sept".
  • fix(landing): read passport dates from the catalog: passportDateOf() in src/lib/regulations.ts for pages (lifecycle, roadmap, repairers and recyclers, timeline, example passport), and {passport:<id>} tokens in faq.json and glossary.json, filled where each page loads its copy, so the visible text and the JSON-LD agree. The README states the rule.

Both builds fail for an act with no sourced date: tried with act="espr" on the docs and {passport:cpr-2024-3110} on the landing, and each build stopped with the helper's own error.

Left as written, each beside the article that sets it: the detergents transition dates (Art. 36), Commission deadlines, application dates and registry user-guide versions. The ELV Art. 13(1) date is inside a quotation of the Official Journal and stays as the act prints it. _main.astro is an unbuilt draft and still has one date. The matching style-guide wording is in odal-node/.github#1.

Checklist

  • pnpm -r build and pnpm -r check
  • check:links, check:llms, check:sitemaps, check:leakage, check:spacing, test:scripts, test:verify, check:core
  • Rendered HTML checked: each date appears in the page text and, on the FAQ and glossary, in the JSON-LD; no {passport token or component name reaches a page
  • Merged locally with docs: rewrite the docs site for developers #38 and the staging-flow branch: no conflicts, and every gate, including docs: rewrite the docs site for developers #38's anchor check, passes on the combined tree
  • No secrets, credentials, or .env files in the diff
  • Founder review

Signed-off-by: chillin_since_26 <aleksandar.temelkov@live.com>
Signed-off-by: chillin_since_26 <aleksandar.temelkov@live.com>
Signed-off-by: chillin_since_26 <aleksandar.temelkov@live.com>
@LKSNDRTMLKV LKSNDRTMLKV changed the title docs: read every passport date from the core catalog docs: read passport dates from the core catalog Oct 27, 2026
@LKSNDRTMLKV
LKSNDRTMLKV merged commit ecc5dd7 into staging Oct 27, 2026
0 of 2 checks passed
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