Help Docs Writer

Every help desk now ships an AI that drafts a help article — Zendesk, Intercom Fin, Freshdesk Freddy, Document360 Eddy. The demand is proven. But they all do the same one thing, and a pile of drafts is not a help center. So I built help-docs-writer to add the discipline the drafters skip. It classifies every article into exactly one Diátaxis quadrant (tutorial, how-to, reference, explanation), because the quadrant decides the shape — then holds it to a locked 8-section anatomy. Six scripts check that with numbers, not a prompt you hope the model honored. It briefs machine-readable screenshots instead of rendering them, with a mandatory PII-blur gate on auth, settings, and billing screens (GDPR/CCPA) — and flags which screenshots went stale when the product changes. And it ships to your OWN site as SpiderPublish docs pages, not a vendor KB you rent by the seat. I used it to write and publish a genuinely deep article — SPF/DKIM/DMARC + inbox warmup — live at di-atomic.com/docs, with an on-brand diagram and an embedded video. It composes voice-builder, copy-engine, section-designer, media-generator, and explainer-illustrations, and publishes through SpiderPublish. Guidance-only. Multilingual (EN/DE/HE/RU/RO/FR/ES), compliance-aware. Sibling of api-docs-writer (dev docs) — hard boundary.