Tl;dr: We’re planning ahead to prevent tech debt from redirects created in the new Community. We’ll chat about redirects that were broken and repaired during the Community migration at a later date.
Features are released or updated and community resources become outdated. When this happens we prevent immediate breakage of links by putting a redirect in place. The new community platform treats resource creation much more efficiently than the old, so we expect redirects to be less frequent and fewer than in the past.
When they are necessary, our proposal for handling redirects is as follows:
Our goal in creating a redirects log is that it will give you time to 1) search for and replace redirected links in your courses, and/or 2) communicate redirected links with your staff so that they can replace them before the redirects are terminated. We also want to ensure we never accumulate the amount of technical debt we did over the past 5 years in our previous community ever again!
Many of you endured the journey right along with us when our Community migration (from Jive to Khoros) revealed a tremendous amount of tech debt compounded from numerous redirects upon redirects. This situation was something we discussed with our migration team, but neither of our teams were able to predict them all breaking. This discussion is not to discuss migration redirects. We’ll start a new conversation when we have more information from Khoros about those options.