Xtrable
How it fits together
Nanoesis ships as one package: the compiler, the editor UI, and the storage adapters. You wire it up with a single call, createEditor, and mount it in any web server. The same code runs whether your files live on your laptop or in cloud storage; only the storage you hand it changes.
1. Bring some storage
Nanoesis reads and writes through a Storage: a plain key-value store with three methods. It never lists or scans (it keeps its own index), so a flat store like S3 or Azure Blob is all it needs. You give it two: one for your editable files, one for the published website. For local files or Azure Blob, use the ready-made folderStorage and azureStorage and implement nothing.
2. Wire the editor
Hand createEditor your two storages and a login, and it returns a ready editor. It builds everything behind the scenes, the content index, the publish step, the reconcile, so you never touch the internals. Use devNoAuth while developing locally, then swap in a real login before you go live.
3. Serve it
An editor is two routes in your web server: send anything under /api/ to editor.handleApi, and serve everything else with serveEditorAsset, which returns the editor UI. That is the entire server. Open it in a browser and you have a working editor.
4. Publish
Authors click Publish in the editor; under the hood that calls editor.publish(). It validates the whole site first, and only if everything is sound does it build and write the static files to your website storage. A broken publish tells you what to fix and never touches the live site.
Optional extras
Everything beyond the basics is opt-in. Add responsive images with the sharp encoder, clear your CDN after each publish with a purge service, or switch on real accounts and roles with the local-jwt login. Leave any of them out and nanoesis simply skips that step.
That is the whole setup
Two storages, a login, two routes. No framework to learn and no build tool to configure. Point the storages wherever your files and site should live, and the same editor and compiler do the rest. For a step-by-step host, see the integration guides.