OPS Content Platform
A Rust-first content operations workspace for reviewable technical notes, website output and manual social publishing packages.
Problem
Technical content easily gets fragmented across notes, drafts, websites and social channels. For operations-focused writing, that creates two risks: quality drops because the same idea is rewritten from scratch, and sensitive details can leak when content is prepared without a repeatable review step.
Approach
This project keeps source content as Markdown with TOML frontmatter under `content/`. A Rust CLI validates the content model, creates new items and builds a static website locally. Social output is prepared as manual publishing packages, not posted automatically.
What works
- Content validation catches missing frontmatter, unsupported types and unsafe URL slugs.
- The static site build renders pages, notes, project pages, topic pages and an RSS feed from local sources.
- LinkedIn and Instagram drafts can be prepared with manual publishing checklists.
- Generated output under `site/public/` is not versioned.
Limitations
- The public website has simple embedded CSS and no deployment pipeline yet.
- There is no React admin or review UI yet.
- Publication tracking is still a planned model, not an implemented workflow.
Next improvements
- Add more real project and article content to exercise the website structure.
- Introduce publication records once content moves from reviewed to published.
- Add a small internal review UI only when CLI-driven review becomes too slow.