> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/website-and-community-surfaces.md). # Website Canonical SONIC public website, community, conversion, marketing and product-truth architecture. The SONIC public website is a **product-led acquisition surface**. Its job is to help visitors understand the creative workflow first, then discover collaboration, marketplace, rewards, governance and Solana infrastructure progressively. ## Canonical domains | Surface | URL | Ownership | | ------------------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------- | | Public website | | Public marketing, product discovery, creators, releases, ecosystem and company information | | Product application | | Authenticated Studio, Wallet, Token Management, Marketplace, Checkout, settings and role-based product workflows | `sonicnetwork.fun` and `sonicnetwork.app` are the canonical public and application origins. Older website/application domains are deprecated and should redirect where operationally appropriate rather than remain as competing canonical URLs. > **MVP rule:** Creator counts, streams, rewards, rankings, token states, governance rights, marketplace activity and release data must not be presented as live unless backed by canonical production data. ## Primary conversion The global marketing CTA is: **Launch Studio →** The canonical target for authenticated product entry is `https://sonicnetwork.app`. Wallet connection is contextual and should appear only when the user reaches an on-chain action. ## Public navigation Recommended primary navigation: ``` Home Create Studio Projects Marketplace Community More ▾ ``` Recommended `More` menu: ``` Creators Challenges Tokenomics Governance Blinks Developers Docs Pricing ``` Do not introduce a generic **Membership** area. Governance is the canonical destination for protocol/community decision-making where governance is actually enabled. ## Homepage story ``` Idea → AI creation → Project → Collaboration → Publish → Participate → Governance / ownership ``` Canonical order: 1. Floating Header 2. Hero + Studio product preview 3. Capability proof 4. AI Studio 5. Project Builder 6. Creator Collaboration 7. Community Challenges 8. Marketplace 9. Rewards & Ownership 10. Governance 11. Solana Infrastructure 12. Pricing 13. FAQ 14. Final CTA 15. Dark-red Footer Every section should make one argument and expose one primary next step. ## Hero copy **Eyebrow** THE CREATIVE PRODUCTION PLATFORM **Title** Turn an idea into a finished creative project. **Description** Generate music with AI, shape ideas into structured productions, collaborate with creators, and manage your work from concept to release in one connected workspace. **Primary CTA** Launch Studio → **Secondary CTA** Explore Projects **Proof line** AI creation · Project production · Creator collaboration · Solana infrastructure ## Product proof near the hero Until verified production metrics exist, use capability proof: ``` AI MUSIC PROJECT BUILDER CREATOR COLLABORATION MARKETPLACE SOLANA ``` Do not use invented creator, track, challenge or rewards numbers. ## Studio presentation The Studio preview should communicate a real product flow: ``` Prompt → Model → Generation progress → Generated track → Open in Project ``` Marketing animations may simulate state transitions but must not imply server-confirmed output. ## Project Builder Project Builder is a signature product concept and should visually transform a prompt into structured production data such as scenes, tasks, assets, collaborators, milestones and release planning. ## Community presentation Community cards prioritize production activity: ``` Project Contribution needed Creator role Deadline Reward Status ``` Avoid generic social-feed layouts when they do not support production. ## Challenges Challenge pages may use cinematic dark treatment, strong artwork, a prominent reward figure and one CTA. Funding and reward status must be explicit. Never imply a reward is funded or claimable without verification. ## Governance Governance is distinct from community membership. Public governance pages may explain proposals, voting, delegation, eligibility and execution, but must accurately label the feature state as `Planned`, `Configured`, `Verified`, `Live` or `Paused`. Token ownership alone must not be described as voting eligibility unless the canonical governance policy confirms it. ## Marketplace Marketplace uses product-first black/white surfaces. Connect Wallet appears only when required for an actual transaction, ownership or claim action. ## Tokenomics Use the current circular red SONIC coin with the white waveform/S mark. Older angular coin artwork is deprecated. Token identity is determined from canonical deployment data, not symbol or artwork alone. ## Footer The default public footer remains dark red in both light and dark themes. Primary footer copy: **Create what comes next.** AI creation, structured production, creator collaboration, and supported Solana-native participation in one connected platform. Recommended groups: ``` PRODUCT Studio Projects Marketplace Pricing ECOSYSTEM Community Creators Challenges Tokenomics Governance RESOURCES Docs Developers Whitepaper Help Status ``` ## SEO metadata baseline Canonical origin: `https://sonicnetwork.fun` Homepage title: **SONIC — AI Creative Production Platform** Homepage description: **Create music with AI, turn ideas into structured projects, collaborate with creators, and manage production from concept to release with SONIC.** Tokenomics title: **SONIC Tokenomics — Supply, Distribution & Utility** Tokenomics description: **Explore the SONIC ecosystem token, including supply policy, distribution, vesting, supported utility, governance, and Solana infrastructure.** Public SEO pages must use `sonicnetwork.fun` as their canonical origin. Application routes under `sonicnetwork.app` should not compete with equivalent public marketing pages for indexing. ## Responsive behavior Mobile composition: ``` Floating Header Single-column Hero Focused Product Preview Capability strip Stacked sections Accordion FAQ Dark-red Footer ``` Do not shrink desktop split layouts into unreadable miniatures. ## Product-data rule Counters, rankings, payouts, proposal state, voting power, badges, engagement metrics and wallet/token state must come from authenticated product data or another approved authoritative source. ## Shipping checklist ``` □ sonicnetwork.fun is the canonical public origin □ sonicnetwork.app is the canonical application origin □ old domains redirect instead of competing as canonicals □ OAuth/CORS/redirect allowlists use the correct origin □ one primary CTA above fold □ one H1 □ no fabricated metrics □ no fake wallet/network state □ no unverified rewards □ no implied governance rights □ responsive at 375px □ keyboard usable □ reduced motion supported □ metadata complete □ theme tested □ footer/header variants correct ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/website-and-community-surfaces.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.