Getting Started
Project Structure
Nexadmin follows the Next.js App Router structure and keeps reusable UI, mock data, and domain types separate.
nexadmin/
├── app/ # Routes, layouts, and global styles
├── components/ # Shared UI and feature components
├── content/docs/ # Public documentation
├── data/ # Mock datasets used by the demo
├── hooks/ # Shared React hooks
├── lib/ # Utilities and shared application logic
├── public/ # Images and other static assets
├── src/config/ # Application configuration, including navigation
└── types/ # Shared TypeScript domain typesImportant areas
app/contains the marketing, authentication, dashboard, and documentation routes. Parenthesized folders are route groups and do not appear in the public URL.components/contains the design-system primitives and reusable feature UI.data/contains deterministic mock data that can be replaced with API responses.src/config/navigation.tsis the main dashboard navigation configuration.app/globals.csscontains the shared design tokens and appearance variables.public/contains product images, dashboard screenshots, and other static assets.
When adding a feature, keep route composition in app/, reusable UI in components/, shared types in types/, and larger demo datasets in data/.