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
It would be good to change the project to use Quarto at some point: https://quarto.org/
It has been out for 2 years now, so a lot of the initial bugs have been weeded out.
This is the next generation technical publishing system developed by the Rstudio team. It merges Rmarkdown and Bookdown and also allows for any language to be used in the code chunks (I've used others and had to make hacks to do so in Rmarkdown).
Pros: Cleaner codebase, no dependency on bookdown and Rmarkdown packages. Stay up-to-date with the technology.
Cons: I think we need to do post-processing (e.g. the fix_envs() function) with Lua, not R. A lot of time to rewrite the post-processing part and test everything.
The text was updated successfully, but these errors were encountered:
It would be good to change the project to use Quarto at some point: https://quarto.org/
It has been out for 2 years now, so a lot of the initial bugs have been weeded out.
This is the next generation technical publishing system developed by the Rstudio team. It merges Rmarkdown and Bookdown and also allows for any language to be used in the code chunks (I've used others and had to make hacks to do so in Rmarkdown).
Pros: Cleaner codebase, no dependency on bookdown and Rmarkdown packages. Stay up-to-date with the technology.
Cons: I think we need to do post-processing (e.g. the
fix_envs()
function) with Lua, not R. A lot of time to rewrite the post-processing part and test everything.The text was updated successfully, but these errors were encountered: