Hexo 3.2 Roadmap

[tommy351]

• Include/Exclude source files
• Not to delete other non-hexo files during generation. Not to delete other non-hexo directory when do generation #1310
• Get rid of index.html. Get rid of index.html in URL #1306
• Ignore node_modules folder in the theme. Exclude a folder from files to be checked/watched #1316
• Make anchors in each posts unique. Anchors in individual blog entries aren't made unique in the main page #1302
• Expose code highlight point. Expose code highlight extend point to use other highlight tools. #1300
• Inline CSS helper. Option in inline css with css helper #1295
• Detect the current category/tag in is_category/tag helper. hexo可以实现判断某个分类么？ #1278

I'll start working on this during summer vacation. Feel free to write your suggestions below.

[Xuanwo]

Sounds great!

[Xuanwo]

Include/Exclude source files

I think we can make it a default option, almost everyone want their md files to be saved.
We can create a source branch and upload the source files while we deploy.

[tommy351]

@Xuanwo Yep, .htaccess for example.

[Xuanwo]

关于插件的更新，我还有一个问题是这样的。

我一直在用travis部署，然后重装系统之后也一直没有重新安装nodejs环境，所以我没有运行npm update的环境，导致我的package.json中插件的有关信息一直没有得到更新。这个问题导致我有一段时间一直build failed。
有没有办法始终保持自己安装的各项插件始终最新呢？

每一次npm install之前手动npm update？还是自己手动修改package.json？

[tommy351]

You can use npm outdated command to check what packages need to be updated.

[Xuanwo]

I got it.

然后我还有的问题就是像这样：#1333
对这种不需要渲染的东西，有没有更加机智地处理办法，感觉skip_render并不是十分好用。
可以另外建立一个raw文件夹，然后generate之后copy到public中去。

nunjucks貌似存在一个BUG，当js文件特别大的时候，会出现报错。

[practicalli-johnny]

Generating an RSS feed for a specific tag (categories are too broad)

• my blog covers many topics and so its not possible to share my feed with many specific blog rollers. This reduces the exposure my blog gets :(

Defining top level navigation, disqus name, banner logo, etc into the main _config.yml file rather than the theme, (or allowing it to be passed through). This would reduce the need to also put the theme into version control

[borian]

Nice, I have been waiting for .htaccess support ! 👍

[Djabx]

I agree with @jr0cket
I would love to not put the theme into version control (at least not with my blog).

Maybe reference themes as an npm plugin / git submodule ?
But the question of the configuration file pop-up...

[leesei]

I also agree on have a root config (say theme.yaml) to override theme config (something like extend(theme/config.yaml, ./theme.yaml).
Most user just pull the theme and modify the config once and for all. It's quite troublesome to fork and check in the theme just for the updated yaml.

[Xuanwo]

Agree with @leesei, maybe we can have a default setting and a user setting. And user setting will override default setting.

[diessica]

Happy that the issue I reported and some other important ones were noticed. I'll stick around :)

[OdinsHat]

• Not just .htaccess but CNAME file which is required for hosting on Github.

[emceeaich]

👍 to @jr0cket's request to move user configurations out of the theme and up to the site level.

This would require modifications to existing themes, but we could split up the work with theme creators/maintainers.

[emceeaich]

I would like to have https://www.npmjs.com/package/hexo-generator-feed in the initial install and the configuration block for syndication feeds by default.

Otherwise, you'll make a rookie mistake like me and think I had gotten feeds set up for my blog! :)

[Xuanwo]

ref #1626, #828, #1411

How about a feature that achieve the arrticles in other floder instead of _post ?

[Vinnl]

I don't really like +1 comments, but there doesn't seem to be another way to indicate demand, so... Per-tag RSS feeds would be great. Second to that overriding theme settings would be nice as well.

(Also, thanks! Hexo seems to be pretty much everything I was looking for!)

[Xuanwo]

@tommy351 although Include/Exclude source files func added, but due to this comment : #1705 (comment) , maybe we should copy them to public instead of just exclude them.

[akfish]

How about #1780?

[soulteary]

@Xuanwo ，skip files的需求我也遇到了...感觉可以考虑让用户自己挂脚本到render里，做路径排除，以及排除后的操作，是sync，还是怎么样，实际修改成本，应该只有在plugin/generate＊里添加一个hook name...

实现参考：https://github.com/soulteary/hexo-extend-plugin/blob/master/patch/hexo/lib/plugins/generator/page.js

[soulteary]

另外，何不让用户自己选择开启或者关闭一些features呢，搭配自带的cli使用，包括并不限rss之类的。

实现参考：https://github.com/soulteary/hexo-extend-plugin/tree/master/patch/hexo/lib/plugins/console

[NoahDragon]

Moved to road map 4.0 #2492