Update Blog “open-sourcing-workshops-on-demand-part-5-create-a-workshop”

content/blog/open-sourcing-workshops-on-demand-part-5-create-a-workshop.md

@@ -33,7 +33,7 @@ As an admin of the Workshops-on-demand infrastructure, I had to perform sever
 
 ##### On the backend server:
 
-1. ##### Test and validate installation of the new kernel on the staging backend server by:
+1. ###### Test and validate installation of the new kernel on the staging backend server by:
 
 * Creating a new branch for this test
 * Modifying the [backend server installation yaml file ](https://github.com/Workshops-on-Demand/wod-backend/blob/main/ansible/install_backend.yml#L326)to include the new kernel.
@@ -44,9 +44,9 @@ As an admin of the Workshops-on-demand infrastructure, I had to perform sever
 * Validating the changes by testing a new backend install process.
 * Pushing the changes to the github repo.
 
-2. ##### Creating a user for the workshop developer on the test/dev and staging backend servers.
-3. ##### Providing to the developer the necessary information to connect to the test/dev and staging backend servers.
-4. ##### Copy over the workshop developer's home folder a workshop template containing examples of introduction, conclusion and lab notebooks, allowing him to start his work.
+2. ###### Creating a user for the workshop developer on the test/dev and staging backend servers.
+3. ###### Providing to the developer the necessary information to connect to the test/dev and staging backend servers.
+4. ###### Copy over the workshop developer's home folder a workshop template containing examples of introduction, conclusion and lab notebooks, allowing him to start his work.
 
 ##### On the database server:
 
@@ -106,10 +106,12 @@ As the developer of the Workshops-on-demand content, Matt had to perform seve
 
 ##### On the backend server:
 
-1. ##### Log on to the backend server and clone the notebook repo in his home folder.
-2. ##### Create a new branch for his workshop following the naming convention defined with the admin.
-3. Leverage the template provided by me to build up the content of his workshop.
-4. Test the workshop leveraging the `test-action.sh` script
+1. ###### Log on to the backend server and clone the notebook repo in his home folder.
+2. ###### Create a new branch for his workshop following the naming convention defined with the admin and clone the notebooks repo.
+3. ###### Leverage the template provided by me to build up the content of his workshop.
+4. ###### Test the workshop leveraging the `test-action.sh` script
+5. ###### Test the workshop using the staging registration portal.
+6. ###### When all tests are green, create a pull request to merge content with master repo.
 
 * Modifying the \[backend server installation yaml file ]