U6 SEO en performance: antwoorden opdrachtgever, planconcept (optie E) en NFR-9

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-11 22:16:59 +01:00
co-authored by Claude Sonnet 5.5
parent 548c7185aa
commit a220d4cff8
4 changed files with 70 additions and 0 deletions
@@ -33,5 +33,12 @@ Options to compare (none chosen):
4. How should test environments be kept out of search results (robots, headers, auth)?
5. Is a measured Lighthouse score a release gate?
## Answers of the product owner (2026-11-11)
1. **Dynamic parts** (revised later on 2026-11-11, replaces "still unclear"): SLP Software has **static text with some dynamic parts such as the packages**. The Andrea Slop Fotografie site is the same, and will later get a dynamic gallery as well; texts becoming dynamic is a possibility further out and is **not** to be designed for now. This points to option E (hybrid): prerender the static text at build time, fill the dynamic parts (packages, later the gallery) from current data.
2. **Who serves the HTML**: answered from the repo and the hosts, not by the owner. The SLP test host (and production, same application) serves the SPA through the .NET CMS host, so it can render HTML itself. The owner's remark about an IIS host concerns the Andrea Slop Fotografie site (IIS production hosting), not SLP Software: to be confirmed with the owner.
3. **Freshness**: ideally within minutes. Whether that is achievable on an IIS host is the open point for the ASF site; for SLP the CMS host can render per request or on publish (option C or the dynamic half of E).
4. **Test environments**: `robots.txt` with `Disallow: /` plus an `X-Robots-Tag: noindex` header on test hosts, served by the host (environment-specific), not baked into the shared bundle. No password protection.
5. **Lighthouse**: same as the ASF site (`web/lighthouserc.cjs`, `lighthouserc.desktop.cjs`): measured in the pipeline on the built site, mobile and desktop, a hard gate with a minimum score of 0.9 per category; exceptions only with a recorded owner decision and a floor, per page.
## Requirements touched
New NFR group "SEO and performance" to be added to `requirements.md` when the unit is planned. Security Baseline applies to any new header or script (CSP, no new third-party scripts).
@@ -46,6 +46,8 @@
- **NFR-7 Maintainability**: theme tokens as CSS variables per variant × mode; Tailwind semantic color names remain; content stays in `content.ts`/API.
- **NFR-8 Compatibility**: hash routing and static hosting remain; the existing Sentry/Umami integration and the CI/CD pipeline keep working.
- **NFR-9 SEO and performance (U6)**: static text is prerendered into the HTML at build; dynamic parts (packages, later gallery) are injected by the CMS host from current data, fresh within minutes; canonical, Open Graph/Twitter, favicon set, JSON-LD (organisation and offers), `robots.txt` and `sitemap.xml`; test hosts serve `Disallow: /` and `X-Robots-Tag: noindex` from the host, not the bundle; Lighthouse in the pipeline on mobile and desktop is a hard gate of at least 0.9 per category (exceptions only with a recorded owner decision); no new third-party scripts.
## Assumptions
- Current copy and texts of the live site (incl. the November text update) are leading unless the design says otherwise.
- The packages API keeps its current shape plus `category`; the CMS session implements it.