Feature: Site Build

Purpose

The project contains a static-site input directory (site.in/) and a generated static-site output directory (site.out/).

The Site Build feature provides the script that converts site.in/ into site.out/.

The generated site is a project summary and dashboard for the AMD MI25 fan-control service. It is deployed at https://labs.bannister.us/projects/amd-mi25-fan-service/ (deployment integration is a later task).

Requirements

• scripts/site-build.sh must generate the static site in site.out/ from the input in site.in/.
• Each site.in/*.txt input file must produce site.out/<name>.html.
• Generated output must be identified as generated.
• The script must accept optional input and output directory arguments.
• When no arguments are given, the script must use site.in/ and site.out/ relative to the repository root.
• The script must be a POSIX shell script.
• The HTML page structure must live in site.in/template.html, not in the build script.
• site.in/template.html must contain the marker line <!-- SITE-CONTENT --> where page content is inserted.
• The site must include a summary page (index.html) and a dashboard page (dashboard.html).
• The dashboard page may contain __TOKEN__ placeholders for live state.
• Live state comes from a generated model file written by scripts/site-state-fetch.sh.
• The default state file is dataflow.out/site-state.txt, overridable with a SITE_STATE_FILE environment variable.
• When the state file is present, the build must substitute its KEY=value lines for matching __KEY__ placeholders.
• When the state file is absent, remaining __KEY__ placeholders must render as unavailable, so the build stays portable.
• The site build must not depend on the live system.

Behavior

• Running the script recreates site.out/ from site.in/.
• Re-running the script overwrites existing output deterministically.
• The summary page renders without any state file.

Dependencies

• None.