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
Copy file name to clipboardExpand all lines: content/blog/open-sourcing-workshops-on-demand-part-5-create-a-workshop.md
+1-18Lines changed: 1 addition & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -115,7 +115,7 @@ The following fields are required by the infrastructure. And I will work as the
115
115
116
116
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/).
117
117
118
-
In the **Replays table:
118
+
In the **Replay table**:
119
119
120
120

121
121
@@ -153,8 +153,6 @@ As an admin of the Workshops-on-Demand infrastructure, I had to perform sever
153
153
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
154
154
155
155
156
-
157
-
158
156
As the developer of the Workshops-on-Demand content, Matt had to perform several tasks:
159
157
160
158
### On the backend server:
@@ -222,21 +220,6 @@ Testing the workshop:
222
220
223
221
`Note: The available trace under ~/.mail/from will detail the different steps of the action and allow you to troubelshoot any issue.`
224
222
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
-
240
223
When all tests have validated the workshop, it can follow the move to prod cycle.
241
224
242
225
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