Skip to content

doc: move to redesign - #66713

Open
avivkeller wants to merge 6 commits into
nodejs:mainfrom
avivkeller:redesign
Open

avivkeller wants to merge 6 commits 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).

@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
Comment thread tools/doc/web.doc-kit.config.mjs Resolved

@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 thread test/doctool/test-make-doc.mjs Resolved
Comment thread test/doctool/test-make-doc.mjs Resolved
@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.68%. Comparing base (d44625a) to head (62a50c5).
⚠️ Report is 24 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #66713      +/-   ##
==========================================
- Coverage   90.69%   90.68%   -0.02%     
==========================================
  Files         797      797              
  Lines      278787   278874      +87     
  Branches    53607    53626      +19     
==========================================
+ Hits       252858   252908      +50     
- Misses      16292    16325      +33     
- Partials     9637     9641       +4     

see 41 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).

Comment thread tools/doc/web.doc-kit.config.mjs Resolved
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Comment thread test/doctool/test-make-doc.mjs Resolved
Comment thread tools/doc/web.doc-kit.config.mjs Resolved
Co-authored-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com>
Signed-off-by: avivkeller <me@aviv.sh>
@nodejs-github-bot

This comment was marked as outdated.

Pass `skip_apidoc_files` from the Makefile to doc-kit with `--ignore`
instead of duplicating the list in the config file, and read the list
in test-make-doc.mjs synchronously (the callback `fs.open` was being
awaited, which threw ERR_INVALID_ARG_TYPE).

Assisted-by: Claude Fable 5.1
Comment thread test/doctool/test-docs.mjs Resolved

@ovflowd ovflowd left a comment

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.

SgTm (Sorcerer Got Temu Merchandise)

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@avivkeller avivkeller added the author ready PRs with CI started, the required approvals, and no outstanding review comments. label Oct 31, 2026
Comment thread Makefile Resolved
Comment thread Makefile Resolved
Comment thread tools/doc/web.doc-kit.config.mjs Resolved
Generate llms.txt from the web config instead of a separate doc-kit
call with `-t llms-txt`. The single call already passes the config, so
`llms-txt` joins its targets, with its output pinned to out/doc where
it lived before, and out/doc/llms.txt becomes one more output of the
stamp rule. The outputs are now listed once, in apidoc_outputs, and
the comment above them says what the stamp is for.

The built docs are identical to before, llms.txt included.

Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
@ovflowd ovflowd added the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Nov 1, 2026
@ovflowd
ovflowd requested a review from bmuenzenmeyer November 1, 2026 23:07

@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.

LGTM

@github-actions github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Nov 2, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Quote the config's top-level keys: 'llms-txt' needs quotes, and the quote-props rule wants the other keys at that level quoted to match.

Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
@ovflowd ovflowd added the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Nov 2, 2026
@avivkeller avivkeller added the tsc-agenda Issues and PRs to discuss during Technical Steering Committee meetings. label Nov 2, 2026
@avivkeller

Copy link
Copy Markdown
Member Author

Adding to the TSC agenda for visibility that this is ready, so they can give their input

@avivkeller avivkeller removed the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs with CI started, the required approvals, and no outstanding review comments. 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. tsc-agenda Issues and PRs to discuss during Technical Steering Committee meetings.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants