docs: update readme

README.md

@@ -7,153 +7,21 @@ One is in alpha and is under heavy development. You *can* use this for building
 ## Usage
 
 ```js
-import {o, mount} from 'one'
-
-const MyComponent = {
-  data() {
-    return {
-      name: 'John Doe',
-    }
-  ),
-  view({ data }) {
-    return o('div', [
-      o('p', `Hello ${data.name}`),
-    ])
-  },
-}
-
-mount(MyComponent, document.body)
-```
-
-## Gotchas
-
-Since One is as lightweight as it is, there are a couple of gotchas that you should
-be aware of. Feel free to submit a PR, if you can't live with the workarounds 😉
-
-However, these are gotchas, and can easily be avoided.
-
-### Conditional rendering
-When using conditional rendering in a components `view` function, you should 
-structure your view in such a way, that you don't break the natural render tree.
-
-The recommended way to have conditional rendering is to use 2 components and the `redraw` attribute set to `true`.
-If you don't use the `redraw` attribute, the component will return a cached version from last render.
-
-Keep in mind that using `redraw` will redraw the component *every time* the parent component re-renders.
-
-See the first example below.
-
-```js
-// ok
-const Component = {
-  name: 'component',
-  // Recommended!
-  view({ data }) {
-    return o('div', [
-      data.bool ? 
-        // Can have props, but if not, set second argument to `null`
-        o(Component1, null, {redraw: true}) :
-        o(Component2, null, {redraw: true})
-    ])
-  }
-}
-
-const Component = {
-  name: 'component',
-  view({ data }) {
-    return o('div', [
-      o('ul',
-        data.items.length
-          ? data.items.map(item => o('li', `${item.name}`))
-          : o('li', 'Loading')
-      )
-    ])
-  }
-}
-
-const Component = {
-  name: 'component',
-  view({ data }) {
-    return o('div', 
-      data.items.length
-        ? o('nav', data.items.map(item => o('a', `${item.name}`)))
-        : o('nav', o('div', 'Loading...'))
-    )
-  }
-}
-
-const Component = {
-  name: 'component',
-  view ({ data }) {
-    return o(
-      'ul',
-      data.items.map(item => o('li', `${item.name}`))
-    )
-  }
-}
-
-const Component = {
-  name: 'component',
-  view ({ props }) {
-    return o('div', [
-      !props.items.length
-        // `p` will be replaced with `ul` since the tagNames differ
-        ? o('p', 'Loading')
-        : o('ul', props.items.map(item => o('li', `${item.name}`)))
-    ])
-  }
-}
-
-// not ok
-const Component = {
-  name: 'component',
-  view({ data }) {
-    return data.items.length
-      ? o('ul', data.items.map(item => o('li', `${item.name}`)))
-      : o('div', o('p', 'Loading...'))
-  }
-}
-
-const Component = {
-  name: 'component',
-  view({ data }) {
-    return o('div', 
-      data.items.length
-      ? o('ul', data.items.map(item => o('li', `${item.name}`)))
-      : o('div', o('p', 'Loading...'))
-    )
-  }
-}
-
-const Component = {
-  name: 'component',
-  view({ data }) {
-    if (!data.items.length) {
-      return o('div', 'Loading')
-    }
-
-    return o('div', 'p', 'Items loaded...')
-  }
-}
+import { one, html } from 'one'
+
+one({
+  name: 'counter',
+  template: html`
+    <div>
+      <button id="dec">-</button>
+      <span o-text="count"></span>
+      <button id="inc">+</button>
+    </div>
+  `,
+  state: { count: 0 },
+  setup({ query, state }) {
+    query('#dec').on('click', () => state.count--)
+    query('#inc').on('click', () => state.count++)
+  }
+})
 ```
-
-### Dangling TextNodes
-One is built around diffing HTML elements and not text nodes. This means that you shouldn't have "dangling" text nodes.
-
-A dangling text node is a text node with HTML element siblings. See below for examples.
-
-It *is* possible, but since One doesn't care about text nodes, they will often be removed from the DOM during rendering.
-
-```js
-// ok
-o('div', 
-  o('h1', 'This is a heading'),
-  o('p', 'This is a paragraph'),
-)
-
-// not ok
-o('div', 
-  o('h1', 'This is a heading'),
-  'This is a "dangling" text node',
-)
-```