Give your community a place to return to.

Plan a community website and mobile companion with profiles, posts, membership visibility, moderation workflows and configured app sign-in.

Review the prepared brief in Studio. A build starts when you send it.

Make membership boundaries readable

State which spaces a visitor can read, what a signed-in member can contribute and which profile fields are public. Keep a member's private contact information separate from the directory. Use one state owner for filters and selected groups so navigation and counts agree. Provide real empty and loading states while the community grows.

Build a moderation path before launch

Posts need reporting, review and removal rules that fit the community. Specify who has authority to perform those actions and avoid implying that a moderator badge itself enforces access. Plan account recovery, blocked content, attachment limits and how a removed member's access changes. Test a second user against private groups and profile data.

Give each screen its own job.

These are proposed interfaces for your brief. Build and verify the core workflow before adding connected companions.

Plan the records and their owners.

Suggested collections for this editable blueprint. Opening this page creates no database records. The plan must declare supported field types, relationships and access rules before building.

CollectionSuggested fieldsAccess to decide
profilesowner, display_name, public_bioSelf-edited profile with only approved fields in the public directory.
postsauthor, group_id, body, visibility, statusPosting and reading scopes match the group's membership rules.
reportsreporter, post_id, reason, statePrivate reporting and explicitly authorized moderation review.

Verify the outcome, then expand.

From this brief to your first version.

  1. Review the proposed workflow

    Start with this editable blueprint brief. Confirm the primary action, target platform, actual business information and declared collection permissions before approving a plan.

  2. Build and check the result

    Review the isolated preview and execute the checks listed on this page. Begin with Public introduction, member directory, groups and discussion views. Resolve missing service setup and save verified progress before expanding the scope.

  3. Connect or export when ready

    Use App connections to review owned companions and shared backend changes. Unlock source when ready to export, then verify the target deployment, packaging and hosted-service configuration.

Make the starting point your own.

Name your project and review the brief. Building starts when you send it.

Start at $0. Source unlock $4.99 once per project.Compare $10 Plus, $20 Pro and $60 Ultra monthly plans

Questions before you build.

Does a member badge protect private content?

No. The service must enforce membership and record-access rules. Check private content with an outsider account.

Can I charge for membership?

Plan the payment and entitlement lifecycle explicitly. The managed test Checkout flow can exercise a purchase, while live subscription access needs separate implementation and verification.

Read the public Markdown reference