feat(pride logo): introduce

[AugustinMauroy]

Description

Read issues #6733 to understand what is going on.

Validation

Related Issues

Related to #6733

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run format to ensure the code follows the style guide.
• I have run npm run test to check if all tests are passing.
• I have run npx turbo build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

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

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	May 31, 2024 7:14am

[github-actions]

Lighthouse Results

URL	Performance	Accessibility	Best Practices	SEO	Report
/en	🟢 98	🟢 100	🟢 100	🟢 91	🔗
/en/about	🟢 99	🟢 100	🟢 100	🟢 91	🔗
/en/about/previous-releases	🟢 98	🟢 100	🟢 100	🟢 92	🔗
/en/download	🟢 94	🟢 100	🟢 100	🟢 91	🔗
/en/blog	🟢 100	🟢 100	🟢 100	🟢 92	🔗

[github-actions]

Unit Test Coverage Report

Lines	Statements	Branches	Functions
	90.06% (589/654)	76.08% (175/230)	92.24% (119/129)

Unit Test Report

Tests	Skipped	Failures	Errors	Time
128	0 💤	0 ❌	0 🔥	5.884s ⏱️

[ovflowd]

What I'm trying to say is that you can merge all the Node.js logo variants into a single React Component, they are after all a React Component.

This (what you did below) is not what I was referring to, and does not reduce the duplication of code.

Try to reflect a bit on how to achieve what I'm saying. It's pretty simple actually ;)

[AugustinMauroy]

I thinks I go your idea just just want one nodejsLogo stroke of text will be apply with tailwind and two other component for Hexagon

[bmuenzenmeyer]

I'm thinking we get this released sooner rather than later, even if we aren't in complete alignment on the approach.

We want to release this ASAP. We can refactor at any time after this. But pride month has started

[bmuenzenmeyer]

Content over purity of engineering

[bmuenzenmeyer]

ugh - on mobile this all looked green - something's wrong post-merge - looking into it

[AugustinMauroy]

@bmuenzenmeyer ?

[AugustinMauroy]

I thinks It’s small delay from Vercel deployment

[bmuenzenmeyer]

@AugustinMauroy https://github.com/nodejs/nodejs.org/commits/main/

[AugustinMauroy]

Oh my bad I thinks you talk about logo 😅

[bmuenzenmeyer]

i'm glad its not outright broken, but apologies on any instability i rushed through - mobile is clearly not a good way to review CI status checks - thought i see here everything looks green.

i suggest we simply roll forward with a merge of a dependency update or something