About Arktion

A storytelling platform with a real editorial identity.

Arktion is being shaped as a layered product: public discovery, immersive reading, creator tools, and admin systems — each with a distinct route and visual role.

Distinct visual language

Arktion uses warmer contrast, sharper spacing, and editorial layout rhythm instead of a generic app shell.

Clear route architecture

Public, auth, reader, creator, and admin are separated intentionally so the app stays maintainable.

Useful customization

We can keep custom components where shadcn ends and add hooks only where they improve state or reuse.

Route clarity matters

Public pages live on public routes, auth callbacks stay chrome-free, reader pages get their own layout, and creator/admin stay isolated.

Design should feel authored

The visual system uses editorial spacing, warm surfaces, and custom composition so the app feels more like a publication than a dashboard.

Publish with structure

Creators get a dedicated path for drafts, publishing, translations, and serialized releases instead of a monolithic settings page.

Open path

Build worlds, not just posts

World bibles, fan-dao concepts, community beats, and licensing tools are planned as first-class surfaces.

Open path

Track what matters

Analytics, earnings, subscriptions, and support live in separate flows so the creator side stays comprehensible at scale.

Open path