Merge pull request #134 from francis-du/master

[DOCS] Improved documentation and updated a blog

Author: Functor10

docs/about/faq.md

@@ -1 +1,3 @@
-[English](./faq.md)|[中文](../zh/about/faq.md)
+[English](./faq.md)|[中文](../zh/about/faq.md)
+
+# FAQ

docs/about/license.md

@@ -1,4 +1,4 @@
-## **MIT License**
+# **MIT License**
 
 **Copyright (c) 2018 <QSql Project>**
 

docs/about/release-notes.md

@@ -1,6 +1,6 @@
 [English](./release-notes.md)|[中文](../zh/about/release-notes.md)
 
-## **RELEASE-0.6**
+# **RELEASE-0.6**
 
 **0.6版涉及的改动如下：**
 
@@ -24,5 +24,5 @@
 
 - 支持混算模式下JDBC数据源的分布式查询。
 
-## **RELEASE-0.5**
+# **RELEASE-0.5**
 - 无

docs/blog/2019.md

@@ -1,7 +1,7 @@
-## 2019-08-27
+# 2019-08-27
 
 [360多数据源混合查询引擎的前世今生 | 刘思源](https://mp.weixin.qq.com/s/ZdWi5CtBE_38t-brGkyB3g)
 
-## 2019-01-09
+# 2019-01-09
 
 [Quicksql——更简单，更安全，更快速的跨数据源统一SQL查询引擎 | 360技术](https://mp.weixin.qq.com/s/XUFhq5iwK-Lfbf8vSXr7tA)

docs/blog/2020.md

@@ -0,0 +1,3 @@
+# 2020-01-03
+
+[Quick SQL在线文档主题色投票结果 | Francis](articles/在线文档主题色投票结果.md)

docs/blog/articles/在线文档主题色投票结果.md

@@ -0,0 +1,37 @@
+# Quick SQL在线文档主题色投票结果出来啦
+
+上周四，也就是2020年01月02日，我们发起了一个关于我们
+[在线文档的主题颜色投票](https://form.chinagdg.org/forms/d/e/1FAIpQLSc4CdXZsDZO3jat8rPgm9VEjXfrqlPQB5DCOva0OTcFemp16w/viewform)
+
+首先呢，通过本次投票，极大的鼓舞了 Quick SQL 社区的小伙伴儿的积极性
+(虽然只有20个人参与)，但是群里的小哥看到我们的新的文档
+表示一下充满了信心，要来贡献代码呢~-~
+
+其次，我们正在逐渐的国际化，最近也开了Slack Channel，我们日常的一些
+开发和讨论都在[Slack](https://quicksql.readthedocs.io/en/latest/community/channel/) 
+上，欢迎大家加入讨论和贡献[代码](https://quicksql.readthedocs.io/en/latest/community/contribution-code/)
+和[文档](https://quicksql.readthedocs.io/en/latest/community/contribution-docs/)哦~
+另外我们的翻译平台也在逐步的建立。总之就是我们会越来越好哒^-^
+
+拉好小板凳,现在让我来公布下投票结果~
+
+获得我们`页面整体色调`人数最多奖的是... `Blue(15%)`
+
+![primary](../../../images/primary-color-count.png)
+
+获得我们`鼠标经过时色调`人数最多奖的是... `Red(20%)`
+
+![accent](../../../images/accent-color-count.png)
+
+我们接下来会将我们的主题颜色改成以上的两位获奖色
+感谢大家的投票，希望下次投票人能多点,`手动捂脸.jpg`
+
+## 加入我们
+
+[![Slack](../../../images/slack.png)](https://join.slack.com/t/quicksql/shared_invite/enQtODkwMzM0Njc3NTExLWQxNjRlY2M5YTlkMTk4OTM2YzhjMjUxYTUyN2VlNzJlNzQwM2E4YjkxNzA4MDllODg5NWUxNDY4MTMyMzczMWI)
+[![Github](../../../images/github.png)](https://github.com/qihoo360/Quicksql/issues)
+[![QQ](../../../images/qq.png)](https://jq.qq.com/?_wv=1027&k=5782R6F)
+
+
+
+

docs/community/channel.md

@@ -1,4 +1,4 @@
-## Join us
+# Join us
 
 [![Slack](../images/slack.png)](https://join.slack.com/t/quicksql/shared_invite/enQtODkwMzM0Njc3NTExLWQxNjRlY2M5YTlkMTk4OTM2YzhjMjUxYTUyN2VlNzJlNzQwM2E4YjkxNzA4MDllODg5NWUxNDY4MTMyMzczMWI)
 [![Github](../images/github.png)](https://github.com/qihoo360/Quicksql/issues)

docs/community/contribution-code.md

@@ -1,3 +1,30 @@
 [English](./contribution-code.md)|[中文](../zh/community/contribution-code.md)
 
-## Contributing code
+# Contributing Code
+
+We welcome contributions.
+
+If you are interested in Quicksql, you can download the source code from GitHub and execute the following maven command at the project root directory：
+
+```shell
+mvn -DskipTests clean package
+```
+
+If you are planning to make a large contribution, talk to us first! It helps to agree on the general approach. Log a Issures on GitHub for your proposed feature.
+
+Fork the GitHub repository, and create a branch for your feature.
+
+Develop your feature and test cases, and make sure that `mvn install` succeeds. (Run extra tests if your change warrants it.)
+
+Commit your change to your branch.
+
+If your change had multiple commits, use `git rebase -i master` to squash them into a single commit, and to bring your code up to date with the latest on the main line.
+
+Then push your commit(s) to GitHub, and create a pull request from your branch to the QSQL master branch. Update the JIRA case to reference your pull request, and a committer will review your changes.
+
+The pull request may need to be updated (after its submission) for two main reasons:
+
+1. you identified a problem after the submission of the pull request;
+2. the reviewer requested further changes;
+
+In order to update the pull request, you need to commit the changes in your branch and then push the commit(s) to GitHub. You are encouraged to use regular (non-rebased) commits on top of previously existing ones.

docs/community/contribution-docs.md

@@ -1,6 +1,6 @@
 [English](./contribution-docs.md)|[中文](../zh/community/contribution-docs.md)
 
-## Contributing documents
+# Contributing documents
 
 ## Installing Python
 Install [Python](https://www.python.org/) or [Anaconda](https://www.anaconda.com/).

docs/community/contributors.md

@@ -1,3 +1,5 @@
+# Contributors
+
 Sort alphabetically,Show only GitHub ID without avatar.
 
 ### Without avatar