The web editor

Open your creator studio #

1. Sign in with GitHub and create a site in your dashboard.
2. Open that site, then choose Open website editor.
3. 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. JSON pages show a static preview beside the source. 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.

Load template replaces the files in the current editing session after confirmation. Saved versions are preserved. Undo last file operation can recover the last added/removed-file or template-replacement operation. It is not a complete edit history.

Format JSON 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. Tab moves keyboard focus so keyboard users can leave the code field.

Validate and preview #

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

The web editor does not execute or syntax-check Lua. app.lua may override the page shown in a JSON preview. Test dynamic routes in Lantern; 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. Choose Save draft. Your signed-in owner session is used; no upload key is needed.
2. Choose Review saved draft to inspect the saved files.
3. Return to the site dashboard’s Releases section and publish the intended version.
4. Open 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 package 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 package also works for incomplete source so you can keep a backup before correcting validation errors. Downloading does not validate or publish the package.