Skip to content

docs(sdk): Reorganize getting-started section and add new categories #16421

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stephanie-anderson merged 2 commits into from
Feb 17, 2026
Merged

docs(sdk): Reorganize getting-started section and add new categories #16421

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0ad6e99
docs(sdk): Reorganize getting-started section and add new categories
stephanie-anderson Feb 17, 2026
884e4ce
Merge branch 'master' into sdk/getting-started-reorganize
stephanie-anderson Feb 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions develop-docs/sdk/getting-started/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,4 @@ description: The following content provides guidance for SDK development at Sent
sidebar_order: 1
---

## Philosophy
Copy link
Contributor

@dingsdax dingsdax Feb 17, 2026

Choose a reason for hiding this comment

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

I do support this change. It was weird anyways that this was not linked to the Philosophy (and likewise for Principles) page 👍


The [values](philosophy/) that shape what we build. Why SDKs exist, what makes a good one, and the design tradeoffs we navigate — trust, compatibility, minimalism, and user impact.

## Principles

Working [principles](principles/) for how we collaborate, review, and ship. They translate philosophy into daily decisions: who owns what, when to automate vs. judge, and why small PRs beat big ones.
<PageGrid />
Copy link

@cursor cursor bot Feb 17, 2026

Choose a reason for hiding this comment

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

Duplicate sidebar_order causes non-deterministic PageGrid ordering

Medium Severity

Switching from manually ordered links to <PageGrid /> exposes a sidebar_order collision: both philosophy and principles have sidebar_order: 2. Previously the index page explicitly listed Philosophy before Principles, so the collision was harmless. Now <PageGrid /> auto-orders children by sidebar_order, making the relative order of these two sections non-deterministic. The new sections use carefully sequenced values (3, 4, 5, 6), but this collision at 2 was not addressed.

Additional Locations (1)

Fix in Cursor Fix in Web

2 changes: 1 addition & 1 deletion develop-docs/sdk/getting-started/philosophy/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Philosophy
description: The values that shape what we build. Why SDKs exist, what makes a good one, and the design tradeoffs we navigate — trust, compatibility, minimalism, and user impact.
description: The values that shape what we build - what makes a good SDK and the design tradeoffs we navigate around trust, compatibility, minimalism, and user impact.
sidebar_order: 2
---

Expand Down
7 changes: 7 additions & 0 deletions develop-docs/sdk/getting-started/playbooks/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
title: Playbooks
description: Step-by-step workflows for common scenarios. Each references the standards it operationalizes.
sidebar_order: 4
---

<PageGrid />
7 changes: 7 additions & 0 deletions develop-docs/sdk/getting-started/skills/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
title: Skills
Copy link
Contributor

@dingsdax dingsdax Feb 17, 2026

Choose a reason for hiding this comment

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

I wander if we wanna limit this to skills or add a more general (AI) tools section?

description: Skills are reusable automation tools and procedures that help SDK teams enforce standards, streamline tasks, and maintain cross-SDK consistency.
sidebar_order: 5
---

<PageGrid />
7 changes: 7 additions & 0 deletions develop-docs/sdk/getting-started/standards/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
title: Standards
description: Enforceable rules, each with a defined automation/enforcement mechanism. Cross-SDK baseline with per-SDK overrides.
sidebar_order: 3
---

<PageGrid />
7 changes: 7 additions & 0 deletions develop-docs/sdk/getting-started/templates/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
title: Templates
description: Shared resources used to standardize key documentation and process patterns across all SDK repos.
sidebar_order: 6
---

<PageGrid />
5 changes: 5 additions & 0 deletions develop-docs/sdk/getting-started/templates/saved-replies/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
title: GitHub Saved Replies
description: GitHub saved replies for common scenarios. These are team-approved responses - using them is expected and encouraged.
sidebar_order: 30
---