Day 3 · 14:00
A zip of PDFs is not a knowledge system. A small website — the same idea as this course site — lets EXCO bookmark the latest brief, page backwards through months, and stop asking you for ‘the latest version’.
You will leave able to
- Configure a Quarto website with a navbar that matches a function’s rhythm.
- Render to a `docs/` folder GitHub Pages (or an internal equivalent) can serve.
- Set a simple publishing rule: main branch is the pack of record.
On the desk
- Quarto websites
- This repository’s _quarto.yml — see Repository
This course site is the teaching example. The original workshop taught R Markdown websites with a YAML navbar. Quarto’s _quarto.yml is the same idea, cleaned up. You will build a Commercial briefing site with five pages: Home, This month, Pipeline, Voice, Archive.
The config file
project: type: website output-dir: docs website: title: "Commercial brief" navbar: background: "#0B1F3A" left: - href: index.qmd text: Home - this-month.qmd - pipeline.qmd - voice.qmd - archive.qmd right: - text: Lagos Business School href: https://www.lbs.edu.ng/ format: html: theme: cosmo toc: trueindex.qmd
---title: "Commercial brief"--- The live pack of record for West Africa commercial.Updated when `main` is rendered. Do not circulate side copies.Render
# in the project folderquarto render # opens docs/index.html — that folder is what you publishOn GitHub: set Pages to serve /docs from main. Inside a bank: publish the same folder to an internal static host, SharePoint (as a last resort), or Posit Connect. The rule matters more than the vendor: there is one URL, it always reflects main, and side copies are how numbers fork.
Exercise 3.3
Navbar for your function
Write a _quarto.yml navbar with four items your function would actually use. If you cannot name four, you do not need a site yet — you need one Quarto PDF.