Skip to main content

​
Frequently Asked Questions

​
Auto-Generated Documentation Platform

When you merge a feature to main with a spec in the Docs/specs/ directory, the auto-generation pipeline publishes end-user documentation to the docs site within 1 hour. The pipeline also generates distributor sales resources and publishes them to the Coda workspace in the same run.
No. The pipeline auto-generates both end-user manuals and distributor sales resources directly from your feature spec and frontend code. You write the spec once, and the system transforms it into customer-facing documentation using Fiftyknots brand voice.
The pipeline flags specs that are too thin for quality end-user docs rather than generating low-quality content. You’ll receive a notification to enrich the spec with additional detail before the documentation can be published.
The pipeline includes a content classification layer that automatically filters internal-only information from external outputs. All generated content enters a pending review state before first publish, giving you a chance to verify that sensitive details are properly excluded.
Yes. The docs site supports versioned documentation that matches platform releases. Customers see docs for their deployed version by default, with a version selector available to view what changed in newer releases.
The pipeline generates feature battle cards with value proposition, target persona, use cases, competitive positioning, and objection handling. It also creates entries for interactive ROI calculators, feature comparison matrices, and updates the What’s New changelog.
The pipeline can’t auto-generate UI screenshots from specs alone. It generates placeholder markers where screenshots should go, which you can fill manually, or it can integrate with a headless browser for automated captures.
The pipeline detects deprecated or removed features and automatically archives or removes the corresponding documentation. This prevents customers from finding outdated guides for features that no longer exist.
End-user manuals, how-tos, FAQs, and distributor sales resources don’t exist yet. Creating and maintaining them manually is unsustainable as features ship weekly. Distributors have no self-serve resource library. An auto-generation pipeline that farms the monorepo knowledge base (23+ feature specs, …
The system handles this scenario gracefully. See the feature documentation for details on how Auto-Generated Documentation Platform manages this case.
The system handles this scenario gracefully. See the feature documentation for details on how Auto-Generated Documentation Platform manages this case.
The system handles this scenario gracefully. See the feature documentation for details on how Auto-Generated Documentation Platform manages this case.
The system handles this scenario gracefully. See the feature documentation for details on how Auto-Generated Documentation Platform manages this case.
The system handles this scenario gracefully. See the feature documentation for details on how Auto-Generated Documentation Platform manages this case.
Yes. As customer using the Fiftyknots platform, you can clear so that I can self-serve answers without waiting for support.
Yes. As Fiftyknots distributor/channel partner, you can a self-serve library of sales resources so that I can sell and support the platform without constant hand-holding from the Fiftyknots team.
Yes. As developer shipping a new feature, you can documentation to be auto-generated from the spec and code I already wrote so that I don’t have to manually write docs as a separate step.
Yes. As customer with a common question, you can FAQs to exist and be searchable so that I get instant answers.
Yes. As customer on a specific platform version, you can docs that match my version so that I’m not confused by features I don’t have yet.
Yes. Pipeline shall parse feature specs (spec.md) and extract user-facing functionality, acceptance scenarios, edge cases, and entity descriptions.
Yes. Pipeline shall parse frontend components (apps/platform/frontend/src/pages/) to extract UI flow structure and page hierarchy.
Yes. Pipeline shall parse API route files to extract endpoint documentation for API docs.
Yes. Pipeline shall use AI (Sonnet 4.5 tier - STANDARD) to transform spec/technical language into end-user language following the Fiftyknots brand voice.
Yes. Pipeline shall validate generated content against brand voice guidelines (75+ brand score for shipping, 90+ for hero content).