Blog migration plan

13 Mar, 2016Jekyll, Hexo

I started using Jekyll’s new theme on February 13th. It’s been exactly a month. During this period, I have been constantly optimizing the effects of the theme, but there are always some functions that the native Jekyll supported by GitHub Pages cannot achieve. If you use Ruby to develop third-party plugins, you can only generate static pages locally and then synchronize. This is also a contradiction in Jekyll: Since third-party plugins are not supported and online editing is not possible, all must be edited locally. Upload again, what is the meaning of Jekyll's existence?

During this period, I also looked at Hexo. There are a lot of users, and the plug-in coverage is relatively complete. Based on node.js, it is completely generated locally, and the development of plug-ins can be more casual. So the next plan is to apply the theme of the current blog to Hexo, and implement the previously unfinished functions on Hexo through existing plug-ins, npm or self-developed plug-ins.

In addition, regarding social comments, the disqus used before, and the ones that have optimized CSS now (the default is simply ugly and there is no mobile adaptation). It’s said that using non-HTTPS Weibo avatars will generate pages HTTPS Warning (Weibo is simply disgusting, this is not HTTPS in this age), so although there have been some blog comments, I plan to use disqus after the migration.

Powered by Gatsby. Theme inspired by end2end.

© 2014-2021. Made withby mdluo.