Concise Description
No response
Description
Currently, the DevCard includes post-related tags, .e.g C# or #career. However, while the user might be interested in learning about C#, they might not know C#. It if appears on their DevCard, it's misleading.
Also, the DevCard can be generated only once and cannot be edited. If user updates their profile (avatar, name, skills) or wants to include/exclude skills, they cannot update the card.
Solution Proposed
Currently, the DevCard includes post-related tags, .e.g C# or #career. However, while the user might be interested in learning about C#, they might not know C#. It if appears on their DevCard, it's misleading.
I suggest:
(1) including only the User tools as tags to highlight their professional skills;
(2) including their post-related tags as "Interests" and their tools as "Skills" to keep both while distinguishing the tags clearly;
Also, the DevCard can be generated only once and cannot be edited. If user updates their profile (avatar, name, skills) or wants to include/exclude skills, they cannot update the card.
I suggest:
(1) adding an Edit option to enable user to personalize their card manually;
(2) adding a Regenerate option to enable user to regenerate their card based on their updated profile.
If these options are available under the paid plan, I suggesting adding an option to upgrade the plan to gain access to the DevCard personalization features.
Additional Context
Code of Conduct
Concise Description
No response
Description
Currently, the DevCard includes post-related tags, .e.g C# or #career. However, while the user might be interested in learning about C#, they might not know C#. It if appears on their DevCard, it's misleading.
Also, the DevCard can be generated only once and cannot be edited. If user updates their profile (avatar, name, skills) or wants to include/exclude skills, they cannot update the card.
Solution Proposed
Currently, the DevCard includes post-related tags, .e.g C# or #career. However, while the user might be interested in learning about C#, they might not know C#. It if appears on their DevCard, it's misleading.
I suggest:
(1) including only the User tools as tags to highlight their professional skills;
(2) including their post-related tags as "Interests" and their tools as "Skills" to keep both while distinguishing the tags clearly;
Also, the DevCard can be generated only once and cannot be edited. If user updates their profile (avatar, name, skills) or wants to include/exclude skills, they cannot update the card.
I suggest:
(1) adding an Edit option to enable user to personalize their card manually;
(2) adding a Regenerate option to enable user to regenerate their card based on their updated profile.
If these options are available under the paid plan, I suggesting adding an option to upgrade the plan to gain access to the DevCard personalization features.
Additional Context
Code of Conduct