Skip to content

Commit f12138c

Browse files
committed
Update Blog “open-sourcing-workshops-on-demand-part-5-create-a-workshop”
1 parent 330cf01 commit f12138c

File tree

1 file changed

+1
-18
lines changed

1 file changed

+1
-18
lines changed

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

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -115,7 +115,7 @@ The following fields are required by the infrastructure. And I will work as the
115115

116116
If you feel you need more details about the registration process, please take a look at the **Register Phase** paragraph in [the following introductionary blog](https://developer.hpe.com/blog/willing-to-build-up-your-own-workshops-on-demand-infrastructure/).
117117

118-
In the **Replays table:
118+
In the **Replay table**:
119119

120120
![](/img/wod-db-go-3.png)
121121

@@ -153,8 +153,6 @@ As an admin of the Workshops-on-Demand infrastructure, I had to perform sever
153153
6. ##### When ready, a pull request can be made. The admin can then review and accept it. The admin can then perform the necessary steps required to prepare the infrastructure to host the workshop
154154

155155

156-
157-
158156
As the developer of the Workshops-on-Demand content, Matt had to perform several tasks:
159157

160158
### On the backend server:
@@ -222,21 +220,6 @@ Testing the workshop:
222220
223221
`Note: The available trace under ~/.mail/from will detail the different steps of the action and allow you to troubelshoot any issue.`
224222
225-
* A set of notebooks that will be used by the student:
226-
227-
* Containing instructions cells in markdown and run code cells leveraging the relevant kernel. If you are not familiar with Jupyter notebooks, a simple [101 workshop](https://developer.hpe.com/hackshack/workshop/25) is available in our Workshops-on-Demand 's catalog.
228-
229-
A workshop should have with at least :
230-
231-
* 0-ReadMeFirst.ipynb
232-
* 1-WKSHP-LAB1.ipynb
233-
* 2-WKSHP-LAB2.ipynb
234-
* 3-WKSHP-Conclusion.ipynb
235-
* LICENCE.MD
236-
* A pictures folder (if any screenshot is required in lab instructions)
237-
* A README.md (0-ReadMeFirst.ipynb in md format)
238-
* wod.yml ( for database injection)
239-
240223
When all tests have validated the workshop, it can follow the move to prod cycle.
241224
242225
You should now have a better understanding of the necessary tasks associated to the creation of a workshop. As you can see, it requires steps on the various sides of the infrastructure.In the next post, I will explain how to deploy and manage the frontend part.

0 commit comments

Comments
 (0)