diff --git a/aidlc-docs/features/redesign-modern-timetravel/construction/plans/u6-seo-performance-plan.md b/aidlc-docs/features/redesign-modern-timetravel/construction/plans/u6-seo-performance-plan.md index 08371cc..d041b42 100644 --- a/aidlc-docs/features/redesign-modern-timetravel/construction/plans/u6-seo-performance-plan.md +++ b/aidlc-docs/features/redesign-modern-timetravel/construction/plans/u6-seo-performance-plan.md @@ -32,6 +32,8 @@ Basis: owner answers in `inception/application-design/unit-u6-seo-and-performanc - Hash routing stays (single page); sitemap lists the one URL plus the privacy page if it gets a real URL. - Host injection needs CMS work and a deploy to both hosts; ASF has the same pattern later (gallery), so keep the marker contract generic. -## Open points for the owner -- Is the privacy page to become a real URL (affects sitemap)? Currently hash route. -- Domain used for canonical/OG on production: `https://slpsoftware.nl` (assumed). +## Decisions of the owner (2026-11-11) +- Plan approved; start with the website part. +- The privacy page becomes a **real URL `/privacy`** (sitemap lists `/` and `/privacy`). Consequence: path routing for that page (or a prerendered static page) instead of the hash route; the CMS host must serve `/privacy` (SpaFallback already covers it). Keep `#` anchors for sections of the home page. NFR-8 "hash routing remains" is relaxed for the privacy page only. +- Canonical domain: `https://slpsoftware.nl`. +- Production host: currently the .NET CMS host; **possibly IIS later**. So the marker contract for dynamic data must not depend on the .NET host only: keep the build-time option (as the ASF site does: build fetches the data, rebuild on change) as a fallback design, and look at how ASF solved it.