A dense React dashboard template for AI-assisted operations, telemetry, and review workflows.
Aether Nexus Dashboard is a static, frontend-only command-center starter. It combines a responsive app shell, operational charts, task review queues, activity streams, and an AI companion panel into one compact interface that can be adapted for internal tools, analytics products, and AI workflow prototypes.
- Responsive three-pane dashboard shell with mobile drawers.
- KPI cards, sparklines, area charts, task queues, and activity feeds.
- AURA side panel for AI-assisted diagnostic and review workflows.
- Tailwind CSS 4 theme tokens for a dark operational interface.
- Recharts visualizations and Lucide React icons.
- No backend, API keys, or runtime environment variables required.
- React 19
- TypeScript
- Vite 6
- Tailwind CSS 4
- Recharts
- Lucide React
- Bun
git clone git@github.com:bymilon/aether-nexus-dashboard.git
cd aether-nexus-dashboard
bun install
bun run devThe dev server runs at http://localhost:3000.
bun run dev # Start Vite on port 3000
bun run build # Create a production build in dist/
bun run preview # Preview the production build
bun run lint # Type-check with TypeScriptsrc/
components/ Sidebar, main dashboard content, and AURA panel
App.tsx Layout state and responsive panel composition
index.css Tailwind theme tokens and global styles
main.tsx React entry point
DESIGN.md Visual design notes and customization guidance
TODO.md Linear-style OSS release backlog- Edit navigation and workspace copy in
src/components/Sidebar.tsx. - Adjust KPI cards, chart data, task queues, and activity feeds in
src/components/MainContent.tsx. - Update AURA panel prompts, generated diagnostic content, and composer actions in
src/components/AIPanel.tsx. - Tune colors, typography, and scrollbar styling in
src/index.css. - Use
DESIGN.mdfor layout, palette, and interaction guidance.
See TODO.md for the release backlog. Tasks are written in a Linear-style format so they can be moved into GitHub issues later.
Issues and pull requests are welcome. Keep changes focused, include screenshots for visual changes, and run:
bun run lint
bun run buildRead CONTRIBUTING.md before opening a pull request.
Do not open public issues for vulnerabilities. Follow SECURITY.md.
MIT. See LICENSE.