QWER VS giscus

thanks grimdeath for reaching out. I actually started my project with this beautiful project, I'm wondering if it's possible to completely remove unocss without losing the wonderful ui ?

I am still actively developing QWER. I wrote lots of shitcodes 💩 in it. I am not ashamed to say it aloud. But, I promise you, I will keep learning and improving my skills along the way.

DEMO: https://svelte-qwer.vercel.app/

QWER is Simply Awesome Blog Starter built with Svelte and ❤. Provides out-of-the-box support for Atom feed, Sitemap, and PWA. Outstanding site performance and SEO support.

That project also has Github issues and discussions pages to ask questions and get help.

When creating my blog-centric personal portfolio, I had a goal of launching it as soon as possible. However, considering including a comment feature, the implementation process could be time-consuming. That's when I started looking for a solution that was easy to set up yet provided essential commenting functionalities. It was during this search that I stumbled upon Giscus.

But now, a new fellow named giscus commenting system has entered the town, it's basically powered by github. Since I already host my blog on github pages, this should be a natural choice for me, right? Many bloggers seem to be migrating to this new system and I might too soon. The downsides however are as follows:

Get Giscus here.

Supports Giscus - a comments system powerd by Github Discussions.

I've encountered https://github.com/utterance/utterances, which relies on github issues for providing a blog comments system of a sort.

Alternatively there's https://github.com/giscus/giscus, which instead uses github discussions.

Haven't used either so can't comment (heh) on their "performance".

There's also a recent similar tool called https://github.com/giscus/giscus that uses Github Discussions as the backing system, rather than Issues.