🐞 Description

I wanted to press the Add your Nuxter card on Github button and display the Nuxters Card for GitHub.
However, the image does not appear and the loading never ends.

🔗 Linked Issue

related #65 .

or module-author?

Based on the initial draft I have done for the new nuxt.com, but will take some time and it's faster to work as a small project here for recognising our contributors. Will draft it here with @SarahM19

This is what we have done with Alex on the new nuxt.com:

Homepage

Header with logo "Nuxters" + nuxt.com + Login with GitHub (or user profile dropdown + profile link and logout)

Title: Discover the Nuxters
Description: The development of Nuxt and its ecosystem is led by an international team. From contributors to developer advocates, the community is made of members with different horizons and skills. We are happy to see new members every day and encourage anyone to join us and help in many ways: answering questions, giving a talk, creating modules and contributing to the core.
CTA: Sign-in with GitHub to discover your Nuxter Card

Leaderboard with all the nuxters.

• Avatar
• Username
• Score

Nuxter Page

Resume of his contributions:

• Total issues + helpful issues
• Total Comments + helpful comments
• Total reactions received 👍

🐞 Description

The Nuxters Card that was displayed in the GitHub README is suddenly not showing up.
The URL of the OG image has been changed and we believe this may be the cause.

• before: https://nuxters.nuxt.com/{GitHub name}/__og_image__/og.png
• after: https://nuxters.nuxt.com/card/{GitHub name}/og.png

However, it is possible that the loading of Add your Nuxter card on Github is not completed and another problem is compounding.
(This one will creating in another bug issue: #66 ).

🔗 Linked Issue

related #66 .

https://twitter.com/Mokkapps/status/1678810414216249377

this might be controversial, but we could have introduce weight to calculate the points for the PRs:

• docs: 1x
• chore: 1x
• style: 1x
• build: 2x
• ci: 2x
• refactor: 2x
• test: 2x
• perf: 3x
• fix: 3x
• feat: 3x

While everything is important, I think it makes the system a little more fun and rewarding.

This might be a bit tricky in terms of data aggregation but it would be a really nice addition I think. Perhaps for this one the mee6 leaderboards could be utilized with e.g. 0.25x multiplier on messages: https://mee6.xyz/de/leaderboard/473401852243869706

Based on the description (3+ reactions) I think this metric isn't quite working yet or I am misunderstanding what reactions are in this case.
Personally I've opened issues that recieved 3+ emote reactions and/or 3+ comments but the api returns 0 points which I find odd based on the description.

As a sidenote: I think it'd be nice to maybe do (3+ reactions OR 5+ comments) for an issue to count as helpful, assuming currently it's only checking emotes. I feel like many people on github don't use emotes and an issue that sparked a discussion instead would be of roughly equal value imo

I think it would tidy up the source code a lot to use the Nuxt Icon module where possible. For example, to replace this icon. From my understanding, they would be rendered to HTML (SVG) as part of the build process, so the end result shouldn't change?

It would be great if we could count all the nuxt unjs dependencies!
Obviously the most important would be nitro and h3, but an argument could be made that all of the ones in the default nuxt lock file should be counted.

Impossible to show the route Atinux nuxter route https://nuxters.nuxt.com/nuxter/Atinux.
I think you need to modify the API call https://github.com/nuxt/nuxters/blob/main/pages/nuxter/%5Busername%5D.vue#L9 with the https://api.nuxt.com/contributors route

There is a link that seems to be wrong in the Hero on the homepage:

According to the copy, it seems like the link should point to the nuxt-modules organization, while at the moment it points to the nuxt/modules repository.

I can open a PR myself, but I wanted to be sure to have a confirmation that this is indeed something to be fixed, and to have a greenlight.

Thanks :)

• nuxt-modules
• nuxt-community
• 3rd party modules from modules API?
• discussions?

I think it would be great to incentivize answering discussions in the GitHub discussion tab to boost activity there. Especially since the author there can actually mark specific comments as solutions.

We could consider implementing multipliers, like 3x for answering a question, and 1x or 0.5x for the author marking an answer as the solution. This would encourage people to accept answers more, since a lot of people don't do that, which can make it look like a question is still unresolved.

I think it is possible to create a dynamic path in the format '/profile/:githubusername' to fetch the user's image and score.
Additionally, the generated image and link can be made easily shareable on social media. The image can be dynamically generated.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update devdependency @nuxt/ui to ^2.15.2

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Every once in a while you see a red role Nuxt MVP pop up in the Discord, but that's quite a rare occurrence.
I get that these roles are meant to be rare and are reserved for a handful of users, not given out to everyone who opens an issue once. Still, I am wondering whether the metrics provided by this project could be used to appoint MVPS as well or at least influence the decision-making process, as I think a breath of fresh air for this role could be quite beneficial.

The "Share your Nuxter profile ✨" text overlaps with the username and points counter at screen widths between 768px and 1024px (md).

I'll open a PR to fix it 👍

Currently, Nuxters, the contribution scoring tool for Nuxt, lacks a metric to reward users for valuable contributions that lead to issue resolution via merged merge request. I propose adding to the category of "useful issue" the consideration of these issues that have been closed by a merged merge request as useful issues. For instance, issue #19930 was resolved through this merge request: nuxt/nuxt#19930.

Let's enhance Nuxters to acknowledge such contributions and motivate meaningful collaborations.