chore: add TanStack Start to list of SDKs

[tamalchowdhury]

This quick PR adds the new TanStack Start SDK to the list of SDKs. Also cleans up and improves the overall doc.

Summary by CodeRabbit

• Documentation
  • Reorganized SDK documentation with updated front-end and back-end categorization.
  • Added new TanStack Start React SDK to back-end options.
  • Removed outdated version-compatibility warning.
  • Restructured Native and Community SDK sections.

[coderabbitai]

Walkthrough

This PR updates the SDK reference documentation page by refreshing front matter (metadata and context navigation), rewriting the introduction, reorganizing SDK categories, and consolidating community guidance into a styled aside block while removing external community links.

Changes

SDK Documentation Refresh

Layer / File(s)	Summary
Front matter and metadata src/content/docs/developer-tools/about/our-sdks.mdx	Page description is updated, app_context navigation path changed from settings/apis to settings/applications, and sidebar position remains stable.
SDK reference content and section reorganization src/content/docs/developer-tools/about/our-sdks.mdx	Introduction text shortened, version-compatibility warning removed, Front end SDK list narrowed (TypeScript link removed), Back end list expanded (TanStack Start React added), Native and Other sections regrouped, and Community SDKs messaging moved into a titled Aside with revised explanatory text; Slack and Discord contribution links removed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A docs page blooms with fresh arrangement,
SDKs sorted with new engagement,
Context paths shift and links realign,
Community prose now clearly defined,
🐰 hops through this tidy redesign!

🚥 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 accurately reflects the primary change: adding TanStack Start SDK to the SDK list. However, it omits other significant changes like front-end section reorganization, content rewrites, and removal of prior compatibility warnings.
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 tamal/update/tanstack-sdk-list-inclusion

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

[cloudflare-workers-and-pages]

Deploying kinde-docs-preview with    Cloudflare Pages

Latest commit:	eeb5988
Status:	✅  Deploy successful!
Preview URL:	https://faeb628e.kinde-docs-preview.pages.dev
Branch Preview URL:	https://tamal-update-tanstack-sdk-li.kinde-docs-preview.pages.dev

View logs

[coderabbitai]

🧹 Nitpick comments (1)

src/content/docs/developer-tools/about/our-sdks.mdx (1)

51-53: ⚡ Quick win

Consider restoring the version compatibility warning.

The AI summary indicates that a version compatibility warning <Aside> was removed from this page. While the compatibility note now appears in the ai_summary metadata (line 48), users won't see this guidance when reading the page. Version compatibility is critical information that should be visible to developers choosing an SDK.

Consider re-adding a brief compatibility note, such as:

💡 Suggested addition after line 53

 Visit your preferred SDK page below to get started. You can also use [Kinde without an SDK](/developer-tools/about/using-kinde-without-an-sdk/).
+
+<Aside type="tip">
+Always verify that your tech stack versions are compatible with the SDK you choose before getting started.
+</Aside>

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/content/docs/developer-tools/about/our-sdks.mdx` around lines 51 - 53,
Restore a visible version compatibility note on the Our SDKs page by adding a
brief Aside (or similar callout) immediately after the paragraph that starts
"Kinde provides Software Development Kits (SDKs)..." so readers see the
compatibility guidance that currently only exists in the ai_summary metadata;
update the content to succinctly warn about SDK version compatibility with Kinde
core (e.g., mention major/minor compatibility and where to find supported
versions) and reference the Aside component (or callout component used
elsewhere) so the note is rendered for readers.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/content/docs/developer-tools/about/our-sdks.mdx`:
- Around line 51-53: Restore a visible version compatibility note on the Our
SDKs page by adding a brief Aside (or similar callout) immediately after the
paragraph that starts "Kinde provides Software Development Kits (SDKs)..." so
readers see the compatibility guidance that currently only exists in the
ai_summary metadata; update the content to succinctly warn about SDK version
compatibility with Kinde core (e.g., mention major/minor compatibility and where
to find supported versions) and reference the Aside component (or callout
component used elsewhere) so the note is rendered for readers.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 53491de3-7e49-4e76-a431-c3b37f7a0d5f

📥 Commits

Reviewing files that changed from the base of the PR and between b750eb9 and eeb5988.

📒 Files selected for processing (1)

• src/content/docs/developer-tools/about/our-sdks.mdx