Search blocks by description or jump to a page.
A voted community question card with author meta and tags above an answers list, an accepted staff answer pinned first, and a reply footer.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Community Q&A Thread is a question and its answers: a question card with an upvote control and a running count of 24, the author avatar, asked date, and view count, a short body describing the problem, and a row of topic tags. An answers header reads 2 answers with the note that the accepted answer shows first. The accepted answer card sits pinned at the top with an Accepted answer Badge, a Staff label on the author, the answer body with an inline API endpoint, and a closing line stating it was marked as accepted. A second community answer follows, and a footer invites a new answer with the reminder that replies are reviewed before they publish.
Tags are one typed const array; the vote counts, avatars, and badges are static values you replace with your own data. The Staff label and the marked as accepted line are the trust signals that tell a reader which answer the question owner actually endorsed.
Reach for this block on a product forum thread, a public knowledge base question, or an internal Q&A route, wired to your community API by question ID. Sort answers so the accepted one leads and keep the review note honest to your moderation flow.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the public product forum thread. Other configurations:
Tip: badge the accepted answer and name its author as Staff so a reader trusts one reply without reading the full thread.