Add redirect/alias field in Forestry blog template #31

New Issue

2026-10-05T05:10:29+02:00

adam commented

2026-10-05 05:10:29 +02:00

If possible, let's add a field in the Forestry blog post template to account for redirects/aliases. Please see https://github.com/ipfs/blog/edit/master/content/post/125-go-ipfs-0-8-0.md for an example of how this is done in Hugo frontmatter.

If possible, let's add a field in the Forestry blog post template to account for redirects/aliases. Please see https://github.com/ipfs/blog/edit/master/content/post/125-go-ipfs-0-8-0.md for an example of how this is done in Hugo frontmatter.

adam closed this issue

2026-10-05 05:10:29 +02:00

adam commented

2026-10-05 05:10:30 +02:00

The easiest solution here would be to use the @vuepress/html-redirect plugin (that we already have installed) and use a .vuepress/redirects file with all the redirects inside it.

If that doesn't work we could either create a plugin that does what we want or somehow generate the redirects file when we build the project, so we wouldn't have to update the file.

Additional note: while I was doing some research I did find a plugin (vuepress-plugin-redirect-frontmatter) that uses a frontmatter field to redirect but it doesn't redirect on server side, so the 404 page always shows up before the redirect.

Let me know your thoughts and what approach you think it's the best here.

The easiest solution here would be to use the `@vuepress/html-redirect` plugin (that we already have installed) and use a `.vuepress/redirects` file with all the redirects inside it. If that doesn't work we could either create a plugin that does what we want or somehow generate the `redirects` file when we build the project, so we wouldn't have to update the file. Additional note: while I was doing some research I did find a plugin ([`vuepress-plugin-redirect-frontmatter`](https://www.npmjs.com/package/vuepress-plugin-redirect-frontmatter)) that uses a frontmatter field to redirect but it doesn't redirect on server side, so the 404 page always shows up before the redirect. Let me know your thoughts and what approach you think it's the best here.

adam commented

2026-10-05 05:10:31 +02:00

As long as there's a very easy way to add a redirect, it doesn't necessarily need to be in the front matter.

This is to explicitly avoid situations like the mistake I made a few weeks ago: we published a blog post with a typo in the URL, but had already shared the typo URL via social media so we couldn't just change the link — we needed to redirect so that "wrong" links would not only work but encourage people visiting them to share the "right" one (because it was reflected in their browser bar post-redirect).

Make sense? Agree that flashing a 404 is ugly and not really an option ...

As long as there's a very easy way to add a redirect, it doesn't necessarily need to be in the front matter. This is to explicitly avoid situations like the mistake I made a few weeks ago: we published a blog post with a typo in the URL, but had already shared the typo URL via social media so we couldn't just change the link — we needed to redirect so that "wrong" links would not only work but encourage people visiting them to share the "right" one (because it was reflected in their browser bar post-redirect). Make sense? Agree that flashing a 404 is ugly and not really an option ...

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/ipfs-blog#31