building-static-sites

Export Next.js sites as static HTML with YAML content.

1|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/bryonjacob/aug --skill building-static-sites
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-static-sites
Source: https://github.com/bryonjacob/aug/tree/main/aug-web/skills/building-static-sites
Command: npx skills add https://github.com/bryonjacob/aug --skill building-static-sites

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams building marketing sites, docs, portfolios, or blogs often face the overhead of bundling data and assets for a fast, static deployment. This Skill streamlines creating static exports of Next.js sites, ensuring SEO-friendly markup and predictable build outputs.

Core Features & Use Cases

  • Static export workflow: convert Next.js apps into a production-ready out/ directory for hosting on GitHub Pages, Netlify, or Vercel.
  • Content-driven templates: organize site data with YAML files (content/global.yaml, content/pages/*.yaml) for consistent content sourcing.
  • Image handling and SEO readiness: guidance for image optimization and safe SEO metadata integration.
  • Deployment-ready outputs: ready-to-publish static sites that require no server-side rendering.

Quick Start

Create a Next.js project configured for static export, populate YAML content under content/, then run the build and export steps to produce the out/ directory.

Frequently Asked Questions about building-static-sites

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export a Next.js app as a static site?

To export a Next.js app as a static site, configure next.config.ts for static export and run the build process to generate a production-ready out/ directory containing fast static HTML.

What is the best way to build SEO-friendly static pages from YAML content?

Building SEO-friendly static pages from YAML content involves organizing site data in YAML files under content/ and using a static export workflow to preserve content structure and generate predictable markup.

Can I host a Next.js static export on GitHub Pages or Netlify?

Yes, a Next.js static export produces an out/ directory that is fully deployment-ready and can be hosted directly on static hosting platforms like GitHub Pages, Netlify, or Vercel.

Does static export work for marketing sites and blogs without server-side logic?

Static export works perfectly for marketing sites, documentation pages, portfolios, and blogs that require fast static delivery without server-side rendering or server-side logic.

What do I need to set up before exporting a Next.js site to static HTML?

Before exporting a Next.js site to static HTML, you need Next.js tooling installed, a next.config.ts configured for static export, and YAML-based content structured under the content/ directory.

Are there limitations when using Next.js static export for production delivery?

Next.js static export is limited to sites without server-side logic, making it unsuitable for applications requiring dynamic server-side rendering while targeting fast static delivery for content-driven pages.