[
{
"path": ".gitignore",
"content": "_site\n_posts/_draft\n_posts/_archive\n_archive\nnode_modules\n.vscode\n*.log\n*.lock\n*.sh\n.DS_Store\n.jekyll-cache\n*/.DS_Store\n*/*/.DS_Store\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": "CNAME",
"content": "huangxuan.me\n"
},
{
"path": "Gemfile",
"content": "source 'https://rubygems.org'\ngem 'jekyll-paginate'\n\ngem \"jekyll\", \"~> 4.0\"\ngem \"rake\"\n\ngem \"webrick\", \"~> 1.7\"\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": "[Hux Blog](https://huangxuan.me)\n================================\n\n> I never expected this to become popular.\n\n\n\n\n[User Manual 👉](_doc/Manual.md)\n--------------------------------------------------\n\n### Getting Started\n\n1. You will need [Ruby](https://www.ruby-lang.org/en/) and [Bundler](https://bundler.io/) to use [Jekyll](https://jekyllrb.com/). Following [Using Jekyll with Bundler](https://jekyllrb.com/tutorials/using-jekyll-with-bundler/) to fullfill the enviromental requirement.\n\n2. Installed dependencies in the `Gemfile`:\n\n```sh\n$ bundle install \n```\n\n3. Serve the website (`localhost:4000` by default):\n\n```sh\n$ bundle exec jekyll serve # alternatively, npm start\n```\n\n### Development (Build From Source)\n\nTo modify the theme, you will need [Grunt](https://gruntjs.com/). There are numbers of tasks you can find in the `Gruntfile.js`, includes minifing JavaScript, compiling `.less` to `.css`, adding banners to keep the Apache 2.0 license intact, watching for changes, etc. \n\nYes, they were inherited and are extremely old-fashioned. There is no modularization and transpilation, etc.\n\nCritical Jekyll-related code are located in `_include/` and `_layouts/`. Most of them are [Liquid](https://github.com/Shopify/liquid/wiki) templates.\n\nThis theme uses the default code syntax highlighter of jekyll, [Rouge](http://rouge.jneen.net/), which is compatible with Pygments theme so just pick any pygments theme css (e.g. from [here](http://jwarby.github.io/jekyll-pygments-themes/languages/javascript.html) and replace the content of `highlight.less`.\n\n\n### Interesting to know more? Checkout the [full user manual](_doc/Manual.md)!\n\n\nOther Resources\n---------------\n\nPorts\n- [**Hexo**](https://github.com/Kaijun/hexo-theme-huxblog) by @kaijun\n- [**React-SSR**](https://github.com/LucasIcarus/huxpro.github.io/tree/ssr) by @LucasIcarus\n\n[Starter/Boilerplate](https://github.com/huxpro/huxblog-boilerplate)\n- Out of date. Helps wanted for updating it on par with the main repo\n\nTranslation\n- [🇨🇳 中文文档（有点过时）](https://github.com/Huxpro/huxpro.github.io/blob/master/_doc/README.zh.md)\n\n\nLicense\n-------\n\nApache License 2.0.\nCopyright (c) 2015-present Huxpro\n\nHux Blog is derived from [Clean Blog Jekyll Theme (MIT License)](https://github.com/BlackrockDigital/startbootstrap-clean-blog-jekyll/)\nCopyright (c) 2013-2016 Blackrock Digital LLC.\n"
},
{
"path": "Rakefile",
"content": "require \"rubygems\"\nrequire 'rake'\nrequire 'yaml'\nrequire 'time'\n\nSOURCE = \".\"\nCONFIG = {\n 'version' => \"12.3.2\",\n 'themes' => File.join(SOURCE, \"_includes\", \"themes\"),\n 'layouts' => File.join(SOURCE, \"_layouts\"),\n 'posts' => File.join(SOURCE, \"_posts\"),\n 'post_ext' => \"md\",\n 'theme_package_version' => \"0.1.0\"\n}\n\n# Usage: rake post title=\"A Title\" subtitle=\"A sub title\"\ndesc \"Begin a new post in #{CONFIG['posts']}\"\ntask :post do\n abort(\"rake aborted: '#{CONFIG['posts']}' directory not found.\") unless FileTest.directory?(CONFIG['posts'])\n title = ENV[\"title\"] || \"new-post\"\n subtitle = ENV[\"subtitle\"] || \"This is a subtitle\"\n slug = title.downcase.strip.gsub(' ', '-').gsub(/[^\\w-]/, '')\n begin\n date = (ENV['date'] ? Time.parse(ENV['date']) : Time.now).strftime('%Y-%m-%d')\n rescue Exception => e\n puts \"Error - date format must be YYYY-MM-DD, please check you typed it correctly!\"\n exit -1\n end\n filename = File.join(CONFIG['posts'], \"#{date}-#{slug}.#{CONFIG['post_ext']}\")\n if File.exist?(filename)\n abort(\"rake aborted!\") if ask(\"#{filename} already exists. Do you want to overwrite?\", ['y', 'n']) == 'n'\n end\n\n puts \"Creating new post: #{filename}\"\n open(filename, 'w') do |post|\n post.puts \"---\"\n post.puts \"layout: post\"\n post.puts \"title: \\\"#{title.gsub(/-/,' ')}\\\"\"\n post.puts \"subtitle: \\\"#{subtitle.gsub(/-/,' ')}\\\"\"\n post.puts \"date: #{date}\"\n post.puts \"author: \\\"Hux\\\"\"\n post.puts \"header-img: \\\"img/post-bg-2015.jpg\\\"\"\n post.puts \"tags: []\"\n post.puts \"---\"\n end\nend # task :post\n\ndesc \"Launch preview environment\"\ntask :preview do\n system \"jekyll --auto --server\"\nend # task :preview\n\n#Load custom rake scripts\nDir['_rake/*.rake'].each { |r| load r }\n"
},
{
"path": "_config.yml",
"content": "# Site settings\ntitle: Hux Blog\nSEOTitle: 黄玄的博客 | Hux Blog\nheader-img: img/home-bg.jpg\nemail: huxpro@gmail.com\ndescription: \"这里是 @Hux黄玄 的个人博客，与你一起发现更大的世界 | 要做一个有 swag 的程序员\"\nkeyword: \"黄玄, Hux黄玄, Hux, 鬼栈, huxpro, @huxpro, 黄玄的博客, Hux Blog, 博客, 个人网站, 互联网, Web, JavaScript, React, React Native, 前端, 设计\"\nurl: \"https://huangxuan.me\" # your host, for absolute URL\nbaseurl: \"\" # for example, '/blog' if your blog hosted on 'host/blog'\n\n# Publish posts or collection documents with a future date.\nfuture: true\n\n# SNS settings\nRSS: false\nweibo_username: huxpro\nzhihu_username: huxpro\ngithub_username: huxpro\ntwitter_username: huxpro\n#facebook_username: huxpro\n#linkedin_username: firstname-lastname-idxxxx\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:\n [\n \"less\",\n \"node_modules\",\n \"Gruntfile.js\",\n \"package.json\",\n \"README.md\",\n \"README.zh.md\",\n ]\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# 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# 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# Disqus settings\ndisqus_username: hux\n\n# Netease settings\nnetease_comment: false\n\n# Analytics settings\n# Baidu Analytics\n# ba_track_id: [your track id]\n\n# Google Analytics\nga_track_id: \"UA-49627206-1\" # Format: UA-xxxxxx-xx\nga_domain: huangxuan.me\n\n# Sidebar settings\nsidebar: true # whether or not using Sidebar.\nsidebar-about-description: \"要做一个有 swag 的程序员 React Team @ Meta\"\nsidebar-avatar: https://github.com/Huxpro.png # use absolute URL, seeing it's used in both `/` and `/about/`\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# Progressive Web Apps\nchrome-tab-theme-color: \"#000000\"\nservice-worker: true\n\n# MathJax rendering for layout:page (e.g. post preview)\npage-mathjax: false\n\n# Friends\nfriends:\n [\n { title: \"乱序（Midare）\", href: \"http://mida.re/\" },\n { title: \"Ebn Zhang\", href: \"https://ebnbin.dev/\" },\n { title: \"Kun Qian\", href: \"http://kunq.me\" },\n { title: \"Sherry Woo\", href: \"https://sherrywoo.me/\" },\n { title: \"SmdCn\", href: \"http://blog.smdcn.net\" },\n { title: \"JiyinYiyong\", href: \"http://tiye.me/\" },\n { title: \"DHong Say\", href: \"http://dhong.co\" },\n { title: \"尹峰以为\", href: \"http://ingf.github.io/\" },\n ]\n"
},
{
"path": "_doc/Manual.md",
"content": "Hux Blog User Manual\n====================\n\n* Basics\n\t* [Getting Started](#getting-started)\n\t* [Development](#development)\n\t* [Config](#configs)\n\t* [Posts](#posts)\n* Components\n\t* [SideBar](#sidebar)\n\t* [Mini About Me](#mini-about-me)\n\t* [Featured Tags](#featured-tags)\n\t* [Friends](#friends)\n\t* [Keynote Layout](#keynote-layout)\n* Misc\n\t* [Comment](#comment)\n\t* [Analytics](#analytics)\n\t* [SEO Title](#seo-title)\n* [FAQ](#faq)\n* [Releases](#releases) \n\n\n### Getting Started\n\n1. You will need [Ruby](https://www.ruby-lang.org/en/) and [Bundler](https://bundler.io/) to use [Jekyll](https://jekyllrb.com/). Following [Using Jekyll with Bundler](https://jekyllrb.com/tutorials/using-jekyll-with-bundler/) to fullfill the enviromental requirement.\n\n2. Installed dependencies in the `Gemfile`:\n\n```sh\n$ bundle install \n```\n\n3. Serve the website (`localhost:4000` by default):\n\n```sh\n$ bundle exec jekyll serve # alternatively, npm start\n```\n\n### Development\n\nTo modify the theme, you will need [Grunt](https://gruntjs.com/). There are numbers of tasks you can find in the `Gruntfile.js`, includes minifing JavaScript, compiling `.less` to `.css`, adding banners to keep the Apache 2.0 license intact, watching for changes, etc. \n\nYes, they were inherited and are extremely old-fashioned. There is no modularization and transpilation, etc.\n\nCritical Jekyll-related code are located in `_include/` and `_layouts/`. Most of them are [Liquid](https://github.com/Shopify/liquid/wiki) templates.\n\nThis theme uses the default code syntax highlighter of jekyll, [Rouge](http://rouge.jneen.net/), which is compatible with Pygments theme so just pick any pygments theme css (e.g. from [here](http://jwarby.github.io/jekyll-pygments-themes/languages/javascript.html) and replace the content of `highlight.less`.\n\n\n### Configs\n\nYou can easily customize the blog by modifying `_config.yml`:\n\n```yml\n# Site settings\ntitle: Hux Blog # title of your website\nSEOTitle: Hux Blog # check out docs for more detail\ndescription: \"Cool Blog\" # ...\n\n# SNS settings \ngithub_username: huxpro # modify this account to yours\nweibo_username: huxpro # the footer woule be auto-updated.\n\n# Build settings\npaginate: 10 # nums of posts in one page\n```\n\nFor more options, please check out [Jekyll - Official Site](http://jekyllrb.com/). \nMost of them are very descriptive so feel brave to dive into code directly as well. \n\n\n### Posts\n\nPosts are simply just Markdown files in the `_posts/`. \nMetadata of posts are listed in a YAML style _front-matter_.\n\nFor instance, [Hello 2015])(https://huangxuan.me/2015/01/29/hello-2015/) has the front-matter of this:\n\n```yml\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\"\ncatalog: true\ntags:\n - Life\n - Meta\n---\n```\n\n> Note: `tags` section can also be written as `tags: [Life, Meta]`.\n\nAfter [Rake](https://github.com/ruby/rake) is introduced, we can use the command below to simplify the post creation:\n\n```\nrake post title=\"Hello 2015\" subtitle=\"Hello World, Hello Blog\"\n```\n\nThis command will automatially generate a sample post similar as above under the `_posts/` folder.\n\nThere are a bunch of _advanced_ configs:\n\n1. a _text style_ header like [this](https://huangxuan.me/2019/09/08/spacemacs-workflow/) with\n\n```yml\nheader-style: text \n```\n\n2. Turning on Latex support:\n\n```yml\nmathjax: true\n```\n\n3. Adding a mask to the header picture:\n\n```yml\nheader-mask: 0.3\n```\n\nEtc.\n\n\n### SideBar\n\n\n\n**SideBar** provides possible modules to show off more personal information.\n\n```yml\n# Sidebar settings\nsidebar: true # default true\nsidebar-about-description: \"your description here\"\nsidebar-avatar: /img/avatar-hux.jpg # use absolute URL.\n```\n\nModules *[Featured Tags](#featured-tags)*, *[Mini About Me](#mini-about-me)* and *[Friends](#friends)* are turned on by default and you can add your own. The sidebar is naturally responsive, i.e. be pushed to bottom in a smaller screen (`<= 992px`, according to [Bootstarp Grid System](http://getbootstrap.com/css/#grid)) \n\n\n### Mini About Me\n\n**Mini-About-Me** displays your avatar, description and all SNS buttons if `sidebar-avatar` and `sidebar-about-description` variables are set. \n\nIt would be hidden in a smaller screen when the entire sidebar are pushed to bottom. Since there is already SNS portion there in the footer.\n\n### Featured Tags\n\n**Featured-Tags** is similar to any cool tag features in website like [Medium](http://medium.com).\nStarted from V1.4, this module can be used even when sidebar is off and displayed always in the bottom. \n\n```yml\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\nThe only thing need to be paid attention to is `featured-condition-size`, which indicate a criteria that tags need to have to be able to \"featured\". Internally, a condition `{% if tag[1].size > {{site.featured-condition-size}} %}` are made.\n\n### Friends\n\nFriends is a common feature of any blog. It helps with SEO if you have a bi-directional hyperlinks with your friends sites.\nThis module can live when sidebar is off as well.\n\nFriends information is configured as a JSON string in `_config.yml`\n\n```yml\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\n\n\nThere is a increased trend to use Open Web technology for keynotes and presentations via Reveal.js, Impress.js, Slides, Prezi etc. I consider a modern blog should have first-class support to embed these HTML based presentation so **Keynote layout** are made.\n\nTo use, in the **front-matter**:\n\n```yml\n---\nlayout: keynote\niframe: \"http://huangxuan.me/js-module-7day/\"\n---\n```\n\nThe `iframe` element will be automatically resized to adapt different form factors and device orientation. \nBecause most of the keynote framework prevent the browser default scroll behavior. A bottom-padding is set to help user and imply user that more content could be presented below.\n\n\n### Comment\n\n> Help Wanted: Moving to a Github-based solution.\n\nCurrently, [Disqus](http://disqus.com) and [Duoshuo](http://duoshuo.com) are supported as third party discussion system.\n\nFirst of all, you need to sign up and get your own account. **Repeat, DO NOT use mine!** (I have set Trusted Domains) It is deathly simple to sign up and you will get the full power of management system. Please give it a try!\n\nSecond, from V1.5, you can easily complete your comment configuration by just adding your **short name** into `_config.yml`:\n\n```yml\nduoshuo_username: _your_duoshuo_short_name_\n# OR\ndisqus_username: _your_disqus_short_name_\n```\n\n**To the old version user**, it's better that you pull the new version, otherwise you have to replace code in `post.html`, `keynote.html` and `about.html` on your own.\n\nFurthermore, Duoshuo support Sharing. if you only wanna use Duoshuo comment without sharing, you can set `duoshuo_share: false`. \n\n\n### Analytics\n\nFrom V1.5, Google Analytics and Baidu Tongji are supported with a simple config away:\n\n```yml\n# Baidu Analytics\nba_track_id: 4cc1f2d8f3067386cc5cdb626a202900\n\n# Google Analytics\nga_track_id: 'UA-49627206-1' # Format: UA-xxxxxx-xx\nga_domain: huangxuan.me\n```\n\nJust checkout the code offered by Google/Baidu, and copy paste here, all the rest is already done for you.\n\n(Google might ask for meta tag `google-site-verification`)\n\n\n### SEO Title\n\nBefore V1.4, site setting `title` is not only used for displayed in Home Page and Navbar, but also used to generate the `` in HTML.\nIt's possible that you want the two things different. For me, my site-title is **“Hux Blog”** but I want the title shows in search engine is **“黄玄的博客 | Hux Blog”** which is multi-language.\n\nSo, the SEO Title is introduced to solve this problem, you can set `SEOTitle` different from `title`, and it would be only used to generate HTML `<title>` and setting DuoShuo Sharing.\n\n\nFAQ\n---\n\n#### cannot load such file -- jekyll-paginate\n\nThis blog started in Jekyll 2 time when `jekyll-paginate` is standard. With Jekyll 3, it's a plugin we included in `_config.yml`.\n\nMake sure you installed it via plain `gem` CLI or Bundler.\n\n\nReleases\n--------\n\n#### V1.8.2\n\n- Merged #333, #336 from @JinsYin.\n- Add `Gemfile` due to increasing Bundler using.\n- TODO: `multilingual` could be more automative via configurations and convention.\n- Drop the entire `portfolio` page until a big rewrite of a better `project` page.\n\n#### V1.8.1\n\n- Improve multi-lingual implementation, see `about.html` or `_posts/2017-07-12-upgrading-eleme-to-pwa.markdown` for a example of uses.\n\n#### V1.8\n\n- Brand new [Archive](https://huangxuan.me/archive/) page! It combines previous Archive and Tag page and it's backward-cmpatible.\nShout out to [@kitian616/jekyll-TeXt-theme](https://github.com/kitian616/jekyll-TeXt-theme) of bringing this idea. \n- Improve engineering by extracting duplicated liquid templates into reuseable includes. This was proposed in #74 by @Kaijun but postponed for entirely 2.5 years! I wasn't able to merge his PR directly because of long-time divegence but the credit is belonging to @Kaijun.\n- Improved code block. Long-wanted line number are supported out of the box (thanks for @SmilingParadise's help from Sina Weibo), the default theme is updated to Atom One Dark as well (checkout FQA for how to change to your farovite theme)\n- MathJax support by @Voleking in #80. I choose to use the SVG renderer though. See [Mathjax, kramdown and Octopress](https://www.lucypark.kr/blog/2013/02/25/mathjax-kramdown-and-octopress/) for writing and escaping details.\n- Open Graph Protocol support by @Android-KitKat in #253\n- `header-img-credit` and `header-img-credit-href`\n- `nav-style: invert` and `header-style: text`\n\n#### V1.7\n\n- PWA / Service Worker support.\n\n#### v1.6\n\n- Change cdn to cdnjs for better HTTPS support\n\n#### V1.5.2\n\n- Feeling annoyed to delete my blog post after clone or pull? Try **Boilerplate (Beta)** to help you get started quickly and easily merge update.\n- `-apple-system` is added in font rule, which display beautiful new font **San Francisco** in iOS 9 by default.\n- Fixed [issue#15](https://github.com/Huxpro/huxpro.github.io/issues/15) about code wrap.\n\n#### V1.5.1\n\n- **[Comment](#comment)** support [**Disqus**](http://disqus.com) officially, thanks to @rpsh.\n\n#### V1.5\n\n- **[Comment](#comment)** and **[Analytics](#analytics)** is configurable now! We also add **Google Analytics support** and drop tencents. Both documents is updated.\n\n#### V1.4\n\n- **[Featured Tags](#featured-tags)** is now independent of [SideBar](#sidebar). Both documents is updated.\n- New **[SEO Title](#seo-title)** for SEO usage which is differ from the site title\n\n#### V1.3.1\n\n- Support **PingFang (苹方)**, the new Chinese font presented by [OS X El Capitan](http://www.apple.com/cn/osx/whats-new/)\n\n\n#### V1.3\n\n- Big Improvement to the **Navigation Menu** *(especially in Android)*: Dropping the old, stuttering, low-performance [Bootstrap collapse.js](http://getbootstrap.com/javascript/#collapse), replaced with an own wrote, [jank free](http://jankfree.org/) navbar menu in a pretty high-performance implementation of [Google Material Design](https://www.google.com/design/spec/material-design/introduction.html).\n\n<img src=\"http://huangxuan.me/img/blog-md-navbar.gif\" width=\"320\" />\n\n\n#### V1.2\n\n- Brand new **[Keynote Layout](#keynote-layout)** is provided for easily posting beautiful HTML presentations you have created with this blog\n\n\n#### V1.1\n\n- We now support a clean and gorgeous **[SideBar](#sidebar)** for displaying more info\n- **[Friends](#friends)** is also added as a common feature of blog help you do SEO\n\n#### V1.0\n\n- Full-feature **Tag** support\n- **Mobile first** user experience optimization\n- **Typographic optimization** for Chinese Fonts\n- **Network optimizaition** for China, dropping Google webfont, using local CDN\n- Using [Github Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/)\n- Using Baidu, Tencent/QQ analytics\n- Using [DuoShuo](http://duoshuo.com/) as the Disqus-like third party discussion system"
},
{
"path": "_doc/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在引入[Rake](https://github.com/ruby/rake)工具之后，我们可以使用命令：\n\n```\nrake post title=\"Hello 2015\" subtitle=\"Hello World, Hello Blog\"\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栅格系统 <http://v3.bootcss.com/css/>\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就是定义了<head><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": "_includes/about/en.md",
"content": "Hey, I am Huang, Xuan (a.k.a. _@huxpro_). I worked on the [React Team](https://beta.reactjs.org/community/meet-the-team#react-core) at FacebookMeta.\n\nI considered myself as a hybrid between a software engineer specifically into the programming languages theories and implementations domain (i.e. compiler, type system, type-based formal verification, virtual machine, runtime systems, garbage collection), and a creative technologiest deeply caring about many humanistic aspects (e.g. visual, sound, interaction) in UI and HCI in general.\n\nI also worked on the [Hermes JavaScript Engine](https://hermesengine.dev/), some other projects under the [Reality Labs (Research)](https://tech.fb.com/ar-vr/), and [ReasonML](https://reasonml.github.io/) (now [ReScript](https://rescript-lang.org/)) efforts at Meta (Facebook).\n\nIn the past, I worked on [Alitrip (Fliggy)](https://www.alitrip.com/) mobile and web apps under the [Alibaba Group](https://en.wikipedia.org/wiki/Alibaba_Group), found and lead front-end infrastructure team at an unicorn startup company [Beijing Weiying (a.k.a. WePiao, now acquired by Maoyan)](https://www.crunchbase.com/organization/beijing-weiying-technology), and helped [Ele.me (now acquired by Alibaba)](https://en.wikipedia.org/wiki/Ele.me) to upgrade their mobile web site into [the first influential PWA (progressive web app) in China](https://medium.com/elemefe/upgrading-ele-me-to-progressive-web-app-2a446832e509).\n\nI studied BA, Digital Media Art at [Communication University of China](https://en.wikipedia.org/wiki/Communication_University_of_China) and MS, Computer Science (with a focus on programming languages, mainly supervised by [Prof. Matthew Fluet](https://www.cs.rit.edu/~mtf/)) at [Rochester Institute of Technology](https://en.wikipedia.org/wiki/Rochester_Institute_of_Technology).\n\n##### Appearence\n\n- [React Labs: What We've Been Working On – June 2022][12] · React Blog · 2022\n- [React Without Memo][11] · [React Conf 2021](https://conf.reactjs.org/)\n- [Toward Hermes being the Default][11] · React Native Blog · 2021\n- React Native 0.64 with Hermes for iOS · [The RN Show Podcast Ep #5](https://www.callstack.com/podcast-react-native-show) · 2021\n- [Upgrading to Progressive Web Apps][9] · [JSConf China Shanghai 2017](http://2017.jsconf.cn/)\n- Building Progressive Web Apps · [CSDI Guangzhou 2017](http://www.csdisummit.com/)\n- The State of Progressive Web App · GDG IO Redux Beijing 2017\n- PWA Rehashing · Baidu HQ Beijing 2017\n- [Service Worker 101][5] · GDG DevFest Beijing 2016\n- [Progressive Web Apps][4] · QCon Shanghai 2016\n- Progressive Web App in my POV · GDG IO Redux Beijing 2016\n- [CSS Still Sucks 2015][2] · 2015\n- [JavaScript Modularization Journey][1] · 2015\n\n[1]: //huangxuan.me/2015/07/09/js-module-7day/\n[2]: //huangxuan.me/2015/12/28/css-sucks-2015/\n[3]: //huangxuan.me/2016/06/05/pwa-in-my-pov/\n[4]: //huangxuan.me/2016/10/20/pwa-qcon2016/\n[5]: //huangxuan.me/2016/11/20/sw-101-gdgdf/\n[6]: https://yanshuo.io/assets/player/?deck=58ac8598b123db0067292f92 \"PWA Rehashing\"\n[7]: https://yanshuo.io/assets/player/?deck=593ad6fbfe88c2006a0a0d6d \"The State of PWA\"\n[8]: https://yanshuo.io/assets/player/?deck=594d673d570c357d0698a950 \"Building PWA\"\n[9]: //huangxuan.me/jsconfcn2017/\n[10]: https://reactnative.dev/blog/2021/10/26/toward-hermes-being-the-default\n[11]: https://youtu.be/lGEMwh32soc\n[12]: https://reactjs.org/blog/2022/06/15/react-labs-what-we-have-been-working-on-june-2022.html\n"
},
{
"path": "_includes/about/zh.md",
"content": "Hey，我是黄玄（a.k.a. Hux, _@huxpro_），一个略懂计算机科学与艺术的斜杆不动青年，自诩是一个[广院](https://baike.baidu.com/item/%E4%B8%AD%E5%9B%BD%E4%BC%A0%E5%AA%92%E5%A4%A7%E5%AD%A6)数字媒体艺术系与 RIT 计算机科学系（师从 [Prof. Matthew Fluet](https://www.cs.rit.edu/~mtf/) 专攻编程语言）杂交出来的[黑客与画家](https://book.douban.com/subject/6021440/)。\n\n现为 Facebook Meta 签约软件工程师，就职于开源技术网红团队 [React](https://beta.reactjs.org/community/meet-the-team#react-core)，曾参与 [Hermes JavaScript 引擎](https://hermesengine.dev/)，[ReasonML](https://reasonml.github.io/) (现 [ReScript](https://rescript-lang.org/))，以及 [Reality Labs](https://tech.fb.com/ar-vr/) 某保密项目等。在国内期间，曾被招募为阿里巴巴 · [阿里旅行（飞猪）](http://alitrip.com)· 前端工程师、微影时代 · 微票儿 · 前端基础设施工程团队负责人、[饿了么](https://ele.me/) · 大前端团队 · [PWA 顾问](https://medium.com/elemefe/upgrading-ele-me-to-progressive-web-app-2a446832e509) 等。\n\n\n目前的物理活动范围主要在美帝纽约与硅谷，也想当个数字游民侠。虚拟分身日常出没于[微博](https://weibo.com/huxpro)、[知乎](https://www.zhihu.com/people/huxpro/pins/posts)、[B站](https://space.bilibili.com/43271611)、[Instagram](https://www.instagram.com/huxpro/)、[推特](https://twitter.com/Huxpro/)、[Github](https://github.com/huxpro) 等。\n\n\n##### 技术演讲\n\n- [我的大前端世界观][20] · [FEDAY](https://fequan.com/2023/) · 2023\n- [前端已死，前端永生][21] · [掘金年度技术演讲](https://juejin.cn/meetings/talk2023) · 2023\n- [React 国情咨文 2022][13] · 第七届中国开源年会 · 2023\n- [React Labs: What We've Been Working On – June 2022][12] · React Blog\n- [React Without Memo][11] · [React Conf 2021](https://conf.reactjs.org/)\n- [Toward Hermes being the Default][11] · React Native Blog · 2021\n- React Native 0.64 with Hermes for iOS · [The RN Show Podcast Ep #5](https://www.callstack.com/podcast-react-native-show) · 2021\n- [Upgrading to Progressive Web Apps][9] · [Youtube](https://www.youtube.com/watch?v=RWzMF-1fjJ8&t=1s) · [JSConf CN 上海 2017](http://2017.jsconf.cn/)\n- Building Progressive Web Apps · [CSDI 广州 2017](http://www.csdisummit.com/)\n- The State of Progressive Web App · GDG IO Redux 北京 2017\n- 炒冷饭 · PWA 到底是个什么玩意？· Baidu HQ 北京 2017\n- [Service Worker 101][5] · GDG DevFest 北京 2016\n- [Progressive Web App，复兴序章][4] · [QCon 上海 2016](http://2016.qconshanghai.com/presentation/3111)\n- Progressive Web App 之我见 · GDG IO Redux 北京 2016\n- [CSS Still Sucks 2015][2] · 2015\n- [JavaScript 模块化七日谈][1] · 2015\n\n\n##### 媒体关注\n\n- [Hux 黄玄：从全局视角看 React 生态][14] · 直播 · 图灵 8 点半 · 2023\n- [2022 中国开源先锋 33 人][18] · SegmentFault · 2023\n- [React 黄玄：不懂艺术的 B-Boy 不是 Swag 的程序员][16] · Gitee 封面人物 · 2022\n- [在硅谷当程序员是怎样的体验？][17] · 知乎[《我所向往的职业啊》](https://movie.douban.com/subject/36015036/) · 2022\n\n\n\n\n[1]: //huangxuan.me/2015/07/09/js-module-7day/\n[2]: //huangxuan.me/2015/12/28/css-sucks-2015/\n[3]: //huangxuan.me/2016/06/05/pwa-in-my-pov/\n[4]: //huangxuan.me/2016/10/20/pwa-qcon2016/\n[5]: //huangxuan.me/2016/11/20/sw-101-gdgdf/\n[6]: https://yanshuo.io/assets/player/?deck=58ac8598b123db0067292f92 \"PWA Rehashing\"\n[7]: https://yanshuo.io/assets/player/?deck=593ad6fbfe88c2006a0a0d6d \"The State of PWA\"\n[8]: https://yanshuo.io/assets/player/?deck=594d673d570c357d0698a950 \"Building PWA\"\n[9]: //huangxuan.me/jsconfcn2017/\n[10]: https://reactnative.dev/blog/2021/10/26/toward-hermes-being-the-default\n[11]: https://youtu.be/lGEMwh32soc\n[12]: https://reactjs.org/blog/2022/06/15/react-labs-what-we-have-been-working-on-june-2022.html\n[13]: https://www.bilibili.com/video/BV1LY411Q7hC/?spm_id_from=333.999.0.0\n[14]: https://appycyfaqcq1951.pc.xiaoe-tech.com/p/t_pc/course_pc_detail/video/v_64477dbfe4b0cf39e6c11d2a\n[15]: https://segmentfault.com/a/1190000043208486\n[16]: https://gitee.com/gitee-stars/30\n[17]: https://www.zhihu.com/zvideo/1542577108190068737?page=ogv\n[18]: https://segmentfault.com/a/1190000043208486\n[19]: https://juejin.cn/post/6844903750155419655\n[20]: https://www.bilibili.com/video/BV1SC4y1c7ju/\n[21]: https://www.bilibili.com/video/BV1uz421d7Ch/\n"
},
{
"path": "_includes/ads.html",
"content": "\n\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