World Vibe Web
The distributed app store for vibe-coded projects. Browse, discover, and install open-source apps from across GitHub.
翻译准备中
尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
A React + TypeScript admin dashboard for managing an ecommerce store — orders, sales analytics, and (soon) customers and products.
Built as a portfolio project to practice frontend architecture, state management, and data visualization with a modern React stack.
Dashboard
• KPI cards with sparkline trends
• Sales performance bar chart and category breakdown donut chart
• Recent orders widget
Orders
• Full order list with status badges and formatted currency
• Filter by status, search by customer/email, and filter by date range
• Order detail side panel with line items and totals查看完整 README ↗A React + TypeScript admin dashboard for managing an ecommerce store — orders, sales analytics, customers and products, backed by Supabase.
Built as a portfolio project to practice frontend architecture, state management, and data visualization with a modern React stack.
Live demo: management-software-three.vercel.app — click Try the demo on the login page to explore it with sample data.
Authentication
app_metadata: admin (full access) and demo (read-only); any other account is signed outPublic demo
auth.users)Dashboard
Orders
Customers
Products
Responsive layout
npm install
cp .env.example .env.local # then fill in your Supabase URL, publishable key and demo credentials
npm run dev
The app runs at http://localhost:5173. The Try the demo button only appears when VITE_DEMO_EMAIL and VITE_DEMO_PASSWORD are set.
Dashboard metrics and customer summaries are derived from the orders at runtime rather than pre-computed, so they stay consistent with the current date and with each other.
The functions that turn orders into dashboard data are pure and live in src/utils, separate from data fetching, so they can be unit-tested without mocking Supabase.
npm run test # watch mode
npm run test:run # single run
Tests sit next to the code they cover (*.test.ts), and src/test/factories.ts builds test orders with sensible defaults so each test only sets the fields it cares about.
The dashboard uses the same Supabase project as the companion Terre d'Oliva storefront, so both apps share one database: orders placed in the store show up here. The database schema lives in the storefront repository, as the single source of truth (see supabase/README.md).
src/
├── components/
│ ├── dashboard/ # Dashboard-specific widgets
│ ├── orders/ # Orders domain components (table, filters, row detail)
│ ├── products/ # Products table and new product sheet
│ ├── shared/ # Components shared across domains
│ ├── layout/ # Sidebar, mobile navbar, header
│ └── ui/ # shadcn/ui primitives
├── hooks/ # Custom hooks (auth)
├── lib/ # Supabase client and helpers
├── pages/ # Route-level pages
├── services/ # Data-fetching layer (Supabase queries)
├── test/ # Test helpers (data factories)
├── types/ # Shared TypeScript types
└── utils/ # Formatting, status helpers and derived-data builders (unit-tested)