RAGBAZ
Ctrl+Alt+T Ctrl+Alt+F
Context Documentation
Language ensves
All guides /docs

Omniland Editor Guide

Reference guide for running Omniland at omniland.ragbaz.xyz with predictable editor behavior and R2-backed assets.

Audience: Omniland operators, editors, and developers

Back to docs

What requires login

Authenticated admin users can access contacts CRUD, R2 image library/object APIs, Send Email, and R2-backed Save/Delete for named documents.

Admin auth uses signed cookie sessions with comma-separated ADMIN_USERNAME and ADMIN_PASSWORD pairs.

What works while logged out

Users can test the editor UI and use Export + Source, including copy/download source and HTML exports.

Save actions are muted with a Login required tooltip, while loading template examples remains available.

Startup assets and templates

Startup assets are namespaced with R2_STARTUP_ASSETS_KEY=omniland-bootstrap/startup-assets.json.

The editor keeps startup assets in localStorage, and now replaces cached assets only when online R2 data is newer by version/updatedAt.

R2 named page storage

Named pages are saved in R2 under the configured R2_PAGES_PREFIX (currently omniland-).

Save requires a file name; slug is derived from that name and persisted as JSON in R2.

Deployment variables

Required secrets: AUTH_SECRET, ADMIN_USERNAME, ADMIN_PASSWORD, RESEND_API_KEY, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY.

Required vars/bindings: R2_BUCKET, DB, S3_BUCKET_NAME, CF_R2_PUBLIC_URL, CF_R2_ENDPOINT, R2_PAGES_PREFIX, R2_STARTUP_ASSETS_KEY, RESEND_FROM.

Copyable command

npx wrangler r2 object put sofiacerne/omniland-bootstrap/startup-assets.json --remote --file ./startup-assets.json

Run this command in your terminal.

Mermaid diagram
flowchart LR U[Editor user] --> M[Head icon menu] M --> D[Project Docs] U --> E[Export and Source always] U --> L[Login] L --> A[Admin session cookie] A --> P[R2 pages + images + contacts + email APIs]

Read next