DocCharm: Automating Help Center Updates via GitHub

DocCharm automates help center updates by watching GitHub repositories and using AI to suggest article revisions or drafts when features change, with every suggestion entering a human review queue before publication. The platform supports Zendesk and Mintlify, runs on a Haskell/Yesod backend with NixOS infrastructure, and uses SQLite with Litestream for tenant-per-database architecture.

DocCharm: Automating Help Center Updates via GitHub Keeping documentation in sync with a rapidly evolving product is a nightmare—most help centers become obsolete the moment a new PR is merged. DocCharm solves this by watching GitHub repositories and using AI to suggest updates to existing articles or draft new ones when features change. From a technical architecture standpoint, the stack is interesting for those who prefer stability and type safety over the usual JS-heavy defaults: It is essentially a real-world deployment of a documentation agent that bridges the gap between the codebase the source of truth and the end-user help center. If you're dealing with documentation drift, this is a practical way to ensure your users aren't reading outdated guides while your devs are shipping updates daily. The logic here isn't "auto-pilot" but "co-pilot." Every AI-generated suggestion hits a review queue first, ensuring a human verifies the technical accuracy before anything goes live. This prevents the hallucination risks usually associated with LLM-driven documentation. For those integrating this into an AI workflow, the compatibility is already quite broad: Supported Platforms: Native imports for Zendesk and Mintlify. Branding: Custom theming support to maintain corporate identity. From a technical architecture standpoint, the stack is interesting for those who prefer stability and type safety over the usual JS-heavy defaults: Backend: Haskell/Yesod Infrastructure: NixOS Database: SQLite with Litestream tenant-per-db architecture Monitoring: Sentry, Prometheus, and Grafana Transactional Email: Resend Billing: Stripe It is essentially a real-world deployment of a documentation agent that bridges the gap between the codebase the source of truth and the end-user help center. If you're dealing with documentation drift, this is a practical way to ensure your users aren't reading outdated guides while your devs are shipping updates daily. Story tracker · related coverage OpenAI vs Open-Weight Models: The Battle for the Bottom Line 8h ago /en/news/2290/ Open Weight AI: Why Restrictions Hurt Innovation 9h ago /en/news/2252/ Claude Code vs. Guardrails: The Cost of Control 9h ago /en/news/2236/ Claude Code: Is Anthropic Overpaying for Our Devs? 10h ago /en/news/2219/ Claude Fable: Reverse Engineering the Jacobian Conjecture 10h ago /en/news/2200/ Skyfall AI: Replacing SaaS CEOs with AI Agents 11h ago /en/news/2180/ Next Open Weight AI: Why Restrictions Hurt Innovation → /en/news/2252/ All Replies （3） D I use a similar setup; adding a changelog trigger really helps keep the docs current. 0 A Been there. Spent way too many hours manually updating guides after every single release. 0 A Does it handle markdown rendering automatically or do you have to format the output manually? 0