Skip to content

Releases: Avinava/document-design-system

v0.2.0 — eight reading patterns and writing documents

Choose a tag to compare

@Avinava Avinava released this 25 Aug 20:51
b357957

writing-documents replaces longform-document-design with eighteen repository-first document types and eight structural reading patterns. Markdown remains canonical; designed HTML and PDF are opt-in.

Installation:

/plugin marketplace add Avinava/document-design-system
/plugin install document-design-system@document-design-system

Highlights:

  • Decision, record, contract, procedure, learning, system, incident, and suite patterns, independent from visual themes.
  • Rewritten Markdown and HTML examples grounded in one fact ledger, with automated title and fact parity checks.
  • Pattern-first GitHub Pages homepage and type catalog with responsive layouts, lightweight thumbnails, navigation, and print support.
  • Stronger distinction between house themes, improved tertiary-text contrast, and a theme audit with zero errors or warnings.
  • Repository agent guidance, pattern-aware skill routing, and source-built Pages deployment.
  • Expanded validation suite: 48 tests plus reproducible example rendering and manifest validation.

Explore the live pattern gallery: https://avinava.github.io/document-design-system/types.html

Full detail: https://github.com/Avinava/document-design-system/blob/main/CHANGELOG.md

v0.1.2 — packaging metadata and manifest validation

Choose a tag to compare

@Avinava Avinava released this 13 Aug 07:13
8089eb6

Packaging metadata and manifest validation. No skill, theme, or token-contract changes — the install identifier is unchanged.

/plugin marketplace add Avinava/document-design-system
/plugin install document-design-system@document-design-system

Fixed

  • The marketplace entry declared no license, repository, or tags. A marketplace browser reads the entry, not plugin.json, so an MIT-licensed plugin appeared unlicensed. All three are now declared and checked against plugin.json so they cannot drift.

Added

  • validate_repository.py now validates both manifests, which previously only CI did. It enforces the two invariants the JSON schema cannot express: the marketplace must be named for the repository, and duplicated fields must agree. A reintroduced "skills" key is rejected.
  • Seven tests asserting the new checks actually reject. Suite: 28 → 35.

Note

displayName was deliberately not added. It is in neither the marketplace nor the plugin-manifest schema, and the CLI ignores it — a field that looks load-bearing but does nothing.

Full detail in CHANGELOG.md.