fluid-dev / hexo-theme-fluid

:ocean: 一款 Material Design 风格的 Hexo 主题 / An elegant Material-Design theme for Hexo
https://hexo.fluid-dev.com/
GNU General Public License v3.0
7.4k stars 1.13k forks source link

Will my own configuration in _config.yml be overrided after updating the fluid theme? #845

Closed erjiaxiao closed 2 years ago

erjiaxiao commented 2 years ago

Make sure

Describe the question

As mentioned in the title, if it will, how could I keep my own configuration while updating?

zkqiang commented 2 years ago

See override-configuration

erjiaxiao commented 2 years ago

Hello @zkqiang, sorry to disturb you, could I ask why we don't need to worry configuration override if we use npm to install and update fluid theme? Is there any mechanism which helps us keep custom configuration automatically?
2022-09-27 202315

zkqiang commented 2 years ago

@erjiaxiao Because _config.fluid.yml file should be in the blog directory after installation via npm (if you follow the guide), npm updating the fluid will not override it

erjiaxiao commented 2 years ago

@zkqiang I see.. So that also means if I store my own custom_avatar.png in the folder blog_dir/themes/fluid/source/img. Then it will be overrided after updating via npm. Is it right?

zkqiang commented 2 years ago

@erjiaxiao No, npm install in blog_dir/node_modules/hexo-theme-fluid, not in the blog_dir/themes/, which is two install ways, and you don't need to do them both.

If you want to update via npm, actually you can delete theme/fluid and place custom_avatar.png in blog_dir/source/

erjiaxiao commented 2 years ago

@zkqiang I see.. Thanks for your patience. The whole process is more clear to me. Do you think it is necessary to open a PR to add these messages in the docs of fluid theme, making it more informative?

zkqiang commented 2 years ago

@erjiaxiao In fact, these messages already exists in the docs, of course some of the messages belongs to Hexo docs

erjiaxiao commented 2 years ago

@zkqiang My bad.. next time I'll look through it more carefully. Thanks for so many explanations!