@obvi/blueprint 1.1.0 → 1.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -0
- package/dist/blueprint.css +1287 -4
- package/dist/blueprint.js +233 -10
- package/dist/code-highlighting/blueprint-code.css +14 -0
- package/dist/code-highlighting/blueprint-code.js +4 -4
- package/package.json +5 -3
package/README.md
CHANGED
|
@@ -11,6 +11,7 @@ A blueprint is a technical document that should look like one: monochrome ink on
|
|
|
11
11
|
- **Semantic HTML is the API.** Headings, paragraphs, lists, tables, figures, and landmarks render as a finished document with no classes to memorize. You write meaning; the design arrives for free.
|
|
12
12
|
- **Classless-first, not class-only.** Components exist only for the few patterns native HTML cannot express, and each is a composition of real semantic elements rather than a replacement for them.
|
|
13
13
|
- **Zero-specificity by contract.** Everything ships in cascade layers wrapped in `:where()`, so the library never fights your own CSS. Your styles always win, with no `!important` and no parent-scoping.
|
|
14
|
+
- **Runtime-complete package.** The default stylesheet includes the chrome that `blueprint.js` injects, and runtime icons are inline SVG, so installed documents do not depend on repository-only CSS or assets.
|
|
14
15
|
|
|
15
16
|
The result is one portable stylesheet, no build step, that turns plain semantic markup into a polished blueprint.
|
|
16
17
|
|