We may want to deprecate the bookdown option once Quarto and/or litedown are fully supported. The main reason we use it is because it enables equation referencing, but that relies on MathJax and rmarkdown doesn't support embedding MathJax so that it works offline. (See discussion in #90).
If bookdown is used for a package vignette, it adds a lot of dependencies to the package. So I think the front_matter_type for bookdown vignettes should be "bookdown_vignette" so that we can implement alternative "vignette" outputs. I think we may also want to rename to argument to output_type or output_format as the choice may affect more than the front matter (e.g. syntax for equation label/references). Since different output types may have different pros and cons (mainly balancing richness of features against Rpackage/system dependencies), I would not set any default and require the user to make a conscious choice.
We may want to deprecate the bookdown option once Quarto and/or litedown are fully supported. The main reason we use it is because it enables equation referencing, but that relies on MathJax and rmarkdown doesn't support embedding MathJax so that it works offline. (See discussion in #90).
If bookdown is used for a package vignette, it adds a lot of dependencies to the package. So I think the
front_matter_typefor bookdown vignettes should be "bookdown_vignette" so that we can implement alternative "vignette" outputs. I think we may also want to rename to argument tooutput_typeoroutput_formatas the choice may affect more than the front matter (e.g. syntax for equation label/references). Since different output types may have different pros and cons (mainly balancing richness of features against Rpackage/system dependencies), I would not set any default and require the user to make a conscious choice.