build-pkgdown-site
About
This Claude Skill builds and deploys a pkgdown documentation site for R packages to GitHub Pages. It covers configuration, theming, article organization, and deployment methods like branch-based or GitHub Actions. Use it to create or customize a package's documentation site, fix deployment issues, or migrate between deployment methods.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/build-pkgdown-siteCopy and paste this command in Claude Code to install this skill
Documentation
Build pkgdown Site
Config + deploy pkgdown doc site for R pkg.
Use When
- Doc site for R pkg
- Customize pkgdown layout, theme, nav
- Fix 404s on deployed pkgdown site
- Migrate between deploy methods
In
- Required: R pkg w/ roxygen2 docs
- Required: GitHub repo
- Optional: Custom theme/branding
- Optional: Vignettes to include as articles
Do
Step 1: Init pkgdown
usethis::use_pkgdown()
Creates _pkgdown.yml + adds pkgdown to .Rbuildignore.
→ _pkgdown.yml in project root. .Rbuildignore has pkgdown entries.
If err: Install pkgdown via install.packages("pkgdown"). _pkgdown.yml already exists → fn updates .Rbuildignore w/o overwriting config.
Step 2: Configure _pkgdown.yml
url: https://username.github.io/packagename/
development:
mode: release
template:
bootstrap: 5
bootswatch: flatly
navbar:
structure:
left: [intro, reference, articles, news]
right: [search, github]
components:
github:
icon: fa-github
href: https://github.com/username/packagename
reference:
- title: Core Functions
desc: Primary package functionality
contents:
- main_function
- helper_function
- title: Utilities
desc: Helper and utility functions
contents:
- starts_with("util_")
articles:
- title: Getting Started
contents:
- getting-started
- title: Advanced Usage
contents:
- advanced-features
- customization
Critical: Set development: mode: release. Default mode: auto causes 404s on GitHub Pages (appends /dev/ to URLs).
→ _pkgdown.yml valid YAML w/ url, template, navbar, reference, articles appropriate for pkg.
If err: Validate YAML syntax w/ online linter. All fn names in reference.contents match actual exported fns.
Step 3: Build Locally
pkgdown::build_site()
→ docs/ dir created w/ complete site incl index.html, fn ref pages, articles.
If err: Common issues: missing pandoc (set RSTUDIO_PANDOC in .Renviron), missing vignette deps (install suggested pkgs), broken examples (fix or wrap in \dontrun{}).
Step 4: Preview
pkgdown::preview_site()
Verify nav, fn ref, articles, search work.
→ Site opens in browser at localhost. Nav links work, ref pages render, search returns results.
If err: Preview doesn't open → manually open docs/index.html. Pages missing → check devtools::document() ran before build.
Step 5: Deploy to GitHub Pages
Method A: GitHub Actions (Recommended)
See setup-github-actions-ci skill for pkgdown workflow.
Method B: Manual Branch Deploy
# Build site
Rscript -e "pkgdown::build_site()"
# Create gh-pages branch if it doesn't exist
git checkout --orphan gh-pages
git rm -rf .
cp -r docs/* .
git add .
git commit -m "Deploy pkgdown site"
git push origin gh-pages
# Switch back to main
git checkout main
→ gh-pages branch on remote w/ site files at root.
If err: Push rejected → ensure write access. Using GitHub Actions instead → skip + follow setup-github-actions-ci.
Step 6: Configure GitHub Pages
- Repo Settings > Pages
- Source: "Deploy from a branch"
- Select
gh-pagesbranch,/ (root)folder - Save
→ Site available at https://username.github.io/packagename/ within min.
If err: 404 → verify Pages source matches deploy method (branch deploy needs "Deploy from a branch"). Check development: mode: release in _pkgdown.yml.
Step 7: Add URL to DESCRIPTION
URL: https://username.github.io/packagename/, https://github.com/username/packagename
→ DESCRIPTION URL has pkgdown site URL + GitHub repo URL, comma-separated.
If err: R CMD check warns invalid URLs → verify pkgdown site actually deployed + accessible before adding.
Check
- Builds locally w/o errs
- All fn ref pages render
- Articles/vignettes accessible + render
- Search works
- Nav links correct
- Deploys to GitHub Pages
- No 404s
-
development: mode: releaseset
Traps
- 404 after deploy: Almost always
development: mode: auto(default). →mode: release - Missing ref pages: Fns must be exported + documented. Run
devtools::document()first - Broken vignette links: Use
vignette("name")syntax for cross-refs, not file paths - Logo not showing: Place at
man/figures/logo.png, ref in_pkgdown.yml - Search not working: Needs
urlfield in_pkgdown.ymlset correctly - Wrong R binary hybrid sys: WSL/Docker →
Rscriptmay resolve to cross-platform wrapper vs native. Checkwhich Rscript && Rscript --version. Prefer native (e.g.,/usr/local/bin/Rscripton Linux/WSL). See Setting Up Your Environment
→
setup-github-actions-ci— automated pkgdown deploy workflowwrite-roxygen-docs— fn docs that appear on sitewrite-vignette— articles in site navrelease-package-version— trigger rebuild on release
GitHub Repository
Related Skills
content-collections
MetaThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
polymarket
MetaThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
creating-opencode-plugins
MetaThis skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
sglang
MetaSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
