Forum-shaped products combine discovery, participation, identity, governance,
moderation, and durable knowledge retrieval. Chirp UI can compose these pages
from existing primitives before adding a publicforum_*namespace.
Use the canonical repository guide for the full recipe set:
docs/FORUM-SITE-PATTERNS.md.
Use This When
- A community home needs rules, categories, visibility, stats, and posting state.
- A topic list needs filters, replies, labels, saved views, or activity state.
- A thread page needs root post, replies, local navigation, composer, and secondary management controls.
- Q&A, moderation, and inbox surfaces need dense but separated operating state.
Blessed Surfaces
app_shell,site_shell,route_tabs,nav_tree,breadcrumbs, andsplit_layout.detail_header,thread_reader_layout,post_card,rendered_content,comment_thread, andcomment.resource_index,resource_card,facet_chip,badge, andcounter_badge.action_bar,share_menu,reaction_pill,message_reactions, andbtn.callout,alert,confirm_dialog,form,action_strip, andtoastfor governance and moderation.
Checks
- Rules, visibility, and posting permissions appear before composers.
- Locked, archived, removed, or moderator-only states are visible before reply forms.
- Reply and moderation actions are keyboard reachable and labeled.
- Long threads provide anchors, sort controls, or continuation markers.
- Sanitized body HTML remains app-owned; recipes do not add new unsafe escape hatches.