Experiencing Hexo

作者 Zhe Wang 日期 2017-12-18
Experiencing Hexo

The post won’t be technical. It’s been quite a long time since I used WordPress as a blog framework, though few blogs had been written. Recently I rebuilt the blog on Hexo, which is simple.
I will keep the old site with http protocol. Meanwhile, the new one could be visited with https protocol.

Some Highlights

1.Static Files Server

I treat Hexo as a blog framework which is deeply related to github.io. As we know, github.io is a blog system that is only able to serve static files. The final deploying files of hexo are all static files like js, css, html and other static asset. No database, backend MVC framework, route dispater and blablahhhh are available.

2.Markdown

However, the owners should write posts with Markdown instead of editing those static files directly. Hexo offers commands to create new post, generate deploying files and so on. It’s like building a project since your main work is within source directory by default (changing name of the directory by modifying configuration is supported, of course, which is meaningless), generating an output directory to deploy at last.

3.Theme and Plugins

You can simply define theme and plugins which your blog may use in a yalm configuration. Hexo also offers many APIs besides commands for senior developing. I haven’t dig the area too much.

P.S.

Compared with WordPress, hexo is much lighter and easier to use. I make this brief introcution mainly because the site you’re visiting right now is powered by hexo and I want to make a new start for the blog.

A Trailer

Recently I’m working on a mobile app based on React Native. Hybrid App is really a major issue and I want to talk about How to Make Webview Run Faster in the next post.