DOC-6954 Give the Client tools page its categories back - #3777
Merged
Conversation
Contributor
Contributor
Contributor
🧠 Redis MemoryFound 8 related items from repository history (3 new this commit):
Memory updated at 9b760b1 |
One deleted line. `categories:` had no value and `aliases:` sat immediately beneath it, so YAML bound the category list to `aliases` and left `categories` null. Removing the stray key restores the list to where it was written. Commit daf2053, during the DOC-4543 restructure, inserted `aliases: ` on the line between `categories:` and its list. Before that the frontmatter was correct. So this was never a mistyped category list -- a new key landed one line too high and took the existing list with it, silently, and nothing in the build noticed for twenty-one months. Inserting any key directly above a block list does the same thing. Two effects, both verified against a full build with a production baseURL. The AI outputs get their tags back. The per-page JSON and the Markdown metadata block both derive `tags` from categories, so this page had been publishing an empty array to every consumer of the feed; it now carries all nine entries. Seven bogus redirects stop being published. Because Hugo resolves a slash-less alias against the declaring page's parent directory, the category words had been publishing stubs at /develop/develop/, /develop/docs/, /develop/kubernetes/, /develop/oss/, /develop/rc/, /develop/rs/ and /develop/stack/, all pointing at /develop/tools/. All seven are gone from the build. Removing them is safe: nothing in content, layouts or static references any of them, and Hugo's stubs carry robots noindex, so they were never indexed either. The list is restored verbatim, duplicate `oss` included. That duplicate looked like a typo worth tidying until I counted: 822 pages carry this exact nine-entry list, and 857 of 4,696 category lists contain some duplicate. It is the house pattern, and removing it here would make this page the odd one out for no benefit. One correction to the ticket, which claimed the page was missing from its category listings. It was not, because there are no category listings: layouts/_default/term.html and taxonomy.html both contain only a comment suppressing Hugo's missing-layout warning, so every category page renders one byte. The real cost of the bug was the empty tags array and the seven spurious redirects, not navigation. Learned: the stated impact was wrong in a way only the built output showed -- category listing pages render nothing at all here, so the cost was to the machine-readable outputs rather than to anything a reader sees Constraint: the duplicate `oss` in this category list is deliberate house style shared by 822 pages, not a typo to tidy Ticket: DOC-6954 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
andy-stark-redis
force-pushed
the
DOC-6954-tools-categories
branch
from
August 10, 2026 14:24
fd84fed to
9b760b1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes DOC-6954. One deleted line.
content/develop/tools/_index.mdhadcategories:with no value andaliases:immediately beneath it, so YAML bound the category list toaliasesand leftcategoriesnull:--- categories: -aliases: - docs - developHow it got there
Commit
daf2053e2(DOC-4543 restructure, 2024-11-11) insertedaliases:on the line betweencategories:and its list. Before that the frontmatter was correct.So this was never a mistyped category list — a new key landed one line too high and took the existing list with it, silently, for twenty-one months. Inserting any key directly above a block list does the same thing, which is worth knowing independently of this file.
Two verified effects
Both checked against a full build with a production-style baseURL.
The AI outputs get their
tagsback. The per-page JSON and the Markdown metadata block both derivetagsfromcategories, so this page had been publishing an empty array to every feed consumer. It now carries all nine entries.Seven bogus redirects stop being published. Hugo resolves a slash-less alias against the declaring page's parent directory, so the category words had been publishing live stubs:
/develop/develop/→/develop/tools//develop/docs/→/develop/tools//develop/kubernetes/→/develop/tools//develop/oss/→/develop/tools//develop/rc/→/develop/tools//develop/rs/→/develop/tools//develop/stack/→/develop/tools/Safe to remove: nothing in
content/,layouts/orstatic/references any of them, and Hugo's alias stubs carryrobots: noindex— confirmed in the built output — so they were never indexed either.Two things I checked rather than assumed
The duplicate
ossis kept. It looked like a typo worth tidying until I counted: 822 pages carry this exact nine-entry list, and 857 of 4,696 category lists contain some duplicate. It's the house pattern, and removing it here would make this page the odd one out for no benefit. The list is restored verbatim.The ticket's claimed impact was wrong. It said the page was missing from its category listings. It wasn't — there are no category listings.
layouts/_default/term.htmlandtaxonomy.htmleach contain only{{/* suppress warnings */}}, so every category page renders one byte. The real cost was the emptytagsarray and the seven spurious redirects, not navigation. Corrected on the ticket.Build emits the same 10 pre-existing
REF_NOT_FOUNDwarnings already onmain(DOC-6955) and no new ones.🤖 Generated with Claude Code
Note
Low Risk
Single documentation frontmatter line removal with no runtime or security impact; only fixes metadata and alias generation for one page.
Overview
Fixes a YAML frontmatter mistake on the Client tools section index (
content/develop/tools/_index.md) by removing a strayaliases:line that sat betweencategories:and its list. That mis-indentation had leftcategoriesempty and treated the nine standard labels (docs,develop,stack, etc.) as URL aliases.Restores metadata for AI feeds: layouts map
categoriesto JSONtagsand Markdown metadata, so this page again publishes the full nine-entry tag set instead of an empty array.Stops seven accidental redirects: those category strings are no longer published as Hugo aliases (e.g.
/develop/docs/→/develop/tools/). No app or layout code changes—only frontmatter structure.Reviewed by Cursor Bugbot for commit 9b760b1. Bugbot is set up for automated code reviews on this repo. Configure here.