Ludo
502b2e8266
Navigation: Docs, Layouts, Lab (simplified from 6 items) Layouts gallery: card grid showing all available page layouts with live links to demo pages. Docs restructure: 8 auto-generated sidebar sections (Getting Started, Typography, Core, Content, Components, Reference, Vault, Packs) with 20 new stub pages. Each stub has inline HTML demos that ASW styles directly. New Hugo layout template for layouts/ section. Decap CMS nav updated. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
17 lines
846 B
Markdown
17 lines
846 B
Markdown
---
|
|
title: "Packs Overview"
|
|
description: "What ASW packs are, how they extend the core stylesheet, and when to use them."
|
|
type: docs
|
|
weight: 51
|
|
date: 2026-04-11
|
|
tags: ["packs", "overview"]
|
|
ai-disclosure: "generated"
|
|
ai-model: "claude-sonnet-4-6"
|
|
ai-provider: "Anthropic"
|
|
---
|
|
|
|
Packs are thin integration layers that connect ASW to a specific tool or pipeline. They do not add new CSS — they configure the tool so that its output maps to the semantic HTML that ASW already styles.
|
|
|
|
The core `asw.css` works with any HTML. Packs handle the glue: Hugo shortcodes, nginx config snippets, Pandoc templates, and so on. Use a pack when you want zero-configuration output from a supported tool, and skip it if you are generating HTML yourself.
|
|
|
|
Available packs: **Hugo**, **nginx**, **Pandoc**. Each pack lives in `packs/<name>/` in the ASW repository.
|