First content merge to the new participant website. (#2) #2

	name: Build website

	on:
	push:
	branches:
	- main

	# Limit token permissions for security
	permissions: read-all

	jobs:
	build-deploy:
	runs-on: ubuntu-latest
	# Stop builds from running more than one at a time, to save resources and also
	# to limit conflicts when uploading to the hosting provider.
	concurrency:
	group: build-website-group
	cancel-in-progress: true
	permissions:
	contents: write
	pages: write
	steps:
	# This is a useful security step to check for unexpected outbound calls from the runner,
	# which could indicate a compromised token or runner.
	- name: Harden the runner (Audit all outbound calls)
	uses: step-security/harden-runner@20cf305ff2072d973412fa9b1e3a4f227bda3c76 # v2.14.0
	with:
	egress-policy: audit

	- name: Check out repository
	uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1

	- name: Set up Quarto
	uses: quarto-dev/quarto-actions/setup@8a96df13519ee81fd526f2dfca5962811136661b # v2.2.0

	# NOTE: Needs the contents and pages write permissions (used above).
	- name: Render and publish to GitHub Pages
	uses: quarto-dev/quarto-actions/publish@8a96df13519ee81fd526f2dfca5962811136661b # v2.2.0
	with:
	target: gh-pages
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Navigation Menu