Open-source project
puikinsh/Adminator-admin-dashboard avatar
puikinsh/Adminator-admin-dashboard

Adminator v4 dropped Bootstrap, and v3 now lives on a branch

Adminator is easy to use and well design admin dashboard template with dark mode for web apps, websites, services and more

4,693 stars1,747 forksHTMLMIT

At a glance

What is it?
Adminator is a vanilla-JS admin dashboard template with 18 pages, a CSS-variable token system and dark mode. The v4 rewrite cut production JavaScript from about 4.5 MB to about 700 KB, and the previous design now receives security updates on its own branch.
Who is it for?
Adminator fits a team that wants a static HTML and CSS dashboard with no framework to argue about, and that will theme it through CSS variables instead of a component API. It does not fit a team whose existing snippets assume Bootstrap classes, and anyone who needs v3 has to track the legacy-v3 branch, which the README says will continue to receive security updates.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 16 days ago.
What is it written in?
Mainly HTML, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • puikinsh/Adminator-admin-dashboard4,693 ★ · +34
Star history
Repository2026-09-232026-11-15
puikinsh/Adminator-admin-dashboard4.7k4.7k

34 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

v4 cut production JS from 4.5 MB to about 700 KB

The headline change in version 4 is a removal rather than an addition. The page states it plainly: Bootstrap is gone, and production JavaScript dropped from about 4.5 MB to about 700 KB, an 85 percent reduction, across the whole 18 page template. The rewrite also introduced a single JS shell that renders the sidebar, topbar and footer once for all 18 pages. The project describes itself as a vanilla-JS admin dashboard template with a token-driven CSS-variable design system, dark mode and zero framework dependencies, and it names what is absent in the same sentence: no jQuery, no Bootstrap, just clean HTML and modern CSS. What that buys you is a template you can host as static files. What it costs you is every Bootstrap convention your existing markup and third-party snippets rely on.

One data-theme attribute re-skins the libraries too

Dark mode here is a token swap rather than a second stylesheet. All colors, typography, spacing and shadows live in `_tokens.scss` as CSS variables with light and dark variants, and editing one variable updates every component that reads it. A single `data-theme` attribute on the html element swaps the entire interface. The harder part, and the part worth reading closely, is what happens to the embedded libraries: Chart.js, FullCalendar and jsvectormap do not read CSS variables on their own, so they re-render through a `MutationObserver` to pick up the new token values. That is a working approach and it is also a runtime cost you inherit, because every theme change triggers re-rendering of three libraries rather than a stylesheet swap. If you toggle themes often, or animate the toggle, this observer is the code path you will be profiling.

Adding a page means editing one NAV array

The shell architecture is the part an extender touches first. Sidebar, topbar and footer render from a single `NAV` manifest in `Shell.js`. A page declares its own attributes on the body element and provides three placeholders:

html
<body data-active="..." data-crumbs="...">

`data-active` is how the shell knows which nav entry to mark current, and `data-crumbs` is how the breadcrumb trail is built, so a new page is registered by adding one array entry and setting two attributes rather than by copying a layout. The page promises three placeholders and does not name them here, so the exact markup contract lives in the docs rather than on this page.

The UI primitives are hand built, with no Bootstrap fallback

Every primitive listed is custom built and theme aware: buttons, dropdowns, alerts, badges, modals, tabs, accordions, switches and progress bars. The page is explicit that there is no framework CSS and no utility class soup, which is the honest reason the bundle shrank. The cost shows up in two places. First, any snippet you copy from elsewhere that assumes Bootstrap markup has to be rewritten against these classes, and there is no compatibility shim in the template. Second, features that a mature framework ships are not automatically present here.

The npm package ships dist, and main is dist/index.html

What you get from the registry is the built template, and the manifest is explicit about it:

json
"main": "dist/index.html",
"engines": {
  "node": ">=22.22.2"
},

The published file list is dist, src, webpack.config.js, webpack/, CLAUDE.md, CHANGELOG.md, README.md and scripts/clean.mjs, scripts/preview.mjs and scripts/verify-build.mjs, and the package version is 4.4.0 under the name adminator-admin-dashboard, with badges pointing at both npm and a jsDelivr copy. Two practical notes. The Node floor is 22.22.2 or later, which is a narrow gate compared with the browsers this kind of template targets, and it applies to building rather than to viewing. And because src ships alongside dist, you get the source of the shell, the tokens and the pages, so a fork starts from the same tree the author builds rather than from minified output.

Two release builds, one dev server, two linters

The script set explains how the two bundle sizes on the page came about. There is a dev server at `webpack server` and a preview script that runs `node scripts/preview.mjs`. Every build starts with `npm run clean`, and the interesting difference is a single environment variable: `release:minified` sets MINIFY=true while `release:unminified` sets it to false, and the plain build script uses MINIFY=false. So the 700 KB figure on the page depends on which of those you ship. There is also `build:analyze`, which turns on ANALYZE=true when you want to know where the bytes went. Linting includes a `lint:js` script that runs eslint over src/assets/scripts. Tests are configured by vitest.config.mjs, and the tree adds a browserslist file, a .nvmrc, ci/ and screenshots/.

v3 is a branch now, not a release line

The page carries a heads-up notice about version 4.0.0 being a ground-up rewrite, with a new design system, new shell architecture and Bootstrap removed. If you prefer the previous design, it lives on the `legacy-v3` branch, and the page says that branch will continue to receive security updates. Read precisely, that is a maintenance promise about defects and a freeze on features. It also changes what a version number means for you: staying on the old design means tracking a branch, not pinning a tag, so your dependency or vendored copy has to follow that branch explicitly.

Six pages are shown and eighteen are claimed

The preview section names six of the eighteen pages: Email as a three-pane inbox, Calendar with full FullCalendar, Charts with themed Chart.js, Forms with inputs and switches, a Data Table that sorts, filters and paginates, and a split-screen Sign In. The README's Pages Included section, which falls after the excerpted part, is where the full list belongs. The table of contents also promises sections on pages included, architecture, theming, tech stack, migrating from v3 and browser support. And the page recommends other products: the paid collection it links includes one template on React, TypeScript, Tailwind CSS and Vite with nine dashboard designs, and several on Bootstrap 5, one with right-to-left support and ten color presets. Those are the author's recommendations, and their stacks differ from this template's in exactly the way that matters when you are choosing.

Editorial conclusion

Adminator fits a team that wants a static HTML and CSS dashboard with no framework to argue about, and that will theme it through CSS variables instead of a component API. It does not fit a team whose existing snippets assume Bootstrap classes, and anyone who needs v3 has to track the legacy-v3 branch, which the README says will continue to receive security updates. Before you adopt it, confirm your Node version clears the 22.22.2 floor in package.json, decide whether you want the minified or the unminified webpack build, and read the README sections on browser support and migrating from v3.

Frequently asked questions

What is the best admin dashboard template?

This repository does not answer that, since it is the page for one template. What Adminator states about itself is a vanilla-JS admin dashboard template with a token-driven CSS-variable design system, dark mode, no jQuery and no Bootstrap, 18 pages, and about 700 KB of production JavaScript after the v4 rewrite.

What is Adminator 4?

Adminator 4 is a vanilla-JS admin dashboard template with a token-driven CSS-variable design system, dark mode and zero framework dependencies. Version 4.0.0 was a ground-up rewrite with a new design system and new shell architecture, and Bootstrap was removed.

How do I install Adminator?

The package is published to npm as adminator-admin-dashboard and is also served through jsDelivr. package.json sets main to dist/index.html, requires Node 22.22.2 or later, and ships dist, src, webpack.config.js, webpack/, CLAUDE.md, CHANGELOG.md, README.md and three scripts (clean.mjs, preview.mjs, verify-build.mjs).

Does Adminator support dark mode?

Yes. A single data-theme attribute on the html element swaps the whole interface, and Chart.js, FullCalendar and jsvectormap re-render through a MutationObserver to read the new token values. The tokens live in _tokens.scss as CSS variables with light and dark variants.

Which libraries does Adminator use?

Chart.js with six chart types, FullCalendar with all four views and 24 seed events, and jsvectormap, all of them themed. The UI primitives themselves, including buttons, dropdowns, alerts, badges, modals, tabs, accordions, switches and progress bars, are custom built instead of coming from a framework.

Can I keep using the old Adminator 3 design?

The v3 codebase lives on the legacy-v3 branch and the page says it will continue to receive security updates. Version 4 replaced the design system and shell architecture and removed Bootstrap, so v3 is maintained as a branch rather than as a release line.

Official sources

  1. License: MIT
  2. Project website
  3. puikinsh/Adminator-admin-dashboard on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/puikinsh-adminator-admin-dashboard.svg)](https://hysenlabs.com/projects/puikinsh-adminator-admin-dashboard)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/puikinsh-adminator-admin-dashboard.svg)](https://hysenlabs.com/projects/puikinsh-adminator-admin-dashboard)

Was this useful?