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:25 UTC
[30/51] [abbrv] incubator-weex-site git commit: fix the markdown
syntax parse error
fix the markdown syntax parse error
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/0e912800
Tree: http://git-wip-us.apache.org/repos/asf/incubator-weex-site/tree/0e912800
Diff: http://git-wip-us.apache.org/repos/asf/incubator-weex-site/diff/0e912800
Branch: refs/heads/master
Commit: 0e912800ffe0c2ae158e335902b3d89c4012390a
Parents: 32a097b
Author: Hanks <zh...@gmail.com>
Authored: Fri Oct 13 12:21:02 2017 +0800
Committer: Hanks <zh...@gmail.com>
Committed: Fri Oct 13 12:21:02 2017 +0800
----------------------------------------------------------------------
_config.yml | 18 ++++++
_config_cn.yml | 18 ++++++
package.json | 3 +-
source/cn/guide/advanced/app-architecture.md | 2 +-
source/cn/wiki/how-it-works.md | 63 -------------------
source/cn/wiki/index.md | 61 ++++++++++++++++++-
source/download.ejs | 3 -
source/playground.ejs | 3 -
source/wiki/css-units.md | 2 +-
source/wiki/how-it-works.md | 71 ----------------------
source/wiki/index.md | 69 ++++++++++++++++++++-
themes/weex/_config.yml | 8 ++-
themes/weex/layout/_partial/post/title.ejs | 4 +-
themes/weex/scripts/helper.js | 4 +-
themes/weex/source/css/partial/highlight.scss | 13 +++-
15 files changed, 188 insertions(+), 154 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/_config.yml
----------------------------------------------------------------------
diff --git a/_config.yml b/_config.yml
index 9dced8b..0b935fa 100644
--- a/_config.yml
+++ b/_config.yml
@@ -111,6 +111,24 @@ pagination_dir: page
## Themes: https://hexo.io/themes/
theme: weex
+# Markdown Syntax
+marked:
+ gfm: true
+ pedantic: false
+ sanitize: false
+ tables: true
+ breaks: true
+ smartLists: true
+ smartypants: true
+ modifyAnchors: ''
+ autolink: true
+
+# Code Highlight
+highlight:
+ enable: true
+ line_number: false
+ tab_replace:
+
# css autoprefixer
autoprefixer:
exclude:
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/_config_cn.yml
----------------------------------------------------------------------
diff --git a/_config_cn.yml b/_config_cn.yml
index 2634b9a..f26b72b 100644
--- a/_config_cn.yml
+++ b/_config_cn.yml
@@ -109,6 +109,24 @@ pagination_dir: page
## Themes: https://hexo.io/themes/
theme: weex
+# Markdown Syntax
+marked:
+ gfm: true
+ pedantic: false
+ sanitize: false
+ tables: true
+ breaks: true
+ smartLists: true
+ smartypants: true
+ modifyAnchors: ''
+ autolink: true
+
+# Code Highlight
+highlight:
+ enable: true
+ line_number: false
+ tab_replace:
+
# css autoprefixer
autoprefixer:
exclude:
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/package.json
----------------------------------------------------------------------
diff --git a/package.json b/package.json
index 083e3b0..c3d43e9 100644
--- a/package.json
+++ b/package.json
@@ -6,7 +6,8 @@
"version": "3.3.9"
},
"scripts": {
- "server": "hexo server"
+ "server": "hexo server",
+ "build": "hexo g -d -w"
},
"dependencies": {
"cheerio": "^1.0.0-rc.2",
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/source/cn/guide/advanced/app-architecture.md
----------------------------------------------------------------------
diff --git a/source/cn/guide/advanced/app-architecture.md b/source/cn/guide/advanced/app-architecture.md
index b19a97e..d68d568 100644
--- a/source/cn/guide/advanced/app-architecture.md
+++ b/source/cn/guide/advanced/app-architecture.md
@@ -1,5 +1,5 @@
---
-title: 用 Weex 构建完整移动应用
+title: 构建完整移动应用
type: guide
group: 高阶特性
order: 8.5
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/source/cn/wiki/how-it-works.md
----------------------------------------------------------------------
diff --git a/source/cn/wiki/how-it-works.md b/source/cn/wiki/how-it-works.md
deleted file mode 100644
index e21fa47..0000000
--- a/source/cn/wiki/how-it-works.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: 工作原理
-type: wiki
-group: Design
-order: 1.1
-has_chapter_content: false
-chapter_title: 优势介绍
-version: 2.1
----
-
-# 工作原理
-
-## 整体架构
-
-Weex 表面上是一个客户端技术，但实际上它串联起了从本地开发环境到云端部署和分发的整个链路。开发者首先可以在本地像撰写 web 页面一样撰写一个 app 的页面，然后编译成一段 JavaScript 代码，形成 Weex 的一个 JS bundle；在云端，开发者可以把生成的 JS bundle 部署上去，然后通过网络请求或预下发的方式传递到用户的移动应用客户端；在移动应用客户端里，WeexSDK 会准备好一个 JavaScript 引擎，并且在用户打开一个 Weex 页面时执行相应的 JS bundle，并在执行过程中产生各种命令发送到 native 端进行的界面渲染或数据存储、网络通信、调用设备功能、用户交互响应等移动应用的场景实践；同时，如果用户没有安装移动应用，他仍然可以在浏览器里打开一个相同的 web 页面，这个页面是使用相同的页面源代码，通过浏览器里的 JavaScript 引擎运行起来的。
-
-
-
-## 本地开发环境
-
-Weex 的本地开发环境基于 web 开发体验而设计，web 开发者可以通过自己熟悉的 HTML/CSS/JavaScript 技术和语法实现移动应用的界面。同时 Weex 也对 [Vue.js](https://vuejs.org/) 这一非常优秀的前端框架做了官方的支持。
-
-除此之外，Weex 的工程设计也是 web 开发者非常熟悉的，首先 web 开发者可以使用自己熟悉的 npm 进行依赖管理；其次 web 开发者在通过项目脚手架初始化工程、开发、调试、质量控制等各个环节，都可以参考 web 开发已有的最佳实践。
-
-和如今 web 开发的最佳实践一样，Weex 会把一个页面的源代码全部编译打包成一个 JS bundle，在浏览器中，我们需要把这个 JS bundle 作为一段 `<script>` 载入网页，在客户端里，我们把这段 JS bundle 载入本地，并通过 WeexSDK 直接执行。
-
-**相关阅读**
-
-* [Weex 和 web 平台的差异](../../references/platform-difference.html)
-* [Vue 2.x 在 Weex 和 web 中的差异](../../references/vue/difference-with-web.html)
-* [快速上手](../index.html)
-* [使用 Devtools](./devtools.html)
-
-## 云端部署和分发
-
-Weex 的 JS bundle 可以作为 web 开发中的一段静态资源进行部署和下发。几乎可以复用 HTML5 所有的工程体系和最佳实践。比如在本地开发环境通过部署工具将 JS bundle 部署到 CDN、通过 CMS 或搭建平台把业务数据和模块化的前端组件自动化拼接生成 JS bundle、通过服务端 JS bundle 的流量和日志统计页面的访问情况、通过 AppCache 或类似的方式对 JS bundle 在客户端进行缓存或预加载以降低网络通信的成本等。
-
-## 客户端 JavaScript 引擎
-
-Weex 的 iOS 和 Android 客户端中都会运行一个 JavaScript 引擎，来执行 JS bundle，同时向各端的渲染层发送规范化的指令，调度客户端的渲染和其它各种能力。我们在 iOS 下选择了 JavaScriptCore 内核，而在 Android 下选择了 UC 提供的 v8 内核。无论是从性能还是稳定性方面都提供了强有力的保障。
-
-为了让整个移动应用的资源利用得更好，我们在客户端提供的 JavaScript 引擎是单例的，即所有 JS bundle 公用一个 JavaScript 内核实例，同时对每个 JS bundle 在运行时进行了上下文的隔离，使得每个 JS bundle 都能够高效安全的工作。我们还把 Vue 2.0 这样的 JS Framework 做了预置，开发者不必把 JS Framework 打包在每个 JS bundle 里，从而大大减少了 JS bundle 的体积，也就进一步保障了页面打开的速度。
-
-## 客户端渲染层
-
-Weex 目前提供了 iOS 和 Android 两个客户端的 native 渲染层。每个端都基于 DOM 模型设计并实现了标准的界面渲染接口供 JavaScript 引擎调用。并且结合 web 标准和 native 的特点和优势实现了一套统一的组件和模块。Weex 在性能方面的表现也是非常优异的，尤其是界面首屏加载时间、native 下长列表的资源开销和复用情况、CPU、内存、帧率 等关键指标。当然，尽管 Weex 官方已经提供了一组开发者最常用的组件和模块，但面对丰富多样的移动应用研发需求，团队也难免会力不从心，为此我们提供了灵活自由的横向扩展能力，开发者可以根据自身的情况定制属于自己的客户端组件和模块，进一步丰富 Weex 在客户端上的能力。
-
-**相关链接**
-
-* [Weex 的组件和模块跟 web 标准的区别](../../references/web-standards.html)
-* [如何使用 iOS](../../references/ios-apis.html)
-* [如何使用 Android](../../references/android-apis.html)
-* [如何扩展 iOS](../../references/advanced/extend-to-ios.html)
-* [如何扩展 Android](../../references/advanced/extend-to-android.html)
-
-## 浏览器渲染
-
-Weex 除了提供 iOS 和 Android 的客户端渲染层之外，还基于 Vue 2.0 对官方的所有组件和模块进行了封装，开发者可以基于 Vue 2.0 用同一套源代码构建出在浏览器中相同效果的页面。并且同样可以横向扩展。
-
-**相关链接**
-
-* [如何使用 HTML5](../../references/html5-apis.html)
-* [如何扩展 HTML5](../../references/advanced/extend-to-html5.html)
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/source/cn/wiki/index.md
----------------------------------------------------------------------
diff --git a/source/cn/wiki/index.md b/source/cn/wiki/index.md
index 8a36f64..e21fa47 100644
--- a/source/cn/wiki/index.md
+++ b/source/cn/wiki/index.md
@@ -1,6 +1,63 @@
---
-title: WiKi
+title: 工作原理
type: wiki
-order: 0
+group: Design
+order: 1.1
+has_chapter_content: false
+chapter_title: 优势介绍
version: 2.1
---
+
+# 工作原理
+
+## 整体架构
+
+Weex 表面上是一个客户端技术，但实际上它串联起了从本地开发环境到云端部署和分发的整个链路。开发者首先可以在本地像撰写 web 页面一样撰写一个 app 的页面，然后编译成一段 JavaScript 代码，形成 Weex 的一个 JS bundle；在云端，开发者可以把生成的 JS bundle 部署上去，然后通过网络请求或预下发的方式传递到用户的移动应用客户端；在移动应用客户端里，WeexSDK 会准备好一个 JavaScript 引擎，并且在用户打开一个 Weex 页面时执行相应的 JS bundle，并在执行过程中产生各种命令发送到 native 端进行的界面渲染或数据存储、网络通信、调用设备功能、用户交互响应等移动应用的场景实践；同时，如果用户没有安装移动应用，他仍然可以在浏览器里打开一个相同的 web 页面，这个页面是使用相同的页面源代码，通过浏览器里的 JavaScript 引擎运行起来的。
+
+
+
+## 本地开发环境
+
+Weex 的本地开发环境基于 web 开发体验而设计，web 开发者可以通过自己熟悉的 HTML/CSS/JavaScript 技术和语法实现移动应用的界面。同时 Weex 也对 [Vue.js](https://vuejs.org/) 这一非常优秀的前端框架做了官方的支持。
+
+除此之外，Weex 的工程设计也是 web 开发者非常熟悉的，首先 web 开发者可以使用自己熟悉的 npm 进行依赖管理；其次 web 开发者在通过项目脚手架初始化工程、开发、调试、质量控制等各个环节，都可以参考 web 开发已有的最佳实践。
+
+和如今 web 开发的最佳实践一样，Weex 会把一个页面的源代码全部编译打包成一个 JS bundle，在浏览器中，我们需要把这个 JS bundle 作为一段 `<script>` 载入网页，在客户端里，我们把这段 JS bundle 载入本地，并通过 WeexSDK 直接执行。
+
+**相关阅读**
+
+* [Weex 和 web 平台的差异](../../references/platform-difference.html)
+* [Vue 2.x 在 Weex 和 web 中的差异](../../references/vue/difference-with-web.html)
+* [快速上手](../index.html)
+* [使用 Devtools](./devtools.html)
+
+## 云端部署和分发
+
+Weex 的 JS bundle 可以作为 web 开发中的一段静态资源进行部署和下发。几乎可以复用 HTML5 所有的工程体系和最佳实践。比如在本地开发环境通过部署工具将 JS bundle 部署到 CDN、通过 CMS 或搭建平台把业务数据和模块化的前端组件自动化拼接生成 JS bundle、通过服务端 JS bundle 的流量和日志统计页面的访问情况、通过 AppCache 或类似的方式对 JS bundle 在客户端进行缓存或预加载以降低网络通信的成本等。
+
+## 客户端 JavaScript 引擎
+
+Weex 的 iOS 和 Android 客户端中都会运行一个 JavaScript 引擎，来执行 JS bundle，同时向各端的渲染层发送规范化的指令，调度客户端的渲染和其它各种能力。我们在 iOS 下选择了 JavaScriptCore 内核，而在 Android 下选择了 UC 提供的 v8 内核。无论是从性能还是稳定性方面都提供了强有力的保障。
+
+为了让整个移动应用的资源利用得更好，我们在客户端提供的 JavaScript 引擎是单例的，即所有 JS bundle 公用一个 JavaScript 内核实例，同时对每个 JS bundle 在运行时进行了上下文的隔离，使得每个 JS bundle 都能够高效安全的工作。我们还把 Vue 2.0 这样的 JS Framework 做了预置，开发者不必把 JS Framework 打包在每个 JS bundle 里，从而大大减少了 JS bundle 的体积，也就进一步保障了页面打开的速度。
+
+## 客户端渲染层
+
+Weex 目前提供了 iOS 和 Android 两个客户端的 native 渲染层。每个端都基于 DOM 模型设计并实现了标准的界面渲染接口供 JavaScript 引擎调用。并且结合 web 标准和 native 的特点和优势实现了一套统一的组件和模块。Weex 在性能方面的表现也是非常优异的，尤其是界面首屏加载时间、native 下长列表的资源开销和复用情况、CPU、内存、帧率 等关键指标。当然，尽管 Weex 官方已经提供了一组开发者最常用的组件和模块，但面对丰富多样的移动应用研发需求，团队也难免会力不从心，为此我们提供了灵活自由的横向扩展能力，开发者可以根据自身的情况定制属于自己的客户端组件和模块，进一步丰富 Weex 在客户端上的能力。
+
+**相关链接**
+
+* [Weex 的组件和模块跟 web 标准的区别](../../references/web-standards.html)
+* [如何使用 iOS](../../references/ios-apis.html)
+* [如何使用 Android](../../references/android-apis.html)
+* [如何扩展 iOS](../../references/advanced/extend-to-ios.html)
+* [如何扩展 Android](../../references/advanced/extend-to-android.html)
+
+## 浏览器渲染
+
+Weex 除了提供 iOS 和 Android 的客户端渲染层之外，还基于 Vue 2.0 对官方的所有组件和模块进行了封装，开发者可以基于 Vue 2.0 用同一套源代码构建出在浏览器中相同效果的页面。并且同样可以横向扩展。
+
+**相关链接**
+
+* [如何使用 HTML5](../../references/html5-apis.html)
+* [如何扩展 HTML5](../../references/advanced/extend-to-html5.html)
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/source/download.ejs
----------------------------------------------------------------------
diff --git a/source/download.ejs b/source/download.ejs
deleted file mode 100644
index ef2c86f..0000000
--- a/source/download.ejs
+++ /dev/null
@@ -1,3 +0,0 @@
-layout: download
-type: download
----
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/source/playground.ejs
----------------------------------------------------------------------
diff --git a/source/playground.ejs b/source/playground.ejs
deleted file mode 100644
index 7f3b070..0000000
--- a/source/playground.ejs
+++ /dev/null
@@ -1,3 +0,0 @@
-layout: playground
-type: playground
----
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/source/wiki/css-units.md
----------------------------------------------------------------------
diff --git a/source/wiki/css-units.md b/source/wiki/css-units.md
index cb6d93e..b533bde 100644
--- a/source/wiki/css-units.md
+++ b/source/wiki/css-units.md
@@ -1,5 +1,5 @@
---
-title: CSS unit
+title: CSS Units
type: wiki
group: 样式
order: 3.3
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/source/wiki/how-it-works.md
----------------------------------------------------------------------
diff --git a/source/wiki/how-it-works.md b/source/wiki/how-it-works.md
deleted file mode 100644
index 274e195..0000000
--- a/source/wiki/how-it-works.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: How it works
-type: wiki
-group: Design
-order: 1.1
-version: 2.1
----
-
-# How it works
-
-## Overall Structure
-
-Weex is a client-side technology on the surface, but in fact it connects the whole way from the local development environment to the cloud deployment and distribution.
-
-Developers can first write an app page just like writing a web page, and then compile the app page into a piece of JavaScript which is called Weex JS bundle.
-
-In the cloud, developers can deploy the generated JS bundle. And then it can be requested or pre-fetched from a mobile app with WeexSDK.
-
-The WeexSDK would prepare a JavaScript engine to run corresponding JS bundle when user opens a Weex page anytime. Usually the JS bundle will make some calls to native-side through Weex JS bridge. They let native-side render the user interface or handle user interactions, storage data, make network communications, call device powers and so on.
-
-Even if a user does not install the App, he can still open a same web page in the browser, using the same source code.
-
-
-
-## Local Development Environment
-
-The design of local development environment of Weex is based on the web development experience. It help web developers writing mobile app UI with their familiar HTML / CSS / JavaScript. At the same time Weex also do the official support to [Vue.js](https://vuejs.org/), a very great front-end framework.
-
-In addition, the management of a Weex project is also very familiar with a web project. First, web developers can use npm packages to manage dependencies. Second, web developers can refer to all best practices from every process of a web project such as scaffolding, development, preview, debugging, test etc.
-
-Also same as the best practice of web development, each Weex page will be built into a JS bundle. In the browser, we put JS bundle into the web page as a `<script>` tag. In the client, we put JS bundle into the local, and execute it in WeexSDK.
-
-**Links**
-
-* [Platform differences between Weex and web](../../references/platform-difference.html)
-* [Differences of using Vue between Weex with web](../../references/vue/difference-with-web.html)
-* [Get Started](../index.html)
-* [Using Devtools](./devtools.html)
-
-## Cloud Deployment & Distribution
-
-Weex JS bundle can be deployed and distributed as a static resource. Almost all current web development system and best practice can be applied to Weex directly such as generating JS bundle through CMS system or deploying JS bundle to static CDN, monitoring JS bundle traffic through server log, caching or pre-fetching JS bundle to reduce networking cost etc.
-
-## Client-side JavaScript Engine
-
-Both iOS and Android client-side of Weex run a JavaScript engine to execute JS bundles and send well defined instructions to the native render layers. We choose JavaScriptCore in iOS and v8 in Android which provide strong performance and stability.
-
-In order to make the mobile resources better utilized, we just run only one instance of JavaScript for all Weex pages. That is, all JS bundles share the same JavaScript instance, but each JS bundle context also isolated well by default in the runtime. We also put Vue 2.0 as a built-in JS Framework, developers do not have to pack it in each JS bundle, which save the size and time of networking.
-
-## Client Rendering Layer
-
-Weex offers both iOS and Android native rendering layers. Each of them are based on the Native DOM model and exposed to JavaScript APIs. At the same time we provide a set of native components and modules to use. Also Weex has high performance especially on first-screen loading time, memory cost and re-reuse of long list, etc.
-
-Although Weex has provided a group of most commonly used components and modules officially. But we definitely know they couldn't satisfy everyone. So we design our native render as extendable as possible. You can extend more components and modules on your own. We can build and share an Weex eco-system together.
-
-**Links**
-
-* [Differences between Weex and web standard](../../references/web-standards.html)
-* [Using Weex in iOS](../../references/ios-apis.html)
-* [Using Weex in Android](../../references/android-apis.html)
-* [Extend to iOS](../../references/advanced/extend-to-ios.html)
-* [Extend to Android](../../references/advanced/extend-to-android.html)
-
-## In the Browser
-
-Besides iOS and Android client, Weex also has a web version based on Vue 2.0. Developers can just use Vue 2.0 to build the same page in browsers.
-
-**Links**
-
-* [Using Weex in HTML5](../../references/html5-apis.html)
-* [Extend to HTML5](../../references/advanced/extend-to-html5.html)
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/source/wiki/index.md
----------------------------------------------------------------------
diff --git a/source/wiki/index.md b/source/wiki/index.md
index 8a36f64..274e195 100644
--- a/source/wiki/index.md
+++ b/source/wiki/index.md
@@ -1,6 +1,71 @@
---
-title: WiKi
+title: How it works
type: wiki
-order: 0
+group: Design
+order: 1.1
version: 2.1
---
+
+# How it works
+
+## Overall Structure
+
+Weex is a client-side technology on the surface, but in fact it connects the whole way from the local development environment to the cloud deployment and distribution.
+
+Developers can first write an app page just like writing a web page, and then compile the app page into a piece of JavaScript which is called Weex JS bundle.
+
+In the cloud, developers can deploy the generated JS bundle. And then it can be requested or pre-fetched from a mobile app with WeexSDK.
+
+The WeexSDK would prepare a JavaScript engine to run corresponding JS bundle when user opens a Weex page anytime. Usually the JS bundle will make some calls to native-side through Weex JS bridge. They let native-side render the user interface or handle user interactions, storage data, make network communications, call device powers and so on.
+
+Even if a user does not install the App, he can still open a same web page in the browser, using the same source code.
+
+
+
+## Local Development Environment
+
+The design of local development environment of Weex is based on the web development experience. It help web developers writing mobile app UI with their familiar HTML / CSS / JavaScript. At the same time Weex also do the official support to [Vue.js](https://vuejs.org/), a very great front-end framework.
+
+In addition, the management of a Weex project is also very familiar with a web project. First, web developers can use npm packages to manage dependencies. Second, web developers can refer to all best practices from every process of a web project such as scaffolding, development, preview, debugging, test etc.
+
+Also same as the best practice of web development, each Weex page will be built into a JS bundle. In the browser, we put JS bundle into the web page as a `<script>` tag. In the client, we put JS bundle into the local, and execute it in WeexSDK.
+
+**Links**
+
+* [Platform differences between Weex and web](../../references/platform-difference.html)
+* [Differences of using Vue between Weex with web](../../references/vue/difference-with-web.html)
+* [Get Started](../index.html)
+* [Using Devtools](./devtools.html)
+
+## Cloud Deployment & Distribution
+
+Weex JS bundle can be deployed and distributed as a static resource. Almost all current web development system and best practice can be applied to Weex directly such as generating JS bundle through CMS system or deploying JS bundle to static CDN, monitoring JS bundle traffic through server log, caching or pre-fetching JS bundle to reduce networking cost etc.
+
+## Client-side JavaScript Engine
+
+Both iOS and Android client-side of Weex run a JavaScript engine to execute JS bundles and send well defined instructions to the native render layers. We choose JavaScriptCore in iOS and v8 in Android which provide strong performance and stability.
+
+In order to make the mobile resources better utilized, we just run only one instance of JavaScript for all Weex pages. That is, all JS bundles share the same JavaScript instance, but each JS bundle context also isolated well by default in the runtime. We also put Vue 2.0 as a built-in JS Framework, developers do not have to pack it in each JS bundle, which save the size and time of networking.
+
+## Client Rendering Layer
+
+Weex offers both iOS and Android native rendering layers. Each of them are based on the Native DOM model and exposed to JavaScript APIs. At the same time we provide a set of native components and modules to use. Also Weex has high performance especially on first-screen loading time, memory cost and re-reuse of long list, etc.
+
+Although Weex has provided a group of most commonly used components and modules officially. But we definitely know they couldn't satisfy everyone. So we design our native render as extendable as possible. You can extend more components and modules on your own. We can build and share an Weex eco-system together.
+
+**Links**
+
+* [Differences between Weex and web standard](../../references/web-standards.html)
+* [Using Weex in iOS](../../references/ios-apis.html)
+* [Using Weex in Android](../../references/android-apis.html)
+* [Extend to iOS](../../references/advanced/extend-to-ios.html)
+* [Extend to Android](../../references/advanced/extend-to-android.html)
+
+## In the Browser
+
+Besides iOS and Android client, Weex also has a web version based on Vue 2.0. Developers can just use Vue 2.0 to build the same page in browsers.
+
+**Links**
+
+* [Using Weex in HTML5](../../references/html5-apis.html)
+* [Extend to HTML5](../../references/advanced/extend-to-html5.html)
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/themes/weex/_config.yml
----------------------------------------------------------------------
diff --git a/themes/weex/_config.yml b/themes/weex/_config.yml
index 357381c..2f5670e 100644
--- a/themes/weex/_config.yml
+++ b/themes/weex/_config.yml
@@ -7,6 +7,12 @@ rss: /atom.xml
# Content
excerpt_link: Read More
+# Code Highlight
+highlight:
+ enable: true
+ line_number: false
+ tab_replace:
+
# Sidebar
sidebar: right
widgets:
@@ -39,4 +45,4 @@ node_sass:
debug: false
outputStyle: nested
precision: 5
- sourceComments: false
\ No newline at end of file
+ sourceComments: false
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/themes/weex/layout/_partial/post/title.ejs
----------------------------------------------------------------------
diff --git a/themes/weex/layout/_partial/post/title.ejs b/themes/weex/layout/_partial/post/title.ejs
index 2b487bf..f032749 100644
--- a/themes/weex/layout/_partial/post/title.ejs
+++ b/themes/weex/layout/_partial/post/title.ejs
@@ -14,5 +14,5 @@
</h1>
<% } %>
<% } %>
- <time class="article-date" datetime="<%= date_xml(post.date) %>">Updated time: <%= date(post.date, 'DD/MM/YYYY') %></time>
-</header>
\ No newline at end of file
+ <!-- <time class="article-date" datetime="<%= date_xml(post.date) %>">Updated time: <%= date(post.date, 'DD/MM/YYYY') %></time> -->
+</header>
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/themes/weex/scripts/helper.js
----------------------------------------------------------------------
diff --git a/themes/weex/scripts/helper.js b/themes/weex/scripts/helper.js
index 7efab2a..07a7df5 100644
--- a/themes/weex/scripts/helper.js
+++ b/themes/weex/scripts/helper.js
@@ -15,7 +15,7 @@ hexo.extend.helper.register('url_for_lang', function(path){
})
hexo.extend.helper.register('page_anchor', function(str){
- var $ = cheerio.load(str, {decodeEntities: false});
+ var $ = cheerio.load(str, {decodeEntities: true});
var headings = $('h1, h2, h3, h4, h5, h6');
if (!headings.length) return str;
@@ -53,4 +53,4 @@ hexo.extend.helper.register('pick_lang', function(lang){
}
return url
-})
\ No newline at end of file
+})
http://git-wip-us.apache.org/repos/asf/incubator-weex-site/blob/0e912800/themes/weex/source/css/partial/highlight.scss
----------------------------------------------------------------------
diff --git a/themes/weex/source/css/partial/highlight.scss b/themes/weex/source/css/partial/highlight.scss
index 9c9a63f..3fa65c2 100644
--- a/themes/weex/source/css/partial/highlight.scss
+++ b/themes/weex/source/css/partial/highlight.scss
@@ -27,10 +27,19 @@ pre code {
.highlight {
margin: 5px 0 15px 0;
overflow-x: auto;
- pre {
+
+ .gutter pre {
+ background: #F3F5F7;
+ margin: 0;
+ padding: 10px 5px;
+ width: 50px;
+ color: #585d65;
+ }
+
+ .code pre {
background: #F3F5F7;
margin: 0;
- padding: 10 20px;
+ padding: 10px 20px;
color: #585d65;
overflow-x: auto;
border-radius: 5px;