trusted by decidable

[chribjel]

Assumed a direct link to our website is reserved for sponsors, which is very understandable!

Hope to sponsor you in the future when it makes sense for us economically!

[coderabbitai]

Walkthrough

Extended the Trusted by section in docs/components/fern/trusted-by.vue by adding a new anchor entry for Decidable with light and dark logo variants, placed after the ConnexTicket block. No existing anchors or logic were changed; only static markup was appended.

Changes

Cohort / File(s)	Summary
Docs UI — Trusted By logos docs/components/fern/trusted-by.vue	Added a Decidable logo entry (anchor) linking to a discussion, including light/dark SVGs; no other markup or logic modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I hop through docs with nimble cheer,
A new logo shines, now crystal clear.
Decidable’s glyph joins the row—
In light and dark, it’s set to glow.
Thump-thump! Another merge well-spun,
Carrot high-five—this change is done. 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "trusted by decidable" directly and concisely summarizes the primary change in the PR — adding a Decidable entry to the Trusted By component — so it is on-topic and clearly related to the changeset. It is brief and understandable, though it uses lowercase styling rather than project-consistent capitalization.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/components/fern/trusted-by.vue (1)

3-3: Grammar nit: “Trusted by teams at”.

Tiny copy edit for correctness and consistency.

-        Trusted by team at
+        Trusted by teams at

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 760590c and 6ee1789.

📒 Files selected for processing (1)

• docs/components/fern/trusted-by.vue (1 hunks)

🔇 Additional comments (1)

docs/components/fern/trusted-by.vue (1)

90-102: Add rel="noopener noreferrer" to the external anchor and confirm Decidable assets

Prevents reverse‑tabnabbing; the anchor in docs/components/fern/trusted-by.vue opens an external link with target="_blank" and currently lacks rel.

-        <a
+        <a
             href="https://github.com/elysiajs/elysia/discussions/1312#discussioncomment-14405781"
             target="_blank"
+            rel="noopener noreferrer"
             title="Decidable uses Elysia to power their Business Intelligence platform, and virtually every new project they start."
             class="opacity-60 hover:opacity-100 focus:opacity-100 transition-opacity"
         >

• Verify that /logo/decidable.webp and /logo/decidable-dark.webp are committed and served (rg only found references in docs/components/fern/trusted-by.vue).
• Check other target="_blank" anchors in this component for the same rel attribute for consistency.