Remove browse by tag - #86
Merged
Merged
Conversation
The most-used tag covers 8 of about 37,000 listings, so every tag page was close to empty. This removes the browsing and keeps the tags. - Gone: the directory's tag chip row and ?tag= filter, the home page's "Browse by tag" section, the footer's tag link, and top_tags/1, which had no other caller - A listing's own tags stay, as text instead of links - ?tag= URLs 301 to the same page without it, keeping any other query; every listing page linked there, so crawlers and bookmarks hold them - Search still matches tags, and the JSON API keeps its tag filter Closes #85 --- Pages affected: - [MCP server directory](https://ai.mcpharbor.dev/servers) -- no tag filter row. - [MCP Harbor](https://ai.mcpharbor.dev/) -- no browse-by-tag section. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Closes #85.
The most-used tag covers 8 of about 37,000 listings, so every tag page was close to empty. This removes the browsing and keeps the tags.
?tag=filter, active-tag pillRegistry.top_tags/1?tag=URLstagfilterWhy a plug for the redirect
A LiveView can only answer its first request with a 302. Every listing page linked to
/servers?tag=…, so those URLs are in crawlers' indexes. A 301 folds them into the page they now show, instead of leaving a copy of/serversunder every tag. The plug runs only in the browser pipeline, so the API'stagparameter is untouched.Tests
Nothing covered tag browsing before. Added: neither page offers it, listing tags render as text, old URLs 301 with other params preserved, and the API filter still works. 231 passing on three seeds.
Pages affected:
🤖 Generated with Claude Code