FAQ Section
Add an expandable list of questions and answers to any page, in the order you choose.
What it adds
A reorderable set of question and answer pairs rendered as an accessible expand-collapse list on any page.
What your agent is told to do
5
What your agent is told to do
5-
1
Build it on real disclosure semantics with a button that toggles its own panel, so keyboard and screen reader users get the behaviour for free.
-
2
Give every question a stable anchor derived from its text and keep it after edits, so a support reply can link straight to one answer.
-
3
Allow answers to contain formatted text, lists, and links, and reuse the app's existing content editor and its sanitisation rules rather than accepting raw markup.
-
4
If the app already has an AI FAQ generator or a help centre, let this section draw from those existing question records instead of holding a separate copy of the same answers.
-
5
Do not force only-one-open behaviour by default. Allowing several open at once is what people expect when they are comparing answers, and it avoids the collapse-and-jump problem entirely.
Edge cases it handles
8
Edge cases it handles
8- A link to a single question must open that item and scroll it into view on load, including when the link is followed while the page is already open.
- If only-one-open behaviour is used, collapsing a tall answer above the one being opened yanks the page. Anchor the scroll position to the item the user clicked so it stays where they are looking.
- Rich answers containing lists and links must not be reachable by keyboard or read by screen readers while the panel is collapsed. Hide the region properly rather than clipping it with height.
- In-page search, including the browser's own find, cannot see text inside closed items. Expand any item containing a match when the page has a search control, and warn authors that browser find will miss collapsed content.
- Printing must render every answer expanded. A printed page of unanswered questions is useless.
- The expand and collapse transition must be skipped when reduced motion is requested.
- An empty answer or a question with no answer yet must not render as an item that opens onto nothing.
- Reordering questions must not change their anchors, or every previously shared link points at a different answer.
Definition of done
9
Definition of done
9- Questions expand and collapse by keyboard and are announced with their expanded state.
- Each question has a stable anchor that survives edits and reordering.
- A deep link opens the target question and scrolls it into view.
- Collapsed answers are hidden from keyboard navigation and assistive technology.
- Print output shows every answer expanded.
- Answers support formatted text and links through the app's existing sanitised editor.
- Transitions respect reduced-motion preferences.
- 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
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
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
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.