# Dasher-Inspired Admin Dashboard Reference

Use this as visual and interaction inspiration for business management web apps. Do not copy Dasher source code, assets, logos, or exact content. Recreate a similar professional admin-dashboard feel with Tailwind CSS, Font Awesome, and static in-memory JavaScript demo behavior.

## Layout
- Prefer an admin workspace layout for management systems: fixed left sidebar by default, top header, and main content area.
- Sidebar should fit the viewport: `fixed left-0 top-0 bottom-0 h-screen`, with clear icon navigation and active item state.
- If the BA brief explicitly requests a top-only navigation, use a fixed/sticky top nav that fits `top-0 left-0 right-0 w-full z-50`.
- Main content must have enough margin or padding so it is never hidden under the sidebar or top nav.
- Use dashboard pages with cards, charts/stat panels, recent activity, task/order/customer lists, and management tables when the brief describes operational workflows.

## Visual Style
- Clean SaaS admin UI with white cards, soft gray page background, graphite text, and a restrained accent color chosen from the BA brief.
- Rounded cards and controls, subtle shadows, generous spacing, and clear section hierarchy.
- Use Font Awesome icons in sidebar navigation, KPI cards, action buttons, empty states, and form labels.
- Use small badges for statuses such as Active, Pending, Completed, Overdue, Paid, Draft, or In Progress.
- Use responsive tables that stay usable on mobile through horizontal scrolling or stacked cards.

## Business App Components
- Include realistic dashboard modules when relevant: KPI cards, line/bar chart placeholders, progress widgets, tables, calendars, workflow boards, notifications, and activity feeds.
- CRUD screens should feel complete: toolbar, search input, filter dropdown, add button, table/list, row actions, and pagination-like UI if useful.
- Forms should use polished modal dialogs with clear labels, validation-friendly inputs, and primary/secondary actions.
- Avoid purely decorative landing-page sections for operational systems unless the BA brief specifically requests a marketing website.

## Interaction Rules
- Core workflow buttons must work with fake in-memory JavaScript data in the static HTML.
- Add/Create opens a modal, submit adds a visible row/card/item immediately.
- Edit opens a modal pre-filled with the selected item, save updates the visible row/card/item immediately.
- Delete opens a confirmation modal, confirm removes the visible row/card/item immediately.
- Search/filter/status controls should update the visible fake data when present.
- Show a small toast or status message after successful add/edit/delete.
