Platform systems prepared as modules.
Sedona is not being shaped as a collection of disconnected pages. Each module below exists to reduce future rework when CMS, auth, payments and Web3 features begin interacting for real.
Content System
Payload collections, media and field-level localization provide the publishing base for projects, blog and release messaging.
Access System
Transactions, entitlements and protected dashboard surfaces define who can reach premium assets and why.
Wallet System
Wallet connection, bindings and token account placeholders keep the product ready for future gated experiences.
Locale routing is consistent across public and dashboard pages.
The same app shell can evolve from marketing to authenticated experience.
The release center is already modeled around entitlement-aware delivery.
Token support is prepared structurally before being implemented behaviorally.