Main Dashboard

[1nonlypiece]

Description
Design the primary dashboard that users see after logging in. This is the central hub showing vault overview, recent activity, quick actions, and key metrics at a glance.

Target Users

• Users managing their vaults
• Users checking vault status
• Users wanting quick access to common actions

Design Requirements

Must Include:

• Header/Navigation:
  • Disciplr logo (links to dashboard)
  • Main navigation (Dashboard, Vaults, Analytics, Settings)
  • Wallet connection status
  • Notifications bell with count badge
  • User profile dropdown
• Summary Cards:
  • Total locked capital (USDC amount)
  • Active vaults count
  • Pending milestones count
  • Completion rate percentage
• Quick Actions:
  • Create new vault (primary CTA)
  • View all vaults
  • Verify milestone (if user is a verifier)
• Vault Preview List:
  • Top 3-5 active vaults
  • Vault name/identifier
  • Amount locked
  • Progress indicator (time or milestone)
  • Status badge (Active, Pending, Completed)
  • Quick action (View details)
• Recent Activity Feed:
  • Vault created events
  • Milestone validated events
  • Funds released/redirected events
  • Timestamp for each activity
• Upcoming Deadlines:
  • Vaults approaching deadline
  • Days/hours remaining
  • Urgency indicator

Should Include:

• Performance chart (success rate over time)
• Welcome message for new users with onboarding CTA
• Behavioral insights snippet
• Quick filters for vault list
• Skeleton loading states
• Empty states for new users

Design Specifications

• Layout: Consider 12-column grid
• Card spacing: Consistent gutters (16-24px)
• Data refresh indicator
• Responsive: Stack cards on mobile, sidebar collapse

Deliverables

• Desktop dashboard layout
• Tablet layout
• Mobile layout
• Empty state (new user, no vaults)
• Loading/skeleton state
• Interactive prototype with navigation

Designer Notes

• This is the "home base"—make it feel organized and calm
• Prioritize actionable information over decoration
• Financial data should be scannable at a glance
• Consider data density—users may have many vaults