# Mira Site Editor 0.5.0

Your site. Your words. Your control.

## Open it

Extract the entire ZIP to a folder you can write to, then double-click **Mira-Site-Editor.exe**. Keep the runtime, app, and node_modules folders beside it. Windows 10/11 x64 and an up-to-date browser are required. No separate Node, Git, Codex, administrator access, or installer is needed. This initial community release is unsigned; we do not advise bypassing a security block. If your organization blocks it, ask its administrator or use the source with approved tooling.

## Start with something real

**Start a site** makes an editable starter in Documents/Mira Websites, or downloads your GitHub repository there. **Manage repositories** adds a Git website already on your PC. Set the website folder to public, docs, or . depending on where its HTML lives. Preview build scripts are optional and execute local code: configure them only for a repository you trust.

Click words to select them. Choose **Edit words** to type. Images, colors, spacing, fonts, transparent backgrounds, sections, undo/redo, layers and groups are available. **Compare sizes** checks desktop, tablet and phone layouts. **Test website** runs your site's JavaScript in an isolated preview. Server-backed forms require their real backend; a preview does not create one.

**Save page** writes to your local website and makes a backup. It does not publish. Protected drafts can be reviewed after reopening. Do not restore an old draft blindly after GitHub/source changes; inspect it first.

## Put it online

For an existing site: Get latest from GitHub → edit → Save page → Publish website. Publication shows the files before pushing. GitHub changes go to your configured Git branch. Your host must already deploy from that branch; entering a live URL does not connect a host. Release verification expects the host to serve public/.well-known/mira-deployment.txt unchanged at /.well-known/mira-deployment.txt. Without this, GitHub can be updated successfully while live verification remains unavailable.

For a starter: create an empty repo in your own GitHub account. In **Manage repositories → GitHub & commit details**, enter its URL, your commit name, and your GitHub private noreply email if desired. Use Publish website. Git Credential Manager handles browser sign-in when GitHub needs authentication; the editor does not ask for or store your GitHub password. The email you select appears in Git commits. Then connect the repo to your chosen host with public as its website folder. GitHub Pages, for example, needs a workflow that deploys public. Hosting and GitHub permissions are yours to manage.

## What this release supports

HTML/CSS/JavaScript websites in Git repositories. Custom Node preview generators can be configured, but their dependencies are not installed automatically. React/Vue apps, WordPress, server-side frameworks and visual editing of private CMS data are not plug-and-play in this release. CSS rules, hidden elements and runtime-generated content sometimes need source-level edits. This is a community preview, not a promise that every website can be edited perfectly.

## Where things live

Editor configuration, backups, font previews and draft recovery: %LOCALAPPDATA%/MiraSiteEditor. Created/cloned websites: Documents/Mira Websites. Existing repos stay in their chosen folders. Updating the extracted app does not replace either location. Export website ZIP is available in Workspace → Releases; private editor settings and credentials are excluded.

To stop: close all editor tabs and allow the idle shutdown to finish. To remove: close it, delete the extracted application folder. Your websites and backups remain. No telemetry is added by the editor. Website scripts may make their own network requests in Test website; GitHub and release checks use the network when requested. The server binds only to 127.0.0.1.

Support: https://thisisbeside.org/support#issues

Third-party licenses and runtime/source links are included in THIRD-PARTY-NOTICES.md and the runtime folders. The editor application and starter template are free to use under the included LICENSE; bundled components retain their own licenses.