This review asks why Stellar has not reached the top tier of Hexo themes. The 2026-08-14 snapshot gives a mixed answer: Stellar ranks ninth in stars, but third in monthly npm downloads; its star growth slowed after a strong 2024, yet its recent annual growth is still ahead of several peers. The product explanation completes the picture: Hexo’s mainstream mental model is still a lightweight blog, while Stellar presents a blog, knowledge base, topic system, and notebook system as one content platform.
Data scope: GitHub and npm snapshots are from 2026-08-14; competitor capabilities are based on official README files and documentation checked on 2026-08-15. “Inference” marks a reasoned conclusion rather than a directly measured fact.
TL;DR: three conclusions
- Positioning is out of step with the mainstream. Stellar’s four integrated content systems are unusually complete, but users looking for a lightweight blog may perceive them as complexity.
- Growth has no flywheel. System-level releases create discussion and tutorials; after the January 2024 release burst, March added 236 stars in one month. When comparable events stopped, growth returned to roughly 30 stars per month.
- Trust and conversion are leaking. A 13-month release gap weakened confidence. Stellar has many installers but fewer public endorsements, and Chinese-first materials limit overseas conversion.
The practical sequence is to clarify the positioning first—a blog and knowledge base in one—provide a low-friction starting path, then turn 2.x into an event and establish a monthly maintenance rhythm.
Data review: position, growth, and trust
A contradictory snapshot
| Metric | Value | Relative position |
|---|---|---|
| Stars | 2,008 | 9th |
| Monthly npm downloads | 8,539 | 3rd |
| Forks / stars | 0.22 | Upper tier |
| Average annual stars | 366 | Mid-pack |
| Releases | 80 | 5th |
| Contributors | 46 | 6th |
| Open issues | 21 | Mid-pack |
| Release gap | 13 months | 2025-07-17 to 2026-08-08 |
Adoption and maintenance investment are not weak, yet the star count remains at 2,008. That contradiction is the central clue.
Growth engine: event-driven, and silent when events stop
2021 ██ 80 |
In January 2024, nine versions were released in quick succession. Version 1.25.0 introduced the topic system and 1.27.0 added the right sidebar; March then became the obvious turning point. From August 2025 to July 2026 there was no comparable product event.
Inference: the mechanism is “system-level feature → community discussion and tutorials → word of mouth,” with a delay of one or two months. Routine maintenance releases do not create the same reach. Each year needs at least one system-level event, together with deliberate communication.
The trust ledger
| Year | Releases | Note |
|---|---|---|
| 2021 | 15 | High-frequency initial iteration |
| 2022 | 22 | Annual peak |
| 2023 | 5 | Clear slowdown |
| 2024 | 18 | Activity recovered |
| 2025 | 13 | Concentrated in June and July |
| 2026 | 7 | Concentrated in August |
After 1.33.1 on 2025-07-17, the next release did not arrive until 1.34.0 on 2026-08-08. This is understandable for a project maintained by one person, but release rhythm still affects trust. Small, regular releases can maintain confidence at much lower cost than a year-long silence followed by a burst.
The scissors gap: many users, fewer endorsements
| Recent monthly ranking | Downloads | Annual ranking | Downloads |
|---|---|---|---|
| NexT | 17,234 | NexT | 196,535 |
| Butterfly | 16,604 | Butterfly | 143,072 |
| Stellar | 8,539 | Fluid | 104,238 |
| Fluid | 7,164 | Redefine | 73,676 |
| Volantis | 6,398 | Keep | 65,901 |
| Redefine | 5,139 | Stellar | 45,076 |
Stellar ranks third in monthly downloads and sixth over the year, but ninth in stars. If “see → install → star → recommend” is a funnel, Stellar performs well in the middle and poorly at both ends. People who find it often use it, but too few people find it and too few recommend it.
The August spike was largely release-driven: downloads rose sharply after the 1.34–1.39 releases, while stars and issues barely moved. July’s spike had no corresponding release and may have come from external sharing or automated traffic. npm does not expose a source or version breakdown, so “existing users upgrading” remains an inference rather than a confirmed fact.
Product review: positioning and mental models
| Theme | One-line positioning | Mental model |
|---|---|---|
| NexT | Classic, elegant, and extensible | The established default |
| Butterfly | Card-based and feature-rich | The Chinese community favorite |
| Volantis | Modular and highly customizable | The modular all-rounder |
| Redefine | Simple, fast, and clean | Minimalist design |
| Solitude | Designer-oriented with distinctive pages | A personal homepage with flair |
| Stellar | Business-like minimalism plus four content systems | A knowledge-management blog |
The mainstream Hexo need is a lightweight blog: posts, categories, tags, links, and comments. Most leading themes answer “how can a blog look and work better?” Stellar answers “what else can live beside a blog?” It treats blog, knowledge base, topics, and notebooks as one content system. That is valuable for long-term creators, but heavy for users who only want to publish posts.
Do the four systems really have no competitors?
That claim needs correction. Volantis officially supports collaboration and documentation modules, so it overlaps with Stellar as an all-rounder. Stellar’s actual difference is the integration of four systems and dynamic data components out of the box, without assembling modules. Redefine has notebooks and Solitude has short-form posts, so multiple content types are not unique to Stellar; few themes package them as a coherent system.
At the engineering level, Stellar has built-in search while most peers require a search plugin. Pjax is common among competitors but not built into Stellar, and Solitude is the only one in this group with built-in PWA support. Stellar leads in content systems, not in every aspect of engineering convenience.
The double edge of substantial features
- Environment cost: Stellar requires Node ≥ 22, while several peers support older Node versions.
- Cognitive cost: topic, wiki, and notebooks introduce concepts that require documentation before their value becomes obvious.
- Migration cost: moving from Butterfly or NexT changes the content model, not just the visual skin.
Inference: the real cost is not “cannot install,” but the first impression. A lightweight theme gives an immediate reward; Stellar asks users to understand its positioning first. The answer is not to remove depth, but to explain the cost clearly and prove that a useful site can be running in 30 minutes.
Knowledge management is not yet a Hexo category
Blogging is a mature category in Hexo; knowledge bases and documentation sites are not. Stellar is betting on a real but smaller audience: creators who want to manage knowledge inside their blog. Category awareness comes from repeating one sentence across the README, documentation, showcase, and tutorials: a blog and knowledge base in one.
Undervalued assets
- npm adoption: third-place monthly downloads suggest that people who discover Stellar are willing to use it.
- Integrated content systems: the combination of four systems and dynamic data components remains a strong differentiator.
- Documentation and examples: the Wiki, blog/docs example repository, showcase sites, and community provide a solid foundation.
The issue is not that these assets are weak; they have not yet been systematically converted into reach, stars, and community participation.
Conclusion: mismatch, not only growth
The complete conclusion is twofold: positioning mismatch and insufficient growth mechanisms. Stellar serves knowledge-management creators while the mainstream expects lightweight blogs; event-driven growth stops when major events stop; long release gaps consume trust; adoption does not yet become advocacy; and users do not consistently flow back into the community.
Positioning is the direction and growth is the amplifier. The order is to explain the positioning, then amplify it through releases, examples, and a steady maintenance cadence.
Roadmap
| Track | Action | Priority | Expected effect |
|---|---|---|---|
| Positioning | State “a blog and knowledge base in one” on the README and provide a lightweight starting path | High | Lower understanding and migration costs |
| Positioning | Continue translating the README and documentation | High | Improve overseas conversion |
| Growth | Turn 2.x into an event with release notes, tutorials, cases, and showcase updates | High | Create a new growth inflection point |
| Growth | Turn npm adoption and showcase sites into communication assets | Medium | Improve star and word-of-mouth conversion |
| Trust | Establish one small maintenance release each month | High | Restore a stable trust baseline |
| Retention | Provide one-click examples and turn documentation issues into tutorials | Medium | Lower the getting-started cost |
| Community | Improve contribution guidance and feedback channels | Medium | Turn one-time users into participants |
Stellar has not built the wrong product; it has not yet occupied the right category. Clarify the positioning first, then use growth events to make it visible.
A personal note from the author
Good design should combine culture and logic. I lack experience and execution ability on the artistic side, so what I can pursue—and have always pursued—is rational aesthetics: the romance of mathematics and formulas. Concentric circles, symmetry, consistency, stability, and intuitive behavior are abstract things with order. That is also why they often look ordinary at first glance rather than immediately eye-catching.
I have always been an extreme introvert: I am barely active in any community and rarely join discussions. I have never used Xiaohongshu and do not have a personal Douyin account; my Moments feed only mirrors blog posts and occasionally shares music. I have not enabled analytics or submitted the site to search engines, and my work has no promotion channel beyond this blog. The traffic is small but comes mostly from real users and readers. Thank you to those quiet contributors. 
