Skip to content

Conversation

@popey
Copy link
Contributor

@popey popey commented Jun 18, 2025

This adds the necessary configuration to allow visitors to comment on venues.
Visitors will need a GitHub account.

This adds the necessary configuration to allow visitors to comment on venues.
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jun 18, 2025

Deploying website with  Cloudflare Pages  Cloudflare Pages

Latest commit: 91f2aa5
Status: ✅  Deploy successful!
Preview URL: https://37b7261e.website-b3u.pages.dev
Branch Preview URL: https://enable-giscus.website-b3u.pages.dev

View logs

popey and others added 8 commits June 18, 2025 11:46
Snippet that will be used at the footer of pages to display comments, and the UI to add comments.
In theory this should add the giscus snippet to the bottom of pages.
Switch to using pathname rather than URL for discussion topic
@popey
Copy link
Contributor Author

popey commented Jun 18, 2025

@darkling WDYT?
Examples:

One gotcha is that the GitHub discussion threads end up with the duplicate content as the top post, "A global map of places to visit that might appeal to nerdy types" and the URL to the page. I'm not sure how much of a pain that is, as I imagine most "normies" will be leaving comments on the website itself, not here in the discussions tab on GitHub. 🤷

Also, people who do browse the discussions page on GitHub will see all discussions from us, and all the ones originating under venue pages. However, it's possible to filter those out with this: https://github.com/NerdyDayTrips/website/discussions?discussions_q=is%3Aopen+-category%3AVenues

@popey popey added the blocked Cannot land due to dependency on other issues/work label Nov 9, 2025
@popey popey self-assigned this Nov 9, 2025
@popey popey marked this pull request as draft November 9, 2025 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blocked Cannot land due to dependency on other issues/work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants