Xandrov Labs publishes long-form strategy content — two companion volumes intended for serious, extended reading. These documents demand book-like ergonomics: readable typography, clear navigation, dark mode, progress tracking. But the author should not be forced to think about design or deployment; the source of truth must remain plain Markdown. The system exists to close this gap, delivering professional reading experience without authoring friction or manual deployment steps.
Long-form documents deserve book-quality reading ergonomics — sticky table of contents, reading progress indicators, light and dark modes, styled tables and callouts — yet generating such output by hand is error-prone and slow. The challenge: keep the source in plain Markdown — the author's native format — while shipping polished, feature-complete HTML. This requires a build system that handles both the ergonomic requirements and end-to-end automation, without placing extra burden on the writer.
A Node build tool reads Markdown files from docs/ and renders them into a complete static site. The tool generates not only content pages but also index, robots.txt, response headers, and 404 error handlers. Every push to main triggers CI to rebuild and deploy automatically to production.
The rendering pipeline produces sticky-scrolling table of contents, reading-progress indicators, light-and-dark theme support, and styled semantic elements for tables, callouts, and footnotes. All features flow from Markdown source — there is no hand-coded HTML in the output. The build process is deterministic and repeatable, ensuring the rendered site always reflects the current state of source documents.
Book-quality reading ergonomics from plain Markdown.
The system is live in production at rs.xandrov.com, deploying automatically on every push to main via CI/CD. Authors shift focus entirely to content — writing and refining Markdown — while the pipeline ensures readers consistently receive polished, book-quality reading ergonomics without manual intervention. The entire workflow from commit to deployment is hands-off.
The description focuses on the technical architecture and deployment pipeline. Specific content, internal performance metrics, and proprietary build configuration details are not included. The system's strategy-content purpose is noted but the volumes themselves remain private to the lab.