``` ### 在每篇文章末端加上讚賞鍵打開 `themes/next/layout/_macro/post.swig` 在合適的位置把 `like_coin.ejs` 放置好 ``` {% if theme.related_posts.enable and (theme.related_posts.display_in_home or not is_index) %} + {% include '../_custom/like_coin.ejs' %} {% include '../_partials/post/post-related.swig' with { post: post } %} {% endif %} ``` 如果您沒有開啟相關文章的話，則加在往上幾行的 `{{ post.content }}` 後方 ``` {% else %} {% if post.type === 'picture' %} {{ post.content }} {% else %} {{ post.content }} + {% include '../_custom/like_coin.ejs' %} {% endif %} {% endif %} {% else %} {{ post.content }} + {% include '../_custom/like_coin.ejs' %} {% endif %}

``` 完成後就可以看到讚賞鍵出現在文章中。 ### 參考文章 > [在Hexo NexT增加like Button](https://blog.typeart.cc/%E5%9C%A8Hexo%20NexT%E5%A2%9E%E5%8A%A0like%20Button/) > [如何将Liker按钮集成到Hexo](https://hive.blog/cn/@aafeng/liker-hexo) > [藍圖重生（一）：給 Hexo 文章加上 LikeCoin 的贊賞鍵 > ](https://blog.mykeyvans.science/posts/add-likebutton-for-hexo.html) > [Hexo教學2 iframe(likecoin) > ](https://allem40306.github.io/blog/posts/183a/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.v2.like.co/zh/general-guides/dapp/creator/self-host/hexo-next.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.