Eltes Studio

Eltes / Studio checking… offline mode

Chat

Workspace

.studio/ · files are served at /preview/

Pick a file to start Choose something in the workspace, or create another.html — every HTML file can be previewed.

no file open Ln 1, Col 1

reloading

Terminal ~/studio ↵ run · ↑ history · Ctrl+C stop

~/studio $

Effects, generated as code

Pick one and Studio writes a complete, dependency-free HTML page into effects/ and previews it. The code is yours to edit — new in v3.10.

How these work

Build a website, step by step

Five real actions in this workspace — no mock screens. Progress saves in this browser.

1
Create the project files Writes index.html, about.html, styles.css, a package.json and a build.mjs into the workspace, then opens the home page.
2
Start the terminal Opens the real shell and runs npm run build, which copies the site into dist/ — streamed while it runs.
3
Add another page Opens the new-file box. Type pricing.html — every HTML file can be previewed.
4
Preview it live Loads the page in the right pane from /preview/, with its CSS and scripts intact.
5
Open the page on its own Opens the preview in a new browser tab, exactly like a deployed site.

Tip: Ctrl/⌘+S saves, and the preview reloads after saves and after build commands.

Read the full workflow

A real workspace next to the app: edit files, preview them live, and run commands in a shell in that folder.

Any HTML file previews. Click an .html file and the right pane follows it, served from /preview/ — relative CSS, JS and images all resolve.
Terminal. ls, git, npm install, npm run build — output streams as it runs. Preview reloads when files change.
Shortcuts. ⌘/Ctrl+S save · Tab indent · ⌘/Ctrl+P quick switch.
No backend? The editor still works and builds a preview in the browser; the terminal needs npm start.
What’s new? The release notes show the rebuilt galaxy sky, the Obsidian black chat and the effects library with screenshots.

The terminal runs on the machine hosting npm start. It is a development tool — keep it on a trusted network. The deployed static site never exposes it.