Skip to content

Update SDKs page#3505

Draft
Strift wants to merge 1 commit intomainfrom
update-sdk-page
Draft

Update SDKs page#3505
Strift wants to merge 1 commit intomainfrom
update-sdk-page

Conversation

@Strift
Copy link
Copy Markdown
Contributor

@Strift Strift commented Mar 16, 2026

Description

ENGPROD-2328 Docs: improve SDKs/integrations pages

I’m missing icons for some languages/frameworks. I’m not sure what the process is to add new icons, but I imagine it can take time.

In the meantime, I think the cards look better without an icon than with a generic icon like plug.

Checklist

For internal Meilisearch team member only:

For external maintainers

  • Did you use any AI tool while implementing this PR (code, tests, docs, etc.)? If yes, disclose it in the PR description and describe what it was used for. AI usage is allowed when it is disclosed.
  • Have you made sure that the title is accurate and descriptive of the changes?

Summary by CodeRabbit

  • Documentation
    • Restructured SDK and integration docs into a card-based layout for improved readability.
    • Reorganized content into clear categories: AI, Client SDKs, Framework SDKs, Platform SDKs, Front-end SDKs, and Community-maintained SDKs.
    • Added docs for Laravel Scout, Strapi v5, Firebase sync, InstantSearch.js, Autocomplete.js, and an MCP server card.
    • Removed prior React/Vue front-end tool listings and the old AI Assistant tools subsection.
    • Consolidated “Other tools”: retained meilisearch-docsearch and replaced the Kubernetes entry with Helm/manifests guidance.
    • Updated contribution guidance with community-focused wording and links.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 16, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 289f8add-1827-48e3-a428-f62ae587e1b5

📥 Commits

Reviewing files that changed from the base of the PR and between 001dc30 and 982c852.

📒 Files selected for processing (1)
  • resources/help/sdks.mdx
🚧 Files skipped from review as they are similar to previous changes (1)
  • resources/help/sdks.mdx

📝 Walkthrough

Walkthrough

Converted the SDKs documentation page from plain-text link lists into a card-based layout with new sections (AI, Client SDKs, Framework SDKs, Platform SDKs, Front-end SDKs, Community-maintained SDKs), added and updated several integration cards, removed some prior references, and revised the Contributing text.

Changes

Cohort / File(s) Summary
SDK Documentation (single file)
resources/help/sdks.mdx
Replaced sectioned plain-text lists with a card-based layout. Added AI (MCP server) card, Client SDKs, Framework SDKs (Laravel Scout), Platform SDKs (Strapi v5, Firebase sync), Front-end SDKs (InstantSearch.js, Autocomplete.js), and reorganized Community-maintained SDKs into Languages/Frameworks groups. Removed previous React/Vue front-end tools and the old "AI Assistant tools" subsection; updated "Other tools" entries and revised Contributing guidance to point to GitHub issues and contribution guidelines.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 I hopped through docs and turned the list to cards,
New SDKs gleam like woodland yards.
MCP hums, frameworks take their place,
A tidy map for every interface.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Update SDKs page' is vague and generic, using non-descriptive terminology that fails to convey the specific nature of the changes made. Use a more specific title that highlights the main change, such as 'Convert SDKs page to card-based layout' or 'Refactor SDKs documentation with card components'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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 update-sdk-page

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 `@learn/resources/sdks.mdx`:
- Line 9: Update the sentence that reads "Meilisearch provides a [MCP
server](/guides/ai/mcp) for integrating Meilisearch with LLM clients and IDEs."
to use the correct article "an" before the initialism: change "a [MCP server]"
to "an [MCP server]"; locate the string "Meilisearch provides a [MCP
server](/guides/ai/mcp)..." in the learn/resources/sdks.mdx content and replace
only the article while keeping the link and rest of the sentence unchanged.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bd26e98b-1bed-4d20-a84b-839682ed2d06

📥 Commits

Reviewing files that changed from the base of the PR and between d4eb78a and eb10799.

📒 Files selected for processing (1)
  • learn/resources/sdks.mdx

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
resources/help/sdks.mdx (1)

111-113: Contributing text can be more direct and action-oriented.

This section is a bit informal (kickstarted, emoji) and does not provide a concrete destination for “issues.” Consider simpler wording and a direct link target.

Suggested rewrite
-All Meilisearch integrations are open-source. We're proud that some of our libraries were kickstarted and are still maintained by external contributors! ♥️
+All Meilisearch integrations are open source, and several are maintained by external contributors.

-If you'd like to contribute, check out the issues on the GitHub repositories. For more information [consult these guidelines](https://github.com/meilisearch/integrations-guides).
+If you'd like to contribute, review open issues in the relevant repository, and [consult these guidelines](https://github.com/meilisearch/integrations-guides).

As per coding guidelines: "Prefer short, direct sentences and avoid jargon when a simpler term exists in documentation" and "Match the existing tone and structure of the docs, referencing learn/resources/contributing_docs.mdx and surrounding files".

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@resources/help/sdks.mdx` around lines 111 - 113, Replace the informal,
indirect phrasing in the paragraph ("kickstarted", emoji, "check out the issues
on the GitHub repositories") with a concise, action-oriented sentence that
points users to a concrete target: link directly to the integrations
repositories list or their GitHub issues page and to the contributing
guidelines; e.g., change the copy to something like "All Meilisearch
integrations are open-source. To contribute, open an issue or submit a pull
request on the integration's GitHub repository. See the contributing guidelines
for details." Ensure you remove the emoji, replace "kickstarted" with a neutral
term like "started" or "created", and reference or link to
learn/resources/contributing_docs.mdx (or the existing integrations-guides URL)
so tone and structure match surrounding docs.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@resources/help/sdks.mdx`:
- Around line 35-36: Change the displayed language name from "Golang" to the
official "Go" in the Card component: update the Card title prop value currently
set to "Golang" to "Go" (keep the icon prop "golang" and href as-is unless you
want to update the icon name too) so the UI uses the official language name.

---

Nitpick comments:
In `@resources/help/sdks.mdx`:
- Around line 111-113: Replace the informal, indirect phrasing in the paragraph
("kickstarted", emoji, "check out the issues on the GitHub repositories") with a
concise, action-oriented sentence that points users to a concrete target: link
directly to the integrations repositories list or their GitHub issues page and
to the contributing guidelines; e.g., change the copy to something like "All
Meilisearch integrations are open-source. To contribute, open an issue or submit
a pull request on the integration's GitHub repository. See the contributing
guidelines for details." Ensure you remove the emoji, replace "kickstarted" with
a neutral term like "started" or "created", and reference or link to
learn/resources/contributing_docs.mdx (or the existing integrations-guides URL)
so tone and structure match surrounding docs.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 44c50a7d-a931-4015-8242-f58a59403189

📥 Commits

Reviewing files that changed from the base of the PR and between eb10799 and 001dc30.

📒 Files selected for processing (1)
  • resources/help/sdks.mdx

Comment on lines +35 to +36
<Card title="Golang" icon="golang" href="https://github.com/meilisearch/meilisearch-go">
Go client
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

Is the official programming language name "Go" (not "Golang") according to the official go.dev documentation?

💡 Result:

Yes, the official programming language name is "Go" (not "Golang") according to the official go.dev documentation.

Citations:


Use the official language name Go instead of Golang.

The official name per go.dev documentation is Go, not Golang. This aligns with the coding guideline to spell technical and product names as in official sources.

Suggested fix
-  <Card title="Golang" icon="golang" href="https://github.com/meilisearch/meilisearch-go">
+  <Card title="Go" icon="golang" href="https://github.com/meilisearch/meilisearch-go">
     Go client
   </Card>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<Card title="Golang" icon="golang" href="https://github.com/meilisearch/meilisearch-go">
Go client
<Card title="Go" icon="golang" href="https://github.com/meilisearch/meilisearch-go">
Go client
</Card>
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@resources/help/sdks.mdx` around lines 35 - 36, Change the displayed language
name from "Golang" to the official "Go" in the Card component: update the Card
title prop value currently set to "Golang" to "Go" (keep the icon prop "golang"
and href as-is unless you want to update the icon name too) so the UI uses the
official language name.

Entire-Checkpoint: 9c68757644a6
@qdequele
Copy link
Copy Markdown
Member

A lot of links where broken but I fixed them all. Should be ready for review :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants