Future frontpage
A stubbed generator of a future front page from fixture copy, matching layout goldens and including the dated items.
This is a small site spec on Spekkr, published by lume. It is listed with the other specs. Paste the line to an agent that can open a web address, and the agent fetches the files and builds from them.
- Spec
lume/future-frontpage- Version
- 0.2.1
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/future-frontpage/start.md.
Paste this to your AI agent. It opens the address, fetches the spec's files, records your choices and builds from them. Nothing to install, no account.
Published by lume.
What does the result look like?
What can I customize?
Your choices go into the line you copy. Anything else is yours to edit, but it leaves the tested path.
What do I get?
-
spec.mdRequirements and acceptance checks.Future frontpage
What this builds
A generator that lays out a newspaper-like front page from a deck of stories. In CI the generator is a stub that places fixture copy into a documented layout, not a paid language-model API. The edition date is frozen. The page must include the dated items from the fixture and match layout goldens. The paper's name and the stories are original. Nothing is a real news claim.
Read
spekkr.inputs.jsonfirst.titleis the masthead.dateis the edition.editionchooses the copy deck.kickerandwebchange the layout. No paid API is used in the checks.Out of scope
- A paid language-model API in the checks.
- A live news scrape or a real masthead.
- A claim that the stories happened.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Placement and dates
fixtures/edition-a.jsonlists stories, kickers, and a date. The generated page includes every headline in that file, and showsdateon the masthead in a documented format.- A story marked
datedincludes its own date line, which must match the file. - A fetch hook fails if a known model or news host is contacted.
Accept when: every headline and dated line is present, the masthead date matches, and the hook stays quiet.
R2. Frames and files
- Goldens: the print-like front, a web-density front, a close of the lead story, and a close of a dated item.
- One command runs the stub, the hook, and writes the frames. No network and no paid API.
Accept when: the command passes for both editions, and the frames match the goldens.
R3. Inputs
- The build reads
spekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key.
Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check.
R4. Checks and report
- One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them.
- Checks do not need a network, a paid API, or physical hardware.
Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it.
Verification
A stubbed generator plus fixture copy produces a page that matches layout goldens and includes every dated item and headline from the file. The edition date is frozen. A fetch hook fails if a paid model or a news host is contacted. No network is required in CI.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to add a story, how the stub places them, and how to run the checks.
# Future frontpage ## What this builds A generator that lays out a newspaper-like front page from a deck of stories. In CI the generator is a stub that places fixture copy into a documented layout, not a paid language-model API. The edition date is frozen. The page must include the dated items from the fixture and match layout goldens. The paper's name and the stories are original. Nothing is a real news claim. Read `spekkr.inputs.json` first. `title` is the masthead. `date` is the edition. `edition` chooses the copy deck. `kicker` and `web` change the layout. No paid API is used in the checks. ## Out of scope - A paid language-model API in the checks. - A live news scrape or a real masthead. - A claim that the stories happened. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Placement and dates - `fixtures/edition-a.json` lists stories, kickers, and a date. The generated page includes every headline in that file, and shows `date` on the masthead in a documented format. - A story marked `dated` includes its own date line, which must match the file. - A fetch hook fails if a known model or news host is contacted. Accept when: every headline and dated line is present, the masthead date matches, and the hook stays quiet. ### R2. Frames and files - Goldens: the print-like front, a web-density front, a close of the lead story, and a close of a dated item. - One command runs the stub, the hook, and writes the frames. No network and no paid API. Accept when: the command passes for both editions, and the frames match the goldens. ### R3. Inputs - The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key. Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check. ### R4. Checks and report - One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. - Checks do not need a network, a paid API, or physical hardware. Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it. ## Verification A stubbed generator plus fixture copy produces a page that matches layout goldens and includes every dated item and headline from the file. The edition date is frozen. A fetch hook fails if a paid model or a news host is contacted. No network is required in CI. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to add a story, how the stub places them, and how to run the checks.
-
design.mdThe fixture copy deck, the stubbed layout, and dated items.Design
This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold.
Layout
A documented grid (columns, a lead well, a sidebar) in
fixtures/front-layout.json. The stub places the lead story first, then others in file order. The masthead date format is3 April 2031for2031-04-03(day month year, no leading zero on day).Screenshot tolerance
8 levels, 98% of pixels. Headlines on the page must also match the file exactly.
Inputs
Key Label Default Notes titleMasthead The Millstead Signal Shown at the top of the page. dateEdition date 2031-04-03 A frozen date for the edition. Checks use this, not wall-clock today. kickerShow kickers on A short label above a story. webWeb density off If on, a tighter column; if off, a print-like front page. editionEdition fixture-a Shipped copy decks. The generator is a stub, not a paid model API. Acceptance at the defaults
The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins.
Fixture Role fixtures/edition-a.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/front-layout.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.spekkr.inputs.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy.
Screenshots
These pictures are headless-Chrome captures of the working reference in
reference/preview.html, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel.File What it shows shots/mast.pngThe Millstead Signal, 3 April 2031, fixture copy in the lead and the mast. How to verify
- Run the checks at the default inputs, without a network.
- Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file.
- Repeat once at the person's inputs when they differ from the defaults.
- A stubbed generator plus fixture copy produces a page that matches layout goldens and includes every dated item and headline from the file. The edition date is frozen. A fetch hook fails if a paid model or a news host is contacted. No network is required in CI.
# Design This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold. ## Layout A documented grid (columns, a lead well, a sidebar) in `fixtures/front-layout.json`. The stub places the lead story first, then others in file order. The masthead date format is `3 April 2031` for `2031-04-03` (day month year, no leading zero on day). ## Screenshot tolerance 8 levels, 98% of pixels. Headlines on the page must also match the file exactly. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Masthead | The Millstead Signal | Shown at the top of the page. | | `date` | Edition date | 2031-04-03 | A frozen date for the edition. Checks use this, not wall-clock today. | | `kicker` | Show kickers | on | A short label above a story. | | `web` | Web density | off | If on, a tighter column; if off, a print-like front page. | | `edition` | Edition | fixture-a | Shipped copy decks. The generator is a stub, not a paid model API. | ## Acceptance at the defaults The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins. | Fixture | Role | | --- | --- | | `fixtures/edition-a.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/front-layout.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy. ## Screenshots These pictures are headless-Chrome captures of the working reference in `reference/preview.html`, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel. | File | What it shows | | --- | --- | | `shots/mast.png` | The Millstead Signal, 3 April 2031, fixture copy in the lead and the mast. | ## How to verify 1. Run the checks at the default inputs, without a network. 2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file. 3. Repeat once at the person's inputs when they differ from the defaults. 4. A stubbed generator plus fixture copy produces a page that matches layout goldens and includes every dated item and headline from the file. The edition date is frozen. A fetch hook fails if a paid model or a news host is contacted. No network is required in CI.
-
tasks.mdBuild tasks in order, each with a check.Tasks
Work in order. Finish a task's check before starting the next.
- Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read
spekkr.inputs.jsonfirst. Check: a blank or heading page loads, and an empty test run passes. - Placement and dates (R1). Build what
R1. Placement and datesasks for, to the numbers indesign.md. In particular:fixtures/edition-a.jsonlists stories, kickers, and a date. The generated page includes every headline in that file, and showsdateon the masthead in a documented format. Check: theR1. Placement and datesacceptance checks pass. - Frames and files (R2). Build what
R2. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens: the print-like front, a web-density front, a close of the lead story, and a close of a dated item. Check: theR2. Frames and filesacceptance checks pass. - Inputs (R3). Build what
R3. Inputsasks for, to the numbers indesign.md. In particular: The build readsspekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: theR3. Inputsacceptance checks pass. - Checks and report (R4). Build what
R4. Checks and reportasks for, to the numbers indesign.md. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: theR4. Checks and reportacceptance checks pass. - Goldens. Capture the frames named in
design.mdat the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. - Finish. Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in
spec.mdis true.
# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read `spekkr.inputs.json` first. Check: a blank or heading page loads, and an empty test run passes. 2. **Placement and dates (R1).** Build what `R1. Placement and dates` asks for, to the numbers in `design.md`. In particular: `fixtures/edition-a.json` lists stories, kickers, and a date. The generated page includes every headline in that file, and shows `date` on the masthead in a documented format. Check: the `R1. Placement and dates` acceptance checks pass. 3. **Frames and files (R2).** Build what `R2. Frames and files` asks for, to the numbers in `design.md`. In particular: Goldens: the print-like front, a web-density front, a close of the lead story, and a close of a dated item. Check: the `R2. Frames and files` acceptance checks pass. 4. **Inputs (R3).** Build what `R3. Inputs` asks for, to the numbers in `design.md`. In particular: The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: the `R3. Inputs` acceptance checks pass. 5. **Checks and report (R4).** Build what `R4. Checks and report` asks for, to the numbers in `design.md`. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: the `R4. Checks and report` acceptance checks pass. 6. **Goldens.** Capture the frames named in `design.md` at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. 7. **Finish.** Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in `spec.md` is true.
- Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read
-
reference/preview.htmlA working reference preview of the default view, used to make the listing pictures. A build does not have to start from this file. -
reference/fonts/fonts.cssWebfont faces for the reference preview. -
reference/fonts/Geist.ttfGeist variable typeface for the reference preview. -
reference/fonts/Newsreader.ttfNewsreader variable typeface for the reference preview. -
reference/fonts/Newsreader-Italic.ttfNewsreader italic variable typeface for the reference preview. -
reference/fonts/Fraunces.ttfFraunces variable typeface for the reference preview. -
reference/fonts/Fraunces-Italic.ttfFraunces italic variable typeface for the reference preview.
Is it for me?
- Kind
- small site
- Platforms
- web
- Tools
- TypeScript
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runnerinstall a tool that compares screenshots
What changed?
- 0.2.115 Nov 2026Names what it builds.
- 0.2.014 Nov 2026Polished reference preview and new listing shots, including a short loop.
- 0.1.014 Nov 2026First version.
For agents: start.md says how to build this spec, spec.json holds everything on this page, and bundle.tar.gz holds its files.