Hello guys! I recently went through creating a similar section for our lab, and had the following feedback for the development section.
[x] Perhaps add a bit about what OpenShift Dev Spaces is during your introduction section, ex. here's what I put with a link to the RHD site: link:https://developers.redhat.com/products/openshift-dev-spaces/overview[*OpenShift Dev Spaces*] is a cloud and container-native development environment that provides a fast, secure, and zero-configuration development environment for Kubernetes and OpenShift. It allows developers to quickly bootstrap their development environment and start coding.
[x] You could add in some information about the devfile usage and why the workspace takes a bit of time to load for this section below, ex. downloading all of the dependencies, etc.
[X] Just to confirm with participants that they're on the right path, perhaps including a screenshot of the uncommenting section so they can confirm they're editing the right file and doing the right uncomment.
[ ] For once the pipeline runs, is there an easy way to verify the new image has been built?
[x] For the terminal post request, maybe also show the command entered
Hello guys! I recently went through creating a similar section for our lab, and had the following feedback for the development section.
[x] Perhaps add a bit about what OpenShift Dev Spaces is during your introduction section, ex. here's what I put with a link to the RHD site:
link:https://developers.redhat.com/products/openshift-dev-spaces/overview[*OpenShift Dev Spaces*] is a cloud and container-native development environment that provides a fast, secure, and zero-configuration development environment for Kubernetes and OpenShift. It allows developers to quickly bootstrap their development environment and start coding.
[x] You could add in some information about the devfile usage and why the workspace takes a bit of time to load for this section below, ex. downloading all of the dependencies, etc.
[X] Just to confirm with participants that they're on the right path, perhaps including a screenshot of the uncommenting section so they can confirm they're editing the right file and doing the right uncomment.
[ ] For once the pipeline runs, is there an easy way to verify the new image has been built?
[x] For the terminal post request, maybe also show the command entered