A temp repo to store instructions and other artifacts in regards to our Quick Labs and Workshops
All of the folders under https://github.com/OpenLiberty/cloud-hosted-guides/tree/master/instructions/
have a matching Gitlab repository used for SkillsNetwork labs.
When creating a new cloud-hosted-guides guide some steps must be taken to ensure that future changes will be mirrored.
- Create a New Project:
- Navigate to the SkillsNetwork Author portal at Become an Author.
- Follow the process to create a Guided Project in Author Workbench
-
Access Your QuickLab:
- Go to your QuickLab page:
https://author.skills.network/quicklabs/:id?show=team
.
- Go to your QuickLab page:
-
Invite Team Members:
- Click on "Invite Member."
- Search for @Gilbert's email and add him as an
Admin
orInstructor
.
- Duplicate the Template Folder:
- Copy and rename the
cloud-hosted-guide-template
folder underinstruction-templates
to and change the folder name to match your QuickLab name. - Keep the original
instructions.md
filename as it will be the file used for editing content.
- Copy and rename the
-
Modify the
mirror.json
andStagingMirror.json
File:- Add a new entry to the
mirror.json
andStagingMirror.json
file using the following format:
{ "guide": "name-of-your-quicklab", "github": "the-folder-name", "quick_lab_id": "quicklab_id", "lab_id": "lab_id" }
- Add a new entry to the
-
Locate QuickLab and Lab IDs:
- Find the QuickLab ID from the URL: https://author.skills.network/quicklabs/:quicklab_id.
- To find the Lab ID, navigate to the Labs tab, hover over the lab, and note the Lab ID from the URL shown at the bottom left of your screen: https://author.skills.network/labs/:lab_id.
- Update the mirror.json with these IDs.
- Mirror Guide Setup:
- Initiate a
Mirror a guide to AWB
action. - Enter the
Guide name
andTo
Options -
- For
To
,prod
for publishing the lab to the world,staging
for saving the lab without publishing.
- For
To contribute to this project, please follow these steps:
-
Create a Pull Request (PR):
- Always create a pull request targeting the
staging
branch when you wish to make updates. This is where all initial changes should be made and reviewed.
- Always create a pull request targeting the
-
Review Process:
- Have someone review your content changes in the
staging
branch. This ensures all updates meet the project's standards and requirements before they are deployed.
- Have someone review your content changes in the
-
Deploy to Staging:
- Use the
Mirror a guide to AWB
GitHub Action to deploy your updates to staging. Set the deployment target by selectingstaging
in the action's inputs. This step saves the content on the Author Workbench (AWB) side for further review.
- Use the
-
Approval and Merging:
- Once your changes are reviewed and approved in the
staging
branch, merge them into theprod
branch.
- Once your changes are reviewed and approved in the
-
Publish to Production:
- After merging to
prod
, use theMirror a guide to AWB
GitHub Action again to publish your content. Set theTo
parameter toprod
to finalize the publication on the production environment.
- After merging to
Following this workflow ensures a structured and error-minimized deployment of content, maintaining high standards of quality and consistency.