# Small personal site

Use an installed V2 engine, three Markdown pages and a static host. No editor accounts are needed. This fictional Field Notes example is public-safe; your real notes may not be.

# Decide the audience

Hidden navigation is not privacy. Search and direct URLs can expose built pages. Work in a disposable installed project and preserve current source/config first.

# Create the source

content/
  _index.md
  notes/
    _index.md
    workstation.md

Root content/_index.md:

---
title: Field Notes
description: Read-only checks for my documentation workstation.
---

# Field Notes

Start with [Workstation check](/notes/workstation-check/).

Section content/notes/_index.md:

---
title: Notes
description: Repeatable checks with expected results.
order: 10
---

# Notes

[Workstation check](/notes/workstation-check/) verifies installed tools.

Article content/notes/workstation.md:

---
title: Workstation check
description: Confirm Node and npm before building.
---

# Workstation check

Use this in the installed MarkStack project before a local build.
It reads versions; it does not install or change tools.

## Installed tools

1. Open a terminal in the project.
2. Run `node --version` and `npm --version`.
3. Node must be 24 or newer for this pinned engine.

## If a tool is missing

Stop the build and use your operating system's approved Node installation
process. Reopen the terminal and repeat the version checks.

## Verify

Record actual version output. Continue only when both tools are available
and Node meets the requirement.

The physical file is workstation.md; its title produces /notes/workstation-check. A host may normalize the trailing slash. These specimen links belong to your example installation, not promised markstack.app routes.

# Build and inspect

After locked dependencies are available, from the installed project:

npm run build
npm run serve

Build recreates output. Keep valuable files outside that target. Serve is local preview, not a production access gate or process supervisor.

Deploy only reviewed generated output to the chosen host. Recheck actual root/deep routes, search and assets. Local success does not certify host TLS, redirects or authorization.

# Maintain and recover

Keep source/config/media and engine pin in your versioned recovery process. Change dates after real review. Preserve stable titles when links matter. Test a changed procedure before describing it as verified.

For isolated networks, prepare dependencies first, use local authored media and serve output over HTTP/HTTPS. Test search/fonts/diagrams under actual network isolation. V2 is not a service-worker offline app; USB file:// loading is not equivalent acceptance.