This repository is a template for courses and webpages for self-learning.
In the pop-up window:
- Choose an organisation where the repository will be hosted
- Enter a name for the new repository (keep in mind that this will be part of the URL)
- Decide if the repository should be Public (most likely) or Private
- Make sure to tick
Include all branches
- Click
Create repository from template
Go to settings and select Collaborators and teams
under Access
in the left side menu
- Click one of the green buttons
add people
oradd teams
- Select a person or a team to invite
- Select the appropriate role
- Click
add user to this repository
Modify and add information about the new workshop/course.
The tmp folder just supports this README file, so you can delete it after modifying it.
The main branch is a folder template to create the actual materials for a workshop session. Notebooks, exercises and materials associated to them (like images) should be here. Maintaining only one version of the coding material is essential to ensure consistency and avoid confusion. Please do not make copies on the server or locally; use version control for edits instead.
On the other hand, actual data and slides are too big for a GitHub repository. Read the next section about hosting data in a zenodo repository. Consider what is the best strategy for hosting or sharing slides. For collaborative questions, there is a copy in SharePoint.
Zenodo is an Open Science data repository from the OpenAIRE project supported by CERN to ensure that everyone can join in Open Science. It allows researchers to upload many different types of data and gives each repository a unique and citeable identifier (DOI). We can also link a GitHub repository and whenever you create a release for the GitHub repo, it will give it as well a DOI. Follow this link for instructions We are using Zenodo to deposit complementary materials and data necessary for the course, relieving the size of the GitHub repo. It also makes it easier to update the materials and use them in the UCloud apps.
The webpage-mkdocs branch contains all the content needed to create and deploy the self-learning part of the course/workshop.
For more instructions, including how to set up GitHub Pages and automatic deploying of the webpage, check the README.md file from the webpage branch.
Note: MkDocs requires a lot of plugins, which can be deprecated over time. You can use the branch webpage-quarto
which does not require extra packages and will be more longeve.
The webpage-quarto branch contains - as above - an example of a webpage to create and deploy the self-learning part of the course/workshop. Go to the branch to see what you need (quarto
and a few R
packages) to get going.
The tool we use to create the website is Quarto with the theme material
. Instead of relying on Quarto, we use GitHub Actions to automatically build and deploy the website.
The source content is stored in the "webpage" branch. Whenever a commit is pushed to this branch, a GitHub workflow is triggered to build the Quarto website and deploy it to a new branch called "gh-pages." This branch serves as the live version of the website. Using this automated workflow ensures that updates to the website are consistent and immediate after changes are made in the "webpage" branch.'