From overview to activity

# Design reference: OpenPanel — Analytics overview
Source: https://demo.openpanel.dev/demo/shoey
Swipefile reference: https://swipefile.design/ref/openpanel-dashboard/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Analytics overview
- nav: Date range, aggregation, filters, and workspace selection remain above the analysis.
- layout: A persistent left rail supports a metrics strip, wide time-series chart, and paired data tables.
- density: Headline metrics are spacious; supporting chart labels and rankings use denser alignment.
- color: White and pale gray surfaces, blue charts, and restrained green or red change indicators.
- typography: Tabular numeric values, small uppercase metric labels, and clear section labels support dense comparison.
- pattern: Arrange analytics from headline metrics to trend context and then detailed rankings.
- states: Populated public demo overview with a selected date range and visible traffic breakdowns.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Arrange analytics from headline metrics to trend context and then detailed rankings.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

# Design reference: OpenPanel — Event explorer
Source: https://demo.openpanel.dev/demo/shoey/events/events
Swipefile reference: https://swipefile.design/ref/openpanel-events/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Event explorer
- nav: Events, conversions, and stats tabs share a local header with listening status, date range, and filters.
- layout: A wide table fills the workspace under tabs and filter controls beside a persistent navigation rail.
- density: Headline metrics are spacious; supporting chart labels and rankings use denser alignment.
- color: Neutral surfaces, thin row dividers, pastel event-type icons, and a green listening indicator.
- typography: Small column headings and aligned timestamps contrast with stronger event names.
- pattern: Make operational event data scannable through stable columns, concise labels, and visible stream status.
- states: Populated public demo event table with anonymous sample profiles and recent activity.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Make operational event data scannable through stable columns, concise labels, and visible stream status.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

# Design reference: Resend — Service status
Source: https://resend-status.com/
Swipefile reference: https://swipefile.design/ref/resend-status/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Service status
- nav: Report and subscription actions sit in the top bar.
- layout: A constrained central column stacks overall status, service rows, and a history action.
- density: Headline metrics are spacious; supporting chart labels and rankings use denser alignment.
- color: Charcoal surfaces, green operational indicators, and occasional warm historical incident markers.
- typography: Bright service labels and small muted percentages make repeated uptime rows easy to compare.
- pattern: Communicate system health with a readable overall summary and drill-down service history.
- states: Capture-time operational summary and per-service uptime bars; conditions may change.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Communicate system health with a readable overall summary and drill-down service history.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.