Skip to content

Conversation

@ovflowd
Copy link
Member

@ovflowd ovflowd commented Jun 29, 2023

This PR simply updates the badges, including a "Powered by Vercel" badge and removing the Twitter badge that is a little bit useless. (We have many socials, doesn't make sense to share just one)

@ovflowd ovflowd requested a review from a team as a code owner June 29, 2023 08:17
@vercel
Copy link

vercel bot commented Jun 29, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 11, 2023 9:17am
nodejs-org-stories ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 11, 2023 9:17am

@vercel vercel bot temporarily deployed to Preview – nodejs-org June 29, 2023 08:18 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories June 29, 2023 08:18 Inactive
Signed-off-by: Claudio Wunder <[email protected]>
@vercel vercel bot temporarily deployed to Preview – nodejs-org June 29, 2023 09:13 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories June 29, 2023 09:13 Inactive
@tniessen
Copy link
Member

removing the Twitter badge that is a little bit useless

On the other hand, are any of them useful? :)

Copy link
Member

@AugustinMauroy AugustinMauroy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ovflowd
Copy link
Member Author

ovflowd commented Jun 29, 2023

On the other hand, are any of them useful? :)

You know you have a point right? But let's pretend these badges have any value lol

@tniessen
Copy link
Member

Since this is just the website repo, I won't push in either direction, but FWIW, I don't think we should use it as a Vercel ad space.

@ovflowd
Copy link
Member Author

ovflowd commented Jun 29, 2023

Since this is just the website repo, I won't push in either direction, but FWIW, I don't think we should use it as a Vercel ad space.

What would be the correct space? nodejs/build has a list of sponsors for the build infra. Shouldn't the website also show a badge of one of the sponsors?

I'm not sure what is the usual place for such kind of badges/"advertisement", so if there's a TSC-approved way of doing things, let me know :)

@bmuenzenmeyer
Copy link
Contributor

bmuenzenmeyer commented Jun 29, 2023

I've done extensive usability research into README badges. In many cases they are not accessible to screen readers. Apple Voiceover, Windows, even JAWS will sometimes read verbatim data url content.

They look nice, yes, but I agree with @tniessen they are sorta like bumperstickers

@ovflowd
Copy link
Member Author

ovflowd commented Jun 29, 2023

They look nice, yes, but I agree with @tniessen they are sorta like bumperstickers

That part I get. But I still would like to know from @tniessen what is the correct approach (or TSC-approved approach) of supporting our sponsors.

@tniessen
Copy link
Member

@ovflowd I really don't have enough of an opinion to care about the website repo's README, nor am I speaking on behalf of the TSC. IIRC, Vercel employees already claimed that Node.js would be switching to Vercel before it was decided. If you think this is the way of "supporting our sponsors", go for it.

@ovflowd
Copy link
Member Author

ovflowd commented Jun 29, 2023

Sorry @tniessen my intent here isn’t at all to make you uncomfortable either to abide by things that are questionable at any given point.

I’m genuinely more than Ok with closing this PR and opening an issue on nodejs/admin and seeking guidance for what’s the best approach here 🙏

@Harkunwar
Copy link
Contributor

I don't have much strong opinions on this either. If they're sponsoring us with hosting the website more than just the free tier, I think I'm okay with putting them in the README, unless of course anyone else has a better idea.

@ovflowd
Copy link
Member Author

ovflowd commented Jul 3, 2023

cc @richardlau as the build repository is an excellent example of showcasing sponsors' badges. Do you have any opinion on this? (the whole argumentation regarding we adding this or not, based on Tobias's points)

@richardlau
Copy link
Member

cc @richardlau as the build repository is an excellent example of showcasing sponsors' badges. Do you have any opinion on this? (the whole argumentation regarding we adding this or not, based on Tobias's points)

I have no opinion on adding things to the README for this (the website) repository.

The stuff in the Build WG's README predates my involvement. In general I think it does make sense to acknowledge the generous donations of infrastructure resources that keep the Node.js project going. If we do end up hosting the website on Vercel we should add them there alongside our other providers who have donated resources to Node.js infrastructure.

@ovflowd
Copy link
Member Author

ovflowd commented Jul 3, 2023

g. If we do end up hosting the website on Vercel we should add them there alongside our other providers who have donated resources to Node.js infrastructure.

Gotcha. From what I'm getting, the general "tone" here is to add a badge if/once a shift to Vercel happens on the production Website. I'm fine by keeping this open.

Also, right now DigitalOcean and CloudFlare are the sponsors for the Node.js Website Infrastructure, so I wonder if we should regardless have a "Sponsors" section below with the organisations that have donated resources to the Node.js project for keeping the Website alive?

@richardlau
Copy link
Member

richardlau commented Jul 3, 2023

Also, right now DigitalOcean and CloudFlare are the sponsors for the Node.js Website Infrastructure, so I wonder if we should regardless have a "Sponsors" section below with the organisations that have donated resources to the Node.js project for keeping the Website alive?

Again, I have no opinion on adding stuff to the website repository but the Build WG README sort of covers that https://github.com/nodejs/build#infrastructure-providers (the text for DigitalOcean and Cloudflare mentions nodejs.org).

@vercel vercel bot temporarily deployed to Preview – nodejs-org July 10, 2023 15:17 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 10, 2023 15:18 Inactive
Signed-off-by: Claudio Wunder <[email protected]>
@vercel vercel bot temporarily deployed to Preview – nodejs-org July 10, 2023 15:21 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 10, 2023 15:21 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Jul 10, 2023

📦 Next.js Bundle Analysis for nodejs.org

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

@nodejs nodejs deleted a comment from github-actions bot Jul 10, 2023
@ovflowd
Copy link
Member Author

ovflowd commented Jul 11, 2023

cc @nodejs/website if anyone is interested on approving this PR.

@vercel vercel bot temporarily deployed to Preview – nodejs-org July 11, 2023 09:17 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 11, 2023 09:17 Inactive
Copy link
Member

@mikeesto mikeesto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes sense to acknowledge the contribution that Vercel is making by way of infrastructure beyond their free tier. A small badge on the README is far less intrusive than, for example, an ad space on the website itself. I'm in support of adding this.

Copy link
Contributor

@bmuenzenmeyer bmuenzenmeyer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like it.

Assuming the logo rendering problem is a quirk of the mobile app rendering.

mobile screenshot

@bmuenzenmeyer bmuenzenmeyer merged commit 713688c into main Jul 12, 2023
@bmuenzenmeyer bmuenzenmeyer deleted the chore/updated-badges branch July 12, 2023 01:32
umairraza96 pushed a commit to umairraza96/nodejs.org that referenced this pull request Jul 12, 2023
* chore: update badges for the repository

Signed-off-by: Claudio Wunder <[email protected]>

* chore: detect dark theme

Signed-off-by: Claudio Wunder <[email protected]>

* chore: add build check

Signed-off-by: Claudio Wunder <[email protected]>

---------

Signed-off-by: Claudio Wunder <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants