[CHORE] Use dark mode in the docs

[guibranco]

📑 Description

[CHORE] Use dark mode in the docs

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

☢️ Does this introduce a breaking change?

• Yes
• No

---

Summary by Sourcery

Enhancements:

• Align documentation theme configuration to consistently use the dark color scheme across the site.

Summary by CodeRabbit

• Chores
  • Updated the default color scheme for the documentation site to dark mode.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Switches the documentation site’s Just-the-Docs configuration to use dark color scheme by default instead of light.

File-Level Changes

Change	Details	Files
Change the Just-the-Docs Jekyll configuration to use dark mode as the default color scheme for the docs site.	Remove the earlier top-level color_scheme configuration entry to avoid conflicting settings. Set the main color_scheme configuration value to 'dark' instead of 'light' in the color scheme section. Keep all other documentation site settings (theme, URLs, favicon, etc.) unchanged.	docs/_config.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Rate limit exceeded

@guibranco has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 25 minutes and 5 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 25 minutes and 5 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 52e2cd19-0380-4975-85ea-1727e86dd861

📥 Commits

Reviewing files that changed from the base of the PR and between 2efb7c6 and 44d8474.

📒 Files selected for processing (1)

• docs/_config.yml

Walkthrough

The documentation site's default color scheme is updated from light to dark mode by modifying the docs/_config.yml configuration file. An earlier duplicate declaration is removed, and the active color scheme setting is changed to reflect the dark theme preference.

Changes

Cohort / File(s)	Summary
Documentation Configuration docs/_config.yml	Changed default color scheme from light to dark mode by updating the color\_scheme setting and removing duplicate declaration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🌙 The darkness calls, and we answer with glee,
Dark theme now graces the docs, can't you see?
From light into shadow, our sight finds relief,
A rabbit's small change brings the greatest belief! 🐰✨

🚥 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 and specifically summarizes the main change: updating the documentation theme to use dark mode, which aligns with the file-level changes showing the color scheme updated from light to dark.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch guibranco-patch-1

---

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 and usage tips.}

[penify-dev]

Failed to generate code suggestions for PR

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/_config.yml`:
- Around line 63-65: Update the section comment above the color_scheme setting
to reflect that the default theme is now dark: change the header text that
currently reads “Color scheme — light by default, toggle to dark” (near the
color_scheme key) to indicate “dark by default, toggle to light” or similar
phrasing so the comment matches the actual default value of color_scheme: dark.

🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e2f90a88-3bb3-44e9-868c-591bb09710f4

📥 Commits

Reviewing files that changed from the base of the PR and between 80df5b3 and 2efb7c6.

📒 Files selected for processing (1)

• docs/_config.yml

[github-actions]

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.

---

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check