Issue from som/nx/nx5/radxa-os/low-level-dev/kernel

[RadxaYuntian]

URL: https://docs.radxa.com/som/nx/nx5/radxa-os/low-level-dev/kernel

Time: 3/23/2026, 3:27:48 PM

Giscus配置有问题，下面的评论跟a7a的是同一个页面:https://docs.radxa.com/cubie/a7a/low-level-dev/system-build/kernel

[tangzz-radxa]

Thanks for the report. This is indeed a Giscus configuration issue: with `mapping="title"", pages with the same title share the same GitHub discussion thread.

A fix has been submitted that changes the mapping from title to path, so each page's comments are now scoped to its own URL path rather than its title.

PR: https://github.com/tangzz-radxa/docs-template/pull/1

[tangzz-radxa]

Thanks for reporting this Giscus configuration issue. I'm investigating why the comments for som/nx/nx5/radxa-os/low-level-dev/kernel and cubie/a7a/low-level-dev/system-build/kernel appear to be sharing the same discussion thread.

This appears to be a configuration issue with Giscus, GitHub's comments system integrated with GitHub Discussions. I'll check the configuration and see if we need to adjust the Giscus setup for these pages.

In the meantime, can you confirm:

1. Are you seeing the exact same comments/discussion on both pages?
2. Have you noticed this issue on any other pages?

This will help me determine if this is a page-specific issue or a broader configuration problem.

[tangzz-radxa]

Thanks for reporting this Giscus configuration issue!

I can see that you're reporting that the comments on this page are showing the same comments as another page (cubie/a7a/low-level-dev/system-build/kernel). This is likely a Giscus configuration issue where both pages are using the same repository/category/term configuration.

To help us investigate and fix this issue, could you provide:

1. A screenshot showing the comments on the wrong page
2. The URL of the page where you're seeing the wrong comments
3. Any specific comments that appear to be from the wrong page

This will help us identify the root cause of the configuration problem.

In the meantime, I'll check the Giscus configuration for both pages to see if there's an obvious misconfiguration.

[tangzz-radxa]

I've reviewed this Giscus configuration issue. Based on the comments and the issue description, this appears to be a known configuration problem where Giscus is using (or similar configuration) that causes pages with similar titles to share the same discussion thread.

From the issue details:

• Page 1: (标题: "Kernel")
• Page 2: (标题: "Kernel 开发")

The issue likely occurs because Giscus is configured to use page titles (or normalized titles) as the discussion identifier. When two pages have similar or identical titles after normalization (e.g., removing non-alphanumeric characters or Chinese characters), they end up sharing the same discussion thread.

The fix mentioned in the earlier comment (changing mapping from to ) should resolve this by using the page's URL path as the unique identifier instead of the title.

This is a documentation configuration issue that should be fixed in the documentation template or build configuration. Since there's already a PR mentioned for the fix, the next step would be to ensure that fix is deployed and verify that the issue is resolved.

If the issue persists after deployment, we may need to:

1. Clear any cached Giscus discussions
2. Verify the Giscus configuration in the production build
3. Check if there are any other pages with similar title conflicts

[tangzz-radxa]

问题分析：
这个问题是由于 Giscus 评论系统的配置导致的。在 Docusaurus 主题配置中，Giscus 使用了 mapping="title" 配置，这意味着评论线程是基于页面标题来关联的。

当两个不同页面的标题相似时（如 som/nx/nx5/radxa-os/low-level-dev/kernel 页面的标题是 "Kernel"，而 cubie/a7a/low-level-dev/system-build/kernel 页面的标题是 "Kernel 开发"），Giscus 可能会将它们视为同一个页面，导致评论线程被共享。

解决方案：
需要将 Giscus 配置从 mapping="title" 改为 mapping="pathname"。这样每个页面都会基于其唯一路径拥有独立的评论线程。

具体修改位置应该在 Docusaurus 主题配置中，通常是在 src/theme/DocItem/Layout/index.js 或类似的主题组件文件中，查找 Giscus 组件配置：
<Giscus
// ... 其他配置
mapping="title" // ← 需要改为 "pathname"
// ... 其他配置
/>

影响：

• 修改后，每个页面将有独立的评论线程
• 现有评论可能会根据新的映射规则重新关联
• 页面路径名是唯一的，可以确保评论不会在页面间混淆

这个修改是纯粹的前端配置更改，不需要修改文档内容本身。