We don't want to change the domain, we just want to change the CMS, move from wordpress to forem. Now links to articles look like this: example.com/bottom-sheets-ios-android-design-ux
and after migration they will look something like this: example.com/user/bottom-sheets-ios-android-design-ux-j4i5
that's why we need a 301 redirect.
If I understand you correctly, you suggest, on the forem side, to make the links wrap without change, that is, the ending -j4i5 is not added.
Then you only need to make one redirect, which can be done using cloudflare:
example.com/slug redirect to example.com/user/slug
And if such a slug is not found, then the redirect will be to the main page, is that all right?
This would greatly simplify the article migration. There are no problems with redirecting from the old domain to the new domain. It is not clear how such a redirect can work on the same domain.
This was helpful to understand in detail — I have some thoughts about how we could handle some of this. I suspect there is a path of how you could accomplish this in the nearterm for your specific case and how we handle all possible scenarios. Our team will give this some thought and try to help this get worked out.
We don't want to change the domain, we just want to change the CMS, move from wordpress to forem. Now links to articles look like this:
example.com/bottom-sheets-ios-android-design-uxand after migration they will look something like this:
example.com/user/bottom-sheets-ios-android-design-ux-j4i5that's why we need a 301 redirect.
If I understand you correctly, you suggest, on the forem side, to make the links wrap without change, that is, the ending
-j4i5is not added.Then you only need to make one redirect, which can be done using cloudflare:
example.com/slug redirect to example.com/user/slugAnd if such a slug is not found, then the redirect will be to the main page, is that all right?
This would greatly simplify the article migration. There are no problems with redirecting from the old domain to the new domain. It is not clear how such a redirect can work on the same domain.
This was helpful to understand in detail — I have some thoughts about how we could handle some of this. I suspect there is a path of how you could accomplish this in the nearterm for your specific case and how we handle all possible scenarios. Our team will give this some thought and try to help this get worked out.
Fine. We will finalize our migration script for now. All possible types of content need to be considered