This blog is for short, readable updates about LatexDo: release notes, writing workflow decisions, LaTeX editor details, and the small engineering notes that are easier to publish as posts than as full documentation pages.
Why this exists
LatexDo has a main product site, documentation, and a browser editor. A blog needs a different shape: one Markdown file per post, a stable URL, clean metadata, RSS, and a layout that does not interrupt the reader.
The goal is simple:
- write Markdown in
content/posts/ - commit the file
- let CI build the static pages
- publish readable HTML with the same LatexDo header, footer, and CSS
A tiny workflow
The local build uses Node only, with no runtime framework and no Markdown package dependency. That keeps the site easy to audit and keeps CI predictable.
npm run build
npm run checkIf those commands pass, the post is ready to ship.