Skip to content

Tailwind #60 — Admin tools

FieldValue
GitLabsourcecontrollers/safecall#60
Parent#52
Roadmaptailwind-roadmap.md
Depends on#59 (closed)
Workflowclosed

Goal

Migrate standalone admin tool pages (own HTML entry shells + TS) from Bulma to Tailwind catalog + utilities.

Tools in scope

ToolPath
Gateway ID / alive scanweb/src/admin/tools/gateway-id/
Gateway configweb/src/admin/tools/gateway-config/
Beacon configweb/src/admin/tools/beacon-config/
Placement plannerweb/src/admin/tools/placement-planner/
Debug deviceweb/src/admin/tools/debug-device/

Design principles

  1. Tools may have denser custom CSS; still prefer tokens over Bulma hooks.
  2. Shared helpers from #54 for toasts/modals/buttons.
  3. Placement planner sidebar: port dark shell to tokens (known Bulma fight area).

Acceptance criteria

  • [x] Each tool’s .html + .ts Bulma classes migrated
  • [x] Tool pages load via existing routes/embeds
  • [x] Smoke: open each tool shell; critical control visible (need not run full hardware flows)

Implementation notes

These pages are often less template-shared than admin CRUD. Watch for duplicated Bulma form patterns; reuse catalog.

Ensure CSS build includes tool HTML class scanning if Tailwind content paths must list admin/tools/**.

Out of scope

WorkIssue
Dashboard / translations / bug-tracker / interface-templates#61
Drop Bulma#62

Key paths

  • web/src/admin/tools/**
  • Tailwind content config / app.css @source paths (if used)

Verification

  1. Web typecheck / build.
  2. Smoke navigate to each tool URL.
  3. Grep web/src/admin/tools for Bulma-only leftovers → 0.

Done when / handoff

  1. Operator verifies → commit with Closes #60 → push gitlab.
  2. Next: #61 admin remaining.