Publish & share
What you build is yours — OIOXO gives you every way out of the browser, and one way to put it on the web.
Download a .zip
One click in the project sidebar (or the command palette) downloads the whole project as a zip. Works for every project type.
Download as one .html
For static sites, OIOXO can inline the CSS and JavaScript into a single self-contained .html file — email it, drop it anywhere, double click and it runs.
Publish to the web (GitHub Pages)
- Click “Publish to the web…” in the project sidebar.
- Paste a fine-grained GitHub token with Pages write access (it stays in your browser — see Working with GitHub).
- OIOXO builds the static site, pushes it to a
gh-pagesbranch, and hands you the live URL.
Re-publish any time; the same flow updates the site.
Save to a local folder
On Chromium browsers, “Save to folder…” writes the project straight to a folder on your disk — from there it’s a normal local project you can also reopen on the Files surface.
Share by code — nothing leaves your device
“Share…” packs your whole project — every file — into a single share code (and a matching /oioxo?share=… link). The code is the project: it’s your files compressed and encoded, with no server, no upload, and no peer connection in between. Copy the link into any chat, email, or note.
Whoever opens the link — or pastes the code into “Got a share code?” on the OIOXO landing page — gets an exact copy of the project, decoded right in their own browser. It’s a portable snapshot, not a live session: their edits and yours are independent from that point on. To collaborate continuously, push to GitHub and let each side open the repo.
Projects on the Build surface live in browser memory and are auto-saved as recent sessions — but a zip or a saved folder is the durable copy. Export anything you care about.