From 335fee9b2abbb6271c09488bd55fb2162a53e3c8 Mon Sep 17 00:00:00 2001 From: wc <78423238+de-soot@users.noreply.github.com> Date: Mon, 10 Feb 2025 12:53:30 +0800 Subject: [PATCH 1/2] Edited blog post --- _posts/2024-05-24-giscus-comments.md | 4 ++-- _site/feed.xml | 6 +++--- _site/giscus-comments.html | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/_posts/2024-05-24-giscus-comments.md b/_posts/2024-05-24-giscus-comments.md index ea82b9b..27438c5 100644 --- a/_posts/2024-05-24-giscus-comments.md +++ b/_posts/2024-05-24-giscus-comments.md @@ -10,7 +10,7 @@ I added a commenting feature for the blog using [giscus][giscus]. Basically, it # Try it -You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the repository's Github Discussions directly and it will show up on the comments section on the website similarly. +You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the [repository's Github Discussions](https://github.com/de-soot/de-soot.github.io/discussions) directly and it will show up on the comments section on the website similarly. # Add it to your own Github Pages website @@ -24,7 +24,7 @@ You can test it out yourself on this blog post in the comments below by signing Giscus finds and links the comments to the Github Discussions by searching through and matching URLs, path names, titles, and other such metadata. If you try to change a page's title without editing the associated Github Discussion accordingly, it may lead to giscus not being able to find and link it to the Github Discussion (this is especially noticible if you set the `]]> \ No newline at end of file diff --git a/_site/giscus-comments.html b/_site/giscus-comments.html index 5e142ca..030e196 100644 --- a/_site/giscus-comments.html +++ b/_site/giscus-comments.html @@ -51,7 +51,7 @@

Comments on Github Pages

Try it

-

You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the repository’s Github Discussions directly and it will show up on the comments section on the website similarly.

+

You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the repository’s Github Discussions directly and it will show up on the comments section on the website similarly.

Add it to your own Github Pages website

@@ -65,7 +65,7 @@

Note

Giscus finds and links the comments to the Github Discussions by searching through and matching URLs, path names, titles, and other such metadata. If you try to change a page’s title without editing the associated Github Discussion accordingly, it may lead to giscus not being able to find and link it to the Github Discussion (this is especially noticible if you set the <script>’s data-strict attribute value to "1"), and hence Giscus will create a new Github Discussion.

-

Giscus also only creates Discussions when someone comments, so it is easier to go back and edit to fix some things on your post if you do not have any comments yet rather than when your post already has comments in its own Discussion and you have to manually copy across those changes.

+

Giscus also does not update or sync the posts made on Github Discussions with the blogs on your website, so you may have to manually copy across the changes and edits you make to your blog posts. Luckily, giscus only creates a post on Discussions when there is interaction (reactions or comments) with giscus on your blog post, so it should not be an issue for new blog posts that no one has commented or reacted to yet.

From 7c1d255322cc7926ac537c0755b8ab0b9f83353f Mon Sep 17 00:00:00 2001 From: wc <78423238+de-soot@users.noreply.github.com> Date: Mon, 10 Feb 2025 12:57:44 +0800 Subject: [PATCH 2/2] Edited blog post --- _posts/2024-05-24-giscus-comments.md | 2 +- _site/feed.xml | 4 ++-- _site/giscus-comments.html | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/_posts/2024-05-24-giscus-comments.md b/_posts/2024-05-24-giscus-comments.md index 27438c5..840f914 100644 --- a/_posts/2024-05-24-giscus-comments.md +++ b/_posts/2024-05-24-giscus-comments.md @@ -10,7 +10,7 @@ I added a commenting feature for the blog using [giscus][giscus]. Basically, it # Try it -You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the [repository's Github Discussions](https://github.com/de-soot/de-soot.github.io/discussions) directly and it will show up on the comments section on the website similarly. +You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the [Github Discussions post](https://github.com/de-soot/de-soot.github.io/discussions/22) directly and it will show up on the comments section on the website similarly. # Add it to your own Github Pages website diff --git a/_site/feed.xml b/_site/feed.xml index 42f35ce..5b18185 100644 --- a/_site/feed.xml +++ b/_site/feed.xml @@ -1,4 +1,4 @@ -Jekyll2025-02-10T12:53:17+08:00http://localhost:4000/feed.xmlde_sootHosted on Github PagesGuide to APA with groff ms and refer2025-02-07T00:00:00+08:002025-02-07T00:00:00+08:00http://localhost:4000/groff-apaThis guide explains why and how I used groff with the ms and refer macros to write my college essay in Neovim.

+Jekyll2025-02-10T12:57:35+08:00http://localhost:4000/feed.xmlde_sootHosted on Github PagesGuide to APA with groff ms and refer2025-02-07T00:00:00+08:002025-02-07T00:00:00+08:00http://localhost:4000/groff-apaThis guide explains why and how I used groff with the ms and refer macros to write my college essay in Neovim.

Table of Contents

@@ -632,7 +632,7 @@ join-authors " & " ", " " & " # Change default "and" to ampersand (&

Try it

-

You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the repository’s Github Discussions directly and it will show up on the comments section on the website similarly.

+

You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the Github Discussions post directly and it will show up on the comments section on the website similarly.

Add it to your own Github Pages website

diff --git a/_site/giscus-comments.html b/_site/giscus-comments.html index 030e196..9fb4ffe 100644 --- a/_site/giscus-comments.html +++ b/_site/giscus-comments.html @@ -51,7 +51,7 @@

Comments on Github Pages

Try it

-

You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the repository’s Github Discussions directly and it will show up on the comments section on the website similarly.

+

You can test it out yourself on this blog post in the comments below by signing into your Github account and commenting, or you can comment on the Github Discussions post directly and it will show up on the comments section on the website similarly.

Add it to your own Github Pages website