Redesign of the Node.js API Docs

Hey, y'all 👋 with the redesign of the Node.js Website done. We're ready to move our efforts into revamping the design of the Node.js API docs and its build process. We understand this is code owned by Node.js Core, so we're (@nodejs/web-infra) opening an issue here. ### 📣 Development Update (06.01.2026) We're closer to the launch of the redesign of the Node.js API docs, we're currently ironing some quirk outs with UX, Speculative Requests, improving search functionality and ensuring everything is ready for launch. * Meanwhile feel free to navigate the preview branch [publicly available here](https://nodejs-api-docs-tooling.vercel.app/) and provide feedback over here ;) * And the source is available at https://github.com/nodejs/doc-kit (most of issues should be opened over there) **TL;DR:** Preview availabe at https://nodejs-api-docs-tooling.vercel.app/ ## Overview ### Revamp of Tooling - We intend to modernize the current tooling of the Node.js API docs (https://github.com/nodejs/node/tree/main/tools/doc), migrating from the current manual code into something more modern: - We intend to transform (in-memory, during build-time, no source change) the raw Markdown into MDX - Replace the YAML metadata (in-memory, during build-time, no source change) to references of MDX Metadata - This is similar to what we did with an MVP on the `nodejs/nodejs.dev` repository as seen [here](https://github.com/nodejs/nodejs.dev/blob/main/util-node/apiDocsTransformUtils.js) and [here](https://github.com/nodejs/nodejs.dev/blob/main/util-node/getApiDocsData.js) - The MDX gets converted into JSX, allowing us to use React Components on the codebase, such as on the Node.js Website - Finally, we use `ReactDOM` (Server) to compile the JSX into plain HTML (initial rendering), which is then embedded in the HTML templates, making each page an HTML file. (Source MD file -> Target HTML file as it has been done so far) - The file names will be the same - The JavaScript client-si…