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.
Right now, documentation is being generated and, then, committed into the repository's
docsfolder before being served through GitHub pages.With the addition of
quartoandpythonvariants, 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, andquartodocsfor python website?Another hiccup would be if we add
shinylivecomponents as that would greatly bloat the repositories size; we would need to switch to using deployments through artifacts and GitHub actions.