Saving Projects

Projects are stored in Supabase through the editor’s Projects UI.

Requirements

• The app running (npm run dev or a deployed Vercel build)
• Supabase configured with the project schema
• A signed-in account (Sign in in the editor header)

Projects are private to your account until you publish them.

Plans

	Free	Pro
Saved projects	3	Unlimited
Publish to the gallery	Yes (needs a handle)	Yes
Embed (/embed/:id)	–	Yes

Upgrade to Pro from the account menu or when the project limit is reached. Billing is handled by PayPal subscriptions.

Public vs private

Each project has a Public/Private toggle in the Projects panel:

• Private — only you can open it. Its /p/:id page is not listed or embeddable.
• Public — anyone can view it on the gallery, play it at /p/:id, fork it, and like it.

To publish for the first time you need a handle (3–24 characters, letters/numbers/_/-). Your handle is required when you create an account — it is your public name across Eyedially. Existing accounts can set or change it any time from the account menu.

What Is Saved

Field	Contents
Name	Project title you enter
Files	All explorer files (name, code, isEntry)
Visibility	Public or Private
Author handle	Your handle, shown on public pages

Multi-file layouts are preserved. The active entry remains the file marked isEntry (usually main.js).

Workflow

1. Build your sketch in the editor
2. Open Projects
3. Save with a name (creates or updates)
4. Later: load from the list to restore files and resume editing

Loading replaces the current unsaved buffer - save first if you care about the open work.

Local vs production

Mode	Command	Notes
Dev	npm run dev	Vite :5173 + local API on :3001
Prod	npm run setup then deploy	Static frontend + docs, API via serverless routes

Tips

• Prefer descriptive names (double-spring-resonance) over test1
• After load, click Restart if you want a fresh state with the loaded code
• Docs are static files under /docs - they are not stored per project