Refactor front-matter: make it has the same key as the configuration file

[jiangtj]

PR Checklist

• The commit message follows our guidelines.
• Tests for the changes was maked (for bug fixes / features).
  • Muse | Mist have been tested.
  • Pisces | Gemini have been tested.
• Docs in NexT website have been added / updated (for features).

PR Type

• Bugfix.
• Feature.
• Code style update (formatting, local variables).
• Refactoring (no functional changes, no api changes).
• Build related changes.
• CI related changes.
• Documentation content changes.
• Other... Please describe:

What is the new behavior?

1. make it has the same key as the configuration file.
2. support reward_settings.comment in front-matter.
3. quicklink support more configuration in front-matter.

I think that front-matter having the same keyword as configuration file is a good solution to avoid confusion.

• Link to demo site with this changes: https://gitlab.com/JiangTJ/next-test/blob/master/source/_posts/many-title.md

How to use?

In post front-matter:

toc:
  enable: true
  number: false
  max_depth: 3
reward_settings:
  enable: true
  comment: Donate comment here.
quicklink:
  enable: true
  delay: true
  timeout: 3000
  priority: true
  ignores:

# Some deprecated
- toc_max_depth: 4
- toc_number: true
- reward: true
- quicklink: true

Does this PR introduce a breaking change?

• Yes.
• No.

quicklink:
  # Home page and archive page can be controlled through home and archive options below.
-  home: true
-  archive: true
+  # This configuration item is independent of `enable`.
+  home: false
+  archive: false

[jiangtj]

https://gitlab.com/JiangTJ/performance-test-hexo/-/jobs/319867428 performance test pass

GitLab

run-test (#319867428) · Jobs · JiangTJ / performance-test-hexo

GitLab.com