Field note 2026-07-28

Routes begin with ordinary files

Derived paths and explicit claims make each published document predictable before a layout renders.

Every routed document begins as a file below the content root. posts/first.md derives /posts/first/; a page can instead claim an explicit route in front matter.

Syncpress extracts this authored prefix as the collection excerpt before rendering the complete page. The post card may render the converted excerpt as trusted markup, while ordinary front-matter values remain escaped.

Read the build lifecycle for the project-level view.

2026-07-31

Why build a static site generator with a sync engine?

What synchronization adds to a static build, where the design pays off, and where an ordinary pipeline remains the better choice.

A static site generator usually expresses its work as an imperative sequence that reads a directory, transforms each document, and writes another directory.

Syncpress uses synchronization when pages share routes, collections, templates, links, generated assets, and deployment files. Work that begins with one source file can affect output across the site. Publication begins after every required part of the build completes successfully.

2026-07-29

Assets follow explicit references

Local links, downloads, SVGs, and primary raster images each take an explicit output path through the build.

The posts collection sorts data.date in descending order, so this note appears before older entries. Its collection card is limited to publication data and an excerpt.