Library / SDK
ppoffice/hexo-theme-icarus avatar
ppoffice/hexo-theme-icarus

hexo-theme-icarus 7: three looks behind one variant key, and a renderer you must install alongside

A simple, delicate, and modern theme for the static site generator Hexo.

6,634 stars1,516 forksJavaScriptMIT

At a glance

What is it?
Icarus is an MIT-licensed Hexo theme that now ships Default, Cyberpunk and Material 3 Expressive variants plus 50+ built-in integrations. It needs Hexo ^7.1.1 or ^8.0.0 and the hexo-renderer-inferno package, and it moved from 6.6.0 to 7.0.1 within three days in October 2026.
Who is it for?
Icarus fits Hexo bloggers on Hexo 7.1.1 or later, or Hexo 8, who want a configurable theme with comments, search, analytics and math already wired in and are happy to manage three layers of configuration. It does not fit sites stuck on older Hexo releases, or anyone who needs the Cyberpunk look in a light scheme.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 21 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • ppoffice/hexo-theme-icarus6,634 ★ · -18
Star history
Repository2026-09-232026-11-15
ppoffice/hexo-theme-icarus6.7k6.6k

-18 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The theme only renders with hexo-renderer-inferno installed beside it

Icarus is not a drop-in folder of templates. Its layouts are built with Inferno, so a published install brings in two npm packages at once, then points Hexo at the theme:

shell
npm install hexo-theme-icarus hexo-renderer-inferno
hexo config theme icarus
hexo server

This has to run in the root of a Hexo site whose Hexo version satisfies ^7.1.1 || ^8.0.0, the same range package.json declares for its hexo dependency. A site on an older Hexo release has to upgrade Hexo first; the published theme will not meet it halfway. On the first run Icarus writes _config.icarus.yml into the site, with every option described inside the file, so the generated config doubles as the option reference. The theme itself is assembled from Hexo, Inferno, Stylus and Bulma, with bulma-stylus 0.8.0 as a runtime dependency.

Published releases and the master branch are not the same thing

The Getting Started guide separates a published install from the current development checkout, and the release history shows why that matters. 6.6.0 appeared on 2026-10-23, 7.0.0 on 2026-10-26, and a 7.0.1 entry the same day about forty minutes later. That 7.0.1 entry is listed under the identifier untagged-511d8369384e629b96b1 rather than a version tag, while package.json on master already reads 7.0.1. The last push to the repository was on 2026-10-26.

For site owners the consequence is that a major version arrived three days after a minor one, and anyone pinned to 6.x is crossing a major boundary when they update. The project keeps a separate Upgrade Guide for that step. Installing from a source checkout gets you whatever is on master, which can differ from the npm package your neighbour installed, so state which one you use when filing an issue.

One variant key switches the whole look, but Cyberpunk has no light mode

A single line in _config.icarus.yml chooses the visual variant, and the same key in a post's front-matter overrides it for that post alone:

- variant: default is the classic Icarus look in light or dark, or appearance: auto, which follows each visitor's system setting and adds a light/dark switch to the navbar. - variant: cyberpunk is always dark, with neon colors, HUD panels with chamfered corners, scanlines and its own code palette. - variant: m3e is Material 3 Expressive: tinted surfaces, rounded cards, and pill-shaped controls that change shape on hover and keyboard focus, in light and dark schemes.

The limitation sits in the Cyberpunk description. It is always dark, so a reader who prefers light pages gets no switch and no system-following behaviour on a Cyberpunk post. If accessibility for light-mode readers matters to you, Default with appearance: auto or m3e are the variants that offer both schemes.

Options resolve across three layers: site, layout and post

Icarus lets you set an option site-wide in _config.icarus.yml, override it for a whole layout in _config.post.yml, and override it again for one post in that post's front-matter. This is how a single post can carry its own variant, or how post pages can show a different sidebar arrangement from the home page.

The cost is that a value on screen can come from any of three files. When a widget appears on one page and not another, check the post's front-matter first, then the layout file, then the site config, before assuming a bug. The responsive layout runs from one to three columns, navbar sub-menus fold into a menu button on narrow screens, the sticky navbar is optional, and mobile readers get their own table of contents, so layout choices also change by screen width.

Most of the 50+ integrations live in hexo-component-inferno

The theme advertises more than 50 built-in plugins that are switched on from config. Comments cover Artalk, Beaudar, Changyan, Disqus, DisqusJS, Giscus, Gitalk 2 (still marked preview), Isso, LiveRe, Twikoo, Utterances and Waline. Search can use Algolia, Baidu, Google CSE or the built-in Insight. Sharing supports AddToAny, ShareThis and Web Share. Donation buttons cover Afdian, Alipay, Buy Me a Coffee, Patreon, PayPal and WeChat Pay. Analytics range from Google Analytics, Matomo and Umami to Baidu Statistics, CNZZ and Hotjar. Math uses KaTeX or MathJax 4, and galleries use lightGallery 3 with Justified Gallery.

Most of these integrations are provided by a separate package, hexo-component-inferno, not by this repository. When a comment system or analytics snippet misbehaves, the fix may belong in that component repository, and a theme update alone will not change it unless the component version changes too.

Cookie Consent gates the built-in analytics, so check your other widgets

In opt-in mode, Cookie Consent loads the built-in analytics only after a visitor allows them. Web Share lets readers share a post without loading a third-party SDK, which is the privacy-friendly choice among the three share options.

The opt-in behaviour is described for analytics. Comment systems such as Disqus, the Google AdSense widget and third-party share services like ShareThis are separate integrations, and the theme's own description of Cookie Consent does not say they are held back. If you run a site where consent rules apply, enable your chosen widgets on a test build and watch what loads before a visitor clicks allow, rather than assuming opt-in mode covers everything. The theme also adds a notice on posts that have not been updated for a long time and a reading progress bar, both independent of consent.

engines says Node 14, the test suite wants Node 20.19

package.json declares engines node >=14, but the tests need Node.js 20.19 or later. For a contributor, the working loop is:

shell
npm ci
npm run lint
npm test            # unit and integration tests
npm run test:e2e    # browser tests; run "npx playwright install chromium" once first

npm test chains test:unit and test:integration, both run with mocha over test/unit/**/*.test.js and test/integration/**/*.test.js. test:e2e drives Playwright with test/e2e/playwright.config.js, and needs Chromium installed once through npx playwright install chromium. test:all runs both. Lint is eslint across the repository with eslint-config-hexo. A contributor on an older Node that satisfies the engines field will still hit failures in the test suite, so set up Node 20.19 before opening a pull request. Translations live in languages/, with 17 languages shipped.

Editorial conclusion

Icarus fits Hexo bloggers on Hexo 7.1.1 or later, or Hexo 8, who want a configurable theme with comments, search, analytics and math already wired in and are happy to manage three layers of configuration. It does not fit sites stuck on older Hexo releases, or anyone who needs the Cyberpunk look in a light scheme. Before upgrading an existing 6.x site, read the Upgrade Guide, and before relying on Cookie Consent for compliance, confirm which of your enabled widgets it actually holds back.

Frequently asked questions

What is the Icarus theme for Hexo?

hexo-theme-icarus is a simple, delicate and modern MIT-licensed theme for the Hexo static site generator. It offers Default, Cyberpunk and Material 3 Expressive variants and more than 50 built-in plugins.

Which Hexo versions does hexo-theme-icarus support?

The published package targets Hexo sites compatible with ^7.1.1 || ^8.0.0, and it must be installed together with hexo-renderer-inferno.

Can hexo-theme-icarus use a different variant on a single post?

Yes. Setting variant in a post's front-matter overrides the site-wide value in _config.icarus.yml for that post only.

What Node.js version do hexo-theme-icarus tests need?

The tests need Node.js 20.19 or later, even though package.json lists engines node >=14. Browser tests also need Chromium installed via npx playwright install chromium.

Official sources

  1. License: MIT
  2. ppoffice/hexo-theme-icarus on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/ppoffice-hexo-theme-icarus.svg)](https://hysenlabs.com/projects/ppoffice-hexo-theme-icarus)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/ppoffice-hexo-theme-icarus.svg)](https://hysenlabs.com/projects/ppoffice-hexo-theme-icarus)

Was this useful?