Documentation Site
Publish structured docs with a nested sidebar, linkable headings, and selectable versions.
What it adds
A documentation site with a nested navigation tree, per-page heading anchors, and versioned content.
What your agent is told to do
5
What your agent is told to do
5-
1
Define the sidebar tree explicitly as ordered content, not by inferring it from file names or page titles. An inferred tree silently drops pages when someone renames one.
-
2
Generate an anchor for every heading and derive it from the heading text, but store the anchor once it has been published so renaming the heading does not break links people have already shared.
-
3
Reuse the app's existing table of contents behaviour for the in-page heading list rather than writing a second scroll-spy, and reuse the existing search rather than adding a docs-only one.
-
4
Make versioning a property of the whole documentation set with one current version and a small number of archived ones. Do not build per-page version branching until there is a real need for it.
-
5
Do not paste examples in as screenshots. Code and configuration must be selectable text so a reader can copy it, and must carry a language label for syntax rendering.
Edge cases it handles
8
Edge cases it handles
8- A page that exists in the content store but sits nowhere in the sidebar tree is unreachable by browsing. Surface those orphans to authors rather than letting them go quietly missing.
- Renaming a heading changes its anchor and silently breaks every deep link to that section. Keep the previous anchor as an alias on the same heading.
- A reader on an older version who follows a link to a page that only exists in the latest version must be told the page is not in their version and offered the latest, not dropped on a not-found page.
- Long code blocks must scroll horizontally inside their own container. The page body itself must never scroll sideways on a phone.
- Arriving from a deep link must open the sidebar to the section containing that page and scroll it into view, otherwise the reader has no idea where they are in the tree.
- Switching versions from a page should land on the same page in the target version when it exists, and on that version's index when it does not.
- Search results must be scoped to the selected version, or readers will keep landing on documentation for software they are not running.
- The archived versions must carry a visible notice that they are not current, with a link to the latest.
Definition of done
9
Definition of done
9- The sidebar renders a nested tree with the current page and its ancestors expanded.
- Every heading has a copyable anchor link, and previously published anchors keep working after a rename.
- Version switching preserves the current page when it exists in the target version.
- Code blocks scroll within their container and the page never scrolls horizontally at 320px.
- Search results are limited to the selected version.
- Pages absent from the navigation tree are reported to authors.
- Archived versions display a notice pointing to the current version.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Newsletter Archive
Newsletter Archive
Turn sent email issues into browsable web pages that new readers can find and read.
What it does
A public archive of past newsletter issues, each with its own permanent page and a subscribe path.
How it works
- 1 Store the sent version of each issue rather than regenerating it. An archive built by re-rendering a template will drift the moment the template changes, and old issues will stop matching what subscribers actually received.
- 2 Convert the email markup to web markup on the way in: strip the table scaffolding, the fixed pixel widths, and the inline styles that only exist to survive an email client, and render the result in the app's normal article styles.
- 3 Reuse the app's existing publishing states rather than adding a second one. An issue should move from sent to archived through the same Draft and Publish States machinery the rest of the content uses.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/newsletter-archive
Blog
Blog
Publish articles from inside the app to public pages with authors and categories.
What it does
A blog with authored posts, categories, scheduling, and public article and index pages.
How it works
- 1 Scope this honestly. The minimum coherent version is a post with a title, body, author, category, publish state, and a public page at a stable URL, plus an index and a feed. Defer multi-language content, per-post custom layouts, and a general page builder rather than half-building them.
- 2 Do not build a new editor. Extend the app's existing Rich Text Editor or Markdown Editor with whatever a post needs, and inherit its autosave, unsaved-change warning, and undo instead of reinventing them.
- 3 Reuse the app's existing Draft and Publish States and Scheduled Publishing rather than adding a second publish workflow for posts. Reuse SEO Setup for titles, descriptions, and social previews.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/blog
Help Center
Help Center
Give customers a searchable help site they can read before they open a support ticket.
What it does
A public help site of articles grouped into collections, with search, browse, and a contact fallback.
How it works
- 1 Treat the article as the single source of help content. If the app already has Contextual Help, Knowledge Base Chat, or an AI knowledge base drafting flow, point them at these same records rather than keeping a second copy of the answers that will drift.
- 2 Index articles into the app's existing search rather than standing up a separate search box with its own ranking. Extend Global Search and reuse the existing match highlighting so a result looks the same wherever it appears.
- 3 Give every article a stable slug and every collection an ordered list of articles, and show breadcrumbs from the collection down to the article so a visitor who landed from search knows where they are.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/help-center
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.