You only need to do these once locally.
- Install Quarto
- Install the VS Code Quarto extension
- Install uv to manage your Python environments (recommended if you want to execute code in your presentation)
- Click on "Use this template" -> "Create a new repository"
- Choose a repository name that starts with
slides-(this should help us spot quarto presentation repositories at a glance, especially important if they proliferate) - Clone the newly created repository and navigate to its root folder
Note
You can skip this step if you don't require any code execution in your presentation.
If you have additional requirements for your execution environment (e.g. your Python package) append them to requirements.txt.
We recommend using uv to manage your Python environment:
- Create a new environment with
uv venv --python=3.13. Make sure the Python version matches the one used in your GitHub Actions workflow. - Activate the environment with
source .venv/bin/activate - Install the required packages with
uv pip install -r requirements.txt
Warning
Make sure Quarto is using the correct Python environment
by setting the QUARTO_PYTHON environment variable.
An easy way to do this once you have activated the environment is:
export QUARTO_PYTHON=$(which python)- Edit the
index.qmdfile to your liking, using the example slides as a guide. Additional images should be placed in theimg/folder whereas references should be added to thereferences.bibfile in BibTeX format. - To build the presentation locally, you can either use the VS Code extension's GUI ("Render" button) or run
quarto render index.qmdin the terminal. - The rendered presentation will be available as
build/index.htmlin the root folder. Note that thebuild/folder is included in.gitignoreto avoid committing generated files to the repository.
Tip
If you want to preview the rendered slides as you're editing them, you can type quarto preview index.qmd in the terminal.
For the first deployment:
- Create an empty
gh-pagesbranch:git checkout --orphan gh-pages git reset --hard # make sure all changes are committed before running this! git commit --allow-empty -m "Initialising gh-pages branch" git push origin gh-pages
- Review the repository Settings/Pages to ensure that deployment is enabled from the
gh-pagesbranch. - Make the first release on GitHub, tagged with a version number (see below for versioning schemes).
For all subsequent deployments:
- Simply make a new release tagged with the appropriate version number. For presentations, we prefer a date-based versioning scheme, e.g.
YY.MMorYY.MM.DD. You are encouraged to include some additional information on location, event, etc. in the release notes. If the release is a work-in-progress, appenddevto the version tag (YY.MM.dev) and tick the "Set as a pre-release" checkbox. - GitHub actions will take care of the rest (see example deployment here)
- Deployed presentations can be found at
https://{USER}.github.io/{REPOSITORY-NAME}/#/title-slide. For repositories of the neuroinformatics-unit organisation, this redirects tohttps://neuroinformatics.dev/{REPOSITORY-NAME}/#/title-slide