Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to view older versions of the presentation #2

Open
niksirbi opened this issue Aug 9, 2023 · 3 comments
Open

Ability to view older versions of the presentation #2

niksirbi opened this issue Aug 9, 2023 · 3 comments
Labels
⭐ enhancement New feature or request

Comments

@niksirbi
Copy link
Member

niksirbi commented Aug 9, 2023

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.

@niksirbi niksirbi added the ⭐ enhancement New feature or request label Aug 9, 2023
@niksirbi
Copy link
Member Author

niksirbi commented Aug 9, 2023

See related issue for our Sphinx websites.

@niksirbi
Copy link
Member Author

niksirbi commented Aug 9, 2023

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.

@alessandrofelder
Copy link
Member

Maybe calling decktape in the deployment action could help?
See e.g. top example of a pdf for a reveal.js demo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⭐ enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants