The web editor.

Open your creator studio.

1. 1Sign in with your thultz.dev account (GitHub) and choose New site in your dashboard.
2. 2Describe the site and let the AI build a first draft, or start from a template or a blank page.
3. 3Later, open the site and choose Open editor. An existing site loads its latest saved version, which may be newer than its live publication. A new site starts with index.json.

Edit files and start from a template.

Select a file in the file list and edit its source. The editor highlights Lua and JSON and completes page component types and properties, ctx fields and page builders. JSON pages show a terminal preview beside the source; pick any page in the preview menu. Add a page such as about.json or guides/start.json, or add app.lua for server-side logic. New files contain working starter content.

Start from a template replaces the files in the current editing session after confirmation. Saved versions are preserved. Undo last file change can recover the last added or removed file, template replacement, format or AI change. Each open file also keeps its own undo history while you edit.

Format reformats a valid JSON file. The editor is a source editor, not a visual drag-and-drop page builder. On narrow screens its panels stack.

Build with AI.

The Build with AI panel writes and changes pages and app.lua for you. Describe a change and press Generate, press Fix to send a validation error, or Explain to have the site described. The AI sees your current files and the site address, runs test requests against its own answer, and shows the explanation, whether it passed the checks, each test request and the files it would change.

Apply to editor merges the answer into the editor: new files are added, changed files replaced and the rest kept. Nothing is saved or published until you save a draft and publish it yourself. Discard throws the answer away.

In app.lua, AI suggestions show grey ghost text at the end of a line after you stop typing. Tab accepts it and Esc dismisses it. Turn suggestions on or off in the editor; the choice is remembered in this browser.

Validate and preview.

Validate checks package paths, size limits and page JSON. The terminal preview updates as JSON becomes valid. Links and forms in that preview are descriptive, not interactive.

The editor does not execute Lua. app.lua may override the page shown in a JSON preview. Test dynamic routes in Lantern, or let the AI builder run its test requests; use the documented complete handler examples and the local Validate site action when available.

Save a draft, then publish.

Saving never replaces the live publication. Each successful save creates an immutable version. The current limit is 100 versions per site. Account upload restrictions, bans and site disabling also apply to editor saves.

1. 1Choose Save draft. Your signed-in owner session is used; no upload key is needed.
2. 2Choose Review and publish to see every page as visitors will, and the app.lua source.
3. 3Publish the version there, or later from the site dashboard's Releases.
4. 4Open hub://your-site/ in Lantern and test it.

Unsaved work and conflicts.

Unsaved changes live in this browser tab. There is no automatic save or cross-device synchronization. Save deliberately or use Download to keep a local copy. Navigation warns about unsaved changes, but a browser crash can still lose them.

If another tab or an upload creates a newer version, saving from an older editor is blocked. Download your work, reload the latest draft, and merge your changes. This prevents silently replacing someone’s newer editing base.

Download also works for incomplete source so you can keep a backup before correcting validation errors. Downloading does not validate or publish the package.