You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A script should be able to run that updates a quick starts prerequisites as the user completes them, giving users updated information about what they still have outstanding to complete before taking the current quick start. (Should be able to also run clean up script so the next person can run it again.)
This also brings up the question of how to handle quick starts that aren't available yet or when prerequisites haven't been completed. Are there any valid use cases for locking quick starts? Given that validation is still not possible, locking quick starts could just invite users to “fake” completion of a quick start to get to the next one. Additionally, we may not want to block advanced users from accessing a quick start later in a course if they don’t need the prior ones. If we find a valid use case for this, we could consider greying out and locking quick starts that users are not yet able to take. (Info on this pulled from OpenShift's Quick start courses exploration doc, page 7 and 8).
The text was updated successfully, but these errors were encountered:
A script should be able to run that updates a quick starts prerequisites as the user completes them, giving users updated information about what they still have outstanding to complete before taking the current quick start. (Should be able to also run clean up script so the next person can run it again.)
This also brings up the question of how to handle quick starts that aren't available yet or when prerequisites haven't been completed. Are there any valid use cases for locking quick starts? Given that validation is still not possible, locking quick starts could just invite users to “fake” completion of a quick start to get to the next one. Additionally, we may not want to block advanced users from accessing a quick start later in a course if they don’t need the prior ones. If we find a valid use case for this, we could consider greying out and locking quick starts that users are not yet able to take. (Info on this pulled from OpenShift's Quick start courses exploration doc, page 7 and 8).
The text was updated successfully, but these errors were encountered: