2026-03-30
Build Reports Make Incremental Work Visible
The build report API exposes which routes and assets were emitted, skipped, restored, or removed so incremental behavior is observable instead of mysterious.
Blog
The blog is where implementation slices, dogfooding lessons, and media-pipeline work are recorded in public.
2026-03-30
The build report API exposes which routes and assets were emitted, skipped, restored, or removed so incremental behavior is observable instead of mysterious.
2026-03-30
Route shape, artifact semantics, and page output policy are separate decisions so the site can emit pages, XML, JSON, and literal flat files without awkward special cases.
2026-03-30
Generated route families keep taxonomies, sitemap pages, and other computed outputs explicit without pushing route bookkeeping into the site program.
2026-03-30
The asset pipeline preserves HDR semantics across supported AVIF, PNG, and JPEG paths while keeping the site-facing API format-agnostic.
2026-03-30
The asset pipeline lets site code request the output it wants while keeping source formats, caching, and media transforms behind a smaller Rust API.
2026-03-30
Markdown-generated tags can be replaced with Rust functions so links, images, and other authored content remain customizable without turning markdown into an opaque HTML string step.
2026-03-30
New image-probing helpers let route handlers and markdown components inspect authored image format and dimensions before deciding which outputs to generate.
2026-03-30
Frontmatter validation and typed entry references let the site fail early on semantic content errors without turning every route into defensive plumbing.