> For the complete documentation index, see [llms.txt](https://docs.v2.like.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v2.like.co/general-guides/dapp/creator/self-host/jekyll.md). # Jekyll How to embed LikeCoin button into Jekyll {% hint style="warning" %} The documentation is designed for Liker Land and LikeCoin v2. For information on [3ook.com](https://3ook.com/) and LikeCoin v3, please visit [docs.3ook.com](https://docs.3ook.com) and [dao.like.co](https://dao.like.co/). {% endhint %} Thanks to the user [PinGuの独り言](https://pingu.moe/2020/01/integrate-likebutton-with-jekyll/) for providing the tutorial. Before adding the LikeCoin button, please [register a Liker ID](/general-guides/dapp/liker-id.md). Follow the steps below: ### Config liker\_id in \_config.yml Add `liker_id` in `_config.yml` and change \[LikerID] into your Liker ID. It should look like this: ``` # Enter your Liker ID to enable LikeCoin button liker_id: [LikerID] ``` Define the variables in `_config.yml`. The variables can be obtained in the site object using `{{site.liker_id}}` ``` https://button.like.co/in/embed/{{site.liker_id}}/button?referrer={{ page.url | absolute_url | cgi_escape }} ``` ### Insert the iframe Develop the LikeCoin button HTML and use the following code to insert the iframe: ``` {% if site.liker_id %} {% endif %} ``` Use if to inspect if `liker_id` exists. Then add the code to the post template, find a place near the end of the post template and add `{% include likeco.html %}` to include the LikeCoin button. Build the website, and the LikeCoin button will be added at the end of each article. However, the size may need adjustment. The LikeCoin button will adapt itself to a width of 485px and a height of 240px. Use the following code to align it to the middle and hide the scroll bar. ``` {% if site.liker_id %} {% endif %} ``` --- # 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/general-guides/dapp/creator/self-host/jekyll.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.