trentuna/asw
8
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

asw-v01: archive deferred content (packs, site, lab, legacy examples)

Browse source 
- 2.1: packs/ -> archive/packs/
- 2.2: site/ -> archive/site/
- 2.3: src/lab/ -> archive/lab/
- 2.4: examples/ -> archive/examples-legacy/ (SSI-based)
This commit is contained in:
exe.dev user 2026-06-07 10:39:21 +02:00
parent 416fe2f180
commit e47a9f4401
173 changed files with 11 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

17
site/content/docs/packs/overview.md
View file

@ -1,17 +0,0 @@
---
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.