Hexo is a great tool to get quick results (see Part One of this series), when you decide to have a blog and its defaults are practical, but it’s power lies in the possiblities of customization via plugins. On the official plugin page, there are actually 302 plugins listed, but there are many more and no wish will be unsatisfied.
I will show you which of these I found worth to work with…
The build-in way to include images in your posts works fine, but it is a little aside the normal way to declare images in Markdown. The plugin [Hexo Asset Link] corrects that. After installing via
npm install hexo-asset-link --save you can write this:
The best is, that VS Code’s Markdown can now show the image.
Actually the plugin destroys external links, so don’t use it until this is fixed … or go to node_modules > hexo-asset-link > index.js in your project and change in line 22
UPDATE from Update:
liolok, the author of the plugin has merged my pull request and published a new new version without the typo. It works now as expected.
A new Hexo project comes with a sample post called
Hello World. This is fine to play around with, but you don’t want to publish it. Here comes a Hexo plugin to the rescue called Hexo Hide Posts. After installing, you just have to write
hidden: true to the Front Matter of you post and it won’t be shown on the blog, but it is still available by URL.
Hexo has the concept of Assets Folders, but for static files, beside article based files, I find it more useful to have a STATIC folder and copy the contents on every build into the publish folder. A good helper for this approach is the plugin Hexo Generator Copy. Install it by running
npm install hexo-generator-copy --save and add
static_dir: static to your
_config.yml and you are done.
![Hexo Static Files](/post/A-New-Blog-Customizing-Hexo/vscode-1.png)
The default Hexo layout has an Atom Feed icon in the upper right corner, but strangely no feed file is generated on build. You need to install the plugin Hexo Feed Generator to fix this, by running
npm install hexo-generator-feed --save and copy following section into the
In these modern times it’s always a good idea, that your blog feels like an App. For this you need a manifest file (JSON) an several icons (PNG). You can generate these files very fast with the Web App Manifest Generator and store it in your static folder.
To bind this file into your blog, you can use the plugin Hexo PWA. Run
npm install --save hexo-pwa and copy following section to your
_config.yml, where you take the settings from your generated manifest file:
To help Google and others a bit to index your blog, it is advisable to provide a sitemap file. Here comes Hexo Generator Sitemap to the rescue. Install it by running the command
npm install hexo-generator-sitemap --save. You can configure it via
The plugin installation doesn’t create the needed
sitemap-template file, so be sure you grab a copy from the plugins repository: https://github.com/hexojs/hexo-generator-sitemap/blob/master/sitemap.xml
Hexo doesn’t have a commenting system, but it’s prepared to stick Disqus comments under each article. Just create a new Disqus account for your blog and note the given short name. By adding following section to the
_config.yml Hexo shows the commenting section:
Hexo shows as much articles at the start page as configured in
index_generator.per_page, but it’s nicer to load more articles as you scroll by using the Hexo script Inifinite Scroll. Install by adding following little script in themes & gt; layout > _partial > after-footer.ejs
Its nice to support the reader on scolling by providing a Scroll-To-Top button. The easiest way to get this, is the script Vanilla Back To Top. Just add follwing to themes >layout > _partial > after-footer.ejs:
You can interact with this article (applause, criticism, whatever) by mention it in one of your posts, which will be shown here as a Webmention ... or you leave a good old comment with your GitHub account.
In case your blog software can't send Webmentions, you can use this form:
No Webmentions yet...