How bsenst/praxis-it works
Project type and purpose
• This is a static documentation/book site built with Quarto (“Praxis-IT” Quarto book).
• Source content lives in .qmd (Quarto Markdown) files; the final site is rendered to HTML and deployed via GitHub Pages.
File structure
• Top-level files:
• _quarto.yml (Quarto project configuration)
• README.md (project overview)
• .github/workflows/publish.yml (CI workflow for build & deploy)
• .nojekyll (instructs GitHub Pages not to use Jekyll)
• Content directory: dozens of *.qmd files (chapters), an assets/ folder for images/CSS/JS, plus citation files (referenzen.bib, referenzen.qmd).
• Build tooling: Quarto CLI invoked in CI to convert .qmd → HTML.
README
• Confirms use of Quarto CLI and GitHub Codespaces for local dev.
• Deployment target is GitHub Pages (via publish.yml).
Main components and interactions
a. Source content
• .qmd files (chapters, sections)
• _quarto.yml (book layout, theme, navigation)
• assets/ (images, styles, GTM snippets)
• citation files
b. Build environment
• Developer workstation or GitHub Codespaces (with Quarto CLI + TinyTeX)
• Quarto CLI: processes .qmd + config → HTML site
c. CI/CD pipeline
• GitHub Actions (publish.yml): triggers on push, runs Quarto build steps
• Installs Quarto CLI, runs quarto render, archives output
• Publishes to GitHub Pages branch
d. Hosting
• GitHub Pages serves the generated static HTML at https://bsenst.github.io/praxis-it
Architectural patterns/design principles
• Static Site Generation (SSG): content separated from rendering logic
• CI/CD for reproducible builds and automated deployment
• Single‐repository monolith for content, build scripts, and deployment config
• Clear separation of concerns: content (QMD) vs. tooling (Quarto CLI) vs. infrastructure (GitHub Actions + Pages)