The FAQ component renders a collapsible question + answer. Multiple FAQ blocks stacked together form an accordion.
Example#
Do you support custom domains?
Yes — on Pro plans and above. Add your domain in Project Settings → Domains, then point a CNAME at the value Dokly gives you. HTTPS is provisioned automatically within a few minutes.
Does Dokly support team members?
Multi-member teams are on the Scale plan ($99/mo, 5 seats). Free, Starter, and Pro are single-seat.
Insert#
Use the slash menu: /faq. Each FAQ block holds one question and one answer. Stack multiple FAQ blocks back-to-back to build an accordion.
Settings#
| Setting | Description |
|---|---|
| Question | The question. Shown as the clickable header. |
| Answer | The answer body. Anything goes — prose, code, lists. |
| Default open | Whether the answer is expanded on first load. Off by default. |
When to use FAQ vs prose#
FAQ blocks are right when:
- The reader is scanning for one specific answer (FAQ pages).
- The page would be too long if every answer was inline.
- The information is genuinely optional context (gotchas, caveats).
FAQ blocks are wrong when:
- The reader needs to read top to bottom (a tutorial).
- You're hiding important information that everyone needs to see.
Don't use FAQ to hide bad UX. If your readers all hit the same gotcha, the gotcha needs to be a callout in the main flow, not a collapsed FAQ.
SEO#
FAQ blocks render with proper <details> / <summary> semantics. Search engines and AI crawlers can read the answers without expanding the block. If you mark up your FAQ page as FAQPage schema, the FAQ blocks contribute to the structured data automatically — see SEO.