Adminova Next.js documentation
A separate React edition built with the Next.js App Router, TypeScript, and Tailwind CSS. Includes 49 routes, native React interactions, local chart/calendar dependencies, and static export support.
Quick start
Use Node.js 20.9 or newer; Node.js 22 is configured for the Netlify build. Run these commands inside adminova/nextjs/:
npm ci npm run dev # http://localhost:3000/nextjs/ # Production static export npm run build npm start
After building, preview all editions from adminova/ using node scripts/serve-package.mjs. Next.js is served at http://127.0.0.1:8080/nextjs/. The HTML editions remain build-free; Next.js source requires installation and a build.
Folder structure
nextjs/ ├── src/app/ App Router pages, layout, metadata, 404 ├── src/screens/ Editable TSX examples for the template pages ├── src/components/ React navigation, UI, apps, products, dialogs, charts ├── src/lib/pages.json Route directory and navigation metadata ├── src/styles/ Tailwind theme and shared component layers ├── public/assets/img/ Local images ├── scripts/ Preview, checks, screenshot helper ├── tests/ Browser interaction tests ├── next.config.ts Static export and /nextjs base path ├── package.json Pinned runtime dependencies └── out/ Generated static export (not committed)
Pages included
Each page uses App Router navigation and an individual screen module. Demo links open in a new tab.
| Category | Pages |
|---|---|
| Dashboards | Analytics, CRM, eCommerce, Projects, Finance, Helpdesk, Academy |
| Apps | Email, Chat, Calendar, Kanban, File Manager, Tasks, Notes, Contacts |
| Commerce | Products, Add Product, Categories, Orders, Order Details, Customers, Customer Details, Reviews, Store Settings |
| Pages | Profile, Account Settings, Security, Billing, Notifications, Pricing, FAQ, API Keys |
| Components | Components, Buttons, Cards, Modals, Tabs, Alerts, Forms, Tables, Charts, Timeline |
| Authentication | Login, Register, Forgot Password, Two Step, Lockscreen, Error 404, Maintenance |
React components
WorkspaceShell shares the header and navigation. WorkspaceProvider manages appearance, direction, layout, dropdowns, dialogs, and toasts. Screen connects the migrated TSX examples to React state for tabs, collapse panels, forms, table filtering, and reporting controls. Chart loads Chart.js on demand and cleans up chart instances.
The eight app workspaces and the product catalog/editor have typed React state and local persistence. They do not load the HTML edition runtime scripts or embed the existing pages.
Layouts and preferences
Default, compact, detached, wide, and horizontal layouts work with light/dark appearance and LTR/RTL direction. Mobile uses a navigation drawer. Preferences are stored under adminova-nextjs-theme, adminova-nextjs-layout, and adminova-nextjs-direction. These keys are isolated from the HTML editions.
Browser features
Analytics uses one consistent illustrative dataset across Bootstrap, Tailwind, and Next.js. Selecting a reporting period updates the metrics, chart totals, campaign spend, funnel counts and percentages, and acquisition-channel counts together. These figures are demo data, not a connected analytics service.
- Profile and notification menus open as nonblocking dropdowns.
- Ctrl/Command + K opens a searchable route directory.
- Analytics includes reporting periods, campaign filtering, and CSV export.
- Tasks, notes, chat, Kanban, contacts, calendar events, and email drafts use local React workflows.
- File Manager stores file metadata locally; it does not upload files to a server.
- Authentication pages validate locally; they do not implement real authentication.
Customization
Edit page JSX in src/screens/, reusable components in src/components/, and design tokens in src/styles/globals.css. The route directory lives in src/lib/pages.json. Its metadata is used for navigation, search, static route generation, and page titles.
App workflows live in src/components/apps/; the app selector loads only the selected workflow. Product screens live in src/components/commerce/catalog.tsx and editor.tsx. Typed fixtures and pure helpers live in src/lib/app-demo-data.ts and src/lib/products.ts. Analytics uses its dedicated component and shared validated dataset. src/components/client-ready.tsx keeps native controls disabled until each lazy workflow hydrates, preventing early edits from being lost on slower devices. File comments explain data ownership, storage boundaries, validation, and cleanup; the package-root DEVELOPMENT.md maps sources and rebuild commands.
Keep client state in client components. Route wrappers and metadata use server components at build time. Assets use the configured /nextjs base path; update next.config.ts, src/lib/routes.ts, and asset references together if moving this edition to its own domain root.
scripts/import-pages.py records the initial migration. It is not part of the normal build and rerunning it replaces migrated TSX examples. Customize the React sources directly.
Product catalog and editor
Create and edit products, save drafts, publish to the local catalog, manage prices and stock, generate up to 30 variants, and add up to four JPG/PNG/WebP images of 2 MB each. Images are resized locally before saving. SKU and price checks run before persistence.
Products use adminova-nextjs-products-v1. Data remains in the current browser and is not synchronized with a live store or the HTML editions. Passwords and payment credentials are not saved by the settings demos.
Assets and dependencies
Next.js 16.4.6, React 19.3.1, Tailwind CSS 4.3.5, Chart.js 4.5.1, and FullCalendar 6.1.15 are recorded in nextjs/package.json and its lockfile. Runtime assets are bundled locally; the preview does not require a CDN. Dependency licenses remain in their installed packages; see nextjs/THIRD-PARTY-NOTICES.md.
Validation
# Inside nextjs/ npm run build npm run check # Browser checks: first start the package server on port 8080 npx playwright install chromium npm run test:e2e # From adminova/ node scripts/check-package.mjs node scripts/build-showcase.mjs
Browser tests cover all routes, hydration errors, dropdowns, keyboard search, appearance, layouts, mobile navigation, reporting, product creation/variants, and core app workflows.
Development commands
| Command | Purpose |
|---|---|
npm run dev | Next.js development server at /nextjs/. |
npm run build | Production build, type checking, and static export. |
npm run check | TypeScript and exported route/asset checks. |
npm start | Serve the production export. |
npm run test:e2e | Run browser tests against the full-package preview. |
Netlify and static deployment
The root netlify.toml installs and builds Next.js, then runs scripts/build-showcase.mjs. The resulting dist/ contains only public assets for all three editions, landing pages, documentation, and description images. Publish dist/; its Next.js preview is /nextjs/.
For other static hosts, run the same build commands and upload dist/. Static export supports these frontend demos without a Node.js runtime. Server Actions, live authentication, payments, and backend APIs are outside this template; enable an appropriate deployment mode when adding server functionality.
Support notes
This is a frontend dashboard template. Demo interactions use local browser state. Connect your own backend, authentication, billing, storage, and email service for production operations. Use the documentation hub to switch editions.