Repository navigation
Dedicated Partners/Sponsors Page + Updates on the Home Page #7909
Description
This issue is a follow-up from an initial TSC PR and conversations I've had with @mhdawson and others, regarding a dedicated sponsors page (that lists Node's official partners (approved by the Foundation) + dedicated section for the Foundation's ESP program.
This issue aims to tackle two distinct tasks:
- Update the Home Page including key-partners based on their level of support (Foundation membership / impact they've been providing to the Node project) in a similar fashion of how ESlint showcases partners on their home page (under the download buttons)
- Add a new Partners/Sponsors Page on /{locale}/about/partners (or /{locale}/about/sponsors) that lists the current partners, the different categories (Hardware, CI, Infrastructure, Security, etc) support they've been giving and a dedicated section for the Foundation's ESP program.
- The page will contain partner's logos, pending their approval and Foundation's approval
- The page will have CTAs to Foundation membership page (for organizations interested to join as a partner) and a CTA to the ESP program.
cc @nodejs/marketing @nodejs/tsc
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
jasnell commentedon Jun 28, 2025
I'm strongly +1 on bringing this proposal to the CPC. @mcollina what will be the necessary process here to help @ovflowd bring a proposal to the CPC for consideration?
ljharb commentedon Jun 29, 2025
From the CPC, I'm a +1 as well, fwiw. Highlighting in-kind sponsors is hugely valuable and will encourage more of the same.
mcollina commentedon Jun 29, 2025
I'm not sure the CPC is the right venue. Possibly a ping to @rginn suffice.
The design must thread carefully to not impact our non-profit status.
mhdawson commentedon Jul 2, 2025
@ovflowd, from the discussion in the TSC meeting is that you work with Robin on a proposal for that.
ovflowd commentedon Jul 2, 2025
I'm meeting with Robin tomorrow around 5pm UTC+2 (8AM PT).
mcollina commentedon Jul 3, 2025
To avoid any breakdown in communication, all @nodejs/tsc members who want to participate in that discussion are welcome to join.
ovflowd commentedon Jul 3, 2025
Right, @rginn or I can invite y'all to the meeting. I believe we could also record it? Is that fine, @rginn?
AugustinMauroy commentedon Jul 3, 2025
also you can do a meeting minutes https://github.com/nodejs/web-team/tree/main/meetings
Is any member of website team can join the meeting ?
rginn commentedon Jul 3, 2025
Let's move this live conversation to the next TSC meeting for my time zone, July 16. I will update this issue with more details prior.
36 remaining items
ovflowd commentedon Jul 20, 2025
ovflowd commentedon Jul 20, 2025
ovflowd commentedon Jul 20, 2025
ovflowd commentedon Jul 20, 2025
@bjohansebas @nodejs/nodejs-website what do you think about this?
ovflowd commentedon Jul 20, 2025
bjohansebas commentedon Jul 20, 2025
I’m going to integrate the release badges into the footer once I have a bit more feedback from the others, since it’s not a simple change that can be made right away, but in the meantime, I’m going to remove the release badges from the homepage.
Though so far, this seems like the best version to me
dario-piotrowicz commentedon Jul 20, 2025
how about putting the sponsor in the bottom center of the view?
Something along the lines of:
ovflowd commentedon Jul 20, 2025
It won't work due to the structure of the site. It also feels a bit lost IMO. And will break depending on screen sizes.
bjohansebas commentedon Jul 22, 2025
Following the comment and the various feedback I received on Slack, the categories under which the companies will be listed would be as follows.
Infrastructure
Find new home for Works on ARM machines openjs-foundation/infrastructure#62 (comment))
ref: https://github.com/nodejs/build?tab=readme-ov-file#infrastructure-providers https://github.com/nodejs/nodejs.org?tab=readme-ov-file#thanks
Services
Ref: https://github.com/nodejs/nodejs.org?tab=readme-ov-file#thanks
Security
Ref: https://github.com/nodejs/node?tab=readme-ov-file#security-release-stewards
Releases
Do we want to add them to the releases? This is in the initial draft. I have no problem adding them, making changes to the list is quite easy. But if that's the case, then this would be the list.
Ref: https://github.com/nodejs/Release?tab=readme-ov-file#releasers-team
ESP
cc: @nodejs/tsc @nodejs/marketing
ovflowd commentedon Jul 22, 2025
I'd also argue that Sentry is service not infrastructure. Infrastructure is anything that powers and enables our systems to run. Services are anything on top of that or even unrelated to it.
bjohansebas commentedon Jul 25, 2025
Hi, the PR (#7991) is ready for review so we can start receiving feedback.
Pages where the changes can be seen:
Security blog post: https://nodejs-org-git-partner-pages-openjs.vercel.app/en/blog/vulnerability/july-2025-security-releases, All blog posts under the "vulnerability" category will include the acknowledgment section.
Downloads:
New partners page: https://nodejs-org-git-partner-pages-openjs.vercel.app/en/about/partners, https://github.com/nodejs/nodejs.org/pull/7991/files#r2229845076
Homepage: https://nodejs-org-git-partner-pages-openjs.vercel.app/en
Also, important for those reviewing: I don’t have all the logos yet, so not all partners will be visible, see comment.
The full list of partners we have so far is available here
https://github.com/nodejs/nodejs.org/blob/d9c5931fd8c7b746e53ad6317e3b98ebf91ded2f/apps/site/util/partners/original.json
GitHub Sponsors will be handled in a separate PR later on, since it requires a token and we're still figuring out the best solution for that small issue. for now, only OpenCollective sponsors are being displayed.