Designing and Deploying Internal Quarto Templates
summary
Shows how an organization packages Quarto templates inside an internal R package (files placed under inst/_extensions) so a single function (create_zelus_html) copies logos CSS/SCSS, installs fonts, creates a ready-to-render .qmd in the user’s working directory and opens it. Uses HTML/CSS tricks inspected via dev tools and Mozilla Web Docs, supports HTML/PDF/slides (Typst migration planned), and keeps templates private instead of public GitHub repos.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:07Why internal Quarto templates matter
- 2:33Benefits of consistent templates
- 3:58Template example and content
- 5:44Customizing templates with CSS
- 7:09Browser dev tools for CSS
- 8:56CSS and HTML learning resources
- 9:40Sharing Quarto templates
- 10:43Packaging templates in R packages
- 11:45File structure for Quarto templates
- 12:28Automating template deployment
- 13:32Demo: template creation and usage
- 14:15Key takeaways
- 15:22Q&A
related talks
20mStyling and Templating Quarto Documents
21mWebsites & Books & Blogs, oh my! Creating Rich Content with Quarto
21mWebsites & Books & Blogs, oh my! Creating Rich Content with Quarto
21mQuarto for the Curious
16mThese are a few of my favorite things (about Quarto presentations)
12mCreating a Design System for Shiny and RMarkdown
41mPublishing Jupyter Notebooks with Quarto
20mTheming Made Easy: Introducing brand.yml
