Hexo Roadmap

Here is a to-do list for Hexo:

New features:

• [ ] Add taxonomies to hexo #828
• [x] Support multiple non-hierarchical categories #848 PR #2734
• [ ] Paginating a post like WordPress <!--nextpage-->? #3035, #896
• [ ] Why can't pages use tags and categories? #1067
• [x] Expose code highlight extend point to use other highlight tools. #1891 #4010
• [x] Support other syntax highlighting libraries https://github.com/hexojs/hexo-util/issues/108 (Highlight.js is slow #1036) #4119
• [x] Get rid of index.html in URL #1306 #3691
• [ ] Single File, Generate/ Deploy #2519
• [ ] Support single page application (SPA), like Vuelog.
• [ ] Expand the cli tool.
  • [ ] Plugin management https://github.com/hexojs/hexo-cli/issues/174
  • [x] Install theme through npm install #2471
• [ ] Apply include: / exclude: to all folders (notably themes/) https://github.com/hexojs/site/pull/1195
• [x] Verify the configuration file https://github.com/hexojs/hexo/pull/4381

Fixes:

• [x] partial not support look up parent directory, and absolute path not functioning as well #819
• [x] include_code link and root config #928
• [x] hexo server error when I change the config #1099 (https://github.com/hexojs/hexo/pull/5055)
• [x] is_current('') is always true, regardless of current page url #1112 (Expected behavior)
• [x] Default language #1125 #3069 #3110
• [x] Spaced string in imgTag #1277
• [ ] Anchors in individual blog entries aren't made unique in the main page #1302
• [x] relative_link: true doesn't work correctly #1381
• [x] AppVeyor test case fails https://github.com/appveyor/ci/issues/1560
• [x] Post name support underscore to connect variables #1970
• [x] Different result between hexo g and hexo s #2451 #2503 #2897 #2902 #2979 #3171 #3756
• [ ] --watch triggers whole site regeneration #2991
• [x] Proper handling of templates in a post #3259

Miscellaneous:

• [x] Convert old js code to ES6 standard.
  • [x] Source code
  • [x] Test code #2488
• [ ] Speed is the key.
• [x] Reduce the number of issues to below 100, which is a decent amount to manage by few people.
• [x] Raise fund to cover existing fees (like domain name fee) and buy extra services (like NPM organization) ~~#2494. Open Collective Account~~ Open Collective is controlling the fund. Maybe bitcoin or paypal donation could be a better approach. @tommy351 figure out a way to cover the cost.
• [x] Clean up leftover tasks in old milestone (Move to 4.0)
• [x] Jade to pug https://github.com/hexojs/hexo-renderer-jade/pull/35
• [x] Remove swig dependency #2903
• [x] Awesome-hexo repo https://github.com/hexojs/awesome-hexo
• [ ] Docker image to avoid the environment setting issue. #3891
• [ ] Using Prepack to optimize the code.
• [ ] Hexo newsletter.
• [x] Hexo general email account. [email protected]
• [x] Add meta generator to Hexo generated website. https://github.com/hexojs/site/pull/649 #2734
• [x] Replace cheerio with native API #3677
• [ ] Migrate helper plugins to hexo-util
• [x] Integrate hexo-bunyan into hexo-log
• [x] Enforce ES6 syntax https://github.com/hexojs/eslint-config-hexo/pull/22
• [ ] Refactor Promise to async/await #3328
• [ ] Adopt Prettier style https://github.com/hexojs/eslint-config-hexo/pull/25
• [x] Replace lodash with native API #3753, project
  • [x] Drop _ (lodash) from Locals/global variable
• [x] Refactor to WHATWG URL API (Project page)
• [ ] Improve test coverage https://github.com/hexojs/hexo/issues/3984
• [ ] Multi core usage #4355

Please feel free to leave your thought in comments.

make sure, that hexo s and hexo g are in sync and take care about the meta tags in < head >, before introducing any new features, please.

see here: https://github.com/hexojs/hexo/issues/2503

Please work on performance and multi core support on hexo server and hexo generate. I have major problem with big site generation in Hexo like this: #2579

@mnlbox Yes, it will be the major update in 4.0 build.

any news, regarding the release date, especially for https://github.com/hexojs/hexo/issues/2503 ?

@kirkcameron Not yet. The server calls the render function is as same as the generator, don't have clue why causes the differences.

@NoahDragon could you please share more details on the performance improvement?

@huiwang Thanks for asking.

The generating performance issue is really hard to reproduce. It may cause by plugin, renderer, or Hexo self. We occasionally receive issue regarding performance, but only few shared their source to investigate. As far as I know, all of them are plugin and theme issue.

I also tested performance on Hexo vanilla install, 1000 posts generated costs 3 mins. Still, have space to improve, but seems not a major issue.

I noticed there's some confusion about how to do unit testing. This mocha.opts will help: https://gist.github.com/tcrowe/b22a63daea19eaee69fe2bc37adee854

Prettier can be included to force a uniform style across all hexo projects and it will integrate with eslint-config-hexo.

npm install prettier eslint-plugin-prettier

./.pretterrc

{
  "proseWrap": "never"
}

./.eslintrc

"plugins": ["node", "prettier"],

eslint --fix will then format using prettier.

Is Hexo still maintained? I love it but most packages are years old and I can't make my website multi-language :(

@microSoftware

Is Hexo still maintained?

Yes. Sure :)

most packages are years old

As you know some packages are not published new version but we continue to commit each official repositories.

I can't make my website multi-language :(

Hexo i18n seems a little bit difficult. (Sorry, I'm not familiar with Hexo i18n...) I think this issue @tcrowe answer might help you :)

Ok. After I tried most things to make it multi-language. I think the easiest solution is to create a seperate blog for each language. And create a simple dropdown in javascript in the theme.

@microSoftware , yes that is the most feasible way. Anything else requires Concept, Architecture, Design and Implementation that will complicate the things considerably. Just to be used by very small percentage of users.

If still interested, there is no shame in learning from (very long)WP experience, Perhaps starting from here.

@tcrowe is there a specific brance all these changes are being developed or worked on ?

@gautamz07 Each change, or set of changes, will be done in individual issues and PRs. So, if you want to do one of the items in the original post you can create a branch on your computer, do the change, and then create a PR.

Some patience is required to get a review and approval.

I changed issue title. Please see #3508 discussion.

#3259 seems to bring breaking changes

I have created a New Hexo Theme

GitHub Repo

Demo URL

@BRAVO68WEB You can submit your theme here: https://github.com/hexojs/site/pulls

Is this project dead?

Drops resolve from dependency in Hexo 7.0.0, see https://github.com/hexojs/hexo/pull/4863

wish add new command, such as:

hexo delete my_post //delete post
hexo modify my_post //modify post,if not exist, new one

Hi there,

Are you still looking for more active contributors for this page? Just curious..