Add ProseMirror SDK guide (#294)

* Consolidate SDK pages under a single "SDKs" navigation group

Move JS SDK, React, iOS SDK, and Android SDK docs into docs/sdks/
with a new group landing page and ProseMirror placeholder. Update
all internal links across 27 files to reflect the new paths.

* Update footer and mobile nav to link to SDKs group page

Change "JS SDK" link to "SDKs" pointing to /docs/sdks in both
the footer and mobile navigation dropdown.

* Add ProseMirror SDK guide with full documentation

Cover installation, quick start, configuration, mark mapping,
remote cursors, sync internals, and lower-level utilities for
the @yorkie-js/prosemirror package.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: hackerwins

components/Layout/Footer.tsx

@@ -80,8 +80,8 @@ export function Footer({ shortFooter }: { shortFooter?: boolean }): ReactElement
                 </Link>
               </li>
               <li className="site_item">
-                <Link href="/docs/js-sdk" className="link">
-                  JS SDK
+                <Link href="/docs/sdks" className="link">
+                  SDKs
                 </Link>
               </li>
               <li className="site_item">

components/Layout/MobileGnbDropdown.tsx

@@ -79,12 +79,12 @@ export function MobileGnbDropdown({ isLoggedIn }: { isLoggedIn: boolean }) {
                   </li>
                   <li className="navigator_group">
                     <Link
-                      href="/docs/js-sdk"
+                      href="/docs/sdks"
                       className={classNames('navigator_item', 'add_icon', {
-                        is_active: asPath.startsWith(`/docs/js-sdk`),
+                        is_active: asPath.startsWith(`/docs/sdks`),
                       })}
                     >
-                      JS SDK
+                      SDKs
                     </Link>
                   </li>
                   <li className="navigator_group">

docs/advanced.mdx

@@ -21,5 +21,5 @@ This section covers configuration and integration topics for building production
 Before exploring these topics, ensure you have:
 1. Completed the [Getting Started guide](/docs/getting-started)
 2. Built at least one application using Yorkie SDKs
-3. Understood basic concepts like [Client](/docs/js-sdk#client), [Document](/docs/js-sdk#document), and [Channel](/docs/js-sdk#channel)
+3. Understood basic concepts like [Client](/docs/sdks/js-sdk#client), [Document](/docs/sdks/js-sdk#document), and [Channel](/docs/sdks/js-sdk#channel)
 4. Reviewed key terms in the [Glossary](/docs/glossary)

docs/advanced/architecture-patterns.mdx

@@ -13,7 +13,7 @@ Understanding these patterns will help you design the optimal architecture for y
 
 If you're new to Yorkie, we recommend:
 1. Complete the [Getting Started guide](/docs/getting-started) first
-2. Understand basic [Client](/docs/js-sdk#client) and [Document](/docs/js-sdk#document) concepts
+2. Understand basic [Client](/docs/sdks/js-sdk#client) and [Document](/docs/sdks/js-sdk#document) concepts
 3. Familiarize yourself with key terms in the [Glossary](/docs/glossary)
 4. Then return here to choose your architecture pattern
 
@@ -52,7 +52,7 @@ sequenceDiagram
 2. Server creates a new document through [Yorkie Admin API](/docs/tools/admin-api#post-yorkiev1adminservicecreatedocument)
 3. Server stores document metadata in your database
 4. Server returns document key to client
-5. Client [attaches](/docs/js-sdk#attaching-the-document) to the document using the provided key
+5. Client [attaches](/docs/sdks/js-sdk#attaching-the-document) to the document using the provided key
 
 **Document Editing Flow:**
 
@@ -159,7 +159,7 @@ sequenceDiagram
 
 1. Client requests document key and initial content from your server
 2. Client creates document locally with received key
-3. Client attaches document with initial content using the [`initialRoot`](/docs/js-sdk#initializing-root) option:
+3. Client attaches document with initial content using the [`initialRoot`](/docs/sdks/js-sdk#initializing-root) option:
 
 ```typescript
 const doc = new yorkie.Document(key); // Key received from server
@@ -214,7 +214,7 @@ sequenceDiagram
     Y-->>C: Detach confirmed
 ```
 
-1. Client finishes editing and [detaches](/docs/js-sdk#detaching-the-document) from document
+1. Client finishes editing and [detaches](/docs/sdks/js-sdk#detaching-the-document) from document
 2. With project-level `RemoveOnDetach` option enabled, document is automatically removed when no clients are attached
 3. This automatic cleanup reduces server management overhead
 
@@ -344,7 +344,7 @@ Explore real-world examples implementing these patterns:
 ### Related Documentation
 
 For more information about Yorkie's API and features:
-- [JS SDK Documentation](/docs/js-sdk) - Client and Document API reference
+- [JS SDK Documentation](/docs/sdks/js-sdk) - Client and Document API reference
 - [Admin API](/docs/tools/admin-api) - Admin API for server-side management
 - [Security Configuration](/docs/advanced/security) - Auth Webhook and access control
 - [CLI](/docs/tools/cli) - Command-line tools for project management

docs/advanced/projects.mdx

@@ -9,7 +9,7 @@ A **Project** in Yorkie is a logical grouping that isolates documents, channels,
 
 ### Overview
 
-Every Yorkie installation starts with a `default` project that is created automatically. When a [Client](/docs/js-sdk#client) connects without specifying an API key, it is placed in the default project. For production applications, you should create dedicated projects to isolate data and configure settings independently.
+Every Yorkie installation starts with a `default` project that is created automatically. When a [Client](/docs/sdks/js-sdk#client) connects without specifying an API key, it is placed in the default project. For production applications, you should create dedicated projects to isolate data and configure settings independently.
 
 ```mermaid
 graph TB
@@ -47,7 +47,7 @@ Each project has two keys:
 
 | Key | Purpose | Usage |
 |-----|---------|-------|
-| **Public Key** | Identifies the project for client connections | Used as `apiKey` when creating a [Client](/docs/js-sdk#client) |
+| **Public Key** | Identifies the project for client connections | Used as `apiKey` when creating a [Client](/docs/sdks/js-sdk#client) |
 | **Secret Key** | Authenticates server-side applications | Used in the `authorization` header for [Admin API](/docs/tools/admin-api) requests |
 
 ```javascript
@@ -121,8 +121,8 @@ Each project can be independently configured with the following settings:
 | **Auth Webhook** | External authentication endpoint for validating client requests | [Security: Auth Webhook](/docs/advanced/security#auth-webhook) |
 | **Event Webhook** | Notification endpoint for document events | [Event Webhook](/docs/advanced/event-webhook) |
 | **Allowed Origins** | CORS restrictions for client connections | [Security: Allowed Origins](/docs/advanced/security#allowed-origins) |
-| **Max Attachments** | Maximum clients that can attach to a single document | [Document Limits](/docs/js-sdk#document-limits) |
-| **Max Subscribers** | Maximum clients that can subscribe to a single document | [Document Limits](/docs/js-sdk#document-limits) |
+| **Max Attachments** | Maximum clients that can attach to a single document | [Document Limits](/docs/sdks/js-sdk#document-limits) |
+| **Max Subscribers** | Maximum clients that can subscribe to a single document | [Document Limits](/docs/sdks/js-sdk#document-limits) |
 | **Client Deactivate Threshold** | Time after which inactive clients are automatically deactivated by [Housekeeping](/docs/internals/housekeeping) | [CLI](/docs/tools/cli#updating-the-project) |
 
 ### Common Patterns

docs/advanced/resources.mdx

@@ -95,7 +95,7 @@ yorkie project update [project-name] \
 ```
 
 <Alert status="info">
-When a client receives a snapshot instead of incremental changes, a `snapshot` event is triggered. Your application should handle this event to update its state. See [Document Events](/docs/js-sdk#documentsubscribesnapshot) for more details.
+When a client receives a snapshot instead of incremental changes, a `snapshot` event is triggered. Your application should handle this event to update its state. See [Document Events](/docs/sdks/js-sdk#documentsubscribesnapshot) for more details.
 </Alert>
 
 #### SnapshotInterval
@@ -191,4 +191,4 @@ yorkie project update my-project \
 - [CLI Reference](/docs/tools/cli) - Complete CLI command reference
 - [Admin API](/docs/tools/admin-api) - API for project management
 - [Architecture Patterns](/docs/advanced/architecture-patterns) - Document lifecycle patterns
-- [JS SDK - Document Events](/docs/js-sdk#documentsubscribesnapshot) - Handling snapshot events
+- [JS SDK - Document Events](/docs/sdks/js-sdk#documentsubscribesnapshot) - Handling snapshot events

docs/advanced/revisions.mdx

@@ -28,7 +28,7 @@ Revisions are immutable snapshots of a document's state stored on the server. Ea
 ### Before You Begin
 
 This guide assumes familiarity with:
-1. [Client](/docs/js-sdk#client) and [Document](/docs/js-sdk#document) basics
+1. [Client](/docs/sdks/js-sdk#client) and [Document](/docs/sdks/js-sdk#document) basics
 2. [YSON format](/docs/internals/yson) for understanding snapshots
 
 ### How Revisions Work
@@ -57,7 +57,7 @@ When you create a revision:
 
 ### API Reference
 
-For detailed API documentation, see [JS SDK - Document Revisions](/docs/js-sdk#document-revisions).
+For detailed API documentation, see [JS SDK - Document Revisions](/docs/sdks/js-sdk#document-revisions).
 
 | Method | Description |
 |--------|-------------|
@@ -340,7 +340,7 @@ Revision operations require appropriate document permissions:
 
 ### Related Documentation
 
-- [JS SDK - Document Revisions](/docs/js-sdk#document-revisions) - Complete API reference
+- [JS SDK - Document Revisions](/docs/sdks/js-sdk#document-revisions) - Complete API reference
 - [YSON](/docs/internals/yson) - Understanding snapshot format
 - [Resources](/docs/advanced/resources) - Project configuration including auto-revisions
 - [CodePair](https://github.com/yorkie-team/codepair) - Reference implementation

docs/advanced/security.mdx

@@ -120,7 +120,7 @@ Yorkie handles authentication failures based on the webhook response and HTTP st
 ##### Token Refresh & Retry Behavior
 For `PushPull` (realtime sync) and `WatchDocuments`:
 - Yorkie automatically retries the request after refreshing the token
-- Notifies via [`document.subscribe('auth-error')`](/docs/js-sdk#documentsubscribeauth-error)
+- Notifies via [`document.subscribe('auth-error')`](/docs/sdks/js-sdk#documentsubscribeauth-error)
 
 For other API calls:
 - The system does not automatically retry; the client must manually handle the `codes.Unauthenticated` error and retry the request

docs/getting-started/with-android-sdk.mdx

@@ -153,4 +153,4 @@ scope.launch {
 }
 ```
 
-Next, let's take a look at the [Android SDK](/docs/android-sdk).
+Next, let's take a look at the [Android SDK](/docs/sdks/android-sdk).

docs/getting-started/with-ios-sdk.mdx

@@ -101,4 +101,4 @@ await doc.subscribePresnece { event in
 }
 ```
 
-Next, let's take a look at the [iOS SDK](/docs/ios-sdk).
+Next, let's take a look at the [iOS SDK](/docs/sdks/ios-sdk).