How bradleyboehmke/intro-to-r-bootcamp works
Project type and purpose
• This is not a service-oriented app but a static content generator for an “Intro to R” bootcamp.
• It houses source materials (R scripts and R Markdown), data sets, styling assets, and generates HTML that is published as a course website on GitHub Pages.
File structure
• Top-level:
• R project files and IDE state (“.Rproj”, “.Rproj.user/…”) – environment metadata
• README files (“README.Rmd”, “README.md”, “README.html”) – project description
• Folders:
– data/ – raw input data files (CSV, TSV, Excel)
– styles.css – site-wide styling
– “Files – students” & “Files – teacher” – finalized lesson outputs (R, HTML)
– Working files/ – in-progress Rmd notebooks, caches, and generated HTML
• No backend server or database; the “engine” is R/knitr generating static HTML.
README for additional insights
• Confirms this is teaching material for a short R course.
• Final site is deployed to an external GitHub Pages repo.
• Licensed CC-SA 2.0.
a. Main components
1. Source Layer
– R Markdown (.Rmd) and R scripts (.R) under Working files/
– Data assets in data/
– Styling and assets (styles.css, images/)
2. Build Engine
– R + knitr/rmarkdown converting .Rmd → HTML + figures
– Caching mechanism (Working files/*_cache/)
3. Output Layer
– Rendered HTML & R scripts in “Files – students” and “Files – teacher”
4. Hosting/Distribution
– Push to GitHub Pages (uc-r.github.io/r_bootcamp)
b. Relationships & interactions
– Data files feed into Rmd notebooks
– Rmd + CSS + images → processed by knitr → HTML pages + supporting assets (figures, cache)
– Final HTML and static assets uploaded to GitHub repository for hosting
c. Architectural patterns & design principles
– Static site generation (SSG) pattern
– Clear separation of source (editable Rmd) vs generated output (HTML folders)
– Content reuse: single data sources feed multiple lessons
d. Key technologies & libraries
– R, RStudio, knitr, rmarkdown
– Git & GitHub Pages for versioning & hosting