Skip to content

Documentation · ARDOR

ARDOR Guides ​

ARDOR is the browser framework of VENIZIA. It structures ra-core applications inside an IGNIS inversion-of-control container. These guides take you from a first project to the core concepts and a migration path.

ARDOR gives you:

  • A container and decorators in the browser (@venizia/ardor-kernel), with React hooks to resolve what you bind (@venizia/ardor-react). @venizia/ardor re-exports the kernel, react and admin packages.
  • A REST data provider, token refresh on a 401 and i18n for ra-core (@venizia/ardor-admin).
  • An HTTP repository from IGNIS on @venizia/ardor/repository, which can share the data provider's token and 401 refresh through getDataSourceAuth().
  • Runtime configuration. RuntimeConfig.get reads window.__APP_CONFIG__, so one built image serves every environment; with required: true it throws an error that carries a code. See One image for every environment.
  • A VULCAN preset that generates an admin with Tailwind, an nginx image (gzip, /health, security headers) and that runtime configuration.

ARDOR is before 1.0, and a minor release can break: read where ARDOR is today.

Where to start

  1. 01Create a ProjectStart a monorepo with an admin, or add one to a monorepo you have, with one VULCAN command.
  2. 02QuickstartWrite a small admin by hand against a stub API: a datasource, a repository, a list page and a login.
  3. 03Build an AdminCreate a complete administration console with list, create, edit and delete pages for one resource.

Learning Roadmap ​

1

First Steps

Create a Project or Setup → Quickstart

Generate an admin with one command, or set up a Vite project and write a small one by hand
2

Build Something Real

Build an Admin → Add Sign-In → Add a Language

Construct complete administrative interfaces with authentication and translations
3

Understand the Framework

Application → Configuration → Providers → Resources and Pages → Dependency Injection

Deep dive into container lifecycles, configuration classes, and dependency resolution
4

Go Further

API References → Best Practices → Migration

Consult technical references, apply production patterns, and migrate legacy codebases