LEVIATHAN NEWS

What changed.
What comes next.

Public product updates and website-v2 development milestones in one place. For deeper implementation context, use the Development Blog; for exact repository changes, use the changelog and GitHub history.

Development Blog →Changelog Roadmap

Website v2September 14, 2026

Community and support become real website systems.

Website v2 now includes a Leviathan-account forum, a development blog, long-form articles and a private support-ticket workspace. These surfaces deliberately separate public discussion, structured feedback, reproducible bugs and user-specific support instead of forcing every conversation into one channel.

The private support flow uses stable SUP identifiers, status history, replies, product and platform context, optional Leviathan error codes and staff-only internal notes.

Open Forum Support Center Read guides

V2COMMUNITY LAYER

RECENT DEVELOPMENT

Current website-v2 milestones.

These entries describe work present in the website-v2 development branch. Production availability depends on a successful deployment.

CapesSep 14

Cape Archive redesign

Official cape names, release context, type-aware rarity, obtainability, linked-profile ownership signals, trusted references, downloads and multiple preview modes.

Explore Capes →

SupportSep 14

Private support tickets

Account-bound cases with stable ticket IDs, product context, replies, status, priority and protected staff notes.

Open Support →

CommunitySep 14

Leviathan Forum

Account-backed discussions with categories, replies and canonical per-user voting rather than anonymous public posting.

Open Forum →

ProfilesSep 14

Profile identity layer

Profile claiming, account linking, notable verification, ranks and external profile references are being kept as separate signals with distinct meanings.

Browse Profiles →

KnowledgeSep 14