You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
One semi-solution could be to also export the presentations as standalone HTML pages with embedded resources and archive all the older versions somewhere. The HTML file may get too large for Git over time, but we could perhaps push them to a GIN repo. All of this would be automated with gh actions, i.e:
Every time a new version is deployed on gh-pages, it is also exported as <name>_<tag>.html and pushed to the archive.
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.
The text was updated successfully, but these errors were encountered: