Files
SlpSoftware/aidlc-docs/features/hero-module/requirements.md
T

1.3 KiB

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.