Clean up mkdocs.yml site settings

[bharvey88]

repo_title is not an mkdocs configuration option, so every build logs Config value 'repo_title': Unrecognised configuration name. The header link tooltip comes from repo_name. Removing the line silences the warning without changing the rendered site.

---

Expanded into a small mkdocs.yml settings cleanup (one commit each):

• Set site_url to https://kno.wled.ge. It was commented out (and pointed at wled.app), so builds emit relative canonical links and a sitemap.xml without real absolute URLs. With it set, canonical tags and the sitemap point at the live site.
• Update repo_url and edit_uri to the current wled organization casing (the project moved from Aircoookie to wled).
• Re-enable the footer copyright notice, which was commented out and frozen at 2016-2021. The config string now uses {year}, substituted with the build year by a small override of the theme's copyright partial, so it stays current automatically on every deploy.

Verified with a local build: canonical URLs and sitemap point at kno.wled.ge, footer shows "Copyright (c) 2016-2026", and no config warnings remain.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 41 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c257e615-365e-4a76-8e73-9141a2a0617f

📥 Commits

Reviewing files that changed from the base of the PR and between 1583203 and 098a574.

📒 Files selected for processing (2)

• docs/assets/overrides/partials/copyright.html
• mkdocs.yml

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code

---

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