[FEATURE] Generate Shareable Developer Portfolio Page

[vaishnavikhatri3]

Overview

samdev-pulse already provides an excellent way for developers to showcase their GitHub statistics through visually appealing profile cards. To further enhance its usefulness, I would like to propose a Shareable Developer Portfolio Page feature.

Motivation

Many students, open-source contributors, and developers rely on multiple platforms to showcase their work, achievements, coding profiles, and projects. Having a dedicated portfolio page generated automatically from existing data would provide a centralized and professional way to present their developer journey.

Proposed Feature

Allow users to generate a public portfolio page using their GitHub username.

Example:

https://samdev-pulse.vercel.app/u/{username}

The portfolio page could include:

• GitHub profile information
• Contribution statistics
• Streak statistics
• Language analytics
• Achievement trophies
• LeetCode, Codeforces, and CodeChef statistics
• Featured repositories
• Social links (LinkedIn, Portfolio, X/Twitter, etc.)
• Optional resume section

Benefits

• Creates a complete developer showcase with minimal setup.
• Helps students and professionals share their work more effectively.
• Eliminates the need for a separate portfolio website for many users.
• Expands samdev-pulse from a stats generator into a comprehensive developer branding platform.

Suggested Implementation

• Create a dynamic route such as /u/[username]
• Reuse existing GitHub statistics and theme infrastructure
• Ensure responsive design across devices
• Allow users to customize displayed sections

Additional Context

This feature would greatly improve the overall value of samdev-pulse and provide users with a professional, shareable portfolio generated directly from their existing developer profiles.

[vaishnavikhatri3]

Hi @SamXop123 ,
I really like this project and would love the opportunity to work on this feature under GSSoC'26.
If you find the idea suitable, could you kindly assign this issue to me? I'd be happy to work on it and contribute to the project.
/assign

[SamXop123]

@vaishnavikhatri3 i really like the idea but the current scope feels quite large and starts moving samdev-pulse beyond a README dashboard generator into a separate portfolio product.
this basically means two projects under one repo, which would be a pretty significant step in a new direction within samdev-pulse
and it might get new users confused with the profile page and dashboard rendering endpoints.
I would not close this issue and will keep this as a future-scope feature for now. The idea itself is genuinely good, but i dont feel like samdev-pulse is ready for this direction at the moment.
I hope you understand.

[vaishnavikhatri3]

Thank you for the detailed explanation, @SamXop123
I completely understand your perspective and I agree that the proposed feature would significantly expand the scope of samdev-pulse beyond its current focus as a README dashboard generator.
Thank you for considering the idea and keeping it open for potential future discussion. I appreciate the feedback and the insight into the project's direction.
I'm looking forward to contributing to features that align more closely with the current vision of samdev-pulse.

[SamXop123]

Thank you for the detailed explanation, @SamXop123 I completely understand your perspective and I agree that the proposed feature would significantly expand the scope of samdev-pulse beyond its current focus as a README dashboard generator. Thank you for considering the idea and keeping it open for potential future discussion. I appreciate the feedback and the insight into the project's direction. I'm looking forward to contributing to features that align more closely with the current vision of samdev-pulse.

@vaishnavikhatri3 well i have one issue in mind rn which i could create, lmk if you are interested

[vaishnavikhatri3]

Thank you @SamXop123 ! I'd definitely be interested. Looking forward to it .

[SamXop123]

Thank you @SamXop123 ! I'd definitely be interested. Looking forward to it .

just check and comment there, i've created the issue #174

[nishita1797-glitch]

/assign