docs: add Google Analytics and a descriptive home page title

[shenxianpeng]

These docs are served from the cpp-linter.github.io origin, but unlike the organization site they have no Google Analytics. So there is no record of what readers look at once they leave the organization's home page. In Search Console these pages had 317 impressions for the home page alone in three weeks, plus inputs-outputs, pr-review-caveats and examples. This PR adds the same property the organization site uses (G-JKH4SXC7HC). It also adds the maintainer flag from cpp-linter/cpp-linter.github.io#83, so the maintainers' own reading can be filtered out.

This PR only changes the site. The Google Analytics side (the Internal Traffic filter, key events) is handled separately.

Before / After (改动前 / 改动后)

	Before (live site, origin/main)	After (this branch, mkdocs build --strict)
Google Analytics	No gtag on any page	G-JKH4SXC7HC on every page
Maintainer visits	—	traffic_type=internal while the cpp-linter-internal flag is set (?internal=1 / ?internal=0 on any page of the origin)
Home page <title>	C/C++ Linter Action	clang-format and clang-tidy GitHub Action - C/C++ Linter Action
Home page meta description	Developer documentation from sources.	Run clang-format and clang-tidy on the C/C++ files a pull request changes, with annotations, review suggestions and a thread comment.
404 page <title>	C/C++ Linter Action (same as the home page)	Page not found - C/C++ Linter Action
docs/overrides/ in the built site	—	Not published (exclude_docs)

Search Console showed this page at an average position of 8.3 with a 0.6% click-through rate. Its title was only the site name, and the description was "Developer documentation from sources."

Evidence: built <head> of index.html

<script>
  try {
    var param = new URLSearchParams(location.search).get("internal");
    if (param === "1") localStorage.setItem("cpp-linter-internal", "1");
    if (param === "0") localStorage.removeItem("cpp-linter-internal");
    if (localStorage.getItem("cpp-linter-internal") === "1") {
      window.dataLayer = window.dataLayer || [];
      (function () { dataLayer.push(arguments); })("set", { traffic_type: "internal" });
    }
  } catch (e) {
    // localStorage is unavailable when storage is blocked; the visit is then not tagged.
  }
</script>
<script id="__analytics">function __md_analytics(){ /* … the theme's snippet, unchanged … */ var t=document.createElement("script");t.async=!0,t.src="https://www.googletagmanager.com/gtag/js?id=G-JKH4SXC7HC",document.getElementById("__analytics").insertAdjacentElement("afterEnd",t)}</script>

The flag script comes before id="__analytics" (character 1605 vs 1999 in the built index.html). The same order holds on inputs-outputs/index.html and 404.html.

Notes

• The flag snippet runs in the theme's analytics block, before the theme's own snippet. That way gtag('set', {traffic_type: 'internal'}) is queued ahead of the first page_view. The same snippet was tested end to end with the real gtag.js and a fake measurement ID in feat: tag maintainer visits, track code copies and add social cards cpp-linter.github.io#83: tt=internal is sent after ?internal=1 and stops after ?internal=0.
• None of these changes alters a page's layout, so there are no screenshots.
• cspell.config.yml gains htmltitle (a Jinja block name in docs/overrides/404.html).

Summary by CodeRabbit

• Documentation
  • Updated the documentation landing page with a clearer title and a summary of the action’s pull-request checks and outputs.
  • Added a custom “Page not found” page to help visitors identify missing documentation pages and return to the site.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 26f452ab-5354-49d1-9708-3a329d074e4d

📥 Commits

Reviewing files that changed from the base of the PR and between f71829c and 0ea91e2.

📒 Files selected for processing: 5

• cspell.config.yml
• docs/index.md
• docs/overrides/404.html
• docs/overrides/main.html
• mkdocs.yml

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

Walkthrough

The documentation changes configure MkDocs metadata, theme overrides, Google Analytics, and internal-traffic tracking. The home page gains a title and description. A 404 page and a template for handling the internal query parameter are added.

Changes

Documentation Site and Analytics

Layer / File(s)	Summary
Configure documentation pages and analytics mkdocs.yml, docs/index.md	MkDocs excludes the overrides directory from documentation pages, uses it as the theme custom directory, and configures Google Analytics. The home page gains a title and description.
Add theme overrides and internal-traffic tracking docs/overrides/*, cspell.config.yml	The overrides add a 404 page and update the internal-traffic flag from the query parameter. When analytics is configured and the flag is set to 1, the template queues the internal traffic setting before the parent analytics block. The spelling list adds htmltitle.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 0ea91

The PR adds documentation metadata and Google Analytics with an internal-traffic flag; the Material override preserves analytics output. No actionable merge-blocking risk remains.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly identifies the main changes: adding Google Analytics and a descriptive home page title. It is concise and specific.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (5 skipped: 5 unsupported.)

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}