[mrjones-plip]

Description

This PR:

• Adds a new Preparing for CHT 5.0 page under existing "migration guides"
• moves existing Preparing for CHT 4.o page under existing "migration guides"
• moves Feature Flag and Remote Collect Update up a level to be under "Quick Guides"
• Updates all relevant links for moves above
• adds aliases so link checker passes:

  Total URLs checked: 465
  Redirects (200): 4
  Other errors: 0
  404 Not Found: 0

• each section in the Preparing for CHT 5.0 page has:
  • Title
  • subset of 4.x the change Applies
  • write up of change
  • background links

Screenshot of new Preparing for CHT 5.0 page and navigation changes

closes #1949

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[mrjones-plip]

@jkuester - there's a couple TK values in there, but I wanted to get this out for an earlier review while we tidy up the other parts (mainly 1943 and 8157)

[andrablaj]

@mrjones-plip I was looking yesterday into the newer versions of Hextra (draft PR #1978) and I really love the banner feature to announce 5.0! We can leverage it if we merge the Hextra upgrade soon. ✨

[mrjones-plip]

oh - fun! I created a local, dummy test branch off your branch, did a little of this in the hugo.toml 👍

[params.banner]
  key = "announcement"
  message = "🎉 CHT 5.0 [Released](#foo) - reduce server disk space by up to 30%!"

And it looks great!

[mrjones-plip]

@jkuester or @dianabarsan - do we know the least expensive upgrade to account for our ecmaversion linting? That is, if I'm on 4.4 and version 4.5 has zero ddoc changes, and thus no re-indexing, I want to go that version first and then version 5.x. The other way is go to 4.22 do a massive re-index and then go to 5.x and do another massive re-index.

I also may be miss-understanding the way to upgrade - so feel free to set me straight!

[jkuester]

@jkuester or @dianabarsan - do we know the least expensive upgrade to account for our medic/cht-core#9202? That is, if I'm on 4.4 and version 4.5 has zero ddoc changes, and thus no re-indexing, I want to go that version first and then version 5.x. The other way is go to 4.22 do a massive re-index and then go to 5.x and do another massive re-index.

Yeah, I think you are on the right track here. (Though, I double checked and I did not see anything about a Couch upgrade in the 4.5.0 release notes. I think the minimum version for an update to 5.0.0 would be 4.6.0 when we upgraded to Couch 3.3.3.).

Either way, it does not look like 4.5.0 or 4.6.0 have any ddoc changes. So, the easiest upgrade from a lower version would be to go to 4.6.0 and then upgrade to 5.0.0.

[mrjones-plip]

Awesome - thanks for confirming @jkuester !

[mrjones-plip]

Really appreciate the detailed feedback @jkuester ! I'll dive into this in the coming day or three

[mrjones-plip]

I think this is good to go! @andrablaj if you want to give a read through for grammar and cohesiveness, that'd be rad, but I suspect that @dianabarsan's final technical sighn off is sufficient as so many folks have looked at this already.

thanks all!

[andrablaj]

So excited about this work! ❤️ The migration guide is extra clear!

I found a few small typos and a building/guides folder that should not be there. Otherwise, looks good!

suggestion: Should we update the cards on the Migration homepage to include the missing sections? Unclear why we added cards only for half of them.

[dianabarsan]

Very nice! I added some minor comments. Everything is super clear and supportive for anyone who wants to upgrade.

[mrjones-plip]

@dianabarsan - I'm assuming you're OK with this PR as is (you reviewed and not approved or requested changes)

@andrablaj - you requested changes so over to you to approve!

[andrablaj]

🚀 Go for it!