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.

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.