# Public site, CMS, launchpad, publishing, and commerce

## Public information architecture

- Public home, how it works, learn more, community, showcase, metrics, and Nightpapers.
- Tier/persona directories for members, founders, builders, sponsors, catalysts, and luminaries.
- DUNA directory and individual public DUNA pages.
- Public launchpad list/detail and market/DUNA calls to join or contribute.
- Registered-agent information, privacy policy, terms of service, and account deletion request.
- Start, signup, login, checkout, cofounder/founder continuation, upgrade, and purchase-success routes.

## CMS and sites

- Payload CMS admin with multi-tenant users, tenants, media, categories, pages, and posts.
- Create/read/update/delete CMS records subject to collection permissions.
- Manage site records and render a site home, named page, blog list, blog post, and document preview.
- Upload/select media and associate categories/content.
- Expose Payload MCP for approved content operations.
- Support public/private site visibility and preview-before-publish.

## Commerce and entitlement

- Display membership plans, included features, coin allocations, bonuses, and current tier.
- Select/upgrade tier and start payment/onramp checkout.
- Associate purchase with wallet/account and founder status.
- Show checkout success/failure/cancelled/pending states.
- Apply code price/discount and access role.
- Surface coins, faucet, usage, and subscription-aware feature gating.

## Discovery and trust

- Search/browse public agents/members/markets/movements.
- Show public handles, profile/brand information, publication status, metrics, and membership tier.
- Show legal entity/registered-agent context for DUNAs where appropriate.
- Clearly distinguish promotional claims, live product capability, sample data, and unavailable/coming-soon features.

## New UI requirements

- Use one shared content model and navigation system for public pages, public profiles, DUNAs, launchpad, and generated sites.
- Provide editorial draft, scheduled/published, archived, preview, revision, and permission states.
- Make commerce receipts, entitlements, refund/support paths, and wallet/account linkage visible.
- Avoid presenting sample/legacy review data as a live transaction or governance state.

