ElementAdmin v3

English

简体中文

English

简体中文

Appearance

ElementAdmin v3Put the business back in control

A lightweight admin template built with Vue 3, Element Plus, and TypeScript. Dynamic routing, multiple layouts, and shared capabilities keep clear boundaries so each application can add only the business features it needs.

Get started in 5 minutes
Explore the architecture

Dynamic routes are the single source of truth

Routes are fetched from the API after login and drive menus, pages, breadcrumbs, and tabs. There is no second business route table to maintain.

Four layouts, one route tree

Classic sidebar, top navigation, mixed navigation, and dual sidebar layouts share the same route data and automatically fall back to a mobile sidebar.

Packages are ready for multiple applications

Request, CRUD, form, icon rendering, and foundational UI capabilities remain independent of Admin, keeping business state out of the shared layer.

Icons work offline by default

Shared components only render icons. Each application registers its own allowlist, so every App bundles only the icon data it actually uses.

Internationalization updates instantly

Vue I18n, the Element Plus locale, the HTML lang attribute, and persisted state stay synchronized, so changing languages never requires a refresh.

Fewer, clearer abstractions

There is no catalog of presentation components. Tables, dialogs, and detail pages belong to the application; the template maintains only capabilities that remain stable across projects.

DYNAMIC ROUTE PIPELINE

One runtime pipeline powers the entire admin application

01Route APIThe server returns paths, components, and meta
02Permission StoreResolves components and stores visible routes
03Vue RouterRegisters and resets routes within the session
04Layout SystemKeeps menus, breadcrumbs, and TagsView in sync

The boundaries of v3 ​

This is not a copy of the previous documentation. v3 removes the all-in-one component demos, client-side route filtering, and unnecessary utility wrappers. The documentation covers only capabilities that actually exist in the repository.

The template ownsThe application owns
Login sessions, dynamic routes, access recoveryThe concrete role and permission model
Four layouts, menus, and TagsViewPage architecture and business navigation
Shared Request, CRUD, and form stateDomain APIs, fields, and interaction flows
Icon rendering and registrationEach application's icon allowlist
Theme and internationalization infrastructureBrand visuals and business copy

Recommended reading order

For your first integration, read Getting Started, Project Structure and Architecture, and Dynamic Routing and Permissions in order.

Keep the core for real business and stay restrained for unknown requirements.

MIT Licensed · ElementAdmin v3