AddThisFeature

FAQ Section

Add an expandable list of questions and answers to any page, in the order you choose.

simple Content & Publishing

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
  1. 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. 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. 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. 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. 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
  • 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
  • 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

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 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.