Hero uit het CMS, verschuivingsfix, productie alleen vanaf release-branch #18

Merged
Sluijsens merged 8 commits from feature/hero-module into master 2026-11-17 12:58:07 +01:00
4 changed files with 65 additions and 0 deletions
Showing only changes of commit 0f3b7e0a2e - Show all commits
+1
View File
@@ -4,3 +4,4 @@
|------|------|--------|--------|---------------------|---------------|
| Feature | react-frontend | ✅ Complete | master | React frontend (SLP Software marketing site) | 2026-07-18 |
| Feature | redesign-modern-timetravel | 🔵 Inception | feature/redesign-modern-timetravel | Theme system, Nav, all landing sections, Contact form (+ CMS/API for form endpoint) | 2026-11-09 |
| Feature | hero-module | 🟢 Construction (test) | feature/hero-module | Hero from the CMS (markers, data block, fallback), CI production condition | 2026-11-16 |
@@ -0,0 +1,39 @@
# AI-DLC State Tracking
## Project Information
- **Feature Name**: Hero module, SLS side (hero from the CMS, baked hero as fallback)
- **Feature Slug**: hero-module
- **Project Type**: Brownfield
- **Start Date**: 2026-11-16
- **Current Stage**: Construction, built for the TEST environment only (no production deploy, no merge to master without the user's go)
- **Branch**: feature/hero-module
## Workspace State
- **Existing Code**: Yes
- **Workspace Root**: K:\Development\SlpSoftware\Projects\SlpSoftware
## Code Location Rules
- **Application Code**: Workspace root (NEVER in aidlc-docs/)
- **Feature Documentation**: aidlc-docs/features/hero-module/ only
## Language Configuration
- **Documentation Language**: English
- **Conversation Language**: Dutch
## Extension Configuration
| Extension | Enabled | Decided At |
|---|---|---|
| Security Baseline | Yes | Requirements Analysis |
| Property-Based Testing | Partial (pure functions: title derivation, target validation) | Requirements Analysis |
## Operations Configuration
- **Include Operations Phase**: No, as separate stages. Covered by the joint release checklist (`aidlc-docs/_shared/joint-release-checklist.md`).
## Requirements
The requirements and the site contract are owned by the CMS repository (branch `feature/hero-module`, K:\Development\Projects\SlpModularCms-contact-forms):
- `aidlc-docs/features/hero-module/inception/requirements/requirements.md`
- `aidlc-docs/features/hero-module/inception/requirements/site-contract-agreed-with-asf.md`
- `aidlc-docs/features/hero-module/inception/requirements/hero-comparison.md`
- `docs/hero-module.md`
See `requirements.md` in this folder for the SLS decisions.
+9
View File
@@ -0,0 +1,9 @@
# Audit Log: hero-module (SLS)
## SLS integration started
**Timestamp**: 2026-11-16
**User Input**: "Doe de SLS-kant van de Hero-module integratie. Alles alleen voor TEST; GEEN productie-deploys, geen merge naar master, geen dispatches van workflows." (relayed by the main session, with Bryan's SLS decisions: title with line breaks, lead, two buttons, no tagline or slides; eyebrow and code line fixed text)
**AI Response**: Branch `feature/hero-module` from origin/master. Read the CMS contract, golden files and host renderer. Built markers, `#cms-data` reader in `src/cms-client/hero`, Hero rendering with fallback, derived screen-reader h1, target validation, tests; aligned the production deploy condition with ASF; documented in `docs/hero-integration.md`.
**Context**: Construction, test only.
---
@@ -0,0 +1,16 @@
# Requirements: Hero module, SLS side
Source of truth: the CMS repository (see `aidlc-state.md`). This file holds only what is specific to SLP Software.
## Decisions of Bryan for SLS (2026-11-16)
- The hero comes from the CMS: title (one field, line breaks: "Websites,\napps\n& meer."), lead, two buttons (label + target). No tagline, no slides.
- Fixed text in the site (`src/i18n/nl.json`, block `home.hero`): the small line "Web & .NET development" and the code line "var website = slp.Bouw(uwIdee);".
- Screen-reader/search-engine h1: `home.hero.headingPrefix` ("SLP Software:") + the title lines joined with a single space. Seed result: "SLP Software: Websites, apps & meer."
- The baked hero (`heroContent`, `Hero.tsx`, `Era2026.tsx`, `StaticLanding.tsx`) is the fallback when the CMS delivers nothing (no block, no hero, not live, outside the schedule, invalid data).
- Changes in the CMS are live (NFR-10): the host writes the data block into every page response (60 s cache).
## Contract points used
Markers `<!--CMS:HERO-HTML-->`, `<!--CMS:HERO-PRELOAD-->`, `<!--CMS:DATA-->` and key `hero` in `#cms-data`. Button targets: `#anchor`, `/path`, `https://`. Details and open points: `docs/hero-integration.md`.
## Pipeline
`deploy-production` (and its build) only run for `workflow_dispatch` with `deploy_production == 'true'` on a `release/*` branch, like ASF.