[
{
"path": ".gitignore",
"content": "_site\n.DS_Store\n\n"
},
{
"path": "404.html",
"content": "---\nlayout: default\ntitle: 404\nhide-in-nav: true\ndescription: \"这里什么都没有 :(\"\nheader-img: \"img/404-bg.jpg\"\npermalink: /404.html\n---\n\n\n\n{% include intro-header.html type=\"page\" short='true' %}\n\n\n"
},
{
"path": "Gruntfile.js",
"content": "module.exports = function(grunt) {\n\n // Project configuration.\n grunt.initConfig({\n pkg: grunt.file.readJSON('package.json'),\n uglify: {\n main: {\n src: 'js/<%= pkg.name %>.js',\n dest: 'js/<%= pkg.name %>.min.js'\n }\n },\n less: {\n expanded: {\n options: {\n paths: [\"css\"]\n },\n files: {\n \"css/<%= pkg.name %>.css\": \"less/<%= pkg.name %>.less\"\n }\n },\n minified: {\n options: {\n paths: [\"css\"],\n cleancss: true\n },\n files: {\n \"css/<%= pkg.name %>.min.css\": \"less/<%= pkg.name %>.less\"\n }\n }\n },\n banner: '/*!\\n' +\n ' * <%= pkg.title %> v<%= pkg.version %> (<%= pkg.homepage %>)\\n' +\n ' * Copyright <%= grunt.template.today(\"yyyy\") %> <%= pkg.author %>\\n' +\n ' */\\n',\n usebanner: {\n dist: {\n options: {\n position: 'top',\n banner: '<%= banner %>'\n },\n files: {\n src: ['css/<%= pkg.name %>.css', 'css/<%= pkg.name %>.min.css', 'js/<%= pkg.name %>.min.js']\n }\n }\n },\n watch: {\n scripts: {\n files: ['js/<%= pkg.name %>.js'],\n tasks: ['uglify'],\n options: {\n spawn: false,\n },\n },\n less: {\n files: ['less/*.less'],\n tasks: ['less'],\n options: {\n spawn: false,\n }\n },\n },\n });\n\n // Load the plugins.\n grunt.loadNpmTasks('grunt-contrib-uglify');\n grunt.loadNpmTasks('grunt-contrib-less');\n grunt.loadNpmTasks('grunt-banner');\n grunt.loadNpmTasks('grunt-contrib-watch');\n\n // Default task(s).\n grunt.registerTask('default', ['uglify', 'less', 'usebanner']);\n\n};\n"
},
{
"path": "LICENSE",
"content": " Apache License\n Version 2.0, January 2004\n http://www.apache.org/licenses/\n\n TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n 1. Definitions.\n\n \"License\" shall mean the terms and conditions for use, reproduction,\n and distribution as defined by Sections 1 through 9 of this document.\n\n \"Licensor\" shall mean the copyright owner or entity authorized by\n the copyright owner that is granting the License.\n\n \"Legal Entity\" shall mean the union of the acting entity and all\n other entities that control, are controlled by, or are under common\n control with that entity. For the purposes of this definition,\n \"control\" means (i) the power, direct or indirect, to cause the\n direction or management of such entity, whether by contract or\n otherwise, or (ii) ownership of fifty percent (50%) or more of the\n outstanding shares, or (iii) beneficial ownership of such entity.\n\n \"You\" (or \"Your\") shall mean an individual or Legal Entity\n exercising permissions granted by this License.\n\n \"Source\" form shall mean the preferred form for making modifications,\n including but not limited to software source code, documentation\n source, and configuration files.\n\n \"Object\" form shall mean any form resulting from mechanical\n transformation or translation of a Source form, including but\n not limited to compiled object code, generated documentation,\n and conversions to other media types.\n\n \"Work\" shall mean the work of authorship, whether in Source or\n Object form, made available under the License, as indicated by a\n copyright notice that is included in or attached to the work\n (an example is provided in the Appendix below).\n\n \"Derivative Works\" shall mean any work, whether in Source or Object\n form, that is based on (or derived from) the Work and for which the\n editorial revisions, annotations, elaborations, or other modifications\n represent, as a whole, an original work of authorship. For the purposes\n of this License, Derivative Works shall not include works that remain\n separable from, or merely link (or bind by name) to the interfaces of,\n the Work and Derivative Works thereof.\n\n \"Contribution\" shall mean any work of authorship, including\n the original version of the Work and any modifications or additions\n to that Work or Derivative Works thereof, that is intentionally\n submitted to Licensor for inclusion in the Work by the copyright owner\n or by an individual or Legal Entity authorized to submit on behalf of\n the copyright owner. For the purposes of this definition, \"submitted\"\n means any form of electronic, verbal, or written communication sent\n to the Licensor or its representatives, including but not limited to\n communication on electronic mailing lists, source code control systems,\n and issue tracking systems that are managed by, or on behalf of, the\n Licensor for the purpose of discussing and improving the Work, but\n excluding communication that is conspicuously marked or otherwise\n designated in writing by the copyright owner as \"Not a Contribution.\"\n\n \"Contributor\" shall mean Licensor and any individual or Legal Entity\n on behalf of whom a Contribution has been received by Licensor and\n subsequently incorporated within the Work.\n\n 2. Grant of Copyright License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n copyright license to reproduce, prepare Derivative Works of,\n publicly display, publicly perform, sublicense, and distribute the\n Work and such Derivative Works in Source or Object form.\n\n 3. Grant of Patent License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n (except as stated in this section) patent license to make, have made,\n use, offer to sell, sell, import, and otherwise transfer the Work,\n where such license applies only to those patent claims licensable\n by such Contributor that are necessarily infringed by their\n Contribution(s) alone or by combination of their Contribution(s)\n with the Work to which such Contribution(s) was submitted. If You\n institute patent litigation against any entity (including a\n cross-claim or counterclaim in a lawsuit) alleging that the Work\n or a Contribution incorporated within the Work constitutes direct\n or contributory patent infringement, then any patent licenses\n granted to You under this License for that Work shall terminate\n as of the date such litigation is filed.\n\n 4. Redistribution. You may reproduce and distribute copies of the\n Work or Derivative Works thereof in any medium, with or without\n modifications, and in Source or Object form, provided that You\n meet the following conditions:\n\n (a) You must give any other recipients of the Work or\n Derivative Works a copy of this License; and\n\n (b) You must cause any modified files to carry prominent notices\n stating that You changed the files; and\n\n (c) You must retain, in the Source form of any Derivative Works\n that You distribute, all copyright, patent, trademark, and\n attribution notices from the Source form of the Work,\n excluding those notices that do not pertain to any part of\n the Derivative Works; and\n\n (d) If the Work includes a \"NOTICE\" text file as part of its\n distribution, then any Derivative Works that You distribute must\n include a readable copy of the attribution notices contained\n within such NOTICE file, excluding those notices that do not\n pertain to any part of the Derivative Works, in at least one\n of the following places: within a NOTICE text file distributed\n as part of the Derivative Works; within the Source form or\n documentation, if provided along with the Derivative Works; or,\n within a display generated by the Derivative Works, if and\n wherever such third-party notices normally appear. The contents\n of the NOTICE file are for informational purposes only and\n do not modify the License. You may add Your own attribution\n notices within Derivative Works that You distribute, alongside\n or as an addendum to the NOTICE text from the Work, provided\n that such additional attribution notices cannot be construed\n as modifying the License.\n\n You may add Your own copyright statement to Your modifications and\n may provide additional or different license terms and conditions\n for use, reproduction, or distribution of Your modifications, or\n for any such Derivative Works as a whole, provided Your use,\n reproduction, and distribution of the Work otherwise complies with\n the conditions stated in this License.\n\n 5. Submission of Contributions. Unless You explicitly state otherwise,\n any Contribution intentionally submitted for inclusion in the Work\n by You to the Licensor shall be under the terms and conditions of\n this License, without any additional terms or conditions.\n Notwithstanding the above, nothing herein shall supersede or modify\n the terms of any separate license agreement you may have executed\n with Licensor regarding such Contributions.\n\n 6. Trademarks. This License does not grant permission to use the trade\n names, trademarks, service marks, or product names of the Licensor,\n except as required for reasonable and customary use in describing the\n origin of the Work and reproducing the content of the NOTICE file.\n\n 7. Disclaimer of Warranty. Unless required by applicable law or\n agreed to in writing, Licensor provides the Work (and each\n Contributor provides its Contributions) on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n implied, including, without limitation, any warranties or conditions\n of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n PARTICULAR PURPOSE. You are solely responsible for determining the\n appropriateness of using or redistributing the Work and assume any\n risks associated with Your exercise of permissions under this License.\n\n 8. Limitation of Liability. In no event and under no legal theory,\n whether in tort (including negligence), contract, or otherwise,\n unless required by applicable law (such as deliberate and grossly\n negligent acts) or agreed to in writing, shall any Contributor be\n liable to You for damages, including any direct, indirect, special,\n incidental, or consequential damages of any character arising as a\n result of this License or out of the use or inability to use the\n Work (including but not limited to damages for loss of goodwill,\n work stoppage, computer failure or malfunction, or any and all\n other commercial damages or losses), even if such Contributor\n has been advised of the possibility of such damages.\n\n 9. Accepting Warranty or Additional Liability. While redistributing\n the Work or Derivative Works thereof, You may choose to offer,\n and charge a fee for, acceptance of support, warranty, indemnity,\n or other liability obligations and/or rights consistent with this\n License. However, in accepting such obligations, You may act only\n on Your own behalf and on Your sole responsibility, not on behalf\n of any other Contributor, and only if You agree to indemnify,\n defend, and hold each Contributor harmless for any liability\n incurred by, or claims asserted against, such Contributor by reason\n of your accepting any such warranty or additional liability.\n\n END OF TERMS AND CONDITIONS\n\n APPENDIX: How to apply the Apache License to your work.\n\n To apply the Apache License to your work, attach the following\n boilerplate notice, with the fields enclosed by brackets \"{}\"\n replaced with your own identifying information. (Don't include\n the brackets!) The text should be enclosed in the appropriate\n comment syntax for the file format. We also recommend that a\n file or class name and description of purpose be included on the\n same \"printed page\" as the copyright notice for easier\n identification within third-party archives.\n\n Copyright 2015-2016 Huxpro\n\n https://github.com/Huxpro/\n\n Licensed under the Apache License, Version 2.0 (the \"License\");\n you may not use this file except in compliance with the License.\n You may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\n Unless required by applicable law or agreed to in writing, software\n distributed under the License is distributed on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n See the License for the specific language governing permissions and\n limitations under the License.\n\n\n=======================================================================\nHux Blog Subcomponents:\n\nThe Hux Blog project contains subcomponents with separate copyright\nnotices and license terms. Your use of the source code for the these\nsubcomponents is subject to the terms and conditions of the following\nlicenses.\n\n(MIT License) Clean Blog Jekyll Theme: https://github.com/BlackrockDigital/startbootstrap-clean-blog-jekyll/\nhttps://github.com/BlackrockDigital/startbootstrap-clean-blog-jekyll/blob/master/LICENSE\nCopyright (c) 2013-2016 Blackrock Digital LLC.\n"
},
{
"path": "README.md",
"content": "# 小马哥的技术博客 [https://mercyblitz.github.io/](https://mercyblitz.github.io/)\n\n欢迎来到小马哥的技术博客，这里将深入探讨相关技术，包括行业动态，架构设计，设计模式，框架使用，源码分析等。\n\n**博客将不定期更新，请小伙伴们随时关注哦！**\n\n\n\n\n\n\n## [我的文章](https://mercyblitz.github.io/archive/)\n\n\n知识星球：https://t.zsxq.com/72rj2rr\n\nSF : https://segmentfault.com/u/mercyblitz\n\n微信：**mercyblitz-1985**\n\n微博：**mercyblitz**\n\n\n## [我的课程](https://mercyblitz.github.io/lessons/)\n\n\n## [《Spring Boot 编程思想》](https://mercyblitz.github.io/books/thinking-in-spring-boot/)\n\n\n## [关于我](https://mercyblitz.github.io/about/)\n\n\n小马哥，十余年Java EE 从业经验，架构师、微服务布道师、Dubbo 维护者。目前主要负责阿里巴巴集团微服务技术实施、架构衍进、基础设施构建等。重点关注云计算、微服务以及软件架构等领域。通过SUN Java（SCJP、SCWCD、SCBCD）以及Oracle OCA 等的认证。\n\n"
},
{
"path": "README.zh.md",
"content": "# Hux blog 模板\n\n### [我的博客在这里 →](http://huxpro.github.io)\n\n\n### 关于收到\"Page Build Warning\"的email\n\n由于jekyll升级到3.0.x,对原来的pygments代码高亮不再支持，现只支持一种-rouge，所以你需要在 `_config.yml`文件中修改`highlighter: rouge`.另外还需要在`_config.yml`文件中加上`gems: [jekyll-paginate]`.\n\n同时,你需要更新你的本地jekyll环境.\n\n使用`jekyll server`的同学需要这样：\n\n1. `gem update jekyll` # 更新jekyll\n2. `gem update github-pages` #更新依赖的包\n\n使用`bundle exec jekyll server`的同学在更新jekyll后，需要输入`bundle update`来更新依赖的包.\n\n参考文档：[using jekyll with pages](https://help.github.com/articles/using-jekyll-with-pages/) & [Upgrading from 2.x to 3.x](http://jekyllrb.com/docs/upgrading/2-to-3/)\n\n\n## 关于模板(beta)\n\n我的博客仓库——`huxpro.github.io`，是经常修改的，而且还会有人乱提交代码，因此给大家做了一个稳定版的模板。大家可以直接fork模板——`huxblog-boilerplate`,要改的地方我都说明了。或者可以直接下载zip到本地自己去修改。\n\n```\n$ git clone git@github.com:Huxpro/huxblog-boilerplate.git\n```\n\n**[在这里预览模板 →](http://huangxuan.me/huxblog-boilerplate/)**\n\n## 各版本特性\n\n##### New Feature (V1.5.2)\n\n* 当你fork了我的仓库之后，还要删掉里面的关于我的文档是不是感到略烦躁呢？**Boilerplate** 模板将帮助你快速开始，方便合并与更新。\n* `-apple-system`被添加到了字体规则里面了，这套字体格式能将iOS9默认的新字体**San Francisco**表现的非常漂亮。\n* 解决了代码过长自动换行的bug,替换为横向滚动条。详情请见[issue#15](https://github.com/Huxpro/huxpro.github.io/issues/15)\n\n###### 其他历史版本个人觉得没有必要了解，看看英文就行了。\n\n\n\n## 支持\n\n* 你可以自由的fork。如果你能将主题作者和 github 的地址保留在你的页面底部，我将非常感谢你。\n* 如果你喜欢我的这个博客模板，请在`huxpro.github.io`这个repository点个赞——右上角**star**一下。\n\n## 说明文档\n\n* 开始\n\t* [环境要求](#environment)\n\t* [开始](#get-started)\n\t* [写一篇博文](#write-posts)\n* 组件\n\t* [侧边栏](#sidebar)\n\t* [迷你关于我](#mini-about-me)\n\t* [推荐标签](#featured-tags)\n\t* [好友链接](#friends)\n\t* [HTML5 演示文档布局](#keynote-layout)\n* 评论与 Google/Baidu Analytics\n\t* [评论](#comment)\n\t* [网站分析](#analytics) \n* 高级部分\n\t* [自定义](#customization)\n\t* [标题底图](#header-image)\n\t* [搜索展示标题-头文件](#seo-title)\n\n#### Environment\n\n如果你安装了jekyll，那你只需要在命令行输入`jekyll serve`就能在本地浏览器预览主题。你还可以输入`jekyll serve --watch`，这样可以边修改边自动运行修改后的文件。\n\n经 [@BrucZhaoR](https://github.com/BruceZhaoR)的测试，好像两个命令都是可以的自动运行修改后的文件的，刷新后可以实时预览。官方文件是建议安装bundler，这样你在本地的效果就跟在github上面是一样的。详情请见这里：https://help.github.com/articles/using-jekyll-with-pages/#installing-jekyll\n\n\n#### Get Started\n\n你可以通用修改 `_config.yml`文件来轻松的开始搭建自己的博客:\n\n```\n# Site settings\ntitle: Hux Blog # 你的博客网站标题\nSEOTitle: Hux Blog\t\t\t# 在后面会详细谈到\ndescription: \"Cool Blog\" # 随便说点，描述一下\n\n# SNS settings \ngithub_username: huxpro # 你的github账号\nweibo_username: huxpro # 你的微博账号，底部链接会自动更新的。\n\n# Build settings\n# paginate: 10 # 一页你准备放几篇文章\n```\n\nJekyll官方网站还有很多的参数可以调，比如设置文章的链接形式...网址在这里：[Jekyll - Official Site](http://jekyllrb.com/) 中文版的在这里：[Jekyll中文](http://jekyllcn.com/).\n\n#### write-posts\n\n要发表的文章一般以markdown的格式放在这里`_posts/`，你只要看看这篇模板里的文章你就立刻明白该如何设置。\n\nyaml 头文件长这样:\n\n```\n---\nlayout: post\ntitle: \"Hello 2015\"\nsubtitle: \"Hello World, Hello Blog\"\ndate: 2015-01-29 12:00:00\nauthor: \"Hux\"\nheader-img: \"img/post-bg-2015.jpg\"\ntags:\n - Life\n---\n\n```\n\n#### SideBar\n\n看右边:\n\n\n设置是在 `_config.yml`文件里面的`Sidebar settings`那块。\n```\n# Sidebar settings\nsidebar: true #添加侧边栏\nsidebar-about-description: \"简单的描述一下你自己\"\nsidebar-avatar: /img/avatar-hux.jpg #你的大头贴，请使用绝对地址.\n```\n\n侧边栏是响应式布局的，当屏幕尺寸小于992px的时候，侧边栏就会移动到底部。具体请见bootstrap栅格系统 \n\n\n#### Mini About Me\n\nMini-About-Me 这个模块将在你的头像下面，展示你所有的社交账号。这个也是响应式布局，当屏幕变小时候，会将其移动到页面底部，只不过会稍微有点小变化，具体请看代码。\n\n#### Featured Tags\n\n看到这个网站 [Medium](http://medium.com) 的推荐标签非常的炫酷，所以我将他加了进来。\n这个模块现在是独立的，可以呈现在所有页面，包括主页和发表的每一篇文章标题的头上。\n\n```\n# Featured Tags\nfeatured-tags: true \nfeatured-condition-size: 1 # A tag will be featured if the size of it is more than this condition value\n```\n\n唯一需要注意的是`featured-condition-size`: 如果一个标签的 SIZE，也就是使用该标签的文章数大于上面设定的条件值，这个标签就会在首页上被推荐。\n \n内部有一个条件模板 `{% if tag[1].size > {{site.featured-condition-size}} %}` 是用来做筛选过滤的.\n\n\n#### Friends\n\n好友链接部分。这会在全部页面显示。\n\n设置是在 `_config.yml`文件里面的`Friends`那块，自己加吧。\n\n```\n# Friends\nfriends: [\n {\n title: \"Foo Blog\",\n href: \"http://foo.github.io/\"\n },\n {\n title: \"Bar Blog\",\n href: \"http://bar.github.io\"\n }\n]\n```\n\n\n#### Keynote Layout\n\nHTML5幻灯片的排版：\n\n\n\n这部分是用于占用html格式的幻灯片的，一般用到的是 Reveal.js, Impress.js, Slides, Prezi 等等.我认为一个现代化的博客怎么能少了放html幻灯的功能呢~\n\n其主要原理是添加一个 `iframe`，在里面加入外部链接。你可以直接写到头文件里面去，详情请见下面的yaml头文件的写法。\n\n```\n---\nlayout: keynote\niframe: \"http://huangxuan.me/js-module-7day/\"\n---\n```\n\niframe在不同的设备中，将会自动的调整大小。保留内边距是为了让手机用户可以向下滑动，以及添加更多的内容。\n\n\n#### Comment\n\n博客不仅支持多说[Duoshuo](http://duoshuo.com)评论系统，也支持[Disqus](http://disqus.com)评论系统。\n\n`Disqus`优点是：国际比较流行，界面也很大气、简介，如果有人评论，还能实时通知，直接回复通知的邮件就行了；缺点是：评论必须要去注册一个disqus账号，分享一般只有Facebook和Twitter，另外在墙内加载速度略慢了一点。想要知道长啥样，可以看以前的版本点[这里](http://brucezhaor.github.io/about.html) 最下面就可以看到。\n\n`多说` 优点是：支持国内各主流社交软件(微博，微信，豆瓣，QQ空间 ...)一键分享按钮功能，另外登陆比较方便，管理界面也是纯中文的，相对于disqus全英文的要容易操作一些；缺点是：就是界面丑了一点。\n当然你是可以自定义界面的css的，详情请看多说开发者文档 http://dev.duoshuo.com/docs/5003ecd94cab3e7250000008 。\n\n**首先**，你需要去注册一个账号，不管是disqus还是多说的。**不要直接使用我的啊！**\n\n**其次**，你只需要在下面的yaml头文件中设置一下就可以了。\n\n```\nduoshuo_username: _你的用户名_\n# 或者\ndisqus_username: _你的用户名_\n```\n\n**最后**多说是支持分享的，如果你不想分享，请这样设置：`duoshuo_share: false`。你可以同时使用两个评论系统，不过个人感觉怪怪的。\n\n#### Analytics\n\n网站分析，现在支持百度统计和Google Analytics。需要去官方网站注册一下，然后将返回的code贴在下面：\n\n```\n# Baidu Analytics\nba_track_id: 4cc1f2d8f3067386cc5cdb626a202900\n\n# Google Analytics\nga_track_id: 'UA-49627206-1' # 你用Google账号去注册一个就会给你一个这样的id\nga_domain: huangxuan.me\t\t\t# 默认的是 auto, 这里我是自定义了的域名，你如果没有自己的域名，需要改成auto。\n```\n\n#### Customization\n\n如果你喜欢折腾，你可以去自定义我的这个模板的 code，[Grunt](gruntjs.com)已经为你准备好了。（感谢 Clean Blog）\n\nJavaScript 的压缩混淆、Less 的编译、Apache 2.0 许可通告的添加与 watch 代码改动，这些任务都揽括其中。简单的在命令行中输入 `grunt` 就可以执行默认任务来帮你构建文件了。如果你想搞一搞 JavaScript 或 Less 的话，`grunt watch` 会帮助到你的。\n\n**如果你可以理解 `_include/` 和 `_layouts/`文件夹下的代码（这里是整个界面布局的地方），你就可以使用 Jekyll 使用的模版引擎 [Liquid](https://github.com/Shopify/liquid/wiki)的语法直接修改/添加代码，来进行更有创意的自定义界面啦！**\n\n#### Header Image\n\n标题底图是可以自己选的，看看几篇示例post你就知道如何设置了。在\n [issue #6 ](https://github.com/Huxpro/huxpro.github.io/issues/6) 中我被问到：怎么样才能让标题底图好看呢？\n \n标题底图的选取完全是看个人的审美了，我也帮不了你。每一篇文章可以有不同的底图，你想放什么就放什么，最后宽度要够，大小不要太大，否则加载慢啊。\n\n但是需要注意的是本模板的标题是**白色**的，所以背景色要设置为**灰色**或者**黑色**，总之深色系就对了。当然你还可以自定义修改字体颜色，总之，用github pages就是可以完全的个性定制自己的博客。\n\n#### SEO Title\n\n我的博客标题是 **“Hux Blog”** 但是我想要在搜索的时候显示 **“黄玄的博客 | Hux Blog”** ，这个就需要SEO Title来定义了。\n\n其实这个SEO Title就是定义了标题这个里面的东西和多说分享的标题，你可以自行修改的。\n\n## 致谢\n\n1. 这个模板是从这里[IronSummitMedia/startbootstrap-clean-blog-jekyll](https://github.com/IronSummitMedia/startbootstrap-clean-blog-jekyll) fork 的。 感谢这个作者\n2. 感谢[@BrucZhaoR](https://github.com/BruceZhaoR)的中文翻译 \n\n3. 感谢 Jekyll、Github Pages 和 Bootstrap!\n\n\n\n"
},
{
"path": "_config.yml",
"content": "# Site settings\ntitle: Mercy Ma\nSEOTitle: 小马哥的技术博客\nheader-img: img/home-bg.jpg\nemail: mercyblitz@gmail.com\ndescription: \"关于程序、设计以及架构 | 小马哥，Javaer ，Software Engineer\"\nkeyword: \"小马哥, mercyblitz, Mercy Ma, 小马哥的技术博客\"\nurl: \"https://weibo.com/mercyblitz\" # your host, for absolute URL\nbaseurl: \"\" # for example, '/blog' if your blog hosted on 'host/blog'\n\npost:\n author: mercyblitz\n\n# Publish posts or collection documents with a future date.\nfuture: true\n\n# SNS settings\nRSS: true\nweibo_username: mercyblitz\ngithub_username: mercyblitz\ntwitter_username: mercyblitz\n#facebook_username: mercyblitz\n#linkedin_username: firstname-lastname-idxxxx\n\n\n\n# Build settings\n# from 2016, 'pygments' is unsupported on GitHub Pages. Use 'rouge' for highlighting instead.\nhighlighter: rouge\npermalink: pretty\npaginate: 10\nexclude: [\"less\",\"node_modules\",\"Gruntfile.js\",\"package.json\",\"README.md\",\"README.zh.md\"]\nanchorjs: true # if you want to customize anchor. check out line:181 of `post.html`\n# If you have timezone issue (e.g. #68) in China, uncomment to use this:\n#timezone: CN \n\n\n\n# Gems\n# from PR#40, to support local preview for Jekyll 3.0\n# make sure you have this gem installed\n# `$ gem install jekyll-paginate`\nplugins: [jekyll-paginate]\n\n\n\n# Markdown settings\n# replace redcarpet to kramdown,\n# although redcarpet can auto highlight code, the lack of header-id make the catalog impossible, so I switch to kramdown\n# document: http://jekyllrb.com/docs/configuration/#kramdown\nmarkdown: kramdown\nkramdown:\n input: GFM # use Github Flavored Markdown !important\n syntax_highlighter_opts:\n span:\n line_numbers: false\n block:\n line_numbers: true\n start_line: 1\n\n\n\n# Disqus settings\ndisqus_username: mercyblitz\n\n# Netease settings\nnetease_comment: false\n\n\n\n# Analytics settings\n# Baidu Analytics \n# ba_track_id: [your track id]\n\n# Google Analytics\n# ga_track_id: TODO # Format: UA-xxxxxx-xx\n# ga_domain: TODO\n\n\n\n# Sidebar settings\nsidebar: true # whether or not using Sidebar.\nsidebar-about-description: \"大家好，我是小马哥\"\nsidebar-avatar: /img/avatar-mecyblitz.jpg # use absolute URL, seeing it's used in both `/` and `/about/`\n\n\n\n# Featured Tags\nfeatured-tags: true # whether or not using Feature-Tags\nfeatured-condition-size: 1 # A tag will be featured if the size of it is more than this condition value\n\n\n\n# Progressive Web Apps\nchrome-tab-theme-color: \"#000000\"\nservice-worker: true\n\n\n\n# MathJax rendering for layout:page (e.g. post preview)\npage-mathjax: false\n\n\n\n# Friends\nfriends: [\n {}\n]\n"
},
{
"path": "_includes/about/en.md",
"content": "\n> Hard Code in Internet，Think Big Data too much\n\nHi, I'm Mercy Ma, as a member in [Apache Dubbo](https://dubbo.apache.org/) PPMC, an achitecture of [Spring Cloud Alibaba](https://github.com/spring-cloud-incubator/spring-cloud-alibaba), and working on Open Source projects and Micro Services infrastructure, certificated SUN Java（SCJP、SCWCD、SCBCD）, Oracle OCA and so on.\n\n\n## Books\n\n- 《Thinking in Spring Boot》（Chinese）\n\n\n## Online Courses\n\n- imooc\n - [\bSpring Boot 2.0深度实践之核心技术篇](https://coding.imooc.com/class/252.html)\n - Spring Boot 2.0深度实践之\b生态整合篇（即将上线...）\n- SegmentFault\n - [Java 微服务实践 - Spring Boot / Spring Cloud](https://segmentfault.com/ls/1650000011387052)\n\n\n## Open Source Projects\n\n- Spring Cloud\n - [Spring Cloud Alibaba](https://github.com/spring-cloud-incubator/spring-cloud-alibaba)\n- Apache\n - [Apache Dubbo](https://github.com/apache/incubator-dubbo)\n - [Apache Dubbo Spring Boot](https://github.com/apache/incubator-dubbo-spring-boot-project) \n- Alibaba\n - [Alibaba Nacos](https://github.com/alibaba/nacos)\n - [Nacos Spring](https://github.com/nacos-group/nacos-spring-project)\n - [Nacos Spring Boot](https://github.com/nacos-group/nacos-spring-boot-project)\n - [Alibaba Sentinel](https://github.com/alibaba/Sentinel)\n - [Velocity Spring Boot Starter](https://github.com/alibaba/velocity-spring-boot-project)\n\n\n## Talks\n\n- Spring Cloud Alibaba 致力于提供分布式应用开发的一站式解决方法 · [CNCC 2018](http://cncc2018.ccf.org.cn/cms/show.action?code=publish_ff80808162f165f90163070bf87105de&siteid=100000&channelid=0000000002)\n- Dubbo Cloud Native 之路的实践与思考 · [Dubbo开发者沙龙（上海站）- 2018 Aliware技术行](https://www.itdks.com/eventlist/detail/2307)\n- Dubbo 的过去、现在以及未来 · [2017 国际互联网大会（上海）](http://2017.thegiac.com/)\n- 微服务实践之路（二） · [2016 SegmentFault 开发者大（杭州站）](https://segmentfault.com/sfdc-2016/hz)\n- 微服务实践之路（一） · [2016 厦门互联网技术峰会](https://www.bagevent.com/event/227489)"
},
{
"path": "_includes/about/zh.md",
"content": "> 手淫互联网，意淫大数据\n\n大家好，我是小马哥（mercyblitz），[Java 劝退师](https://www.douyu.com/mercyblitz)，[Apache Dubbo](https://dubbo.apache.org/) PMC、[Spring Cloud Alibaba](https://github.com/spring-cloud-incubator/spring-cloud-alibaba) 项目架构师，通过 SUN Java（SCJP、SCWCD、SCBCD）以及 Oracle OCA 等的认证。目前为自由职业者，承接企业培训、架构设计和咨询等业务。\n\n### [书籍出版](/my/books)\n\n### [线上课程](/my/lessons/)\n\n### [开源项目](/my/open-sources/)\n\n### [报告分享](/my/presentations/)\n\n### [企业培训](/my/training/)\n\n- 电子邮箱：mercyblitz@gmail.com\n- 微信：mercyblitz-1985\n- [微博](https://weibo.com/mercyblitz)：[@mercyblitz](https://weibo.com/mercyblitz)\n- [Github](http://github.com/mercyblitz)：[http://github.com/mercyblitz](http://github.com/mercyblitz)\n- [Twitter](https://twitter.com/mercyblitz)：[@mercyblitz](https://twitter.com/mercyblitz)\n- 微信公众号：**次灵均阁**\n\n\n\n\n## 社区交流\n\n- 小马哥和小伙伴1号群（已满）\n- 小马哥和小伙伴2号群（已满）\n- 小马哥和小伙伴3号群\n\n\n"
},
{
"path": "_includes/featured-tags.html",
"content": "{% comment %}\n @param {boolean} bottom - bottom will render \n{% endcomment %}\n\n{% if site.featured-tags %}\n\n {% if include.bottom %}\n \n {% endif %}\n