Use an original two-page Hugo static site generator fixture to trace source, template selection and fresh artifacts. Record preview, normal build and deployment as different states. A successful local build is useful evidence, but it is not a live website.
Record the version before preparing the project
The reviewed Hugo quick start specifies v0.158.0 or later and excludes draft content from default builds. Its draft-including preview uses the buildDrafts option. These documentation facts do not establish an installed local version.
For the native project field-notes, first record the actual Hugo version, environment, configuration and command. Compare them with the reviewed documentation before creating layouts. The local HTML example does not install Hugo, download a theme, create a native project or start a server.
Keep the example original and theme-free. The useful preparation artifact is a source/layout/configuration plan and an acceptance manifest, rather than an inherited theme whose lookup behavior has not been inspected.
Make the two source pages easy to trace
| Source | Front-matter title | Draft | Original body specification |
|---|---|---|---|
| content/welcome.md | Welcome | false | Introduction heading; “Keep field observations with their source.” |
| content/pending.md | Pending | true | Introduction heading; “Review this note before release.” |
Each page has one authored Introduction heading in its body; its page title comes from the page template. Do not duplicate the same title as another body heading merely to make a screenshot look complete.
The content inventory should retain the exact body text and draft value. Create the actual native source files only after confirming the template mapping. No dates, images or external integrations are necessary for this fixture.
Map page kinds to original layouts
Hugo's current template-type documentation describes layouts/baseof.html, home.html and page.html. A base supplies shared structure; home renders the home page and page renders a regular page. Template selection depends on the applicable lookup rules, so a familiar historical layout path is not enough to establish selection in the implementation.
| Planned layout | Original responsibility |
|---|---|
| layouts/baseof.html | Shared document structure and named main block |
| layouts/home.html | Main definition listing the rendered regular pages |
| layouts/page.html | Main definition with page title and body content |
The reviewed base-application conditions require a child template to include a define action and contain only defines, whitespace and template comments. Matching defines replace named base blocks. Plan the child's content inside the main definition; loose markup outside it can prevent the expected base from applying.
That explanation is a source plan, not a copy of the documentation's template. Later tests must confirm that the actual original layouts are selected, the base appears, and the content/title are rendered exactly once.
Separate preview from the acceptance build
In the intended draft-including preview, both Welcome and Pending are available. That visibility is deliberate and does not change pending.md's draft flag.
The normal acceptance build uses the same recorded source/configuration with drafts excluded and a new separate output destination. Its expected home list contains Welcome and omits Pending. Verify that the Pending route and its authored body are absent from the fresh artifact set, not merely hidden from one menu.
Use a fresh destination for each acceptance run so stale files cannot masquerade as current output. Do not delete a shared directory to obtain freshness. The future build plan should choose isolated output paths and record them in the manifest.
| Check | Draft preview expectation | Fresh normal-build expectation |
|---|---|---|
| Welcome page and body | Included | Included |
| Pending page and body | Included intentionally | Excluded |
| Home links | Include both rendered pages | Welcome only among these two pages |
| Output evidence | Preview context identified | New destination and actual command recorded |
Other generated files may exist. The two authored pages do not imply exactly two artifacts, and the manifest should distinguish generated support files from the fixture's acceptance checks.
Inspect generated links and deployment status
Use generated page references for the home links, then inspect their actual routes under the selected configuration. Verify that links reach the corresponding output pages and do not point to Markdown files or the draft preview context.
The quick start distinguishes rendering local build artifacts from deployment. Keep “built locally” and “deployed” as separate evidence fields. This example does not upload or publish a site, push a repository, configure a host or trigger a release.
The native source, layouts, configuration, version/command manifest and review ledger remain the primary deliverable. Leave actual build logs, artifact paths/hashes, browser checks and deployment evidence blank until those actions occur.
Copyable source-to-output prompt
Prepare an original native source/layout/configuration plan and fresh-output acceptance manifest for a future theme-free Hugo project field-notes. Record actual Hugo version/environment before implementation; reviewed quick-start requirement is v0.158.0+, not an installed-version claim. Do not install, create code/HTML, run a server/build or deploy at this preparation stage.
Two regular-page specifications: content/welcome.md title Welcome/draft false/body Introduction plus “Keep field observations with their source.”; content/pending.md title Pending/draft true/body Introduction plus “Review this note before release.” One authored Introduction heading each; page template supplies title. No copied theme/example templates or invented assets/dates.
Map current documented layouts/baseof.html shared structure/main block; layouts/home.html main definition lists rendered regular pages; layouts/page.html main definition renders title/content. Verify actual version/lookup selection later. Child base application requires at least one define and only defines/whitespace/template comments; matching block/define names, no loose child markup. Prepare original templates after mapping approval.
Draft-including preview intentionally includes both pages without changing draft flag. Normal build to a new isolated output destination excludes Pending route/body and home link, includes Welcome. No stale prior output as evidence and no shared-directory deletion. Manifest version/config/command/source hashes/output destination/log/artifact paths and acceptance results; actual results blank until run. Generated support files may exist, not exactly two artifacts.
Verify selected layouts/base/title/content once, normal versus draft behavior and actual generated page links/routes. Source Markdown is not deployed HTML. Local artifact rendering and network deployment are separate; no automatic push/host/speed/SEO guarantee. Native files/manifest/review ledger primary. Mark actual source/template/build/link/render/article-width/360 px and NOS runtime checks not_tested. No NOS Hugo compiler or project-import claim.
Optional use for already generated HTML
Keep the native Hugo project and build manifest as the primary developer materials. NOS supports saving and rendering a prepared HTML sample. Verify that sample and its required assets in the actual workspace; this does not establish Hugo compilation or whole-project import in NOS.
Explore NOS with a prepared HTML sample, keeping actual native build evidence separate from the source plan and expected output.