// 11 matches
oCMS 0.31.0 keeps supported editor formatting, searches readable page text, and warns about removed markup. What changes for editors, and what operators should check before upgrading.
UTC timestamps, mandatory production MFA, and health-aware deployments: what oCMS 0.29 and 0.30 change for developers running real sites.
Five Claude Code presets, four real task types, 60 runs: the light presets passed every check at a tenth of the cost of Opus at high effort. How the harness, the graders and the fairness controls were built.
oCMS now ships a read-only MCP server: ten typed tools let Claude Code, Cursor and other agents search and read site content, with drafts hidden and every API key policy enforced.
AI did not kill engineering. It killed the illusion that typing code was the hard part. In my Claude Code + Go + oCMS workflow, the human job moved upstream: intent, constraints, architecture, verification, and context discipline.
A 54-commit build diary: Claude Desktop drafted the spec, Claude Code executed it, and the result is a production-grade single-binary Go service scheduled by systemd.
Karpathy-style LLM Wiki over oCMS: 106 Markdown pages compiled by Claude Code in one evening, ten documentation contradictions surfaced, wikilint enforcing invariants, CLAUDE.md making the wiki consultable for agents.
The Model Context Protocol is everywhere. Claude Code, ChatGPT, VS Code Copilot, Cursor — they all speak MCP now. But if you search for "how to build an MCP server," you'll drown in Python and...
How a pen test finding turned into a shipped feature — planned, coded, tested, and pushed to production from a phone while walking a dog along the Rhône, using Claude Code in the browser.
A deep technical dive into building oCMS — a full-featured content management system in Go. Architecture decisions, library choices, mistakes made, and lessons learned after five months of development.