Documentation & Shinylive Deployment

[coatless]

Right now, documentation is being generated and, then, committed into the repository's docs folder before being served through GitHub pages.

With the addition of quarto and python variants, there will likely need to be changes on the documentation deployment front. For the minimum, we may need to set up an index page leading into the slide decks for each variant. Maybe introduce a Quarto documentation portal that has subpages to: {pkgdown} website, quarto, and quartodocs for python website?

Another hiccup would be if we add shinylive components as that would greatly bloat the repositories size; we would need to switch to using deployments through artifacts and GitHub actions.

[gadenbuie]

I've been envisioning a Quarto webpage to unite the three packages. Quarto's a natural fit for the extension and with quartodoc it'll be straightforward to integrate the Python package docs into the webpage. For the R package, we could use altdoc or just use a pkgdown site deployed into a subfolder.

I agree that we should get the rendered page out of the main branch and into gh-pages, especially if we want to have a shinylive demos.

[coatless]

Okay, I'm probably going to move first to switch the existing deploy over to a GitHub action with artifact and, then, tackle the quarto website.