Private Pro category · 10 compositions
Faq
Question discovery and disclosure layouts for product and policy topics. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 10 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Installation questions
Billing placeholders
Security questions
Accessibility questions
Team access questions
Design kit questions
Update policy placeholders
Support questions
Data handling questions
Category contract
- Purpose
- Question discovery and disclosure layouts for product and policy topics.
- Declared dependencies
- gummy-accordion, gummy-typography
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Faq blocks
An FAQ composition should resolve recurring, consequential questions rather than restate marketing copy. Group questions by customer task, write standalone headings in the visitor’s language, and place contractual topics near the canonical policy that governs them.
Keep answers in a maintained content source and link to pricing, licence, refund, privacy, or technical documentation when detail belongs there. Disclosure controls must expose expanded state correctly, work by keyboard, and leave the answer readable when scripting is unavailable.
Check answers with their subject owners and remove stale promises instead of quietly qualifying them. Test long answers, deep links, searching, multiple expanded items, translated labels, and print output. FAQ structured data, if added later, must exactly match visible public content.
For every answer, record a canonical policy or product source, subject owner, review date, and conditions that would make it obsolete. Provide stable anchors for frequently shared questions. If an answer changes a customer’s contractual understanding, update the governing document first and make the FAQ summarize and link to it rather than becoming a competing source.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.