Skip to main content

​
Auto-Generated Documentation Platform

​
Overview

Fiftyknots ships features weekly. Your documentation stays current without you lifting a finger. The platform automatically generates end-user manuals, distributor sales resources, and FAQs from specs and code in the monorepo - so you always have accurate, on-brand content when you need it.

​
Step-by-Step Guide

​
For Founders Using Documentation

  1. Access the docs site - Visit docs.fiftyknots.com and use the search bar or sidebar navigation to find what you need.
  2. Search or browse - Enter keywords like “briefing wizard” in the search bar, or navigate by category (Getting Started, Project Vaults, Expert Matchmaking, etc.) in the sidebar.
  3. Read the guide - Each feature manual includes an overview, step-by-step instructions, common questions, troubleshooting tips, and links to related features.
  4. Switch versions if needed - Use the version selector to view docs matching your current platform version. The default shows your deployed version.
  5. Check the FAQ section - If you have a quick question, scan the auto-generated FAQs extracted from common scenarios and support patterns.

​
For Distributors Using Sales Resources

  1. Log into the Coda portal - Access your distributor workspace with your registered credentials. Resources automatically filter to your region and tier.
  2. Browse battle cards - Navigate to Feature Battle Cards to see value propositions, target personas, competitive positioning, and objection handling for each feature.
  3. Use the ROI calculator - Open the interactive ROI calculator, input your prospect’s parameters, and generate a branded output to share with potential customers.
  4. Check What’s New - Review the auto-generated changelog to see recent features and updates you can pitch to prospects.
  5. Download training materials - Access onboarding guides and training resources to bring new team members up to speed.

​
For Developers Shipping Features

  1. Write your spec - Complete your feature with a spec in Docs/specs/NNN-feature-name/spec.md following the standard template.
  2. Trigger the pipeline - Run the doc generation command manually, or let it trigger automatically when you merge to main via GitHub Actions.
  3. Review generated content - Check the “pending review” state for your feature’s first publish. The pipeline flags specs that are too thin for quality docs.
  4. Approve or refine - Approve the generated docs if they meet brand standards, or add detail to your spec and regenerate if the content needs enrichment.
  5. Verify publication - Confirm that both the end-user docs site and distributor Coda workspace show your new content within 1 hour.

​
Common Questions

Q: How quickly do docs update after a feature ships?
A: Within 1 hour. The pipeline runs automatically on merge to main, transforming your spec and code into end-user and distributor content that publishes immediately. Q: What if my feature spec doesn’t have enough detail for good docs?
A: The pipeline flags thin specs rather than generating low-quality content. Add acceptance scenarios, edge cases, and entity descriptions to your spec, then regenerate. Q: Can I see docs for features that haven’t shipped yet?
A: No. The docs site defaults to your deployed platform version. You can use the version selector to view upcoming features once they’re in a pre-release version, but unreleased content stays internal. Q: How do I know the generated content matches our brand voice?
A: The pipeline validates all generated content against brand voice guidelines. Content needs a 75+ brand score to ship, and 90+ for hero content. The system automatically transforms spec language into Founder’s Edge voice. Q: What happens if a feature gets deprecated?
A: The pipeline detects deprecated features and automatically archives or removes the corresponding docs from the public site. You won’t see outdated content confusing users.

​
Troubleshooting

Issue: I can’t find documentation for a feature I know exists
Solution: Check the version selector - you might be viewing docs for an older platform version. Switch to your current version or search across all versions. If the feature shipped within the last hour, wait for the pipeline to complete. Issue: The generated docs contain internal information that shouldn’t be public
Solution: This shouldn’t happen - the pipeline automatically filters internal-only content (pricing margins, competitive intelligence, architecture decisions). If you spot sensitive content, flag it immediately. The classification layer should catch this during the “pending review” state before first publish. Issue: Distributor resources show features I don’t have access to
Solution: The Coda portal uses row-level access control to filter resources by your tier and region. Contact your distributor admin to verify your access settings. Only resources matching your permissions should appear. Issue: Generated content quality is poor or doesn’t make sense
Solution: The source spec likely lacks sufficient detail. Review the acceptance scenarios, edge cases, and functional requirements in the original spec. Add missing context, then manually trigger a regeneration of the docs. The pipeline can only work with the quality of input it receives. SupaSherpa - Your AI assistant can answer documentation questions in real-time and surface relevant docs based on your current context. If you’re stuck, ask SupaSherpa instead of searching manually. Data Room - The auto-generated documentation pipeline can export content directly to your project Data Room for investor review. Use this to keep stakeholders informed without manual document assembly. Journey Dashboard - Track which documentation resources users access most frequently. This data feeds back into the pipeline to improve FAQ generation and identify gaps in coverage.