normalize tags and author keys #59

Closed
opened 2026-10-05 05:12:02 +02:00 by adam · 7 comments
Owner

Problem

Currently tags and authors are case sensitive and expressed in plain text resulting in ugly/fragile preview urls:

?author=Kyle%20Drake&tags=go-ipfs,bootstrap%20nodes,breaking%20change

Suggestion:

Use this included slug module to enforce urls into lower kebab-case keys and match the objects in a case insensitive way:

?author=kyle-drake&tags=go-ipfs,bootstrap-nodes,breaking-change

It would be best to do this sooner rather than later so that we don't end up with too many inbound links using the current structure.

### Problem Currently tags and authors are case sensitive and expressed in plain text resulting in ugly/fragile preview urls: `?author=Kyle%20Drake&tags=go-ipfs,bootstrap%20nodes,breaking%20change` ### Suggestion: Use this included `slug` module to enforce urls into lower kebab-case keys and match the objects in a case insensitive way: `?author=kyle-drake&tags=go-ipfs,bootstrap-nodes,breaking-change` It would be best to do this sooner rather than later so that we don't end up with too many inbound links using the current structure. <!-- github-sync-id:859594037 -->
adam closed this issue 2026-10-05 05:12:02 +02:00
Author
Owner

Sounds good 👍
Should we support the old format to not break old links?

Sounds good 👍 Should we support the old format to not break old links? <!-- github-comment-id:821111764 -->
Author
Owner

I think we're early enough for that not to be an issue yet, plus any unrecognised links will just fall back to the blog index.

I think we're early enough for that not to be an issue yet, plus any unrecognised links will just fall back to the blog index. <!-- github-comment-id:821113244 -->
Author
Owner

Suggest we do fall back for category types with spaces in them - eg news releases - as there are definitely links directly to those in circulation.

Suggest we **do** fall back for category types with spaces in them - eg news releases - as there are definitely links directly to those in circulation. <!-- github-comment-id:821172246 -->
Author
Owner

If it doesn't add too much complexity then yes that would be great also. It will only affect %20 items, so weighing up implementation cost against that.

If it doesn't add too much complexity then yes that would be great also. It will only affect `%20` items, so weighing up implementation cost against that. <!-- github-comment-id:821188785 -->
Author
Owner

@jdiogopeixoto Just checking in on this one? Thank you!

@jdiogopeixoto Just checking in on this one? Thank you! <!-- github-comment-id:822883427 -->
Author
Owner

@jessicaschilling I'm finishing the work on this one. I should be done tomorrow.

@jessicaschilling I'm finishing the work on this one. I should be done tomorrow. <!-- github-comment-id:822889916 -->
Author
Owner

@jdiogopeixoto could we also include a fix in this work for the category pages? Basically adding hard coded redirects for each page to /?category=event e.g.

I can do this quickly in the PR you create.

@jdiogopeixoto could we also include a fix in this work for the category pages? Basically adding hard coded redirects for each page to `/?category=event` e.g. I can do this quickly in the PR you create. <!-- github-comment-id:823460874 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/ipfs-blog#59