This demo is built from Markdown and organization-compatible Liquid components. The source is reviewable, versioned, deterministic, and separated from the target environment’s record IDs.
A small component vocabulary
row, col, features, feature, card, details, slides, and embeds like netlify turn long-form Markdown into a designed information hierarchy.
org_posts, feed, org_team, user, comment, event, and podcast bring live Forem records into the page. agent_session can add a curated, redacted work trace when showing the reasoning is useful.
cta, offer, org_lead_form, and org_lead_gate make the next action explicit while preserving a clear disclosure of what the visitor shares.
Example source
{% features %}
{% feature title="Useful by default" icon="heart" %}
Start with the reader’s next task, then earn every additional component.
{% endfeature %}
{% endfeatures %}
Forem protects Liquid syntax inside fenced code, so this example remains readable instead of compiling the component when the page is saved.
The maintenance loop
1. Collect
Pull recurring questions from comments, events, search, and support. Keep source links so every proposed change can be checked.
Safe promotion checklist
Does the organization slug and name match exactly?
The uploader refuses to continue unless both match the manifest. This prevents a valid manifest from being applied to the wrong organization.
Do all page tabs already exist on the target?
They must. The API can update organization pages but cannot safely create and attach new tabs, so missing pages are a hard stop.
Have environment-specific Liquid IDs been replaced?
Events, lead forms, comments, and agent sessions use target-specific IDs or slugs. Local values are fixture data and must never be copied blindly to DEV.
Is there a fresh backup and an explicit apply gate?
Apply requires an API key, an unused backup path, and an explicit production flag. Planning is read-only; validation does not make network requests.
Reference implementation
Forem is open source. Browse the implementation on GitHub, or use the maintained developer documentation for the supported integration surface.
