Back

@WeirdWriter @eleventy According to the #11ty docs, if you apply the universal slugify filter to the tag name, it should convert it to lower case as that filter is based on this npm package which defaults to converting inputs to lower case. For example {{ tag | slugify }} would take Newsletter and turn it into newsletter. https://www.npmjs.com/package/@sindresorhus/slugify

@bobmonsour @WeirdWriter @eleventy if I'm interpreting the problem and suggestion correctly, that suggestion will cover getting the correct links in templates - e.g. pseudocode language mishmash

tags.map(tag => `<a href="/tags/{tag|slugify}">{tag}</a>`

You'll still need to make your permalinks lowercase. You can do that on a per-directory basis with `eleventyComputed` in an `.11tydata` data file. But it sounds like you want it site wide? For that you can use `addGlobalData` in your Eleventy config file. Here's a minimal example https://stackblitz.com/edit/eleventy-with-lowercase-permalinks inspired by the Eleventy docs' "Permalinks > Remove trailing slashes" example https://www.11ty.dev/docs/permalinks/#remove-trailing-slashes

@bobmonsour @WeirdWriter @eleventy ah now I see the code link. I may have misunderstood the problem - looks like you're talking about `tag-pages.md`, where `slugify` in the computed permalinks does look like a complete solution.

@WeirdWriter @olets @bobmonsour `post.url` in your `tag-feeds.njk` template will already have the slugified URL if you’ve set the permalink of each template that you’re iterating over.

For example if a post is in `collections.AI` it needs to its own permalink with slugify too (set somewhere in the data cascade for that template)