Reorder blog post footer to render Share/Author before Giscus comments

[Copilot]

Description

On blog post pages, the comment box was rendering before the social share section and author card. This updates the render order so Share this post and the author card appear first, with Giscus comments rendered after them.

Type of Change

• New feature (e.g., new page, component, or functionality)
• Bug fix (non-breaking change that fixes an issue)
• UI/UX improvement (design, layout, or styling updates)
• Performance optimization (e.g., code splitting, caching)
• Documentation update (README, contribution guidelines, etc.)
• Other (please specify):

Changes Made

• Blog-only Giscus gating
  • Added route-aware behavior in src/components/giscus.tsx to suppress default inline MDX rendering on /blog/* unless explicitly forced.
• Footer-controlled comment placement
  • Updated src/theme/BlogPostItem/Footer/index.tsx to render <GiscusComments forceRender /> at the end of the blog footer wrapper, after social share and author card.
• Duplicate embed prevention
  • This avoids double comment mounts on blog pages by ensuring only the footer-owned instance renders there.

// src/components/giscus.tsx
if (isBlogPostPage && !forceRender) {
  return null;
}

// src/theme/BlogPostItem/Footer/index.tsx
{isBlogPostPage && <GiscusComments forceRender />}

Dependencies

• No new dependencies.
• No dependency version changes.

Checklist

• My code follows the style guidelines of this project.
• I have tested my changes across major browsers and devices
• My changes do not generate new console warnings or errors .
• I ran npm run build and attached screenshot(s) in this PR.
• This is already assigned Issue to me, not an unassigned issue.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
recode-website	Ready	Preview, Comment	May 22, 2026 3:25pm