Refactoring your blog urls


πŸŽ„This post has fully grown

I just did a quick refactoring of my JAMStack blog urls. Some didn't fit with my style, some had _ that I wanted to switch to -, and others were rediculously long. I've been using forestry as my CMS, I write many of my posts there, and sometimes it picks some crazy file names (based on my titles). It was time to refactor.

article cover for Large Refactor At The Command Line

Large Refactor At The Command Line

As projects grow patterns that worked early on break and we need to change things to make the project easier to work wit

read more

When refactorings similar to this get really big I often need to do some project wide find an replace, I usually do this right from the command line.

πŸ–Š Rename posts change the filename

My post urls are based on the file name of my markdown file, so I can simply go through my filesystem and rename anything I want. From here its probably best to only commit the addition of the new file name, until the redirects clear, but these are all low traffic posts for me so I just commited both at once.

Safely redirect without breaking links

redirects ‴ _/redirects

I am hosted on netlify, which automatically puts very ⚑ performant redirects on the edge based on a /_redirects route on your site. So I added a redirect from the old route to the new route there.

rename long posts


pedantic πŸ€” probably

This is probably being a bit pedantic. Realistically my urls were probably ok. These posts probably aren't going to be topping the google search charts anyways, but I wanted to do it without killing off any links that I may have happened to post somewhere.

πŸ‘€ see an issue, edit this post on GitHub

If you found value in this post
and want to send a tip.

Buy Me A Coffee

tweet about this post and it will show up here.

←An IndieWeb Webring πŸ•ΈπŸ’β†’