Hello from Wales

Ah, fab, I'll reach out Nicole, a few early...hints for LMS elements and apologies if any of this is Granny sucking eggs talk. And of course, just my experience and opinion

Making sure your review->approve->copy control is sound (I love me some document control QMS I do 😀) as once it's out there its harder to review, revise and release, especially on the quiz question changes when publishing updated SCORMs from Rise as it loses tracking and some LMS have to have the user's progression reset, otherwise it grey screens on them.

Figure out what a critical change is and just grammar/spelling - whilst neither are suitable, knowing that the change is needed or wanted is key - if it would lead the user/learner to be misinformed, confused, etc., then it's critical. Anything else can be updated later (hence my comment on review/approval earlier, if that's sound, you should have fewer of these). Tracking changes is a challenge, especially when users say what's wrong and maybe you don't have an SME or technical writer to let you know what the right content is.

Build in accessible enabling aspects into templates early on, accessibility signposts to the various browsers for contrast, fonts, CC, keyboard shortcuts in Rise, etc.,  saves you a shed of time and really helps the learner navigate the learning...not the platform, and I tend to build in an orientation to the Rise build so the user knows what this looks like for that module/session/ /[insert block title here]

Of course, feel free to fire Q's my way, I'm not precious about this stuff and the more we share the more we learn