Architecture decisions

No CMS, no auth. Public site reads from a read-only SQLite DB via GET-only routes — no login/session/auth anywhere in the app.
Dynamic without an editor. Content updates are a re-run, not an edit: npm run import:wp re-fetches WordPress's REST API and upserts by slug.
Static vs. DB-backed. Hand-authored copy (About/Hub Model, Get Involved, Tools intro text) lives directly in Angular templates. List/detail content goes through the DB.
Events — native module, not a port. WP's calendar is a 3rd-party Localist/Concept3D embed and isn't portable.
Fonts — keep linking Cornell's Typekit kit (nwp2wku). Cornell is entitled to its own kit; don't vendor licensed font files.

Page inventory

@for (row of pageInventory; track row.route) { }

WP page	New route	data.menu
{{ row.wpPage }}	`{{ row.route }}`	{{ row.menu }}

@for (row of contentTypes; track row.type) { }

Type	Source endpoint	Notes
{{ row.type }}	`{{ row.endpoint }}`	{{ row.notes }}

npm run check after each phase (typecheck + prod build).
npm run dev; load every route from the page inventory table in-browser and visually diff against the live WP page.
Re-run npm run import:wp twice in a row — row counts and asset file counts must be stable (idempotency).
grep -r "passport\|jwt\|session" server/ stays empty — GET-only, no auth anywhere.
Mobile breakpoint check (<768px) for nav collapse and card stacking.