Closed mitjapotocin closed 1 year ago
@mitjapotocin, I do not know enough about this tool, but all redirects need to be 301 redirects so that these are properly registered by search engines (and we do not lose SEO generated by blogs).
I searched a bit and I do not think you can do this in the site content. We will likely need a list of OLDURL -> NEWURL so that we add this to our server config (the server we use for proxying to github).
So whatever you do here is only a fallback that should only be used if the proxy is misconfigured.
@markotoplak ok I can provide you a JSON with {oldUrl: newUrl}
@markotoplak This can be handled in Next. I will implement it and we'll check if its ok. https://nextjs.org/docs/api-reference/next.config.js/redirects
Our page needs to work on a static (dumb) file server with a nginx proxy in front of it. I suspect these things need to run server side - if so, this disqualifies them.
If not and the static files can generate correct responses, even better!
This will redirects from old urls like:
/blog/2020/2020-01-29-machine-anthropology/
=> to new styled urls like:/blog/what-is-machine-anthropology