Rendering Book

Render the "Data Science with Python" book into HTML or PDF formats using Quarto.

Why? Automates the Quarto commands required to build the book, ensuring consistent output for both web (HTML) and print (PDF) formats.

Quick Start

1. Check Dependencies: Ensure Python venv and Quarto are installed.
2. Activate venv: source .venv/bin/activate
3. Choose Format: HTML (default) or PDF.
4. Execute: Run the appropriate command.
5. Verify: Check logs and output files.

Prerequisites

• Python Environment: Must have Python 3.11+ installed.
• Virtual Environment: Create and activate venv:
  bashCopy

  python -m venv .venv
  source .venv/bin/activate
  pip install -r requirements.txt
  

• Quarto: Must have Quarto installed:
  bashCopy

  brew install --cask quarto
  

Workflow Steps

1. Preview (Development)

Live preview with auto-reload on file changes.

source .venv/bin/activate
quarto preview

[!TIP] The preview will open automatically in your browser at http://localhost:4XXX.

2. Render HTML

This is the default and most common format.

source .venv/bin/activate
quarto render

[!TIP] The output will be generated in docs/index.html.

3. Render PDF

Use this for generating the print version.

[!NOTE] PDF generation uses LaTeX (LuaLaTeX). TinyTeX will auto-install required packages.

[!IMPORTANT] Always use --no-clean to preserve the docs/data/ folder which contains static datasets.

source .venv/bin/activate
quarto render --to pdf --no-clean

4. Quality Check

After rendering, verify output:

ls -la docs/index.html
ls -la docs/*.pdf

Verification

Verify the output exists and was recently modified (within last 5 minutes):

# Verify HTML
find docs/ -name "index.html" -mmin -5

# Verify PDF
find docs/ -name "*.pdf" -mmin -5

Troubleshooting

Common Mistakes

1. Running without venv active: Always activate the virtual environment first.

   bashCopy

   # Wrong - will fail
   quarto render
   
   # Correct
   source .venv/bin/activate && quarto render
   

2. Editing docs/ directly: Never edit files in docs/. They get overwritten on each render. Edit the .qmd source files instead.

3. Forgetting to save .qmd files: Ensure all changes are saved before rendering.

Sample Output

Successful HTML build:

Output created: docs/index.html

Successful preview:

Watching files for changes
Browse at http://localhost:4846/

Quality Rules

• Always activate venv: Ensure Python dependencies are available.
• Check output before committing: Always verify that docs/index.html was updated.
• Clean build for major changes: If output looks wrong, delete freeze and rebuild:
  bashCopy

  rm -rf _freeze docs/* && quarto render