尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
A multi-client music management web app. Manage songs, tour, content scheduling, royalties, banking splits, and works catalog — all in one place.
The most important file: src/lib/store.ts — every button press calls a function defined there.
Step 1 — Install Node.js (one-time setup)
Download from https://nodejs.org (click the "LTS" version).
Verify it worked — open Terminal (Mac) or Command Prompt (Windows):
You should see something like v20.x.x.
Step 2 — Open the project folder in Terminal
Tip: On Mac, open Terminal and drag the studio folder into it to auto-fill the path.檢視完整 README ↗A multi-client music management web app. Manage songs, tour, content scheduling, royalties, banking splits, and works catalog — all in one place.
studio/
├── src/
│ ├── app/ ← Next.js pages (the URLs)
│ ├── components/
│ │ ├── StudioApp.tsx ← Root component — wires everything together
│ │ ├── layout/ ← Header, subnav
│ │ ├── dashboard/ ← Client roster + add/edit modals
│ │ ├── songs/ ← Track list, stage advancement
│ │ ├── tour/ ← Shows, venue details
│ │ ├── content/ ← Calendar, Studio view, Lab
│ │ └── business/ ← Royalties, Banking, Catalog
│ ├── lib/
│ │ ├── store.ts ← ALL app state + actions live here (Zustand)
│ │ ├── demo-data.ts ← Starting demo data (3 artists)
│ │ ├── utils.ts ← Shared helpers (fmt, initials, calendar, etc.)
│ │ └── cn.ts ← Tiny classname helper
│ └── types/
│ └── index.ts ← TypeScript types for every data structure
└── README.md
The most important file: src/lib/store.ts — every button press calls a function defined there.
Download from https://nodejs.org (click the "LTS" version).
Verify it worked — open Terminal (Mac) or Command Prompt (Windows):
node --version
You should see something like v20.x.x.
cd /path/to/studio
Tip: On Mac, open Terminal and drag the studio folder into it to auto-fill the path.
npm install
Downloads all the code libraries. Takes ~30 seconds.
npm run dev
Open your browser to: http://localhost:3000
You'll see the Mgmt Path dashboard with 3 demo clients. Data saves automatically in your browser.
That's it. You'll get a live URL like studio-yourname.vercel.app in about 2 minutes.
Every time you push code changes to GitHub, Vercel auto-deploys.
Each customer gets their own login and their own data.
npm install @supabase/supabase-js
localStorage calls in store.ts with Supabase database queriessrc/app/login/page.tsxCost: Free up to 500MB + 50,000 users
Customers pay monthly, you get paid automatically.
npm install stripe @stripe/stripe-js
/pricing page with your plans/api/checkout route that starts a Stripe checkoutSuggested pricing:
| Plan | Price/mo | Clients |
|---|---|---|
| Solo | $49 | Up to 5 |
| Agency | $99 | Up to 20 |
| Label | $199 | Unlimited |
usestudio.io)1. Define the data in src/types/index.ts
2. Add actions in src/lib/store.ts:
addNote: (trackId: string, text: string) => {
const { data, clientId } = get()
// update data immutably, then:
saveData(updated)
set({ data: updated })
}
3. Build the UI component in the relevant folder under src/components/
4. Wire it in src/components/StudioApp.tsx
| Layer | Technology | Why |
|---|---|---|
| Framework | Next.js 14 | Industry standard React framework |
| Language | TypeScript | Catches bugs before they ship |
| Styling | Tailwind v4 | Utility-first, easy to customize |
| State | Zustand | Simple global state, zero boilerplate |
| Database* | Supabase | Postgres + Auth + storage, free tier |
| Payments* | Stripe | Industry standard subscriptions |
| Hosting | Vercel | One-click deploy, auto-scales |
*Not yet integrated — see Phase 2 & 3 above.
| Problem | Fix |
|---|---|
command not found: npm | Install Node.js from nodejs.org |
Module not found error | Run npm install again |
| Blank page in browser | Press F12, check the Console tab for red errors |
| Changes not showing | Make sure npm run dev is still running |