A community is the branded space members actually experience — logo, colours, rules, feed, challenges, and rewards. Orgs can have many communities; each one has its own theme and content.Documentation Index
Fetch the complete documentation index at: https://docs.nudj.cx/llms.txt
Use this file to discover all available pages before exploring further.
Creation flow
Basics
Name, URL slug, short description, and a banner image. Communities start in Draft by default — invisible to members until you flip them.
Status
Use the status dropdown on the community settings page to switch between Draft, Live, Archived, and Disabled.
Featured flag
Mark any community as Featured. Featured communities are surfaced first in multi-community experiences (embed launcher, landing page, org-level dashboard).
Rules & legal
Under Legal & Policies, add community rules using the rich-text editor. Choose whether members must agree to rules via a checkbox on join, and whether the rules panel is a permanent, always-visible toggle. See Legal & Policies.
Theme
Each community can override the org theme. The theme editor has a live preview iframe on the right so you can see your changes in real-time. See Community-Level Theming.
Community statuses
| Status | Visible to members? | In admin lists? |
|---|---|---|
| Draft | No | Yes |
| Live | Yes | Yes |
| Archived | No | Only on the Archived page |
| Disabled | No | Yes (greyed out) |
Rules and agreement
Communities can require members to accept rules before participating.- Rich-text rules
- Agreement checkboxes
- Permanent toggle
Use the TipTap rich-text editor (headings, lists, links, inline images) to write your rules. Saved to the community’s
legalConfig.Going live — checklist
Status dropdown set to Live (confirmation popup accepted).
Community has a name, banner, and short description.
At least one challenge is Live (or scheduled).
Theme has been previewed in the live iframe.
Rules, agreement, and landing page are configured if applicable.