mirror of
https://github.com/andwati/andwati-nextgen.git
synced 2026-11-02 20:02:16 +00:00
andwati
63007a1c09
- Port adammaj.com layout, sidebar and 3D bookshelf from Chakra to Tailwind v4, matched to measured pixel values - Pages: About, Writing, Reading (bookshelf), Portfolio; content exported to markdown with YAML frontmatter, KaTeX math, callouts and YouTube embeds - Shiki (github-light) code highlighting via rehype-pretty-code - SEO: per-page metadata and canonicals, JSON-LD, generated OG images, sitemap, robots, RSS/JSON feeds, llms.txt - Umami analytics via PUBLIC_UMAMI_SCRIPT_URL / PUBLIC_UMAMI_WEBSITE_ID - Prettier + cspell for content, husky/lint-staged pre-commit hook - Multi-stage Dockerfile (Node 24, pnpm, standalone output) for Dokploy - Remove unused Chakra, emotion, framer-motion, posthog, next-seo and MDX deps
64 lines
2.6 KiB
Markdown
64 lines
2.6 KiB
Markdown
---
|
|
title: "What say you?"
|
|
description: "Adding a comment system by utterances"
|
|
date: "2023-08-24"
|
|
tags: ["blog", "utterances"]
|
|
---
|
|
|
|
Free speech enhanced
|
|
|
|
There is no point in writing online if your readers cannot provide feedback for your writings. You might as well be shouting at a void. My ideal commenting system has to be free, open source and should not be a hassle to setup. Luckily, [utterances 🔮](https://github.com/utterance/utterances) checks all of these conditions
|
|
|
|
It is a lightweight comments widget built on GitHub issues. Use GitHub issues for blog comments, wiki pages and more! The notable features are:
|
|
|
|
- Open source. 🙌
|
|
- No tracking, no ads, always free. 📡🚫
|
|
- No lock-in. All data stored in GitHub issues. 🔓
|
|
- Styled with Primer, the css toolkit that powers GitHub. 💅
|
|
- Dark theme. 🌘
|
|
- Lightweight. Vanilla TypeScript. No font downloads, JavaScript frameworks or polyfills for evergreen browsers. 🐦🌲
|
|
|
|
## How it works
|
|
|
|
When Utterances loads, the GitHub [issue search API](https://developer.github.com/v3/search/#search-issues) is used to find the issue associated with the page based on url, pathname or title. If it cannot find an issue that matches the page, [utterances-bot](https://github.com/utterances-bot) will automatically create an issue the first time someone comments.
|
|
|
|
To comment, users must authorize the utterances app to post on their behalf using the GitHub [OAuth flow](https://developer.github.com/v3/oauth/#web-application-flow). Alternatively, users can comment on the GitHub issue directly.
|
|
|
|
# Setting up Utterances
|
|
|
|
### Repository
|
|
|
|
Choose the repository utterances will connect to.
|
|
|
|
Make sure the repo is public, otherwise your readers will not be able to view the issues/comments.
|
|
Make sure the utterances app is installed on the repo, otherwise users will not be able to post comments.
|
|
If your repo is a fork, navigate to its settings tab and confirm the issues feature is turned on.
|
|
|
|
```
|
|
repo:
|
|
username/repo
|
|
```
|
|
|
|
A public GitHub repository. This is where the blog post issues and issue-comments will be posted.
|
|
|
|
### Theme
|
|
|
|
Choose an Utterances theme that matches your blog.
|
|
|
|
### Enable Utterances
|
|
|
|
Add the following script tag to your blog's template. Position it where you want the comments to appear. Customize the layout using the .utterances and .utterances-frame selectors.
|
|
|
|
```js
|
|
<script
|
|
src="https://utteranc.es/client.js"
|
|
repo="[ENTER REPO HERE]"
|
|
issue-term="title"
|
|
theme="gruvbox-dark"
|
|
crossorigin="anonymous"
|
|
async
|
|
></script>
|
|
```
|
|
|
|
The complete documentation can be found at [https://utteranc.es](https://utteranc.es/)
|