Latent Margins

Technical Note

Designing a Technical Publishing Stack

A first vertical slice for code-heavy posts, Mermaid diagrams, and static-first publishing.

1 min read
astro python diagrams

Technical blogs work best when the writing format stays plain, the output is fast, and richer explanations can appear exactly where they help. Astro content collections give the site a typed Markdown layer astro-content, while uv keeps the Python-side tooling fast and reproducible uv.

Build Flow

flowchart LR A[Markdown and MDX posts] --> B[Astro content collections] B --> C[Static HTML] D[uv Python tools] --> B C --> E[Cloudflare Pages]

Python Tooling

The site can stay static while Python handles validation and publishing chores at build time.

from pathlib import Path

POSTS = Path("src/content/blog")

def slugs() -> list[str]:
    return sorted(path.stem for path in POSTS.glob("*.mdx"))

That split keeps hosting simple and makes the authoring workflow pleasant.

Citation

Please cite this work as:

Latent Margins, "Designing a Technical Publishing Stack", Latent Margins, May 2026. https://boredatthemoment.github.io/latent-margins/blog/technical-blog-stack/

Or use the BibTeX citation:

@article{latentmargins2026designingatechnicalpublishingstack,
  author = {Latent Margins},
  title = {Designing a Technical Publishing Stack},
  journal = {Latent Margins},
  year = {2026},
  month = {May},
  url = {https://boredatthemoment.github.io/latent-margins/blog/technical-blog-stack/},
}