nodejs/nodejs.org

The Node.js® Website

Node.js Website built using Next.js with TypeScript, CSS Modules/Tailwind, and MDXv3

What is this repo?

Nodejs.org by the OpenJS Foundation is the official website for the Node.js® JavaScript runtime. This repo is the source code for the website. It is built using Next.js, a React Framework.

npm ci
npx turbo dev

# listening at localhost:3000

Contributing

This project adopts the Node.js Code of Conduct.

Any person who wants to contribute to the Website is welcome! Please read Contribution Guidelines and see the Figma Design to understand better the structure of this repository.

Important

Please read our Translation Guidelines before contributing to Translation and Localization of the Website

Note

We recommend a read of all Relevant Links below before doing code changes; Including Dependency changes, Content changes, and Code changes.

Deployment

The Website is automatically deployed to Vercel through its GitHub App integration when new pushes happen on the main branch.

Details regarding the deployment are only accessible to the maintainers of the Website Team due to certain limitations.

The current integration is owned by the OpenJS Foundation and managed by the Website Team.

Legacy Deployment

The full setup is in https://github.com/nodejs/build/tree/master/ansible/www-standalone minus secrets and certificates.

The webhook is set up on GitHub for this project and talks to a small Node server on the host, which does the work. See the github-webhook package for this.

Node.js Binaries & API Docs

This repository does not contain the codebase or related infrastructure that serves https://nodejs.org/api/, https://nodejs.org/docs/ or https://nodejs.org/dist/.

These are maintained in different repositories and we urge users to open issues in their respective repositories, for bug reports, feature requests or any matter related to these endpoints.

• release-cloudflare-worker: The codebase responsible for serving the Node.js Distribution Binaries, API Docs and any other assets from the links mentioned above.
  • We use Cloudflare R2 Buckets for storing our Assets and Cloudflare Workers for serving these Assets to the Web.
• node/doc/api: The source code of our API docs, it contains all the Node.js API Documentation Markdown files
  • node/doc contains the HTML templates, CSS styles and JavaScript code that runs on the client-side of our API Docs generated pages.
  • node/tools/doc contains the tooling that validates, lints, builds and compiles our API Docs. Also responsible for generating what you see when accessing https://nodejs.org/api/.

Relevant Links

Code of Conduct

Contribution Guidelines

Collaborator Guide

Figma Design

Content vs Code

Dependency Pinning

Translation Guidelines

Thanks

• Thanks to all contributors and collaborators that make this project possible.
• Thanks to Chromatic for providing the visual testing platform that helps us review UI changes and catch visual regressions.
• Thanks to Vercel for providing the infrastructure that serves and powers the Node.js Website
• Thanks to Cloudflare for providing the infrastructure that serves Node.js's Website, Node.js's CDN and more.
  • A really warm thank you to Cloudflare as we would not be able to serve our community without their immense support.
• Thanks to Sentry for providing an open source license for their error reporting, monitoring and diagnostic tools.
• Thanks to Crowdin for providing a platform that allows us to localize the Node.js Website and collaborate with translators.
• Thanks to Orama for providing a search platform that indexes our expansive content and provides lightning-fast results for our users.

nodejs.org's Issues

Improved Get Involved page

Our "Get Involved" page is pretty weak. We have so many places people can get involved nowadays and we basically just list bug writing guidelines. The page should

• List NodeSchool and other community events and learning.
• List the most accessible working groups.
• Link to information about getting involved in core.

Scroll to top is required, especially for long pages like contribute/development

Title says it all. I'm ready to take it up.

Local build is failing

What am I doing wrong? I've ...

1. ... cloned this repo
2. ... executed npm install and npm run serve within it

And this & this is all I got.

styles.styl can't find base.styl

$ iojs build.js 
[metalsmith] build/static finished: 157ms
/Users/srl/git/new.nodejs.org/build.js:68
      if (err) { throw err; }
                 ^

Error: styles.styl:1:9
   1| @import 'base'
--------------^
   2| 

failed to locate @import file base.sty


    at Evaluator.visitImport (/Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/node_modules/stylus/lib/visitor/evaluator.js:901:21)
    at Evaluator.Visitor.visit (/Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/node_modules/stylus/lib/visitor/index.js:28:40)
    at Evaluator.visit (/Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/node_modules/stylus/lib/visitor/evaluator.js:156:18)
    at Evaluator.visitRoot (/Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/node_modules/stylus/lib/visitor/evaluator.js:693:27)
    at Evaluator.Visitor.visit (/Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/node_modules/stylus/lib/visitor/index.js:28:40)
    at Evaluator.visit (/Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/node_modules/stylus/lib/visitor/evaluator.js:156:18)
    at Evaluator.evaluate (/Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/node_modules/stylus/lib/visitor/evaluator.js:233:15)
    at Renderer.render (/Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/node_modules/stylus/lib/renderer.js:86:26)
    at /Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/lib/index.js:42:11
    at Array.forEach (native)
    at Ware.<anonymous> (/Users/srl/git/new.nodejs.org/node_modules/metalsmith-stylus/lib/index.js:22:12)
    at Ware.<anonymous> (/Users/srl/git/new.nodejs.org/node_modules/metalsmith/node_modules/ware/node_modules/wrap-fn/index.js:45:19)
    at next (/Users/srl/git/new.nodejs.org/node_modules/metalsmith/node_modules/ware/lib/index.js:85:20)
    at /Users/srl/git/new.nodejs.org/node_modules/metalsmith/node_modules/ware/node_modules/wrap-fn/index.js:121:18
    at Ware.<anonymous> (/Users/srl/git/new.nodejs.org/plugins/filter-stylus-partials.js:16:9)
    at Ware.<anonymous> (/Users/srl/git/new.nodejs.org/node_modules/metalsmith/node_modules/ware/node_modules/wrap-fn/index.js:45:19)

http://www.nodejs.org/ redirect loop

http://www.nodejs.org/ loops probably the https and removal of www interfering with each other?

roadmap.nodejs.org

See nodejs/roadmap#52

Information / brainstorm / input session w/ all of the content and “locale” groups

Crosslinking this issue here: nodejs/Intl#9

cc @nodejs/website

Track relevant issues from iojs.org/old nodejs.org

There is a small list of issues (mainly enhancements and ideas), which might be relevant for nodejs.org as well:

https://github.com/nodejs/iojs.org/labels/new%20nodejs.org
https://github.com/nodejs/nodejs.org/labels/new.nodejs.org

index_md anchor links (# appearing onhover on headings in nodejs.org) are missing.

These anchor links are neat way of referring to a section of a page on social networks/forums. They are missing on new.nodejs.org

Screenshot from nodejs.org:

Transfer nodejs.org domain name ownership to foundation

From nodejs/iojs.org#386 @mikeal

We need to figure this out. We'll have to find a way to transfer the management of the domain name without interrupting the service. @misterdjules @mkdolan @nodejs/build

Can we migrate nodejs.org to strict https?

The current nodejs.org has https enabled but it's not strict. See the config for details of what's enabled for plain http. In summary, URLs matching /dist/* /**.json will be served but anything else will get a 301 redirect to the equivalent https URL.

You'll see a note in the config:

    # don't redirect dist to https as it breaks nvm/travis-ci
    # probably the same is true for json

I don't know the provenance of this, perhaps TJ, perhaps @misterdjules? I can understand the caution in jumping straight to https when the redirect was first put in place, but has the time come to make a full move?

I'd really like to redirect everything to https like we do with iojs.org, the days of http are numbered and we shouldn't let it linger. The files served from /dist/* are the ones that benefit the most from being served via https yet they are also the ones getting a pass.

So, my question to @nodejs/website and @nodejs/build is what do you all want to do about this? Can we make a switch to strict https with our website change and v4 release or is there reason to maintain caution here?

@ljharb: can you give us some context about nvm? Do you have details on whether it can currently handle https and if so, when was this enabled and do you have any way of knowing how many users of those old versions are out there?

Does anyone have an entry to Travis to find out the impact there?

Any clues about the .json files? Are there people loading them from the frontend that would need them served via http?

Next Steps

Let's try to write out all the next steps to get the website up and running and assign them to people so that we can avoid overlap.

Content

For more details please refer to this earlier thread about the taxonomy. #19 (comment)

• Home
• About.md
  • governance.md
  • working-groups.md
• Security.md
• Downloads.md
• Foundation.md
  • members.md
  • TSC.md
  • TSC meeting minutes
• Contribute.md
• Docs.md
  • FAQ.md
  • ES6.md
• API (link to https://iojs.org/api/ for now)
• Blog.md
• 404.md

Templates

• About.hbs
• Security.hbs
• Downloads.hbs
• Foundation.hbs
• Contribute.hbs
• Docs.hbs
• Blog.hbs

Style Fixes

• Home
• Blog
• General style for all the basic markdown pages like About and Foundation.

Blog

• Merge in old io.js posts from the evangelism repo. (Mikeal is working on this)

RSS feeds

• Blog posts
• TSC meeting minutes

Other

• Inventory and map out any links breaking on the new site
• Properly permanent redirect relevant old content to new urls

Website URL in node v4 release post

Is v4's website URL in the release blog post supposed to be https://nodejs.org/docs/v4.0.0/? That URL only serves a directory index ATM.

For previous releases that URL was a complete copy of the actual website targeted that specific release, e.g. https://nodejs.org/docs/v0.12.7/

docs.new.nodejs.org

We should probably take this opportunity in building this repo out to take a more active role in the docs maintenance, since no one WG has really laid claim over it yet. Unless @nodejs/build has? Or maybe we should make a @nodejs/docs WG?

Linux Foundation svg is cutoff on smaller mobile devices

I wanted to open an issue to see if it is possible to edit the svg that is used. I wasn't sure if that was provided by the Linux Foundation and could have any changes. If changes can be made, I can work on making it fit on mobile now.

Here is what it currently looks like:

Foundation members page logos are not properly arranged

Update Security Policy

We now have the security policy on the front page of nodejs.org (once we're ready to deploy the new website).

If there are any changes to be made to this policy please update https://github.com/nodejs/new.nodejs.org/blob/master/locale/en/security.md

@rvagg
@nodejs/security
@evilpacket
@nodejs/tsc

Send charset in `content-type` http headers.

Removed, wrong project.

Switchable banner/notification/alert about important security upgrades

Reminder based on nodejs/iojs.org#397

Bootstrap/Font Awesome?

Is this project going to use Bootstrap at all for things like a mobile menu and standardized component styling?

What about Font Awesome for download icons, content icons, etc.?

Add dates and optional authors to blog post pages

Dates are missing, I don't think this is intentional, they are on the index, not sure where they should go though.

It's also be good to be able to read an author from the metadata and put that somewhere if there is one, then we could have posts by named people in the foundation and the broader community, not just faceless text. This'd have to be an optional field I suppose.

Font change?

I noticed the font has changed from the old nodejs.org. Was this intentional or just an oversight?

Website testing on mobile and small screens

We need to test the website on small screens as well. This means browser tests (e.g. with Chrome's device mode), but also real browser tests on devices (Safari iOS, Chrome for Android, Opera Mobile).

• Test overall website
• Test site performance (Wifi, EDGE, 3G)
• Check font size, margins, table- and blog layout
• Adjust layout of main navigation
• Adjust layout of sub-navigation
• …

Automated release posts

So, we have the releases .json file from build, if we also got the latest Changelog.md we could automatically generate the release blog posts rather than the manual ones we currently have which are quite a pain in the ass.

Banner & Announcements

Heya,

We needed to get up a press release today and a banner for the conference so I pushed them this morning, I was going to post it as a PR and then merge it so that we had a place to talk about it after but I forgot so I'm posing this issue now :)

The banner is placed where the "Node on the Road" banner was on the old site. It's a little large but looks pretty nice, but I'm open to reducing its size if we find a better background image (this one didn't look good when I reduced the height).

Additionally, the foundation is going to be putting out press releases fairly often. I created a new "announcement" section on the blog and a filtered feed for the Foundation section. This is pretty similar to other foundation sites.

Also, announcements went out today about the board director elections and the new foundation lead event Node.js Interactive, is live.

Links for downloads to pLinux, zLinux and AIX missing

The previous download page when hosted on the old side included links to where you could download versions for these platforms. This section was added under this PR #101 (comment)

and it looked like this

Post-summit Updates / Docs Collab.

During the https://github.com/nodejs/summit we had a chance to get members from the emerging docs WG, website group and other stakeholders together for some strategy meetings.

We mostly focussed on ensuring smooth collaboration with documentation in their evolving efforts. To that point, it was agreed that we should work together (via this repo) to develop a static site generation stack together to harmonize how both projects work.

The docs team, to start, will operate similar to an i18n group providing occasional PRs against website repo. In the long term we'll break things up to smaller repos (content, tooling, documentations) and try to automate a lot of this current process overhead. For the short term this strategy of working in one repo actually simplifies things and let's us just get the shared tooling evolving faster. Some work they've already done will be contributed in to this project's metalsmith work.

While technically we're two WG, in the short term we may end up acting more like one. We'll try to get some overlap in meetings to ensure our content structures and strategies align. An example of this is that website will own the overall CSS/structure/frontend-JS/etc. while they own any docs or guides type markdown content.

More to come on this topic, including efforts to get some shared meetings rolling soon. I just wanted to update everyone in @nodejs/website who wasn't there of our plan to work together.

/cc @nodejs/documentation

MVP

Can we put together a list of tasks to accomplish in order to get an MVP live for the converged project.

It's very difficult to discern what needs to get done or how to get involved based on the current issues/readme. Perhaps this information is embedded somewhere in prior repos but even I can't seem to figure it out.

Node.js v4.0.0 Release Checklist for nodejs.org

See nodejs/node#2522 for ongoing details; the current plan is for it to be released in a bit over 24 hours from now so I want to make sure that (a) we have people available who can fix up the website if needed and (b) we capture all of the items that we know need doing on the website end.

The obvious differences between v4.x and v0.12.x for the website that I can think of are:

• New download file types and adjusted old ones—armv6, armv7, arm64, no "universal" .pkg for OSX, no 32-bit OSX, .xz versions of all of the tarballs.
• New style CHANGELOG meaning we can do more than just list commits.

What do we need to get done?

• New download page, it looks like @phillipj has this ready to go here: #87
• Release blog post, we're not auto-generating these from core any more, it'll have to be done manually for now I suppose. Current release proposal with WIP changelog entry: nodejs/node#2715, also should have some additional blog-post style text to go along with it with a quick summary of what v4 is all about and pointing to any resources we have for people to read. I can work on the text here and PR to this repo for feedback.

Is there anything else I'm not seeing? I'm assuming that nodejs.org/dist/index.json will be automatically picked up and the downloads pages generated for them, is that correct?

Manual line breaks in README.md

I was just writing in README.md, and I noticed that some or all of the line breaks in the file are manually done. Is this intentional? If not, I'll send a PR to fix it.

Serves up 'not found'

OK it builds now (thanks) but serves up:

Not Found

$ npm run serve

> [email protected] serve /Users/srl/git/new.nodejs.org
> ./build.js serve

http://localhost:8080/
[metalsmith] build/static finished: 778ms
[metalsmith] build/en finished: 7970ms

Enable custom 404 page in nginx

Please use /en/404.html as custom 404 page.

Content structure for new.nodejs.org

At the moment, the content structure of iojs.org and nodejs.org is very heterogenous, so simply merging the content of both sites for a new.nodejs.org won't work. I took the time and went briefly over the structure, which is currently in place:

Content structure iojs.org

• Home
  Linking to: Downloads (/dist directory), Weekly Update (external), News Archive (external) and Nightly (next) releases
• Roadmap (external)
• FAQ
  Relationship node.js/io.js, semver, contributing, open source gouvernance
• ES6
  Description of features and flags
• API Docs (external)

Footer links

• Release History (linking to external changelog and /dist)
• GitHub Issues (external)
• GitHub Org (external)
• IRC Chat (external)
• Logs (external)
• Governance (external)

---

Content structure nodejs.org

• Home
  Including web server example
• Downloads
  Download links in platform matrix (32bit / 64bit), external platform support: IBM Power Systems/System Z
• Documentation
  General text explaining tutorials, localization and API docs
  • API Docs
  • Tutorials
    Short text about NodeSchool, no further resources
  • Localization
    Links to international communities and user groups – not about localization/localized content
  • Contributing (only visible on API docs page; not identical with https://nodejs.org/contribute/)
  • Workflow (only visible on API docs page; contribution workflow guide)
• Contribute
  Introduction text to the three topics below; only focused on node.js core development.
  • Code contributions (New Node.js Foundation Development Policy; not 100% identical to https://nodejs.org/documentation/contributing/)
    • Workflow (not 100% identical to https://nodejs.org/documentation/workflow/))
  • Accepting contributions
  • Becoming a collaborator
• Foundation
  Introduction text to the topics below
  • Anchor: Timeline (listed in left navigation)
  • Anchor: Core documents (listed in left navigation)
  • Members
    Logos of members, separated by platinum, gold, silver status
  • Blog
    Links to hand picked articles on blog.nodejs.org, github issues, joyent.com, medium.com, developer.intel.com, …
• Community
  mixed list: report issues, docs/code contribution, events, mailing list, GitHub issues, IRC, various community sites, official API docs, NodeSchool, Stack Overflow, again links to GitHub, contribution/localization, …
  • Github Issues (listed in footer navigation)
  • Mailing List (listed in footer navigation)
  • IRC (listed in footer navigation)
  • Twitter (listed in footer navigation)
• About
  "hello world" http server
  • Organization
    • TSC meeting minutes
  • Releases
    Description of patch/minor/major releases and scoping features, not actual list of releases
  • Resources (logos, desktop background)
  • Advisory board (not listed in footer navigation; advisory board charter)
    • Members
    • Minutes
  • Security (not listed in footer navigation; reporting bugs, disclosure policy)
• Jobs (external site by SimplyHired)
• Blog (mostly release announcements)

npm install failing on v4.0.0-pre

Just an fyi... using v4.0.0-pre (nodejs/node master), npm install is failing:

bash-3.2$ npm install
npm WARN engine [email protected]: wanted: {"node":">= 0.9"} (current: {"node":"4.0.0-pre","npm":"2.13.3"})
npm ERR! Darwin 14.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.0.0-pre
npm ERR! npm  v2.13.3
npm ERR! code ETARGET

npm ERR! notarget No compatible version found: vinyl-fs@'>=0.3.0 <0.4.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.0.1","0.0.2","0.1.0","1.0.0"]
npm ERR! notarget 
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget 
npm ERR! notarget It was specified as a dependency of 'gulp'
npm ERR! notarget 

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/james/Node/main/new.nodejs.org/npm-debug.log
bash-3.2$ 

then, of course, there's

bash-3.2$ npm run serve

> [email protected] serve /Users/james/Node/main/new.nodejs.org
> iojs build.js serve

sh: iojs: command not found

SSL cert issues?

I think I saw a related ticket a few days ago but couldn't find it anymore. When I try to access new.nodejs.org with wget (scanning for 404s), I get the following message:

Resolving new.nodejs.org (new.nodejs.org)... 104.131.173.199
Connecting to new.nodejs.org (new.nodejs.org)|104.131.173.199|:443... connected.
ERROR: cannot verify new.nodejs.org's certificate, issued by 'CN=COMODO RSA Domain Validation Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB':
  Unable to locally verify the issuer's authority.
To connect to new.nodejs.org insecurely, use `--no-check-certificate'.

Browser is working fine, reporting just in case it causes issues for other tools as well.

Connecting with Marketing/Evangelism

This is to track an external issue nodejs/evangelism#100 which is discussing how Evangelism, Marketing and Website will be working together.

Reduce amount of web fonts included (page performance!)

I just noticed we include all font styles of Source Sans Pro, which has a heavy impact on page performance:

<link href="http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,200,200italic,300,300italic,400italic,600,600italic,700,700italic,900,900italic" rel="stylesheet" type="text/css">

At the moment we use the widths 300 (default text), 500 (headlines), and 700 (for bold). Maybe we could get rid of the latter as well.

Fix sticky footer to work with IE11

We had an issue with a combination of using flexbox, the

element and the sticky footer, which rendered the page completely useless in IE11, as the whole content was covered:

See: https://twitter.com/jaffathecake/status/639776927839072257

I did a quick fix yesterday, but also ended up disabling the sticky footer for now. It would be cool if someone could investigate this issue and fix the footer for IE11.
(Maybe this helps: http://thatemil.com/blog/2013/11/03/sticky-footers-flexbox-and-ie10/)

Font glitches while clicking around

Am I the only one seeing this on page load while clicking around? The text seems slightly bigger for the first few 100 milliseconds, before suddenly changing. Must be recent change as I havent noticed this before.

Chrome v45.

node.foundation / nodejs.foundation

I bought these domains ages ago. If we'd like to use them I'm happy to transfer them over. Wanted to get the discussion started about stand-alone foundation website vs. foundation as a page on the new Node.js website.

In either case I think the .foundation gTLD is a bit fun. Even if they were just redirects to a page on another website.

New site is live with 0.12.7 everywhere, except link to changelog

Probably a known issue, but Home page lists v0.12.7 as current, but link to changelog on this repo is to current v3.3.0.

Looks good though.

blog.nodejs.org structure from joyent/node-website on nodejs/new.nodejs.org

The current nodejs.org at joyent/node-website uses complete, individual markdown files for metadata such as title, post date, etc. What needs to be done to model the old posts into the blog given a build process similar to the one iojs.org has? Just wanted to get this topic rolling so everyone's aware of it.

Website WG Membership / Collaborator Establishment

This is an issue a la #4 (comment). If you want to be a member or collaborator in the Website WG...

• via grandfathering from the old iojs/website WG repo
• via official Joyent/Node Foundation role
• via Node Foundation membership

... make it known here, and you will be appropriately added to the WG. (or directly add yourself in #14)

If you want to join, but are not a member of one of these groups, you should see the (in-progress) GOVERNANCE.md - namely:

Individuals making significant and valuable contributions are made Collaborators and given commit-access to the project. These individuals are identified by the WG and their addition as Collaborators is discussed during the weekly WG meeting.

Note: If you make a significant contribution and are not considered for commit-access log an issue or contact a WG member directly and it will be brought up in the next WG meeting.

First release checklist

This is the list of blockers for getting the new site live. There's plenty of additional things to do to improve the website, this list is only things that MUST be done in order to go live.

Content

• Docs.md (main docs page content)
• versions.json w/ all io.js and node.js releases
• https://iojs.org/api/ -> https://new.nodejs.org/api/
• Google Analytics

What else?

Is 1.2 MiB png photo really needed on the title page?

I'm speaking about http://events.linuxfoundation.org/sites/events/files/styles/1920px_maxwidth/public/banner-images/portland.png now.

I see ~15% size improvement (1232339 to 1052669 bytes) after applying lossless png compression like this:

pngcrush -brute -reduce -ow -q portland.png
advdef -z -4 -q portland.png

Converting that photo to a jpg image (with default convert options) reduces the size 3.5x (1232339 to 345452 bytes) with almost no visible difference (that's a photo, remember?).

Markdown content gets escaped twice

Found this when working on #27. If you try with that content on line 18 you can see the apostrophes escaped to ' by metalsmith-markdown, then ' by metalsmith-prism.

Seems like the only way to make Prism not escape them is to use Prism's hooks and metalsmith-prism doesn't really have them exposed.

Wording & project description (aka README)

I stole this title from nodejs/iojs.org#2 but in this case the issue concerns the contents of the README specifically.

I assume we'll be bringing over much of the existing node/iojs.org README content in some form as this project evolves to include concepts such as "project structures" and "publishing".

For now mostly I'm requesting a proof read of the initial content I added and for us to get in some glaring omissions:

• collaborators (up-to-date version), aka "Current Project Team Members"
• governance

These can be broad summaries linking to the relevant CONTRIBUTING and GOVERNANCE files, which also still need to be added.

Width of <aside> on /foundation is too small, rendering poor hovering effect for long titles.

Width of the sidebar on /foundation page is too small to accommodate long titles such as "Technical Steering Committee" in one line. We should either

• use abbreviation (TS Committee)
• or adjust the width of <aside> i.e. adjust the decided grid layout
• or consider smaller font-size *

However former solution seems to be more aesthetically pleasing.

*nodejs.org uses font-size of 14px while new.nodejs.org using 20px/1.5 (on my 13" MBA)

Publishing/hosting logistics (working with the build team)

This issue is officially being tracked in nodejs/build#119 so please direct conversation there. (This exists just for tracking the external issue.)

Blog only shows the 4.0.0 release on new.nodejs.org

https://new.nodejs.org/en/blog/ shows the new release while https://nodejs.org/en/blog/ does not show it.