Friday, 26 August 2022

25 days ago

4 minutes read

  • Giscus
  • GitHub
  • Blog
  • Frontend
  • Open Source

Giscus is the key

Adding comments and reactions to a blog that was developed with a Static Site Generator (SSG) like Gatsby? Easy peasy lemon squeezy πŸ”₯ Wanna know how? Come around and have a look πŸ‘€

Tiago Sousa

Tiago Sousa

Software Engineer


Disclaimer: If took time to read this blog post and you have a GitHub account please react to this article πŸ˜ŠπŸ™

Whenever I have some time I like to improve my personal projects and enrich them as I can. This time the topic is my website.

I was going through my website and something crossed my mind right away! What if I added comments and reactions to my blog posts? πŸ€” I mean, comments aren't something that people often write in technical blog posts, unless they are really engaged with the author's content, and that's why I really like the reaction approach. With reactions and emojis you can express yourself regarding something very particular and this something can be a comment, a blog post, a photo ... well, an unlimited list of options could be inserted here.

After understanding that I wanted to implement this for my personal website, even if it doesn't have many views, I started to investigate some solutions that were available and, of course, as any Software Engineer I wanted to develop my own SaaS and provide an awesome development experience to whoever wanted to add comments or reactions to something but it would take time to be developed and time to maintain. Developing this SaaS is one of my objectives as a Software Engineer but it's a huge commitment that I dont want to take at this point in my life. But who knows in the future πŸ‘€

Please, have a look πŸ‘€link

Yes, Tiago... Now that you already talked about your 1 million dollar idea what about the result of the research that you did? Ouh yes.... sorry, I got distracted πŸ‘€ After my investigation I found a couple of really cool tools that I will list below as they can be a solution for you too:

... and last but not least:

Some of these tools are Software As A Service and others are open-source projects.

To be very honest with you, I don't mind paying for a SaaS but it has to fulfill and cover my needs and none of the available options was a suitable solution for me. Since I wanted to implement this as soon as possible I focused a little bit more on the open source community and utteranc looked very simple and promising but I dug even deeper and found giscus which was exactly what I was looking for!

Giscus is very inspired in utteranc but besides the fact that it allows you to install but including a <script /> tag it also has a nice wrapper for multiple frameworks like react, vue and svelte that you can install through npm or yarn.

But how utteranc and giscus save the data regarding the comments and reactions? The answer to that question was one of the reasons of why I chose this approach! They save the data directly in a GitHub repository, through the GitHub Discussions. Wait, you are saying that for my SSG website I can have all the reactions and comments for my articles saved on GitHub? What a dream 🀩

KISS 😘link

Yes, KISS, Keep It Simple Stupid!

As my website is mostly viewed by technical people within the IT sector I thought that signing in with GitHub would be really nice as everyone has a GitHub account! No need to get redirected to other services that you don't know or trust or even social media platforms! Keeping things within GitHub ecosystem looked like a good option.

But how can I do the same and implement it for my website? Well, I will try to make this step-by-step and as clean as possible!

GitHub Configurationlink

First of all, you need to have a public GitHub repository, which in my case wasn't a problem as my website is open source and everyone can see the codebase. After having a public repository you need to enable GitHub Discussions in the repository settings under the Features section.

GitHub Settings

Features Section

After enabling the GitHub Discussions you should be able to see a new tab called Discussions for your repository at the same level of the Settings like the image below:

Discussions Tab

Regarding GitHub configurations that's all! Now let's get to the code implementation

What about code changes?link

Code changes? You just need 3 minutes and that's depending on the package manager that you are using πŸ˜…

First of all, let's start by installing the giscus package for the framework/library that you are using. In my case, I will install the react package.

yarn add @giscus/react


npm i @giscus/react


if you are using vue or svelte just replace whatever is after @giscus/ to the framework that you are using e.g. yarn add @giscus/vue

Now go to the Configuration section in giscus and add your public repository name and choose the discussion category for the comments and reactions. Of course, there are more configurations that you can change, feel free to choose whatever suits you best!

If you scroll a little bit you will find a section called Enable giscus that will contain all the props that you need to add to your component like the image below:

Giscus Configuration Section

By the end of the configuration, you should have something very similar to this


import Giscus from '@giscus/react';
<Giscus id="comments" repo={YOUR_REPO_NAME_HERE} repoId={YOUR_REPO_ID_HERE} category={YOUR_CATEGORY_HERE} categoryId={YOUR_CATEGORY_ID_HERE} mapping={YOUR_MAPPING_STRATEGY} reactionsEnabled="1" emitMetadata="0" inputPosition="top" theme={YOUR_PREFERED_THEME} lang="en" loading="lazy" />

Everything is extremely customizable as you can see on the giscus website. Feel free to spend time having a look and trying the multiple available options that the tool offers.

But can you protect me a little bit?link

As you can imagine, everyone can have access to the values that you use to integrate Giscus with your GitHub discussions by doing what you just did! So what prevents me to add this to a random page and start spamming your discussions and populate them with random data?

For that, and that's why is very important to always read everything, you can add a giscus.json in your project root folder specifying the origins or even originsRegex like I have here.

This information is available in the giscus ADVANCED-USAGE.md documentation.


You are still here? Did you read this section? Damn! If you, react with a ❀️ to the article!

Finally, I will just add here a link to the PR where I made these changes. Feel free to read the Special notes for your reviewer in the PR description and you will understand how easy was to integrate giscus!

Anyways I hope you found this article interesting, feel free to share it with your colleagues or friends, because you know... Sharing is caring!

Also, if you enjoy working at a large scale in projects with global impact and if you enjoy a challenge, please reach out to us at xgeeks! We're always looking for talented people to join our team πŸ™Œ

Tiago Sousa

Written by Tiago Sousa

Hey there, my name is Tiago Sousa and I'm a Fullstack Engineer currently working at xgeeks. I'm a technology enthusiast and I try to explore new things to keep myself always updated. My motto is definitely "Sharing is caring" and that's exactly why you are currently reading this!

Interested in collaborating with me?

Let's Talk

All the rights reserved Β© Tiago Sousa 2022


Designed with love by Mauricio Oliveira