InkIsle can now add comments and reactions to articles through Giscus or Waline. Interactions remain opt-in: when no provider is configured, the generated site loads no third-party interaction resources.
\nBoth providers are integrated at the InkIsle renderer boundary, so the built-in personal and business-blog themes expose the same behavior.
An article can declare a permanent interaction identifier:
\ninteractionId: permanent-article-id\ncomments: true\nreactions: true\nProviders use interactionId, rather than the public URL, to find the article discussion. Existing comments therefore survive title, slug, locale-prefix, deployment-base, and domain changes as long as the identifier remains stable.
Translated articles can share one discussion or keep separate discussions per language. An article can also set comments: false to remove the complete interaction section or reactions: false to keep comments without reactions.
The InkIsle site runs on GitHub Pages and uses Giscus to store article interactions in the InkIsle Blog Discussions category of YGM-Studio/inkisle. Chinese and English translations share a discussion, and the Giscus interface follows the site’s light and dark themes.
We also maintain two independent npm canaries. Neither references the source workspace: each installs a pinned npm release and validates it through a separate repository and GitHub Pages workflow.
\nTheir ownership boundaries, external data, and release update workflow are documented in Canary Sites.
\nThis article is also a long-running public acceptance page. Leave feedback below to help us keep validating loading, sign-in, replies, and reactions in a real deployment.
\n","date_published":"2026-07-12T00:00:00.000Z","date_modified":"2026-07-12T00:00:00.000Z","tags":["Interactions","Giscus","Waline"],"language":"en"},{"id":"https://ygm-studio.github.io/inkisle/posts/comments-and-reactions/","url":"https://ygm-studio.github.io/inkisle/posts/comments-and-reactions/","title":"InkIsle 现已支持点赞与留言","summary":"通过 Giscus 或 Waline 为静态文章加入点赞和留言，同时保持构建过程完全静态。","content_html":"InkIsle 现在可以通过 Giscus 或 Waline 为文章提供点赞与留言。互动功能仍然是可选的：没有配置 Provider 时，构建结果不会加载任何第三方互动资源。
\n两个 Provider 都由 InkIsle 的 renderer 统一接入，内置的 personal 和 business-blog 主题会保持相同的行为。
文章可以显式设置永久互动标识：
\ninteractionId: permanent-article-id\ncomments: true\nreactions: true\nProvider 使用 interactionId，而不是公开 URL，来查找文章对应的讨论。修改标题、slug、语言前缀、部署子路径或域名时，只要保留这个标识，原有留言就不会丢失。
翻译文章可以共用一个讨论，也可以按语言分开。文章还可以通过 comments: false 关闭完整互动区域，或者通过 reactions: false 只保留留言。
InkIsle 官方站运行在 GitHub Pages 上，使用 Giscus 把文章互动保存到 YGM-Studio/inkisle 的 InkIsle Blog Discussions 分类。中英文翻译共用讨论，明暗主题切换也会同步到 Giscus。
我们还维护了两个独立 npm canary。它们都不引用源码工作区，而是从 npm 安装固定版本，再通过各自的仓库和 GitHub Pages 工作流验证发布包：
\n两个站点的维护边界、数据归属和版本升级流程记录在Canary Sites中。
\n这篇文章本身就是长期运行的公开验收页面。你可以在下方留下反馈，帮助我们继续验证真实环境下的加载、登录、回复和 reaction 体验。
\n","date_published":"2026-07-12T00:00:00.000Z","date_modified":"2026-07-12T00:00:00.000Z","tags":["Interactions","Giscus","Waline"],"language":"zh"},{"id":"https://ygm-studio.github.io/inkisle/en/posts/configuration/","url":"https://ygm-studio.github.io/inkisle/en/posts/configuration/","title":"Configuration","summary":"Use inkisle.config.mjs to configure identity, themes, locales, base paths, and outputs.","content_html":"InkIsle runs with defaults, but real sites usually add inkisle.config.mjs at the project root.
export default {\n title: "My Site",\n description: {\n zh: "我的内容站",\n en: "My content site"\n },\n site: "https://example.com",\n theme: {\n name: "business-blog",\n defaultMode: "system",\n allowUserToggle: true\n }\n};\ntitle and description drive page metadata, homepage copy, feeds, and llms.txt.locales and defaultLocale control multilingual content directories.theme.name selects personal or business-blog.base supports subpath deployments such as /inkisle.interactions can opt into Waline or Giscus; no third-party comment script loads by default.pwa, analytics, verificationFiles, and redirects handle browser integration, analytics, verification files, and migration redirects.base changes browser-facing URLs. It does not change Markdown paths or the generated file layout.
GitHub Pages project sites usually live under a repository subpath, such as https://ygm-studio.github.io/inkisle/. Configure both site and base for that shape.
export default {\n site: "https://ygm-studio.github.io",\n base: "/inkisle"\n};\nAfter build, asset links, search index requests, RSS, JSON Feed, llms.txt, and sitemap URLs include the /inkisle/ prefix.
The InkIsle website builds site/dist with GitHub Actions and deploys it to Pages. You can use the same pattern:
npm run build\nnpm run check:links\nIf you use a custom root domain, omit base or set it to /.
The default InkIsle project is content-only. You maintain content/, optional public/, and optional inkisle.config.mjs; the renderer and Astro internals stay inside the InkIsle package.
npm exec inkisle -- init my-site\ncd my-site\nnpm install\nnpm run dev\nnpm exec inkisle -- new post "First post"\nnpm exec inkisle -- new page "About"\nDefault-language content lives in content/posts/ and content/pages/. English translations can live in content/en/posts/ and content/en/pages/.
npm run build\nnpm run check\nnpm run check:links\nThese commands build the static site, run Astro diagnostics, and check generated internal links.
\n","date_published":"2026-05-17T00:00:00.000Z","date_modified":"2026-05-17T00:00:00.000Z","tags":["Quick Start","CLI"],"language":"en"},{"id":"https://ygm-studio.github.io/inkisle/en/posts/roadmap/","url":"https://ygm-studio.github.io/inkisle/en/posts/roadmap/","title":"Roadmap","summary":"InkIsle is alpha software focused on content shape, theme boundaries, and deployment quality.","content_html":"InkIsle is still alpha software. The current priority is a solid Markdown publishing workflow, not a full CMS.
\npersonal and business-blog themes.llms.txt.InkIsle is not trying to become a server runtime, login system, hosted comment service, or admin backend. It stays static-first, with Markdown as the source of truth.
\n","date_published":"2026-05-17T00:00:00.000Z","date_modified":"2026-05-17T00:00:00.000Z","tags":["Roadmap","Alpha"],"language":"en"},{"id":"https://ygm-studio.github.io/inkisle/posts/quick-start/","url":"https://ygm-studio.github.io/inkisle/posts/quick-start/","title":"快速开始","summary":"用几条命令创建一个只需要维护 Markdown 的 InkIsle 内容站。","content_html":"InkIsle 的默认项目是 content-only 形态。你维护 content/、可选的 public/ 和 inkisle.config.mjs，渲染器和 Astro 细节留在 InkIsle 包里。
npm exec inkisle -- init my-site\ncd my-site\nnpm install\nnpm run dev\nnpm exec inkisle -- new post "第一篇文章"\nnpm exec inkisle -- new page "关于"\n主语言内容放在 content/posts/ 和 content/pages/。英文翻译可以放在 content/en/posts/ 和 content/en/pages/。
npm run build\nnpm run check\nnpm run check:links\n这些命令会生成静态站点、运行 Astro 检查，并确认构建产物里的内部链接没有断掉。
\n","date_published":"2026-05-17T00:00:00.000Z","date_modified":"2026-05-17T00:00:00.000Z","tags":["Quick Start","CLI"],"language":"zh"},{"id":"https://ygm-studio.github.io/inkisle/posts/roadmap/","url":"https://ygm-studio.github.io/inkisle/posts/roadmap/","title":"路线图","summary":"InkIsle 目前处于 alpha 阶段，优先打磨内容模型、主题边界和部署体验。","content_html":"InkIsle 仍处于 alpha 阶段。当前重点是把 Markdown 发布的基础体验做扎实，而不是急着扩展成完整 CMS。
\npersonal 和 business-blog 两个内置主题。llms.txt 等机器友好输出。InkIsle 暂时不追求服务端运行时、登录系统、评论托管或复杂后台管理。它会保持静态优先，让内容源文件继续是 Markdown。
\n","date_published":"2026-05-17T00:00:00.000Z","date_modified":"2026-05-17T00:00:00.000Z","tags":["Roadmap","Alpha"],"language":"zh"},{"id":"https://ygm-studio.github.io/inkisle/posts/deployment/","url":"https://ygm-studio.github.io/inkisle/posts/deployment/","title":"部署到 GitHub Pages","summary":"InkIsle 支持项目页子路径部署，适合托管在 GitHub Pages。","content_html":"GitHub Pages 项目页通常部署在仓库名子路径下，例如 https://ygm-studio.github.io/inkisle/。这种场景需要同时配置 site 和 base。
export default {\n site: "https://ygm-studio.github.io",\n base: "/inkisle"\n};\n构建后，页面里的资源、搜索索引、RSS、JSON Feed、llms.txt 和 sitemap 都会带上 /inkisle/ 前缀。
InkIsle 官网使用 GitHub Actions 构建 site/dist 并部署到 Pages。你也可以在自己的仓库里使用同样方式：
npm run build\nnpm run check:links\n如果使用自定义根域名，可以省略 base 或设置为 /。
InkIsle 的默认配置已经可以直接运行。需要定制时，在项目根目录添加 inkisle.config.mjs。
export default {\n title: "My Site",\n description: {\n zh: "我的内容站",\n en: "My content site"\n },\n site: "https://example.com",\n theme: {\n name: "business-blog",\n defaultMode: "system",\n allowUserToggle: true\n }\n};\ntitle 和 description 控制页面标题、首页文案、feed 和 llms.txt。locales 和 defaultLocale 控制多语言内容目录。theme.name 可以选择 personal 或 business-blog。base 用于 GitHub Pages 这类子路径部署，例如 /inkisle。interactions 可按需接入 Waline 或 Giscus，默认不会加载第三方评论脚本。pwa、analytics、verificationFiles 和 redirects 处理浏览器集成、统计、搜索验证文件和迁移跳转。base 只影响浏览器可访问 URL，不改变 Markdown 内容路径，也不改变构建目录里的文件结构。