Skip to content

docs: README in example-led (Julia-package) form + EXPLAINME deep-dive#45

Merged
hyperpolymath merged 2 commits into
mainfrom
claude/docs-readme-explainme
Jun 23, 2026
Merged

docs: README in example-led (Julia-package) form + EXPLAINME deep-dive#45
hyperpolymath merged 2 commits into
mainfrom
claude/docs-readme-explainme

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

What

The core documentation upgrade you asked for.

README.adoc — reshaped into the canonical Julia-package idiom (the "Axiom.jl shape"): clean badges → one-line pitch → a concrete runnable example up front (source tree → casket-ssg build → accessible _site/) → install → differentiators → implemented-vs-planned features → docs links → where-it-fits → license. It now leads with the real positioning — accessibility-first, metadata-driven; verified + agent-native as the trajectory — instead of the generic "pure functional SSG in Haskell". Stays honest (the truthed implemented/planned split is preserved).

EXPLAINME.adoc (new) — developer deep-dive: build pipeline, module map (CasketGnosis + the Gnosis.* set, and the legacy Casket.hs), accessibility invariants (FlexiText/Tri-Guard, addThScope, accessible default theme), content/metadata model, known gaps (Pandoc build break; SixSCM still on .scm not descriptiles/*.a2ml), and the ADR-0001 direction.

Notes

  • Docs-only; inherits the two standing main reds (Pandoc build; Hypatia findings) — neither introduced here.
  • README "Axiom.jl shape" = the Julia-package README idiom (I couldn't find a specific Axiom.jl to mirror exactly; happy to re-shape if a particular one was meant).
  • Repo description and topics can't be set via the available tooling — proposed separately for you to apply in Settings.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WN6nPWWe4dvXfoqBG6auWN


Generated by Claude Code

…-dive

Reshape README.adoc into the canonical Julia-package idiom: clean badges, one-line pitch, a concrete runnable example up front, install, differentiators, implemented-vs-planned features, docs links, where-it-fits (poly-ssg/ddraig/boj), license. Lead with the real positioning (accessibility-first, metadata-driven; verified+agent-native as trajectory per ADR-0001) instead of the generic 'pure functional SSG'. Add EXPLAINME.adoc: developer deep-dive of the build pipeline, module map, accessibility invariants, content/metadata model, known gaps, and the ADR-0001 direction.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Claude-Session: https://claude.ai/code/session_01WN6nPWWe4dvXfoqBG6auWN
@github-actions

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@hyperpolymath
hyperpolymath marked this pull request as ready for review June 23, 2026 22:15
@hyperpolymath
hyperpolymath merged commit e597ff1 into main Jun 23, 2026
5 of 11 checks passed
@hyperpolymath
hyperpolymath deleted the claude/docs-readme-explainme branch June 23, 2026 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants