[FEAT] Add "Why DevTrack?" Section to the Landing Page
Problem Statement
The current landing page showcases DevTrack's features but does not clearly communicate its unique value proposition compared to GitHub's built-in analytics and contribution tracking tools. As a result, new visitors may find it difficult to quickly understand the benefits of using DevTrack and how it enhances their developer experience.
I would like to work on this issue under GSSoC.
Proposed Solution
Add a dedicated "Why DevTrack?" section to the landing page that highlights the platform's key advantages over GitHub's native analytics. This can be implemented using a comparison table or feature cards showcasing capabilities such as:
- Goal Tracking
- AI Weekly Insights
- Year Wrapped
- Multi-Account Support
- Self-Hosting
The section should be visually appealing, responsive, and aligned with the existing design system.
Feature Area
Landing Page
Alternatives Considered
The benefits could be incorporated into existing feature sections. However, a dedicated section would provide a clearer and more focused explanation of DevTrack's unique value proposition.
Acceptance Criteria
Additional Context
A comparison table or feature-card layout can be used to help users quickly understand how DevTrack differs from GitHub and why they should use it.
[FEAT] Add "Why DevTrack?" Section to the Landing Page
Problem Statement
The current landing page showcases DevTrack's features but does not clearly communicate its unique value proposition compared to GitHub's built-in analytics and contribution tracking tools. As a result, new visitors may find it difficult to quickly understand the benefits of using DevTrack and how it enhances their developer experience.
I would like to work on this issue under GSSoC.
Proposed Solution
Add a dedicated "Why DevTrack?" section to the landing page that highlights the platform's key advantages over GitHub's native analytics. This can be implemented using a comparison table or feature cards showcasing capabilities such as:
The section should be visually appealing, responsive, and aligned with the existing design system.
Feature Area
Landing Page
Alternatives Considered
The benefits could be incorporated into existing feature sections. However, a dedicated section would provide a clearer and more focused explanation of DevTrack's unique value proposition.
Acceptance Criteria
Additional Context
A comparison table or feature-card layout can be used to help users quickly understand how DevTrack differs from GitHub and why they should use it.