Dreams ERP Agent Banner

Introduction

Dreams ERP Next.js is a modern, responsive enterprise administration dashboard built with Next.js 16 (App Router), React 19, TypeScript, and Tailwind CSS v4. It provides prebuilt components and pages to manage employees, CRM, finance, inventory, projects, and more in a unified dashboard.

Requirement

Technologies
  • Node
  • Text editor as per your wish
System Requirements
  • Next.js version = 16.2.10
  • React version = 19.2.7
  • TypeScript version = ^5
  • Node js Package
  • Node version = ^24.4.1
  • Visual Studio Code
  • Terminal

Core Features

– Built with Next.js 16 App Router
– React 19.2.7 + TypeScript
– Server Components with route-group layouts
– Static HTML export ready (output: "export")
– Redux Toolkit state management
– Tailwind CSS v4 (CSS-first config)
– Ant Design v6 component library
– 6 layout variants (default, mini, hoverview, hidden, full-width, RTL)
– Light & dark mode with no flash on load
– Fully Responsive Design
– 220+ prebuilt pages across CRM, HRM, Finance, Inventory, Projects, Sales, Purchase, POS
– ApexCharts, Chart.js & ECharts
– Self-hosted icon webfonts
– React Compiler enabled
– Compatible Browsers: Firefox, Safari, Opera, Edge, Chrome
– Easy to Customize with css Variables

File Structure

Project Overview

The project follows a modular structure with clear separation of concerns.

nextjs/
├── public/
│   └── assets/img/          # avatar, card, icons, product, logo.svg, logo-small.svg, logo-white.svg
├── src/
│   ├── app/                 # App Router
│   │   ├── (auth-pages)/         # 20 pages  -> AuthLayout
│   │   ├── (layout-demo-pages)/  # 5 pages   -> LayoutDemoShell
│   │   ├── (pos-pages)/          # 1 page    -> PosLayout
│   │   ├── (public-pages)/       # 196 pages -> PublicLayout
│   │   ├── globals.css
│   │   ├── layout.tsx            # root layout
│   │   ├── apple-icon.png
│   │   └── favicon.png
│   ├── components/          # 16 shared components
│   ├── config/metadata.ts   # getPageMetadata() helper
│   ├── core/data/           # interface.ts - shared TS types
│   ├── hooks/               # useDebouncedValue, useTagInput
│   ├── layout/              # authLayout, publicLayout, posLayout,
│   │                        # layoutVariantWrapper, layoutDemoShell
│   ├── providers/           # LayoutSync.tsx, StoreProvider.tsx
│   ├── redux/               # store.ts, hooks.ts, slices/layoutSlice.ts
│   ├── routes/all_routes.tsx  # central path constants
│   ├── style/
│   │   ├── css/style.css    # theme tokens + Tailwind entry
│   │   └── icons/           # self-hosted icon webfonts
│   ├── utils/json/          # commonSelectOption, sidebarMenu
│   ├── views/               # page modules
│   └── environment.tsx
├── eslint.config.mjs
├── next.config.ts
├── package.json
├── postcss.config.mjs
└── tsconfig.json
Route groups inside (public-pages)

(advanced-ui), (application-pages), (assets), (base-ui), (charts), (crm), (dashboard), (documents), (finance), (forms), (hrm), (icons), (inventory), (membership), (pos), (projects), (purchase), (sales), (support), (system), (tables), (utilities)

Note

Folders wrapped in parentheses are route groups. They organise files without adding a URL segment, so (base-ui)/ui-accordion/page.tsx is served at /nextjs/ui-accordion. There is no src/app/page.tsx – the / redirect in next.config.ts handles the root.

Shared Components (src/components/)

breadcrumb, common-date-picker, common-date-range-picker, common-footer, common-header, common-lightbox, common-select, common-sidebar, common-tag-input, data-table, image-with-base-path, multiple-Select, password-input, preview-code-toggle, skeleton, text-editor

Page Modules (src/views/)

assets, auth-pages, blank-page, crm, documents, finance, hrm, inventory, main-pages, membership, pos, projects, purchase, sales, support, system, ui-interface

Next.js Structure

Structure Overview

Dreams ERP Next.js uses the App Router with route groups and nested layouts to keep the app scalable and maintainable.

Layouts nest from the outside in: the root src/app/layout.tsx renders the <html> and <body> shell, then each route group applies its own layout, then the page renders.

ROUTE GROUP PAGES LAYOUT
(public-pages)196PublicLayout – sidebar + header shell
(auth-pages)20AuthLayout – bare
(layout-demo-pages)5LayoutDemoShell
(pos-pages)1PosLayout

Each group layout is a one-liner that delegates to the matching file in src/layout/.

Below is the root layout, src/app/layout.tsx:

import { Metadata } from "next";
import StoreProvider from "../providers/StoreProvider";
import LayoutSync from "../providers/LayoutSync";
import { THEME_KEY } from "../redux/slices/layoutSlice";
import "../style/icons/@phosphor-icons/web/duotone/style.css";
import "../style/icons/@phosphor-icons/web/regular/style.css";
import "../style/icons/@phosphor-icons/web/fill/style.css";
import "../style/icons/lucide-static/font/lucide.css";
import "../style/icons/@fortawesome/fontawesome-free/css/fontawesome.min.css";
import "../style/icons/@fortawesome/fontawesome-free/css/all.min.css";
import "../style/css/style.css";
import "./globals.css";
import "preline";

export const metadata: Metadata = {
  title: "Dreams ERP - Tailwind CSS ERP Admin Dashboard Template",
  description: "Dreams ERP is a professional Tailwind CSS ERP Admin Dashboard Template ...",
  authors: [{ name: "Dreams Technologies" }],
  icons: {
    icon: "/nextjs/assets/img/favicon.png",
    apple: "/nextjs/assets/img/apple-icon.png",
  },
};

export default function RootLayout({ children }: Readonly<{ children: React.ReactNode }>) {
  return (
    <html lang="en" data-theme="light" suppressHydrationWarning>
      <head>
        <script
          dangerouslySetInnerHTML={{
            __html: `(function(){try{if(localStorage.getItem(${JSON.stringify(
              THEME_KEY,
            )})==="dark")document.documentElement.setAttribute("data-theme","dark")}catch(e){}})()`,
          }}
        />
        <link rel="preconnect" href="https://fonts.googleapis.com" />
        <link rel="preconnect" href="https://fonts.gstatic.com" crossOrigin="anonymous" />
        <link href="https://fonts.googleapis.com/css2?family=Geist:wght@100..900&display=swap" rel="stylesheet" />
      </head>
      <body>
        <StoreProvider>
          <LayoutSync />
          {children}
        </StoreProvider>
      </body>
    </html>
  );
}
Three things worth noting in the root layout
  • The metadata export – Next's Metadata API sets the title, description and icons. No head-management library is needed.
  • The inline theme script – it reads localStorage["dt-theme"] and applies data-theme="dark" before first paint, which prevents a flash of the light theme. suppressHydrationWarning on <html> is required because that script mutates the DOM before React hydrates.
  • Geist via Google Fonts – loaded with a preconnect and stylesheet link in the head.
Page metadata and paths

Individual pages export generateMetadata using the getPageMetadata(pageName) helper from src/config/metadata.ts. The src/routes/all_routes.tsx map survives as a central set of path constants used by the sidebar menu and links.

Installation Guide

Prerequisites
Node.js and NPM :

Ensure that Node.js is installed and running on your system.

Package Manager

Use npm (recommended with this project lockfile) or Yarn if preferred.

npm -v
Next.js

Next.js is the framework and build tool. It is installed automatically as a project dependency – no global installation required.

Installation Steps
1
Extract & Navigate

After downloading, extract the Dreams ERP package and navigate to the nextjs directory.

2
Install Dependencies
npm install

Before proceeding you'll need to install npm packages. You can do this by running npm install from the root of your project to install all the necessary dependencies.

3
Start Development Server
npm run dev

For running a project, run the command

4
Open in Browser

Open your browser at http://localhost:3000/nextjs. The /nextjs path comes from basePath: "/nextjs" in next.config.ts, and the root / redirects to /login.

5
Build for Production
npm run build

Because output: "export" is set, this produces a static HTML export in the out/ directory, which can be served by any static host. The next start script exists but is not the intended serving path for a static export.

Tailwind Config

CSS-first configuration

This project uses Tailwind CSS v4.3.2, which is configured in CSS rather than JavaScript. There is no content array and no tailwind.config.js in this project at all – the @source directive replaces them. Tailwind is wired in through PostCSS.

The PostCSS setup in postcss.config.mjs is the whole integration:

const config = {
  plugins: {
    "@tailwindcss/postcss": {},
  },
};

export default config;

All configuration lives at the top of src/style/css/style.css:

@import url('https://fonts.googleapis.com/css2?family=Geist:wght@100..900&display=swap');

/* 1. ALL @imports must be at the very top */
@import "tailwindcss";
@import "../../../node_modules/preline/variants.css";

/* 2. Then @plugin and @source */
@plugin "@tailwindcss/forms";
@source "../../../node_modules/preline/dist/*.js";

/* 3. Then @layer and @custom-variant */
@layer theme, base, components, pages, utilities;
@custom-variant dark (&:where([data-theme="dark"], [data-theme="dark"] *));
What each directive does
  • @source – tells Tailwind which extra files to scan for class names. It replaces the content array from v3.
  • @plugin "@tailwindcss/forms" – better default styling for form elements.
  • @import "preline/variants.css"Preline v4 supplies the headless JavaScript behaviour for dropdowns, overlays and tabs.
  • @custom-variant dark – makes every dark: utility key off the data-theme attribute.
Note

src/app/globals.css holds component-level overrides (rich text editor, scrollbars and similar) layered on top of the theme tokens.

Fonts

The default typography font for the template is Geist. It is loaded in two places, and both must be updated when you change it:

1. The Google Fonts link in src/app/layout.tsx
<link
  href="https://fonts.googleapis.com/css2?family=Inter:wght@100..900&display=swap"
  rel="stylesheet"
/>
2. The import and token in src/style/css/style.css
/* Import the new Google Font at the very top of style.css */
@import url('https://fonts.googleapis.com/css2?family=Inter:wght@100..900&display=swap');

/* Update the variable inside the @theme block */
@theme {
    --font-family-primary: "Inter", sans-serif;
}

Color System

All theme colors are defined as design tokens under the @theme directive in your src/style/css/style.css file. These variables control the look and feel of components:

@theme {
    --font-family-primary: "Geist", sans-serif;

    --color-primary: #0F766E;   /* primary color */
    --color-secondary: #2563EB; /* secondary color */
    --color-dark: #1E293B;      /* dark surfaces */

    /* System Colors */
    --color-success: #059669;   /* success states */
    --color-warning: #D97706;   /* warnings */
    --color-danger: #B91C1C;    /* error states */
    --color-info: #0EA5E9;      /* informational */
}

The same block also defines the primary shades --color-primary-100 through --color-primary-900, plus --color-primary-hover, so you can tune hover and accent states without touching component code.

Changing Element Colors

You can customize the color of any element by editing its class or variable assignment in the CSS file. For example, changing the header topbar background color:

.navbar-header {
    @apply bg-(--topbar-bg);
}

Dark Mode

How it Works

Dark mode state is managed in Redux and persisted to localStorage under the key dt-theme. A sync component writes the current theme to a data-theme attribute on the <html> element, which a Tailwind custom variant reads to apply dark: utility classes.

The theme lives in src/redux/slices/layoutSlice.ts, and src/providers/LayoutSync.tsx is the single bridge that writes it to the DOM:

document.documentElement.setAttribute("data-theme", layout.theme);

In src/style/css/style.css, a custom Tailwind variant reacts to that attribute so any dark: utility applies automatically:

@custom-variant dark (&:where([data-theme="dark"], [data-theme="dark"] *));

/* usage example */
body { @apply dark:bg-none dark:bg-[#1A1A1A]; }
Server rendering: avoiding a hydration mismatch

This is the main difference from a client-only React build. The server has no localStorage, so the theme has to be resolved carefully in two stages.

1. A per-request storesrc/providers/StoreProvider.tsx seeds the store like a lazy initializer. On the server readStoredTheme() returns "light", matching the server-rendered HTML; in the browser it reads the same key the inline script used, so the store and DOM agree:

storeRef.current = makeStore({
  layout: { ...defaultLayoutState, theme: readStoredTheme() },
});

2. A pre-paint script – the root layout runs a small blocking script in <head> that applies the dark attribute before the browser paints, so a dark-mode user never sees a white flash:

(function () {
  try {
    if (localStorage.getItem("dt-theme") === "dark")
      document.documentElement.setAttribute("data-theme", "dark");
  } catch (e) {}
})();

Because that script mutates the DOM before React hydrates, the root <html> element carries suppressHydrationWarning.

RTL Support

Right-to-Left layout is driven through Redux rather than by hand-editing markup. Dispatching setVariant("rtl") makes LayoutSync add dir="rtl" to the <html> tag and toggle the layout-rtl class on the body:

<html lang="en" dir="rtl">

Tailwind CSS automatically transforms positioning utilities (like margins, padding, and flex alignments) using standard logical properties when the dir="rtl" attribute is active.

RTL Demo

A preconfigured RTL demo is available at the /layout-rtl route. See src/app/(layout-demo-pages)/layout-rtl/ for a live demonstration.

Icons

Dreams ERP includes multiple popular icon packages ready for use. All of them are self-hosted webfonts under src/style/icons/ and imported in src/app/layout.tsx – no CDN request is made. You can use any of the following icon libraries:

1. Lucide Icons

Use Lucide icons with the icon-[name] class prefix:

<i class="icon-house"></i>
<i class="icon-users"></i>
<i class="icon-settings"></i>
2. Phosphor Icons

Use Phosphor icons with the ph-[style] ph-[name] prefix classes. The duotone, regular and fill styles are imported:

<i class="ph-duotone ph-plus-circle"></i>
<i class="ph-fill ph-calendar"></i>
<i class="ph ph-user"></i>
3. Font Awesome Icons

Use Font Awesome Free icons with standard classes:

<i class="fa-solid fa-hashtag"></i>
<i class="fa-brands fa-react"></i>

Layout Options

Dreams ERP ships six layout variants, all driven from Redux. The variant type is declared in src/redux/slices/layoutSlice.ts:

export type LayoutVariant = "default" | "mini" | "hoverview" | "hidden" | "full-width" | "rtl";

src/providers/LayoutSync.tsx applies the active variant by writing a data-layout attribute on <html> and toggling body classes (mini-sidebar, expand-menu, hidden-layout, full-width, layout-rtl). All variants support light and dark modes.

Demo routes

Each variant has a live demo page under src/app/(layout-demo-pages)/:

  • /layout-mini – icon-only collapsed sidebar.
  • /layout-hoverview – mini sidebar that expands on hover via expand-menu.
  • /layout-hidden – sidebar fully hidden, toggled in on demand.
  • /layout-fullwidth – full-width content with the sidebar as an overlay.
  • /layout-rtl – right-to-left layout.
How the demos work

The group layout renders src/layout/layoutDemoShell.tsx, which derives the variant from the URL segment rather than from a per-page prop:

const VARIANT_BY_SEGMENT: Record<string, LayoutVariant> = {
  "layout-mini": "mini",
  "layout-hoverview": "hoverview",
  "layout-hidden": "hidden",
  "layout-fullwidth": "full-width",
  "layout-rtl": "rtl",
};

const LayoutDemoShell = ({ children }: { children: ReactNode }) => {
  const segment = usePathname().split("/").filter(Boolean).pop() ?? "";
  const variant = VARIANT_BY_SEGMENT[segment] ?? "default";

  return <LayoutVariantWrapper variant={variant}>{children}</LayoutVariantWrapper>;
};

Each demo route is a server page.tsx that exports generateMetadata via getPageMetadata, paired with a *Client.tsx that dynamic(..., { ssr: false })-imports the shared view from @/views/main-pages/layout-demo/.

Default Layout

The default vertical layout with a left sidebar, topbar, and center content area. It is applied by the (public-pages) route group.

  • Sidebar: Navigation menu, logo, profile details, and collapsible dropdowns.
  • Topbar: Search input, user alerts, settings, and profile toggle actions.
  • Responsive: Collapses into an overlay sidebar on tablets and mobile screens automatically.

Mini Sidebar

A screen-saving option that collapses the sidebar to show icons only. LayoutSync adds the mini-sidebar class to the <body> when the variant is active. See the /layout-mini demo route.

  • Icon View: Collapses the sidebar to maximize the main work area.
  • Hover Expand: Hovering expands the sidebar to reveal module text labels (the hoverview variant).
  • Toggle: Switch between default and mini sidebar using the toggle button in the topbar.

Component Reference

Dreams ERP comes with 24+ pre-styled UI components. The routes live in src/app/(public-pages)/(base-ui)/ with their views in src/views/ui-interface/, or click below to view their live layouts:

License

Dreams ERP is developed by Dreams Technologies and is available under both Envato Extended & Regular License options.

Regular License

Usage by either yourself or a single client is permitted for a single end product, provided that end users are not subject to any charges.

Extended License

For use by you or one client in a single end product for which end users may be charged.

What are the main differences between the Regular License and the Extended License?

Note

If you operate as a freelancer or agency, you have the option to acquire the Extended License, which permits you to utilize the item across multiple projects on behalf of your clients.

Support

If you have any questions or run into issues with the template, feel free to contact us via email at support@dreamstechnologies.com.

Response Time: Typically 12–24 hours on weekdays (GMT+5:30). Support covers template bugs, errors, and standard features. It does not cover custom installations or custom coding changes.

Contact Support

Custom Work

Do you need custom development for your application?

If you need customization, new page integration, feature setups, or database connections, our engineering team can help tailor this template to your precise specifications.

  • Tailoring features to your exact branding and workflow.
  • Deploying the template to your production servers.
  • Integrating backend endpoints and databases.
thanks

Thank You

Thank you for choosing Dreams ERP! We hope this template facilitates building your application. We kindly ask you to share your feedback by leaving a rating on ThemeForest.

Leave a Review