feat(blog): pride

[vcarl]

Description

Add a blog post for Pride 2025 ✨

See #6802

Validation

Yes, please

Related Issues

n/a

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run pnpm format to ensure the code follows the style guide.
• I have run pnpm test to check if all tests are passing.
• I have run pnpm 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	Jun 27, 2025 0:49am

[Copilot]

Pull Request Overview

This PR adds a new blog post for Pride 2025, presenting a personal narrative on open-sourced identity and how evolving labels reflect personal and professional growth.

• Introduces a new Markdown file for the 2025 Pride post
• Provides thoughtful content linking change in coding practices to personal identity

[avivkeller]

@nodejs/tsc @nodejs/marketing

[avivkeller]

As a reminder to organization members, adding a pride blog post(s) was voted for in the leading candidate during the organization-wide vote we recently held.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.50%. Comparing base (65026c0) to head (84743e7).
Report is 6 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7888      +/-   ##
==========================================
+ Coverage   75.49%   75.50%   +0.01%     
==========================================
  Files         101      101              
  Lines        8311     8311              
  Branches      218      218              
==========================================
+ Hits         6274     6275       +1     
+ Misses       2035     2034       -1     
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ljharb]

This is beautifully written; thanks @vcarl!

[mcollina]

My understanding of the blog post idea (from @benjamingr if I recall correctly) was quite different. The idea of the blog post series to highlight the technical contributions done by LGBTQ+ people, showing how much they made a difference to the project.

While I like this specific blog post, I don’t think it fits our blog.

[AugustinMauroy]

LOVE it

[avivkeller]

My understanding of the blog post idea (from @benjamingr if I recall correctly) was quite different. The idea of the blog post series to highlight the technical contributions done by LGBTQ+ people, showing how much they made a difference to the project.

While I like this specific blog post, I don’t think it fits our blog.

"Publish a series of blog posts outlining contributions from voluntary LGBT+ contributors."

One could argue that contributing a blog post itself is a voluntary contribution. Additionally, this blog post features a quote from npm's co-founder, whose contributions to the ecosystem have been immense.

One could also point out that a blog post like this will inspire more LGBTQ contributors to contribute to the project, perhaps we can mention in the blog post that we are looking for LGBTQ contributors to write posts, and this will act as an introduction to the series?

[MattIPv4]

The idea of the blog post series to highlight the technical contributions done by LGBTQ+ people, showing how much they made a difference to the project.

While Carl may not be a core contributor to the code powering Node.js, they absolutely have contributed to Node.js as a whole, most recently with the launch of our official Discord server, which is definitely making a difference to the project by giving the community a new space to engage.

[bmuenzenmeyer]

My understanding of the blog post idea (from @benjamingr if I recall correctly) was quite different. The idea of the blog post series to highlight the technical contributions done by LGBTQ+ people, showing how much they made a difference to the project.

While I like this specific blog post, I don’t think it fits our blog.

FWIW, this style of post was exactly the kind of post I was envisioning

[avivkeller]

@nodejs/TSC I would love if this was merged before July, as to make it merged during Pride Month, so please review when you get a chance.

@mcollina Given the additional comments, would you mind taking a second look 🙏?

Thank you all!

[RaisinTen]

LGTM

[kyliewd]

thank you @vcarl for writing this blog post, and thanks to the rest of the team for championing this initiative. please let me know when the different posts are live, as i would love to post this on the social channels + add accompanying graphics.

my only requests -- change openjs to node.js so its more specific (as mentioned above) and please ensure open source doesn't have a dash in the middle of it.

otherwise, looks excellent from a foundation perspective. and again, thank YOU! ❤️

[benjamingr]

@mcollina is correct regarding my idea, I am not blocking (or approving) though

Thanks for clarifying @benjamingr . I prefer your original idea, but not blocking this.

[avivkeller]

Thanks for your insight! While your comments are respected and noted, this has received a significant amount of approval from the web team, TSC, collaborators, and marketing, so I'm merging this PR.

As previously mentioned, this will serve as an introduction to the series that you had in mind.

Thank you again!

[RaisinTen]

This part from Kylie's comment still needs to be addressed, so I removed it from queue:

please ensure open source doesn't have a dash in the middle of it.

Feel free to add it back after addressing.

[avivkeller]

Ahh, I didn't see that. Thanks for catching that, @RaisinTen!

[RaisinTen]

Looks good!

[avivkeller]

I'm locking this pull request as a precaution to prevent potential harassment.

Please refer to #6802