# shadcn-dashboard-landing-template: an admin panel and a landing page in one repo > The ShadcnStore template ships the same product twice, once as a Vite React application and once as a Next.js 16 App Router application, with 30+ dashboard pages, a marketing landing page, live theme customisation and a component library built on shadcn/ui. It suits a developer who wants a presentable admin interface to start from rather than a design system to build. **shadcnstore/shadcn-dashboard-landing-template** — Accelerate your development with a sleek, open-source admin dashboard and landing page built on Vite-React, Next.js, Tailwind CSS, and Shadcn/UI which is fully customizable and production-ready. - Repository: https://github.com/shadcnstore/shadcn-dashboard-landing-template - Website: https://shadcnstore.com/templates/dashboard/shadcn-dashboard-landing-template/dashboard - Stars: 1,260 · Forks: 265 - Language: TypeScript - License: MIT - Published: 2026-10-19 · Updated: 2026-10-19 · Language: en - Canonical page: https://hysenlabs.com/projects/shadcnstore-shadcn-dashboard-landing-template ## Two templates, two frameworks, one product This is an admin dashboard template and a landing page template, and the unusual thing about it is that both come in two framework versions. The project description says it is built on Vite-React, Next.js, Tailwind CSS and shadcn/ui, and the README expands it into a Vite plus React plus TypeScript version and a Next.js plus TypeScript version. The live demos are published separately, one for the dashboard with apps and one for the landing page, and the README notes the template includes both a complete dashboard, with mail, tasks, chat and calendar apps, and a marketing landing page in both Vite and Next.js versions. The primary language is TypeScript, the licence is MIT, the last push was on 2026-10-09, and the releases are v2.0.0 on 2026-10-08, v1.1.0 on 2026-01-02 and v1.0.0 on 2025-09-24. The maintained by ShadcnStore framing is worth keeping in mind, since the same shop sells premium blocks and the free template is the funnel. ## The 2.0 move from Radix to Base UI The most consequential line in the README is the note that 2.0 is out and the template now runs on Base UI instead of Radix UI, with every dependency on its latest release. There is a link to the changelog section on migrating a customised 1.x copy. This is the kind of change that breaks a customised fork, and it is the reason to read the changelog before you start rather than after. The component library is described in the feature list as shadcn/ui on Base UI in the base-nova style, and the earlier Radix-based version is the one most existing copies will be running. The two are not interchangeable, because a shadcn/ui component is copied into your source rather than installed, so a change of underlying primitive library propagates into files you have edited. The release timing is recent, v2.0.0 on 2026-10-08, and the last push was the next day. ## What is in the dashboard The dashboard feature list is specific about the scope. There are two dashboard variants, an Overview and an Analytics. There are app demos for Mail, Tasks, Chat, Calendar and Users. There are more than 30 pages including authentication, settings, error pages, FAQ and pricing. The data tables are advanced, with sorting, filtering and pagination, and the charts use Recharts. The features that make it a template rather than a mockup are the ones you would otherwise build first, the tables and the charts, because a dashboard without a working paginated table is a picture of a dashboard. The error pages are explicitly called out, 404 and 500 among them, which is a small signal about the quality of the reference implementation, since most templates skip them and every application needs them. ## Theming, and the two customisers Theming is where this template does more than ship a dark mode toggle. There is a live theme customizer for real-time colour and layout switching, and a built-in customizer that previews all possible combinations live, alongside a tweakcn integration for professional theme management. The multiple layouts cover sidebar variants and collapsible navigation, and the responsive design is described as mobile-first with container queries rather than media queries, which is the more modern approach and the one that works with a resizable sidebar. Dark and light mode switching is handled without a reload. The reason two customisers exist is that they serve different purposes, with tweakcn giving you a controlled professional theme editor and the built-in one giving you a fast preview loop while you are still deciding what you want. ## The repository layout, and how the two versions differ The top level is `nextjs-version/` and `vite-version/` beside a `docs/` directory, and the README prints the full tree of the Vite version. The `src/app/` directory holds the demo pages and applications, with subdirectories for the dashboard and its alternative, the landing page, auth, the mail, tasks, chat and calendar demos, settings, errors, users, faqs and pricing. Alongside it sit `src/components/` with the shadcn/ui components under `ui/`, the layout components and the theme customizer, then `src/hooks/`, `src/lib/` and `src/types/`. The Next.js version mirrors that structure but uses route groups, with an `(auth)` group containing login, signup, forgot-password and errors, and a `(dashboard)` group containing the dashboard, its alternative, the applications, the settings and the pricing pages, and a `layout.tsx` for the dashboard shell. The route group pattern is the meaningful difference between the two trees, and it is the reason the Next.js version suits an application with a shared authenticated shell while the Vite version suits a single-page admin. ## Where this template sits Two things about it are worth knowing before you commit. The first is that a template is a starting point, not a product, and the demo applications, the mail client, the task manager and the chat, are scaffolding to be deleted. They are there so the dashboard has data to display and so you can see the tables and charts working, and keeping them is a decision rather than a default. The second is the maintenance model. The template is published by a store that sells premium blocks, and the free version is the top of the funnel, which means the pace of updates follows what sells rather than what you need, and a major version that swaps the component primitives is exactly the kind of change that arrives on a schedule you do not control. The README's own upgrade path, pointing at the changelog for migrating a customised copy, is the practical advice to read before you start editing rather than after. ## Conclusion Adopt the shadcn-dashboard-landing-template if you want a complete, presentable admin interface and a marketing page to start from, since the amount of scaffolding it removes is substantial. Skip it if you need one framework only and would rather not carry two copies of the same UI, because the two versions are separate applications. Before you start, note that version 2 moved the component library from Radix UI to Base UI, so a customised 1.x copy needs the changelog migration notes, and the package manager is pnpm. ## FAQ ### What is in the shadcn-dashboard-landing-template? Two complete templates, a modern admin dashboard with 30+ pages and a business-ready landing page, each shipped in a Vite React version and a Next.js 16 App Router version, with demo mail, tasks, chat and calendar applications. ### What changed in version 2.0 of the template? The component library moved from Radix UI to Base UI, with every dependency on its latest release. The changelog has a section on migrating a customised 1.x copy, and that is the thing to read before starting. ### How do I change the colours and layout of the template? With a live theme customizer for real-time colour and layout switching, a built-in customizer that previews all possible combinations, and a tweakcn integration for professional theme management. There are also multiple layouts with sidebar variants and collapsible navigation, plus dark and light mode. ### What is the difference between the Vite and Next.js versions? The Next.js 16 version uses the App Router with route groups, an (auth) group and a (dashboard) group with a shared layout, while the Vite version is a single React application with the pages directly under src/app. The README calls the Next.js version production-ready with the App Router. ## Sources - [License: MIT](https://github.com/shadcnstore/shadcn-dashboard-landing-template/blob/main/LICENSE) - [Project website](https://shadcnstore.com/templates/dashboard/shadcn-dashboard-landing-template/dashboard) - [README](https://github.com/shadcnstore/shadcn-dashboard-landing-template/blob/main/README.md) - [Releases](https://github.com/shadcnstore/shadcn-dashboard-landing-template/releases) - [shadcnstore/shadcn-dashboard-landing-template on GitHub](https://github.com/shadcnstore/shadcn-dashboard-landing-template) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/shadcnstore-shadcn-dashboard-landing-template