Skip to content

Dashboard Page Editor

Jump to bottom
Dominic edited this page Jul 10, 2026 · 1 revision

Dashboard Page Editor

Add or edit dashboard views safely with a beta → live pipeline. Broken drafts never reach the live dashboard unless you promote them.

Pipeline

Stage Where What happens
Beta draft public/beta/<file> All edits start in the beta copy. The beta dashboard is served at /beta/ for safe preview.
Preview http://localhost:3200/beta/ Open the beta URL in a browser (or ask Atlas to inspect it) before promoting anything to live.
Promote Add Page drawer → Promote Copies the beta file to the live public/ directory. The current live file is backed up first to data/dashboard-backups/.
Revert Add Page drawer → Revert If the live dashboard breaks, restore the most recent backup immediately. Then delete the bad beta draft.

Files you can edit

  • public/index.html — add new <section class="view" id="view-NAME"> blocks and matching rail buttons in the left nav.
  • public/js/app.js — add view rendering functions, switchView wiring, API calls, and event handlers for the new page.
  • public/css/style.css — add styles for the new view and components. Keep existing CSS intact.

How to ask Warden

Ask Warden to make the change. It will follow the beta pipeline automatically:

Add a new dashboard page called "Logs" with a view that lists the last
50 chat messages. Add a rail button below Activity, a section with
id="view-logs", and a render function in app.js that calls /api/messages.

Warden should: copy public/index.html → public/beta/index.html and add the view + rail button; copy public/js/app.js → public/beta/js/app.js and add the render logic; then tell you to preview at /beta/ before promoting.

Manual editing

  • Click the Add Page button at the bottom of the left rail.
  • Click Edit beta next to the file you want to change.
  • Save the draft, preview at /beta/, then click Promote.

Never edit public/index.html, public/js/app.js, or public/css/style.css directly for a new page — always go through beta.

Rules

  • Preview before promote. A broken beta promoted to live breaks the live dashboard for everyone.
  • One page per beta cycle. Keep beta changes focused so reverts are clean.
  • Backups are automatic. Every promotion saves the old live file. Revert restores the most recent backup.
  • Don't delete backups. They live in data/dashboard-backups/ and are your safety net.
  • If live breaks: revert immediately, then tell Warden what went wrong and iterate in beta.

Home

Clone this wiki locally