# SupportPages > Help docs, screenshots and videos that update when you ship. SupportPages reads your code and keeps your help centre up to date - every merge, no backlog. Every page below is also served as raw markdown at the .md URL shown; drop the .md for the HTML version. ## Screenshots for documentation - [How to Update Every Screenshot After a Redesign](https://supportpages.io/guides/update-every-screenshot-after-a-redesign.md): A redesign invalidates every image in your help centre at once. Here is how to find them, fix the ones that matter, and avoid doing it all again next time. - [How to Take Screenshots for Documentation](https://supportpages.io/guides/take-screenshots-for-documentation.md): The settings and conventions to fix before you capture anything, so forty images end up looking like one set rather than forty separate decisions. - [How to Capture a Full-Page or Scrolling Screenshot](https://supportpages.io/guides/capture-a-full-page-or-scrolling-screenshot.md): Capturing a page taller than the screen, without the stitching seams, duplicated headers and cut-off text that most scrolling-capture tools produce. - [How to Redact Customer Data in a Screenshot](https://supportpages.io/guides/redact-customer-data-in-a-screenshot.md): Blurring is not redaction. What to remove, how to remove it so it cannot be recovered, and why the reliable answer is never to capture it in the first place. - [How to Screenshot a Dropdown or Hover State](https://supportpages.io/guides/screenshot-a-dropdown-or-hover-state.md): Menus close the moment you reach for the capture key. Three reliable ways to freeze a transient interface state long enough to photograph it. - [How to Keep Screenshots Consistent Across a Help Centre](https://supportpages.io/guides/keep-screenshots-consistent-across-a-help-centre.md): Readers notice inconsistency long before they notice imperfection. The five variables that cause it, and how to hold them steady across authors and years. - [What Size Should Documentation Screenshots Be?](https://supportpages.io/guides/what-size-should-documentation-screenshots-be.md): One capture width, one display width, and a decision about retina. The three numbers that determine whether your images look sharp or soft. - [How to Compress Screenshots Without Blurring the Text](https://supportpages.io/guides/compress-screenshots-without-blurring-text.md): JPEG is the wrong format for a screenshot. Why interface text smears under lossy compression, and what to use instead to get small files that stay sharp. ## Screen recording and product video - [How to Re-record a Walkthrough After a UI Change](https://supportpages.io/guides/re-record-a-walkthrough-after-a-ui-change.md): A triage rule for which videos a redesign actually breaks, and how to match the original capture conditions so the replacement does not look like a different product. - [How to Record a Product Walkthrough Video](https://supportpages.io/guides/record-a-product-walkthrough-video.md): One task, one rehearsed click path, narration recorded separately. The setup and sequence that produces a usable walkthrough without a studio or a seventh take. - [How to Script a Screencast Before You Record](https://supportpages.io/guides/script-a-screencast-before-you-record.md): A two-column script - what the screen does, what the voice says - that turns a fifteen-take recording session into a three-take one and survives being handed to someone else. - [How to Add Subtitles to a Product Video](https://supportpages.io/guides/add-subtitles-to-a-product-video.md): Auto-transcribe, then fix the product nouns by hand. How to produce a caption file that stays searchable, translatable and readable rather than burning text into the pixels. - [How to Narrate a Tutorial Without Recording Your Voice](https://supportpages.io/guides/narrate-a-tutorial-without-recording-your-voice.md): Three workable alternatives - on-screen text, synthesised speech, and deliberate silence - and the production details that stop each one sounding like a corner was cut. - [How to Record a Demo Without Exposing Customer Data](https://supportpages.io/guides/record-a-demo-without-exposing-customer-data.md): Video leaks differently from screenshots: it leaks for one frame, in a dropdown, in a notification banner. The setup that keeps real data out of the recording entirely. - [How to Choose Between a GIF and a Video for Documentation](https://supportpages.io/guides/gif-or-video-for-documentation.md): A duration test, a control test and a sound test that settle the question in under a minute - plus why the right answer to 'GIF' is usually a silent looping MP4. ## Writing help content - [How to Write a Help Centre Article](https://supportpages.io/guides/write-a-help-centre-article.md): One article, one task, one reader who arrived from search mid-problem. The structure that follows from that, the grammar of a numbered step, and the test that proves the article actually works. - [How to Write an FAQ Page](https://supportpages.io/guides/write-an-faq-page.md): An FAQ is a record of questions people actually asked, in the words they asked them. How to source them, answer them in one sentence, and keep the page from becoming a landfill. - [How to Document an Error Message](https://supportpages.io/guides/document-an-error-message.md): The page has to be found by someone pasting the error into a search box, so the exact string goes in the title. Then: what it means, what causes it, what to do, in that order. - [How to Write a Troubleshooting Guide](https://supportpages.io/guides/write-a-troubleshooting-guide.md): Start from the symptom the reader can see, order the checks by likelihood rather than by architecture, and make every check answerable yes or no. - [How to Write Release Notes](https://supportpages.io/guides/write-release-notes.md): Release notes are for the person deciding whether this release affects them. Lead with the effect, put required actions at the top, and never publish 'various improvements'. - [How to Write a Getting Started Guide](https://supportpages.io/guides/write-a-getting-started-guide.md): Pick the first moment the product does something useful, work backwards to the shortest path to it, and delete everything else. One outcome, one path, one next step. - [How to Document a Feature for Non-Technical Users](https://supportpages.io/guides/document-a-feature-for-non-technical-users.md): Translate a feature from what it does internally to what it does for the reader, without dropping the limitations that turn into support tickets three weeks later. ## Keeping documentation current - [How to Keep Documentation Up to Date](https://supportpages.io/guides/keep-documentation-up-to-date.md): Documentation decays fastest where the product moves fastest. Tie review to your release cadence rather than to a calendar reminder nobody honours. - [How to Tell Which Articles Are Out of Date](https://supportpages.io/guides/tell-which-articles-are-out-of-date.md): Six signals that identify stale articles without reading them, ranked by how much evidence each one actually gives you. - [How to Audit a Help Centre You Inherited](https://supportpages.io/guides/audit-a-help-centre-you-inherited.md): Someone left, and now a few hundred articles are yours. A one-week audit that ends with a decision against every page rather than a reading list. - [How to Delete a Help Article Without Breaking Links](https://supportpages.io/guides/delete-a-help-article-without-breaking-links.md): Deleting the article is the quick part. The work is finding everything that points at it and giving each of those readers somewhere to land. - [How to Version Documentation Across Releases](https://supportpages.io/guides/version-documentation-across-releases.md): Most products need release notes, not versioned documentation. Here is how to tell which you are, and how to build the version tree if you genuinely need one. ## Publishing and ranking a help centre - [How to Set Up Help on Your Own Domain](https://supportpages.io/guides/set-up-help-on-your-own-domain.md): Move your help centre off the vendor's URL and onto a hostname you own, with a valid certificate and no duplicate copy left indexed behind you. - [How to Choose Between help., docs. and support. Subdomains](https://supportpages.io/guides/help-vs-docs-vs-support-subdomain.md): Three words, one decision, and a rename later is a migration. What each subdomain signals to a reader, and how to pick the one that matches your content. - [Should Documentation Live on a Subdomain or a Subdirectory?](https://supportpages.io/guides/subdomain-or-subdirectory-for-docs-seo.md): The SEO argument is weaker than the operational one. Decide on what your infrastructure can actually serve, then handle the search consequences deliberately. - [How to Add a Sitemap for a Help Centre](https://supportpages.io/guides/add-a-sitemap-for-a-help-centre.md): A sitemap is a list of the URLs you want indexed, with honest dates. Both halves of that sentence are where help centre sitemaps usually go wrong. - [How to Get Help Articles to Rank](https://supportpages.io/guides/get-help-articles-to-rank.md): Help content ranks on intent match more than on effort. Take the phrasing from your own support inbox, give each question exactly one page, and structure the page for the reader who lands mid-way down it. - [How to Add Search to Your Documentation](https://supportpages.io/guides/add-search-to-your-documentation.md): Choosing an index is the small decision. Synonyms, result snippets and a log of what returned nothing are what make documentation search usable. ## Structuring a knowledge base - [How to Organise a Help Centre](https://supportpages.io/guides/organise-a-help-centre.md): Structure derived from the questions people ask, not from your product's navigation. Every article in exactly one place, and redirects for everything that moves. - [How Many Categories Should a Help Centre Have?](https://supportpages.io/guides/how-many-categories-should-a-help-centre-have.md): Five to nine top-level sections, each holding five to fifteen articles. Here is the arithmetic behind those numbers and what to do when a section breaks them. - [How to Name Help Centre Categories](https://supportpages.io/guides/name-help-centre-categories.md): A category name has about two seconds to tell a stranger whether their answer is inside. Test yours by asking someone to file ten articles into them. - [How to Tell When to Split One Article Into Two](https://supportpages.io/guides/when-to-split-one-article-into-two.md): Length is the worst reason to split an article. Count the questions it answers instead, then split without stranding the readers who already have the link. ## Measuring documentation - [How to Measure Whether Your Documentation Works](https://supportpages.io/guides/measure-whether-documentation-works.md): Documentation succeeds by absence, so every number you can collect is a proxy. Which proxies are worth having, and what each one over-claims. - [How to Track Ticket Deflection](https://supportpages.io/guides/track-ticket-deflection.md): Deflection counts tickets that were never filed, an event that leaves no trace. How to estimate it anyway, and how to report the estimate honestly. - [How to Use a Was This Helpful Widget](https://supportpages.io/guides/use-a-was-this-helpful-widget.md): The votes are close to worthless and the comments are the point. How to set the widget up so the free text arrives, and what the score cannot tell you. - [What to Do With Zero-Result Searches](https://supportpages.io/guides/what-to-do-with-zero-result-searches.md): An empty search result is the only place a reader states their intent in their own words. How to turn that log into a ranked list of work. ## Documentation for AI assistants - [What Is llms.txt?](https://supportpages.io/guides/what-is-llms-txt.md): A proposed convention for a curated, machine-readable index of your documentation. What the file contains, how to publish one, and what nobody can promise about it. - [How to Make Your Docs Readable by AI Assistants](https://supportpages.io/guides/make-docs-readable-by-ai-assistants.md): Assistants quote sections, not pages, from systems whose behaviour is unpublished. What to change in your documentation given that constraint, and what Google says you can skip. - [How to Check What ChatGPT Says About Your Product](https://supportpages.io/guides/check-what-chatgpt-says-about-your-product.md): A repeatable audit for the answers assistants give about you, designed around the fact that those answers are non-deterministic and unversioned. - [How to Add an AI Chatbot to Your Help Centre](https://supportpages.io/guides/add-an-ai-chatbot-to-your-help-centre.md): A retrieval bot inherits every gap and every stale page in your documentation, then states them confidently. What to fix first, and how to launch safely. - [Should You Let AI Write Your Documentation?](https://supportpages.io/guides/should-you-let-ai-write-your-documentation.md): Generation and verification are separate jobs, and only one of them got cheap. A decision procedure, and the review gate that has to exist either way. ## Moving your documentation - [How to Migrate from Notion to a Help Centre](https://supportpages.io/guides/migrate-from-notion-to-a-help-centre.md): Moving the customer-facing half of a Notion workspace into a help centre, without dragging the page IDs, dead internal links and team-only notes along with it. - [How to Migrate from Confluence to a Public Help Centre](https://supportpages.io/guides/migrate-from-confluence-to-a-public-help-centre.md): Lifting the customer-facing pages out of a Confluence space and publishing them, with the macros resolved, the attachments intact and the runbooks left behind. - [How to Move Google Docs Into a Help Centre](https://supportpages.io/guides/move-google-docs-into-a-help-centre.md): Turning a folder of shared documents into published articles, with the headings intact, the images extracted and the originals stopped from being edited. - [How to Export Articles From Intercom, Zendesk or Help Scout](https://supportpages.io/guides/export-articles-from-intercom-zendesk-help-scout.md): Getting a complete local copy of every published article - body, images, identifiers and structure - out of a hosted help desk, in a form you can import elsewhere. - [How to Move Documentation Out of Your README](https://supportpages.io/guides/move-documentation-out-of-your-readme.md): Splitting a README that has grown into a manual, so contributors and users each get the page they came for, without breaking the links people have bookmarked. ## Documentation as a team process - [Who Should Own Documentation?](https://supportpages.io/guides/who-should-own-documentation.md): Ownership is four separate jobs bundled under one word. Splitting them, and naming a person for each, is what stops documentation belonging to nobody. - [How to Add Docs to Your Definition of Done](https://supportpages.io/guides/add-docs-to-your-definition-of-done.md): Writing a documentation rule teams can actually satisfy: a checkable line, a list of what counts as user-facing, and a legitimate way to answer no. - [How to Review Documentation in a Pull Request](https://supportpages.io/guides/review-documentation-in-a-pull-request.md): A docs review that catches wrong instructions rather than comma placement, done in the same pull request as the change and finished in minutes. - [How to Onboard a Support Hire With Your Docs](https://supportpages.io/guides/onboard-a-support-hire-with-your-docs.md): Using a new starter's first fortnight as the most honest documentation audit you will ever get, while getting them answering tickets faster than a slide deck would. ## Blog - [What We Got Wrong About Onboarding](https://supportpages.io/blog/what-we-got-wrong-about-onboarding.md): We built AI-generated onboarding questions. The answers arrived downstream with the questions deleted. - [Your Monorepo Is Not the Problem](https://supportpages.io/blog/your-monorepo-is-not-the-problem.md): One help centre, many repositories. How to structure documentation when the product does not map to a single codebase. - [Video Walkthroughs Without the Screen Recorder](https://supportpages.io/blog/video-walkthroughs-without-a-screen-recorder.md): Ninety seconds of narrated video, generated from your codebase, re-recorded whenever the interface moves. - [How Much Is a Support Ticket Actually Costing You?](https://supportpages.io/blog/what-a-support-ticket-costs.md): Run the numbers on deflection before you run them on headcount. - [Write the Error Message Down Exactly](https://supportpages.io/blog/write-the-error-message-down-exactly.md): Users do not describe their problem. They paste the red text. Title the article with it. - [Inside the Review Inbox](https://supportpages.io/blog/inside-the-review-inbox.md): AI writes the draft. You still decide what ships. Here is the workflow that keeps both true. - [The Procurement Question You Are Failing](https://supportpages.io/blog/the-procurement-question.md): Somewhere in every enterprise evaluation is a line asking where your documentation is. - [The Ten Articles Every SaaS Product Needs](https://supportpages.io/blog/ten-articles-every-saas-needs.md): Different products, same skeleton. The coverage set that answers most inbound before it arrives. - [Writing Docs for Readers Who Are Machines](https://supportpages.io/blog/writing-docs-for-machines.md): Half your documentation traffic may already be a language model answering someone's question about your product. - [Screenshots Rot. Ours Regenerate.](https://supportpages.io/blog/screenshots-rot-ours-regenerate.md): A redesign used to invalidate every image in your help centre. Now it just triggers a re-render. - [Reading the Room: What Unanswered Questions Reveal](https://supportpages.io/blog/what-unanswered-questions-reveal.md): Every question your help centre could not answer is a documentation ticket that wrote itself. - [One Model Does Not Fit Every Task](https://supportpages.io/blog/one-model-doesnt-fit-every-task.md): Detecting a project structure and writing a polished article are different jobs. Now you can pick a different engine for each. - [The Users Who Never File a Ticket](https://supportpages.io/blog/users-who-never-file-a-ticket.md): Your support queue is a filtered sample. The users who could not work it out mostly just left. - [Six Months of Building in Public](https://supportpages.io/blog/six-months-of-building-in-public.md): What shipped, what flopped, and what we would do differently - the first half of the roadmap, unedited. - [Why We Run AI in a Container, Not Behind an API Call](https://supportpages.io/blog/why-we-run-ai-in-a-container.md): Prompting a model about your code gives you plausible docs. Letting an agent read the repository gives you correct ones. - [What to Write First When You Have No Docs at All](https://supportpages.io/blog/what-to-write-first.md): The blank page is the real blocker. Here is the running order we recommend for a help centre starting from zero. - [The Documentation Debt Nobody Gets Paged For](https://supportpages.io/blog/documentation-debt-nobody-gets-paged-for.md): Code debt has alerts, dashboards and a backlog. Docs debt has none of that - it just accrues until a customer finds it. - [From First Visit to Signup: Funnel Analytics for Your Help Centre](https://supportpages.io/blog/from-first-visit-to-signup-funnel-analytics.md): Docs aren't just deflection - they sell. SupportPages analytics now shows the full path visitors take, with drill-downs at every step. - [Internal Docs, Magic Links, and Who Sees What](https://supportpages.io/blog/internal-docs-magic-links-and-who-sees-what.md): Team invites, domain-restricted help centres with magic-link access, and precise visibility controls - SupportPages grew up for teams this week. - [Video Walkthroughs: Watch It, Don't Just Read It](https://supportpages.io/blog/video-walkthroughs-watch-it-dont-just-read-it.md): SupportPages now generates narrated video walkthroughs of your features - from the same source as everything else: your code. - [Your Help Centre Can Now Answer Back, Right Inside Your App](https://supportpages.io/blog/your-help-centre-can-now-answer-back.md): The new embeddable chat widget puts AI answers from your docs inside your product - where the questions actually happen. - [SupportPages for Open Source: Public Repo Support](https://supportpages.io/blog/supportpages-for-open-source-public-repos.md): You can now point SupportPages at any public GitHub repository - no app install, no write access, no friction. Open-source projects deserve real help centres too. - [Your Help Centre Is Now AI-Agent Ready](https://supportpages.io/blog/your-help-centre-is-now-ai-agent-ready.md): Your next customer might not read your docs - their AI assistant will. SupportPages help centres now speak llms.txt. - [Bitbucket Support Is Live](https://supportpages.io/blog/bitbucket-support-is-live.md): SupportPages now connects to Bitbucket as well as GitHub. Your choice of repo host shouldn't decide whether your docs stay current. - [Set the Tone: Your Docs, Your Voice](https://supportpages.io/blog/set-the-tone-writing-style-controls.md): AI-generated docs shouldn't sound AI-generated. SupportPages now matches your writing style across every article it drafts. - [Help Centre Analytics: Know What Your Users Actually Read](https://supportpages.io/blog/help-centre-analytics-know-what-your-users-read.md): Support tickets tell you where your docs failed. Analytics tell you where they almost worked. SupportPages now ships with both ends of that story. - [Introducing SupportPages. AI Documentation from Your Codebase.](https://supportpages.io/blog/introducing-supportpages-ai-documentation-from-code.md): Help docs that write themselves when you ship code. No more outdated documentation. ## Alternatives and comparisons - [7 Best Document360 Alternatives for Customer Help Centres](https://supportpages.io/alternatives/document360.md): Document360 is a broad knowledge-base platform with strong organization, governance and AI features. The alternatives serve different teams: support suites, developer-docs platforms, open-source builders and SaaS products that want documentation generated from code. - [7 Best Docusaurus Alternatives Without the Maintenance Overhead](https://supportpages.io/alternatives/docusaurus.md): Docusaurus offers open-source control over a React documentation site. Alternatives trade some of that control for managed publishing, collaborative editing, API tooling, support integration or documentation generated from product code. - [7 Best GitBook Alternatives for Technical and Product Docs](https://supportpages.io/alternatives/gitbook.md): GitBook combines visual collaboration with Git-aware documentation workflows. Alternatives become more compelling when you need automatic content generation, a dedicated support suite, API-first experiences or complete open-source control. - [7 Best Intercom Help Center Alternatives for SaaS Teams](https://supportpages.io/alternatives/intercom-help-center.md): Intercom Help Center is most powerful as part of Intercom's support ecosystem. These alternatives cover teams that want a standalone knowledge base, technical docs, API references, open-source control or automated end-user documentation. - [7 Best Mintlify Alternatives for SaaS Documentation](https://supportpages.io/alternatives/mintlify.md): Mintlify is a strong developer-documentation platform, but the best alternative depends on whether you need collaborative authoring, API tooling, a support-suite knowledge base, open-source control, or customer help generated from your product code. - [7 Best ReadMe Alternatives for Software Documentation](https://supportpages.io/alternatives/readme.md): ReadMe is strongest when the API itself is the product experience. The right alternative depends on whether you need broader developer docs, customer-facing product help, collaborative knowledge management or an open-source site. - [7 Best Zendesk Knowledge Alternatives for Customer Documentation](https://supportpages.io/alternatives/zendesk-knowledge.md): Zendesk Knowledge is designed for established service operations. Alternatives range from Intercom's integrated support knowledge to standalone documentation platforms and code-connected help-centre automation. - [Document360 vs Intercom Help Center: Knowledge Platform or Support Integration?](https://supportpages.io/compare/document360-vs-intercom.md): Choose Document360 when knowledge needs its own platform, governance and public or private destinations. Choose Intercom Help Center when articles should work across an Intercom-led support experience. - [Document360 vs Zendesk Knowledge: Standalone Knowledge Base or Support Suite?](https://supportpages.io/compare/document360-vs-zendesk.md): Choose Document360 when documentation and knowledge management should stand on their own. Choose Zendesk Knowledge when the corpus must operate inside established Zendesk service and agent workflows. - [GitBook vs Document360: Collaborative Docs or Knowledge Governance?](https://supportpages.io/compare/gitbook-vs-document360.md): Choose GitBook for a collaborative technical-documentation workflow spanning browser editing and Git. Choose Document360 for a governed knowledge-base programme covering public, private and internal content. - [Intercom Help Center vs Zendesk Knowledge: Which Fits Your Support Stack?](https://supportpages.io/compare/intercom-vs-zendesk.md): Choose Intercom Help Center when knowledge should power Messenger, Inbox and Fin in an Intercom-led support experience. Choose Zendesk Knowledge for established service organizations centered on Zendesk workflows and governance. - [Mintlify vs Docusaurus: Managed Platform or Open-Source Control?](https://supportpages.io/compare/mintlify-vs-docusaurus.md): Choose Mintlify for a managed developer-documentation platform with API and AI-native features. Choose Docusaurus when open-source ownership and complete React control justify operating the site yourself. - [Mintlify vs GitBook: Which Documentation Platform Should You Choose?](https://supportpages.io/compare/mintlify-vs-gitbook.md): Choose Mintlify when developer experience, API documentation and agent-native delivery lead the decision. Choose GitBook when a mixed team needs a strong visual editor and collaborative knowledge workflow. - [Mintlify vs ReadMe: Which Is Better for Developer Documentation?](https://supportpages.io/compare/mintlify-vs-readme.md): Choose ReadMe when interactive API adoption and developer dashboards are the centre of the experience. Choose Mintlify for a broader developer-documentation platform spanning references, guides, agent delivery and customizable content. ## Pages These pages are HTML only. - [Pricing](https://supportpages.io/pricing): SupportPages pricing: Free, Solo from $30/month and Pro from $99/month. Flat price, no credits. Every plan includes a hosted help centre and full branding. - [How it works](https://supportpages.io/how-it-works): From code change to published help article in minutes. Analysed in our cloud sandbox or on your own infrastructure. Every merge becomes docs, no content debt. - [What we do with your code](https://supportpages.io/your-code): How supportpages.io handles your code: read-only, never stored, analysed in a throwaway sandbox then deleted - or written by your own local coding agent. - [WTFM: Write the F***ing Manual](https://supportpages.io/wtfm): WTFM is a free, open-source plugin for Claude Code and Codex that writes user guides with screenshots drawn from your UI code. No running app, no account. - [Help centres for open source projects](https://supportpages.io/open-source/help-centres): Illustrated help centres SupportPages.io generated from the public code of open source projects. Maintainers can claim theirs free, or have it removed. - [Documentation software alternatives and comparisons](https://supportpages.io/alternatives): Independent, source-backed comparisons of leading documentation, knowledge-base and help-centre platforms for SaaS teams. - [About Simon Moxon](https://supportpages.io/about): Simon Moxon has built SaaS companies since 2009. He writes the SupportPages blog and guides, and builds help docs that regenerate when the code changes.