The dashboard is built from approved components and a planned sitemap, server-rendered with Go templates, Oat and htmx #2029

Open
opened 2026-11-16 08:26:02 +00:00 by sam · 1 comment
Owner

The binary serves ui/src/archie/, a thin set of pages written from scratch. It lost the old dashboard's design and reads like a generated document. Generating the dashboard from the OpenAPI document isn't the answer either; that was only ever a one-off stopgap.

Build it deliberately, in this order, each step approved by the maintainer before the next:

  1. Components. A small set of Go template components, server-rendered with Oat and htmx 4 (vendored at pinned versions, embedded, no build step, no CDN). Each maps to a shape the API has: a collection, an item, an editable setting, a write-only secret, a confirmed action, a live stream (hx-sse), the run trail, the workflow editor. Each carries the old dashboard's design (ui/src/components, ui/src/workflows), not its code, and is approved before any page uses it.
  2. Sitemap. Which pages exist, what question each answers, and which components it uses. It starts from what a person needs (what is waiting on me, what Archie handled and its verdict, how far each action class is trusted), not from the API's tags.
  3. Pages, composed only from approved components.
  4. Review against the OpenAPI document (#2028). Every operation has a home on some page or is deliberately left off, with the reason. A planned review, not tooling.

Carried from the earlier plan:

  • Forms post with htmx. The handler decodes against the operation's schema and calls it in-process with the signed-in person's session, so the dashboard can do nothing the API refuses.
  • Write-only fields are never echoed back.
  • Mutations pass http.CrossOriginProtection.
  • Pages are served under a strict content security policy (hx-csp).
  • Until identity lands (#2017), signing in exchanges the bootstrap admin token for a session cookie.

ui/ stays in the tree until each page's replacement lands. The binary stops embedding the Vue build when the last one does.

Done when: the components and sitemap are approved, every page in the sitemap is served, the review shows every operation reachable or deliberately omitted, and the bootstrap admin can configure a source, a trigger and a connector, then follow a run's trail live, end to end.

The binary serves `ui/src/archie/`, a thin set of pages written from scratch. It lost the old dashboard's design and reads like a generated document. Generating the dashboard from the OpenAPI document isn't the answer either; that was only ever a one-off stopgap. Build it deliberately, in this order, each step approved by the maintainer before the next: 1. **Components.** A small set of Go template components, server-rendered with Oat and htmx 4 (vendored at pinned versions, embedded, no build step, no CDN). Each maps to a shape the API has: a collection, an item, an editable setting, a write-only secret, a confirmed action, a live stream (`hx-sse`), the run trail, the workflow editor. Each carries the old dashboard's design (`ui/src/components`, `ui/src/workflows`), not its code, and is approved before any page uses it. 2. **Sitemap.** Which pages exist, what question each answers, and which components it uses. It starts from what a person needs (what is waiting on me, what Archie handled and its verdict, how far each action class is trusted), not from the API's tags. 3. **Pages**, composed only from approved components. 4. **Review against the OpenAPI document (#2028).** Every operation has a home on some page or is deliberately left off, with the reason. A planned review, not tooling. Carried from the earlier plan: - Forms post with htmx. The handler decodes against the operation's schema and calls it in-process with the signed-in person's session, so the dashboard can do nothing the API refuses. - Write-only fields are never echoed back. - Mutations pass `http.CrossOriginProtection`. - Pages are served under a strict content security policy (`hx-csp`). - Until identity lands (#2017), signing in exchanges the bootstrap admin token for a session cookie. `ui/` stays in the tree until each page's replacement lands. The binary stops embedding the Vue build when the last one does. Done when: the components and sitemap are approved, every page in the sitemap is served, the review shows every operation reachable or deliberately omitted, and the bootstrap admin can configure a source, a trigger and a connector, then follow a run's trail live, end to end.
sam added the featurehigh labels 2026-11-16 08:26:02 +00:00
sam added a new dependency 2026-11-16 08:26:11 +00:00
sam added a new dependency 2026-11-16 08:26:12 +00:00
sam added a new dependency 2026-11-16 08:26:13 +00:00
sam changed title from The default dashboard is generated from the OpenAPI document, server-rendered with Go templates and Oat to The default dashboard is generated from the OpenAPI document, server-rendered with Go templates, Oat and htmx 2026-11-16 08:35:37 +00:00
sam changed title from The default dashboard is generated from the OpenAPI document, server-rendered with Go templates, Oat and htmx to The dashboard is built from approved components and a planned sitemap, server-rendered with Go templates, Oat and htmx 2026-11-17 08:23:57 +00:00
Author
Owner

Dropped by the maintainer: the Vue SPA in ui/ is the dashboard and is rewired onto the module APIs (#2023), sign-in first (#2017). MIGRATION.md updated.

Dropped by the maintainer: the Vue SPA in ui/ is the dashboard and is rewired onto the module APIs (#2023), sign-in first (#2017). MIGRATION.md updated.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#2029