chore: add AI attribution governance blog post and projects page

[shenxianpeng]

Summary

Updates the website to reflect the latest ecosystem updates across the commit-check organization.

Changes

1. New blog post — AI Attribution Governance: Enforcing AI Disclosure Policies at the CI Level

   • Covers commit-check v2.11.0's new AI attribution governance feature
   • Industry background (Linux kernel, Python discourse, etc.)
   • Configuration guide, signature database, false-positive prevention
   • Ecosystem integration status

2. New Projects page (docs/projects.md)

   • Clear overview of all three repos (commit-check, commit-check-action, commit-check-mcp)
   • Latest versions and feature highlights
   • Quick-reference table for what to use when

3. Home page improvement (docs/index.md)

   • Added Ecosystem module with project cards and version badges
   • Links to new Projects page

4. Navigation (mkdocs.yml)

   • Added Projects tab to the top nav bar

Preview

Build passes with mkdocs build --strict.

Summary by CodeRabbit

• New Features

  • Added a new Projects page and navigation entry to showcase the Commit Check ecosystem.
  • Expanded the site with an ecosystem overview linking the core product, GitHub Action, and MCP server.

• Documentation

  • Published a new blog post about AI attribution governance, including policy settings, enforcement behavior, examples, and setup guidance.
  • Added project cards, release highlights, and quick links to help users find the right tool and docs faster.

[netlify]

✅ Deploy Preview for commit-check-github-io ready!

Name	Link
🔨 Latest commit	716c7ad
🔍 Latest deploy log	https://app.netlify.com/projects/commit-check-github-io/deploys/6a4c145cf7c2b10008b0e992
😎 Deploy Preview	https://deploy-preview-11--commit-check-github-io.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Warning

Review limit reached

@shenxianpeng, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 892c7334-ab36-4ba1-8a19-8314247a5515

📥 Commits

Reviewing files that changed from the base of the PR and between 0287bb7 and 716c7ad.

📒 Files selected for processing (3)

• docs/blog/posts/ai-attribution-governance.md
• docs/projects.md
• mkdocs.yml

📝 Walkthrough

Walkthrough

Adds documentation: a blog post on AI Attribution Governance, a new "Ecosystem" section on the homepage, a new Projects landing page describing three Commit Check components with a Mermaid diagram and tables, and a corresponding mkdocs navigation entry.

Changes

Documentation Additions

Layer / File(s)	Summary
AI attribution governance blog post docs/blog/posts/ai-attribution-governance.md	Adds a blog post covering CI enforcement of commit-message AI disclosure policy, configuration modes, detection patterns, false-positive prevention, and integration points.
Projects landing page docs/projects.md	Adds a Projects page with a card grid for three components, a Mermaid diagram of how they relate, a release history table, and a quick links table.
Homepage ecosystem section docs/index.md	Adds an "Ecosystem" section with three product cards and a link to the new Projects page.
Navigation wiring mkdocs.yml	Adds a "Projects" entry to the mkdocs nav pointing to projects.md.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Sequence Diagram(s)

Not applicable; changes are documentation-only additions with no component interaction flow to visualize.

Suggested labels: blog

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main additions: an AI attribution governance blog post and a new projects page.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/add-blog-and-projects-page

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/blog/posts/ai-attribution-governance.md`:
- Around line 145-153: The rollout description is overstating GitHub Action
availability in the feature list. Update the “GitHub Action” bullet in the AI
attribution section of the blog post so it clearly indicates the support is
pending or gated by an upstream dependency update, rather than implying it is
already fully available. Keep the wording consistent with the surrounding
availability bullets and the existing commit-check-action reference.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b3ae0bdb-3ede-4f03-ba7d-4ff63eb8aba6

📥 Commits

Reviewing files that changed from the base of the PR and between 932f8b0 and 0287bb7.

📒 Files selected for processing (4)

• docs/blog/posts/ai-attribution-governance.md
• docs/index.md
• docs/projects.md
• mkdocs.yml