4.3 KiB
Requirements Analysis — Questions
Fill in each
[Answer]:tag. Options A-E plus X (Other). The file is the authoritative record of your requirements decisions.
Q1: Edition length
Should the generator produce a single self-contained page, or support multi-page newspapers that flow across printed A4 sheets?
A) Single page — the whole newspaper is one page, printed on one A4 sheet B) Multi-page — content flows across multiple A4 sheets with automatic page breaks (recommended for a real newspaper feel) C) Single long scrolling page that the browser splits across sheets when printing X) Other (please specify)
Answer: B its a must have I want this to work across pages
Q2: Masthead & issue identity
Does the newspaper need a classic newspaper masthead (title banner, date/issue line, volume)?
A) Yes — a title banner plus a date / issue / "Volume X" line (recommended) B) Title banner only, no date/issue metadata C) No masthead — just the article layout X) Other (please specify)
Q3: Article types / sections
Which content types should the layout support? (choose all that apply)
A) Lead/front-page story B) Interior news articles with headings + bylines C) Pull quotes / sidebars / fact boxes D) A "schedule" or "events" block (e.g. ceremony / reception timetable) E) A lighter section (messages/letters, well-wishes, memory corner) X) Other (please specify)
Answer: A, B, C, D, E, and X - i want crosswords and comics as well please, I'd love a little xkcd that somehow relates to the main page (you'll have to pull this obvoiusly with context)
Q4: Photos and images
Should articles support embedded photos/images, or is the newspaper text-focused?
A) Photos supported — images placed per article with captions (recommended) B) Photos supported, layout auto-balances them into columns C) Text only — no image support needed for now X) Other (please specify)
Q5: Visual theme
What visual style should the newspaper have? (This drives the print CSS.)
A) Classic broadsheet: black ink on white/cream, serif headlines and body, column rules (recommended) B) Cream/off-white paper tint with ink text — a warmer, vintage wedding feel C) A color-accented modern tabloid (one accent color for section headers) X) Other (please specify)
Q6: Auto-generated copy
The generator may optionally call AI to draft the newspaper copy before rendering. Which AI route should we use, given the project must stay fully local with no external services?
A) Local AI via Ollama (runs on the LAN, never leaves the machine) — recommended B) No AI generation — the script only renders copy I provide C) An external AI API (cloud LLM) — requires a key and sends content off-machine X) Other (please specify)
Answer: A ollama is on this laptop and ready to go. You are free to use deepseek-v4-flash:cloud
Q7: Print fidelity
Any fixed target for the printed output (page count, margins, print quality)?
A) Fluid — content auto-flows across as many A4 pages as it needs, with sensible margins and clean page breaks (recommended) B) Fixed target — fit within a set page count (e.g. exactly 2 A4 pages) regardless of content C) Tune margins/typography for maximum A4 ink-jet crispness X) Other (please specify)
Consolidated Summary Confirmation
Summary of your seven requirements answers before the requirements document is generated:
- Edition length: multi-page — content flows across multiple A4 sheets with automatic page breaks (must-have)
- Masthead: yes — title banner plus date / issue / "Volume X" line
- Article types (all selected): lead story, interior articles with bylines, pull quotes/sidebars/fact boxes, schedule/events block, lighter messages/well-wishes corner — plus crosswords and comics, and an xkcd-style front-page cartoon relating to the day
- Photos: auto-balanced into columns per article
- Visual theme: classic broadsheet — black ink on white/cream, serif headlines and body, column rules
- AI route: local Ollama (granted
deepseek-v4-flash:cloudfor copy generation)- Print fidelity: fluid — flows across as many A4 pages as needed, sensible margins, clean page breaks
Does this all look correct before I generate the requirements artifact?
- Looks correct
- Request changes
Answer: Looks correct