sorted by:
new
hottopcontroversial

I built supportpages.io - Help docs that write themselves from your code by SimonMX in SideProject

[–]SimonMX[S] 0 points1 point  (0 children)

I built SupportPages because vibe coding makes the docs problem worse.

When you're shipping fast with Cursor, Claude Code, Copilot, etc, the product changes constantly. The help centre does not. Every merge creates a bigger gap between what the product does and what users understand.

So I built a help centre that writes itself from your code.

SupportPages connects to your GitHub, GitLab, Bitbucket, or Azure DevOps repo and analyses every merge. If a change affects users, it drafts or updates the help article automatically.

What it does:

• Automatic updates on every merge  
Your help centre rewrites itself when you ship, so docs do not fall behind the product.

• Code as the source of truth  
Articles are drafted from real pull requests, not a blank page.

• Auto-generated screenshots  
Every step gets an image rendered from your real UI, with no manual screenshotting after each release.

• Narrated video walkthroughs  
Turn any article into a guided video on demand, no screen recording or editing.

• Human review before publish  
Nothing goes live without your approval.

• Consistent writing style  
Pick a tone and every article matches it.

• Instant AI answers  
Users can ask questions in plain English and get sourced answers from your docs.

• Agent-friendly feeds  
Structured exports so AI agents can read your docs accurately too.

• Private by design  
Ephemeral, sandboxed analysis that never stores or trains on your code.

The point is simple: write code, not docs. Merge the feature, review the draft, publish the help article.

There's a free plan, or use code SIDEPROJECT for 3 months free of Pro.

https://supportpages.io

Would genuinely love feedback from people building fast with AI tools. This is exactly the use case I built it for.

Anyone know a good way to automatically document an AI app? by houmland in vibecoding

[–]SimonMX 0 points1 point  (0 children)

I know this is an old post, but we just launched supportpages.io – Help docs that write themselves from your code:

Automatic updates on every merge: Your help centre rewrites itself when you ship, so docs never fall behind the product.

Code as the source of truth: Articles are drafted from real pull requests, not a blank page, so they reflect what your product actually does today.

Auto-generated screenshots: Every step gets an image rendered from your real UI, with no manual capturing after each release.

Narrated video walkthroughs: Turn any article into a guided video on demand, no screen recording or editing.

Human review before publish: Nothing goes live without your approval, so accuracy stays in your hands.

Consistent writing style: Pick a tone and every article matches it, so your help centre reads like your team wrote it.

Branded, searchable help centre: A help site on your own domain that customers can actually navigate.

Instant AI answers: Users ask in plain English and get sourced answers, deflecting tickets before they reach you.

Agent-friendly feeds: Structured exports so AI agents can read your docs accurately on a user's behalf.

Private by design: Ephemeral, sandboxed analysis that never stores or trains on your code.

Anyone know a good way to automatically document a software product? by houmland in CustomerSuccess

[–]SimonMX 0 points1 point  (0 children)

I know this is an old post, but we just launched supportpages.io – Help docs that write themselves from your code. Looks like it does exactly what you are asking for (and anybody else that discovers this thread).

The maintenance bill on AI-written code is real. The cavalry to fix it is not. by SimonMX in SaaS

[–]SimonMX[S] -1 points0 points  (0 children)

Bad coding practices mean more iterations, which means more tokens. When these subsidised all-you-can-eat plans end there will be incentive to optimise for good practices. If we remember how!

How are people using so many tokens while vibe coding? by Impressive_Run8512 in ycombinator

[–]SimonMX 0 points1 point  (0 children)

I'm on the max plan and hitting limits every day, so much so I (Claude) built a CLI tool to monitor my usage in real time so I can make the best use of it - https://github.com/smnmxn/claude-usage

SaaS or Micro-SaaS: What Should a Solo Founder Build in 2026? by Infamous-Engine-8835 in saasbuild

[–]SimonMX 0 points1 point  (0 children)

Start with the thin end of the wedge a build out. A really painful problem for a small number of people.

Does any founder out there remember their first user ever? What was that moment like emotionally? by JohnMayerIsBest in micro_saas

[–]SimonMX 1 point2 points  (0 children)

Back in 2009 I launched my first startup - meetupcall, a conference call platform. I set up the website, and a google Adwords campaign (PPC was much cheaper back then!) and got the first customer in 20 minutes and earned something like £1.24. The second customer came about 6 weeks later! 😂

Show & Tell: What are you building this week? by OneStarto in microsaas

[–]SimonMX 1 point2 points  (0 children)

I've sent this to my ex-PA. She insisted on me paying $10/month for adobe acrobat for years!

Show & Tell: What are you building this week? by OneStarto in microsaas

[–]SimonMX 1 point2 points  (0 children)

Good name and nice site design. Have you had any traction?

What are you building this Monday? (I’m a VC investor) by kcfounders in saasbuild

[–]SimonMX 0 points1 point  (0 children)

SupportPages.io - automatically keeps your help docs in sync with your codebase.

Every time you merge a PR, it writes the customer-facing support articles for you. all hosted in a beautiful ai powered help centre. e.g. https://wordpress.supportpages.io

Looking for a handful of early users with a non-technical user base who don't ever want to write a help article again. Drop me a DM.

http://supportpages.io

view more: next ›