You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@weex.apache.org by ha...@apache.org on 2017/10/13 13:04:46 UTC
[51/51] [abbrv] incubator-weex-site git commit: update file structure
and fix responsive styles
update file structure and fix responsive styles
Project: http://git-wip-us.apache.org/repos/asf/incubator-weex-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-weex-site/commit/12e3a8bc
Tree: http://git-wip-us.apache.org/repos/asf/incubator-weex-site/tree/12e3a8bc
Diff: http://git-wip-us.apache.org/repos/asf/incubator-weex-site/diff/12e3a8bc
Branch: refs/heads/master
Commit: 12e3a8bcd85c23a672ec660c215551b801156fee
Parents: 0e91280
Author: Hanks <zh...@gmail.com>
Authored: Fri Oct 13 20:46:23 2017 +0800
Committer: Hanks <zh...@gmail.com>
Committed: Fri Oct 13 20:46:23 2017 +0800
----------------------------------------------------------------------
_draft/difference-with-web.en.md | 149 -----
_draft/difference-with-web.md | 138 -----
_draft/native-dom-api.md | 212 -------
_draft/timer.cn.md | 49 --
_draft/timer.md | 60 --
_draft/v-0.10/advanced/extend-to-android.md | 189 ------
_draft/v-0.10/advanced/extend-to-html5.md | 258 --------
_draft/v-0.10/advanced/extend-to-ios.md | 311 ----------
.../v-0.10/advanced/how-data-binding-works.md | 39 --
_draft/v-0.10/advanced/images/how-arch.png | Bin 62303 -> 0 bytes
_draft/v-0.10/advanced/images/how-render.png | Bin 42957 -> 0 bytes
_draft/v-0.10/advanced/index.md | 148 -----
_draft/v-0.10/advanced/integrate-to-android.md | 204 -------
_draft/v-0.10/advanced/integrate-to-html5.md | 77 ---
_draft/v-0.10/advanced/integrate-to-ios.md | 118 ----
_draft/v-0.10/guide/.gitkeep | 0
.../how-to/customize-a-native-component.md | 58 --
.../guide/how-to/cuszomize-native-apis.md | 80 ---
_draft/v-0.10/guide/how-to/debug-with-html5.md | 47 --
_draft/v-0.10/guide/how-to/index.md | 40 --
.../guide/how-to/preview-in-playground-app.md | 20 -
.../guide/how-to/require-3rd-party-libs.md | 56 --
.../how-to/transform-code-into-js-bundle.md | 110 ----
_draft/v-0.10/guide/images/tut-cli-qrcode.png | Bin 45480 -> 0 bytes
_draft/v-0.10/guide/images/tut-first.png | Bin 51434 -> 0 bytes
_draft/v-0.10/guide/images/tut-second.png | Bin 78519 -> 0 bytes
_draft/v-0.10/guide/images/tut1.jpg | Bin 47442 -> 0 bytes
_draft/v-0.10/guide/images/tut2.jpg | Bin 52428 -> 0 bytes
_draft/v-0.10/guide/images/tut3.png | Bin 52198 -> 0 bytes
_draft/v-0.10/guide/images/tut4.gif | Bin 218245 -> 0 bytes
_draft/v-0.10/guide/index.md | 211 -------
_draft/v-0.10/guide/syntax/comm.md | 228 --------
.../v-0.10/guide/syntax/composed-component.md | 114 ----
_draft/v-0.10/guide/syntax/config-n-data.md | 61 --
_draft/v-0.10/guide/syntax/data-binding.md | 248 --------
_draft/v-0.10/guide/syntax/display-logic.md | 173 ------
_draft/v-0.10/guide/syntax/events.md | 59 --
_draft/v-0.10/guide/syntax/id.md | 65 ---
_draft/v-0.10/guide/syntax/index.md | 122 ----
_draft/v-0.10/guide/syntax/render-logic.md | 35 --
_draft/v-0.10/guide/syntax/style-n-class.md | 118 ----
_draft/v-0.10/references/api.md | 84 ---
_draft/v-0.10/references/bubble.md | 150 -----
_draft/v-0.10/references/cheatsheet.md | 102 ----
_draft/v-0.10/references/color-names.md | 182 ------
_draft/v-0.10/references/common-attrs.md | 78 ---
_draft/v-0.10/references/common-event.md | 120 ----
_draft/v-0.10/references/common-style.md | 208 -------
_draft/v-0.10/references/component-defs.md | 131 -----
_draft/v-0.10/references/components/a.md | 50 --
_draft/v-0.10/references/components/cell.md | 42 --
_draft/v-0.10/references/components/div.md | 48 --
_draft/v-0.10/references/components/image.md | 55 --
_draft/v-0.10/references/components/index.md | 24 -
.../v-0.10/references/components/indicator.md | 98 ----
_draft/v-0.10/references/components/input.md | 124 ----
_draft/v-0.10/references/components/list.md | 292 ---------
.../references/components/refresh-loading.md | 297 ----------
_draft/v-0.10/references/components/scroller.md | 136 -----
_draft/v-0.10/references/components/slider.md | 107 ----
_draft/v-0.10/references/components/switch.md | 81 ---
_draft/v-0.10/references/components/text.md | 94 ---
_draft/v-0.10/references/components/textarea.md | 81 ---
_draft/v-0.10/references/components/video.md | 75 ---
_draft/v-0.10/references/components/web.md | 152 -----
.../v-0.10/references/components/wxc-navpage.md | 74 ---
.../v-0.10/references/components/wxc-tabbar.md | 94 ---
_draft/v-0.10/references/gesture.md | 74 ---
.../v-0.10/references/images/css-boxmodel.png | Bin 12581 -> 0 bytes
.../references/images/css-flexbox-align.jpg | Bin 35005 -> 0 bytes
.../references/images/css-flexbox-justify.svg | 59 --
.../references/images/css-flexbox-sample.png | Bin 3210 -> 0 bytes
_draft/v-0.10/references/images/nav.png | Bin 83497 -> 0 bytes
_draft/v-0.10/references/index.md | 49 --
_draft/v-0.10/references/modules/animation.md | 63 --
_draft/v-0.10/references/modules/clipboard.md | 53 --
_draft/v-0.10/references/modules/dom.md | 114 ----
_draft/v-0.10/references/modules/globalevent.md | 89 ---
_draft/v-0.10/references/modules/index.md | 28 -
_draft/v-0.10/references/modules/modal.md | 192 ------
_draft/v-0.10/references/modules/navigator.md | 198 -------
_draft/v-0.10/references/modules/storage.md | 111 ----
_draft/v-0.10/references/modules/stream.md | 86 ---
_draft/v-0.10/references/modules/timer.md | 60 --
_draft/v-0.10/references/modules/webview.md | 160 -----
_draft/v-0.10/references/special-element.md | 36 --
_draft/v-0.10/references/specs/index.md | 309 ----------
.../v-0.10/references/specs/js-bundle-format.md | 307 ----------
.../references/specs/js-framework-apis.md | 191 ------
.../v-0.10/references/specs/virtual-dom-apis.md | 147 -----
_draft/v-0.10/references/text-style.md | 43 --
_draft/v-0.10/tools/devtools-android.md | 123 ----
_draft/v-0.10/tools/devtools-ios.md | 76 ---
_draft/v-0.10/tools/devtools.md | 102 ----
_draft/v-0.10/tools/index.md | 97 ---
_draft/v-0.10/tools/playground.md | 24 -
_draft/v-0.10/tools/transformer.md | 38 --
_draft/v1.0/advanced/create-a-weex-project.md | 271 ---------
.../advanced/customize-a-native-component.md | 168 ------
_draft/v1.0/advanced/cuszomize-native-apis.md | 85 ---
_draft/v1.0/advanced/extend-to-android.md | 170 ------
_draft/v1.0/advanced/extend-to-html5.md | 253 --------
_draft/v1.0/advanced/extend-to-ios.md | 279 ---------
_draft/v1.0/advanced/how-data-binding-works.md | 39 --
_draft/v1.0/advanced/images/how-arch.png | Bin 62303 -> 0 bytes
_draft/v1.0/advanced/images/how-render.png | Bin 42957 -> 0 bytes
_draft/v1.0/advanced/index.md | 146 -----
.../advanced/integrate-devtools-to-android.md | 272 ---------
.../v1.0/advanced/integrate-devtools-to-ios.md | 230 --------
_draft/v1.0/advanced/integrate-to-android.md | 201 -------
_draft/v1.0/advanced/integrate-to-html5.md | 69 ---
_draft/v1.0/advanced/integrate-to-ios.md | 110 ----
_draft/v1.0/blog/index.md | 4 -
.../v1.0/guide/develop-on-your-local-machine.md | 175 ------
_draft/v1.0/guide/how-to/debug-with-html5.md | 47 --
_draft/v1.0/guide/how-to/index.md | 185 ------
.../v1.0/guide/how-to/require-3rd-party-libs.md | 57 --
.../how-to/transform-code-into-js-bundle.md | 112 ----
_draft/v1.0/guide/index.md | 60 --
_draft/v1.0/guide/syntax/comm.md | 134 -----
_draft/v1.0/guide/syntax/composed-component.md | 158 -----
_draft/v1.0/guide/syntax/config-n-data.md | 72 ---
_draft/v1.0/guide/syntax/data-binding.md | 332 -----------
_draft/v1.0/guide/syntax/display-logic.md | 252 --------
_draft/v1.0/guide/syntax/events.md | 103 ----
_draft/v1.0/guide/syntax/id.md | 124 ----
_draft/v1.0/guide/syntax/index.md | 134 -----
_draft/v1.0/guide/syntax/render-logic.md | 44 --
_draft/v1.0/guide/syntax/style-n-class.md | 117 ----
_draft/v1.0/index.md | 5 -
_draft/v1.0/migration/difference.md | 249 --------
_draft/v1.0/migration/index.md | 11 -
_draft/v1.0/migration/migration-from-weex.md | 116 ----
_draft/v1.0/references/api.md | 67 ---
_draft/v1.0/references/bubble.md | 150 -----
_draft/v1.0/references/cheatsheet.md | 114 ----
_draft/v1.0/references/color-names.md | 180 ------
_draft/v1.0/references/common-attrs.md | 166 ------
_draft/v1.0/references/common-event.md | 492 ----------------
_draft/v1.0/references/common-style.md | 322 ----------
_draft/v1.0/references/component-defs.md | 126 ----
_draft/v1.0/references/components/a.md | 273 ---------
_draft/v1.0/references/components/cell.md | 191 ------
_draft/v1.0/references/components/div.md | 245 --------
_draft/v1.0/references/components/image.md | 161 -----
_draft/v1.0/references/components/index.md | 24 -
_draft/v1.0/references/components/indicator.md | 124 ----
_draft/v1.0/references/components/input.md | 309 ----------
_draft/v1.0/references/components/list.md | 375 ------------
_draft/v1.0/references/components/loading.md | 118 ----
_draft/v1.0/references/components/refresh.md | 204 -------
_draft/v1.0/references/components/scroller.md | 324 ----------
_draft/v1.0/references/components/slider.md | 121 ----
_draft/v1.0/references/components/switch.md | 98 ----
_draft/v1.0/references/components/text.md | 116 ----
_draft/v1.0/references/components/textarea.md | 115 ----
_draft/v1.0/references/components/video.md | 82 ---
_draft/v1.0/references/components/web.md | 143 -----
_draft/v1.0/references/gesture.md | 79 ---
_draft/v1.0/references/images/Artboard.jpg | Bin 36223 -> 0 bytes
_draft/v1.0/references/images/coding_weex_1.jpg | Bin 56225 -> 0 bytes
_draft/v1.0/references/images/css-boxmodel.png | Bin 12581 -> 0 bytes
.../references/images/css-flexbox-align.jpg | Bin 35005 -> 0 bytes
.../references/images/css-flexbox-justify.svg | 59 --
_draft/v1.0/references/images/div_1.jpg | Bin 59561 -> 0 bytes
_draft/v1.0/references/images/div_2.jpg | Bin 62574 -> 0 bytes
_draft/v1.0/references/images/div_3.jpg | Bin 82345 -> 0 bytes
_draft/v1.0/references/images/div_4.jpg | Bin 200642 -> 0 bytes
_draft/v1.0/references/images/image_1.jpg | Bin 163705 -> 0 bytes
_draft/v1.0/references/images/image_2.jpg | Bin 255560 -> 0 bytes
_draft/v1.0/references/images/list_2.jpg | Bin 56635 -> 0 bytes
_draft/v1.0/references/images/list_3.jpg | Bin 128082 -> 0 bytes
_draft/v1.0/references/images/list_4.jpg | Bin 339799 -> 0 bytes
_draft/v1.0/references/images/nav.jpg | Bin 124441 -> 0 bytes
_draft/v1.0/references/images/scroller_1.jpg | Bin 344783 -> 0 bytes
_draft/v1.0/references/images/style_1.jpg | Bin 59366 -> 0 bytes
_draft/v1.0/references/images/style_2.jpg | Bin 59696 -> 0 bytes
_draft/v1.0/references/index.md | 46 --
_draft/v1.0/references/modules/animation.md | 90 ---
_draft/v1.0/references/modules/clipboard.md | 112 ----
_draft/v1.0/references/modules/dom.md | 79 ---
_draft/v1.0/references/modules/globalevent.md | 87 ---
_draft/v1.0/references/modules/index.md | 20 -
_draft/v1.0/references/modules/modal.md | 196 -------
_draft/v1.0/references/modules/navigator.md | 110 ----
_draft/v1.0/references/modules/storage.md | 224 -------
_draft/v1.0/references/modules/stream.md | 220 -------
_draft/v1.0/references/modules/webview.md | 66 ---
_draft/v1.0/references/replace.md | 57 --
_draft/v1.0/references/special-element.md | 38 --
_draft/v1.0/references/specs/index.md | 309 ----------
.../v1.0/references/specs/js-framework-apis.md | 190 ------
.../v1.0/references/specs/virtual-dom-apis.md | 148 -----
_draft/v1.0/references/text-style.md | 40 --
_draft/v1.0/references/units.md | 66 ---
_draft/v1.0/references/wxc/index.md | 44 --
_draft/v1.0/references/wxc/wxc-navpage.md | 192 ------
_draft/v1.0/references/wxc/wxc-tabbar.md | 176 ------
_draft/v1.0/tools/devtools-android.md | 123 ----
_draft/v1.0/tools/devtools-ios.md | 65 ---
_draft/v1.0/tools/devtools.md | 99 ----
_draft/v1.0/tools/index.md | 96 ---
_draft/v1.0/tools/playground.md | 22 -
_draft/v1.0/tools/transformer.md | 38 --
_draft/web-dev-experience.en.md | 36 --
_draft/web-dev-experience.md | 38 --
_draft/web-standards.en.md | 584 ------------------
_draft/web-standards.md | 585 -------------------
_draft/weex-dom-api.md | 224 -------
_draft/write-once.en.md | 23 -
_draft/write-once.md | 25 -
_drafts/difference-with-web.en.md | 149 +++++
_drafts/difference-with-web.md | 138 +++++
_drafts/native-dom-api.md | 212 +++++++
_drafts/timer.cn.md | 49 ++
_drafts/timer.md | 60 ++
_drafts/v-0.10/advanced/extend-to-android.md | 189 ++++++
_drafts/v-0.10/advanced/extend-to-html5.md | 258 ++++++++
_drafts/v-0.10/advanced/extend-to-ios.md | 311 ++++++++++
.../v-0.10/advanced/how-data-binding-works.md | 39 ++
_drafts/v-0.10/advanced/images/how-arch.png | Bin 0 -> 62303 bytes
_drafts/v-0.10/advanced/images/how-render.png | Bin 0 -> 42957 bytes
_drafts/v-0.10/advanced/index.md | 148 +++++
_drafts/v-0.10/advanced/integrate-to-android.md | 204 +++++++
_drafts/v-0.10/advanced/integrate-to-html5.md | 77 +++
_drafts/v-0.10/advanced/integrate-to-ios.md | 118 ++++
_drafts/v-0.10/guide/.gitkeep | 0
.../how-to/customize-a-native-component.md | 58 ++
.../guide/how-to/cuszomize-native-apis.md | 80 +++
_drafts/v-0.10/guide/how-to/debug-with-html5.md | 47 ++
_drafts/v-0.10/guide/how-to/index.md | 40 ++
.../guide/how-to/preview-in-playground-app.md | 20 +
.../guide/how-to/require-3rd-party-libs.md | 56 ++
.../how-to/transform-code-into-js-bundle.md | 110 ++++
_drafts/v-0.10/guide/images/tut-cli-qrcode.png | Bin 0 -> 45480 bytes
_drafts/v-0.10/guide/images/tut-first.png | Bin 0 -> 51434 bytes
_drafts/v-0.10/guide/images/tut-second.png | Bin 0 -> 78519 bytes
_drafts/v-0.10/guide/images/tut1.jpg | Bin 0 -> 47442 bytes
_drafts/v-0.10/guide/images/tut2.jpg | Bin 0 -> 52428 bytes
_drafts/v-0.10/guide/images/tut3.png | Bin 0 -> 52198 bytes
_drafts/v-0.10/guide/images/tut4.gif | Bin 0 -> 218245 bytes
_drafts/v-0.10/guide/index.md | 211 +++++++
_drafts/v-0.10/guide/syntax/comm.md | 228 ++++++++
.../v-0.10/guide/syntax/composed-component.md | 114 ++++
_drafts/v-0.10/guide/syntax/config-n-data.md | 61 ++
_drafts/v-0.10/guide/syntax/data-binding.md | 248 ++++++++
_drafts/v-0.10/guide/syntax/display-logic.md | 173 ++++++
_drafts/v-0.10/guide/syntax/events.md | 59 ++
_drafts/v-0.10/guide/syntax/id.md | 65 +++
_drafts/v-0.10/guide/syntax/index.md | 122 ++++
_drafts/v-0.10/guide/syntax/render-logic.md | 35 ++
_drafts/v-0.10/guide/syntax/style-n-class.md | 118 ++++
_drafts/v-0.10/references/api.md | 84 +++
_drafts/v-0.10/references/bubble.md | 150 +++++
_drafts/v-0.10/references/cheatsheet.md | 102 ++++
_drafts/v-0.10/references/color-names.md | 182 ++++++
_drafts/v-0.10/references/common-attrs.md | 78 +++
_drafts/v-0.10/references/common-event.md | 120 ++++
_drafts/v-0.10/references/common-style.md | 208 +++++++
_drafts/v-0.10/references/component-defs.md | 131 +++++
_drafts/v-0.10/references/components/a.md | 50 ++
_drafts/v-0.10/references/components/cell.md | 42 ++
_drafts/v-0.10/references/components/div.md | 48 ++
_drafts/v-0.10/references/components/image.md | 55 ++
_drafts/v-0.10/references/components/index.md | 24 +
.../v-0.10/references/components/indicator.md | 98 ++++
_drafts/v-0.10/references/components/input.md | 124 ++++
_drafts/v-0.10/references/components/list.md | 292 +++++++++
.../references/components/refresh-loading.md | 297 ++++++++++
.../v-0.10/references/components/scroller.md | 136 +++++
_drafts/v-0.10/references/components/slider.md | 107 ++++
_drafts/v-0.10/references/components/switch.md | 81 +++
_drafts/v-0.10/references/components/text.md | 94 +++
.../v-0.10/references/components/textarea.md | 81 +++
_drafts/v-0.10/references/components/video.md | 75 +++
_drafts/v-0.10/references/components/web.md | 152 +++++
.../v-0.10/references/components/wxc-navpage.md | 74 +++
.../v-0.10/references/components/wxc-tabbar.md | 94 +++
_drafts/v-0.10/references/gesture.md | 74 +++
.../v-0.10/references/images/css-boxmodel.png | Bin 0 -> 12581 bytes
.../references/images/css-flexbox-align.jpg | Bin 0 -> 35005 bytes
.../references/images/css-flexbox-justify.svg | 59 ++
.../references/images/css-flexbox-sample.png | Bin 0 -> 3210 bytes
_drafts/v-0.10/references/images/nav.png | Bin 0 -> 83497 bytes
_drafts/v-0.10/references/index.md | 49 ++
_drafts/v-0.10/references/modules/animation.md | 63 ++
_drafts/v-0.10/references/modules/clipboard.md | 53 ++
_drafts/v-0.10/references/modules/dom.md | 114 ++++
.../v-0.10/references/modules/globalevent.md | 89 +++
_drafts/v-0.10/references/modules/index.md | 28 +
_drafts/v-0.10/references/modules/modal.md | 192 ++++++
_drafts/v-0.10/references/modules/navigator.md | 198 +++++++
_drafts/v-0.10/references/modules/storage.md | 111 ++++
_drafts/v-0.10/references/modules/stream.md | 86 +++
_drafts/v-0.10/references/modules/timer.md | 60 ++
_drafts/v-0.10/references/modules/webview.md | 160 +++++
_drafts/v-0.10/references/special-element.md | 36 ++
_drafts/v-0.10/references/specs/index.md | 309 ++++++++++
.../v-0.10/references/specs/js-bundle-format.md | 307 ++++++++++
.../references/specs/js-framework-apis.md | 191 ++++++
.../v-0.10/references/specs/virtual-dom-apis.md | 147 +++++
_drafts/v-0.10/references/text-style.md | 43 ++
_drafts/v-0.10/tools/devtools-android.md | 123 ++++
_drafts/v-0.10/tools/devtools-ios.md | 76 +++
_drafts/v-0.10/tools/devtools.md | 102 ++++
_drafts/v-0.10/tools/index.md | 97 +++
_drafts/v-0.10/tools/playground.md | 24 +
_drafts/v-0.10/tools/transformer.md | 38 ++
_drafts/v1.0/advanced/create-a-weex-project.md | 271 +++++++++
.../advanced/customize-a-native-component.md | 168 ++++++
_drafts/v1.0/advanced/cuszomize-native-apis.md | 85 +++
_drafts/v1.0/advanced/extend-to-android.md | 170 ++++++
_drafts/v1.0/advanced/extend-to-html5.md | 253 ++++++++
_drafts/v1.0/advanced/extend-to-ios.md | 279 +++++++++
_drafts/v1.0/advanced/how-data-binding-works.md | 39 ++
_drafts/v1.0/advanced/images/how-arch.png | Bin 0 -> 62303 bytes
_drafts/v1.0/advanced/images/how-render.png | Bin 0 -> 42957 bytes
_drafts/v1.0/advanced/index.md | 146 +++++
.../advanced/integrate-devtools-to-android.md | 272 +++++++++
.../v1.0/advanced/integrate-devtools-to-ios.md | 230 ++++++++
_drafts/v1.0/advanced/integrate-to-android.md | 201 +++++++
_drafts/v1.0/advanced/integrate-to-html5.md | 69 +++
_drafts/v1.0/advanced/integrate-to-ios.md | 110 ++++
_drafts/v1.0/blog/index.md | 4 +
.../v1.0/guide/develop-on-your-local-machine.md | 175 ++++++
_drafts/v1.0/guide/how-to/debug-with-html5.md | 47 ++
_drafts/v1.0/guide/how-to/index.md | 185 ++++++
.../v1.0/guide/how-to/require-3rd-party-libs.md | 57 ++
.../how-to/transform-code-into-js-bundle.md | 112 ++++
_drafts/v1.0/guide/index.md | 60 ++
_drafts/v1.0/guide/syntax/comm.md | 134 +++++
_drafts/v1.0/guide/syntax/composed-component.md | 158 +++++
_drafts/v1.0/guide/syntax/config-n-data.md | 72 +++
_drafts/v1.0/guide/syntax/data-binding.md | 332 +++++++++++
_drafts/v1.0/guide/syntax/display-logic.md | 252 ++++++++
_drafts/v1.0/guide/syntax/events.md | 103 ++++
_drafts/v1.0/guide/syntax/id.md | 124 ++++
_drafts/v1.0/guide/syntax/index.md | 134 +++++
_drafts/v1.0/guide/syntax/render-logic.md | 44 ++
_drafts/v1.0/guide/syntax/style-n-class.md | 117 ++++
_drafts/v1.0/index.md | 5 +
_drafts/v1.0/migration/difference.md | 249 ++++++++
_drafts/v1.0/migration/index.md | 11 +
_drafts/v1.0/migration/migration-from-weex.md | 116 ++++
_drafts/v1.0/references/api.md | 67 +++
_drafts/v1.0/references/bubble.md | 150 +++++
_drafts/v1.0/references/cheatsheet.md | 114 ++++
_drafts/v1.0/references/color-names.md | 180 ++++++
_drafts/v1.0/references/common-attrs.md | 166 ++++++
_drafts/v1.0/references/common-event.md | 492 ++++++++++++++++
_drafts/v1.0/references/common-style.md | 322 ++++++++++
_drafts/v1.0/references/component-defs.md | 126 ++++
_drafts/v1.0/references/components/a.md | 273 +++++++++
_drafts/v1.0/references/components/cell.md | 191 ++++++
_drafts/v1.0/references/components/div.md | 245 ++++++++
_drafts/v1.0/references/components/image.md | 161 +++++
_drafts/v1.0/references/components/index.md | 24 +
_drafts/v1.0/references/components/indicator.md | 124 ++++
_drafts/v1.0/references/components/input.md | 309 ++++++++++
_drafts/v1.0/references/components/list.md | 375 ++++++++++++
_drafts/v1.0/references/components/loading.md | 118 ++++
_drafts/v1.0/references/components/refresh.md | 204 +++++++
_drafts/v1.0/references/components/scroller.md | 324 ++++++++++
_drafts/v1.0/references/components/slider.md | 121 ++++
_drafts/v1.0/references/components/switch.md | 98 ++++
_drafts/v1.0/references/components/text.md | 116 ++++
_drafts/v1.0/references/components/textarea.md | 115 ++++
_drafts/v1.0/references/components/video.md | 82 +++
_drafts/v1.0/references/components/web.md | 143 +++++
_drafts/v1.0/references/gesture.md | 79 +++
_drafts/v1.0/references/images/Artboard.jpg | Bin 0 -> 36223 bytes
.../v1.0/references/images/coding_weex_1.jpg | Bin 0 -> 56225 bytes
_drafts/v1.0/references/images/css-boxmodel.png | Bin 0 -> 12581 bytes
.../references/images/css-flexbox-align.jpg | Bin 0 -> 35005 bytes
.../references/images/css-flexbox-justify.svg | 59 ++
_drafts/v1.0/references/images/div_1.jpg | Bin 0 -> 59561 bytes
_drafts/v1.0/references/images/div_2.jpg | Bin 0 -> 62574 bytes
_drafts/v1.0/references/images/div_3.jpg | Bin 0 -> 82345 bytes
_drafts/v1.0/references/images/div_4.jpg | Bin 0 -> 200642 bytes
_drafts/v1.0/references/images/image_1.jpg | Bin 0 -> 163705 bytes
_drafts/v1.0/references/images/image_2.jpg | Bin 0 -> 255560 bytes
_drafts/v1.0/references/images/list_2.jpg | Bin 0 -> 56635 bytes
_drafts/v1.0/references/images/list_3.jpg | Bin 0 -> 128082 bytes
_drafts/v1.0/references/images/list_4.jpg | Bin 0 -> 339799 bytes
_drafts/v1.0/references/images/nav.jpg | Bin 0 -> 124441 bytes
_drafts/v1.0/references/images/scroller_1.jpg | Bin 0 -> 344783 bytes
_drafts/v1.0/references/images/style_1.jpg | Bin 0 -> 59366 bytes
_drafts/v1.0/references/images/style_2.jpg | Bin 0 -> 59696 bytes
_drafts/v1.0/references/index.md | 46 ++
_drafts/v1.0/references/modules/animation.md | 90 +++
_drafts/v1.0/references/modules/clipboard.md | 112 ++++
_drafts/v1.0/references/modules/dom.md | 79 +++
_drafts/v1.0/references/modules/globalevent.md | 87 +++
_drafts/v1.0/references/modules/index.md | 20 +
_drafts/v1.0/references/modules/modal.md | 196 +++++++
_drafts/v1.0/references/modules/navigator.md | 110 ++++
_drafts/v1.0/references/modules/storage.md | 224 +++++++
_drafts/v1.0/references/modules/stream.md | 220 +++++++
_drafts/v1.0/references/modules/webview.md | 66 +++
_drafts/v1.0/references/replace.md | 57 ++
_drafts/v1.0/references/special-element.md | 38 ++
_drafts/v1.0/references/specs/index.md | 309 ++++++++++
.../v1.0/references/specs/js-framework-apis.md | 190 ++++++
.../v1.0/references/specs/virtual-dom-apis.md | 148 +++++
_drafts/v1.0/references/text-style.md | 40 ++
_drafts/v1.0/references/units.md | 66 +++
_drafts/v1.0/references/wxc/index.md | 44 ++
_drafts/v1.0/references/wxc/wxc-navpage.md | 192 ++++++
_drafts/v1.0/references/wxc/wxc-tabbar.md | 176 ++++++
_drafts/v1.0/tools/devtools-android.md | 123 ++++
_drafts/v1.0/tools/devtools-ios.md | 65 +++
_drafts/v1.0/tools/devtools.md | 99 ++++
_drafts/v1.0/tools/index.md | 96 +++
_drafts/v1.0/tools/playground.md | 22 +
_drafts/v1.0/tools/transformer.md | 38 ++
_drafts/web-dev-experience.en.md | 36 ++
_drafts/web-dev-experience.md | 38 ++
_drafts/web-standards.en.md | 584 ++++++++++++++++++
_drafts/web-standards.md | 585 +++++++++++++++++++
_drafts/weex-dom-api.md | 224 +++++++
_drafts/write-once.en.md | 23 +
_drafts/write-once.md | 25 +
source/cn/development-process.md | 6 +
source/development-process.md | 6 +
source/wiki/common-styles.md | 2 +-
source/wiki/css-units.md | 2 +-
source/wiki/platform-difference.md | 11 +
source/wiki/platfrom-difference.md | 11 -
themes/weex/languages/cn.yml | 1 +
themes/weex/languages/en.yml | 1 +
themes/weex/layout/_partial/article.ejs | 6 +
themes/weex/layout/_partial/footer.ejs | 6 +-
themes/weex/layout/_partial/header.ejs | 3 +
themes/weex/layout/layout.ejs | 7 +-
themes/weex/source/css/common.scss | 2 +-
themes/weex/source/css/media-queries.scss | 44 +-
themes/weex/source/css/partial/article.scss | 42 +-
themes/weex/source/css/partial/footer.scss | 18 +-
themes/weex/source/css/partial/header.scss | 7 +-
themes/weex/source/css/partial/sidebar.scss | 22 +-
themes/weex/source/css/partial/summary.scss | 10 +-
themes/weex/source/css/post.scss | 34 +-
themes/weex/source/css/variable.scss | 4 +-
443 files changed, 23811 insertions(+), 23704 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/difference-with-web.en.md
----------------------------------------------------------------------
diff --git a/_draft/difference-with-web.en.md b/_draft/difference-with-web.en.md
deleted file mode 100644
index 2af11f9..0000000
--- a/_draft/difference-with-web.en.md
+++ /dev/null
@@ -1,149 +0,0 @@
----
-title: Difference with Web
-type: references
-order: 10.1
-version: 2.1
----
-
-# Differences between using Vue in Web and Weex
-
-## Platform Differences
-
-Vue.js was designed for the Web platform at the begining. Although it can be based on Weex to develop native applications, there are still many differences between web and native. See [Platform Differences Between Weex and Web](../ platform-difference.html) for more details.
-
-Due to those differences, Weex doesn't support those features in Vue.js (mostly are DOM-related):
-
-+ Event bubbling and capturing are not supported. Event modifiers, such as `.prevent`,` .capture`, `.stop`,` .self` are meaningless in the native environment.
-+ The keyboard event modifiers, like `.{KeyCode | keyAlias}` is also meaningless. (see [docs in Vue.js](https://vuejs.org/v2/guide/events.html#Key-Modifiers))
-+ No need to call `vm.$mount` manually, the entry component will mount to the root view of the native container by default.
-+ `v-html` and` v-text` directives are not supported.
-
-## Functional differences
-
-### Vue 2.0 Runtime-only build
-
-Vue 2.0 provides two available builds, the standalone build and the runtime-only build. see the [official document](https://vuejs.org/v2/guide/installation.html#Standalone-vs-Runtime-only-Build) for more information.
-
-Weex only required the runtime-only build of Vue 2.0 for better performance and less code size.
-
-The specific differences are:
-
-+ The `template` attribute is not supported when defining a component.
-+ Does not support using `x-templates`.
-+ Does not support using `Vue.compile`.
-
-### Isolate the context of multiple pages
-
-Weex use the "multiple-pages" concept in native, different js bundle will be run in different native views, there context is isolated. Even the `Vue` variable is not the same instance between js bundles. (However, all the js bundle will share the same Weex runtime.)
-
-Based on this feature, the global configurations in `Vue` will only take effect on the current page:
-
-+ `Vue.config`
-+ `Vue.component`
-+ `Vue.directive`
-+ `Vue.filter`
-+ `Vue.mixin`
-+ `Vue.use`
-
-> Note: Those methods are still work, but its effect will be limited to the current page.
-
-## Restrictions in style
-
-CSS is very flexible, has a lot of properties, support a variety of layout modes. This is the advantage of CSS, but also a bottleneck in browser performance optimization.
-
-The style in Weex is parsed by the native renderer, and for the sake of performance and complexity, Weex makes some trade-offs about CSS features to make it better suited to *"best practices"*.
-
-### Single class selector
-
-Weex only supports to use single class name in `<style>`, does not support *type selectors*, *ID selectors*, *attribute selectors*, *adjacent sibling selectors* and the *combinators*.
-
-```CSS
-/* Support single class name selector */
-.one-class {
- font-size: 36px;
-}
-
-/* Does not support to use combinators between selector */
-.parent > .child {
- padding-top: 10px;
-}
-.foo + .bar {
- margin-left: 20px;
-}
-
-/* Does not support attribute selectors. The `v-cloak` directive is not supported */
-[V-cloak] {
- color: #FF6600;
-}
-```
-
-The restriction is only for the style definition, does not affect the use of class names. You can still use multiple class names on a single tag, such as:
-
-```Html
-<template>
- <div class="one two three"><div>
-</template>
-```
-
-### Scoped by default
-
-In Weex, For single file components, the styles written in the `<style>` can only be used in the current component.
-
-In order to maintain consistency with Native, it is recommended that you write the style in the `.vue` file with the` scoped` attribute, that is, `<style scoped>`.
-
-### Supported CSS attributes
-
-Weex supports a subset of CSS, and will continue to expand.
-
-Weex supports *box-model* and *flexbox*, as well as other common styles. See [Weex Common Style](../ common-style.html) and [Supported Web Standards](http://weex.apache.org/references/web-standards.html) for more information.
-
-In addition, you should also pay attention to the following points:
-
-+ No need to write style prefix.
-+ Weex doesn't support `display: none;` and therefore doesn't support the `v-show` directive.
-+ In order to optimize the efficiency of CSS parser, Weex doesn't support shorthand attributes, involving the following attributes:
- + `flex`
- + `border`, `border-(top|bottom|left|right)`
- + `margin`
- + `padding`
- + `font`
- + `background`
-
-## Differences in development
-
-Because of the platform difference, you have to compile your source file in two different ways:
-
-+ For the web, you can compile source files in any official way, such as Webpack + vue-loader or Browserify + vueify. and require the [weex-vue-render](https://www.npmjs.com/package/weex-vue-render), which is a group of Weex build-in components.
-+ For Android and iOS, we've provided [weex-loader](https://github.com/weexteam/weex-loader) to compile the `.vue` files. That is, use Webpack + weex-loader to generate the js bundle that is available for the native.
-
-### Use weex-loader
-
-[weex-loader](https://github.com/weexteam/weex-loader) is a loader for Webpack, see the [official document](http://webpack.github.io/docs/using-loaders.html) to learn how to use it.
-
-One more thing should be reminded is that if the *entry file* of your webpack config is a `.vue` file, you also need to pass an additional ` entry` parameter, usually set to `true`.
-
-```Js
-module.exports = {
- // Add the entry parameter for the .vue file
- entry: './path/to/App.vue?entry=true',
-
- // other configurations ...
-
- module: {
- loaders: [{
-
- // matches the .vue file path that contains the entry parameter
- test: /\.vue(\?^^]+)?$/,
- loaders: ['weex-loader']
- }]
- },
-}
-```
-
-**You don't need to write those additional parameters if you are using `.js` file as entry file.** We recommend using javascript files as the entry file of webpack config.
-
-### Setup native development environments
-
-Since your are using Weex to develop native apps, setup native development environments, both Android and iOS, would be very useful.
-
-See [Integrating Weex to the existing application](../../guide/integrate-to-your-app.html) for more information.
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/difference-with-web.md
----------------------------------------------------------------------
diff --git a/_draft/difference-with-web.md b/_draft/difference-with-web.md
deleted file mode 100644
index d075312..0000000
--- a/_draft/difference-with-web.md
+++ /dev/null
@@ -1,138 +0,0 @@
----
-title: Vue.js 在 Weex 中的差异
-type: guide
-group: 高阶特性
-order: 8.3
-version: 2.1
----
-
-
-# Vue.js 在 Weex 和 Web 中的差异
-
-## 平台差异
-
-Vue.js 最初是为 Web 平台设计的，虽然可以基于 Weex 开发原生应用，但是 Web 开发和原生开发毕竟不同，在功能和开发体验上都有一些差异，这些差异从本质上讲是原生开发平台和 Web 平台之间的差异，可以通过[《Weex 和 Web 平台的差异》](../platform-difference.html)了解更多细节和原因。
-
-由于运行平台存在差异，Weex 不支持 Vue.js 中与 DOM 相关的功能：
-
-+ 不支持事件冒泡和捕获机制，`.prevent` 、`.capture` 、`.stop` 、`.self` 等事件修饰符在原生环境中无意义。
-+ 键盘事件的 `.{keyCode | keyAlias}` 修饰符在原生环境中无意义。(参考 [Vue 相关文档](https://cn.vuejs.org/v2/guide/events.html#按键修饰符))
-+ 无需自行调用 `vm.$mount`，默认会将入口组件挂载到原生应用的视图中。
-+ 不支持 `v-html` 和 `v-text` 指令。
-
-## 功能差异
-
-### 仅引入了 Vue Runtime
-
-Vue 除了提供默认的完整包以外，还提供一个更小巧的 `vue.runtime.js`，在这个文件中移除了模板编译的相关操作，Weex 中也仅引入 Vue Runtime 的功能，这样做除了可以减少代码体积以外，还能减少运行期编译模板的负担，提升性能。
-
-具体的差异有：
-
-+ 定义组件时不支持使用 `template` 属性。
-+ 不支持使用 `x-templates`。
-+ 不支持使用 `Vue.compile`。
-
-### 隔离多页面的作用域
-
-Weex 在原生端使用的是“多页”的实现，不同的 js bundle 将会在不同的原生页面中执行；也就是说，不同的 js bundle 之间将不同共享 js 变量。即使是 `Vue` 这个变量，在不同页面中也对应了不同的引用。
-
-基于这个特性，Vue 中全局功能将只在当前页面内生效：
-
-+ `Vue.config`
-+ `Vue.component`
-+ `Vue.directive`
-+ `Vue.filter`
-+ `Vue.mixin`
-+ `Vue.use`
-
-> 注：以上接口的功能并未受影响，只是其生效范围将会限制在同一页面内。
-
-## 样式差异
-
-Web 中的 CSS 非常的灵活，积累了特别多的属性，支持多种布局方法；这是其优势，也是浏览器性能优化的一个瓶颈。
-
-Weex 中的样式是由原生渲染器解析的，出于性能和功能复杂度的考虑，Weex 对 CSS 的特性做了一些取舍，使其更符合最佳实践。
-
-### 单类名选择器和作用域
-
-Weex 中只支持单个类名选择器，不支持关系选择器，也不支持属性选择器。
-
-```css
-/* 支持单个类名选择器 */
-.one-class {
- font-size: 36px;
-}
-
-/* 不支持关系选择器 */
-.parent > .child {
- padding-top: 10px;
-}
-
-/* 不支持属性选择器，不支持 `v-cloak` 指令 */
-[v-cloak] {
- color: #FF6600;
-}
-```
-
-这个只是对样式定义的限制，不影响样式类名的使用，在标签中可以添加多个样式类名，如：
-
-```html
-<template>
- <div class="one two three"><div>
-</template>
-```
-
-### 组件级别的作用域
-
-在 Weex 中，写在组件 `<style>` 里的样式只能用在当前组件中，默认是 `scoped` 作用域。为了保持和 Native 的一致性，建议在 `.vue` 文件中写样式时，加上 `scoped` 属性，即： `<style scoped>`。
-
-### 支持的样式属性
-
-Weex 支持的样式特性是 CSS 的子集，并且会不断扩充；在实现过程中我们参考了 [CSS 属性在浏览器中的使用频率](https://gist.github.com/Jinjiang/ea6b403036b7287cf8b8508729b77ac0#css-properties)，优先实现其中频率最高的一些属性。
-
-Weex 支持了基本的盒模型和 flexbox 布局，以及其他常用样式，详情可参考[Weex 通用样式文档](../common-style.html)。
-
-在编写样式时，还应该注意一下几点：
-
-+ 不需要写样式前缀。
-+ Weex 不支持 `display: none;`，因此也不支持 `v-show` 指令。
-+ 为了优化样式解析的效率，样式属性暂不支持简写，涉及一下属性：
- + `border` 、`border-(top|bottom|left|right)`
- + `margin`
- + `padding`
- + `flex`
-
-## 编译环境的差异
-
-在 Weex 中使用 Vue.js ，你所需要关注的运行平台除了 Web 之外还有 Android 和 iOS ，在开发和编译环境上还有一些不同点。针对 Web 和原生平台，将 Vue 项目源文件编译成目标文件，有两种不同的方式：
-
-+ 针对 Web 平台，和普通 Vue 2.X 项目一样，可以使用任意官方推荐的方式编译源文件，如 Webpack + vue-loader 或者 Browserify + vueify 。
-+ 针对 Android 和 iOS 平台，我们提供了 [weex-loader](https://github.com/weexteam/weex-loader) 工具支持编译 `.vue` 格式的单文件组件；也就是说，目前只能使用 Webpack + weex-loader 来生成原生端可用的 js bundle。
-
-### 使用 weex-loader
-
-weex-loader 是 Webpack 的一个加载器，使用方法参考其[官方文档](http://webpack.github.io/docs/using-loaders.html)。需要提醒的是，如果 Webpack 配置的入口文件是个 `.vue` 格式的文件的话，还需要额外传递 `entry` 参数，通常设置为 `true`，表示将当前组件作为入口组件。为了能正常匹配 `.vue` 文件，Webpack 配置文件中 weex-loader 的匹配规则也需要有所调整。
-
-```js
-module.exports = {
- // 针对 .vue 文件要添加 entry 参数
- entry: './path/to/App.vue?entry=true',
-
- // 其他配置项 ...
-
- module: {
- loaders: [{
-
- // 匹配包含了 entry 参数的 .vue 文件路径
- test: /\.vue(\?[^?]+)?$/,
- loaders: ['weex-loader']
- }]
- },
-}
-```
-
-如果使用 `.js` 文件作为 Webpack 配置的入口文件，则不需要额外配置这些参数，我们推荐使用 Javascript 文件作为编译的入口文件。
-
-### 搭建原生开发环境
-
-Weex 项目生成的是原生应用，学习一些开发原生应用的基础知识，会对你开发 Weex 项目很有帮助。参考[《集成 Weex 到已有应用》](../../guide/integrate-to-your-app.html)了解更多信息。
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/native-dom-api.md
----------------------------------------------------------------------
diff --git a/_draft/native-dom-api.md b/_draft/native-dom-api.md
deleted file mode 100644
index 37729a2..0000000
--- a/_draft/native-dom-api.md
+++ /dev/null
@@ -1,212 +0,0 @@
----
-title: Native DOM APIs
-type: references
-order: 6
-version: 2.1
-has_chapter_content: true
----
-
-# Native DOM APIs
-
-Weex in the JS engine, for each page provides a set of Native DOM APIs. This interface is very close to the HTML DOM APIs. Using this interface we can control native rendering logic via JavaScript. And Weex upper layer of Vue 2.0 is based on this interface to adapt.
-
-In most cases, the JS framework will encapsulate native DOM APIs. That way, the developer does not need to work directly on the Native DOM.
-
-+ `Document` class: full page document.
-+ `Node` class: the base class of nodes.
-+ `Element` class: element node, inherited from Node, single view unit.
-+ `Comment` class: comment node, inherited from Node, no practical meaning, usually used as placeholders.
-
-Each Weex page has a `weex.document` object, which is an instance of the Document class and is the starting point for all the following interface calls.
-
-Let's take a look at their usage in detail:
-
-## `Document` class
-Each `Document` instance will automatically have a `documentElement` property when it is created. This attribute represents the document node. The document node can have a body, which is the main node of the document.
-
-Note: The document node body only accepts `<div>`, `<list>`, or `<scroller>` three types of element nodes.
-
-### Constructor
-`new Document(id: string, url: string?)`
-
-### Member method
-`createElement(tagName: string, props: Object?): Element`
-
-+ Creates an `Element` instance of a specific type `tagName`, which is an element node. Props can contain attr objects and style objects. Such as `createBody ('div', {style: {backgroundColor: '#ffffff'}})`.
-
-`createComment(text: string): Comment`
-
-+ Create an instance of ·`Comment`, which is a comment node and set a text description.
-
-`createBody(tagName: string, props: Object?): Element`
-
-+ Create a document body node and automatically mount it under `documentElement`.
-
-`fireEvent(el: Element, type: string, e: Object?, domChanges: Object?)`
-Triggers a particular type of event. When the event modifies the DOM's properties or styles during the generation process, the fourth argument is used to describe the changes, and the parameter format is the same as the format of the `createElement` method above.
-
-`destroy()`
-
-+ Destroy the current document. Once the document is destroyed, it will no longer work.
-
-### Read-only member variables
-`id: string`
-
-+ Each `Document` instance has a unique id. This is also the only id that each Weex page has.
-
-`URL: string?`
-
-+ If the current Weex page has a JS bundle URL, the URL will be returned here.
-
-`body: Element`
-
-+ The main body of the document, the concept similar to the HTML DOM document.body.
-
-`documentElement: Element`
-
-+ Document node, the concept similar to the HTML DOM document.documentElement.
-+ The relationship between body and documentElement is: documentElement is the parent of the body.
-
-`getRef(id): Node`
-
-+ Get the node based on the node id.
-
-## `Node` Class
-### Constructor
-`new Node()`
-
-### Member method
-`destroy()`
-
-### Read-only member variables or methods
-`ref: string`
-
-+ Each `Node` instance has its own unique ref value in the entire `Document instance.
-
-`nextSibling: Node?`
-
-`previousSibling: Node?`
-
-`parentNode: Node?`
-
-+ The three interfaces are consistent with the definition of HTML DOM.
-
-`children: Node[]`
-
-+ The node has an array of all child nodes.
-
-`pureChildren: Node[]`
-
-The node has an array of all the child elements. The difference between it and `children` is that `pureChildren` contains only the `Element` instance and not the `Comment` instance.
-
-
-## `Element` class, inherited from `Node`
-### Constructor
-`new Element(type: string, props: Object?)`
-
-+ Creates an element node of a particular type `type`, and the `props` parameter can contain an `attr` object or a `style` object.
-
-### DOM tree operation
-`appendChild(node: Node)`
-`insertBefore(node: Node, before: Node?)`
-
-+ The two interfaces are similar to HTML DOM.
-
-`insertAfter(node: Node, after: Node?)`
-
-+ Insert a new node before a child node.
-
-`removeChild(node: Node, preserved: boolean?)`
-
-+ Delete the child node node. Parameters `preserved` whether it is immediately removed from memory or temporarily retained.
-
-`clear()`
-
-+ Clear all child nodes.
-
-### The DOM property itself operates
-
-`setAttr(key: string, value: string, silent: boolean?)`
-
-`setStyle(key: string, value: string, silent: boolean?)`
-
-+ In the above two interfaces, when `silent` is true, the node only updates itself, does not pass the command to the client render layer. This parameter is used to handle user events that have changed the node-related properties at the time of occurrence, and will not send commands repeatedly to the client after the Native DOM has changed.
-
-`addEvent(type: string, handler: Function)`
-
-`removeEvent(type: string)`
-
-`fireEvent(type: string, e: any)`
-
-+ Bind events, unbind events, trigger events.
-
-#### Component method for a specific component type
-
-Special: Different component types can have their own unique methods, such as `<web>` components support `refresh` method. You can see the description of each component. In this case, we will generate a specific component type of class, such as `WebElement`, which inherited from `Element`.
-
-Such as:
-
->`WebElement` inherited from `Element`
->Indicates that a webview is embedded in the Wex page
-
->`Refresh ()`: Refreshes the current webview
-
-
-### Read-only member variables or methods
-
-`ref`, `nextSibling`, `previousSibling`, `parentNode`
-
-+ Inherited from `Node`.
-
-`nodeType: number`
-
-+ The number is always 1.
-
-
-`type: string`
-
-+ Consistent with the `type` in the constructor.
-
-`attr: Object`
-
-+ The key pair of all the characteristics of the current node. It is recommended to use the `setAttr ()` method to modify, rather than directly modify the object here.
-
-`style: Object`
-
-+ The value of all the keys of the current node. It is recommended to modify the `setStyle ()` method, rather than directly modify the object here.
-
-`event: Object`
-
-+ All events of the current node are bound. Each event type corresponds to an event handler method. It is recommended to use the `addEvent () / removeEvent ()` method to modify, rather than directly modify the object here.
-
-`toJSON(): Object`
-
-+ Returns a JSON object that describes the element's node, such as: `{ref: string, type: string, attr: Object, style: Object, event: Array (string), children: Array}`.
-
-
-## `Comment` class, inherited from `Node`
-
-### Constructor
-`new Comment(value: string)`
-
-### Read-only member variables or methods
-
-`ref`, `nextSibling`, `previousSibling`, `parentNode`
-
-+ Inherited from `Node`.
-
-`nodeType: number`
-
-+ The number is always 8.
-
-`type: string`
-
-+ The type is always `'comment'`
-
-`value: string`
-
-+ Consistent with the value in the constructor.
-
-`toJSON(): Object`
-
-+ Returns a JSON object describing the annotation node. For example: `<! - value ->`.
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/timer.cn.md
----------------------------------------------------------------------
diff --git a/_draft/timer.cn.md b/_draft/timer.cn.md
deleted file mode 100644
index c93f937..0000000
--- a/_draft/timer.cn.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Timer
-type: references
-group: 内置模块
-order: 9.03
-version: 0.10
----
-
-# Timer
-Weex Timer可以用来延时启动一个一次性任务或者重复任务。Timer会尽最大努力提供精确的延时，但是延时可能并不精确，延时时间很可能会超过用户期望的时间。实际上，timer仅仅是为了支持HTML5中的polyfill，*不建议*开发者直接使用timer.
-
-## API
-Timer中延时的单位是毫秒，且延时时间应该为一个非负的**int**值(int值最大为0x7FFFFF).如果延时时间为零，会将该任务马上插入任务队列的尾部。对于其他非法值，timer的行为未定义。
-
-### setTimeout(fn, timeout)
-`setTimeout()`会等待指定的时间，然后执行给出的函数。
-* 可以使用 `clearTimeout()`去阻止`setTimeout()`运行如果此时对应的`setTimeout()`还没有运行的话。
-* 如果需要重复执行任务，使用`setInterval()`.
-
-#### Arguments
-* `fn` (function): 待执行的函数.
-* `timeout` (number): 执行函数前的等待时间，单位为毫秒。
-
-#### Return value
-一个Number对象, 表示这个任务的id。把id传入clearTimeout(fnId)中可以用来取消任务。
-
-### setInterval(fn, interval)
-`setInterval()`每隔指定的时间间隔后，会执行对应的函数。`setInterval()`不会停止，除非`clearInterval()`被调用。`setInterval()`的返回值可以用来作为`setInterval()`的参数。
-
-#### Arguments
-* `fn` (function): 待执行的函数。
-* `interval` (number): 这次执行函数与下一次函数之间的时间间隔，单位为毫秒。
-
-#### Return value
-一个Number对象，代表任务序列的id。可以把这个值传入`clearInterval`中来终止重复任务的执行。
-
-### clearTimeout(fnId)
-`clearTimeout()`可以用来提前终止`setTimeout()`启动的任务。仅当`setTimeout()`对应的任务没有被执行时，`clearTimeout()`才可以用来终止该任务，否则`clearTimeout()`没有任何效果。
-
-#### Arguments
-* `fnId` (number): `setTimeout()`的返回值.
-
-### clearInterval(fnId)
- `clearInterval()`可以用来终止 `setInterval()`启动的任务序列。
-
-#### Arguments
-* `fnId` (number): `setInterval()`的返回值
-
-[Try it](http://dotwe.org/vue/ad564965f1eac5a4bc86946ecff70a0c)
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/timer.md
----------------------------------------------------------------------
diff --git a/_draft/timer.md b/_draft/timer.md
deleted file mode 100644
index da518fd..0000000
--- a/_draft/timer.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Timer
-type: references
-group: Build-in Modules
-order: 9.03
-version: 0.10
----
-
-# Timer
-
-Weex encapsulates a series of APIs in order to start/stop a one-time task or a repeated task at a fixed delay. Please note that this module don't provide an accuracy delay. It provides best-effort delivery, but the actual delay may still exceed the delay user wants if the corresponding thread is busy.
-Actually, this module is made for the polyfill of HTML5 timer APIs, developers **should not** use this module directly unless they know exactly what they are doing.
-
-## API
-
-All timeout or interval in this module are measured in milliseconds. Also, timeout and interval should be a non-negative **integer**(the max of integer is 0x7FFFFFFF). The behavior of invalid value for timeout or interval is undefined.
-
-### setTimeout(fn, timeout)
-
-The `setTimeout()` method calls a function after a specified number of milliseconds. Use the `clearTimeout()` method to prevent the function from running. The function is only executed once. If you need to repeat execution, use the `setInterval()` method.
-
-#### Arguments
-
-- `fn` (function): The function that will be executed
-- `timeout` (number): The number of milliseconds to wait before executing the function
-
-#### Return value
-
-A Number, representing the fnId value of the timer that is set. Use this value with the `clearTimeout()` method to cancel the timer.
-
-### setInterval(fn, interval)
-
-The `setInterval()` method calls a function at specified intervals (in milliseconds), and it will continue calling the function until `clearInterval()` is called. The fnId value returned by `setInterval()` is used as the parameter for the `clearInterval()` method.
-
-#### Arguments
-
-- `fn` (function): The function that will be executed
-- `interval` (number): The intervals (in milliseconds) on how often to execute the function
-
-#### Return value
-
-A Number, representing the fnId value of the timer that is set. Use this value with the `clearInterval()` method to cancel the timer
-
-### clearTimeout(fnId)
-
-The `clearTimeout()` method clears a timer set with the `setTimeout()` method. The fnId value returned by `setTimeout()` is used as the parameter for the `clearTimeout()` method. If the function has not already been executed, you will be able to stop the execution by calling the `clearTimeout()` method, otherwise, this method has no influence on the task.
-
-#### Arguments
-
-- `fnId` (number): The fnId value of the timer returned by the `setTimeout()` method
-
-### clearInterval(fnId)
-
-The `clearInterval()` method clears a timer set with the `setInterval()` method. The fnId value returned by `setInterval()` is used as the parameter for the `clearInterval()` method.
-
-#### Arguments
-
-- `fnId` (number): The fnId of the timer returned by the `setInterval()` method
-
-[Try it](http://dotwe.org/vue/ad564965f1eac5a4bc86946ecff70a0c)
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/v-0.10/advanced/extend-to-android.md
----------------------------------------------------------------------
diff --git a/_draft/v-0.10/advanced/extend-to-android.md b/_draft/v-0.10/advanced/extend-to-android.md
deleted file mode 100644
index 97bb49e..0000000
--- a/_draft/v-0.10/advanced/extend-to-android.md
+++ /dev/null
@@ -1,189 +0,0 @@
----
-title: Extend to Android
-type: advanced
-order: 6
-has_chapter_content: true
-version: 0.10
----
-
-# Extend to Android
-
-### Module extend
-weex sdk support Module extend,
-Weex SDK provides only rendering capabilities, rather than have other capabilities, such as network, picture, and URL redirection. If you want the these features, you need to implement it.
-
-For example: If you want to implement an address jumping function, you can achieve a Module Follow the steps below.
-
-#### Step to customize a module
-
-1. Customize module must extend WXModule
-2. @WXModuleAnno annotation must be added, as it is the only the way to recognized by Weex
-3. The access levels of mehtod must be **public**
-4. The module class also can not be an inner class
-5. Customize can not be obfuscated by tools like ProGuard
-6. Module methods will be invoked in UI thread, do not put time consuming operation there
-7. Weex params can be int, double, float, String, Map, List
-
-Refer to the following example:
-
-```java
-public class WXEventModule extends WXModule{
-
- private static final String WEEX_CATEGORY="com.taobao.android.intent.category.WEEX";
-
- @JSMethod
- public void openURL(String url){
- //implement your module logic here
- }
-}
-
-```
-
-#### Register the moulde
-
-```java
- WXSDKEngine.registerModule("event", WXEventModule.class);
-```
-
-### Use this module in weex DSL
-Now `event` moudle is avaiable in weex, use the module like this:
-
-```javascript
-var event = require('@weex-module/event');
-event.openURL("http://www.github.com");
-```
-
-### Javascript callback
-
-If the module need implement a callback to javascript, you just add `JSCallback` argument to the method you want expose to javascript:
-
-```java
- @JSMethod
- public void openURL(String url,JSCallback callback){
- //implement your module logic here
- Map<String,Object> resp = new HashMap();
- resp.put("result","ok");
- callback.invoke(resp);
- }
-```
-
-At the javascript side, call the module with javascript function to receive callback data:
-
-```javascript
-event.openURL("http://www.github.com",function(resp){ console.log(resp.result); });
-```
-
-### Component extend
-
-There are label, image, div, scroll, ect. components in weex, you can also customize your own components.
-
-#### Step to customize a component
-
-1. Customize components must extend WXComponent or WXContainer
-2. @WXComponentProp(name=value(value is attr or style of dsl)) for it be recognized by weex SDK.
-3. The access levels of mehtod must be **public**
-4. The component class can not be an inner class
-5. Customize can not be obfuscated by tools like ProGuard
-6. Component methods will be invoked in UI thread, do not put time consuming operation there.
-7. Weex params can be int, double, float, String, Map, List, Array
-
-
-Refer to the following example
-
-```java
-public class MyViewComponent extends WXComponent{
- public MyViewComponent(WXSDKInstance instance, WXDomObject dom,
- WXVContainer parent, String instanceId, boolean isLazy)
- {
- public MyViewComponent(WXSDKInstance instance, WXDomObject dom,
- WXVContainer parent, String instanceId, boolean isLazy) {
- super(instance, dom, parent, instanceId, isLazy);
- }
-
- @Override
- protected void initView() {
- mHost = new TextView(mContext);
- }
- @WXComponentProp(name=WXDomPropConstant.WX_ATTR_VALUE)
- public void setMyViewValue(String value) {
- ((TextView)mHost).setText(value);
- }
-}
-```
-
-#### Register the Component
-
-
-```java
-WXSDKEngine.registerComponent("MyView", MyViewComponent.class);
-```
-
-### Adapter extend
-
-#### ImagedownloadAdapter
-
-Weex SDK has no image download capability, you need to implement `IWXImgLoaderAdapter`. Refer to the following examples.
-
-```java
-public class ImageAdapter implements IWXImgLoaderAdapter {
-
- private Activity mContext;
-
- public ImageAdapter(Activity activity) {
- mContext = activity;
- }
-
- @Override
- public void setImage(final String url, final ImageView view,
- WXImageQuality quality, WXImageStrategy strategy) {
- mContext.runOnUiThread(new Runnable() {
-
- @Override
- public void run() {
- if (TextUtils.isEmpty(url)) {
- view.setImageBitmap(null);
- return;
- }
- String temp = url;
- if (url.startsWith("//")){
- temp = "http:" + url;
- }
- if (view.getLayoutParams().width<=0 || view.getLayoutParams().height<=0) {
- return;
- }
- Picasso.with(WXEnvironment.getApplication())
- .load(temp)
- .resize(view.getLayoutParams().width,
- view.getLayoutParams().height).into(view);
- }
- });
- }
-}
-```
-
-#### Component Method
-from WeexSDK `0.9.5`, you can define your component method
-
-for example, define a method in component:
-
-```java
-@JSMethod
-public void focus(){
-//method implementation
-}
-```
-
-after your registration for your own custom component, now you can call it in your js file.
-
-```html
-<template>
- <mycomponent id='mycomponent'></mycomponent>
-</template>
-<script>
- module.exports = {
- created: function() {
- this.$el('mycomponent').focus();
- }
- }
-</script>
-```
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/v-0.10/advanced/extend-to-html5.md
----------------------------------------------------------------------
diff --git a/_draft/v-0.10/advanced/extend-to-html5.md b/_draft/v-0.10/advanced/extend-to-html5.md
deleted file mode 100644
index 6201fc7..0000000
--- a/_draft/v-0.10/advanced/extend-to-html5.md
+++ /dev/null
@@ -1,258 +0,0 @@
----
-title: Extend to web
-type: advanced
-order: 8
-has_chapter_content: true
-version: 0.10
----
-
-# Extend Weex HTML5
-
-### Intro
-
-Weex is a extendable cross-platform solution for dynamic programming and publishing projects. You can build your own components on web platform or native platform by extending the components system. Also you can extend weex by adding new methods for one module, new moudles or new bundle loaders. Follow the steps bellow you can dive into the journy of creating multiple builtin components, APIs and loaders.
-
-First of all, components, APIs and loaders are extensions to weex, so you can create your extensions without requiring the weex package, that means your extensions can be totally standalone.
-
-Second, you should always implement a extension for all the three platforms (android, ios and web), except that you only use it on one specific platform. After all weex is a cross platform framework and the equality of user expierence in all platforms is very important. Although you can create components separately on one platform by another, or welcome other developers on other platforms to join your work (You can always find coders who want the same feature with you in the commity). Here are docs about how to create native extensions on [ios](./extend-to-ios.html) and [android](./extend-to-android.html).
-
-You should publish your extensions somewhere weex developers can easily find, somewhere popular, independent and easy to search and use, such as, npm. Npm is what we strongly recommended.
-
-The most important thing is, you'd better name your extension appropriately: it should begin with a `weex-` if it is a weex extension, and it should end up with a `-<platform>` as a platform mark. If your package is wrapped up with all the three platforms you can ignore it through. Here is a demonstrating component [`<weex-hello-web>`](https://github.com/MrRaindrop/weex-hello-web) to show how to define your own component.
-
-### Create a new component
-
-Steps:
-
-1. Extend `Weex.Component`, override methods of component class.
-2. Use `Weex.registerComponent` to register your customized component in the `init` method of the installation module.
-3. export the `init` method for the installation (Every weex-html5 extension has to have a `init` method in the export object, which is for another weex project to install.)
-
-Here's a example to create a weex component for web platform (weex-html5):
-
-```javascript
-const attr = {
- // ...
-}
-const style = {
- // ...
-}
-const event = {
- // ...
-}
-// every extension file should have a init method.
-function init (Weex) {
- const Component = Weex.Component
- const extend = Weex.utils.extend
-
- // the component's constructor
- function Hello (data) {
- Component.call(this, data)
- }
-
- // extend the prototype
- Hello.prototype = Object.create(Component.prototype)
- extend(Hello.prototype, proto)
-
- // config the attributes, styles and events.
- extend(Hello.prototype, { attr })
- extend(Hello.prototype, {
- style: extend(Object.create(Component.prototype.style), style)
- })
- extend(Hello.prototype, { event })
-
- Weex.registerComponent('weex-hello', Hello)
-}
-
-// export the init method.
-export default { init }
-```
-
-The code above is extracted from [weex-hello-web/src/index.js](https://github.com/MrRaindrop/weex-hello-web/blob/master/src/index.js#L46-L65).
-
-This demo has overrided the `create` method of the base class `Component`. You can also override other methods to customize your component's behavior. The typical methods of class `Component` you may override are:
-
-* `create`: to create the node of the component, and return it.
-* `createChildren` to create the children's nodes.
-* `insertBefore` to insert a child before another child.
-* `appendChild` to append a child in the children list.
-* `removeChild` to remove a child in the children list.
-
-**Advanced**: Need more code demonstrations about overriding the component's methods ? Just take a look at the [weex repo's code](https://github.com/apache/incubator-weex/tree/dev/html5/). Basically the most of the built-in components are defined this way.
-
-Important! To register your component in the `init` method, use `Weex.registerComponent`. Here's the demo code:
-
-```javascript
-Weex.registerComponent('weex-hello', Hello)
-```
-
-The code above is from [weex-hello-web/src/index.js](https://github.com/MrRaindrop/weex-hello-web/blob/master/src/index.js#L62)
-
-Install the component using `Weex.install`.
-
-```javascript
-// import the original weex-html5.
-import weex from 'weex-html5'
-import hello from 'weex-hello-web'
-// install the component.
-weex.install(hello)
-```
-
-The code above is from [weex_extend_demo/src/main.js](https://github.com/MrRaindrop/weex_extend_demo/blob/master/src/main.js#L1-L5)
-
-use the component in your `.we` file:
-
-```html
-<template>
- <div>
- <weex-hello class="hello" style="txt-color:#fff;bg-color:green"
- value="WEEX" onclick="handleClick">
- </weex-hello>
- </div>
-</template>
-```
-
-The code above is from [weex_extend_demo/demo/index.we](https://github.com/MrRaindrop/weex_extend_demo/blob/master/demo/index.we#L10-L15)
-
-### Add a new API
-
-You can add new API modules, or just add a new API for any existing API modules. For example, you can add a new module `user` with APIs like 'login', 'logout' etc. The developer can invoke the API by using `require('@weex-module/moduleName)[methodName](arg1, arg2, ...)` ([Module APIs](../references/api.html)).
-
-Steps:
-
-1. Implement your API modules.
-2. Use `Weex.registerAPIModules` to register your API modules in the init method of your installation module.
-
-**Here is a example for register a new API module**
-
-First create a file named `user.js` for a new module, then define `login/logout` methods.
-
-```javascript
-const user = {
- // for user to login.
- login (callbackId) {
- login.then(res => {
- this.sender.performCallback(callbackId, res)
- }).catch(err => {
- this.sender.performCallback(callbackId, err)
- })
- },
-
- // for user to logout.
- logout (callbackId) {
- logout.then(res => {
- this.sender.performCallback(callbackId, res)
- }).catch(err => {
- this.sender.performCallback(callbackId, err)
- })
- }
-}
-
-// add meta info to user module.
-const meta = {
- user: [{
- name: 'login',
- args: ['function']
- }, {
- name: 'logout',
- args: ['function']
- }]
-}
-
-export default {
- init (Weex) {
- // Register your new module. The last parameter is your
- // new API module's meta info.
- Weex.registerApiModule('user', user, meta)
- }
-}
-```
-
-After above coding work, you can publish this user helper API to npm now, for example, with the name of `weex-user-helper`.
-
-Install the component using `Weex.install` in your new weex project.
-
-```javascript
-import Weex from 'weex-html5'
-import user from 'weex-user-helper'
-
-Weex.install(user)
-```
-
-Use the user helper API in your dsl code (xxx.we):
-
-```html
-<template>
- <div>
- <div class="btn" onclick="handleClick">
- <text>LOGIN</text>
- </div>
- </div>
-</template>
-
-<script>
- var userHelper = require('@weex-module/user')
- module.exports = {
- methods: {
- handleClick: function () {
- userHelper.login(function () {
- // ... do sth. in callback.
- })
- }
- }
- }
-</script>
-```
-
-### Add a new loader
-
-**Loader is only a type of extension for weex-html5 (web platform), native platform is not needing this.**
-
-Weex's builtin loaders to load a weex bundle are `xhr`, `jsonp` and `source`. The default loader is `xhr`. You can register your own loader by using `weex.registerLoader`. For example, you got a service method named `myServe.getWeexBundle`, which can load a weex bundle file through some magical tunnel:
-
-```javascript
-function loadByMyServe(pageId, callback) {
- myServe.getWeexBundle(pageId).then(function (bundle) {
- callback(bundle)
- }).catch(function(err) {
- callback(err)
- })
-}
-
-// export the init method to enable weex install this loader.
-export default {
- init (Weex) {
- Weex.registerLoader('myserve', loadByMyServe)
- }
-}
-```
-
-install and use your loader in your project's entry file:
-
-```javascript
-import Weex from 'weex-html5'
-
-// or import from './myserve.js', no matter where you can import your loader file.
-import loader from 'myLoader'
-
-Weex.install(loader)
-
-// use your loader in the init function:
-(function () {
- function getUrlParam (key) {
- const reg = new RegExp('[?|&]' + key + '=([^&]+)')
- const match = location.search.match(reg)
- return match && match[1]
- }
- const page = getUrlParam('page') || 'examples/build/index.js'
- Weex.init({
- appId: location.href,
- loader: 'myserve', // use the loader type you defined.
- source: page,
- rootId: 'weex'
- })
-})();
-```
-
-That's the major extension feature weex brought to you. The deep details can be found in the [weex's repo](https://github.com/alibaba/weex) and the weex's community.
-
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/v-0.10/advanced/extend-to-ios.md
----------------------------------------------------------------------
diff --git a/_draft/v-0.10/advanced/extend-to-ios.md b/_draft/v-0.10/advanced/extend-to-ios.md
deleted file mode 100644
index bddb96e..0000000
--- a/_draft/v-0.10/advanced/extend-to-ios.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-title: Extend to iOS
-type: advanced
-order: 7
-has_chapter_content: true
-version: 0.10
----
-
-# Extend to iOS
-
-### Module extend
-
-Weex SDK provides only rendering capabilities, rather than have other capabilities, such as network, picture, and URL redirection. If you want these features, you need to implement it.
-
-For example: If you want to implement an address jumping function, you can achieve a Module following the steps below.
-
-#### Step to customize a module
-
-1. Module
- customized must implement WXModuleProtocol
-2. A macro named `WX_EXPORT_METHOD` must be added, as it is the only way to be recognized by Weex. It takes arguments that specifies the method in module called by JavaScript code.
-3. The weexInstance should be synthesized. Each module object is bind to a specific instance.
-4. Module methods will be invoked in UI thread, so do not put time consuming operation there. If you want to execute the whole module methods in other thread, please implement the method `- (NSThread *)targetExecuteThread` in protocol. In the way, tasks distributed to this module will be executed in targetExecuteThread.
-5. Weex params can be String or Map.
-6. Module supports to return results to Javascript in callback. This callback is type of `WXModuleCallback`, the params of which can be String or Map.
-
-```objective-c
-@implementation WXEventModule
-@synthesize weexInstance;
- WX_EXPORT_METHOD(@selector(openURL:callback))
-
-- (void)openURL:(NSString *)url callback:(WXModuleCallback)callback
-{
- NSString *newURL = url;
- if ([url hasPrefix:@"//"]) {
- newURL = [NSString stringWithFormat:@"http:%@", url];
- } else if (![url hasPrefix:@"http"]) {
- newURL = [NSURL URLWithString:url relativeToURL:weexInstance.scriptURL].absoluteString;
- }
-
- UIViewController *controller = [[WXDemoViewController alloc] init];
- ((WXDemoViewController *)controller).url = [NSURL URLWithString:newURL];
-
- [[weexInstance.viewController navigationController] pushViewController:controller animated:YES];
- callback(@{@"result":@"success"});
-}
-
-@end
-```
-
-#### Register the module
-
-You can register the customized module by calling the method `registerModule:withClass` in WXSDKEngine.
-
-```objective-c
-WXSDKEngine.h
-/**
-* @abstract Registers a module for a given name
-* @param name The module name to register
-* @param clazz The module class to register
-**/
-+ (void)registerModule:(NSString *)name withClass:(Class)clazz;
-
-[WXSDKEngine registerModule:@"event" withClass:[WXEventModule class]];
-```
-
-### Handler extend
-
-Weex SDK doesn't have capabilitis, such as image download 、navigator operation，please implement these protocols by yourself.
-
-#### WXImgLoaderProtocol
-<font color="gray">
-Weex SDK has no image download capability, you need to implement `WXImgLoaderProtocol`. Refer to the following examples.
-
-```objective-c
-WXImageLoaderProtocol.h
-@protocol WXImgLoaderProtocol <WXModuleProtocol>
-
-/**
- * @abstract Creates a image download handler with a given URL
- * @param imageUrl The URL of the image to download
- * @param imageFrame The frame of the image you want to set
- * @param options : The options to be used for this download
- * @param completedBlock : A block called once the download is completed.
- image : the image which has been download to local.
- error : the error which has happened in download.
- finished : a Boolean value indicating whether download action has finished.
- */
- -(id<WXImageOperationProtocol>)downloadImageWithURL:(NSString *)url imageFrame:(CGRect)imageFrame userInfo:(NSDictionary *)options completed:(void(^)(UIImage *image, NSError *error, BOOL finished))completedBlock;
- @end
-```
-
-Implement above protocol as follows.
-
-
-```objective-c
-@implementation WXImgLoaderDefaultImpl
-#pragma mark -
-#pragma mark WXImgLoaderProtocol
-
-- (id<WXImageOperationProtocol>)downloadImageWithURL:(NSString *)url imageFrame:(CGRect)imageFrame userInfo:(NSDictionary *)userInfo completed:(void(^)(UIImage *image, NSError *error, BOOL finished))completedBlock
-{
- if ([url hasPrefix:@"//"]) {
- url = [@"http:" stringByAppendingString:url];
- }
- return (id<WXImageOperationProtocol>)[[SDWebImageManager sharedManager] downloadImageWithURL:[NSURL URLWithString:url] options:0 progress:^(NSInteger receivedSize, NSInteger expectedSize) {
- } completed:^(UIImage *image, NSError *error, SDImageCacheType cacheType, BOOL finished, NSURL *imageURL) {
- if (completedBlock) {
- completedBlock(image, error, finished);
- }
- }];
-}
-@end
-```
-
-#### Register the handler
-
-You can register the handler which implements the protocol by calling `registerHandler:withProtocol` in WXSDKEngine.
-
-```objective-c
-WXSDKEngine.h
-/**
-* @abstract Registers a handler for a given handler instance and specific protocol
-* @param handler The handler instance to register
-* @param protocol The protocol to confirm
-*/
-+ (void)registerHandler:(id)handler withProtocol:(Protocol *)protocol;
-
-[WXSDKEngine registerHandler:[WXImgLoaderDefaultImpl new] withProtocol:@protocol(WXImgLoaderProtocol)];
-```
-
-## Custom Native Components for iOS
-
-### Component extend
-
-There are a lot of native components ready to be used in the Weex SDK, but users always have their own use cases. You might have written an awesome native UI widget in your previous work and just want to wrap up it and export to Weex. So we provide a way to enable developers to create their own custom fully-native components.
-
-This guide will use the implementation of existing component `image` to show you how to build a native component. It will also assume that you are familiar with iOS programming.
-
-#### Registration
-
-Defining a custom native component is simple. Just call `[WXSDKEngine registerComponent:withClass:]` with the component's tag name as first argument.
-
-```objective-c
-[WXSDKEngine registerComponent:@"image" withClass:[WXImageComponent class]];
-```
-
-Then you can create a `WXImageComponent` class to represent the implementation of image component.
-
-Now you can use `<image>` wherever you want in the template.
-
-```html
-<image></image>
-```
-
-#### Adding Properties
-
-The next thing we can do is to extend some native properties to make the component more powerful. As an image, let's say we should have a `src` attribute as image's remote source and a `resize` attribute as image's resize mode(contain/cover/stretch).
-
-```objective-c
-@interface WXImageComponent ()
-
-@property (nonatomic, strong) NSString *imageSrc;
-@property (nonatomic, assign) UIViewContentMode resizeMode;
-
-@end
-```
-
-All of the styles, attributes and events will be passed to the component's initialization method, so here you can store the properties which you are interested in.
-
-```objective-c
-@implementation WXImageComponent
-
-- (instancetype)initWithRef:(NSString *)ref type:(NSString *)type styles:(NSDictionary *)styles attributes:(NSDictionary *)attributes events:(NSArray *)events weexInstance:(WXSDKInstance *)weexInstance
-{
- if (self = [super initWithRef:ref type:type styles:styles attributes:attributes events:events weexInstance:weexInstance]) {
- _imageSrc = [WXConvert NSString:attributes[@"src"]];
- _resizeMode = [WXConvert UIViewContentMode:attributes[@"resize"]];
- }
-
- return self;
-}
-
-@end
-```
-
-The properties getted in the attributes are of `id` type, so we have to convert them to the type we want using a conversion function. Basic conversion functions can be found in the `WXConvert` file, or you can just add your own conversion function.
-
-
-#### Hooking Render Life Cycle
-
-A Native Component has a life cycle managed by Weex. Weex creates it, layout it, renders it and destroys it.
-
-Weex offers component life cycle hooks that give you visibility into these key moments and the ability to act when they occur.
-
-method| description
-:----:|------
-initWithRef:type:...| Initializes a new component using the specified properties.
-layoutDidFinish | Called when the component has just laid out.
-loadView | Creates the view that the component manages.
-viewWillLoad | Called before the load of component's view .
-viewDidLoad | Called after the component's view is loaded and set.
-viewWillUnload | Called just before releasing the component's view.
-viewDidUnload | Called when the component's view is released.
-updateStyles:| Called when component's style are updated.
-updateAttributes:| Called when component's attributes are updated.
-addEvent:| Called when adding an event to the component.
-removeEvent:| Called when removing an event frome the component.
-
-
-As in the image component example, if we need to use our own image view, we can override the `loadView` method.
-
-
-```objective-c
-- (UIView *)loadView
-{
- return [[WXImageView alloc] init];
-}
-```
-
-Now Weex will use `WXImageView` to render the `image` component.
-
-As an image component, we will need to fetch the remote image and set it to the image view. This can be done in `viewDidLoad` method when the view is created and loaded. `viewDidLoad` is also the best time to perform additional initialization for your view， such as content mode changing.
-
-
-```objective-c
-- (void)viewDidLoad
-{
- UIImageView *imageView = (UIImageView *)self.view;
- imageView.contentMode = _resizeMode;
- imageView.userInteractionEnabled = YES;
- imageView.clipsToBounds = YES;
- imageView.exclusiveTouch = YES;
-
- // Do your image fetching and updating logic
-}
-```
-
-If image's remote source can be changed, you can also hook the `updateAttributes:` method to perform your attributes changing logic. Component's view always has been loaded while `updateAttributes:` or `updateStyles:` is called.
-
-
-```objective-c
-- (void)updateAttributes:(NSDictionary *)attributes
-{
- if (attributes[@"src"]) {
- _imageSrc = [WXConvert NSString:attributes[@"src"]];
- // Do your image updating logic
- }
-
- if (attributes[@"resize"]) {
- _resizeMode = [WXConvert UIViewContentMode:attributes[@"resize"]];
- self.view.contentMode = _resizeMode;
- }
-}
-```
-
-Maybe there is even more life cycle hooks you might need to consider, such as `layoutDidFinish` while layout computing is finished. If you want to go deeper, check out the `WXComponent.h` file in the source code.
-
-Now you can use `<image>` and its attributes wherever you want in the template.
-
-```html
-<image style="your-custom-style" src="image-remote-source" resize="contain/cover/stretch"></image>
-```
-#### Component Method
-from WeexSDK `0.9.5`, you can define your component method by macro `WX_EXPORT_METHOD`
-for example:
-
-```
-@implementation WXMyComponent
- +WX_EXPORT_METHOD(@selector(focus))
- +- (instancetype)initWithRef:(NSString *)ref type:(NSString *)type styles:(NSDictionary *)styles attributes:(NSDictionary *)attributes events:(NSArray *)events weexInstance:(WXSDKInstance *)weexInstance
- {
- if (self = [super initWithRef:ref type:type styles:styles attributes:attributes events:events weexInstance:weexInstance]) {
- // handle your attributes
- // handle your styles
- }
-
- return self;
- }
-
-
- - (void)focus
- {
- NSLog(@"you got it");
- }
-@end
-```
-
-after your registration for your own custom component, now you can call it in your js file.
-
-```html
-<template>
- <mycomponent id='mycomponent'></mycomponent>
-</template>
-<script>
- module.exports = {
- created: function() {
- this.$el('mycomponent').focus();
- }
- }
-</script>
-```
-
-
-
-
-
-
-
-
-
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/v-0.10/advanced/how-data-binding-works.md
----------------------------------------------------------------------
diff --git a/_draft/v-0.10/advanced/how-data-binding-works.md b/_draft/v-0.10/advanced/how-data-binding-works.md
deleted file mode 100644
index a207997..0000000
--- a/_draft/v-0.10/advanced/how-data-binding-works.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: How data-binding works
-type: advanced
-order: 2
-has_chapter_content: true
-version: 0.10
----
-
-# How data-binding works
-
-Weex JS Framework is a MVVM framework. It observe data and use `{% raw %}{{bindedKey}}{% endraw %}` syntax to bind in views. When data is changed in anyway, the view will automatically be updated due to data-binding.
-
-For example, The content of a `<text>` component is bound with the key `notes` in data:
-
-```html
-<template>
- <div>
- <text>{{notes}}</text>
- </div>
-<template>
-
-<script>
- module.exports = {
- data: {
- notes: 'Hello'
- }
- }
-</script>
-```
-
-Weex JS Framework first observe the data object to make sure each data change in the future will be observed. And then it will compile the whole `<template>`. When it finds that the content of the `<text>` is bound with `notes`, JS Framework will watch the `data.notes` changes and set a handler which will update the `<text>` content with new `data.notes`. So developer only need to manage the data, the view display could automatically do corresponding changes.
-
-Some special data-binding syntax here:
-
-* `{% raw %}<foo if="{{condition}}">{% endraw %}` will watch the condition value changes. When it changes to `true`, the `<foo>` element will be created and attached, otherwise it will be not created or removed.
-* `{% raw %}<foo repeat="{{list}}">{% endraw %}` will watch the mutations of a list. At the beginning the `<foo>` element will be cloned and attached with each item in list. When some items are added, removed or moved, the `<foo>` element list will be re-generated new content in the right order with minimum alterations.
-* `{% raw %}<foo if="{{condition}}" repeat="{{list}}">{% endraw %}` will process `repeat` first and `if` the second. In another way, it will walk through each item in list, if the item's condition value is true, a `<foo>` element will be cloned and attached with this certain item value.
-
-Compared with virtual DOM diff algorithm, we just "diff" the data and only calculate/update the virtual DOM with minimum alterations for each user interaction or data-change operation. So it's more lightweight and fast especially for small views in mobile devices.
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/v-0.10/advanced/images/how-arch.png
----------------------------------------------------------------------
diff --git a/_draft/v-0.10/advanced/images/how-arch.png b/_draft/v-0.10/advanced/images/how-arch.png
deleted file mode 100644
index a13df7a..0000000
Binary files a/_draft/v-0.10/advanced/images/how-arch.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/12e3a8bc/_draft/v-0.10/advanced/images/how-render.png
----------------------------------------------------------------------
diff --git a/_draft/v-0.10/advanced/images/how-render.png b/_draft/v-0.10/advanced/images/how-render.png
deleted file mode 100644
index db9b0f4..0000000
Binary files a/_draft/v-0.10/advanced/images/how-render.png and /dev/null differ