Skip to content


This section describes common steps to customize the dashboard.

Dynamic document <title> tag

Document <title> tag contists of defaultDocumentTitle and route's meta.title.

For instance, HomeView's title Dashboard — Admin One Vue 3 Tailwind is generated with ${to.meta.title} — ${defaultDocumentTitle}.

Both const defaultDocumentTitle and router.afterEach hook (where title template is being processed) are set in src/main.js

Each route's meta.title can be set in src/router/index.js

const routes = [
    // Document title tag
    // We combine it with defaultDocumentTitle set in `src/main.js` on router.afterEach hook
    meta: {
      title: 'Dashboard'
    path: '/dashboard',
    name: 'dashboard',
    component: Home

Static meta and title in index.html

Update info in <title> and <meta> tags in index.html:

<title>Admin One - Vue.js 3 Tailwind dashboard template</title>

<meta name="description" content="Admin One - free Vue.js 3 Tailwind dashboard">

<meta property="og:url" content="">
<meta property="og:site_name" content="">
<meta property="og:title" content="Admin One Vue.js 3 Tailwind free">
<meta property="og:description" content="Admin One - free Vue.js 3 Tailwind dashboard with dark mode. Vite & Vue CLI supported">
<meta property="og:image" content="">
<meta property="og:image:type" content="image/png">
<meta property="og:image:width" content="1920">
<meta property="og:image:height" content="960">

<meta property="twitter:card" content="summary_large_image">
<meta property="twitter:title" content="Admin One Vue.js 3 Tailwind free">
<meta property="twitter:description" content="Admin One - free Vue.js 3 Tailwind dashboard with dark mode. Vite & Vue CLI supported">
<meta property="twitter:image:src" content="">
<meta property="twitter:image:width" content="1920">
<meta property="twitter:image:height" content="960">

Remove our Analytics

Remove our analytic script from index.html:

<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src=""></script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'UA-130795909-1');


Favicon file is located in public/favicon.png. It's set with basic link tag, but you're free to add other favicon variations in index.html:

<link rel="icon" href="/favicon.png">
<!-- Other icon variations -->

Default style

It's likely, you'll use only one app style, either basic or one of listed in src/styles.js. So, let's just set one of choice.

src/main.js (or resources/js/app.js for Laravel)

// styleKey is no longer needed, so remove it from @/config.js import
// import { darkModeKey, styleKey } from '@/config.js'
import { darkModeKey } from '@/config.js'

// Remove setStyle action argument
// styleStore.setStyle(localStorage[styleKey] ?? 'basic')

src/stores/style.js (or resources/js/stores/style.js for Laravel)

Here we just import the only required style object and set it via store:

// Replace @/styles.js import
// Import either `basic` or any other style of choice
import { basic as styleDefault } from '@/styles.js'

// styleKey is no longer needed, so remove it from @/config.js import
// import { darkModeKey, styleKey } from '@/config.js'
import { darkModeKey } from '@/config.js'

export const useStyleStore = defineStore('style', {
  state: () => ({
    // ...
  actions: {
    // Set imported style
    setStyle () {
      for (const key in styleDefault) {
        this[`${key}Style`] = styleDefault[key]
    // ...


Remove unused const declarations, so Tailwind will not add that to production CSS file.

Dark mode setting

By default we check, if darkMode is enabled or disabled in localStorage[darkModeKey] and if nothing's set there, we check prefers-color-scheme setting.

// Dark mode is off by default, then we check prefers-color-scheme setting
if ((!localStorage[darkModeKey] && window.matchMedia('(prefers-color-scheme: dark)').matches) || localStorage[darkModeKey] === '1') {

You may prefer to use backend-based setting instead of localStorage, or CSS-only solution, based on Tailwind media query. For CSS-only solution, remove darkMode setting from tailwind.config.js

Aside Menu

Basic structure

Aside menu is configured in src/menu.js. The basic structure is array of menu items.

To make the link work, either to or href should be set. Icon is optional, but is recommended for first level items, and is not recommended for dropdown items.

<AsideMenuItem> emits @menu-click event with two arguments - event and item.

export default [
    // RouterLink path
    to: '/dashboard',

    // ... or external link href
    href: '',

    // Target (optional)
    target: '_blank',

    // Icon (optional)
    icon: mdiDesktopMac,

    // Menu item label
    label: 'Dashboard',

    // Dropdown menu (optional)
    menu: [],

    // Key. Required if using secondaryMenu
    key: 'secondary-1'


Icons shall be set for all items on first-level menu, excluding those inside a dropdown.

Dropdown items are placed in menu.

How to structure items properly?

First-level items can conatain menu (which is a dropdown):

export default [
    to: '/',
    icon: mdiDesktopMac,
    label: 'Item without submenus'
    label: 'Dropdown',
    icon: mdiViewList,
    menu: [
        label: 'Item One'
        label: 'Item Two'

External links can be set via href, the target is optional:

export default [
      href: '',
      label: 'External link',
      icon: mdiMonitorShimmer,
      target: '_blank'
    // ...

Icon set

We use @mdi/js package. Full list of icons is available on Material Design Icons website.

The idea behind <BaseIcon /> is an <svg> tag with the :path set via prop value from @mdi/js package. So, you can use any icon package which provides svg paths.

Why not just use an icon font? Svg paths are better, because you import only what you need. When using font you get excess payload of about 700kb (in case of @mdi/font).