refactor(home): standardize "Install tracking" empty state using EmptyState component
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- next.js, react, typescript
- Domain
- frontend
Research direction
Update the install-tracking empty state in apps/dashboard/app/(main)/home/page.tsx by replacing the ad-hoc Card layout with the shared <EmptyState /> component from @databuddy/ui. Start by reading the showSetupPrompt logic and checking how the shared component is used elsewhere in the dashboard. The work is done when new or empty websites show the standardized install-tracking prompt and the existing prompt behavior remains intact; run the dashboard’s relevant checks afterward.
Written by the indexing model from the issue text.
Description
Description
Background
Currently, the homepage uses an ad-hoc implementation of a Card component to prompt users to install tracking on new or empty websites. This approach
creates a design inconsistency compared to other parts of the platform that utilize the shared component from @databuddy/ui.
The Problem
- Inconsistency: The custom card layout in the Home page does not align with the standardized empty state patterns used elsewhere in the dashboard.
- Maintenance: Hardcoding the layout in page.tsx makes it harder to update the visual style for setup prompts globally.
The Solution
Refactor the showSetupPrompt logic in apps/dashboard/app/(main)/home/page.tsx to utilize the shared @databuddy/ui component. This will:
- Ensure the setup prompt is visually consistent with other empty states in the application.
- Reduce code duplication.
- Improve the polish and professional feel of the dashboard's "first-run" experience.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 227
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 249
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databuddy-analytics/Databuddy
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
databuddy-analytics/Databuddy#1143 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
databuddy-analytics/Databuddy#1131 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
databuddy-analytics/Databuddy#1126 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
databuddy-analytics/Databuddy#1124 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
databuddy-analytics/Databuddy#1108 ·
Maintainers usually reply within 1 day
All issues in databuddy-analytics/Databuddy
Similar issues
-
docs(api): openapi.yaml still documents gif-tools optimize colors as 2-256 instead of 2, 4, 16, 256Openarea: backend documentation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
snapotter-hq/SnapOtter#2919 ·
Maintainers usually reply within 1 day
-
accepted :+1: bug db/redis
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
beekeeper-studio/beekeeper-studio#4882 · 1 comment ·
Maintainers usually reply within 1 day
-
ready-for-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
konflux-ci/konflux-ui#1630 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
ahmedkhaleel2004/gitdiagram#233 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
simkimsia/netlify-axi#19 ·
Maintainers usually reply within 1 day