Rendering Book

Render the "Data Science with R" book into HTML or PDF formats using R's bookdown package.

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

Quick Start

1. Check Dependencies: Ensure R and bookdown are installed.
2. Pre-flight: Check _output.yml for deprecated flags.
3. Choose Format: HTML (default) or PDF (slow, heavy build).
4. Execute: Run the appropriate command.
5. Verify: Check logs and output files.

Prerequisites

• R Environment: Must have R installed.
• Packages: bookdown package must be installed.

  if (!require("bookdown")) install.packages("bookdown")
  

Workflow Steps

0. Pre-flight Check (Optional)

Check _output.yml for deprecated Pandoc arguments.

grep "highlight-style" _output.yml

[!TIP] If found, consider replacing with --syntax-highlighting to avoid warnings.

1. Render HTML (Gitbook)

This is the default and most common format.

Rscript -e "bookdown::render_book('index.Rmd', 'bookdown::gitbook')"

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

2. Render PDF

Use this for generating the print version.

[!NOTE] PDF generation involves heavy LaTeX compilation and may download large assets. Expect this to take significantly longer than HTML.

Rscript -e "bookdown::render_book('index.Rmd', 'bookdown::pdf_book')"

[!CAUTION] PDF generation requires a LaTeX installation (like TinyTeX). If it fails, try installing TinyTeX in R: tinytex::install_tinytex().

3. Render All Formats

Generates all formats defined in _output.yml.

Rscript -e "bookdown::render_book('index.Rmd', 'all')"

4. Quality Check (Log Analysis)

After rendering, check for hidden warnings that don't fail the build:

grep -E "Warning|undefined|multiply-defined" Data-Science-with-R.log

Verification

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

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

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

Troubleshooting

Common Mistakes

1. Running from wrong directory: Always run from the book root (where index.Rmd lives).

   # Wrong - will fail
   cd docs && Rscript -e "bookdown::render_book(...)"
   
   # Correct
   Rscript -e "bookdown::render_book('index.Rmd', 'bookdown::gitbook')"
   

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

3. Forgetting to save .Rmd files: Ensure all changes are saved before rendering. Unsaved changes won't appear in output.

4. Running PDF before HTML: If you've never built the book, build HTML first to catch errors faster. PDF builds are slow and LaTeX errors are harder to debug.

Sample Output

Successful HTML build:

Output created: docs/index.html

Successful PDF build:

Output created: docs/Data-Science-with-R.pdf

Failed build (missing package):

Error in library(ggplot2) : there is no package called 'ggplot2'
Calls: ... -> source -> withVisible -> eval -> eval -> library
Execution halted

[!TIP] Package errors show which package is missing. Install it with install.packages("package_name").

Quality Rules

• Do not use _build.sh: The legacy script is deprecated.
• Check _output.yml: Ensure the configuration file exists before rendering.
• Verify output before committing: Always check that docs/index.html or docs/*.pdf was updated.
• Run pre-flight check for new setups: Check for deprecated Pandoc flags before first build.
• Clean build for major changes: If output looks wrong after structural changes, delete docs/ and rebuild:

  rm -rf docs/* && Rscript -e "bookdown::render_book('index.Rmd', 'bookdown::gitbook')"
  

Testing

Evaluation Scenarios

Validation Commands

# Verify HTML build success
test -f docs/index.html && echo "HTML OK" || echo "HTML MISSING"

# Verify PDF build success
test -f docs/Data-Science-with-R.pdf && echo "PDF OK" || echo "PDF MISSING"

# Check for build warnings
grep -c "Warning" docs/*.log 2>/dev/null || echo "No warnings"