Current status
The idea is that we generate one repository per project using this repo as a template. Each time we make a new presentation on that project, we update that repo and tag a new release, triggering the website build (via Quarto) and deployment on gh-pages.
Problem
According to the above workflow, the website will always display the latest version of a presentation. The only way to view an older version would be to check out an old release/commit and build it with Quarto locally.
Vision
It would be nice to have multiple versions of a presentation deployed, navigable with some sort of version switcher dropdown.
Current status
The idea is that we generate one repository per project using this repo as a template. Each time we make a new presentation on that project, we update that repo and tag a new release, triggering the website build (via Quarto) and deployment on gh-pages.
Problem
According to the above workflow, the website will always display the latest version of a presentation. The only way to view an older version would be to check out an old release/commit and build it with Quarto locally.
Vision
It would be nice to have multiple versions of a presentation deployed, navigable with some sort of version switcher dropdown.