Public marketing and content routes share one editorial shell built on reusable `packages/ui` primitives.
The shell stays intentionally modular: content pages, store pages, and server-facing information all render inside the same visual language without hardcoding business flows yet.
The landing surface anchors the public shell and introduces the store, server, and content navigation model without committing to final module logic.
Primary storefront and featured item surfaces live under the catalog tree.
Static and editorial information pages reuse the same content shell.
Monitoring and command references stay available from the public layer.
/catalog
/product/raider-bootstrap-kit
/p2p
/referrals
/news
/rules
/socials
/commands
/monitoring
/wipe-block