@webqit/oohtml 2.1.63 → 2.1.64

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.
Files changed (2) hide show
  1. package/README.md +10 -4
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -7,11 +7,13 @@
7
7
 
8
8
  **[Overview](#overview) • [Modular HTML](#modular-html) • [HTML Imports](#html-imports) • [Data Binding](#data-binding) • [Data Plumbing](#data-plumbing) • [Polyfill](#polyfill) • [Examples](#examples) • [License](#license)**
9
9
 
10
- Object-Oriented HTML (OOHTML) is a set of features that extend standard HTML and the DOM to enable authoring modular, reusable and reactive markup - with a "buildless", web-native workflow as design goal! This project presents what "modern" HTML could look like!
10
+ Object-Oriented HTML (OOHTML) is a set of features that extend standard HTML and the DOM to enable authoring modular, reusable and reactive markup - with a "buildless", web-native workflow as design goal! This project presents what "modern" HTML could look like at its best!
11
+
12
+ Building Single Page Applications? OOHTML is a special love letter!
11
13
 
12
14
  ## Motivation
13
15
 
14
- Vanilla HTML is increasingly becoming the compelling option for web developers! But the current authoring experience still leaves much to be desired in how the language lacks modularity, reusability, and data binding! Authors still have to rely on tools - or, to say the least, do half of the work in HTML and half in JS - to get even basic things working!
16
+ Vanilla HTML is surprisingly becoming a compelling option for an increasing number of web developers! But the current authoring experience still leaves much to be desired in how the language lacks modularity, reusability, and data binding! Authors still have to rely on tools - or, to say the least, do half of the work in HTML and half in JS - to get even basic things working!
15
17
 
16
18
  This project pursues an object-oriented approach to HTML and implicitly revisits much of what inhibits the idea of a *component* architecture for HTML!
17
19
 
@@ -19,14 +21,18 @@ This project pursues an object-oriented approach to HTML and implicitly revisits
19
21
 
20
22
  ## Overview
21
23
 
22
- On the agenda is a set of features that normalises how the modern UI lends itself to be built! And all of it comes as a special love letter to Single Page Applications!
24
+ On the agenda:
23
25
 
24
26
  + [Modular HTML](#modular-html)
25
27
  + [HTML Imports](#html-imports)
26
28
  + [Data Binding](#data-binding)
27
29
  + [Data Plumbing](#data-plumbing)
28
30
 
29
- > **Note** This is documentation for `OOHTML@2.x`. (Looking for [`OOHTML@1.x`](https://github.com/webqit/oohtml/tree/v1.10.4)?)
31
+ <details><summary>Version <code>v2.x</code></summary>
32
+
33
+ *This is documentation for `OOHTML@2.x`. (Looking for [`OOHTML@1.x`](https://github.com/webqit/oohtml/tree/v1.10.4)?)*
34
+
35
+ </details>
30
36
 
31
37
  ## Modular HTML
32
38
 
package/package.json CHANGED
@@ -14,7 +14,7 @@
14
14
  "wicg-proposal"
15
15
  ],
16
16
  "homepage": "https://webqit.io/tooling/oohtml",
17
- "version": "2.1.63",
17
+ "version": "2.1.64",
18
18
  "license": "MIT",
19
19
  "repository": {
20
20
  "type": "git",