A draft isn't a help center. This is the discipline that makes one.
Every help desk now writes your docs. I built the part they skip: Diátaxis classification, screenshot briefs with a PII-blur gate, and documentation that ships to your own site, not a locked vendor KB.
What it does that the drafters don't
Classifies every article
Tutorial, how-to, reference, or explanation, declared up front and held to a locked eight-section shape by six scripts that pass or fail with numbers.
Briefs your screenshots
Machine-readable specs with a required blur list for auth, settings, and billing screens, so nothing leaks. Flags the stale ones when your UI ships.
Ships to your own site
Output lands as SpiderPublish docs on your own domain, in your design. You own the help center, not a login to one.
Audits the gaps
Finds orphaned articles, missing Diátaxis coverage, and stale screenshots, so the center stays trustworthy as it grows.
Speaks seven languages
EN, DE, HE, RU, RO, FR, ES, with the blur discipline built for regulated, compliance-heavy products.
Guidance-only, no black box
It reads its own playbook and does the work with the model you already trust, then hands the finished article to SpiderPublish.
Get the help-center discipline
help-docs-writer is live on the OPVS marketplace. Trigger it with "plan a help center" or "write a help article."
View on the marketplace