[codex] centralize plugin count

[ToriChanIntegration]

Summary

• Derive the public plugin count from the plugin registry instead of hardcoded marketing numbers.
• Reuse the shared count in footer, pricing, docs, about, alternatives, Appflow, and Capawesome copy.
• Remove stale plugin-count claims from older blog posts where a dynamic registry value is not available.

Why

The site had inconsistent plugin totals such as 20+, 30+, 90+, 100+, and 130+. The registry already knows the current count, so the display copy should use that single source where possible.

Validation

• bunx prettier --write <touched files>
• bun run check

Summary by CodeRabbit

• Refactor
  • Centralized plugin count configuration to be dynamically sourced from a single configuration value instead of hardcoded numbers across multiple pages and components, ensuring consistent and easily updatable plugin count information throughout the site.

[coderabbitai]

Warning

Rate limit exceeded

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

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: b1a9abd2-510d-48e6-8da6-18772401433e

📥 Commits

Reviewing files that changed from the base of the PR and between 3a4a6c9 and 9c3f174.

📒 Files selected for processing (1)

• AGENTS.md

📝 Walkthrough

Walkthrough

This PR introduces dynamic plugin count exports derived from the plugins array and replaces hardcoded plugin count references across pages, components, copy strings, and documentation with dynamic label interpolation.

Changes

Dynamic Plugin Count Implementation

Layer / File(s)	Summary
Source Definition apps/web/src/config/plugins.ts	Exports pluginCount computed from actions.length and pluginCountLabel formatted as ${pluginCount}+.
Re-exports apps/docs/src/config/plugins.ts	Re-exports pluginCount and pluginCountLabel alongside existing exports.
Message Templates apps/shared/copy/messages.ts	Replaces hardcoded counts ("100+", "over 90+", "over 20+") with {pluginCountLabel} placeholders in alternatives, appflow, capwesome, and footer messages.
Components apps/web/src/components/Footer.astro, apps/web/src/components/pricing/ComparePlans.astro	Import pluginCountLabel and pass it to message interpolation and template rendering instead of hardcoded plugin counts.
Pages apps/web/src/pages/about.astro, apps/web/src/pages/alternatives.astro, apps/web/src/pages/capwesome.astro, apps/web/src/pages/ionic-appflow.astro	Import pluginCountLabel and interpolate into localized message calls and content sections replacing previous hardcoded "30+", "100+", and empty parameter lists.
Documentation & Blog apps/docs/src/content/docs/docs/index.mdx, apps/web/src/content/blog/en/appflow-shutdown-alternative.md, apps/web/src/content/blog/en/capacitor-comprehensive-guide.md, apps/web/src/content/blog/en/creating-and-deleting-update-channels-in-capacitor.md	Documentation homepage uses dynamic pluginCountLabel in heading; blog posts update plugin count references to general "broad plugin collection" phrasing and cross-links.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Cap-go/website#590: Adds new plugin entries to actions array; affects computed pluginCount and pluginCountLabel values.
• Cap-go/website#640: Modifies apps/web/src/config/plugins.ts with plugin and icon mapping changes; directly interacts with the new exports.
• Cap-go/website#642: Adds new plugin row to actions array; will cause pluginCount and pluginCountLabel to reflect updated count.

Poem

🐰 From hardcoded counts to dynamic springs,
The plugin label now grows with each new thing!
One source of truth across the whole site,
Messages dance with pluginCountLabel's light. ✨

🚥 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 '[codex] centralize plugin count' directly and clearly summarizes the main change: centralizing plugin count management across the codebase by deriving it from a single registry source instead of hardcoded values.
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 codex/centralize-plugin-count

---

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

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud