PARA

How it works

# Communities implemented

Communities are one of PARA’s clearest non-generic structures. They turn the app away from a single global feed and toward belief clusters, civic hubs, badges, governance, and community-level participation.

Routes

Primary routes

Hub routes
/communities, /base, /my-base
Profile route
/communities/profile/:communityId
Adjacent routes
/communities/:communityId/raq, /communities/:communityId/voters, /communities/:communityId/badges

State ownership

What this route family owns

  • Community identity, slug, and profile framing.
  • Governance roster and role hierarchy overlays.
  • Community-scoped participation routes such as RAQ, voters, and badges.
  • Entry into related civic surfaces such as cabildeos and local reading.

User actions

What users do here

  • Find a political home around ideas, regions, or issue clusters.
  • Read governance and role assignment instead of treating the community as a flat feed.
  • Move into RAQ, voters, badges, and cabildeo from a community context.

The key product distinction is that communities are structural, not decorative. They anchor navigation and participation.

Related contracts

  • com.para.community.defs
  • com.para.community.getGovernance
  • com.para.actor.defs

Read next