vigilio opened issue trentuna/asw#24

vigilio
2026-04-10T17:44:54Z

24#[PLAN] Reconcile trentuna/asw with agentic-semantic-web legacy#

Context

~/projects/agentic-semantic-web/ is the original ASW framework — no git, no Forgejo repo. It has significant work NOT yet in trentuna/asw:

What we ported

src/layers/*.css → assets/css/layers/ (M1)

lab/hugo-demo/content/ → frontmatter audited, ready for M2 import

lab/hugo-demo/themes/asw-hugo/layouts/ → partially ported (M2)

What we have NOT ported

Packs (server integration kits):

packs/hugo/ — Hugo theme (the mature asw-hugo theme)

packs/nginx/ — nginx SSI config

packs/flask/ — Flask integration

packs/pandoc/ — Pandoc template

packs/apache/, packs/caddy/, packs/python/

Templates (standalone HTML):

templates/doc.html, page.html, pattern.html, example.html

Examples (component demos):

examples/charts/, examples/components/, examples/content/, examples/layout/, examples/vault/

Docs (HTML docs site):

docs/ — full documentation site (introduction, philosophy, typography, vocabulary, design-tokens, utilities, charts, components, layout, vault, packs)

docs/llms.txt — LLM-readable spec

Lab (experiments):

lab/kitchen-sink.html, lab/charts/, lab/css-art.html, lab/fonts.html

Build system:

build.sh — concatenates layers into agentic.css

package.json — dependencies

Live artifacts:

agentic.css — compiled single-file CSS (symlinked from nginx at /agentic.css)

index.html — landing page

web-fonts.css — font loading

Decision needed (Ludo)

1. What is trentuna/asw? Is it:
a) The Hugo site only (asw.trentuna.com) — framework stays in agentic-semantic-web
b) The entire framework — agentic-semantic-web becomes legacy, everything moves to trentuna/asw
c) Two repos: trentuna/asw (site) + trentuna/asw-framework (CSS framework with packs/docs/examples)

2. Packs: Do the server integration packs move to trentuna/asw or stay separate?

3. Docs site: The HTML docs at /docs/ are substantial. Convert to Hugo content pages, or keep as static HTML?

4. agentic.css: The compiled single-file is still served by nginx. When trentuna/asw is the canonical source, this symlink needs updating.

5. llms.txt: This is valuable. Where does it live in the new structure?

What's clean now (this session)

M1: Hugo scaffold, PostCSS pipeline, push-to-render webhook ✅

M2: Content migration (frontmatter audited, issues created) — partially done

M3: oklch palette, dead code purge ✅

git.trentuna.com: live, Forgejo ROOT_URL proper ✅

CSS architecture: main.css (manifest) → 01-asw.css (framework) → layers 02-09

Palette: --color-1 to --color-16, --palette-hue for theming, fixed-hue state colors

Remaining M2 issues (open)

#9-13: Content port (docs, papers, posts, vault)

#14-16: Layout/partial/shortcode port

#17: hugo.toml merge

#18: Gate review

#19: Retire asw-site/ to dustbin

Known tech debt

24 TODO-tagged named palette refs in layers 02-09 (need --syntax-* token aliases for Chroma highlighting)

palette-test.html in static/ — useful demo, keep or move to docs

agentic-semantic-web/ has no git — should get a Forgejo repo as archive at minimum