mirror of
https://github.com/4gray/iptvnator.git
synced 2026-10-11 11:06:16 -08:00
4grayandClaude Fable 5.1
fd963bb0c5
The published post was the raw release-notes scaffold: 42 feature and 76 fix bullets in area-prefixed inventory form, with the four highlight sections buried after the feature list. Rework it into the v0.22 shape: a "What changed" table, the four highlights first and expanded, themed improved/fixed sections with one-line entries, and the long tail of fixes under a Spoiler. Every PR/issue reference from the original is preserved; open text drops from 6.7k to 3.4k words. Spoiler.astro sits inside `not-prose`, so lists rendered without markers and links in body colour; give its content list, link, strong and code styling so grouped lists inside it read like the rest of the post. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
IPTVnator Website
The website is an Astro static site deployed to GitHub Pages at https://4gray.github.io/iptvnator/.
Blog Comments
Blog posts render Giscus comments from apps/website/src/components/GiscusComments.astro.
Giscus stores comments in GitHub Discussions for 4gray/iptvnator and maps each page to a discussion by pathname, including the GitHub Pages base path such as /iptvnator/blog/why-external-players-help/.
The embed is wired to the dedicated Blog comments discussion category:
- Repository id:
MDEwOlJlcG9zaXRvcnkyMTMxOTQ3Mzg= - Category id:
DIC_kwDODLUX8s4C9eBJ - Mapping:
pathname - Theme:
transparent_dark
If the category is recreated, query the new category id:
gh api graphql \
-f owner=4gray \
-f name=iptvnator \
-f query='query($owner:String!, $name:String!) { repository(owner:$owner, name:$name) { discussionCategories(first:25) { nodes { id name slug isAnswerable } } } }'
Then update data-category-id in GiscusComments.astro.
Moderation happens in GitHub Discussions. Maintainers can hide, delete, lock, or move discussions and comments from the repository Discussions UI.