OpsHub

Context

A self-imposed brief: design and build the frontend of a credible small-business operations dashboard end-to-end, with the layout, navigation, and component architecture decisions made deliberately rather than improvised. The goal was a clean piece of UI work I could point clients at when the conversation turns to "what would the dashboard look like".

Approach

A single Next.js 14 (App Router) app with TypeScript and Tailwind, structured so that each domain — leads, orders, support tickets, automations, settings — is its own route group with its own composable building blocks. KPI cards, activity feeds, filterable tables, and detail panes share a small primitive layer rather than diverging per page.

The API routes intentionally serve sample data: this project is a UI showcase, not a backend. Anywhere data would normally come from a real system, a mock provider returns a representative payload so the screens render in a realistic state.

Outcome

A dashboard frontend that can be cloned, rebranded, and wired to a real backend without architectural changes. It also serves as a working answer to "what does production-quality UI look like for this kind of internal tool" without leaning on a generic component-library demo.