Tangram is an admin and dashboard template built as one standalone React 19 project, with TypeScript in strict mode, React Router 8, Vite 8, and Tailwind CSS v4. It has 84 finished pages, all built on one design token core. It is a good fit for online shops, creator tools, marketing suites, and other consumer-facing back offices.
Tangram has a flat bento look: light tiles on a deep green canvas, with no borders, no shadows, and no hairlines. Depth comes from blocks of color. Every control is a full pill, and the numbers are set large in Bricolage Grotesque.
84 pages, nothing rounded up
Every route opens a real, finished page. There are no empty placeholder routes, and no page count padded with copies of the same screen.
- 7 dashboards: Home, Sales, Traffic, Products, Customers, Loyalty, and Payments
- 26 lists: orders, drafts, returns, abandoned carts, catalog, collections, inventory, gift cards, reviews, customers, segments, campaigns, email templates, discounts, affiliates, reports, transactions, payouts, disputes, invoices, pages, blog, team, activity, roles, and connected apps
- 8 full-height apps: the shipping queue, customer messages, a social planner, the media library, the team inbox, chat, a calendar, and notes
- 9 forms and editors: Add product, the campaign builder, the post editor, and six settings screens (general, store, checkout, shipping zones, taxes, and notifications)
- 5 records: order, product, customer, campaign, and invoice. Each one is the detail page its list links to.
- 7 authentication screens: sign in, sign up, forgot password, reset password, two-factor authentication, lock screen, and onboarding
- 6 error pages: 401, 403, 404, 500, 503, and maintenance
- A 13-page design kit inside the app: tiles, buttons, inputs, selection, status, navigation, feedback, tables, charts, icons, typography, the color schemes, and the motion system
- 3 standing pages: live traffic, your plan, and the account profile
Every page belongs to one shop
Tangram is not a set of sample screens from many industries. Every page belongs to one small homewares brand. So a number on a dashboard matches the order it came from, and a customer in a list matches the customer record. The demo data lives in 31 JSON files, each number has one owner, and nothing is random when the page renders.
Five color schemes, two themes, two densities
A color scheme is a whole palette, not a new background. Green, Cocoa, Navy, and Plum each change the canvas, the tiles, the text, the charts, and the three signal tiles together. A fifth scheme, Calm, is bone on bone, for people who want a quiet version.
- Light and dark themes for every scheme. In the dark theme, the colored canvas stays and the tiles turn dark.
- Two row heights: comfortable and compact
- An expanded sidebar or an icon rail
- Right-to-left text direction
- A live customizer to switch all of these while the app runs. Your choices are saved in the browser and restored before the first paint, so the page never flashes the wrong theme.
Charts, tables, and a map
Tangram has 13 chart shapes from one library (ApexCharts), behind one typed wrapper, all in the product's colors: a line that draws itself over a soft area, bars that grow one after another, rings that fill to their value with the number in the middle, and small sparklines for table cells. Every chart shows its values on hover, and redraws when you change the theme, the color scheme, or the row height. There are also data tables with a compact row mode, and a live Leaflet map.
Real React, not a port
- React 19.2 and React Router 8.3, with function components and hooks only. There are no class components.
- TypeScript 5.9 in strict mode, with no any in the source. The route manifest is typed, so a wrong page name fails the build.
- Vite 8 with the official React plugin. You get instant hot reload in development and one lazy-loaded file per route in the build.
- Tailwind CSS v4 for layout utilities, with the look set by CSS custom properties.
- Seven runtime dependencies. Two of them (ApexCharts and Leaflet) load only on the pages that use them.
- No jQuery, no Bootstrap, no CSS-in-JS, and no third-party component library to fight with.
Built to be changed
- One token core. Color, radius, and type come from one folder of token files. Components have no hard-coded values, so a new theme is a token change.
- Checked for WCAG 2.1 AA. Every text pair, focus ring, control edge, and chart series meets the contrast level in both themes, at both row heights, and in all five schemes. All 84 routes are checked with axe-core.
- Real RTL. The CSS uses logical properties from the start. The whole app flips, including the charts and the sidebar.
- One route manifest. All 84 routes come from one JSON file. The sidebar, the breadcrumb, and the command palette all read it. To add a page, you add a name and a file.
- Small downloads. 25 KB of CSS and 115 KB of JavaScript, gzipped, on first load, React included.
- Eight checks before a release. Strict type check, ESLint, Stylelint, and checks for tokens, the route manifest, motion, demo data, and gzipped size. All of them are set up in the download.
What is included
- The complete React project: the source, the public folder, the index page, the package file, the Vite config, the TypeScript configs, and a README
- All 84 pages, from one shared route manifest
- The full design token core, with five color schemes in light and dark, and two row heights
- The 13-page design kit, as pages you can open in the running app
- HTML documentation in one file that works offline: getting started, installation, project structure, theming, adding pages, and deployment
- License and credits inside the documentation
Requirements
- Node.js 20.19 or newer, or 22.12 or newer (this is the minimum for Vite)
- npm, Yarn, or pnpm
- No server software. The build command creates static files you can host anywhere.
The demo avatars and illustrations are original SVGs made for this template. No stock photos or paid assets are included. Tabler icons (MIT), the Google Fonts Bricolage Grotesque and Figtree (OFL), and the open-source libraries are credited in the documentation.