UI redesign: newer, nicer look and feel (no logic or flow changes) #2

Open
opened 2026-11-22 00:05:46 +05:30 by ayush · 0 comments
Owner

Summary

The current UI (Laravel + Livewire + Flux 2 + Tailwind 4, zinc palette + Instrument Sans in resources/css/app.css) proves the concept works but is functional rather than pleasant. Redesign the look and layout — full creative control delegated to whoever implements this: reorganize, restyle, show things differently, pick the design direction.

Hard constraints

  1. No change to processing logic — how data is computed, validated, and persisted stays exactly as is (Livewire component boundaries may be reworked visually; behavior/methods stay semantically identical).
  2. No change to what is displayed — same data, same numbers, same states; different framing/layout/visual hierarchy is the whole point.
  3. No flow dropped — every existing page and flow must remain reachable and complete:
    • / Dashboard (Dashboard)
    • /transactions Transactions index + drawer + split modal + quick-add
    • /cards Card bills
    • /reimbursements
    • /recurring
    • /budget Budget builder
    • /rollover
    • /archives
    • Settings (profile, security/2FA, appearance, people, payment methods, credit cards, API tokens, initial setup)
    • Setup wizard (/setup)
  4. npm run build must succeed; Flux components may be replaced with plain Tailwind where Flux fights the new look.

Current surface map (for orientation)

  • Views: resources/views/livewire/ (dashboard, transactions, cardbills, reimbursements, recurring, budgetbuilder, rollover, archives, settings, setup-wizard, quick-add, app-nav, month-switcher)
  • Layout: resources/views/layouts/app.blade.php + resources/views/layouts/app/
  • Components: resources/views/components/ (app-logo, auth-header, desktop-user-menu, …)
  • Design tokens: resources/css/app.css — zinc scale, --color-accent, @theme block with font + colors
  • Routes: routes/web.php

Out of scope

  • The MCP proposed-transaction approval queue is a separate feature (its own issue) — the review UI it needs should follow whatever design language this issue settles on, but it is not required to land here.
## Summary The current UI (Laravel + Livewire + Flux 2 + Tailwind 4, zinc palette + Instrument Sans in `resources/css/app.css`) proves the concept works but is functional rather than pleasant. Redesign the look and layout — **full creative control delegated** to whoever implements this: reorganize, restyle, show things differently, pick the design direction. ## Hard constraints 1. **No change to processing logic** — how data is computed, validated, and persisted stays exactly as is (Livewire component boundaries may be reworked visually; behavior/methods stay semantically identical). 2. **No change to *what* is displayed** — same data, same numbers, same states; different framing/layout/visual hierarchy is the whole point. 3. **No flow dropped** — every existing page and flow must remain reachable and complete: - `/` Dashboard (`Dashboard`) - `/transactions` Transactions index + drawer + split modal + quick-add - `/cards` Card bills - `/reimbursements` - `/recurring` - `/budget` Budget builder - `/rollover` - `/archives` - Settings (profile, security/2FA, appearance, people, payment methods, credit cards, API tokens, initial setup) - Setup wizard (`/setup`) 4. `npm run build` must succeed; Flux components may be replaced with plain Tailwind where Flux fights the new look. ## Current surface map (for orientation) - Views: `resources/views/livewire/` (dashboard, transactions, cardbills, reimbursements, recurring, budgetbuilder, rollover, archives, settings, setup-wizard, quick-add, app-nav, month-switcher) - Layout: `resources/views/layouts/app.blade.php` + `resources/views/layouts/app/` - Components: `resources/views/components/` (app-logo, auth-header, desktop-user-menu, …) - Design tokens: `resources/css/app.css` — zinc scale, `--color-accent`, `@theme` block with font + colors - Routes: `routes/web.php` ## Out of scope - The MCP proposed-transaction approval queue is a separate feature (its own issue) — the review UI it needs should follow whatever design language this issue settles on, but it is not required to land here.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ayush/accounting#2
No description provided.