Skip to content

doc: move to redesign - #66713

Open
avivkeller wants to merge 1 commit into
nodejs:mainfrom
avivkeller:redesign
Open

avivkeller wants to merge 1 commit into
nodejs:mainfrom
avivkeller:redesign

Conversation

@avivkeller

Copy link
Copy Markdown
Member

This PR shouldn't change much from it's current form. Most changes will go in doc-kit. test-make-doc was removed, since our new generator minifies the output HTML (so it's format is structurally inconsistent) and can't be easily parsed with the existing regular expressions.

Furthermore, such tests are not needed due to our tests in doc-kit.

Preview: https://beta.docs.nodejs.org


Notable Change:

Node.js is thrilled to announce a brand new redesign of our documentation experience! The updated documentation now features HTML structure and styling that are much more closely aligned with the main Node.js website UI, creating a more consistent experience across the brand. You can check out the redesigned documentation today at https://nodejs.org/api (Striked out since this isn't correct until this PR lands).

Signed-off-by: avivkeller <me@aviv.sh>
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/web-infra

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to Node.js builds or CI infrastructure. doc Issues and PRs related to Node.js documentation. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. labels Oct 13, 2026
const urlFromRoot = (path) => new URL(path, root).href;

const canBundle = async () => {
try {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We should remove this, I think we already have conditionals to make it work or not?

@bmuenzenmeyer bmuenzenmeyer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think we need to do better, align on fallback strategy here, or at least affirm that #66613 or this test is enough (not both) . If canBundle ever returns false, we don't get HTML docs at all, which we identified as a production issue worthy of an expensive new release.

Could we add this check to the release process too? Is CI enough? Perhaps

Comment on lines +3 to +5
import assert from 'assert';
import fs from 'fs';
import path from 'path';

@bmuenzenmeyer bmuenzenmeyer Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: siblings files do this both ways

Suggested change
import assert from 'assert';
import fs from 'fs';
import path from 'path';
import assert from 'node:assert';
import fs from 'node:fs';
import path from 'node:path';

const mdURL = new URL('../../doc/api/', import.meta.url);

// Kept in sync with `skip_apidoc_files` in the Makefile.
const skippedDocs = ['quic'];

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

https://github.com/nodejs/node/pull/66613/changes does a better job of keeping this in sync by reading the Makefile directly.

@codecov

codecov Bot commented Oct 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.49%. Comparing base (4599b6a) to head (4428178).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #66713   +/-   ##
=======================================
  Coverage   90.48%   90.49%           
=======================================
  Files         791      791           
  Lines      277204   277204           
  Branches    53311    53308    -3     
=======================================
+ Hits       250828   250851   +23     
+ Misses      16796    16781   -15     
+ Partials     9580     9572    -8     

see 32 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@avivkeller

Copy link
Copy Markdown
Member Author

If canBundle ever returns false, we don't get HTML docs at all, which we identified as a production issue worthy of an expensive new release.

We know that lightningcss resolves on release machines, so I assume Rolldown will as well, but I 100% want to double-check that on a release-ci after regular CI passes (a regular CI is not enough).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to Node.js builds or CI infrastructure. doc Issues and PRs related to Node.js documentation. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants