Fill the scaffold with an original reporting example
This is an original fictional school-project issue, not a real school event. Its supplied notes are:
- N1: Room 8 opened a book-swap shelf on October 20, 2026.
- N2: The shelf started with 24 donated books.
- N3: Opening hours have not been confirmed.
Issue: Room 8 Practice Press. Date: October 21, 2026. Byline: Demonstration reporting team. These are fictional issue labels.
Headline: Room 8 Opens Book-Swap Shelf With 24 Donated Books
Lead: Room 8 opened a book-swap shelf on October 20 with 24 donated books.
Short body: The practice note set identifies the room, opening date, and starting book count. It does not include an interview or a confirmed opening-hours schedule.
Use an original schematic illustration of a shelf, with the caption Illustration of a book-swap shelf; not a photograph of an actual event. A drawing with a few book shapes should not imply a visual count of all 24 donations.
The public school-newspaper template description includes issue fields and a two-article structure. The reporting, source checks, and illustration specification here are original rather than a copy of its downloadable artwork.
Make the second brief useful without inventing hours
Brief headline: Book-Swap Hours Await Confirmation
Brief text: Opening hours are not confirmed in the supplied practice notes. The reporting team needs the approved schedule before adding hours to the issue.
That brief gives the editor a next reporting task. It does not supply “open every lunch period” merely because that would fit a school story. Leave a source-request field: Hours / person to confirm / response date: [TO SUPPLY].
Separate reader copy from editorial checking
The reader version includes the two finished original texts and their fictional-example label. The editor version keeps the same asserted facts and adds a claim-to-note map:
| Claim | Supporting note | Editorial action |
|---|---|---|
| Room 8 opened the shelf on October 20. | N1 | Keep the room and date consistent in headline/lead. |
| It started with 24 donated books. | N2 | Preserve the starting-count wording; do not invent later totals. |
| Opening hours | N3 says unconfirmed | Do not assert a schedule; request confirmation. |
Switching views must not change the news facts. Editorial highlighting helps inspect the notes; it is not verification of a real event or permission to publish it.
Plan columns around article order
Give the main story one clear start, followed by its body and caption, then the short brief. On a narrow screen, stack those complete blocks in that order. Do not interleave the first paragraph of one story with the second paragraph of another because their desktop columns happen to align.
Keep headlines readable without oversized masthead decoration displacing the lead. Confirm the source permissions and required Word or print format in your school's original workflow. A preview is not a published newspaper or a tested print output.
Copy a newspaper-scaffold prompt
Draft an original newspaper scaffold and filled reporting example in US English.
Issue/title/date/byline: [inputs]
Permitted reporting notes with stable note IDs: [inputs]
Confirmed facts versus open questions: [inputs]
Story count, illustration permissions and required output format: [inputs]
Create a supported headline, lead, short body, caption, and separate brief. Map each asserted fact to a supplied note. Keep unconfirmed facts visibly unresolved and include the next reporting request. Reader/editor versions must retain identical asserted facts. Use an original schematic illustration description only if requested; label it as an illustration, never an event photo.
Specify complete article reading order on desktop and narrow screens; do not interleave story paragraphs. Do not invent interviews, quotes, names/photos of real pupils, events, counts, hours, permissions, or publication results. Use [NEEDED: input] for gaps and label fictional notes/examples persistently. Return copy and layout requirements, keeping source notes, permissions and required Word/print files in the approved workflow.
Read the proof beside the notes
If you prepare an HTML issue proof, NOS can save and render it while you compare the headline and lead with N1/N2 and inspect the unresolved-hours brief. Keep approved reporting notes and source permissions in their original locations. End with one readable story supported by its notes and one clearly named fact to confirm before expanding the issue.