build-pkgdown-site

Solid

Build and deploy a pkgdown documentation site for an R package to GitHub Pages. Covers _pkgdown.yml configuration, theming, article organization, reference index customization, and deployment methods. Use when creating a documentation site for a new or existing package, customizing layout or navigation, fixing 404 errors on a deployed site, or migrating between branch-based and GitHub Actions deployment methods.

Web & Frontend 26 stars 4 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
48
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Build pkgdown Site Configure and deploy a pkgdown documentation website for an R package. ## When to Use - Creating a documentation site for an R package - Customizing pkgdown layout, theme, or navigation - Fixing 404 errors on a deployed pkgdown site - Migrating between deployment methods ## Inputs - **Required**: R package with roxygen2 documentation - **Required**: GitHub repository - **Optional**: Custom theme or branding - **Optional**: Vignettes to include as articles ## Procedure ### Step 1: Initialize pkgdown ```r usethis::use_pkgdown() ``` This creates `_pkgdown.yml` and adds pkgdown to `.Rbuildignore`. **Got:** `_pkgdown.yml` exists in the project root. `.Rbuildignore` contains pkgdown-related entries. **If fail:** Install pkgdown with `install.packages("pkgdown")`. If `_pkgdown.yml` already exists, the function will update `.Rbuildignore` without overwriting the config. ### Step 2: Configure `_pkgdown.yml` ```yaml 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_wi...

Details

Author
pjt222
Repository
pjt222/agent-almanac
Created
1 years ago
Last Updated
today
Language
R
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

github-pages

Arrange a project's README and GitHub Pages documentation into a consistent user-first layout: short README that links out, just-the-docs Jekyll site with a user-facing index, one page per user-facing feature (split into child pages when long), and a developer guide with technical sub-pages. TRIGGER when: setting up docs/ for a new project, adding a GitHub Pages site, writing or restructuring a README that will link to GH Pages, adding a new user-facing feature page, or asked to align docs with this project or bga-assistant. DO NOT TRIGGER when: editing unrelated docs outside docs/, working on a project that already has an incompatible docs framework (Docusaurus, MkDocs, VitePress, etc.).

0 Updated 1 weeks ago
AnotherSava
AI & Automation Solid

mykg-github-pages

Set up and maintain the GitHub Pages site for the mykg repo (SenolIsci/mykg) — a purpose-built pages/ folder (landing page adapted from README.md, blog posts, diagrams), built by a GitHub Actions workflow that runs Jekyll and deploys the result to a gh-pages branch. Use whenever the user wants to publish project documentation or blog articles as a website, create a landing page, turn the project into a public site, enable/configure/troubleshoot GitHub Pages or the gh-pages branch, add a new page/blog post/diagram to the published site, fix a broken/failing Pages build, or asks things like "can we get a docs site for mykg", "I want a landing page based on README", "publish this blog article", "is Pages enabled yet", "the pages workflow failed", or "add this new doc to the site". Also trigger on custom domain / CNAME requests for the project site. Scoped to the mykg repo's own pages/ folder and its gh-pages publishing pipeline — not for unrelated new project sites.

59 Updated 3 days ago
SenolIsci
API & Backend Listed

scaffold-pagesmith-docs

Stand up a brand-new Pagesmith documentation site from nothing — @pagesmith/docs wired to diagramkit, sample content, package skills installed, ending on a running preview. Triggers on "scaffold / bootstrap / stand up / start / create a new docs site", "new Pagesmith docs from scratch", "set up a docs site with diagrams". Writes to disk and runs local tooling (npm install, skills install, site build, dev server) — it configures a deploy target but NEVER deploys, pushes, or opens a PR; it prints the deploy command for a human to run. Confirms before touching an existing pagesmith.config. This is the greenfield counterpart to /adk:pagesmith (use that for an EXISTING site) and hands diagram-only work to /adk:diagramkit. It restates no package config schema, no engine flags, no palette — every version-sensitive authoring detail is delegated to the consumer's installed skills under node_modules.

0 Updated 5 days ago
sujeet-pro