design

Arena

Arena is Dravensoft's design language: a token layer, React and Angular component libraries built on that layer, and a shared Tailwind layer. Arena's identity is warm black under bone text, with crimson as the voice and gold as distinction.

Arena is a product-application library. Arena ships tables, forms, navigation, dialogs, charts, cards and the states around them, which is the furniture of an application somebody works in. A media or a consumer product is a different register. A photo wall, a feed of posts, a document editor or a game map is markup you write yourself. The skin travels either way, because a style plugin's answers hold whatever the product is. When that is your product, or one screen of it, read references/media-register.md. That page is what Arena hands you instead of a component: the pattern your markup binds, the parts the package already ships for it, and the one rule that bends.

This file routes. Read only what your task needs. The rules below bind the code you write. The table under them routes. Read the rules once per project rather than once per screen.

Which job is this?

Building something with Arena, meaning a screen, a prototype, a skin or an integration: stay here and follow the table below. On a project you have not walked yet, start at references/cold-start.md instead. That page's first question is whether the project already carries Arena. A project that does gets a short walk, which reads the config and the style plugin already there. A project that does not gets the only page that asks what this product looks like before anything answers.

Changing Arena itself, meaning adding a component, moving a token, or editing a contract or a gate: read AGENTS.md instead. That file is the root of the other branch and this file is not. The path is relative to a clone. A published copy of this file points that link at the repository, because that branch belongs to the repository and reaches nothing a package or this site carries.