Add postCopyright into the default injects point

[bytemain]

PR Checklist

Please check if your PR fulfills the following requirements:

• 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

What kind of change does this PR introduce?

• 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 current behavior?

The default copyright style.

Issue resolved: N/A

What is the new behavior?

you can create the copyright you like.

• Screenshots with this changes:
  after create custom copyright file:
  
• Link to demo site with this changes: https://lengthmin.me/posts/install-arch-wsl/

How to use?

In NexT _config.yml:

#postCopyright: source/_data/post-copyright.swig

uncomment the line, and insert your own file.

Does this PR introduce a breaking change?

• Yes.
• No.

[welcome]

Thanks so much for opening your first PR here!

[CLAassistant]

All committers have signed the CLA.

[1v9]

Cool, could you share your custom swig? We can add it to Awesome-NexT.

[jiangtj]

What is the difference between pointBodyEnd and postCopyright?
Maybe you can try adding postCopyright to pointBodyEnd.

[bytemain]

What is the difference between pointBodyEnd and postCopyright?
Maybe you can try adding postCopyright to pointBodyEnd.

their position are different, so I think it's better to add a new config.

[bytemain]

What is the difference between pointBodyEnd and postCopyright?
Maybe you can try adding postCopyright to pointBodyEnd.

and I think BodyEnd custom file is different from postCopyright custom file.
the BodyEnd behavior:

[jiangtj]

their position are different, so I think it's better to add a new config.

If the wechat_subscriber and the reward are added through postBodyEnd, the two injection points overlap, so modify the implementation of the wechat_subscriber and the reward can be better, do you think?

[bytemain]

Cool, could you share your custom swig? We can add it to Awesome-NexT.

I will share it later. Thanks for you appreciation! 😆

[bytemain]

their position are different, so I think it's better to add a new config.

If the wechat_subscriber and the reward are added through postBodyEnd, the two injection points overlap, so modify the implementation of the wechat_subscriber and the reward can be better, don't you think?

in my mind, I'd like to divide it into two files, because I have used postBodyEnd file to implement another func.
我觉得分成两个比较舒服... 因为我拿 postBodyEnd 当成了正文结束的提示。
如果不分我也是可以接受的，毕竟确实离得近了，调整下顺序的问题。

[jiangtj]

in my mind, I'd like to divide it into two files, because I have used postBodyEnd file to implement another func.

你可以试试通过优先级确认前后位置。
You can try to confirm the position before and after by priority. default is 10.

[jiangtj]

And the same injection point supports injecting multiple layouts, not just one. Just make sure the name of the injection is different.

[bytemain]

我原来是直接改 copyright 来实现的，今天发现了可以自定义注入，于是加了这一块。
主要是因为我是用 CI 来生成博客的，所以更新 next 得我手动同步合并最新的 next 主题代码然后推到我自己的仓库， CI 从我的仓库拉取 Next 主题的代码。。。

现在这么改确实有点不太 elegant，不太 next....

[stevenjoezhang]

iissnan/hexo-theme-next#1667

[bytemain]

iissnan/hexo-theme-next#1667

我是从这hexo-theme-yelee 抄来的~

作者demo: http://moxfive.xyz/2016/06/14/duoshuo-disqus-comment-count/#footer

[bytemain]

Cool, could you share your custom swig? We can add it to Awesome-NexT.

https://gist.github.com/lengthmin/e5250848c6b2437a392d9d1411a0fbd6

Gist

post-copyright

post-copyright. GitHub Gist: instantly share code, notes, and snippets.

[jiangtj]

Anyway, thanks for your time. And pointBodyEnd and postCopyright are similar, I refactor in #980. (本来想过段时间再弄得QwQ，I thought about it for a while QwQ.)

[bytemain]

Thanks to @jiangtj , This PR isn't elegant,
see #980 (comment)

[jiangtj]

Looking forward to your PR In Awesome NexT，for better post-copyright next plugin.