fix: remove redundant TOC picker from legacy HTML template.

[ubay1]

Removed the __TOC_PICKER__ placeholder from the template and its corresponding generation logic in replaceTemplateValues.mjs to avoid rendering a duplicate Table of Contents in the API documentation layout.

Description

This change removes the extra Table of Contents picker rendered in the content header area of the generated API documentation pages.

The sidebar navigation already provides the full documentation index, so rendering another TOC picker in the page header created redundant navigation and unnecessary visual clutter.

This update removes:

• The __TOC_PICKER__ placeholder from the HTML template
• The related generation logic in replaceTemplateValues.mjs

Validation

• Generated API docs locally using doc-kit
• Verified that the duplicate TOC section no longer appears in the content header
• Confirmed sidebar navigation and other pickers continue to function normally

Related Issues

Fixes nodejs/node#60667

Check List

• I have read the [Contributing Guidelines](https://github.com/nodejs/api-docs-tooling/blob/main/CONTRIBUTING.md) and made commit messages that follow the guideline.
• I have run node --run test and all tests passed.
• I have check code formatting with node --run format & node --run lint.
• I've covered new added functionality with unit tests if necessary.Removed the __TOC_PICKER__ placeholder from the template and its corresponding generation logic in replaceTemplateValues.mjs to avoid rendering a duplicate Table of Contents in the API documentation layout.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
api-docs-tooling	Ready	Preview	May 22, 2026 10:44pm

[cursor]

PR Summary

Medium Risk
Adds a new CLI/config-driven redirect script and home-link behavior for the legacy HTML index page, which can change navigation and URL handling. Risk is limited to the legacy-html generator output but could cause unexpected redirects if misconfigured.

Overview
Adds support for redirecting the legacy HTML index.html to a configurable target via new CLI flag --index-redirect-url and corresponding legacy-html.indexRedirectURL configuration.

Updates the legacy HTML template and replaceTemplateValues to inject a redirect script + configurable home link, and conditionally suppress the __TOC_PICKER__ on the index page when a redirect is enabled.

^{Reviewed by Cursor Bugbot for commit edff75f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[avivkeller]

This affects every page of an already legacy UI, why?

[ubay1]

This affects every page of an already legacy UI, why?

Sorry, I misunderstood the scope of the issue initially. You're right that the original approach was too broad since it affected all pages in the legacy UI.

I've reworked the implementation so the behavior is now opt-in via a new --index-redirect-url configuration. This allows consumers (like nodejs/node) to redirect only the generated index.html landing page to something like documentation.html without changing the behavior of other legacy pages by default.

[ubay1]

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0206b3b. Configure here.}

[avivkeller]

I don't see the benefit of this, I only see the added complexity

[ubay1]

I don't see the benefit of this, I only see the added complexity

The goal is to support consumers that want documentation.html to be the primary entry point for their documentation.

Currently, opening the root URL always leads to the generated TOC page (index.html), which only contains a list of links. Some consumers may prefer to take users directly to the documentation landing page instead.

This change is optional and only applies when an indexRedirectUrl is explicitly configured. The default behavior remains unchanged.

For example, this is needed by nodejs.org because we don't want to expose the generated TOC page as the documentation entry point and would rather direct users to the documentation landing page.