/`:
+
+ * `/invite//`
+If you believe you meet these requirements, you can -[apply for access to full release comms features](/docs/discord-social-sdk/core-concepts/communication-features#applying-for-rate-limit-removal). +[apply for access to full release comms features](/developers/docs/discord-social-sdk/core-concepts/communication-features#applying-for-rate-limit-removal). Discord may approve or deny your access after review of your application and additional terms may apply. -::: +
**For example:** Example Studio's *Wumpus Wars* is available to players on Sony PlayStation 5 and Xbox Series S and Xbox Series X. Example Studio submits the feature list and *Wumpus Wars* capture for Xbox. -::: +
Make sure to make your players aware to only link channels in servers you trust your players to join, and/or provide in-game options to disable this feature for certain lobbies. -::: +
If your announcements do not focus on Discord Social SDK features that require account linking, you can still generally use this guidance and our brand guidelines. -::: +
Joining a game directly from a friend’s profile (similar to game invites) | -| **Unified Friends List** | Players can access their Discord friends list from within the game. Includes friend tiers. | Sending game invites directly to friends from in-game
Knowing which of your friends is playing, and who isn’t playing but is online and could play
Not having to re-create your friends list social in a new game that you play | +| **Rich Presence** | Shows on Discord which games players are currently playing. | Knowing what your friends are doing in-game, so you know if they'd be available to play together
Joining a game directly from a friend's profile (similar to game invites) | +| **Unified Friends List** | Players can access their Discord friends list from within the game. Includes friend tiers. | Sending game invites directly to friends from in-game
Knowing which of your friends is playing, and who isn't playing but is online and could play
Not having to re-create your friends list social in a new game that you play | | **Deeplink Game Invites** | Users can send invites that link directly to specific game instances or parts of a game. | Challenging users to specific game instances | | **Flexible Account Requirements** | Users can choose to link their Discord account to unlock deeper integrated features such as the Unified Friends List and Rich Presence, but can also take advantage of the in-game social features without linking an account through an innovative "provisional account." | Account linking: Automatic Discord-based sign in, or, linking of your Discord account to a game account.
Take full advantage of the Discord integration
Provisional accounts: Provisional accounts let you use Discord's voice and text chat features while playing connected games \- without needing to create a Discord account first. | -| **Cross-Platform Messaging** | Allows players to communicate seamlessly both in-game and through Discord, even without a Discord account. | DMing your friends when they’re in-game and out of game
Receiving messages from your friends when you aren’t playing.
In-game text chat for guilds, matches, lobbies, etc. | -| **Linked Channels** | Players can link their in-game group chat with in-Discord channels, providing persistent group chats. | In-game guild/group chat mirrored in your guild’s/group’s Discord server
No more feeling isolated from the broader group if you’re online when everyone else isn’t, or vice-versa | +| **Cross-Platform Messaging** | Allows players to communicate seamlessly both in-game and through Discord, even without a Discord account. | DMing your friends when they're in-game and out of game
Receiving messages from your friends when you aren't playing.
In-game text chat for guilds, matches, lobbies, etc. | +| **Linked Channels** | Players can link their in-game group chat with in-Discord channels, providing persistent group chats. | In-game guild/group chat mirrored in your guild's/group's Discord server
No more feeling isolated from the broader group if you're online when everyone else isn't, or vice-versa | | **Discord Voice Chat** | High quality voice chat powered by Discord available directly in the game. | In-game voice chat for guilds, matches, lobbies, etc. | ## Integration Announcement Plan Recommendations @@ -102,9 +99,9 @@ If you would like to tag @Discord in any of your announcements, please feel free ## Discord Brand Assets & Guidance -We’re excited you’re helping us spread the word about Discord. We’d love to make sure you have the right assets to use and guidelines from our brand team. +We're excited you're helping us spread the word about Discord. We'd love to make sure you have the right assets to use and guidelines from our brand team. -When using Discord Marks and Brand Assets, you must always comply with Discord’s [Brand Guidelines found here](https://discord.com/branding). +When using Discord Marks and Brand Assets, you must always comply with Discord's [Brand Guidelines found here](https://discord.com/branding). As a reminder, you may not make any statement that suggests a partnership with, sponsorship by, or endorsement by Discord without our prior written approval in each instance. We also have some additional guidance below specific for your Discord Social SDK launch. ### Discord Logo and Wordmark @@ -112,12 +109,12 @@ As a reminder, you may not make any statement that suggests a partnership with, * [Download Link](https://discord.com/branding) * Guidance for Discord Social SDK * When using our logo or wordmark in your CTA buttons in-game, in social and blog post visual assets, please -review the Logo & Symbol sections of our brand guidelines. If you’re not sure about use or have questions, please reach out to your Discord point of contact. +review the Logo & Symbol sections of our brand guidelines. If you're not sure about use or have questions, please reach out to your Discord point of contact. * Please refer to our articles on in-game - [Connection Points](/docs/discord-social-sdk/design-guidelines/connection-points) and - [Overall Flow](/docs/discord-social-sdk/design-guidelines/signing-in#before-the-user-connects) for more guidance for in-game messaging. + [Connection Points](/developers/docs/discord-social-sdk/design-guidelines/connection-points) and + [Overall Flow](/developers/docs/discord-social-sdk/design-guidelines/signing-in#before-the-user-connects) for more guidance for in-game messaging. * Usage Guidance - * [Logo Usage Do’s and Don’ts](https://discord.com/branding) (Click "View Brand Kit" then "Logo" then "Usage"). + * [Logo Usage Do's and Don'ts](https://discord.com/branding) (Click "View Brand Kit" then "Logo" then "Usage"). ### Discord Bumper Splash Animation @@ -127,7 +124,7 @@ review the Logo & Symbol sections of our brand guidelines. If you’re not sure * [3 second bumper splash animation audio (Streaming)](https://cdn.discordapp.com/assets/content/f3070170acd3f62b08ba9a63ab71080f6f7a72be5c84b74d1b247b4767696045.wav) * Best Practice Guidance for Discord Social SDK * This can be used as an intro splash video to your game, video launch announcement of the SDK, or game trailer - content where Discord Social SDK features are shown. You should not use this splash video in your content if Discord Social SDK features aren’t present in the content. + content where Discord Social SDK features are shown. You should not use this splash video in your content if Discord Social SDK features aren't present in the content. * Usage Guidance * When using this splash animation in your video, always include this at the beginning of the video. This splash video should never go in the middle or end of your content. @@ -148,4 +145,4 @@ Please visit our [Discord Brand Guidelines](https://discord.com/branding) for ad | Date | Changes | |---------------|------------------| -| July 22, 2025 | initial creation | \ No newline at end of file +| July 22, 2025 | initial creation | diff --git a/docs/discord-social-sdk/how-to/use-with-discord-apis.mdx b/discord/developers/docs/discord-social-sdk/how-to/use-with-discord-apis.mdx similarity index 76% rename from docs/discord-social-sdk/how-to/use-with-discord-apis.mdx rename to discord/developers/docs/discord-social-sdk/how-to/use-with-discord-apis.mdx index e7a0d4e69e..2fcef6508e 100644 --- a/docs/discord-social-sdk/how-to/use-with-discord-apis.mdx +++ b/discord/developers/docs/discord-social-sdk/how-to/use-with-discord-apis.mdx @@ -1,12 +1,9 @@ --- -sidebar_label: Use with Discord APIs +title: Use with Discord APIs +description: Combine Discord Social SDK with Discord's REST APIs for enhanced functionality. --- -import PublicClient from '../partials/callouts/public-client.mdx'; -import SupportCallout from '../partials/callouts/support.mdx'; - -[Home](/docs/intro) > [Discord Social SDK](/docs/discord-social-sdk/overview) > [How To](/docs/discord-social-sdk/how-to) > {sidebar_label} - -# {sidebar_label} +import PublicClient from '/snippets/discord-social-sdk/callouts/public-client.mdx'; +import SupportCallout from '/snippets/discord-social-sdk/callouts/support.mdx'; ## Overview @@ -26,19 +23,19 @@ Before you begin, make sure you have: ### Bot Token Authentication For server-to-server communication: -``` +```bash curl -X GET https://discord.com/api/v10/users/@me \ -H "Authorization: Bot YOUR_BOT_TOKEN" ``` -:::info +
For integrations experienced on Sony Platforms (e.g. PlayStation 5)…
1. **Do not allow access to Account Linking** entry points.
2. **Do not allow access to Linked Channels**.
3. **Limit messaging and Invites to other players currently playing** the game.
4. **Do not display off-platform presence and logos** (including Discord). -::: \ No newline at end of file +
+
+
+
+## Extend Discord with Custom Integrations
+
+Enhance the Discord experience with custom apps, commands, and integrations.
+
+
+
+
+## Build Multiplayer Games and Social Experiences
+
+Use the Embedded App SDK to create real-time games and social experiences that users can launch directly inside Discord.
+
+
+
+
+## Bring Social Features to Your Game
+
+Enable rich presence, voice chat, and more to create a seamless social experience for your players and grow your game.
+
+
+
+
+## Find Support
+
+Connect with the developer community, report issues, and stay updated with API changes.
+
+
+ +
+
+
diff --git a/docs/monetization/enabling-monetization.mdx b/discord/developers/docs/monetization/enabling-monetization.mdx
similarity index 72%
rename from docs/monetization/enabling-monetization.mdx
rename to discord/developers/docs/monetization/enabling-monetization.mdx
index 3642f70fee..0c3beed021 100644
--- a/docs/monetization/enabling-monetization.mdx
+++ b/discord/developers/docs/monetization/enabling-monetization.mdx
@@ -1,4 +1,7 @@
-# Enabling Monetization
+---
+title: Enabling Monetization
+description: Step-by-step guide to meet eligibility requirements and enable monetization.
+---
Before you can add monetization to your app, you must ensure that your app and team meet the eligibility criteria.
@@ -11,13 +14,13 @@ Before you can add monetization to your app, you must ensure that your app and t
5. Implement monetization in your app
6. Start offering your premium features
-Once these are complete, you can [create SKUs](/docs/monetization/managing-skus#creating-a-sku) to represent your premium offerings and [add support for your premium offering](/docs/monetization/enabling-monetization#step-5-implement-monetization-in-your-app) in your app.
+Once these are complete, you can [create SKUs](/developers/docs/monetization/managing-skus#creating-a-sku) to represent your premium offerings and [add support for your premium offering](/developers/docs/monetization/enabling-monetization#step-5-implement-monetization-in-your-app) in your app.
## Step 1. Set Up Your Developer Team and App
Before monetization can be enabled, you will need:
-- A [team](/docs/topics/teams) in the developer portal. If you don't have one, you can [create one on the Teams page](https://discord.com/developers/teams)
+- A [team](/developers/docs/topics/teams) in the developer portal. If you don't have one, you can [create one on the Teams page](https://discord.com/developers/teams)
- A [verified app](https://support-dev.discord.com/hc/en-us/articles/23926564536471-How-Do-I-Get-My-App-Verified) that is _owned by that team_
- Your app and team must be eligible for monetization. See the Eligibility Checklist below for details.
@@ -25,7 +28,7 @@ Before monetization can be enabled, you will need:
Before you can start creating SKUs and offering payments in your app, your app and team must be eligible for monetization. When a team owner enables monetization, they'll be taken through a series of steps and checks to ensure the following criteria are met:
-
+
+
+## Build with Discord
+
+Discord provides a platform for building social experiences, whether you're
+creating apps within Discord or integrating Discord's features into your game.
+
+
+
+
+
+ Build Where the World Plays
+Create social games, experiences, and integrations for millions of users on Discord
+
+ 
+
+
+ + +
+
+On this page we'll answer the questions:
+
+* [What can apps do?](/developers/docs/quick-start/overview-of-apps#what-can-apps-do)
+* [Where are apps installed?](/developers/docs/quick-start/overview-of-apps#where-are-apps-installed)
+* [What APIs can apps use?](/developers/docs/quick-start/overview-of-apps#what-apis-can-apps-use)
+
+` endpoint when `with_counts` is `true` |
+| approximate_member_count? | integer | approximate count of total members, returned from the `GET /invites/` endpoint when `with_counts` is `true` |
+| expires_at | ?ISO8601 timestamp | the expiration date of this invite |
+| guild_scheduled_event? | [guild scheduled event](/developers/docs/resources/guild-scheduled-event#guild-scheduled-event-object) object | guild scheduled event data, only included if `guild_scheduled_event_id` contains a valid guild scheduled event id |
+| flags? | integer | [guild invite flags](/developers/docs/resources/invite#invite-object-guild-invite-flags) for guild invites |
+
+
+This is deprecated.
+
+
+/invites/[\{invite.code\}](/developers/docs/resources/invite#invite-object)
+
+Returns an [invite](/developers/docs/resources/invite#invite-object) object for the given code.
+
+/invites/[\{invite.code\}](/developers/docs/resources/invite#invite-object)
+
+Delete an invite. Requires the `MANAGE_CHANNELS` permission on the channel this invite belongs to, or `MANAGE_GUILD` to remove any invite across the guild. Returns an [invite](/developers/docs/resources/invite#invite-object) object on success. Fires an [Invite Delete](/developers/docs/events/gateway-events#invite-delete) Gateway event.
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
diff --git a/discord/developers/docs/resources/lobby.mdx b/discord/developers/docs/resources/lobby.mdx
new file mode 100644
index 0000000000..eaba1264e3
--- /dev/null
+++ b/discord/developers/docs/resources/lobby.mdx
@@ -0,0 +1,180 @@
+---
+title: Lobby Resource
+sidebarTitle: Lobby
+description: Reference for Discord lobby objects used for matchmaking.
+---
+
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+import {Route} from '/snippets/route.jsx'
+
+### Lobby Object
+
+Represents a lobby within Discord. See [Managing Lobbies](/developers/docs/discord-social-sdk/development-guides/managing-lobbies) for more information.
+
+ | dictionary of string key/value pairs. The max total length is 1000. |
+| members | array of [lobby member](/developers/docs/resources/lobby#lobby-member-object) objects | members of the lobby |
+| linked_channel? | channel object | the guild channel linked to the lobby |
+
+### Lobby Member Object
+
+Represents a member of a lobby, including optional metadata and flags.
+
+ | dictionary of string key/value pairs. The max total length is 1000. |
+| flags? | integer | [lobby member flags](/developers/docs/resources/lobby#lobby-member-object-lobby-member-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |
+
+/lobbies
+
+Creates a new lobby, adding any of the specified members to it, if provided.
+
+Returns a [lobby](/developers/docs/resources/lobby#lobby-object) object.
+
+
+[Discord Social SDK](/developers/docs/discord-social-sdk/overview) clients will not be able to join or leave a lobby created using this API, such as [`Client::CreateOrJoinLobby`]. See [Managing Lobbies](/developers/docs/discord-social-sdk/development-guides/managing-lobbies) for more information.
+
+
+### JSON Params
+
+| Field | Type | Description |
+|-----------------------|---------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| metadata? | ?dict\ | optional dictionary of string key/value pairs. The max total length is 1000. |
+| members? | array of [lobby member](/developers/docs/resources/lobby#lobby-member-object) objects | optional array of up to 25 users to be added to the lobby |
+| idle_timeout_seconds? | integer | seconds to wait before shutting down a lobby after it becomes idle. Value can be between 5 and 604800 (7 days). See [`LobbyHandle`] for more details on this behavior. |
+
+#### Lobby Member JSON Params
+
+| Field | Type | Description |
+|-----------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| id | snowflake | Discord user id of the user to add to the lobby |
+| metadata? | ?dict\ | optional dictionary of string key/value pairs. The max total length is 1000. |
+| flags? | integer | [lobby member flags](/developers/docs/resources/lobby#lobby-member-object-lobby-member-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |
+
+## Get Lobby
+/lobbies/[\{lobby.id\}](/developers/docs/resources/lobby#lobby-object)
+
+Returns a [lobby](/developers/docs/resources/lobby#lobby-object) object for the specified lobby id, if it exists.
+
+## Modify Lobby
+/lobbies/[\{lobby.id\}](/developers/docs/resources/lobby#lobby-object)
+
+Modifies the specified lobby with new values, if provided.
+
+Returns the updated [lobby](/developers/docs/resources/lobby#lobby-object) object.
+
+### JSON Params
+
+| Field | Type | Description |
+|-----------------------|---------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| metadata? | ?dict\ | optional dictionary of string key/value pairs. The max total length is 1000. Overwrites any existing metadata. |
+| members? | array of [lobby member](/developers/docs/resources/lobby#lobby-member-object) objects | optional array of up to 25 users to replace the lobby members with. If provided, lobby members not in this list will be removed from the lobby. |
+| idle_timeout_seconds? | integer | seconds to wait before shutting down a lobby after it becomes idle. Value can be between 5 and 604800 (7 days). See [`LobbyHandle`] for more details on this behavior. |
+
+## Delete Lobby
+/lobbies/[\{lobby.id\}](/developers/docs/resources/lobby#lobby-object)
+
+Deletes the specified lobby if it exists.
+
+It is safe to call even if the lobby is already deleted as well.
+
+Returns nothing.
+
+## Add a Member to a Lobby
+/lobbies/[\{lobby.id\}](/developers/docs/resources/lobby#lobby-object)/members/[\{user.id\}](/developers/docs/resources/user#user-object)
+
+Adds the provided user to the specified lobby. If called when the user is already a member of the lobby will update fields such as metadata on that user instead.
+
+Returns the [lobby member](/developers/docs/resources/lobby#lobby-member-object) object.
+
+### JSON Params
+
+| Field | Type | Description |
+|-----------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| metadata? | ?dict\ | optional dictionary of string key/value pairs. The max total length is 1000. |
+| flags? | integer | [lobby member flags](/developers/docs/resources/lobby#lobby-member-object-lobby-member-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |
+
+## Remove a Member from a Lobby
+/lobbies/[\{lobby.id\}](/developers/docs/resources/lobby#lobby-object)/members/[\{user.id\}](/developers/docs/resources/user#user-object)
+
+Removes the provided user from the specified lobby. It is safe to call this even if the user is no longer a member of the lobby, but will fail if the lobby does not exist.
+
+Returns nothing.
+
+## Leave Lobby
+/lobbies/[\{lobby.id\}](/developers/docs/resources/lobby#lobby-object)/members/@me
+
+Removes the current user from the specified lobby. It is safe to call this even if the user is no longer a member of the lobby, but will fail if the lobby does not exist.
+
+Uses `Bearer` token for authorization.
+
+Returns nothing.
+
+## Link Channel to Lobby
+/lobbies/[\{lobby.id\}](/developers/docs/resources/lobby#lobby-object)/channel-linking
+
+Links an existing text channel to a lobby. See [Linked Channels](/developers/docs/discord-social-sdk/development-guides/linked-channels) for more information.
+
+Uses `Bearer` token for authorization and user must be a lobby member with `CanLinkLobby` [lobby member flag](/developers/docs/resources/lobby#lobby-member-object-lobby-member-flags).
+
+Returns a [lobby](/developers/docs/resources/lobby#lobby-object) object with a linked channel.
+
+### JSON Params
+
+| Field | Type | Description |
+|-------------|-----------|------------------------------------------------------------------------------------------------------------------------|
+| channel_id? | snowflake | the id of the channel to link to the lobby. If not provided, will unlink any currently linked channels from the lobby. |
+
+## Unlink Channel from Lobby
+/lobbies/[\{lobby.id\}](/developers/docs/resources/lobby#lobby-object)/channel-linking
+
+Unlinks any currently linked channels from the specified lobby.
+
+Send a request to this endpoint with an empty body to unlink any currently linked channels from the specified lobby.
+
+Uses `Bearer` token for authorization and user must be a lobby member with `CanLinkLobby` [lobby member flag](/developers/docs/resources/lobby#lobby-member-object-lobby-member-flags).
+
+Returns a [lobby](/developers/docs/resources/lobby#lobby-object) object without a linked channel.
+
+{/* Autogenerated Reference Links */}
+[`Client::CreateOrJoinLobby`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a8b4e195555ecaa89ccdfc0acd28d3512
+[`LobbyHandle`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1LobbyHandle.html#a04cebab69ab0e7fb930346a14a87e843
\ No newline at end of file
diff --git a/docs/resources/message.mdx b/discord/developers/docs/resources/message.mdx
similarity index 58%
rename from docs/resources/message.mdx
rename to discord/developers/docs/resources/message.mdx
index 4bc2908256..6887e250aa 100644
--- a/docs/resources/message.mdx
+++ b/discord/developers/docs/resources/message.mdx
@@ -1,77 +1,82 @@
---
-sidebar_label: Message
+title: Message Resource
+sidebarTitle: Message
+description: Reference for Discord message objects and management endpoints.
---
-# Messages Resource
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+import {Route} from '/snippets/route.jsx'
### Message Object
Represents a message sent in a channel within Discord.
+
+Fields specific to the `MESSAGE_CREATE` and `MESSAGE_UPDATE` events are listed in the [Gateway documentation](/developers/docs/events/gateway-events#message-create).
+
+
+
+An app will receive empty values in the `content`, `embeds`, `attachments`, and `components` fields while `poll` will be omitted if they have not configured (or been approved for) the [`MESSAGE_CONTENT` privileged intent (`1 << 15`)](/developers/docs/events/gateway#message-content-intent).
+
+
+| Field | Type | Description |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| id | snowflake | id of the message |
+| channel_id | snowflake | id of the channel the message was sent in |
+| author \[1\] | [user](/developers/docs/resources/user#user-object) object | the author of this message (not guaranteed to be a valid user, see below) |
+| content \[2\] | string | contents of the message |
+| timestamp | ISO8601 timestamp | when this message was sent |
+| edited_timestamp | ?ISO8601 timestamp | when this message was edited (or null if never) |
+| tts | boolean | whether this was a TTS message |
+| mention_everyone | boolean | whether this message mentions everyone |
+| mentions | array of [user](/developers/docs/resources/user#user-object) objects | users specifically mentioned in the message |
+| mention_roles | array of [role](/developers/docs/topics/permissions#role-object) object ids | roles specifically mentioned in this message |
+| mention_channels? \[3\] | array of [channel mention](/developers/docs/resources/message#channel-mention-object) objects | channels specifically mentioned in this message |
+| attachments \[2\] | array of [attachment](/developers/docs/resources/message#attachment-object) objects | any attached files |
+| embeds \[2\] | array of [embed](/developers/docs/resources/message#embed-object) objects | any embedded content |
+| reactions? | array of [reaction](/developers/docs/resources/message#reaction-object) objects | reactions to the message |
+| nonce? | integer or string | used for validating a message was sent |
+| pinned | boolean | whether this message is pinned |
+| webhook_id? | snowflake | if the message is generated by a webhook, this is the webhook's id |
+| type | integer | [type of message](/developers/docs/resources/message#message-object-message-types) |
+| activity? | [message activity](/developers/docs/resources/message#message-object-message-activity-structure) object | sent with Rich Presence-related chat embeds |
+| application? | partial [application](/developers/docs/resources/application#application-object) object | sent with Rich Presence-related chat embeds |
+| application_id? | snowflake | if the message is an [Interaction](/developers/docs/interactions/receiving-and-responding) or application-owned webhook, this is the id of the application |
+| flags? | integer | [message flags](/developers/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |
+| message_reference? | [message reference](/developers/docs/resources/message#message-reference-structure) object | data showing the source of a crosspost, channel follow add, pin, or reply message |
+| message_snapshots? \[5\] | array of [message snapshot](/developers/docs/resources/message#message-snapshot-object) objects | the message associated with the `message_reference`. This is a minimal subset of fields in a message (e.g. `author` is excluded.) |
+| referenced_message? \[4\] | ?[message object](/developers/docs/resources/message#message-object) | the message associated with the message_reference |
+| interaction_metadata? | [message interaction metadata object](/developers/docs/resources/message#message-interaction-metadata-object) | Sent if the message is sent as a result of an [interaction](/developers/docs/interactions/receiving-and-responding) |
+| interaction? | [message interaction object](/developers/docs/interactions/receiving-and-responding#message-interaction-object-message-interaction-structure) | **Deprecated in favor of `interaction_metadata`**; sent if the message is a response to an [interaction](/developers/docs/interactions/receiving-and-responding) |
+| thread? | [channel](/developers/docs/resources/channel#channel-object) object | the thread that was started from this message, includes [thread member](/developers/docs/resources/channel#thread-member-object) object |
+| components? \[2\] | array of [message components](/developers/docs/components/reference#component-object) | sent if the message contains components like buttons, action rows, or other interactive components |
+| sticker_items? | array of [message sticker item objects](/developers/docs/resources/sticker#sticker-item-object) | sent if the message contains stickers |
+| stickers? | array of [sticker](/developers/docs/resources/sticker#sticker-object) objects | **Deprecated** the stickers sent with the message |
+| position? | integer | A generally increasing integer (there may be gaps or duplicates) that represents the approximate position of the message in a thread, it can be used to estimate the relative position of the message in a thread in company with `total_message_sent` on parent thread |
+| role_subscription_data? | [role subscription data](/developers/docs/resources/message#role-subscription-data-object) object | data of the role subscription purchase or renewal that prompted this ROLE_SUBSCRIPTION_PURCHASE message |
+| resolved? | [resolved](/developers/docs/interactions/receiving-and-responding#interaction-object-resolved-data-structure) data | data for users, members, channels, and roles referenced in this message |
+| poll? \[2\] | [poll](/developers/docs/resources/poll#poll-object) object | A poll! |
+| call? | [message call](/developers/docs/resources/message#message-call-object) object | the call associated with the message |
\[1\] The author object follows the structure of the user object, but is only a valid user in the case where the message is generated by a user or bot user. If the message is generated by a webhook, the author object corresponds to the webhook's id, username, and avatar. You can tell if a message is generated by a webhook by checking for the `webhook_id` on the message object.
-\[2\] An app will receive empty values in the `content`, `embeds`, `attachments`, and `components` fields while `poll` will be omitted if they have not configured (or been approved for) the [`MESSAGE_CONTENT` privileged intent (`1 << 15`)](/docs/events/gateway#message-content-intent).
+\[2\] An app will receive empty values in the `content`, `embeds`, `attachments`, and `components` fields while `poll` will be omitted if they have not configured (or been approved for) the [`MESSAGE_CONTENT` privileged intent (`1 << 15`)](/developers/docs/events/gateway#message-content-intent).
\[3\] Not all channel mentions in a message will appear in `mention_channels`. Only textual channels that are visible to everyone in a lurkable guild will ever be included. Only crossposted messages (via Channel Following) currently include `mention_channels` at all. If no mentions in the message meet these requirements, this field will not be sent.
\[4\] This field is only returned for messages with a `type` of `19` (REPLY), `21` (THREAD_STARTER_MESSAGE), or `23` (CONTEXT_MENU_COMMAND). If the message is one of these but the `referenced_message` field is not present, the backend did not attempt to fetch the message that was being replied to, so its state is unknown. If the field exists but is null, the referenced message was deleted.
-\[5\] See [message reference types](/docs/resources/message#message-reference-types)
+\[5\] See [message reference types](/developers/docs/resources/message#message-reference-types)
+
Type `19` and `20` are only available in API v8 and above. In v6, they are represented as type `0`. Additionally, type `21` is only available in API v9 and above.
-:::
+
| Type | Value | Deletable |
|----------------------------------------------|-------|-----------|
@@ -115,13 +120,15 @@ Type `19` and `20` are only available in API v8 and above. In v6, they are repre
\* Can only be deleted by members with `MANAGE_MESSAGES` permission
+
While message snapshots are able to support nested snapshots, we currently limit the depth of nesting to 1.
-:::
+
### Reaction Object
+
For the `attachments` array in Message Create/Edit requests, only the `id` is required.
-:::
-
-| Field | Type | Description |
-|----------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------|
-| id | snowflake | attachment id |
-| filename | string | name of file attached |
-| title? | string | the title of the file |
-| description? | string | description for the file (max 1024 characters) |
-| content_type? | string | the attachment's [media type](https://en.wikipedia.org/wiki/Media_type) |
-| size | integer | size of file in bytes |
-| url | string | source url of file |
-| proxy_url | string | a proxied url of file |
-| height? | ?integer | height of file (if image) |
-| width? | ?integer | width of file (if image) |
-| ephemeral? \* | boolean | whether this attachment is ephemeral |
-| duration_secs? | float | the duration of the audio file (currently for voice messages) |
-| waveform? | string | base64 encoded bytearray representing a sampled waveform (currently for voice messages) |
-| flags? | integer | [attachment flags](/docs/resources/message#attachment-object-attachment-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |
+
+
+| Field | Type | Description |
+|----------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| id | snowflake | attachment id |
+| filename | string | name of file attached |
+| title? | string | the title of the file |
+| description? | string | description for the file (max 1024 characters) |
+| content_type? | string | the attachment's [media type](https://en.wikipedia.org/wiki/Media_type) |
+| size | integer | size of file in bytes |
+| url | string | source url of file |
+| proxy_url | string | a proxied url of file |
+| height? | ?integer | height of file (if image) |
+| width? | ?integer | width of file (if image) |
+| ephemeral? \* | boolean | whether this attachment is ephemeral |
+| duration_secs? | float | the duration of the audio file (currently for voice messages) |
+| waveform? | string | base64 encoded bytearray representing a sampled waveform (currently for voice messages) |
+| flags? | integer | [attachment flags](/developers/docs/resources/message#attachment-object-attachment-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |
\* Ephemeral attachments will automatically be removed after a set period of time. Ephemeral attachments on messages are guaranteed to be available as long as the message itself exists.
+/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages
-Retrieves the messages in a channel. Returns an array of [message](/docs/resources/message#message-object) objects from newest to oldest on success.
+Retrieves the messages in a channel. Returns an array of [message](/developers/docs/resources/message#message-object) objects from newest to oldest on success.
If operating on a guild channel, this endpoint requires the current user to have the `VIEW_CHANNEL` permission. If the channel is a voice channel, they must _also_ have the `CONNECT` permission.
If the current user is missing the `READ_MESSAGE_HISTORY` permission in the channel, then no messages will be returned.
-:::info
+
The `before`, `after`, and `around` parameters are mutually exclusive, only one may be passed at a time.
-:::
+
+/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)
-Retrieves a specific message in the channel. Returns a [message](/docs/resources/message#message-object) object on success.
+Retrieves a specific message in the channel. Returns a [message](/developers/docs/resources/message#message-object) object on success.
If operating on a guild channel, this endpoint requires the current user to have the `VIEW_CHANNEL` and `READ_MESSAGE_HISTORY` permissions. If the channel is a voice channel, they must _also_ have the `CONNECT` permission.
## Create Message
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages
-:::warn
+
Discord may strip certain characters from message content, like invalid unicode characters or characters which cause unexpected message formatting. If you are passing user-generated strings into message content, consider sanitizing the data to prevent unexpected behavior and using `allowed_mentions` to prevent unexpected mentions.
-:::
+
-Post a message to a guild text or DM channel. Returns a [message](/docs/resources/message#message-object) object. Fires a [Message Create](/docs/events/gateway-events#message-create) Gateway event. See [message formatting](/docs/reference#message-formatting) for more information on how to properly format messages.
+Post a message to a guild text or DM channel. Returns a [message](/developers/docs/resources/message#message-object) object. Fires a [Message Create](/developers/docs/events/gateway-events#message-create) Gateway event. See [message formatting](/developers/docs/reference#message-formatting) for more information on how to properly format messages.
-To create a message as a reply or forward of another message, apps can include a [`message_reference`](/docs/resources/message#message-reference-structure).
+To create a message as a reply or forward of another message, apps can include a [`message_reference`](/developers/docs/resources/message#message-reference-structure).
Refer to the documentation for required fields.
-Files must be attached using a `multipart/form-data` body as described in [Uploading Files](/docs/reference#uploading-files).
+Files must be attached using a `multipart/form-data` body as described in [Uploading Files](/developers/docs/reference#uploading-files).
+/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)/crosspost
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)/crosspost
Crosspost a message in an Announcement Channel to following channels. This endpoint requires the `SEND_MESSAGES` permission, if the current user sent the message, or additionally the `MANAGE_MESSAGES` permission, for all other messages, to be present for the current user.
-Returns a [message](/docs/resources/message#message-object) object. Fires a [Message Update](/docs/events/gateway-events#message-update) Gateway event.
+Returns a [message](/developers/docs/resources/message#message-object) object. Fires a [Message Update](/developers/docs/events/gateway-events#message-update) Gateway event.
## Create Reaction
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/docs/resources/emoji#emoji-object)/@me
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/developers/docs/resources/emoji#emoji-object)/@me
-Create a reaction for the message. This endpoint requires the `READ_MESSAGE_HISTORY` permission to be present on the current user. Additionally, if nobody else has reacted to the message using this emoji, this endpoint requires the `ADD_REACTIONS` permission to be present on the current user. Returns a 204 empty response on success. Fires a [Message Reaction Add](/docs/events/gateway-events#message-reaction-add) Gateway event.
+Create a reaction for the message. This endpoint requires the `READ_MESSAGE_HISTORY` permission to be present on the current user. Additionally, if nobody else has reacted to the message using this emoji, this endpoint requires the `ADD_REACTIONS` permission to be present on the current user. Returns a 204 empty response on success. Fires a [Message Reaction Add](/developers/docs/events/gateway-events#message-reaction-add) Gateway event.
The `emoji` must be [URL Encoded](https://en.wikipedia.org/wiki/Percent-encoding) or the request will fail with `10014: Unknown Emoji`. To use custom emoji, you must encode it in the format `name:id` with the emoji name and emoji id.
## Delete Own Reaction
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/docs/resources/emoji#emoji-object)/@me
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/developers/docs/resources/emoji#emoji-object)/@me
-Delete a reaction the current user has made for the message. Returns a 204 empty response on success. Fires a [Message Reaction Remove](/docs/events/gateway-events#message-reaction-remove) Gateway event.
+Delete a reaction the current user has made for the message. Returns a 204 empty response on success. Fires a [Message Reaction Remove](/developers/docs/events/gateway-events#message-reaction-remove) Gateway event.
The `emoji` must be [URL Encoded](https://en.wikipedia.org/wiki/Percent-encoding) or the request will fail with `10014: Unknown Emoji`. To use custom emoji, you must encode it in the format `name:id` with the emoji name and emoji id.
## Delete User Reaction
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/docs/resources/emoji#emoji-object)/[\{user.id\}](/docs/resources/user#user-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/developers/docs/resources/emoji#emoji-object)/[\{user.id\}](/developers/docs/resources/user#user-object)
-Deletes another user's reaction. This endpoint requires the `MANAGE_MESSAGES` permission to be present on the current user. Returns a 204 empty response on success. Fires a [Message Reaction Remove](/docs/events/gateway-events#message-reaction-remove) Gateway event.
+Deletes another user's reaction. This endpoint requires the `MANAGE_MESSAGES` permission to be present on the current user. Returns a 204 empty response on success. Fires a [Message Reaction Remove](/developers/docs/events/gateway-events#message-reaction-remove) Gateway event.
The `emoji` must be [URL Encoded](https://en.wikipedia.org/wiki/Percent-encoding) or the request will fail with `10014: Unknown Emoji`. To use custom emoji, you must encode it in the format `name:id` with the emoji name and emoji id.
## Get Reactions
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/docs/resources/emoji#emoji-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/developers/docs/resources/emoji#emoji-object)
-Get a list of users that reacted with this emoji. Returns an array of [user](/docs/resources/user#user-object) objects on success.
+Get a list of users that reacted with this emoji. Returns an array of [user](/developers/docs/resources/user#user-object) objects on success.
The `emoji` must be [URL Encoded](https://en.wikipedia.org/wiki/Percent-encoding) or the request will fail with `10014: Unknown Emoji`. To use custom emoji, you must encode it in the format `name:id` with the emoji name and emoji id.
+/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)/reactions
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)/reactions
-Deletes all reactions on a message. This endpoint requires the `MANAGE_MESSAGES` permission to be present on the current user. Fires a [Message Reaction Remove All](/docs/events/gateway-events#message-reaction-remove-all) Gateway event.
+Deletes all reactions on a message. This endpoint requires the `MANAGE_MESSAGES` permission to be present on the current user. Fires a [Message Reaction Remove All](/developers/docs/events/gateway-events#message-reaction-remove-all) Gateway event.
## Delete All Reactions for Emoji
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/docs/resources/emoji#emoji-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)/reactions/[\{emoji.id\}](/developers/docs/resources/emoji#emoji-object)
-Deletes all the reactions for a given emoji on a message. This endpoint requires the `MANAGE_MESSAGES` permission to be present on the current user. Fires a [Message Reaction Remove Emoji](/docs/events/gateway-events#message-reaction-remove-emoji) Gateway event.
+Deletes all the reactions for a given emoji on a message. This endpoint requires the `MANAGE_MESSAGES` permission to be present on the current user. Fires a [Message Reaction Remove Emoji](/developers/docs/events/gateway-events#message-reaction-remove-emoji) Gateway event.
The `emoji` must be [URL Encoded](https://en.wikipedia.org/wiki/Percent-encoding) or the request will fail with `10014: Unknown Emoji`. To use custom emoji, you must encode it in the format `name:id` with the emoji name and emoji id.
## Edit Message
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)
Edit a previously sent message. The fields `content`, `embeds`, `flags` and `components` can be edited by the original message author. Other users can only edit `flags` and only if they have the `MANAGE_MESSAGES` permission in the corresponding channel. When specifying flags, ensure to include all previously set flags/bits in addition to ones that you are modifying. Only `flags` documented in the table below may be modified by users (unsupported flag changes are currently ignored without error).
When the `content` field is edited, the arrays `mentions` and `mention_roles` and the boolean `mention_everyone` in the message object will be reconstructed from scratch based on the new content. When the message flag `IS_COMPONENTS_V2` is set, the reconstructed arrays and boolean are based on the edited content in the `components` array. The `allowed_mentions` field of the edit request controls how this happens. If there is no explicit `allowed_mentions` in the edit request, the content will be parsed with _default_ allowances, that is, without regard to whether or not an `allowed_mentions` was present in the request that originally created the message.
-Returns a [message](/docs/resources/message#message-object) object. Fires a [Message Update](/docs/events/gateway-events#message-update) Gateway event.
+Returns a [message](/developers/docs/resources/message#message-object) object. Fires a [Message Update](/developers/docs/events/gateway-events#message-update) Gateway event.
-Refer to [Uploading Files](/docs/reference#uploading-files) for details on attachments and `multipart/form-data` requests.
+Refer to [Uploading Files](/developers/docs/reference#uploading-files) for details on attachments and `multipart/form-data` requests.
Any provided files will be **appended** to the message. To remove or replace files you will have to supply the `attachments` field which specifies the files to retain on the message after edit.
-:::warn
+
Starting with API v10, the `attachments` array must contain all attachments that should be present after edit, including **retained and new** attachments provided in the request body.
-:::
+
-:::info
+
All parameters to this endpoint are optional and nullable.
-:::
+
+/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)
-Delete a message. If operating on a guild channel and trying to delete a message that was not sent by the current user, this endpoint requires the `MANAGE_MESSAGES` permission. Returns a 204 empty response on success. Fires a [Message Delete](/docs/events/gateway-events#message-delete) Gateway event.
+Delete a message. If operating on a guild channel and trying to delete a message that was not sent by the current user, this endpoint requires the `MANAGE_MESSAGES` permission. Returns a 204 empty response on success. Fires a [Message Delete](/developers/docs/events/gateway-events#message-delete) Gateway event.
-:::info
+
This endpoint supports the `X-Audit-Log-Reason` header.
-:::
+
## Bulk Delete Messages
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/bulk-delete
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/bulk-delete
-Delete multiple messages in a single request. This endpoint can only be used on guild channels and requires the `MANAGE_MESSAGES` permission. Returns a 204 empty response on success. Fires a [Message Delete Bulk](/docs/events/gateway-events#message-delete-bulk) Gateway event.
+Delete multiple messages in a single request. This endpoint can only be used on guild channels and requires the `MANAGE_MESSAGES` permission. Returns a 204 empty response on success. Fires a [Message Delete Bulk](/developers/docs/events/gateway-events#message-delete-bulk) Gateway event.
Any message IDs given that do not exist or are invalid will count towards the minimum and maximum message count (currently 2 and 100 respectively).
-:::warn
+
This endpoint will not delete messages older than 2 weeks, and will fail with a 400 BAD REQUEST if any message provided is older than that or if any duplicate message IDs are provided.
-:::
+
-:::info
+
This endpoint supports the `X-Audit-Log-Reason` header.
-:::
+
+/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/pins
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/pins
Retrieves the list of pins in a channel. Requires the `VIEW_CHANNEL` permission. If the user is missing the `READ_MESSAGE_HISTORY` permission in the channel, then no pins will be returned.
+/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/pins/[\{message.id\}](/docs/resources/message#message-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/pins/[\{message.id\}](/developers/docs/resources/message#message-object)
-Pin a message in a channel. Requires the `PIN_MESSAGES` permission. Fires a [Channel Pins Update](/docs/events/gateway-events#channel-pins-update) Gateway event.
+Pin a message in a channel. Requires the `PIN_MESSAGES` permission. Fires a [Channel Pins Update](/developers/docs/events/gateway-events#channel-pins-update) Gateway event.
-:::info
+
This endpoint supports the `X-Audit-Log-Reason` header.
-:::
+
## Unpin Message
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/pins/[\{message.id\}](/docs/resources/message#message-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/messages/pins/[\{message.id\}](/developers/docs/resources/message#message-object)
-Unpin a message in a channel. Requires the `PIN_MESSAGES` permission. Returns a 204 empty response on success. Fires a [Channel Pins Update](/docs/events/gateway-events#channel-pins-update) Gateway event.
+Unpin a message in a channel. Requires the `PIN_MESSAGES` permission. Returns a 204 empty response on success. Fires a [Channel Pins Update](/developers/docs/events/gateway-events#channel-pins-update) Gateway event.
-:::info
+
This endpoint supports the `X-Audit-Log-Reason` header.
-:::
+
## Get Pinned Messages (deprecated)
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/pins
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/pins
-Gets the first 50 pinned messages in a channel, returning an array of [message](/docs/resources/message#message-object) objects on success.
-This endpoint is deprecated. Use [Get Channel Pins](/docs/resources/message#get-channel-pins) instead.
+Gets the first 50 pinned messages in a channel, returning an array of [message](/developers/docs/resources/message#message-object) objects on success.
+This endpoint is deprecated. Use [Get Channel Pins](/developers/docs/resources/message#get-channel-pins) instead.
## Pin Message (deprecated)
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/pins/[\{message.id\}](/docs/resources/message#message-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/pins/[\{message.id\}](/developers/docs/resources/message#message-object)
-This endpoint is deprecated. Use [Pin Message](/docs/resources/message#pin-message) instead.
+This endpoint is deprecated. Use [Pin Message](/developers/docs/resources/message#pin-message) instead.
## Unpin Message (deprecated)
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/pins/[\{message.id\}](/docs/resources/message#message-object)
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/pins/[\{message.id\}](/developers/docs/resources/message#message-object)
-This endpoint is deprecated. Use [Unpin Message](/docs/resources/message#unpin-message) instead.
+This endpoint is deprecated. Use [Unpin Message](/developers/docs/resources/message#unpin-message) instead.
diff --git a/discord/developers/docs/resources/poll.mdx b/discord/developers/docs/resources/poll.mdx
new file mode 100644
index 0000000000..8c955562fe
--- /dev/null
+++ b/discord/developers/docs/resources/poll.mdx
@@ -0,0 +1,158 @@
+---
+title: Poll Resource
+sidebarTitle: Poll
+description: Reference for Discord poll objects and management endpoints.
+---
+
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+import {Route} from '/snippets/route.jsx'
+
+A poll is... well... a poll! It holds information about a poll!
+
+
+
+### Poll Object
+
+The poll object has a lot of levels and nested structures. It was also designed
+to support future extensibility, so some fields may appear to be more complex than
+necessary.
+
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/polls/[\{message.id\}](/developers/docs/resources/message#message-object)/answers/[\{answer_id\}](/developers/docs/resources/poll#poll-answer-object)
+
+Get a list of users that voted for this specific answer.
+
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/polls/[\{message.id\}](/developers/docs/resources/message#message-object)/expire
+
+Immediately ends the poll. You cannot end polls from other users.
+
+Returns a [message](/developers/docs/resources/message#message-object) object. Fires a [Message Update](/developers/docs/events/gateway-events#message-update) Gateway event.
diff --git a/docs/resources/sku.mdx b/discord/developers/docs/resources/sku.mdx
similarity index 80%
rename from docs/resources/sku.mdx
rename to discord/developers/docs/resources/sku.mdx
index d7f7ad96e1..268af8cab6 100644
--- a/docs/resources/sku.mdx
+++ b/discord/developers/docs/resources/sku.mdx
@@ -1,24 +1,29 @@
---
-sidebar_label: SKU
+title: SKU Resource
+sidebarTitle: SKU
+description: Reference for Discord SKU objects that represent premium app offerings.
---
-# SKU Resource
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+import {Route} from '/snippets/route.jsx'
SKUs (stock-keeping units) in Discord represent premium offerings that can be made available to your application's users or guilds.
### SKU Object
+/applications/[\{application.id\}](/docs/resources/application#application-object)/skus
+/applications/[\{application.id\}](/developers/docs/resources/application#application-object)/skus
Returns all SKUs for a given application.
-:::info
+
Because of how our SKU and subscription systems work, you will see two SKUs for your subscription offering. For integration and testing entitlements for Subscriptions, you should use the SKU with `type: 5`.
-:::
+
```json
[
diff --git a/discord/developers/docs/resources/soundboard.mdx b/discord/developers/docs/resources/soundboard.mdx
new file mode 100644
index 0000000000..7a8169a2bf
--- /dev/null
+++ b/discord/developers/docs/resources/soundboard.mdx
@@ -0,0 +1,160 @@
+---
+title: Soundboard Resource
+sidebarTitle: Soundboard
+description: Reference for Discord soundboard objects and management endpoints.
+---
+
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+import {Route} from '/snippets/route.jsx'
+
+Users can play soundboard sounds in voice channels, triggering a [Voice Channel Effect Send](/developers/docs/events/gateway-events#voice-channel-effect-send) Gateway event for users connected to the voice channel.
+
+There is a set of [default sounds](/developers/docs/resources/soundboard#list-default-soundboard-sounds) available to all users. Soundboard sounds can also be [created in a guild](/developers/docs/resources/soundboard#create-guild-soundboard-sound); users will be able to use the sounds in the guild, and Nitro subscribers can use them in all guilds.
+
+Soundboard sounds in a set of guilds can be retrieved over the Gateway using [Request Soundboard Sounds](/developers/docs/events/gateway-events#request-soundboard-sounds).
+
+### Soundboard Sound Object
+
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/send-soundboard-sound
+
+Send a soundboard sound to a voice channel the user is connected to. Fires a [Voice Channel Effect Send](/developers/docs/events/gateway-events#voice-channel-effect-send) Gateway event.
+
+Requires the `SPEAK` and `USE_SOUNDBOARD` permissions, and also the `USE_EXTERNAL_SOUNDS` permission if the sound is from a different server. Additionally, requires the user to be connected to the voice channel, having a [voice state](/developers/docs/resources/voice#voice-state-object) without `deaf`, `self_deaf`, `mute`, or `suppress` enabled.
+
+/soundboard-default-sounds
+
+Returns an array of [soundboard sound](/developers/docs/resources/soundboard#soundboard-sound-object) objects that can be used by all users.
+
+## List Guild Soundboard Sounds
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/soundboard-sounds
+
+Returns a list of the guild's soundboard sounds. Includes `user` fields if the bot has the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission.
+
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/soundboard-sounds/[\{sound.id\}](/developers/docs/resources/soundboard#soundboard-sound-object)
+
+Returns a [soundboard sound](/developers/docs/resources/soundboard#soundboard-sound-object) object for the given sound id. Includes the `user` field if the bot has the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission.
+
+## Create Guild Soundboard Sound
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/soundboard-sounds
+
+Create a new soundboard sound for the guild. Requires the `CREATE_GUILD_EXPRESSIONS` permission. Returns the new [soundboard sound](/developers/docs/resources/soundboard#soundboard-sound-object) object on success. Fires a [Guild Soundboard Sound Create](/developers/docs/events/gateway-events#guild-soundboard-sound-create) Gateway event.
+
+
+Soundboard sounds have a max file size of 512kb and a max duration of 5.2 seconds.
+
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
+
+###### JSON /guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/soundboard-sounds/[\{sound.id\}](/developers/docs/resources/soundboard#soundboard-sound-object)
+
+Modify the given soundboard sound. For sounds created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other sounds, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns the updated [soundboard sound](/developers/docs/resources/soundboard#soundboard-sound-object) object on success. Fires a [Guild Soundboard Sound Update](/developers/docs/events/gateway-events#guild-soundboard-sound-update) Gateway event.
+
+
+All parameters to this endpoint are optional.
+
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
+
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/soundboard-sounds/[\{sound.id\}](/developers/docs/resources/soundboard#soundboard-sound-object)
+
+Delete the given soundboard sound. For sounds created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other sounds, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns `204 No Content` on success. Fires a [Guild Soundboard Sound Delete](/developers/docs/events/gateway-events#guild-soundboard-sound-delete) Gateway event.
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
diff --git a/docs/resources/stage-instance.mdx b/discord/developers/docs/resources/stage-instance.mdx
similarity index 61%
rename from docs/resources/stage-instance.mdx
rename to discord/developers/docs/resources/stage-instance.mdx
index 81772c2d0d..13df4b418c 100644
--- a/docs/resources/stage-instance.mdx
+++ b/discord/developers/docs/resources/stage-instance.mdx
@@ -1,25 +1,30 @@
---
-sidebar_label: Stage Instance
+title: Stage Instance Resource
+sidebarTitle: Stage Instance
+description: Reference for Discord stage instance objects for managing live audio events.
---
-# Stage Instance Resource
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+import {Route} from '/snippets/route.jsx'
-A _Stage Instance_ holds information about a live stage.
+A Stage Instance holds information about a live stage.
### Stage Instance Object
+/stage-instances
-Creates a new Stage instance associated to a Stage channel. Returns that [Stage instance](/docs/resources/stage-instance#stage-instance-object-stage-instance-structure). Fires a [Stage Instance Create](/docs/events/gateway-events#stage-instance-create) Gateway event.
+Creates a new Stage instance associated to a Stage channel. Returns that [Stage instance](/developers/docs/resources/stage-instance#stage-instance-object-stage-instance-structure). Fires a [Stage Instance Create](/developers/docs/events/gateway-events#stage-instance-create) Gateway event.
Requires the user to be a moderator of the Stage channel.
-:::info
+
This endpoint supports the `X-Audit-Log-Reason` header.
-:::
+
+/stage-instances/[\{channel.id\}](/docs/resources/channel#channel-object)
+/stage-instances/[\{channel.id\}](/developers/docs/resources/channel#channel-object)
Gets the stage instance associated with the Stage channel, if it exists.
## Modify Stage Instance
-/stage-instances/[\{channel.id\}](/docs/resources/channel#channel-object)
+/stage-instances/[\{channel.id\}](/developers/docs/resources/channel#channel-object)
-Updates fields of an existing Stage instance. Returns the updated [Stage instance](/docs/resources/stage-instance#stage-instance-object-stage-instance-structure). Fires a [Stage Instance Update](/docs/events/gateway-events#stage-instance-update) Gateway event.
+Updates fields of an existing Stage instance. Returns the updated [Stage instance](/developers/docs/resources/stage-instance#stage-instance-object-stage-instance-structure). Fires a [Stage Instance Update](/developers/docs/events/gateway-events#stage-instance-update) Gateway event.
Requires the user to be a moderator of the Stage channel.
-:::info
+
This endpoint supports the `X-Audit-Log-Reason` header.
-:::
+
+/stage-instances/[\{channel.id\}](/docs/resources/channel#channel-object)
+/stage-instances/[\{channel.id\}](/developers/docs/resources/channel#channel-object)
-Deletes the Stage instance. Returns `204 No Content`. Fires a [Stage Instance Delete](/docs/events/gateway-events#stage-instance-delete) Gateway event.
+Deletes the Stage instance. Returns `204 No Content`. Fires a [Stage Instance Delete](/developers/docs/events/gateway-events#stage-instance-delete) Gateway event.
Requires the user to be a moderator of the Stage channel.
-:::info
+
This endpoint supports the `X-Audit-Log-Reason` header.
-:::
+
diff --git a/discord/developers/docs/resources/sticker.mdx b/discord/developers/docs/resources/sticker.mdx
new file mode 100644
index 0000000000..ccc025fb49
--- /dev/null
+++ b/discord/developers/docs/resources/sticker.mdx
@@ -0,0 +1,202 @@
+---
+title: Sticker Resource
+sidebarTitle: Sticker
+description: Reference for Discord sticker objects and management endpoints.
+---
+
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+import {Route} from '/snippets/route.jsx'
+
+### Sticker Object
+
+Represents a sticker that can be sent in messages.
+
+/stickers/[\{sticker.id\}](/developers/docs/resources/sticker#sticker-object)
+
+Returns a [sticker](/developers/docs/resources/sticker#sticker-object) object for the given sticker ID.
+
+## List Sticker Packs
+/sticker-packs
+
+Returns a list of available sticker packs.
+
+/sticker-packs/[\{pack.id\}](/developers/docs/resources/sticker#sticker-pack-object)
+
+Returns a [sticker pack](/developers/docs/resources/sticker#sticker-pack-object) object for the given sticker pack ID.
+
+## List Guild Stickers
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/stickers
+
+Returns an array of [sticker](/developers/docs/resources/sticker#sticker-object) objects for the given guild. Includes `user` fields if the bot has the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission.
+
+## Get Guild Sticker
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/stickers/[\{sticker.id\}](/developers/docs/resources/sticker#sticker-object)
+
+Returns a [sticker](/developers/docs/resources/sticker#sticker-object) object for the given guild and sticker IDs. Includes the `user` field if the bot has the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission.
+
+## Create Guild Sticker
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/stickers
+
+Create a new sticker for the guild. Send a `multipart/form-data` body. Requires the `CREATE_GUILD_EXPRESSIONS` permission. Returns the new [sticker](/developers/docs/resources/sticker#sticker-object) object on success. Fires a [Guild Stickers Update](/developers/docs/events/gateway-events#guild-stickers-update) Gateway event.
+
+Every guilds has five free sticker slots by default, and each Boost level will grant access to more slots.
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
+
+
+Lottie stickers can only be uploaded on guilds that have either the `VERIFIED` and/or the `PARTNERED` [guild feature](/developers/docs/resources/guild#guild-object-guild-features).
+
+
+
+Uploaded stickers are constrained to 5 seconds in length for animated stickers, and 320 x 320 pixels.
+
+
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/stickers/[\{sticker.id\}](/developers/docs/resources/sticker#sticker-object)
+
+Modify the given sticker. For stickers created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other stickers, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns the updated [sticker](/developers/docs/resources/sticker#sticker-object) object on success. Fires a [Guild Stickers Update](/developers/docs/events/gateway-events#guild-stickers-update) Gateway event.
+
+
+All parameters to this endpoint are optional.
+
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
+
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/stickers/[\{sticker.id\}](/developers/docs/resources/sticker#sticker-object)
+
+Delete the given sticker. For stickers created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other stickers, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns `204 No Content` on success. Fires a [Guild Stickers Update](/developers/docs/events/gateway-events#guild-stickers-update) Gateway event.
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
diff --git a/docs/resources/subscription.mdx b/discord/developers/docs/resources/subscription.mdx
similarity index 83%
rename from docs/resources/subscription.mdx
rename to discord/developers/docs/resources/subscription.mdx
index 68e7161300..51d18312d0 100644
--- a/docs/resources/subscription.mdx
+++ b/discord/developers/docs/resources/subscription.mdx
@@ -1,8 +1,10 @@
---
-sidebar_label: Subscription
+title: Subscription Resource
+sidebarTitle: Subscription
+description: Reference for Discord subscription objects that represent recurring payments.
---
-# Subscription Resource
+import {Route} from '/snippets/route.jsx'
Subscriptions in Discord represent a user making recurring payments for at least one SKU over an ongoing period. Successful payments grant the user access to entitlements associated with the SKU.
@@ -49,9 +51,9 @@ If the user cancels the subscription, the subscription will enter the `ENDING` s
| ENDING | 1 | Subscription is active but will not renew. |
| INACTIVE | 2 | Subscription is inactive and not being charged. |
-:::info
-Subscription status should not be used to grant perks. Use [entitlements](/docs/resources/entitlement#entitlement-object) as an indication of whether a user should have access to a specific SKU. See our guide on [Implementing App Subscriptions](/docs/monetization/implementing-app-subscriptions) for more information.
-:::
+
+Subscription status should not be used to grant perks. Use [entitlements](/developers/docs/resources/entitlement#entitlement-object) as an indication of whether a user should have access to a specific SKU. See our guide on [Implementing App Subscriptions](/developers/docs/monetization/implementing-app-subscriptions) for more information.
+
Subscriptions can start and change between any of these statuses within the current period. A subscription can be `ACTIVE` outside its current period or `INACTIVE` within its current period.
@@ -61,9 +63,9 @@ Some examples of this behavior include:
- A refund or chargeback during the current period would make the subscription `INACTIVE`.
## List SKU Subscriptions
-/skus/[\{sku.id\}](/docs/resources/sku#sku-object)/subscriptions
+/skus/[\{sku.id\}](/developers/docs/resources/sku#sku-object)/subscriptions
-Returns all subscriptions containing the SKU, filtered by user. Returns a list of [subscription](/docs/resources/subscription#subscription-object) objects.
+Returns all subscriptions containing the SKU, filtered by user. Returns a list of [subscription](/developers/docs/resources/subscription#subscription-object) objects.
### Query String Params
@@ -75,6 +77,6 @@ Returns all subscriptions containing the SKU, filtered by user. Returns a list o
| user_id? | snowflake | User ID for which to return subscriptions. Required except for OAuth queries. | absent |
## Get SKU Subscription
-/skus/[\{sku.id\}](/docs/resources/sku#sku-object)/subscriptions/[\{subscription.id\}](/docs/resources/subscription#subscription-object)
+/skus/[\{sku.id\}](/developers/docs/resources/sku#sku-object)/subscriptions/[\{subscription.id\}](/developers/docs/resources/subscription#subscription-object)
-Get a subscription by its ID. Returns a [subscription](/docs/resources/subscription#subscription-object) object.
\ No newline at end of file
+Get a subscription by its ID. Returns a [subscription](/developers/docs/resources/subscription#subscription-object) object.
\ No newline at end of file
diff --git a/docs/resources/user.mdx b/discord/developers/docs/resources/user.mdx
similarity index 55%
rename from docs/resources/user.mdx
rename to discord/developers/docs/resources/user.mdx
index 0036189b68..74a4b002dd 100644
--- a/docs/resources/user.mdx
+++ b/discord/developers/docs/resources/user.mdx
@@ -1,8 +1,11 @@
---
-sidebar_label: User
+title: User Resource
+sidebarTitle: User
+description: Reference for Discord user objects and management endpoints.
---
-# Users Resource
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+import {Route} from '/snippets/route.jsx'
Users in Discord are generally considered the base entity. Users can spawn across the entire platform, be members of
guilds, participate in text and voice chat, and much more. Users are separated by a distinction of "bot" vs "normal." Although they are similar, bot users are automated users that are "owned" by another user. Unlike normal users, bot users do
@@ -26,30 +29,32 @@ There are other rules and restrictions not shared here for the sake of spam and
### User Object
+/users/@me
-Returns the [user](/docs/resources/user#user-object) object of the requester's account. For OAuth2, this requires the `identify` scope, which will return the object _without_ an email, and optionally the `email` scope, which returns the object _with_ an email if the user has one.
+Returns the [user](/developers/docs/resources/user#user-object) object of the requester's account. For OAuth2, this requires the `identify` scope, which will return the object _without_ an email, and optionally the `email` scope, which returns the object _with_ an email if the user has one.
## Get User
-/users/[\{user.id\}](/docs/resources/user#user-object)
+/users/[\{user.id\}](/developers/docs/resources/user#user-object)
-Returns a [user](/docs/resources/user#user-object) object for a given user ID.
+Returns a [user](/developers/docs/resources/user#user-object) object for a given user ID.
## Modify Current User
/users/@me
-Modify the requester's user account settings. Returns a [user](/docs/resources/user#user-object) object on success. Fires a [User Update](/docs/events/gateway-events#user-update) Gateway event.
+Modify the requester's user account settings. Returns a [user](/developers/docs/resources/user#user-object) object on success. Fires a [User Update](/developers/docs/events/gateway-events#user-update) Gateway event.
-:::info
+
All parameters to this endpoint are optional.
-:::
+
+/users/@me/guilds
-Returns a list of partial [guild](/docs/resources/guild#guild-object) objects the current user is a member of. For OAuth2, requires the `guilds` scope.
+Returns a list of partial [guild](/developers/docs/resources/guild#guild-object) objects the current user is a member of. For OAuth2, requires the `guilds` scope.
+
This endpoint returns 200 guilds by default, which is the maximum number of guilds a non-bot user can join. Therefore, pagination is **not needed** for integrations that need to get a list of the users' guilds.
-:::
+
+/users/@me/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/member
+/users/@me/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/member
-Returns a [guild member](/docs/resources/guild#guild-member-object) object for the current user. Requires the `guilds.members.read` OAuth2 scope.
+Returns a [guild member](/developers/docs/resources/guild#guild-member-object) object for the current user. Requires the `guilds.members.read` OAuth2 scope.
## Leave Guild
-/users/@me/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)
+/users/@me/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)
-Leave a guild. Returns a 204 empty response on success. Fires a [Guild Delete](/docs/events/gateway-events#guild-delete) Gateway event and a [Guild Member Remove](/docs/events/gateway-events#guild-member-remove) Gateway event.
+Leave a guild. Returns a 204 empty response on success. Fires a [Guild Delete](/developers/docs/events/gateway-events#guild-delete) Gateway event and a [Guild Member Remove](/developers/docs/events/gateway-events#guild-member-remove) Gateway event.
## Create DM
/users/@me/channels
-Create a new DM channel with a user. Returns a [DM channel](/docs/resources/channel#channel-object) object (if one already exists, it will be returned instead).
+Create a new DM channel with a user. Returns a [DM channel](/developers/docs/resources/channel#channel-object) object (if one already exists, it will be returned instead).
-:::warn
+
You should not use this endpoint to DM everyone in a server about something. DMs should generally be initiated by a user action. If you open a significant amount of DMs too quickly, your bot may be rate limited or blocked from opening new ones.
-:::
+
+/users/@me/channels
-Create a new group DM channel with multiple users. Returns a [DM channel](/docs/resources/channel#channel-object) object. This endpoint was intended to be used with the now-deprecated GameBridge SDK. Fires a [Channel Create](/docs/events/gateway-events#channel-create) Gateway event.
+Create a new group DM channel with multiple users. Returns a [DM channel](/developers/docs/resources/channel#channel-object) object. This endpoint was intended to be used with the now-deprecated GameBridge SDK. Fires a [Channel Create](/developers/docs/events/gateway-events#channel-create) Gateway event.
-:::warn
+
This endpoint is limited to 10 active group DMs.
-:::
+
+/users/@me/connections
-Returns a list of [connection](/docs/resources/user#connection-object) objects. Requires the `connections` OAuth2 scope.
+Returns a list of [connection](/developers/docs/resources/user#connection-object) objects. Requires the `connections` OAuth2 scope.
## Get Current User Application Role Connection
-/users/@me/applications/[\{application.id\}](/docs/resources/application#application-object)/role-connection
+/users/@me/applications/[\{application.id\}](/developers/docs/resources/application#application-object)/role-connection
-Returns the [application role connection](/docs/resources/user#application-role-connection-object) for the user. Requires an OAuth2 access token with `role_connections.write` scope for the application specified in the path.
+Returns the [application role connection](/developers/docs/resources/user#application-role-connection-object) for the user. Requires an OAuth2 access token with `role_connections.write` scope for the application specified in the path.
## Update Current User Application Role Connection
-/users/@me/applications/[\{application.id\}](/docs/resources/application#application-object)/role-connection
+/users/@me/applications/[\{application.id\}](/developers/docs/resources/application#application-object)/role-connection
-Updates and returns the [application role connection](/docs/resources/user#application-role-connection-object) for the user. Requires an OAuth2 access token with `role_connections.write` scope for the application specified in the path.
+Updates and returns the [application role connection](/developers/docs/resources/user#application-role-connection-object) for the user. Requires an OAuth2 access token with `role_connections.write` scope for the application specified in the path.
+/voice/regions
-Returns an array of [voice region](/docs/resources/voice#voice-region-object) objects that can be used when setting a voice or stage channel's [`rtc_region`](/docs/resources/channel#channel-object-channel-structure).
+Returns an array of [voice region](/developers/docs/resources/voice#voice-region-object) objects that can be used when setting a voice or stage channel's [`rtc_region`](/developers/docs/resources/channel#channel-object-channel-structure).
## Get Current User Voice State
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/voice-states/@me
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/voice-states/@me
-Returns the current user's [voice state](/docs/resources/voice#voice-state-object) in the guild.
+Returns the current user's [voice state](/developers/docs/resources/voice#voice-state-object) in the guild.
## Get User Voice State
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/voice-states/[\{user.id\}](/docs/resources/user#user-object)
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/voice-states/[\{user.id\}](/developers/docs/resources/user#user-object)
-Returns the specified user's [voice state](/docs/resources/voice#voice-state-object) in the guild.
+Returns the specified user's [voice state](/developers/docs/resources/voice#voice-state-object) in the guild.
## Modify Current User Voice State
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/voice-states/@me
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/voice-states/@me
-Updates the current user's voice state. Returns `204 No Content` on success. Fires a [Voice State Update](/docs/events/gateway-events#voice-state-update) Gateway event.
+Updates the current user's voice state. Returns `204 No Content` on success. Fires a [Voice State Update](/developers/docs/events/gateway-events#voice-state-update) Gateway event.
+/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/voice-states/[\{user.id\}](/docs/resources/user#user-object)
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/voice-states/[\{user.id\}](/developers/docs/resources/user#user-object)
-Updates another user's voice state. Returns `204 No Content` on success. Fires a [Voice State Update](/docs/events/gateway-events#voice-state-update) Gateway event.
+Updates another user's voice state. Returns `204 No Content` on success. Fires a [Voice State Update](/developers/docs/events/gateway-events#voice-state-update) Gateway event.
+
+These types don't include [webhook events](/developers/docs/events/webhook-events), which are outgoing webhooks sent to your app by Discord. See [Webhook Events](/developers/docs/events/webhook-events) for details.
+
+
+| Value | Name | Description |
+|-------|------------------|----------------------------------------------------------------------------------------------------------------|
+| 1 | Incoming | Incoming Webhooks can post messages to channels with a generated token |
+| 2 | Channel Follower | Channel Follower Webhooks are internal webhooks used with Channel Following to post new messages into channels |
+| 3 | Application | Application webhooks are webhooks used with Interactions |
+
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/webhooks
+
+Creates a new webhook and returns a [webhook](/developers/docs/resources/webhook#webhook-object) object on success. Requires the `MANAGE_WEBHOOKS` permission. Fires a [Webhooks Update](/developers/docs/events/gateway-events#webhooks-update) Gateway event.
+
+An error will be returned if a webhook name (`name`) is not valid. A webhook name is valid if:
+
+- It does not contain the substrings `clyde` or `discord` (case-insensitive)
+- It follows the nickname guidelines in the [Usernames and Nicknames](/developers/docs/resources/user#usernames-and-nicknames) documentation, with an exception that webhook names can be up to 80 characters
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
+
+/channels/[\{channel.id\}](/developers/docs/resources/channel#channel-object)/webhooks
+
+Returns a list of channel [webhook](/developers/docs/resources/webhook#webhook-object) objects. Requires the `MANAGE_WEBHOOKS` permission.
+
+## Get Guild Webhooks
+/guilds/[\{guild.id\}](/developers/docs/resources/guild#guild-object)/webhooks
+
+Returns a list of guild [webhook](/developers/docs/resources/webhook#webhook-object) objects. Requires the `MANAGE_WEBHOOKS` permission.
+
+## Get Webhook
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)
+
+Returns the new [webhook](/developers/docs/resources/webhook#webhook-object) object for the given id.
+
+This request requires the `MANAGE_WEBHOOKS` permission unless the application making the request owns the
+webhook. [(see: webhook.application_id)](/developers/docs/resources/webhook#webhook-object)
+
+## Get Webhook with Token
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/developers/docs/resources/webhook#webhook-object)
+
+Same as above, except this call does not require authentication and returns no user in the webhook object.
+
+## Modify Webhook
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)
+
+Modify a webhook. Requires the `MANAGE_WEBHOOKS` permission. Returns the updated [webhook](/developers/docs/resources/webhook#webhook-object) object on success. Fires a [Webhooks Update](/developers/docs/events/gateway-events#webhooks-update) Gateway event.
+
+
+All parameters to this endpoint are optional
+
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
+
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/developers/docs/resources/webhook#webhook-object)
+
+Same as above, except this call does not require authentication, does not accept a `channel_id` parameter in the body, and does not return a user in the webhook object.
+
+## Delete Webhook
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)
+
+Delete a webhook permanently. Requires the `MANAGE_WEBHOOKS` permission. Returns a `204 No Content` response on success. Fires a [Webhooks Update](/developers/docs/events/gateway-events#webhooks-update) Gateway event.
+
+
+This endpoint supports the `X-Audit-Log-Reason` header.
+
+
+## Delete Webhook with Token
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/developers/docs/resources/webhook#webhook-object)
+
+Same as above, except this call does not require authentication.
+
+## Execute Webhook
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/developers/docs/resources/webhook#webhook-object)
+
+Refer to [Uploading Files](/developers/docs/reference#uploading-files) for details on attachments and `multipart/form-data` requests. Returns a message or `204 No Content` depending on the `wait` query parameter.
+
+
+Note that when sending a message, you must provide a value for at **least one of** `content`, `embeds`, `components`, `file`, or `poll`.
+
+
+
+If the webhook channel is a forum or media channel, you must provide either `thread_id` in the query string params, or `thread_name` in the JSON/form params. If `thread_id` is provided, the message will send in that thread. If `thread_name` is provided, a thread with that name will be created in the channel.
+
+
+
+Discord may strip certain characters from message content, like invalid unicode characters or characters which cause unexpected message formatting. If you are passing user-generated strings into message content, consider sanitizing the data to prevent unexpected behavior and using `allowed_mentions` to prevent unexpected mentions.
+
+
+
+For the webhook embed objects, you can set every field except `type` (it will be `rich` regardless of if you try to set it), `provider`, `video`, and any `height`, `width`, or `proxy_url` values for images.
+
+
+## Execute Slack-Compatible Webhook
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/developers/docs/resources/webhook#webhook-object)/slack
+
+Refer to [Slack's documentation](https://api.slack.com/incoming-webhooks) for more information. We do not support Slack's `channel`, `icon_emoji`, `mrkdwn`, or `mrkdwn_in` properties.
+
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/developers/docs/resources/webhook#webhook-object)/github
+
+[Add a new webhook](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks) to your GitHub repo (in the repo's settings), and use this endpoint as the "Payload URL." You can choose what events your Discord channel receives by choosing the "Let me select individual events" option and selecting individual events for the new webhook you're configuring. The supported [events](https://docs.github.com/en/webhooks/webhook-events-and-payloads) are `commit_comment`, `create`, `delete`, `fork`, `issue_comment`, `issues`, `member`, `public`, `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `release`, `watch`, `check_run`, `check_suite`, `discussion`, and `discussion_comment`.
+
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/developers/docs/resources/webhook#webhook-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)
+
+Returns a previously-sent webhook message from the same token. Returns a [message](/developers/docs/resources/message#message-object) object on success.
+
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/developers/docs/resources/webhook#webhook-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)
+
+Edits a previously-sent webhook message from the same token. Returns a [message](/developers/docs/resources/message#message-object) object on success.
+
+When the `content` field is edited, the arrays `mentions` and `mention_roles` and the boolean `mention_everyone` in the message object will be reconstructed from scratch based on the new content. When the message flag `IS_COMPONENTS_V2` is set, the reconstructed arrays and boolean are based on the edited content in the `components` array. The `allowed_mentions` field of the edit request controls how this happens. If there is no explicit `allowed_mentions` in the edit request, the content will be parsed with _default_ allowances, that is, without regard to whether or not an `allowed_mentions` was present in the request that originally created the message.
+
+Refer to [Uploading Files](/developers/docs/reference#uploading-files) for details on attachments and `multipart/form-data` requests.
+Any provided files will be **appended** to the message. To remove or replace files you will have to supply the `attachments` field which specifies the files to retain on the message after edit.
+
+
+Starting with API v10, the `attachments` array must contain all attachments that should be present after edit, including **retained and new** attachments provided in the request body.
+
+
+
+All parameters to this endpoint are optional and nullable.
+
+
+/webhooks/[\{webhook.id\}](/developers/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/developers/docs/resources/webhook#webhook-object)/messages/[\{message.id\}](/developers/docs/resources/message#message-object)
+
+Deletes a message that was created by the webhook. Returns a `204 No Content` response on success.
+
+
+Since all Activities presence data has an **Ask to Join** button, Join Invites are only applicable when building with the [Game SDK](/developers/docs/rich-presence/using-with-the-game-sdk)
+
- Have you successfully implemented join invites for your game if applicable?
- Does the state of the invite properly represent the party/group in-game with regards to:
diff --git a/discord/developers/docs/rich-presence/best-practices.mdx b/discord/developers/docs/rich-presence/best-practices.mdx
new file mode 100644
index 0000000000..782539e3ef
--- /dev/null
+++ b/discord/developers/docs/rich-presence/best-practices.mdx
@@ -0,0 +1,104 @@
+---
+title: Best Practices for Rich Presence
+sidebarTitle: Best Practices
+description: Best practices and guidelines for implementing effective Rich Presence.
+---
+
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+
+Rich Presence lets you display actionable data in a Discord user's profile about what they're up to in your game or app. This guide is intended to show some best practices on how to make that data the best it can be.
+
+If you don't already know about Rich Presence, read [the overview](/developers/docs/rich-presence/overview) first.
+
+
+Since all Activities presence data has an **Ask to Join** button, Join Invites are only applicable when building with the [Game SDK](/developers/docs/rich-presence/using-with-the-game-sdk)
+
+
+- Have you successfully implemented join invites for your game if applicable?
+- Does the state of the invite properly represent the party/group in-game with regards to:
+ - Size?
+ - Open slots?
+ - Discord _and_ non-Discord users in the party?
+- Are you able to post invites to Discord without any additional in-game setup or configuration?
+- Are you properly removing data from the presence payload when someone can no longer send invites?
+ - A Join secret should not be sent if the player can't invite anyone!
diff --git a/discord/developers/docs/rich-presence/overview.mdx b/discord/developers/docs/rich-presence/overview.mdx
new file mode 100644
index 0000000000..fd562c2406
--- /dev/null
+++ b/discord/developers/docs/rich-presence/overview.mdx
@@ -0,0 +1,109 @@
+---
+title: Overview of Rich Presence
+sidebarTitle: Overview
+description: Learn how to integrate Rich Presence to display activity information on user profiles.
+---
+
+
+
+Rich Presence lets you display actionable data in a Discord user's profile about what they're up to in your game or app. The data you choose to display is up to you—whether it's a user's score, the duration they've been playing your game, what they're listening to on your platform, or something else.
+
+---
+
+## Choosing an SDK
+
+There are three options when integrating Rich Presence. Depending on what you're building, you'll want to choose the right SDK for your project:
+
+- The **[Discord Social SDK](/developers/docs/rich-presence/overview#discord-social-sdk)** allows you to build social features into your game or app, including friends lists, game invites, and more.
+- The **[Embedded App SDK](/developers/docs/rich-presence/overview#embedded-app-sdk)** should be used if you're building an [Activity](/developers/docs/activities/overview) in Discord.
+- The **[Game SDK (legacy)](/developers/docs/rich-presence/overview#game-sdk)** can be used if you're building an off-platform game or app and you want to integrate it into Discord.
+
+All SDKs use similar underlying primitives (like the [`SET_ACTIVITY` RPC command](/developers/docs/topics/rpc#setactivity)), so a lot is the same between them. But there are a few differences, like feature compatibility, which is covered in the sections below.
+
+
+Rich Presence data appears publicly on your Discord profile, so during development you should use a test account that only belongs to your private development server(s).
+
+
+### Discord Social SDK
+
+The [Discord Social SDK](/developers/docs/discord-social-sdk/overview) is used for building social features directly into your game. When a user is playing your game, you can show what they're up to in their Discord profile and even prompt their friends to join in with game invites.
+
+When integrating Rich Presence with an off-platform game, data can be shown about what a user is up to in your game. A "Join" button can also be configured to allow a user's friends to jump into their game and enable sending game invites.
+
+[Read about using Rich Presence with the Discord Social SDK](/developers/docs/rich-presence/using-with-the-discord-social-sdk)
+
+### Embedded App SDK
+
+The [Embedded App SDK](/developers/docs/developer-tools/embedded-app-sdk) is used to build Activities, which are multiplayer games and social experiences hosted in an iframe within Discord. The SDK handles communication between Discord and the Activity and helps integrate platform features (like Rich Presence!).
+
+After a user joins an Activity, Rich Presence can be used to dynamically show data about what that user is doing or playing, as well as prompt others to join in and play along.
+
+[Read about using Rich Presence with the Embedded App SDK](/developers/docs/rich-presence/using-with-the-embedded-app-sdk)
+
+### Game SDK
+
+
+**The Game SDK has been archived.**
+
+We recommend using the [Discord Social SDK](/developers/docs/discord-social-sdk/overview) for new projects.
+
+Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/developers/docs/discord-social-sdk/overview) for new features and updates.
+
+
+The [Game SDK](/developers/docs/developer-tools/game-sdk) makes it easier to build 3rd party games and integrate them with Discord. While many features of the Game SDK are deprecated, it can still be used for a few use cases (like integrating Rich Presence!).
+
+When integrating Rich Presence with an off-platform game, data can be shown about what a user is up to in your game. A "Join" button can also be configured to allow a user's friends to jump into their game.
+
+[Read about using Rich Presence with the Game SDK](/developers/docs/rich-presence/using-with-the-game-sdk)
+
+## Adding Custom Art Assets
+
+While integrating Rich Presence, you'll likely want to upload custom art assets for your app. **For all Rich Presence assets, it's highly recommended to make them 1024 x 1024**.
+
+To add custom assets for Rich Presence, navigate to your [app's settings](https://discord.com/developers/applications) and click **Rich Presence** on the left-hand sidebar. On the **Art Assets** page, there are two different types of assets you can upload.
+
+### Invite Image
+
+The Rich Presence invite image appears when [invites](/developers/docs/developer-tools/game-sdk#sendinvite) are sent for a 3rd party game or app using the [Game SDK](/developers/docs/rich-presence/overview#game-sdk). After uploading an invite image for your app, you can see a preview of it to the right (under "IRL Invite Image Example").
+
+
+The invite image can be ignored if you're building using the [Embedded App SDK](/developers/docs/rich-presence/overview#embedded-app-sdk). Invites sent using the Embedded App SDK's[`openInviteDialog()`](/developers/docs/developer-tools/embedded-app-sdk#openinvitedialog) use the Activity's cover art.
+
+
+
+
+### Assets
+
+Up to 300 custom assets can be added for your app to use when setting Rich Presence for a Discord user. These assets can be anything that help orient others to what a user is doing inside of your Activity or 3rd party game.
+
+If you need more than 300 custom assets or want to use images stored somewhere else, you can also [specify an external URL](/developers/docs/events/gateway-events#activity-object-activity-asset-image) as long it still has the proper dimensions and size.
+
+
+For tips on choosing assets, take a look at the [Rich Presence best practices guide](/developers/docs/rich-presence/best-practices#have-interesting-expressive-art).
+
+
+When uploading Rich Presence assets, **the asset keys will automatically be changed to lowercase**. You can see this reflected in your app's settings after saving a newly-uploaded asset, and should keep it in mind when referencing any asset keys in your code.
+
+
+
+### Using the Visualizer
+
+
+The Rich Presence visualizer currently uses an outdated Discord UI, but can still be helpful as a quick-and-dirty reference for what your Rich Presence data will look like in Discord.
+
+
+In your app's settings, there's a Rich Presence visualizer to make it easier to see what your uploaded [assets](/developers/docs/rich-presence/overview#assets) will look like in the context of a Discord profile. To access the visualizer, navigate to your [app's settings](https://discord.com/developers/applications) and click **Rich Presence** on the left-hand sidebar. On the **Visualizer** page, you can fill out some custom strings, party information, and select your uploaded assets to see a preview.
+
+## Start Building
+
+
+
+ Guide on using Rich Presence in the Embedded App SDK while you're building an Activity
+
+
+ Guide on using Rich Presence in the Game SDK
+
+
+ Best practices and launch checklist for when you're integrating Rich Presence with your game or app
+
+
\ No newline at end of file
diff --git a/discord/developers/docs/rich-presence/using-with-the-discord-social-sdk.mdx b/discord/developers/docs/rich-presence/using-with-the-discord-social-sdk.mdx
new file mode 100644
index 0000000000..e4d2ea706e
--- /dev/null
+++ b/discord/developers/docs/rich-presence/using-with-the-discord-social-sdk.mdx
@@ -0,0 +1,29 @@
+---
+title: Using Rich Presence with the Discord Social SDK
+sidebarTitle: Using with the Discord Social SDK
+description: Learn how to implement Rich Presence features using the Discord Social SDK.
+---
+
+When developing a game, the [Discord Social SDK](/developers/docs/discord-social-sdk/overview) makes it easy to integrate Rich Presence to display details about what a user is up to inside of your game or social experience.
+
+
+Not sure if you should be building with the Discord Social SDK? Read through [Choosing an SDK](/developers/docs/rich-presence/overview#choosing-an-sdk) to understand your options when integrating Rich Presence with your app.
+
+
+## Understanding Rich Presence Data
+
+Before we dig in, it's helpful to understand what Rich Presence data you can set when updating a user's presence data. Let's just take a look at what we're working with:
+
+
+
+
+For tips on designing Rich Presence, take a look at the [Rich Presence best practices guide](/developers/docs/rich-presence/best-practices).
+
+
+## Setting Rich Presence Data
+
+Check out our [Setting Rich Presence](/developers/docs/discord-social-sdk/development-guides/setting-rich-presence) guide and our to learn how to set custom presence data for your players using the Discord Social SDK.
+
+- [Design Guidelines: Status & Rich Presence](/developers/docs/discord-social-sdk/design-guidelines/status-rich-presence)
+
+
diff --git a/discord/developers/docs/rich-presence/using-with-the-embedded-app-sdk.mdx b/discord/developers/docs/rich-presence/using-with-the-embedded-app-sdk.mdx
new file mode 100644
index 0000000000..8ac2bf7fd2
--- /dev/null
+++ b/discord/developers/docs/rich-presence/using-with-the-embedded-app-sdk.mdx
@@ -0,0 +1,158 @@
+---
+title: Using Rich Presence with the Embedded App SDK
+sidebarTitle: Using with the Embedded App SDK
+---
+
+When developing an [Activity](/developers/docs/activities/overview), the [Embedded App SDK](/developers/docs/developer-tools/embedded-app-sdk) makes it easy to integrate Rich Presence to display details about what a user is up to inside of your game or social experience.
+
+Rich Presence data can be thought of as an extension of your Activity—and leveling it up just a *little* makes it more interesting and relevant to the user playing your Activity (and their friends that might want to jump in and play). This guide provides an overview of the platform and technical knowledge you need to integrate Rich Presence with your existing Activity.
+
+
+Not sure if you should be building with the Embedded App SDK? Read through [Choosing an SDK](/developers/docs/rich-presence/overview#choosing-an-sdk) to understand your options when integrating Rich Presence with your app.
+
+
+The rest of the guide assumes you've already developed an [app](/developers/docs/quick-start/overview-of-apps) that can launch an Activity. If you aren't at that point quite yet, you should follow the guide on [building your first Activity](/developers/docs/activities/building-an-activity) before continuing.
+
+## Understanding Rich Presence Data
+
+### Default Rich Presence Data
+
+By default, when a user is connected to your Activity, the app's icon will appear on their profile. If the user viewing the profile has the ability to join, an "Ask to Join" button will be displayed as well.
+
+
+
+While this is okay, it's pretty limited and doesn't provide much context about what a user is actually *doing* inside of the Activity. In the following sections, we'll take a look at what richer and more actionable presence can look like.
+
+### Custom Rich Presence Data
+
+Now let's see what custom presence data can look like when a user joins your Activity. The [types for these fields](/developers/docs/rich-presence/using-with-the-embedded-app-sdk#setactivity-fields) and [examples](/developers/docs/rich-presence/using-with-the-embedded-app-sdk#setactivity-example) are in the sections below, but for now let's just get an idea of what we're working with:
+
+
+
+A few small things to note about the above image:
+1. `large_image` and `small_image` are both in the `assets` object, which you can see below in the [table below](/developers/docs/rich-presence/using-with-the-embedded-app-sdk#activity-partial-object). They're labeled with the object's keys to make it more clear how they appear in a Discord profile.
+2. You can't set App Name when setting presence—it's always the name configured in your [app's settings](https://discord.com/developers/applications).
+3. The state `(1 of max_party)` badge will only render when a party field is provided. Otherwise, state will be shown in a line of text below details.
+
+## Updating Presence
+
+When updating Rich Presence data using the Embedded App SDK, the only real command you need to use is **[`setActivity()`](/developers/docs/developer-tools/embedded-app-sdk#setactivity)**. Under the hood, `setActivity()` calls the RPC [`SET_ACTIVITY` command](/developers/docs/topics/rpc#setactivity) with the features and fields available when you're building an Activity.
+
+
+As you start exploring the Rich Presence docs, you'll start seeing the word "activity" a *lot*. The "activities" referenced in docs (like the [RPC ones](/developers/docs/topics/rpc#setactivity)) aren't related to the Activities you're building with the Embedded App SDK.
+
+When Rich Presence was introduced, the underlying object that contains presence data was called an "activity" (long before the Embedded App SDK), which is what the RPC [`SET_ACTIVITY` command](/developers/docs/topics/rpc#setactivity) is referencing. And that's *also* why the Embedded App SDK's wrapper around the RPC command is called `setActivity()` yet isn't really related to setting the state for the kind of Activity that *you're* building.
+
+We know, it's confusing ¯\\\_(⊙︿⊙)\_/¯ — the naming was logical at the time because it was really about the user's activity in a 3rd party game or service, but now it sorta feels like activity-ception. Understanding the nuances here aren't super important, and it's why we have guides like this one. But as they say...the more you (at least sort of) know.
+
+
+### rpc.activities.write Scope
+
+To display custom Rich Presence data for a user, your app will need to be authorized with the [`rpc.activities.write` scope](/developers/docs/topics/oauth2#shared-resources-oauth2-scopes) for that user.
+
+To request the scope, your [`authorize()`](/developers/docs/developer-tools/embedded-app-sdk#authorize) call might look something like this:
+
+
+
+
+The following example only focuses on calling `authorize()`. Follow the [Building an Activity guide](/developers/docs/activities/building-an-activity) for more details on topics like installing and instantiating the Embedded App SDK.
+
+
+```js
+// Authorize with Discord Client
+const { code } = await discordSdk.commands.authorize({
+ client_id: import.meta.env.VITE_DISCORD_CLIENT_ID,
+ response_type: "code",
+ state: "",
+ prompt: "none",
+ scope: [
+ "identify",
+ "rpc.activities.write"
+ ],
+});
+```
+
+
+### setActivity Fields
+
+When calling [`setActivity()`](/developers/docs/developer-tools/embedded-app-sdk#setactivity), you are expected to pass a partial [activity object](/developers/docs/events/gateway-events#activity-object-activity-structure).
+
+Below is a table with many of the available fields for the activity partial. Some were left out since they don't have an effect for Activities.
+
+#### Activity partial object
+
+
+All of the fields on the partial object are optional and nullable
+
+
+| field | type | description |
+|------------|-------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| type | integer | [Activity](/developers/docs/events/gateway-events#activity-object-activity-types) type, which determines the header text for the Rich Presence data |
+| state | string | User's current party status |
+| details | string | What the player is currently doing in your Activity |
+| timestamps | [timestamps](/developers/docs/events/gateway-events#activity-object-activity-timestamps) object | Unix timestamps to display start and/or end times |
+| assets | [assets](/developers/docs/events/gateway-events#activity-object-activity-assets) object | Images used for the Rich Presence data (and their hover texts) |
+| party | [party](/developers/docs/events/gateway-events#activity-object-activity-party) object | Information for the current party of the player |
+
+### setActivity Example
+
+Now let's take a look at more of a real example. Take a look at the Rich Presence data below that is for an Activity:
+
+
+
+To create this sort of Rich Presence, here is what the `setActivity()` code would look like:
+
+
+
+
+The following example only focuses on using `setActivity()`. Follow the [Building an Activity guide](/developers/docs/activities/building-an-activity) for more details on topics like instantiating the Embedded App SDK and authenticating users.
+
+```js
+await discordSdk.commands.setActivity({
+ activity: {
+ type: 0,
+ details: 'Traveling with a group',
+ state: 'In Mainframe',
+ assets: {
+ large_image: 'main-game-image',
+ large_text: 'in a group',
+ small_image: 'map-mainframe',
+ small_text: 'in mainframe'
+ },
+ timestamps: {
+ start: 1723137832
+ },
+ party: {
+ size: [2,4]
+ }
+ }
+});
+```
+
+
+## Using External Custom Assets
+
+Typically when building an Activity, you need to be aware of the proxy and [how to use external resources](/developers/docs/activities/development-guides/networking#using-external-resources). However, luckily for you (and the writer of this guide), image URLs in fields for features like Rich Presence don't need to jump through any extra hoops.
+
+As mentioned in the [Rich Presence overview](/developers/docs/rich-presence/overview#assets), you have more than 300 custom assets or if you want to use your stored images from somewhere else, you can specify an external URL for `large_image` or `small_image` within the `assets` object.
+
+
+
+
+The following example only focuses on using `setActivity()`. Follow the [Building an Activity guide](/developers/docs/activities/building-an-activity) for more details on topics like instantiating the Embedded App SDK and authenticating users.
+
+```js
+await discordSdk.commands.setActivity({
+ activity: {
+ type: 2,
+ state: 'Broken Hearts and Code (club edit)',
+ details: 'DJ Wump',
+ assets: {
+ large_image: 'https://example.com/album-covers/dj-wump/broken-code-and-hearts-club-edit.jpg',
+ large_text: 'Listening to a track',
+ }
+ }
+});
+```
+
+
diff --git a/docs/rich-presence/using-with-the-game-sdk.mdx b/discord/developers/docs/rich-presence/using-with-the-game-sdk.mdx
similarity index 63%
rename from docs/rich-presence/using-with-the-game-sdk.mdx
rename to discord/developers/docs/rich-presence/using-with-the-game-sdk.mdx
index bb9ce898b7..175d94d92c 100644
--- a/docs/rich-presence/using-with-the-game-sdk.mdx
+++ b/discord/developers/docs/rich-presence/using-with-the-game-sdk.mdx
@@ -1,32 +1,32 @@
---
-sidebar_label: Using with the Game SDK
+title: Using Rich Presence with the Game SDK
+sidebarTitle: Using with the Game SDK
+tag: "LEGACY"
---
-# Using Rich Presence with the Game SDK
-
-:::warn
+
**The Game SDK has been archived.**
-We recommend using the [Discord Social SDK](/docs/discord-social-sdk/overview) for new projects.
+We recommend using the [Discord Social SDK](/developers/docs/discord-social-sdk/overview) for new projects.
-Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/docs/discord-social-sdk/overview) for new features and updates.
-:::
+Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/developers/docs/discord-social-sdk/overview) for new features and updates.
+
-The [Game SDK](/docs/developer-tools/game-sdk) helps you build 3rd party games and integrate them with Discord. One of its specialties is making it easy to bring your game's data to Discord using [Rich Presence](/docs/rich-presence/overview), which this guide will cover.
+The [Game SDK](/developers/docs/developer-tools/game-sdk) helps you build 3rd party games and integrate them with Discord. One of its specialties is making it easy to bring your game's data to Discord using [Rich Presence](/developers/docs/rich-presence/overview), which this guide will cover.
-Before we dig in, make sure you've gone through the guide on [Getting Started with the Game SDK](/docs/developer-tools/game-sdk#getting-started). This guide expects that you've already [downloaded the SDK](/docs/developer-tools/game-sdk#step-1-get-the-sdk), [configured your app](/docs/developer-tools/game-sdk#step-2-create-your-app), and [gotten up and running with a basic example](/docs/developer-tools/game-sdk#step-3-start-coding).
+Before we dig in, make sure you've gone through the guide on [Getting Started with the Game SDK](/developers/docs/developer-tools/game-sdk#getting-started). This guide expects that you've already [downloaded the SDK](/developers/docs/developer-tools/game-sdk#step-1-get-the-sdk), [configured your app](/developers/docs/developer-tools/game-sdk#step-2-create-your-app), and [gotten up and running with a basic example](/developers/docs/developer-tools/game-sdk#step-3-start-coding).
-:::info
-Not sure if you should be building with the Game SDK? Read through [Choosing an SDK](/docs/rich-presence/overview#choosing-an-sdk) to understand your options when integrating Rich Presence.
-:::
+
+Not sure if you should be building with the Game SDK? Read through [Choosing an SDK](/developers/docs/rich-presence/overview#choosing-an-sdk) to understand your options when integrating Rich Presence.
+
## Understanding Rich Presence Data
Before we dig in, it's helpful to understand what Rich Presence data you can set when updating a user's presence data. We'll explain the specific fields below, but for now let's just take a look at what we're working with:
-
+
-
+
| location | field name | notes |
|----------------------------------------|----------------|----------------------------------------------------------------------------|
| First row below title | details | |
@@ -41,17 +41,17 @@ Before we dig in, it's helpful to understand what Rich Presence data you can set
Note that this layout may be subject to change without warning. This information is only provided to help those with
impaired eyesight to understand the potential layout of this information in a user interface.
-
+
-:::info
-For tips on designing Rich Presence, take a look at the [Rich Presence best practices guide](/docs/rich-presence/best-practices).
-:::
+
+For tips on designing Rich Presence, take a look at the [Rich Presence best practices guide](/developers/docs/rich-presence/best-practices).
+
## Activities Manager
-As you likely learned when setting up your app, the Game SDK has a handful of specialized [manager classes](/docs/developer-tools/game-sdk#managers). The **[`ActivitiesManager`](/docs/developer-tools/game-sdk#activities)** is responsible for integrating Rich Presence and sending invites, so that's where we'll spend our focus in this guide.
+As you likely learned when setting up your app, the Game SDK has a handful of specialized [manager classes](/developers/docs/developer-tools/game-sdk#managers). The **[`ActivitiesManager`](/developers/docs/developer-tools/game-sdk#activities)** is responsible for integrating Rich Presence and sending invites, so that's where we'll spend our focus in this guide.
-Like other Game SDK managers, the `ActivitiesManager` class has a handful of [functions](/docs/developer-tools/game-sdk#functions) and [events](/docs/developer-tools/game-sdk#functions) that are used when building Rich Presence support. We'll touch on the ones important to presence below.
+Like other Game SDK managers, the `ActivitiesManager` class has a handful of [functions](/developers/docs/developer-tools/game-sdk#functions) and [events](/developers/docs/developer-tools/game-sdk#functions) that are used when building Rich Presence support. We'll touch on the ones important to presence below.
### Fetching Activity Manager
@@ -63,49 +63,49 @@ var activityManager = discord.GetActivityManager();
## Updating Presence
-The most important function when integrating Rich Presence using the Game SDK will be [`UpdateActivity()`](/docs/developer-tools/game-sdk#updateactivity). This is how you will send your game data to Discord to update a user's presence data. You should call `UpdateActivity()` any time something important in the presence payload changes.
+The most important function when integrating Rich Presence using the Game SDK will be [`UpdateActivity()`](/developers/docs/developer-tools/game-sdk#updateactivity). This is how you will send your game data to Discord to update a user's presence data. You should call `UpdateActivity()` any time something important in the presence payload changes.
### UpdateActivity Fields
-When calling `UpdateActivity()`, you'll be expected to pass the [activity](/docs/developer-tools/game-sdk#activity-struct) fields besides your `ApplicationId` and `Name` (which are both read-only).
+When calling `UpdateActivity()`, you'll be expected to pass the [activity](/developers/docs/developer-tools/game-sdk#activity-struct) fields besides your `ApplicationId` and `Name` (which are both read-only).
#### Partial Activity Struct
Below are the fields we'll be paying attention to as we're passing presence data for a user.
-:::info
+
All fields are optional and nullable
-:::
-
-| Name | Type | Description |
-|------------|--------------------------------------------------------------------------------|-----------------------------------------------------------------|
-| State | string | the player's current party status |
-| Details | string | what the player is currently doing |
-| Timestamps | [ActivityTimestamps](/docs/developer-tools/game-sdk#activitytimestamps-struct) | helps create elapsed/remaining timestamps on a player's profile |
-| Assets | [ActivityAssets](/docs/developer-tools/game-sdk#activityassets-struct) | assets to display on the player's profile |
-| Party | [ActivityParty](/docs/developer-tools/game-sdk#activityparty-struct) | information about the player's party |
-| Secrets | [ActivitySecrets](/docs/developer-tools/game-sdk#activitysecrets-struct) | secret passwords for joining the player's game |
-| Instance | bool | whether this activity is an instanced context, like a match |
+
+
+| Name | Type | Description |
+|------------|-------------------------------------------------------------------------------------------|-----------------------------------------------------------------|
+| State | string | the player's current party status |
+| Details | string | what the player is currently doing |
+| Timestamps | [ActivityTimestamps](/developers/docs/developer-tools/game-sdk#activitytimestamps-struct) | helps create elapsed/remaining timestamps on a player's profile |
+| Assets | [ActivityAssets](/developers/docs/developer-tools/game-sdk#activityassets-struct) | assets to display on the player's profile |
+| Party | [ActivityParty](/developers/docs/developer-tools/game-sdk#activityparty-struct) | information about the player's party |
+| Secrets | [ActivitySecrets](/developers/docs/developer-tools/game-sdk#activitysecrets-struct) | secret passwords for joining the player's game |
+| Instance | bool | whether this activity is an instanced context, like a match |
### UpdateActivity Example
Now let's take a look at a code example for updating presence data.
-:::info
+
All of the code samples in this guide are in C#, but there are some similar examples in other languages [on GitHub](https://github.com/msciotti/discord-game-sdk-test-apps).
-:::
+
Our code sample in this section is based on the data from the example from before:
-
+
The **Ask to Join** button will be covered more in the following sections, but if you don't want it included, you can remove the `Party` and `Secret` fields.
-
+
-:::info
-The following example only focuses on using `UpdateActivity()`. You can read the [Getting Started](/docs/developer-tools/game-sdk#getting-started) and [Using the SDK](/docs/developer-tools/game-sdk#using-the-sdk) sections for more general information about using the Game SDK.
-:::
+
+The following example only focuses on using `UpdateActivity()`. You can read the [Getting Started](/developers/docs/developer-tools/game-sdk#getting-started) and [Using the SDK](/developers/docs/developer-tools/game-sdk#using-the-sdk) sections for more general information about using the Game SDK.
+
```cs
var activity = new Discord.Activity
@@ -151,7 +151,7 @@ activityManager.UpdateActivity(activity, (result) =>
}
});
```
-
+
## Asking to Join
@@ -161,17 +161,17 @@ In the example above, there was an **Ask to Join** button that a user could clic
To get the **Ask to Join** button to appear under the presence data for a 3rd party game, you should send along a few fields: `ActivityParty.Id`, `ActivityParty.Size.CurrentSize`, `ActivityParty.Size.MaxSize`, and `ActivitySecrets.Join`.
-To see what you need for each Rich Presence feature, you can view the [Activity Action Field Requirements](/docs/developer-tools/game-sdk#activity-action-field-requirements) table.
+To see what you need for each Rich Presence feature, you can view the [Activity Action Field Requirements](/developers/docs/developer-tools/game-sdk#activity-action-field-requirements) table.
### Handling Ask to Join
-To listen for when someone clicks the button, you'll use the [`OnActivityJoinRequest` event](/docs/developer-tools/game-sdk#onactivityjoinrequest). This will include a [user](/docs/developer-tools/game-sdk#user-struct) for the individual that clicked the button.
+To listen for when someone clicks the button, you'll use the [`OnActivityJoinRequest` event](/developers/docs/developer-tools/game-sdk#onactivityjoinrequest). This will include a [user](/developers/docs/developer-tools/game-sdk#user-struct) for the individual that clicked the button.
As an example, let's say we updated Player A's presence data, and Player B found the **Ask to Join** button on their profile and proceeded to click it. At that point, your app will receive an `OnActivityJoinRequest`. Your game should surface this to Player A to confirm they wish to play with Player B.
-After you confirm that Player A is game, you will call [`SendRequestReply`](/docs/developer-tools/game-sdk#sendrequestreply) with Player B's `userId` and a `reply` field with an [`ActivityJoinRequestReply` value](/docs/developer-tools/game-sdk#activityjoinrequestreply-enum).
+After you confirm that Player A is game, you will call [`SendRequestReply`](/developers/docs/developer-tools/game-sdk#sendrequestreply) with Player B's `userId` and a `reply` field with an [`ActivityJoinRequestReply` value](/developers/docs/developer-tools/game-sdk#activityjoinrequestreply-enum).
-
+
```cs
activityManager.OnActivityJoinRequest += user =>
@@ -186,10 +186,10 @@ activityManager.OnActivityJoinRequest += user =>
});
}
```
-
+
The **Ask to Join** request persists for 30 seconds after the request is received. Therefore, keep these two points in mind:
-- Ensure you call [`RunCallbacks()`](/docs/developer-tools/game-sdk#runcallbacks) as frequently as possible to ensure your game client is up to date with any data from Discord
+- Ensure you call [`RunCallbacks()`](/developers/docs/developer-tools/game-sdk#runcallbacks) as frequently as possible to ensure your game client is up to date with any data from Discord
- If the player is in a state in which they cannot interact with an **Ask to Join** request—like in the middle of a match—you should not send `ActivitySecrets.Join` in the presence payload
## Secrets
@@ -229,8 +229,8 @@ Currently, the SDK does not support this. Party slot information is determined b
#### Q: Can I send images via the payload rather than uploading them to my app's settings?
-Yes! In addition to uploading an asset and specifying its name, you can also specify an external image URL for us to proxy. For more information, see [Activity Asset Image](/docs/events/gateway-events#activity-object-activity-asset-image).
+Yes! In addition to uploading an asset and specifying its name, you can also specify an external image URL for us to proxy. For more information, see [Activity Asset Image](/developers/docs/events/gateway-events#activity-object-activity-asset-image).
#### Q: OK—I've got it working! Now, how do I make my integration look _awesome_?
-I'm happy ~~we preempted your question~~ you asked! Check out our [Rich Presence Best Practices](/docs/rich-presence/best-practices) guide for a rundown on how to make your integration the best that it can be!
+I'm happy ~~we preempted your question~~ you asked! Check out our [Rich Presence Best Practices](/developers/docs/rich-presence/best-practices) guide for a rundown on how to make your integration the best that it can be!
diff --git a/docs/topics/certified-devices.md b/discord/developers/docs/topics/certified-devices.md
similarity index 79%
rename from docs/topics/certified-devices.md
rename to discord/developers/docs/topics/certified-devices.md
index 93e36d3bd3..69888c2c58 100644
--- a/docs/topics/certified-devices.md
+++ b/discord/developers/docs/topics/certified-devices.md
@@ -8,11 +8,11 @@ I'm glad you asked!
1. [Create an application](https://discord.com/developers/applications) for your hardware vendor—save the Client ID!
2. Talk to Discord via one simple HTTP or WebSocket call
-3. Send us a [`SET_CERTIFIED_DEVICES`](/docs/topics/rpc#setcertifieddevices) WebSocket payload or equivalent HTTP POST whenever the state of the device changes
+3. Send us a [`SET_CERTIFIED_DEVICES`](/developers/docs/topics/rpc#setcertifieddevices) WebSocket payload or equivalent HTTP POST whenever the state of the device changes
Yup, that's it. You give us the real-time info about any connected devices, and we'll handle the rest to make sure that anyone using your device will have an awesome experience. Your device will also have a `CERTIFIED` badge in Discord's audio settings, and really, who doesn't love badges?
-
+
## Connecting
@@ -48,9 +48,11 @@ Each time you update, send a full array of `devices`, sorted by your preferred p
For each device in the `SET_CERTIFIED_DEVICES` payload, there is an `id` field. This `id` should be the Windows device's UUID, retrieved through the native Windows API. You'll get back something that looks like `{0.0.1.00000000}.{6cff2b76-44a8-46b9-b528-262ad8609d9f}`.
-:::info
+
+
On macOS, the `id` will be the name of the device.
-:::
+
+
###### Microphone Id Example
@@ -164,17 +166,17 @@ The socket will respond with a `200 OK` status code and the following JSON.
###### Device Object
-| Field | Type | Description |
-|---------------------------|----------------------------------------------------------------------|----------------------------------------------------------|
-| type | [device type](/docs/topics/certified-devices#models-device-type) | the type of device |
-| id | string | the device's Windows UUID |
-| vendor | [vendor](/docs/topics/certified-devices#models-vendor-object) object | the hardware vendor |
-| model | [model](/docs/topics/certified-devices#models-model-object) object | the model of the product |
-| related | array of strings | UUIDs of related devices |
-| echo_cancellation?\* | boolean | if the device's native echo cancellation is enabled |
-| noise_suppression?\* | boolean | if the device's native noise suppression is enabled |
-| automatic_gain_control?\* | boolean | if the device's native automatic gain control is enabled |
-| hardware_mute?\* | boolean | if the device is hardware muted |
+| Field | Type | Description |
+|---------------------------|---------------------------------------------------------------------------------|----------------------------------------------------------|
+| type | [device type](/developers/docs/topics/certified-devices#models-device-type) | the type of device |
+| id | string | the device's Windows UUID |
+| vendor | [vendor](/developers/docs/topics/certified-devices#models-vendor-object) object | the hardware vendor |
+| model | [model](/developers/docs/topics/certified-devices#models-model-object) object | the model of the product |
+| related | array of strings | UUIDs of related devices |
+| echo_cancellation?\* | boolean | if the device's native echo cancellation is enabled |
+| noise_suppression?\* | boolean | if the device's native noise suppression is enabled |
+| automatic_gain_control?\* | boolean | if the device's native automatic gain control is enabled |
+| hardware_mute?\* | boolean | if the device is hardware muted |
\*These fields are only applicable for `AUDIO_INPUT` device types
diff --git a/discord/developers/docs/topics/certified-devices.mdx b/discord/developers/docs/topics/certified-devices.mdx
new file mode 100644
index 0000000000..fb1fcddd79
--- /dev/null
+++ b/discord/developers/docs/topics/certified-devices.mdx
@@ -0,0 +1,220 @@
+---
+title: Certified Devices
+description: Learn about Discord's Certified Device program for hardware integration.
+---
+
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+
+Baked into Discord is the ability for hardware manufacturers to tell us a little more about the certified devices that are plugged into a user's computer. Unfortunately, no, you can't show that a user's PUBG Chicken Dinner was all thanks to the amazing TotallyRealHardware RGB Mouse and Keyboard Set Extraordinaire™, but you _can_ give them an amazing experience using your hardware with Discord!
+
+
+On macOS, the `id` will be the name of the device.
+
+
+
In accordance with the relevant RFCs, the token and token revocation URLs will **only** accept a content type of `application/x-www-form-urlencoded`. JSON content is not permitted and will return an error.
-:::
+
+
+In order to add a user to a guild, your bot has to already belong to that guild. `role_connections.write` cannot be used with the [Implicit grant type](/developers/docs/topics/oauth2#implicit-grant).
+
## State and Security
@@ -71,32 +79,35 @@ The authorization code grant is what most developers will recognize as "standard
All calls to the OAuth2 endpoints require either HTTP Basic authentication or `client_id` and `client_secret` supplied in the form data body.
+
When you revoke a token, any active access or refresh tokens associated with that authorization will be revoked, regardless of the `token` and `token_type_hint` values you pass in.
-:::
+
```python
import requests
@@ -199,14 +213,16 @@ Boom; the tokens are safely revoked.
The implicit OAuth2 grant is a simplified flow optimized for in-browser clients. Instead of issuing the client an authorization code to be exchanged for an access token, the client is directly issued an access token. The URL is formatted as follows:
+
Team applications are limited to the `identify` and `applications.commands.update` scope, because teams are not bound to a specific user.
-:::
+
+
Developers must abide by the [terms of service](https://support-dev.discord.com/hc/articles/8562894815383-Discord-Developer-Terms-of-Service), which includes refraining from automating standard user accounts (generally called "self-bots") outside of the OAuth2/bot API.
-:::
+
Bot users have a few differences compared to standard Discord users:
1. Bots are added to guilds through the OAuth2 API, and cannot accept normal invites.
2. Bots cannot have friends or be added to or join Group DMs.
3. [Verified bots](https://support-dev.discord.com/hc/en-us/articles/23926564536471-How-Do-I-Get-My-App-Verified) do not have a maximum number of guilds.
-4. Bots have an entirely separate set of [rate limits](/docs/topics/rate-limits#rate-limits).
+4. Bots have an entirely separate set of [rate limits](/developers/docs/topics/rate-limits).
### Bot Authorization Flow
Bot authorization is a special server-less and callback-less OAuth2 flow that makes it easy for users to add bots to guilds. The URL you create looks similar to what we use for full stack implementation:
+/oauth2/applications/@me
-Returns the bot's [application](/docs/resources/application#application-object) object.
+Returns the bot's [application](/developers/docs/resources/application#application-object) object.
## Get Current Authorization Information
/oauth2/@me
Returns info about the current authorization. Requires authentication with a bearer token.
+
+[Application command permissions](/developers/docs/interactions/application-commands#permissions) allow you to enable or disable specific commands for entire channels in addition to individual roles or users.
+
Permissions are stored in a variable-length integer serialized into a string, and are calculated using bitwise operations. For example, the permission value `123` will be serialized as `"123"`. For long-term stability, it's recommended to deserialize the permissions using your preferred languages' Big Integer libraries. The total permissions integer can be determined by OR-ing (`|`) together each individual value, and flags can be checked using AND (`&`) operations.
In API v8 and above, all permissions are serialized as strings, including the `allow` and `deny` fields in overwrites. Any new permissions are rolled back into the base field.
-:::info
-In [API v6 (now deprecated)](/docs/reference), the `permissions`, `allow`, and `deny` fields in roles and overwrites are still serialized as a number; however, these numbers shall not grow beyond 31 bits. During the remaining lifetime of API v6, all new permission bits will only be introduced in `permissions_new`, `allow_new`, and `deny_new`. These `_new` fields are just for response serialization; requests with these fields should continue to use the original `permissions`, `allow`, and `deny` fields, which accept both string or number values.
-:::
+
+In [API v6 (now deprecated)](/developers/docs/reference), the `permissions`, `allow`, and `deny` fields in roles and overwrites are still serialized as a number; however, these numbers shall not grow beyond 31 bits. During the remaining lifetime of API v6, all new permission bits will only be introduced in `permissions_new`, `allow_new`, and `deny_new`. These `_new` fields are just for response serialization; requests with these fields should continue to use the original `permissions`, `allow`, and `deny` fields, which accept both string or number values.
+
```python
# Permissions value that can Send Messages (0x800) and Add Reactions (0x40):
@@ -30,60 +35,60 @@ Additional logic is required when permission overwrites are involved; this is fu
Below is a table of all current permissions, their integer values in hexadecimal, brief descriptions of the privileges that they grant, and the channel type they apply to, if applicable.
+
When sending `tertiary_color` the API enforces the role color to be a holographic style with values of:
`primary_color = 11127295`, `secondary_color = 16759788`, and `tertiary_color = 16761760`.
-:::
+
+
+Because rate limits depend on a variety of factors and are subject to change, **rate limits should not be hard coded into your app**. Instead, your app should parse [response headers](/developers/docs/topics/rate-limits#header-format-rate-limit-header-examples) to prevent hitting the limit, and to respond accordingly in case you do.
+
**Per-route rate limits** exist for many individual endpoints, and may include the HTTP method (`GET`, `POST`, `PUT`, or `DELETE`). In some cases, per-route limits will be shared across a set of similar endpoints, indicated in the `X-RateLimit-Bucket` header. It's recommended to use this header as a unique identifier for a rate limit, which will allow you to group shared limits as you encounter them.
-During calculation, per-route rate limits often account for top-level resources within the path using an identifier—for example, `guild_id` when calling [`/guilds/{guild.id}/channels`](/docs/resources/guild#get-guild-channels). Top-level resources are currently limited to channels (`channel_id`), guilds (`guild_id`), and webhooks (`webhook_id` or `webhook_id + webhook_token`). This means that an endpoint with two different top-level resources may calculate limits independently. As an example, if you exceeded a rate limit when calling one endpoint `/channels/1234`, you could still call another similar endpoint like `/channels/9876` without a problem.
+During calculation, per-route rate limits often account for top-level resources within the path using an identifier—for example, `guild_id` when calling [`/guilds/{guild.id}/channels`](/developers/docs/resources/guild#get-guild-channels). Top-level resources are currently limited to channels (`channel_id`), guilds (`guild_id`), and webhooks (`webhook_id` or `webhook_id + webhook_token`). This means that an endpoint with two different top-level resources may calculate limits independently. As an example, if you exceeded a rate limit when calling one endpoint `/channels/1234`, you could still call another similar endpoint like `/channels/9876` without a problem.
-**Global rate limits** apply to the total number of requests a bot or user makes, independent of any per-route limits. You can read more on [global rate limits](/docs/topics/rate-limits#global-rate-limit) below.
+**Global rate limits** apply to the total number of requests a bot or user makes, independent of any per-route limits. You can read more on [global rate limits](/developers/docs/topics/rate-limits#global-rate-limit) below.
-:::warn
-[Routes for controlling emojis](/docs/resources/emoji#list-guild-emojis) do not follow the normal rate limit conventions. These routes are specifically limited on a per-guild basis to prevent abuse. This means that the quota returned by our APIs may be inaccurate, and you may encounter 429s.
-:::
+
+[Routes for controlling emojis](/developers/docs/resources/emoji#list-guild-emojis) do not follow the normal rate limit conventions. These routes are specifically limited on a per-guild basis to prevent abuse. This means that the quota returned by our APIs may be inaccurate, and you may encounter 429s.
+
## Header Format
@@ -44,12 +44,12 @@ In the case that a rate limit is exceeded, the API will return a HTTP 429 respon
###### Rate Limit Response Structure
-| Field | Type | Description |
-|-------------|---------|-----------------------------------------------------------------------------|
-| message | string | A message saying you are being rate limited. |
-| retry_after | float | The number of seconds to wait before submitting another request. |
-| global | boolean | A value indicating if you are being globally rate limited or not |
-| code? | integer | An [error code](/docs/topics/opcodes-and-status-codes#json) for some limits |
+| Field | Type | Description |
+|-------------|---------|----------------------------------------------------------------------------------------|
+| message | string | A message saying you are being rate limited. |
+| retry_after | float | The number of seconds to wait before submitting another request. |
+| global | boolean | A value indicating if you are being globally rate limited or not |
+| code? | integer | An [error code](/developers/docs/topics/opcodes-and-status-codes#json) for some limits |
Note that normal route rate-limiting headers will also be sent in this response. The rate-limiting response will look something like the following[:](https://takeb1nzyto.space/)
@@ -115,7 +115,7 @@ Global rate limit issues generally show up as repeatedly getting banned from the
If you are experiencing repeated Cloudflare bans from the Discord API within normal operations of your bot, you can reach out to support to see if you qualify for increased global rate limits. You can contact Discord support using [https://dis.gd/rate-limit](https://dis.gd/rate-limit).
-[Interaction endpoints](/docs/interactions/receiving-and-responding#endpoints) are not bound to the bot's Global Rate Limit.
+[Interaction endpoints](/developers/docs/interactions/receiving-and-responding#endpoints) are not bound to the bot's Global Rate Limit.
## Invalid Request Limit aka Cloudflare bans
diff --git a/discord/developers/docs/topics/rate-limits.mdx b/discord/developers/docs/topics/rate-limits.mdx
new file mode 100644
index 0000000000..6f279056e1
--- /dev/null
+++ b/discord/developers/docs/topics/rate-limits.mdx
@@ -0,0 +1,142 @@
+---
+title: Rate Limits
+description: Understand Discord's rate limiting system including per-route and global limits.
+---
+
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+
+Rate limits exist across Discord's APIs to prevent spam, abuse, and service overload. Limits are applied to individual bots and users both on a per-route basis and globally. Individuals are determined using a request's authentication—for example, a bot token for a bot.
+
+
+Because rate limits depend on a variety of factors and are subject to change, **rate limits should not be hard coded into your app**. Instead, your app should parse [response headers](/developers/docs/topics/rate-limits#header-format-rate-limit-header-examples) to prevent hitting the limit, and to respond accordingly in case you do.
+
+
+**Per-route rate limits** exist for many individual endpoints, and may include the HTTP method (`GET`, `POST`, `PUT`, or `DELETE`). In some cases, per-route limits will be shared across a set of similar endpoints, indicated in the `X-RateLimit-Bucket` header. It's recommended to use this header as a unique identifier for a rate limit, which will allow you to group shared limits as you encounter them.
+
+During calculation, per-route rate limits often account for top-level resources within the path using an identifier—for example, `guild_id` when calling [`/guilds/{guild.id}/channels`](/developers/docs/resources/guild#get-guild-channels). Top-level resources are currently limited to channels (`channel_id`), guilds (`guild_id`), and webhooks (`webhook_id` or `webhook_id + webhook_token`). This means that an endpoint with two different top-level resources may calculate limits independently. As an example, if you exceeded a rate limit when calling one endpoint `/channels/1234`, you could still call another similar endpoint like `/channels/9876` without a problem.
+
+**Global rate limits** apply to the total number of requests a bot or user makes, independent of any per-route limits. You can read more on [global rate limits](/developers/docs/topics/rate-limits#global-rate-limit) below.
+
+
+[Routes for controlling emojis](/developers/docs/resources/emoji#list-guild-emojis) do not follow the normal rate limit conventions. These routes are specifically limited on a per-guild basis to prevent abuse. This means that the quota returned by our APIs may be inaccurate, and you may encounter 429s.
+
+
+## Header Format
+
+For most API requests made, we return optional HTTP response headers containing the rate limit encountered during your request.
+
+
+
For now, RPC is in a private beta. We are not currently accepting any new developers into the program at this time.
-:::
+
+
All Discord clients have an RPC server running on localhost that allows control over local Discord clients.
@@ -14,7 +16,7 @@ All Discord clients have an RPC server running on localhost that allows control
## Restrictions
-For connections to the RPC server, a [list of approved testers](/docs/topics/rpc#authorize) is used to restrict access while you're still developing. You can invite up to 50 people.
+For connections to the RPC server, a [list of approved testers](/developers/docs/topics/rpc#authorize) is used to restrict access while you're still developing. You can invite up to 50 people.
For applications/games not approved, we limit you to creating 10 guilds and 10 channels. This limit is raised to virtually unlimited after approval.
@@ -22,13 +24,13 @@ For applications/games not approved, we limit you to creating 10 guilds and 10 c
###### Payload Structure
-| Field | Type | Description | Present |
-|-------|--------|-----------------------------------------------------------------------|----------------------------------------------------------|
-| cmd | enum | [payload command](/docs/topics/rpc#commands-and-events-rpc-commands) | Always |
-| nonce | string | unique string used once for replies from the server | In responses to commands (not subscribed events) |
-| evt | enum | [subscription event](/docs/topics/rpc#commands-and-events-rpc-events) | In subscribed events, errors, and (un)subscribing events |
-| data | object | event data | In responses from the server |
-| args | object | command arguments | In commands sent to the server |
+| Field | Type | Description | Present |
+|-------|--------|----------------------------------------------------------------------------------|----------------------------------------------------------|
+| cmd | enum | [payload command](/developers/docs/topics/rpc#commands-and-events-rpc-commands) | Always |
+| nonce | string | unique string used once for replies from the server | In responses to commands (not subscribed events) |
+| evt | enum | [subscription event](/developers/docs/topics/rpc#commands-and-events-rpc-events) | In subscribed events, errors, and (un)subscribing events |
+| data | object | event data | In responses from the server |
+| args | object | command arguments | In commands sent to the server |
## Connecting
@@ -55,7 +57,7 @@ The port range for Discord's local RPC server is [6463, 6472]. Since the RPC ser
## Authenticating
-In order to call any commands over RPC, you must be authenticated or you will receive a code `4006` error response. Thankfully, we've removed the oppressive nature of a couple commands that will let you `AUTHORIZE` and `AUTHENTICATE` new users. First, call [AUTHORIZE](/docs/topics/rpc#authorize):
+In order to call any commands over RPC, you must be authenticated or you will receive a code `4006` error response. Thankfully, we've removed the oppressive nature of a couple commands that will let you `AUTHORIZE` and `AUTHENTICATE` new users. First, call [AUTHORIZE](/developers/docs/topics/rpc#authorize):
###### RPC Authorize Example
@@ -70,7 +72,7 @@ In order to call any commands over RPC, you must be authenticated or you will re
}
```
-The user will then be prompted to authorize your app to access RPC on Discord. The `AUTHORIZE` command returns a `code` that you can exchange with a POST to `https://discord.com/api/oauth2/token` containing the [standard OAuth2 body parameters](https://tools.ietf.org/html/rfc6749#section-4.1.3) for the token exchange. The token endpoint on our API will return an `access_token` that can be sent with [AUTHENTICATE](/docs/topics/rpc#authenticate):
+The user will then be prompted to authorize your app to access RPC on Discord. The `AUTHORIZE` command returns a `code` that you can exchange with a POST to `https://discord.com/api/oauth2/token` containing the [standard OAuth2 body parameters](https://tools.ietf.org/html/rfc6749#section-4.1.3) for the token exchange. The token endpoint on our API will return an `access_token` that can be sent with [AUTHENTICATE](/developers/docs/topics/rpc#authenticate):
###### RPC Authenticate Example
@@ -92,54 +94,54 @@ Commands are requests made to the RPC socket by a client.
###### RPC Commands
-| Name | Description |
-|------------------------------------------------------------------------|-----------------------------------------------------------------|
-| [DISPATCH](/docs/topics/rpc#commands-and-events-rpc-events) | event dispatch |
-| [AUTHORIZE](/docs/topics/rpc#authorize) | used to authorize a new client with your app |
-| [AUTHENTICATE](/docs/topics/rpc#authenticate) | used to authenticate an existing client with your app |
-| [GET_GUILD](/docs/topics/rpc#getguild) | used to retrieve guild information from the client |
-| [GET_GUILDS](/docs/topics/rpc#getguilds) | used to retrieve a list of guilds from the client |
-| [GET_CHANNEL](/docs/topics/rpc#getchannel) | used to retrieve channel information from the client |
-| [GET_CHANNELS](/docs/topics/rpc#getchannels) | used to retrieve a list of channels for a guild from the client |
-| [SUBSCRIBE](/docs/topics/rpc#subscribe) | used to subscribe to an RPC event |
-| [UNSUBSCRIBE](/docs/topics/rpc#unsubscribe) | used to unsubscribe from an RPC event |
-| [SET_USER_VOICE_SETTINGS](/docs/topics/rpc#setuservoicesettings) | used to change voice settings of users in voice channels |
-| [SELECT_VOICE_CHANNEL](/docs/topics/rpc#selectvoicechannel) | used to join or leave a voice channel, group dm, or dm |
-| [GET_SELECTED_VOICE_CHANNEL](/docs/topics/rpc#getselectedvoicechannel) | used to get the current voice channel the client is in |
-| [SELECT_TEXT_CHANNEL](/docs/topics/rpc#selecttextchannel) | used to join or leave a text channel, group dm, or dm |
-| [GET_VOICE_SETTINGS](/docs/topics/rpc#getvoicesettings) | used to retrieve the client's voice settings |
-| [SET_VOICE_SETTINGS](/docs/topics/rpc#setvoicesettings) | used to set the client's voice settings |
-| [SET_CERTIFIED_DEVICES](/docs/topics/rpc#setcertifieddevices) | used to send info about certified hardware devices |
-| [SET_ACTIVITY](/docs/topics/rpc#setactivity) | used to update a user's Rich Presence |
-| [SEND_ACTIVITY_JOIN_INVITE](/docs/topics/rpc#sendactivityjoininvite) | used to consent to a Rich Presence Ask to Join request |
-| [CLOSE_ACTIVITY_REQUEST](/docs/topics/rpc#closeactivityrequest) | used to reject a Rich Presence Ask to Join request |
+| Name | Description |
+|-----------------------------------------------------------------------------------|-----------------------------------------------------------------|
+| [DISPATCH](/developers/docs/topics/rpc#commands-and-events-rpc-events) | event dispatch |
+| [AUTHORIZE](/developers/docs/topics/rpc#authorize) | used to authorize a new client with your app |
+| [AUTHENTICATE](/developers/docs/topics/rpc#authenticate) | used to authenticate an existing client with your app |
+| [GET_GUILD](/developers/docs/topics/rpc#getguild) | used to retrieve guild information from the client |
+| [GET_GUILDS](/developers/docs/topics/rpc#getguilds) | used to retrieve a list of guilds from the client |
+| [GET_CHANNEL](/developers/docs/topics/rpc#getchannel) | used to retrieve channel information from the client |
+| [GET_CHANNELS](/developers/docs/topics/rpc#getchannels) | used to retrieve a list of channels for a guild from the client |
+| [SUBSCRIBE](/developers/docs/topics/rpc#subscribe) | used to subscribe to an RPC event |
+| [UNSUBSCRIBE](/developers/docs/topics/rpc#unsubscribe) | used to unsubscribe from an RPC event |
+| [SET_USER_VOICE_SETTINGS](/developers/docs/topics/rpc#setuservoicesettings) | used to change voice settings of users in voice channels |
+| [SELECT_VOICE_CHANNEL](/developers/docs/topics/rpc#selectvoicechannel) | used to join or leave a voice channel, group dm, or dm |
+| [GET_SELECTED_VOICE_CHANNEL](/developers/docs/topics/rpc#getselectedvoicechannel) | used to get the current voice channel the client is in |
+| [SELECT_TEXT_CHANNEL](/developers/docs/topics/rpc#selecttextchannel) | used to join or leave a text channel, group dm, or dm |
+| [GET_VOICE_SETTINGS](/developers/docs/topics/rpc#getvoicesettings) | used to retrieve the client's voice settings |
+| [SET_VOICE_SETTINGS](/developers/docs/topics/rpc#setvoicesettings) | used to set the client's voice settings |
+| [SET_CERTIFIED_DEVICES](/developers/docs/topics/rpc#setcertifieddevices) | used to send info about certified hardware devices |
+| [SET_ACTIVITY](/developers/docs/topics/rpc#setactivity) | used to update a user's Rich Presence |
+| [SEND_ACTIVITY_JOIN_INVITE](/developers/docs/topics/rpc#sendactivityjoininvite) | used to consent to a Rich Presence Ask to Join request |
+| [CLOSE_ACTIVITY_REQUEST](/developers/docs/topics/rpc#closeactivityrequest) | used to reject a Rich Presence Ask to Join request |
Events are payloads sent over the socket to a client that correspond to events in Discord.
###### RPC Events
-| Name | Description |
-|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|
-| [READY](/docs/topics/rpc#ready) | non-subscription event sent immediately after connecting, contains server information |
-| [ERROR](/docs/topics/rpc#error) | non-subscription event sent when there is an error, including command responses |
-| [GUILD_STATUS](/docs/topics/rpc#guildstatus) | sent when a subscribed server's state changes |
-| [GUILD_CREATE](/docs/topics/rpc#guildcreate) | sent when a guild is created/joined on the client |
-| [CHANNEL_CREATE](/docs/topics/rpc#channelcreate) | sent when a channel is created/joined on the client |
-| [VOICE_CHANNEL_SELECT](/docs/topics/rpc#voicechannelselect) | sent when the client joins a voice channel |
-| [VOICE_STATE_CREATE](/docs/topics/rpc#voicestatecreatevoicestateupdatevoicestatedelete) | sent when a user joins a subscribed voice channel |
-| [VOICE_STATE_UPDATE](/docs/topics/rpc#voicestatecreatevoicestateupdatevoicestatedelete) | sent when a user's voice state changes in a subscribed voice channel (mute, volume, etc.) |
-| [VOICE_STATE_DELETE](/docs/topics/rpc#voicestatecreatevoicestateupdatevoicestatedelete) | sent when a user parts a subscribed voice channel |
-| [VOICE_SETTINGS_UPDATE](/docs/topics/rpc#voicesettingsupdate) | sent when the client's voice settings update |
-| [VOICE_CONNECTION_STATUS](/docs/topics/rpc#voiceconnectionstatus) | sent when the client's voice connection status changes |
-| [SPEAKING_START](/docs/topics/rpc#speakingstartspeakingstop) | sent when a user in a subscribed voice channel speaks |
-| [SPEAKING_STOP](/docs/topics/rpc#speakingstartspeakingstop) | sent when a user in a subscribed voice channel stops speaking |
-| [MESSAGE_CREATE](/docs/topics/rpc#messagecreatemessageupdatemessagedelete) | sent when a message is created in a subscribed text channel |
-| [MESSAGE_UPDATE](/docs/topics/rpc#messagecreatemessageupdatemessagedelete) | sent when a message is updated in a subscribed text channel |
-| [MESSAGE_DELETE](/docs/topics/rpc#messagecreatemessageupdatemessagedelete) | sent when a message is deleted in a subscribed text channel |
-| [NOTIFICATION_CREATE](/docs/topics/rpc#notificationcreate) | sent when the client receives a notification (mention or new message in eligible channels) |
-| [ACTIVITY_JOIN](/docs/topics/rpc#activityjoin) | sent when the user clicks a Rich Presence join invite in chat to join a game |
-| [ACTIVITY_SPECTATE](/docs/topics/rpc#activityspectate) | sent when the user clicks a Rich Presence spectate invite in chat to spectate a game |
-| [ACTIVITY_JOIN_REQUEST](/docs/topics/rpc#activityjoinrequest) | sent when the user receives a Rich Presence Ask to Join request |
+| Name | Description |
+|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|
+| [READY](/developers/docs/topics/rpc#ready) | non-subscription event sent immediately after connecting, contains server information |
+| [ERROR](/developers/docs/topics/rpc#error) | non-subscription event sent when there is an error, including command responses |
+| [GUILD_STATUS](/developers/docs/topics/rpc#guildstatus) | sent when a subscribed server's state changes |
+| [GUILD_CREATE](/developers/docs/topics/rpc#guildcreate) | sent when a guild is created/joined on the client |
+| [CHANNEL_CREATE](/developers/docs/topics/rpc#channelcreate) | sent when a channel is created/joined on the client |
+| [VOICE_CHANNEL_SELECT](/developers/docs/topics/rpc#voicechannelselect) | sent when the client joins a voice channel |
+| [VOICE_STATE_CREATE](/developers/docs/topics/rpc#voicestatecreatevoicestateupdatevoicestatedelete) | sent when a user joins a subscribed voice channel |
+| [VOICE_STATE_UPDATE](/developers/docs/topics/rpc#voicestatecreatevoicestateupdatevoicestatedelete) | sent when a user's voice state changes in a subscribed voice channel (mute, volume, etc.) |
+| [VOICE_STATE_DELETE](/developers/docs/topics/rpc#voicestatecreatevoicestateupdatevoicestatedelete) | sent when a user parts a subscribed voice channel |
+| [VOICE_SETTINGS_UPDATE](/developers/docs/topics/rpc#voicesettingsupdate) | sent when the client's voice settings update |
+| [VOICE_CONNECTION_STATUS](/developers/docs/topics/rpc#voiceconnectionstatus) | sent when the client's voice connection status changes |
+| [SPEAKING_START](/developers/docs/topics/rpc#speakingstartspeakingstop) | sent when a user in a subscribed voice channel speaks |
+| [SPEAKING_STOP](/developers/docs/topics/rpc#speakingstartspeakingstop) | sent when a user in a subscribed voice channel stops speaking |
+| [MESSAGE_CREATE](/developers/docs/topics/rpc#messagecreatemessageupdatemessagedelete) | sent when a message is created in a subscribed text channel |
+| [MESSAGE_UPDATE](/developers/docs/topics/rpc#messagecreatemessageupdatemessagedelete) | sent when a message is updated in a subscribed text channel |
+| [MESSAGE_DELETE](/developers/docs/topics/rpc#messagecreatemessageupdatemessagedelete) | sent when a message is deleted in a subscribed text channel |
+| [NOTIFICATION_CREATE](/developers/docs/topics/rpc#notificationcreate) | sent when the client receives a notification (mention or new message in eligible channels) |
+| [ACTIVITY_JOIN](/developers/docs/topics/rpc#activityjoin) | sent when the user clicks a Rich Presence join invite in chat to join a game |
+| [ACTIVITY_SPECTATE](/developers/docs/topics/rpc#activityspectate) | sent when the user clicks a Rich Presence spectate invite in chat to spectate a game |
+| [ACTIVITY_JOIN_REQUEST](/developers/docs/topics/rpc#activityjoinrequest) | sent when the user receives a Rich Presence Ask to Join request |
#### AUTHORIZE
@@ -151,12 +153,12 @@ We also have an RPC token system to bypass the user authorization modal. This is
###### Authorize Argument Structure
-| Field | Type | Description |
-|-----------|------------------------------------------------------------------------------|---------------------------------------------------------------------------|
-| scopes | array of [OAuth2 scopes](/docs/topics/oauth2#shared-resources-oauth2-scopes) | scopes to authorize |
-| client_id | string | OAuth2 application id |
-| rpc_token | string | one-time use RPC token |
-| username | string | username to create a guest account with if the user does not have Discord |
+| Field | Type | Description |
+|-----------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------------------|
+| scopes | array of [OAuth2 scopes](/developers/docs/topics/oauth2#shared-resources-oauth2-scopes) | scopes to authorize |
+| client_id | string | OAuth2 application id |
+| rpc_token | string | one-time use RPC token |
+| username | string | username to create a guest account with if the user does not have Discord |
###### Authorize Response Structure
@@ -201,12 +203,12 @@ Used to authenticate an existing client with your app.
###### Authenticate Response Structure
-| Field | Type | Description |
-|-------------|-----------------------------------------------------------------------------------------|---------------------------------|
-| user | partial [user](/docs/resources/user#user-object) object | the authed user |
-| scopes | array of [OAuth2 scopes](/docs/topics/oauth2#shared-resources-oauth2-scopes) | authorized scopes |
-| expires | date | expiration date of OAuth2 token |
-| application | [OAuth2 application](/docs/topics/rpc#authenticate-oauth2-application-structure) object | application the user authorized |
+| Field | Type | Description |
+|-------------|----------------------------------------------------------------------------------------------------|---------------------------------|
+| user | partial [user](/developers/docs/resources/user#user-object) object | the authed user |
+| scopes | array of [OAuth2 scopes](/developers/docs/topics/oauth2#shared-resources-oauth2-scopes) | authorized scopes |
+| expires | date | expiration date of OAuth2 token |
+| application | [OAuth2 application](/developers/docs/topics/rpc#authenticate-oauth2-application-structure) object | application the user authorized |
###### OAuth2 Application Structure
@@ -262,9 +264,9 @@ Used to get a list of guilds the client is in.
###### Get Guilds Response Structure
-| Field | Type | Description |
-|--------|----------------------------------------------------------------------|---------------------------|
-| guilds | array of partial [guild](/docs/resources/guild#guild-object) objects | the guilds the user is in |
+| Field | Type | Description |
+|--------|---------------------------------------------------------------------------------|---------------------------|
+| guilds | array of partial [guild](/developers/docs/resources/guild#guild-object) objects | the guilds the user is in |
###### Example Get Guilds Command Payload
@@ -306,12 +308,12 @@ Used to get a guild the client is in.
###### Get Guild Response Structure
-| Field | Type | Description |
-|----------|----------------------------------------------------------------------------|-------------------------------------------------------|
-| id | string | guild id |
-| name | string | guild name |
-| icon_url | string | guild icon url |
-| members | array of [guild member](/docs/resources/guild#guild-member-object) objects | members of the guild (deprecated; always empty array) |
+| Field | Type | Description |
+|----------|---------------------------------------------------------------------------------------|-------------------------------------------------------|
+| id | string | guild id |
+| name | string | guild name |
+| icon_url | string | guild icon url |
+| members | array of [guild member](/developers/docs/resources/guild#guild-member-object) objects | members of the guild (deprecated; always empty array) |
###### Example Get Guild Command Payload
@@ -352,18 +354,18 @@ Used to get a channel the client is in.
###### Get Channel Response Structure
-| Field | Type | Description |
-|--------------|--------------------------------------------------------------------------|------------------------------------------------------------------|
-| id | string | channel id |
-| guild_id | string | channel's guild id |
-| name | string | channel name |
-| type | integer | channel type (guild text: 0, guild voice: 2, dm: 1, group dm: 3) |
-| topic | string | (text) channel topic |
-| bitrate | integer | (voice) bitrate of voice channel |
-| user_limit | integer | (voice) user limit of voice channel (0 for none) |
-| position | integer | position of channel in channel list |
-| voice_states | array of [voice state](/docs/resources/voice#voice-state-object) objects | (voice) channel's voice states |
-| messages | array of [message](/docs/resources/message#message-object) objects | (text) channel's messages |
+| Field | Type | Description |
+|--------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------|
+| id | string | channel id |
+| guild_id | string | channel's guild id |
+| name | string | channel name |
+| type | integer | channel type (guild text: 0, guild voice: 2, dm: 1, group dm: 3) |
+| topic | string | (text) channel topic |
+| bitrate | integer | (voice) bitrate of voice channel |
+| user_limit | integer | (voice) user limit of voice channel (0 for none) |
+| position | integer | position of channel in channel list |
+| voice_states | array of [voice state](/developers/docs/resources/voice#voice-state-object) objects | (voice) channel's voice states |
+| messages | array of [message](/developers/docs/resources/message#message-object) objects | (text) channel's messages |
###### Example Get Channel Command Payload
@@ -432,9 +434,9 @@ Used to get a guild's channels the client is in.
###### Get Channels Response Structure
-| Field | Type | Description |
-|----------|----------------------------------------------------------------------------|-------------------------------|
-| channels | array of partial [channel](/docs/resources/channel#channel-object) objects | guild channels the user is in |
+| Field | Type | Description |
+|----------|---------------------------------------------------------------------------------------|-------------------------------|
+| channels | array of partial [channel](/developers/docs/resources/channel#channel-object) objects | guild channels the user is in |
###### Example Get Channels Command Payload
@@ -477,16 +479,16 @@ Used to change voice settings of users in voice channels
###### Set User Voice Settings Argument and Response Structure
-| Field | Type | Description |
-|---------|----------------------------------------------------------------|----------------------------------------------------------|
-| user_id | string | user id |
-| pan? | [pan](/docs/topics/rpc#setuservoicesettings-pan-object) object | set the pan of the user |
-| volume? | integer | set the volume of user (defaults to 100, min 0, max 200) |
-| mute? | boolean | set the mute state of the user |
+| Field | Type | Description |
+|---------|---------------------------------------------------------------------------|----------------------------------------------------------|
+| user_id | string | user id |
+| pan? | [pan](/developers/docs/topics/rpc#setuservoicesettings-pan-object) object | set the pan of the user |
+| volume? | integer | set the volume of user (defaults to 100, min 0, max 200) |
+| mute? | boolean | set the mute state of the user |
-:::info
+
In the current release, we only support a single modifier of voice settings at a time over RPC. If an app changes voice settings, it will lock voice settings so that other apps connected simultaneously lose the ability to change voice settings. Settings reset to what they were before being changed after the controlling app disconnects. When an app that has previously set voice settings connects, the client will swap to that app's configured voice settings and lock voice settings again. This is a temporary situation that will be changed in the future.
-:::
+
###### Pan Object
@@ -533,7 +535,7 @@ In the current release, we only support a single modifier of voice settings at a
#### SELECT_VOICE_CHANNEL
-Used to join and leave voice channels, group dms, or dms. Returns the [Get Channel](/docs/topics/rpc#getchannel) response, `null` if none.
+Used to join and leave voice channels, group dms, or dms. Returns the [Get Channel](/developers/docs/topics/rpc#getchannel) response, `null` if none.
###### Select Voice Channel Argument Structure
@@ -544,9 +546,11 @@ Used to join and leave voice channels, group dms, or dms. Returns the [Get Chann
| force | boolean | forces a user to join a voice channel |
| navigate | boolean | after joining the voice channel, navigate to it in the client |
-:::warn
+
+
When trying to join the user to a voice channel, you will receive a `5003` error coded response if the user is already in a voice channel. The `force` parameter should only be specified in response to the case where a user is already in a voice channel and they have **approved** to be moved by your app to a new voice channel.
-:::
+
+
###### Example Select Voice Channel Command Payload
@@ -605,11 +609,11 @@ When trying to join the user to a voice channel, you will receive a `5003` error
#### GET_SELECTED_VOICE_CHANNEL
-Used to get the client's current voice channel. There are no arguments for this command. Returns the [Get Channel](/docs/topics/rpc#getchannel) response, or `null` if none.
+Used to get the client's current voice channel. There are no arguments for this command. Returns the [Get Channel](/developers/docs/topics/rpc#getchannel) response, or `null` if none.
#### SELECT_TEXT_CHANNEL
-Used to join and leave text channels, group dms, or dms. Returns the [Get Channel](/docs/topics/rpc#getchannel) response, or `null` if none.
+Used to join and leave text channels, group dms, or dms. Returns the [Get Channel](/developers/docs/topics/rpc#getchannel) response, or `null` if none.
###### Select Text Channel Argument Structure
@@ -622,18 +626,18 @@ Used to join and leave text channels, group dms, or dms. Returns the [Get Channe
###### Get Voice Settings Response Structure
-| Field | Type | Description |
-|------------------------|------------------------------------------------------------------------------------------------|-----------------------------------|
-| input | [voice settings input](/docs/topics/rpc#getvoicesettings-voice-settings-input-object) object | input settings |
-| output | [voice settings output](/docs/topics/rpc#getvoicesettings-voice-settings-output-object) object | output settings |
-| mode | [voice settings mode](/docs/topics/rpc#getvoicesettings-voice-settings-mode-object) object | voice mode settings |
-| automatic_gain_control | boolean | state of automatic gain control |
-| echo_cancellation | boolean | state of echo cancellation |
-| noise_suppression | boolean | state of noise suppression |
-| qos | boolean | state of voice quality of service |
-| silence_warning | boolean | state of silence warning notice |
-| deaf | boolean | state of self-deafen |
-| mute | boolean | state of self-mute |
+| Field | Type | Description |
+|------------------------|-----------------------------------------------------------------------------------------------------------|-----------------------------------|
+| input | [voice settings input](/developers/docs/topics/rpc#getvoicesettings-voice-settings-input-object) object | input settings |
+| output | [voice settings output](/developers/docs/topics/rpc#getvoicesettings-voice-settings-output-object) object | output settings |
+| mode | [voice settings mode](/developers/docs/topics/rpc#getvoicesettings-voice-settings-mode-object) object | voice mode settings |
+| automatic_gain_control | boolean | state of automatic gain control |
+| echo_cancellation | boolean | state of echo cancellation |
+| noise_suppression | boolean | state of noise suppression |
+| qos | boolean | state of voice quality of service |
+| silence_warning | boolean | state of silence warning notice |
+| deaf | boolean | state of self-deafen |
+| mute | boolean | state of self-mute |
###### Voice Settings Input Object
@@ -653,21 +657,21 @@ Used to join and leave text channels, group dms, or dms. Returns the [Get Channe
###### Voice Settings Mode Object
-| Field | Type | Description |
-|----------------|------------------------------------------------------------------------------------------|---------------------------------------------------------------------|
-| type | string | voice setting mode type (can be `PUSH_TO_TALK` or `VOICE_ACTIVITY`) |
-| auto_threshold | boolean | voice activity threshold automatically sets its threshold |
-| threshold | float | threshold for voice activity (in dB) (min: -100, max: 0) |
-| shortcut | [shortcut key combo](/docs/topics/rpc#getvoicesettings-shortcut-key-combo-object) object | shortcut key combos for PTT |
-| delay | float | the PTT release delay (in ms) (min: 0, max: 2000) |
+| Field | Type | Description |
+|----------------|-----------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|
+| type | string | voice setting mode type (can be `PUSH_TO_TALK` or `VOICE_ACTIVITY`) |
+| auto_threshold | boolean | voice activity threshold automatically sets its threshold |
+| threshold | float | threshold for voice activity (in dB) (min: -100, max: 0) |
+| shortcut | [shortcut key combo](/developers/docs/topics/rpc#getvoicesettings-shortcut-key-combo-object) object | shortcut key combos for PTT |
+| delay | float | the PTT release delay (in ms) (min: 0, max: 2000) |
###### Shortcut Key Combo Object
-| Field | Type | Description |
-|-------|---------|--------------------------------------------------------------|
-| type | integer | see [key types](/docs/topics/rpc#getvoicesettings-key-types) |
-| code | integer | key code |
-| name | string | key name |
+| Field | Type | Description |
+|-------|---------|-------------------------------------------------------------------------|
+| type | integer | see [key types](/developers/docs/topics/rpc#getvoicesettings-key-types) |
+| code | integer | key code |
+| name | string | key name |
###### Key Types
@@ -733,26 +737,28 @@ Used to join and leave text channels, group dms, or dms. Returns the [Get Channe
#### SET_VOICE_SETTINGS
-:::info
+
+
In the current release, we only support a single modifier of voice settings at a time over RPC. If an app changes voice settings, it will lock voice settings so that other apps connected simultaneously lose the ability to change voice settings. Settings reset to what they were before being changed after the controlling app disconnects. When an app that has previously set voice settings connects, the client will swap to that app's configured voice settings and lock voice settings again. This is a temporary situation that will be changed in the future.
-:::
+
+
When setting voice settings, all fields are optional. Only passed fields are updated.
###### Set Voice Settings Argument and Response Structure
-| Field | Type | Description |
-|------------------------|------------------------------------------------------------------------------------------------|-----------------------------------|
-| input | [voice settings input](/docs/topics/rpc#getvoicesettings-voice-settings-input-object) object | input settings |
-| output | [voice settings output](/docs/topics/rpc#getvoicesettings-voice-settings-output-object) object | output settings |
-| mode | [voice settings mode](/docs/topics/rpc#getvoicesettings-voice-settings-mode-object) object | voice mode settings |
-| automatic_gain_control | boolean | state of automatic gain control |
-| echo_cancellation | boolean | state of echo cancellation |
-| noise_suppression | boolean | state of noise suppression |
-| qos | boolean | state of voice quality of service |
-| silence_warning | boolean | state of silence warning notice |
-| deaf | boolean | state of self-deafen |
-| mute | boolean | state of self-mute |
+| Field | Type | Description |
+|------------------------|-----------------------------------------------------------------------------------------------------------|-----------------------------------|
+| input | [voice settings input](/developers/docs/topics/rpc#getvoicesettings-voice-settings-input-object) object | input settings |
+| output | [voice settings output](/developers/docs/topics/rpc#getvoicesettings-voice-settings-output-object) object | output settings |
+| mode | [voice settings mode](/developers/docs/topics/rpc#getvoicesettings-voice-settings-mode-object) object | voice mode settings |
+| automatic_gain_control | boolean | state of automatic gain control |
+| echo_cancellation | boolean | state of echo cancellation |
+| noise_suppression | boolean | state of noise suppression |
+| qos | boolean | state of voice quality of service |
+| silence_warning | boolean | state of silence warning notice |
+| deaf | boolean | state of self-deafen |
+| mute | boolean | state of self-mute |
###### Example Set Voice Settings Command Payload
@@ -897,23 +903,23 @@ Used by hardware manufacturers to send information about the current state of th
###### Set Certified Devices Argument Structure
-| Field | Type | Description |
-|---------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------|
-| devices | array of [certified device](/docs/topics/rpc#setcertifieddevices-device-object) objects | a list of devices for your manufacturer, in order of priority |
+| Field | Type | Description |
+|---------|----------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| devices | array of [certified device](/developers/docs/topics/rpc#setcertifieddevices-device-object) objects | a list of devices for your manufacturer, in order of priority |
###### Device Object
-| Field | Type | Description |
-|---------------------------|---------------------------------------------------------------------|----------------------------------------------------------|
-| type | [device type](/docs/topics/rpc#setcertifieddevices-device-type) | the type of device |
-| id | string | the device's Windows UUID |
-| vendor | [vendor](/docs/topics/rpc#setcertifieddevices-vendor-object) object | the hardware vendor |
-| model | [model](/docs/topics/rpc#setcertifieddevices-model-object) object | the model of the product |
-| related | array of strings | UUIDs of related devices |
-| echo_cancellation?\* | boolean | if the device's native echo cancellation is enabled |
-| noise_suppression?\* | boolean | if the device's native noise suppression is enabled |
-| automatic_gain_control?\* | boolean | if the device's native automatic gain control is enabled |
-| hardware_mute?\* | boolean | if the device is hardware muted |
+| Field | Type | Description |
+|---------------------------|--------------------------------------------------------------------------------|----------------------------------------------------------|
+| type | [device type](/developers/docs/topics/rpc#setcertifieddevices-device-type) | the type of device |
+| id | string | the device's Windows UUID |
+| vendor | [vendor](/developers/docs/topics/rpc#setcertifieddevices-vendor-object) object | the hardware vendor |
+| model | [model](/developers/docs/topics/rpc#setcertifieddevices-model-object) object | the model of the product |
+| related | array of strings | UUIDs of related devices |
+| echo_cancellation?\* | boolean | if the device's native echo cancellation is enabled |
+| noise_suppression?\* | boolean | if the device's native noise suppression is enabled |
+| automatic_gain_control?\* | boolean | if the device's native automatic gain control is enabled |
+| hardware_mute?\* | boolean | if the device is hardware muted |
\*These fields are only applicable for `AUDIO_INPUT` device types
@@ -986,14 +992,14 @@ Used to update a user's Rich Presence.
###### Set Activity Argument Structure
-:::info
+
When using `SET_ACTIVITY`, the `activity` object is limited to a `type` of Playing (`0`), Listening (`2`), Watching (`3`), or Competing (`5`).
-:::
+
-| Field | Type | Description |
-|----------|----------------------------------------------------------------|-----------------------------------------|
-| pid | integer | the application's process id |
-| activity | [activity](/docs/events/gateway-events#activity-object) object | the rich presence to assign to the user |
+| Field | Type | Description |
+|----------|---------------------------------------------------------------------------|-----------------------------------------|
+| pid | integer | the application's process id |
+| activity | [activity](/developers/docs/events/gateway-events#activity-object) object | the rich presence to assign to the user |
###### Example Set Activity Payload
@@ -1083,11 +1089,11 @@ Used to reject an Ask to Join request.
###### Ready Dispatch Data Structure
-| Field | Type | Description |
-|--------|-------------------------------------------------------------------------------------------|------------------------------------|
-| v | integer | RPC version |
-| config | [rpc server configuration](/docs/topics/rpc#ready-rpc-server-configuration-object) object | server configuration |
-| user | partial [user](/docs/resources/user#user-object) object | the user to whom you are connected |
+| Field | Type | Description |
+|--------|------------------------------------------------------------------------------------------------------|------------------------------------|
+| v | integer | RPC version |
+| config | [rpc server configuration](/developers/docs/topics/rpc#ready-rpc-server-configuration-object) object | server configuration |
+| user | partial [user](/developers/docs/resources/user#user-object) object | the user to whom you are connected |
###### RPC Server Configuration Object
@@ -1153,10 +1159,10 @@ Used to reject an Ask to Join request.
###### Guild Status Dispatch Data Structure
-| Field | Type | Description |
-|--------|------------------------------------------------------------|--------------------------------------------------------|
-| guild | partial [guild](/docs/resources/guild#guild-object) object | guild with requested id |
-| online | integer | number of online users in guild (deprecated; always 0) |
+| Field | Type | Description |
+|--------|-----------------------------------------------------------------------|--------------------------------------------------------|
+| guild | partial [guild](/developers/docs/resources/guild#guild-object) object | guild with requested id |
+| online | integer | number of online users in guild (deprecated; always 0) |
###### Example Guild Status Dispatch Payload
@@ -1253,7 +1259,7 @@ No arguments
###### Voice Settings Argument Structure
-No arguments. Dispatches the [Get Voice Settings](/docs/topics/rpc#getvoicesettings) response.
+No arguments. Dispatches the [Get Voice Settings](/developers/docs/topics/rpc#getvoicesettings) response.
###### Example Voice Settings Dispatch Payload
@@ -1472,17 +1478,17 @@ Dispatches message objects, with the exception of deletions, which only contains
#### NOTIFICATION_CREATE
-No arguments. This event requires the `rpc.notifications.read` [OAuth2 scope](/docs/topics/oauth2#shared-resources-oauth2-scopes).
+No arguments. This event requires the `rpc.notifications.read` [OAuth2 scope](/developers/docs/topics/oauth2#shared-resources-oauth2-scopes).
###### Notification Create Dispatch Data Structure
-| Field | Type | Description |
-|------------|----------------------------------------------------------|-------------------------------------------|
-| channel_id | string | id of channel where notification occurred |
-| message | [message](/docs/resources/message#message-object) object | message that generated this notification |
-| icon_url | string | icon url of the notification |
-| title | string | title of the notification |
-| body | string | body of the notification |
+| Field | Type | Description |
+|------------|---------------------------------------------------------------------|-------------------------------------------|
+| channel_id | string | id of channel where notification occurred |
+| message | [message](/developers/docs/resources/message#message-object) object | message that generated this notification |
+| icon_url | string | icon url of the notification |
+| title | string | title of the notification |
+| body | string | body of the notification |
###### Example Notification Create Dispatch Payload
@@ -1534,9 +1540,9 @@ No arguments
###### Activity Join Dispatch Data Structure
-| Field | Type | Description |
-|--------|--------|-------------------------------------------------------------------------------------------------|
-| secret | string | the [`join_secret`](/docs/developer-tools/game-sdk#activitysecrets-struct) for the given invite |
+| Field | Type | Description |
+|--------|--------|------------------------------------------------------------------------------------------------------------|
+| secret | string | the [`join_secret`](/developers/docs/developer-tools/game-sdk#activitysecrets-struct) for the given invite |
###### Example Activity Join Dispatch Payload
@@ -1556,9 +1562,9 @@ No arguments
###### Activity Spectate Dispatch Data Structure
-| Field | Type | Description |
-|--------|--------|-----------------------------------------------------------------------------------------------------|
-| secret | string | the [`spectate_secret`](/docs/developer-tools/game-sdk#activitysecrets-struct) for the given invite |
+| Field | Type | Description |
+|--------|--------|----------------------------------------------------------------------------------------------------------------|
+| secret | string | the [`spectate_secret`](/developers/docs/developer-tools/game-sdk#activitysecrets-struct) for the given invite |
###### Example Activity Spectate Dispatch Payload
@@ -1578,9 +1584,9 @@ No arguments
###### Activity Join Request Data Structure
-| Field | Type | Description |
-|-------|---------------------------------------------------------|-----------------------------------------------|
-| user | partial [user](/docs/resources/user#user-object) object | information about the user requesting to join |
+| Field | Type | Description |
+|-------|--------------------------------------------------------------------|-----------------------------------------------|
+| user | partial [user](/developers/docs/resources/user#user-object) object | information about the user requesting to join |
###### Example Activity Join Request Dispatch Payload
diff --git a/discord/developers/docs/topics/rpc.mdx b/discord/developers/docs/topics/rpc.mdx
new file mode 100644
index 0000000000..a93353e9bb
--- /dev/null
+++ b/discord/developers/docs/topics/rpc.mdx
@@ -0,0 +1,1734 @@
+---
+title: RPC
+description: Learn about Discord's Rich Presence Client (RPC) for local application integration.
+---
+
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+
+
+
+For now, RPC is in a private beta. We are not currently accepting any new developers into the program at this time.
+
+
+All Discord clients have an RPC server running on localhost that allows control over local Discord clients.
+
+
+In the current release, we only support a single modifier of voice settings at a time over RPC. If an app changes voice settings, it will lock voice settings so that other apps connected simultaneously lose the ability to change voice settings. Settings reset to what they were before being changed after the controlling app disconnects. When an app that has previously set voice settings connects, the client will swap to that app's configured voice settings and lock voice settings again. This is a temporary situation that will be changed in the future.
+
+
+
+When trying to join the user to a voice channel, you will receive a `5003` error coded response if the user is already in a voice channel. The `force` parameter should only be specified in response to the case where a user is already in a voice channel and they have **approved** to be moved by your app to a new voice channel.
+
+
+
+In the current release, we only support a single modifier of voice settings at a time over RPC. If an app changes voice settings, it will lock voice settings so that other apps connected simultaneously lose the ability to change voice settings. Settings reset to what they were before being changed after the controlling app disconnects. When an app that has previously set voice settings connects, the client will swap to that app's configured voice settings and lock voice settings again. This is a temporary situation that will be changed in the future.
+
+
+When setting voice settings, all fields are optional. Only passed fields are updated.
+
+
+When using `SET_ACTIVITY`, the `activity` object is limited to a `type` of Playing (`0`), Listening (`2`), Watching (`3`), or Competing (`5`).
+
+
+| Field | Type | Description |
+|----------|---------------------------------------------------------------------------|-----------------------------------------|
+| pid | integer | the application's process id |
+| activity | [activity](/developers/docs/events/gateway-events#activity-object) object | the rich presence to assign to the user |
+
+
+
Only the team Owner and team Admins can invite or remove additional users.
-:::
+
+
## Adding Apps to a Team
@@ -22,17 +24,19 @@ Once your team is set up, you can create or transfer apps that will be owned by
To create a new app that belongs to a team, select the team from the **Team** dropdown in the app creation modal. If you want to keep the app under your own account's ownership, choose `Personal`:
-
+
### Transferring an App
To transfer an existing app to a team, navigate to the [Application](https://discord.com/developers/applications) that you want to transfer. At the bottom of the app's **General Information** page, click "Transfer App to Team".
-:::danger
+
+
Once an app has been transferred to a team, it _cannot_ be transferred back.
-:::
-
+
+
+
## Team Member Roles
@@ -47,28 +51,28 @@ Team members can be one of four roles (owner, admin, developer, and read-only),
| Developer | developer | Developers can access information about team-owned apps, like the client secret or public key. They can also take limited actions on team-owned apps, like configuring interaction endpoints or resetting the bot token. Members with the Developer role *cannot* manage the team or its members, or take destructive actions on team-owned apps. |
| Read-only | read_only | Read-only members can access information about a team and any team-owned apps. Some examples include getting the IDs of applications and exporting payout records. Members can also invite bots associated with team-owned apps that are marked private. |
-\* The owner role is not represented in the `role` field on the [team member object](/docs/topics/teams#data-models-team-member-object). Instead, the `owner_user_id` field on the [team object](/docs/topics/teams#data-models-team-object) should be used to identify which user has the owner role for the team.
+\* The owner role is not represented in the `role` field on the [team member object](/developers/docs/topics/teams#data-models-team-member-object). Instead, the `owner_user_id` field on the [team object](/developers/docs/topics/teams#data-models-team-object) should be used to identify which user has the owner role for the team.
## Data Models
###### Team Object
-| field | type | description |
-|---------------|-----------------------------------------------------------------------------------|--------------------------------------|
-| icon | ?string | Hash of the image of the team's icon |
-| id | snowflake | Unique ID of the team |
-| members | array of [team member](/docs/topics/teams#data-models-team-member-object) objects | Members of the team |
-| name | string | Name of the team |
-| owner_user_id | snowflake | User ID of the current team owner |
+| field | type | description |
+|---------------|----------------------------------------------------------------------------------------------|--------------------------------------|
+| icon | ?string | Hash of the image of the team's icon |
+| id | snowflake | Unique ID of the team |
+| members | array of [team member](/developers/docs/topics/teams#data-models-team-member-object) objects | Members of the team |
+| name | string | Name of the team |
+| owner_user_id | snowflake | User ID of the current team owner |
###### Team Member Object
-| field | type | description |
-|------------------|---------------------------------------------------------|---------------------------------------------------------------------------------------------|
-| membership_state | integer | User's [membership state](/docs/topics/teams#data-models-membership-state-enum) on the team |
-| team_id | snowflake | ID of the parent team of which they are a member |
-| user | partial [user](/docs/resources/user#user-object) object | Avatar, discriminator, ID, and username of the user |
-| role | string | [Role](/docs/topics/teams#team-member-roles-team-member-role-types) of the team member |
+| field | type | description |
+|------------------|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|
+| membership_state | integer | User's [membership state](/developers/docs/topics/teams#data-models-membership-state-enum) on the team |
+| team_id | snowflake | ID of the parent team of which they are a member |
+| user | partial [user](/developers/docs/resources/user#user-object) object | Avatar, discriminator, ID, and username of the user |
+| role | string | [Role](/developers/docs/topics/teams#team-member-roles-team-member-role-types) of the team member |
###### Membership State Enum
diff --git a/discord/developers/docs/topics/teams.mdx b/discord/developers/docs/topics/teams.mdx
new file mode 100644
index 0000000000..765c31f282
--- /dev/null
+++ b/discord/developers/docs/topics/teams.mdx
@@ -0,0 +1,87 @@
+---
+title: Teams
+description: Learn how to create and manage developer teams for collaborative development.
+---
+
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+
+Teams are groups of developers (or other Discord users) who want to collaborate and share access to an app's configuration, management, and payout settings. Go team(s)!
+
+## Creating a Team
+
+To create or be a member on a team, you must [enable 2FA for your Discord account](https://support.discord.com/hc/en-us/articles/219576828-Setting-up-Two-Factor-Authentication). After you have 2FA enabled, create a team by navigating to the [Teams page](https://discord.com/developers/teams) then clicking the "New Team" button.
+
+
+
+Once you create a team, you'll land on the **Team Information** page where you can fill out details and start inviting other Discord users to join your team. Since users added to a team have access to any apps that team owns, use caution when adding new team members.
+
+
+Only the team Owner and team Admins can invite or remove additional users.
+
+
+## Adding Apps to a Team
+
+Once your team is set up, you can create or transfer apps that will be owned by the team. Teams can have a maximum of 25 apps.
+
+### Creating an App
+
+To create a new app that belongs to a team, select the team from the **Team** dropdown in the app creation modal. If you want to keep the app under your own account's ownership, choose `Personal`:
+
+
+
+### Transferring an App
+
+To transfer an existing app to a team, navigate to the [Application](https://discord.com/developers/applications) that you want to transfer. At the bottom of the app's **General Information** page, click "Transfer App to Team".
+
+
+Once an app has been transferred to a team, it _cannot_ be transferred back.
+
+
+
+
+## Team Member Roles
+
+Team members can be one of four roles (owner, admin, developer, and read-only), and each role inherits the access of those below it. Roles for team members can be configured under **Team Members** in a team's settings.
+
+
+
The `SEND_MESSAGES` permission has no effect in threads; users must have `SEND_MESSAGES_IN_THREADS` to talk in a thread.
-:::
+
+
Private threads are similar to Group DMs, but in a guild: You must be invited to the thread to be able to view or participate in it, or be a moderator (`MANAGE_THREADS` permission).
@@ -77,36 +79,36 @@ Finally, threads are treated slightly differently from channels in the gateway p
## Gateway Events
-- [Guild Create](/docs/events/gateway-events#guild-create) contains a field, `threads`, which is an array of channel objects. This represents all active threads in the guild that the current user is able to view.
-- When a thread is created, updated, or deleted, a [Thread Create](/docs/events/gateway-events#thread-create), [Thread Update](/docs/events/gateway-events#thread-update), or [Thread Delete](/docs/events/gateway-events#thread-delete) event is sent. Like their channel counterparts, these just contain a thread.
-- Since the gateway only syncs active threads that the user can see, if a user _gains_ access to a channel, then the gateway may need to sync the active threads in that channel to the user. It will send a [Thread List Sync](/docs/events/gateway-events#thread-list-sync) event for this.
+- [Guild Create](/developers/docs/events/gateway-events#guild-create) contains a field, `threads`, which is an array of channel objects. This represents all active threads in the guild that the current user is able to view.
+- When a thread is created, updated, or deleted, a [Thread Create](/developers/docs/events/gateway-events#thread-create), [Thread Update](/developers/docs/events/gateway-events#thread-update), or [Thread Delete](/developers/docs/events/gateway-events#thread-delete) event is sent. Like their channel counterparts, these just contain a thread.
+- Since the gateway only syncs active threads that the user can see, if a user _gains_ access to a channel, then the gateway may need to sync the active threads in that channel to the user. It will send a [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) event for this.
## Thread Membership
Each thread tracks explicit membership. There are two primary use cases for this data:
-- Clients use _their own_ [thread member](/docs/resources/channel#thread-member-object) to calculate read states and notification settings. This is largely irrelevant for bots though, but is the reason for some of the syncing complexity detailed here.
+- Clients use _their own_ [thread member](/developers/docs/resources/channel#thread-member-object) to calculate read states and notification settings. This is largely irrelevant for bots though, but is the reason for some of the syncing complexity detailed here.
- Knowing everyone that is in a thread.
-Membership is tracked in an array of [thread member](/docs/resources/channel#thread-member-object) objects. These have four fields, `id` (the thread id), `user_id`, `join_timestamp`, and `flags`. Currently the only `flags` are for notification settings, but others may be added in future updates.
+Membership is tracked in an array of [thread member](/developers/docs/resources/channel#thread-member-object) objects. These have four fields, `id` (the thread id), `user_id`, `join_timestamp`, and `flags`. Currently the only `flags` are for notification settings, but others may be added in future updates.
### Syncing for the current user
-- A [Thread Members Update](/docs/events/gateway-events#thread-members-update) Gateway Event is always sent when the current user is added to or removed from a thread.
-- A [Thread Member Update](/docs/events/gateway-events#thread-member-update) Gateway Event is sent whenever the current user's [thread member](/docs/resources/channel#thread-member-object) object is updated.
-- Certain API calls, such as listing archived threads and search will return an array of [thread member](/docs/resources/channel#thread-member-object) objects for any returned threads the current user is a member of. Other API calls, such as getting a channel will return the [thread member](/docs/resources/channel#thread-member-object) object for the current user as a property on the channel, if the current user is a member of the thread.
-- The [Guild Create](/docs/events/gateway-events#guild-create) Gateway Event will contain a [thread member](/docs/resources/channel#thread-member-object) object as a property on any returned threads the current is a member of.
-- The [Thread Create](/docs/events/gateway-events#thread-create) Gateway Event will contain a [thread member](/docs/resources/channel#thread-member-object) object as a property of the thread if the current user is a member of, and the user has recently gained access to view the parent channel.
-- The [Thread List Sync](/docs/events/gateway-events#thread-list-sync) Gateway Event will contain an array of [thread member](/docs/resources/channel#thread-member-object) objects for any returned threads the current user is a member of.
+- A [Thread Members Update](/developers/docs/events/gateway-events#thread-members-update) Gateway Event is always sent when the current user is added to or removed from a thread.
+- A [Thread Member Update](/developers/docs/events/gateway-events#thread-member-update) Gateway Event is sent whenever the current user's [thread member](/developers/docs/resources/channel#thread-member-object) object is updated.
+- Certain API calls, such as listing archived threads and search will return an array of [thread member](/developers/docs/resources/channel#thread-member-object) objects for any returned threads the current user is a member of. Other API calls, such as getting a channel will return the [thread member](/developers/docs/resources/channel#thread-member-object) object for the current user as a property on the channel, if the current user is a member of the thread.
+- The [Guild Create](/developers/docs/events/gateway-events#guild-create) Gateway Event will contain a [thread member](/developers/docs/resources/channel#thread-member-object) object as a property on any returned threads the current is a member of.
+- The [Thread Create](/developers/docs/events/gateway-events#thread-create) Gateway Event will contain a [thread member](/developers/docs/resources/channel#thread-member-object) object as a property of the thread if the current user is a member of, and the user has recently gained access to view the parent channel.
+- The [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) Gateway Event will contain an array of [thread member](/developers/docs/resources/channel#thread-member-object) objects for any returned threads the current user is a member of.
### Syncing for other users
-:::info
-These require the `GUILD_MEMBERS` [Gateway Intent](/docs/events/gateway#gateway-intents)
-:::
+
+These require the `GUILD_MEMBERS` [Gateway Intent](/developers/docs/events/gateway#gateway-intents)
+
-- An API `GET` call to [`/channels//thread-members`](/docs/resources/channel#list-thread-members) which returns an array of [thread member](/docs/resources/channel#thread-member-object) objects.
-- The [Thread Members Update](/docs/events/gateway-events#thread-members-update) Gateway Event which will include all users who were added to or removed from a thread by an action.
+- An API `GET` call to [`/channels//thread-members`](/developers/docs/resources/channel#list-thread-members) which returns an array of [thread member](/developers/docs/resources/channel#thread-member-object) objects.
+- The [Thread Members Update](/developers/docs/events/gateway-events#thread-members-update) Gateway Event which will include all users who were added to or removed from a thread by an action.
## Editing & Deleting Threads
@@ -123,31 +125,31 @@ Threads do not explicitly set the `nsfw` field. All threads in a channel marked
## New Message Types
-Threads introduce a few [message types](/docs/resources/message#message-object-message-types), and repurpose some others:
+Threads introduce a few [message types](/developers/docs/resources/message#message-object-message-types), and repurpose some others:
- `RECIPIENT_ADD` and `RECIPIENT_REMOVE` have been repurposed to also send when a user is added to or removed from a thread by someone else
- `CHANNEL_NAME_CHANGE` has been repurposed and is sent when the thread's name is changed
-- `THREAD_CREATED` is a new message sent to the parent `GUILD_TEXT` channel, used to inform users that a thread has been created. It is currently only sent in one case: when a `PUBLIC_THREAD` is created from an older message (older is still TBD, but is currently set to a very small value). The message contains a [message reference](/docs/resources/message#message-reference-structure) with the `guild_id` and `channel_id` of the thread. The `content` of the message is the `name` of the thread.
-- `THREAD_STARTER_MESSAGE` is a new message sent as the first message in threads that are started from an existing message in the parent channel. It _only_ contains a [message reference](/docs/resources/message#message-reference-structure) field that points to the message from which the thread was started.
+- `THREAD_CREATED` is a new message sent to the parent `GUILD_TEXT` channel, used to inform users that a thread has been created. It is currently only sent in one case: when a `PUBLIC_THREAD` is created from an older message (older is still TBD, but is currently set to a very small value). The message contains a [message reference](/developers/docs/resources/message#message-reference-structure) with the `guild_id` and `channel_id` of the thread. The `content` of the message is the `name` of the thread.
+- `THREAD_STARTER_MESSAGE` is a new message sent as the first message in threads that are started from an existing message in the parent channel. It _only_ contains a [message reference](/developers/docs/resources/message#message-reference-structure) field that points to the message from which the thread was started.
## Enumerating threads
There are four `GET` routes for enumerating threads in a specific channel:
-- [`/guilds//threads/active`](/docs/resources/guild#list-active-guild-threads) returns all active threads in a guild that the current user can access, includes public & private threads
-- [`/channels//users/@me/threads/archived/private`](/docs/resources/channel#list-joined-private-archived-threads) returns all archived, private threads in a channel, that the current user has is a member of, sorted by thread id descending
-- [`/channels//threads/archived/public`](/docs/resources/channel#list-public-archived-threads) returns all archived, public threads in a channel, sorted by archive timestamp descending
-- [`/channels//threads/archived/private`](/docs/resources/channel#list-private-archived-threads) returns all archived, private threads in a channel, sorted by archive timestamp descending
+- [`/guilds//threads/active`](/developers/docs/resources/guild#list-active-guild-threads) returns all active threads in a guild that the current user can access, includes public & private threads
+- [`/channels//users/@me/threads/archived/private`](/developers/docs/resources/channel#list-joined-private-archived-threads) returns all archived, private threads in a channel, that the current user has is a member of, sorted by thread id descending
+- [`/channels//threads/archived/public`](/developers/docs/resources/channel#list-public-archived-threads) returns all archived, public threads in a channel, sorted by archive timestamp descending
+- [`/channels//threads/archived/private`](/developers/docs/resources/channel#list-private-archived-threads) returns all archived, private threads in a channel, sorted by archive timestamp descending
## Webhooks
-Webhooks can send messages to threads by using the `thread_id` query parameter. See the [execute webhook](/docs/resources/webhook#execute-webhook) docs for more details.
+Webhooks can send messages to threads by using the `thread_id` query parameter. See the [execute webhook](/developers/docs/resources/webhook#execute-webhook) docs for more details.
## Details about Thread Access and Syncing
-While the syncing of threads is similar to channels, there are two important differences that are relevant for [Thread List Sync](/docs/events/gateway-events#thread-list-sync) and [Thread Create](/docs/events/gateway-events#thread-create) events:
+While the syncing of threads is similar to channels, there are two important differences that are relevant for [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) and [Thread Create](/developers/docs/events/gateway-events#thread-create) events:
-1. The [Gateway](/docs/events/gateway) will only sync threads that the app has permission to view
+1. The [Gateway](/developers/docs/events/gateway) will only sync threads that the app has permission to view
2. The Gateway will only sync threads once the app has "subscribed" to the guild. For context, in Discord's official clients, a subscription happens when the user visits a channel in the guild.
These differences mean there is some unique behavior that is worth going into.
@@ -158,44 +160,44 @@ These differences mean there is some unique behavior that is worth going into.
When an app is added to a private thread, it likely doesn't have that thread in memory yet since it doesn't have permission to view it.
-Private threads are only synced to you if you are a member or a moderator. Whenever a user is added to a private thread, the Gateway also sends a [Thread Create](/docs/events/gateway-events#thread-create) event. This ensures the client always has a non-null value for that thread.
+Private threads are only synced to you if you are a member or a moderator. Whenever a user is added to a private thread, the Gateway also sends a [Thread Create](/developers/docs/events/gateway-events#thread-create) event. This ensures the client always has a non-null value for that thread.
-:::info
+
The `THREAD_CREATE` event is also sent when the user is a moderator (and thus would already have the channel in memory).
-:::
+
#### Gaining Access to Public Threads
Upon connecting to the Gateway, apps will be automatically subscribed to thread events and active threads.
-However, when a non-app is added to a public thread but hasn't subscribed to threads, it may not have that thread in memory yet (which is a requirement for Discord's clients). Because of this, the Gateway will send a [Thread Create](/docs/events/gateway-events#thread-create) event when a user is added to _any_ thread, even if the event is not necessary for apps.
+However, when a non-app is added to a public thread but hasn't subscribed to threads, it may not have that thread in memory yet (which is a requirement for Discord's clients). Because of this, the Gateway will send a [Thread Create](/developers/docs/events/gateway-events#thread-create) event when a user is added to _any_ thread, even if the event is not necessary for apps.
### Channel Access
#### Gaining Access to Channels
-When an app gains access to a channel (for example, they're given the moderator role), they likely won't have the threads in memory for that channel since the Gateway only syncs threads that the client has permission to view. To account for this, a [Thread List Sync](/docs/events/gateway-events#thread-list-sync) event is sent.
+When an app gains access to a channel (for example, they're given the moderator role), they likely won't have the threads in memory for that channel since the Gateway only syncs threads that the client has permission to view. To account for this, a [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) event is sent.
-The [Thread List Sync](/docs/events/gateway-events#thread-list-sync) event contains a `channel_ids` array, which is the IDs of all channels whose threads are being synced. This field can be used to first clear out any active threads whose `parent_id` is in the `channel_ids` array, and then ingest any threads that were in the event.
+The [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) event contains a `channel_ids` array, which is the IDs of all channels whose threads are being synced. This field can be used to first clear out any active threads whose `parent_id` is in the `channel_ids` array, and then ingest any threads that were in the event.
#### Losing Access to Channels
-When an app loses access to a channel, the Gateway does **not** send it [Thread Delete](/docs/events/gateway-events#thread-delete) event (or any equivalent thread-specific event). Instead, the app will receive the event that caused its permissions on the channel to change.
+When an app loses access to a channel, the Gateway does **not** send it [Thread Delete](/developers/docs/events/gateway-events#thread-delete) event (or any equivalent thread-specific event). Instead, the app will receive the event that caused its permissions on the channel to change.
-If an app wanted to track when it lost access to any thread, it's possible but difficult as it would need to handle all cases correctly. Usually, events that cause permission changes are a [Guild Role Update](/docs/events/gateway-events#guild-role-update), [Guild Member Update](/docs/events/gateway-events#guild-member-update) or [Channel Update](/docs/events/gateway-events#channel-update) event.
+If an app wanted to track when it lost access to any thread, it's possible but difficult as it would need to handle all cases correctly. Usually, events that cause permission changes are a [Guild Role Update](/developers/docs/events/gateway-events#guild-role-update), [Guild Member Update](/developers/docs/events/gateway-events#guild-member-update) or [Channel Update](/developers/docs/events/gateway-events#channel-update) event.
-:::info
+
Discord's clients check their permissions *first* when performing an action. That way, even if it has some stale data, it does not end up acting on it.
-:::
+
-Additionally, when a user or app loses access to a channel, they are not removed from the thread and will continue to be reported as a member of that thread. However, they will **not** receive any new Gateway events unless they are removed from the thread, in which case they will receive a [Thread Members Update](/docs/events/gateway-events#thread-members-update) event.
+Additionally, when a user or app loses access to a channel, they are not removed from the thread and will continue to be reported as a member of that thread. However, they will **not** receive any new Gateway events unless they are removed from the thread, in which case they will receive a [Thread Members Update](/developers/docs/events/gateway-events#thread-members-update) event.
### Unarchiving a Thread
When a thread is unarchived, there is no guarantee that an app has the thread or its member status in memory. To account for this, the Gateway will send two events (in the listed order):
-1. A [Thread Update](/docs/events/gateway-events#thread-update) event, which contains the full channel object.
-2. A [Thread Member Update](/docs/events/gateway-events#thread-member-update) event, which is sent to all members of the unarchived thread. Discord's clients only load active threads into memory on start, so this event is sent even if it may not be relevant to most apps.
+1. A [Thread Update](/developers/docs/events/gateway-events#thread-update) event, which contains the full channel object.
+2. A [Thread Member Update](/developers/docs/events/gateway-events#thread-member-update) event, which is sent to all members of the unarchived thread. Discord's clients only load active threads into memory on start, so this event is sent even if it may not be relevant to most apps.
## Forums
@@ -203,22 +205,26 @@ A `GUILD_FORUM` (type `15`) channel is similar to a `GUILD_TEXT` channel, except
Messages cannot be sent directly in forum channels.
-:::info
+
+
More information about forum channels and how they appear in Discord can be found in the [Forum Channels FAQ](https://support.discord.com/hc/en-us/articles/6208479917079-Forum-Channels-FAQ#h_01G69FJQWTWN88HFEHK7Z6X79N)
-:::
+
+
## Media Channels
A `GUILD_MEDIA` (type `16`) channel is similar to a `GUILD_FORUM` channel in that only threads can be created in them. Unless otherwise noted, threads in media channels behave in the same way as in forum channels - meaning they use the same endpoints and receive the same Gateway events. More information about media channels and how they appear in Discord can be found in the [media channels Help Center Article](https://creator-support.discord.com/hc/en-us/articles/14346342766743).
-:::warn
+
+
`GUILD_MEDIA` channels are in beta and still being actively developed. The API and other technical details are subject to change.
-:::
+
+
### Creating Threads in Forum and Media Channels
-Within thread-only channels, threads appear as posts. Threads can be created using the [`POST /channels//threads`](/docs/resources/channel#start-thread-in-forum-or-media-channel) endpoint with [slightly different parameters](/docs/resources/channel#start-thread-in-forum-or-media-channel-jsonform-params) than threads in text channels. For example, when creating threads in a threads-only channel, a message is created that has the same ID as the thread which requires you to pass parameters for both a thread *and* a message.
+Within thread-only channels, threads appear as posts. Threads can be created using the [`POST /channels//threads`](/developers/docs/resources/channel#start-thread-in-forum-or-media-channel) endpoint with [slightly different parameters](/developers/docs/resources/channel#start-thread-in-forum-or-media-channel-jsonform-params) than threads in text channels. For example, when creating threads in a threads-only channel, a message is created that has the same ID as the thread which requires you to pass parameters for both a thread *and* a message.
Threads in thread-only channels have the same permissions behavior as threads in a text channel, inheriting all permissions from the parent channel, with one exception: creating a thread in a thread-only channel only requires the `SEND_MESSAGES` permission.
@@ -226,21 +232,21 @@ Threads in thread-only channels have the same permissions behavior as threads in
It's worth calling out a few details about fields specific to thread-only channels that may be important to keep in mind:
-- The `last_message_id` field is the ID of the most recently created thread in that channel. As with messages, your app will not receive a `CHANNEL_UPDATE` event when the field is changed. Instead clients should update the value when receiving [Thread Create](/docs/events/gateway-events#thread-create) events.
+- The `last_message_id` field is the ID of the most recently created thread in that channel. As with messages, your app will not receive a `CHANNEL_UPDATE` event when the field is changed. Instead clients should update the value when receiving [Thread Create](/developers/docs/events/gateway-events#thread-create) events.
- The `topic` field is what is shown in the "Guidelines" section within the Discord client.
- The `rate_limit_per_user` field limits how frequently threads can be created. There is a new `default_thread_rate_limit_per_user` field on thread-only channels as well, which limits how often messages can be sent _in a thread_. This field is copied into `rate_limit_per_user` on the thread at creation time.
- The `available_tags` field can be set when creating or updating a channel, which determines which tags can be set on individual threads within the thread's `applied_tags` field.
-- The `flags` field indicates any [channel flags](/docs/resources/channel#channel-object-channel-flags) set for a thread-only channel. Currently only `REQUIRE_TAG` can be used, which requires that a tag from `available_tags` be specified when creating a thread in that channel.
+- The `flags` field indicates any [channel flags](/developers/docs/resources/channel#channel-object-channel-flags) set for a thread-only channel. Currently only `REQUIRE_TAG` can be used, which requires that a tag from `available_tags` be specified when creating a thread in that channel.
-All fields for channels, including thread-only channels, can be found in the [Channel Object](/docs/resources/channel#channel-object).
+All fields for channels, including thread-only channels, can be found in the [Channel Object](/developers/docs/resources/channel#channel-object).
### Forum and Media Channel Thread Fields
-A thread can be pinned within a thread-only, which will be represented as the [`PINNED` flag](/docs/resources/channel#channel-object-channel-flags) in the `flags` field within a thread-only channel. A thread that is pinned will have the `(1 << 1)` flag set, and archiving that thread will unset the flag. A pinned thread will *not* auto-archive.
+A thread can be pinned within a thread-only, which will be represented as the [`PINNED` flag](/developers/docs/resources/channel#channel-object-channel-flags) in the `flags` field within a thread-only channel. A thread that is pinned will have the `(1 << 1)` flag set, and archiving that thread will unset the flag. A pinned thread will *not* auto-archive.
The `message_count` and `total_message_sent` fields on threads in thread-only channels will increment on `MESSAGE_CREATE` events, and decrement on `MESSAGE_DELETE` and `MESSAGE_DELETE_BULK` events. There will be no specific `CHANNEL_UPDATE` event that notifies your app of changes to those fields—instead, apps should update those values when receiving corresponding events.
-All fields for threads in thread-only channels can be found in the [channel resources documentation](/docs/resources/channel#start-thread-in-forum-or-media-channel-jsonform-params).
+All fields for threads in thread-only channels can be found in the [channel resources documentation](/developers/docs/resources/channel#start-thread-in-forum-or-media-channel-jsonform-params).
### Forum and Media Channel Formatting
diff --git a/discord/developers/docs/topics/threads.mdx b/discord/developers/docs/topics/threads.mdx
new file mode 100644
index 0000000000..324754b66a
--- /dev/null
+++ b/discord/developers/docs/topics/threads.mdx
@@ -0,0 +1,250 @@
+---
+title: Threads
+description: Learn about Discord threads - temporary sub-channels for organizing conversations.
+---
+
+[Threads](/developers/docs/resources/channel#channel-object) can be thought of as temporary sub-channels inside an existing channel, to help better organize conversation in a busy channel.
+
+Threads have been designed to be very similar to [channel](/developers/docs/resources/channel#channel-object) objects, and this topic aggregates all of the information about threads, which should all help to make migrating very straightforward.
+
+## Backwards Compatibility
+
+Threads are only available in API v9 and above. Bots that do not update to API v9 or above will not receive most gateway events for threads, or things that happen in threads (such as [Message Create](/developers/docs/events/gateway-events#message-create)). Bots on API v8 will still receive gateway events for Interactions.
+
+The list of gateway events that may be dropped includes, but is not limited to:
+
+- MESSAGE_CREATE
+- MESSAGE_DELETE
+- MESSAGE_DELETE_BULK
+- MESSAGE_REACTION_ADD
+- MESSAGE_REACTION_REMOVE
+- MESSAGE_REACTION_REMOVE_ALL
+- MESSAGE_REACTION_REMOVE_EMOJI
+- MESSAGE_UPDATE
+- THREAD_CREATE
+- THREAD_UPDATE
+- THREAD_DELETE
+- THREAD_MEMBER_UPDATE
+- THREAD_MEMBERS_UPDATE
+
+## Thread Fields
+
+Threads share and repurpose a number of the existing fields from the [channel object](/developers/docs/resources/channel#channel-object):
+
+- `id`, `guild_id`, `type`, `name`, `last_message_id`, `last_pin_timestamp`, `rate_limit_per_user` are being re-used
+- `owner_id` has been repurposed to store the id of the user that started the thread
+- `parent_id` has been repurposed to store the id of the `GUILD_TEXT` or `GUILD_ANNOUNCEMENT` channel the thread was created in
+
+Additionally, there are a few fields that are only available on threads:
+
+- `member_count` stores an approximate member count, but it stops counting at 50 (this is only used in our UI, so it is not valuable to bots)
+- `message_count` and `total_message_sent` store the number of messages in a thread. The difference is that when a message is deleted, `message_count` is decremented, but `total_message_sent` will not be. (threads created before July 1, 2022 stop counting both values at 50).
+- `thread_metadata` contains a few thread specific fields, `archived`, `archive_timestamp`, `auto_archive_duration`, `locked`. `archive_timestamp` is changed when creating, archiving, or unarchiving a thread, and when changing the `auto_archive_duration` field.
+
+## Public & Private Threads
+
+Public threads are viewable by everyone who can view the parent channel of the thread. Public threads must be created from an existing message, but can be "orphaned" if that message is deleted. The created thread and the message it was started from will share the same id. The [type](/developers/docs/resources/channel#channel-object-channel-types) of thread created matches the [type](/developers/docs/resources/channel#channel-object-channel-types) of the parent channel. `GUILD_TEXT` channels [create](/developers/docs/resources/channel#start-thread-from-message) `PUBLIC_THREAD` and `GUILD_ANNOUNCEMENT` channels [create](/developers/docs/resources/channel#start-thread-from-message) `ANNOUNCEMENT_THREAD`.
+
+Private threads behave similar to Group DMs, but in a Guild. Private threads are always [created](/developers/docs/resources/channel#start-thread-without-message) with the `GUILD_PRIVATE_THREAD` [type](/developers/docs/resources/channel#channel-object-channel-types) and can only be created in `GUILD_TEXT` channels.
+
+## Locked Threads
+Users (including bot users) without the `MANAGE_THREADS` permission are more restricted in locked threads. Users won't be able to create or update messages in locked threads, or update properties like its title or tags. Additionally, some user activity like deleting messages and adding or removing reactions will *only* be allowed in locked threads if that thread is also active (or un-archived).
+
+If a user or bot user has the `MANAGE_THREADS` permission, they will still be able to make changes to the thread and messages.
+
+## Active & Archived Threads
+
+Every thread can be either active or archived. Changing a thread from archived -> active is referred to as unarchiving the thread. Threads that have `locked` set to true can only be unarchived by a user with the `MANAGE_THREADS` permission.
+
+Besides helping to de-clutter the UI for users, archiving exists to limit the working set of threads that need to be kept around. Since the number of archived threads can be quite large, keeping all of them in memory may be quite prohibitive. Therefore guilds are capped at a certain number of active threads, and only active threads can be manipulated. Users cannot edit messages, add reactions, use application commands, or join archived threads. The only operation that should happen within an archived thread is messages being deleted. Sending a message will automatically unarchive the thread, unless the thread has been locked by a moderator.
+
+Because of this constraint, the gateway protocol is designed to ensure that bots are able to have an accurate view of the full set of active threads, but archived threads are not synced up-front via the gateway.
+
+Threads do not count against the max-channels limit in a guild, but there is a limit on the maximum number of active threads in a guild.
+
+Threads automatically archive after a period of inactivity. As a server approaches the max thread limit this timer will automatically lower, usually not below the `auto_archive_duration`. In very busy channels, threads set to a 7 day auto archive may archive earlier to help avoid the server becoming "full"). "Activity" is defined as sending a message, unarchiving a thread, or changing the auto-archive time. The `auto_archive_duration` field previously controlled how long a thread could stay active, but is now repurposed to control how long the thread stays in the channel list. Channels can also set `default_auto_archive_duration`, which is used by our clients to pre-select a different `auto_archive_duration` value when a user creates a thread.
+
+## Permissions
+
+Threads generally inherit permissions from the parent channel (e.g. if you can add reactions in the parent channel, you can do that in a thread as well).
+
+Three permission bits are specific to threads: `CREATE_PUBLIC_THREADS`, `CREATE_PRIVATE_THREADS`, and `SEND_MESSAGES_IN_THREADS`.
+
+
+The `SEND_MESSAGES` permission has no effect in threads; users must have `SEND_MESSAGES_IN_THREADS` to talk in a thread.
+
+
+Private threads are similar to Group DMs, but in a guild: You must be invited to the thread to be able to view or participate in it, or be a moderator (`MANAGE_THREADS` permission).
+
+Finally, threads are treated slightly differently from channels in the gateway protocol. Clients will not be informed of a thread through the gateway if they do not have permission to view that thread.
+
+## Gateway Events
+
+- [Guild Create](/developers/docs/events/gateway-events#guild-create) contains a field, `threads`, which is an array of channel objects. This represents all active threads in the guild that the current user is able to view.
+- When a thread is created, updated, or deleted, a [Thread Create](/developers/docs/events/gateway-events#thread-create), [Thread Update](/developers/docs/events/gateway-events#thread-update), or [Thread Delete](/developers/docs/events/gateway-events#thread-delete) event is sent. Like their channel counterparts, these just contain a thread.
+- Since the gateway only syncs active threads that the user can see, if a user _gains_ access to a channel, then the gateway may need to sync the active threads in that channel to the user. It will send a [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) event for this.
+
+## Thread Membership
+
+Each thread tracks explicit membership. There are two primary use cases for this data:
+
+- Clients use _their own_ [thread member](/developers/docs/resources/channel#thread-member-object) to calculate read states and notification settings. This is largely irrelevant for bots though, but is the reason for some of the syncing complexity detailed here.
+- Knowing everyone that is in a thread.
+
+Membership is tracked in an array of [thread member](/developers/docs/resources/channel#thread-member-object) objects. These have four fields, `id` (the thread id), `user_id`, `join_timestamp`, and `flags`. Currently the only `flags` are for notification settings, but others may be added in future updates.
+
+### Syncing for the current user
+
+- A [Thread Members Update](/developers/docs/events/gateway-events#thread-members-update) Gateway Event is always sent when the current user is added to or removed from a thread.
+- A [Thread Member Update](/developers/docs/events/gateway-events#thread-member-update) Gateway Event is sent whenever the current user's [thread member](/developers/docs/resources/channel#thread-member-object) object is updated.
+- Certain API calls, such as listing archived threads and search will return an array of [thread member](/developers/docs/resources/channel#thread-member-object) objects for any returned threads the current user is a member of. Other API calls, such as getting a channel will return the [thread member](/developers/docs/resources/channel#thread-member-object) object for the current user as a property on the channel, if the current user is a member of the thread.
+- The [Guild Create](/developers/docs/events/gateway-events#guild-create) Gateway Event will contain a [thread member](/developers/docs/resources/channel#thread-member-object) object as a property on any returned threads the current is a member of.
+- The [Thread Create](/developers/docs/events/gateway-events#thread-create) Gateway Event will contain a [thread member](/developers/docs/resources/channel#thread-member-object) object as a property of the thread if the current user is a member of, and the user has recently gained access to view the parent channel.
+- The [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) Gateway Event will contain an array of [thread member](/developers/docs/resources/channel#thread-member-object) objects for any returned threads the current user is a member of.
+
+### Syncing for other users
+
+
+These require the `GUILD_MEMBERS` [Gateway Intent](/developers/docs/events/gateway#gateway-intents)
+
+
+- An API `GET` call to [`/channels//thread-members`](/developers/docs/resources/channel#list-thread-members) which returns an array of [thread member](/developers/docs/resources/channel#thread-member-object) objects.
+- The [Thread Members Update](/developers/docs/events/gateway-events#thread-members-update) Gateway Event which will include all users who were added to or removed from a thread by an action.
+
+## Editing & Deleting Threads
+
+Threads can be edited and deleted with the existing `PATCH` and `DELETE` endpoints to edit a channel.
+
+- Deleting a thread requires the `MANAGE_THREADS` permission.
+- Editing a thread to set `archived` to `false` only requires the current user has already been added to the thread. If `locked` is true, then the user must have created the thread or have `MANAGE_THREADS`
+- Editing a thread to change the `name`, `archived`, `auto_archive_duration` fields requires `MANAGE_THREADS` or that the current user is the thread creator
+- Editing a thread to change `rate_limit_per_user` or `locked` requires `MANAGE_THREADS`
+
+## NSFW Threads
+
+Threads do not explicitly set the `nsfw` field. All threads in a channel marked as `nsfw` inherit that setting though.
+
+## New Message Types
+
+Threads introduce a few [message types](/developers/docs/resources/message#message-object-message-types), and repurpose some others:
+
+- `RECIPIENT_ADD` and `RECIPIENT_REMOVE` have been repurposed to also send when a user is added to or removed from a thread by someone else
+- `CHANNEL_NAME_CHANGE` has been repurposed and is sent when the thread's name is changed
+- `THREAD_CREATED` is a new message sent to the parent `GUILD_TEXT` channel, used to inform users that a thread has been created. It is currently only sent in one case: when a `PUBLIC_THREAD` is created from an older message (older is still TBD, but is currently set to a very small value). The message contains a [message reference](/developers/docs/resources/message#message-reference-structure) with the `guild_id` and `channel_id` of the thread. The `content` of the message is the `name` of the thread.
+- `THREAD_STARTER_MESSAGE` is a new message sent as the first message in threads that are started from an existing message in the parent channel. It _only_ contains a [message reference](/developers/docs/resources/message#message-reference-structure) field that points to the message from which the thread was started.
+
+## Enumerating threads
+
+There are four `GET` routes for enumerating threads in a specific channel:
+
+- [`/guilds//threads/active`](/developers/docs/resources/guild#list-active-guild-threads) returns all active threads in a guild that the current user can access, includes public & private threads
+- [`/channels//users/@me/threads/archived/private`](/developers/docs/resources/channel#list-joined-private-archived-threads) returns all archived, private threads in a channel, that the current user has is a member of, sorted by thread id descending
+- [`/channels//threads/archived/public`](/developers/docs/resources/channel#list-public-archived-threads) returns all archived, public threads in a channel, sorted by archive timestamp descending
+- [`/channels//threads/archived/private`](/developers/docs/resources/channel#list-private-archived-threads) returns all archived, private threads in a channel, sorted by archive timestamp descending
+
+## Webhooks
+
+Webhooks can send messages to threads by using the `thread_id` query parameter. See the [execute webhook](/developers/docs/resources/webhook#execute-webhook) docs for more details.
+
+## Details about Thread Access and Syncing
+
+While the syncing of threads is similar to channels, there are two important differences that are relevant for [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) and [Thread Create](/developers/docs/events/gateway-events#thread-create) events:
+
+1. The [Gateway](/developers/docs/events/gateway) will only sync threads that the app has permission to view
+2. The Gateway will only sync threads once the app has "subscribed" to the guild. For context, in Discord's official clients, a subscription happens when the user visits a channel in the guild.
+
+These differences mean there is some unique behavior that is worth going into.
+
+### Thread Access
+
+#### Gaining Access to Private Threads
+
+When an app is added to a private thread, it likely doesn't have that thread in memory yet since it doesn't have permission to view it.
+
+Private threads are only synced to you if you are a member or a moderator. Whenever a user is added to a private thread, the Gateway also sends a [Thread Create](/developers/docs/events/gateway-events#thread-create) event. This ensures the client always has a non-null value for that thread.
+
+
+The `THREAD_CREATE` event is also sent when the user is a moderator (and thus would already have the channel in memory).
+
+
+#### Gaining Access to Public Threads
+
+Upon connecting to the Gateway, apps will be automatically subscribed to thread events and active threads.
+
+However, when a non-app is added to a public thread but hasn't subscribed to threads, it may not have that thread in memory yet (which is a requirement for Discord's clients). Because of this, the Gateway will send a [Thread Create](/developers/docs/events/gateway-events#thread-create) event when a user is added to _any_ thread, even if the event is not necessary for apps.
+
+### Channel Access
+
+#### Gaining Access to Channels
+
+When an app gains access to a channel (for example, they're given the moderator role), they likely won't have the threads in memory for that channel since the Gateway only syncs threads that the client has permission to view. To account for this, a [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) event is sent.
+
+The [Thread List Sync](/developers/docs/events/gateway-events#thread-list-sync) event contains a `channel_ids` array, which is the IDs of all channels whose threads are being synced. This field can be used to first clear out any active threads whose `parent_id` is in the `channel_ids` array, and then ingest any threads that were in the event.
+
+#### Losing Access to Channels
+
+When an app loses access to a channel, the Gateway does **not** send it [Thread Delete](/developers/docs/events/gateway-events#thread-delete) event (or any equivalent thread-specific event). Instead, the app will receive the event that caused its permissions on the channel to change.
+
+If an app wanted to track when it lost access to any thread, it's possible but difficult as it would need to handle all cases correctly. Usually, events that cause permission changes are a [Guild Role Update](/developers/docs/events/gateway-events#guild-role-update), [Guild Member Update](/developers/docs/events/gateway-events#guild-member-update) or [Channel Update](/developers/docs/events/gateway-events#channel-update) event.
+
+
+Discord's clients check their permissions *first* when performing an action. That way, even if it has some stale data, it does not end up acting on it.
+
+
+Additionally, when a user or app loses access to a channel, they are not removed from the thread and will continue to be reported as a member of that thread. However, they will **not** receive any new Gateway events unless they are removed from the thread, in which case they will receive a [Thread Members Update](/developers/docs/events/gateway-events#thread-members-update) event.
+
+### Unarchiving a Thread
+
+When a thread is unarchived, there is no guarantee that an app has the thread or its member status in memory. To account for this, the Gateway will send two events (in the listed order):
+
+1. A [Thread Update](/developers/docs/events/gateway-events#thread-update) event, which contains the full channel object.
+2. A [Thread Member Update](/developers/docs/events/gateway-events#thread-member-update) event, which is sent to all members of the unarchived thread. Discord's clients only load active threads into memory on start, so this event is sent even if it may not be relevant to most apps.
+
+## Forums
+
+A `GUILD_FORUM` (type `15`) channel is similar to a `GUILD_TEXT` channel, except *only* threads can be created in them. Unless otherwise noted, threads in forum channels behave in the same way as in text channels—meaning they use the same endpoints and receive the same Gateway events.
+
+Messages cannot be sent directly in forum channels.
+
+
+More information about forum channels and how they appear in Discord can be found in the [Forum Channels FAQ](https://support.discord.com/hc/en-us/articles/6208479917079-Forum-Channels-FAQ#h_01G69FJQWTWN88HFEHK7Z6X79N)
+
+
+## Media Channels
+
+A `GUILD_MEDIA` (type `16`) channel is similar to a `GUILD_FORUM` channel in that only threads can be created in them. Unless otherwise noted, threads in media channels behave in the same way as in forum channels - meaning they use the same endpoints and receive the same Gateway events. More information about media channels and how they appear in Discord can be found in the [media channels Help Center Article](https://creator-support.discord.com/hc/en-us/articles/14346342766743).
+
+
+`GUILD_MEDIA` channels are in beta and still being actively developed. The API and other technical details are subject to change.
+
+
+
+### Creating Threads in Forum and Media Channels
+
+Within thread-only channels, threads appear as posts. Threads can be created using the [`POST /channels//threads`](/developers/docs/resources/channel#start-thread-in-forum-or-media-channel) endpoint with [slightly different parameters](/developers/docs/resources/channel#start-thread-in-forum-or-media-channel-jsonform-params) than threads in text channels. For example, when creating threads in a threads-only channel, a message is created that has the same ID as the thread which requires you to pass parameters for both a thread *and* a message.
+
+Threads in thread-only channels have the same permissions behavior as threads in a text channel, inheriting all permissions from the parent channel, with one exception: creating a thread in a thread-only channel only requires the `SEND_MESSAGES` permission.
+
+### Forum and Media Channel Fields
+
+It's worth calling out a few details about fields specific to thread-only channels that may be important to keep in mind:
+
+- The `last_message_id` field is the ID of the most recently created thread in that channel. As with messages, your app will not receive a `CHANNEL_UPDATE` event when the field is changed. Instead clients should update the value when receiving [Thread Create](/developers/docs/events/gateway-events#thread-create) events.
+- The `topic` field is what is shown in the "Guidelines" section within the Discord client.
+- The `rate_limit_per_user` field limits how frequently threads can be created. There is a new `default_thread_rate_limit_per_user` field on thread-only channels as well, which limits how often messages can be sent _in a thread_. This field is copied into `rate_limit_per_user` on the thread at creation time.
+- The `available_tags` field can be set when creating or updating a channel, which determines which tags can be set on individual threads within the thread's `applied_tags` field.
+- The `flags` field indicates any [channel flags](/developers/docs/resources/channel#channel-object-channel-flags) set for a thread-only channel. Currently only `REQUIRE_TAG` can be used, which requires that a tag from `available_tags` be specified when creating a thread in that channel.
+
+All fields for channels, including thread-only channels, can be found in the [Channel Object](/developers/docs/resources/channel#channel-object).
+
+### Forum and Media Channel Thread Fields
+
+A thread can be pinned within a thread-only, which will be represented as the [`PINNED` flag](/developers/docs/resources/channel#channel-object-channel-flags) in the `flags` field within a thread-only channel. A thread that is pinned will have the `(1 << 1)` flag set, and archiving that thread will unset the flag. A pinned thread will *not* auto-archive.
+
+The `message_count` and `total_message_sent` fields on threads in thread-only channels will increment on `MESSAGE_CREATE` events, and decrement on `MESSAGE_DELETE` and `MESSAGE_DELETE_BULK` events. There will be no specific `CHANNEL_UPDATE` event that notifies your app of changes to those fields—instead, apps should update those values when receiving corresponding events.
+
+All fields for threads in thread-only channels can be found in the [channel resources documentation](/developers/docs/resources/channel#start-thread-in-forum-or-media-channel-jsonform-params).
+
+### Forum and Media Channel Formatting
+
+In thread-only channels, the first message in a thread and the channel topic can both contain markdown for bulleted lists and headings (unlike text channels).
diff --git a/docs/topics/voice-connections.mdx b/discord/developers/docs/topics/voice-connections.mdx
similarity index 65%
rename from docs/topics/voice-connections.mdx
rename to discord/developers/docs/topics/voice-connections.mdx
index 834a8df2f4..e96655046c 100644
--- a/docs/topics/voice-connections.mdx
+++ b/discord/developers/docs/topics/voice-connections.mdx
@@ -1,17 +1,23 @@
-# Voice
+---
+title: Voice
+description: Technical guide to implementing voice connections with Discord.
+---
-Voice connections operate in a similar fashion to the [Gateway](/docs/events/gateway) connection. However, they use a different set of payloads and a separate UDP-based connection for voice data transmission. Because UDP is used for both receiving and transmitting voice data, your client _must_ be able to receive UDP packets, even through a firewall or NAT (see [UDP Hole Punching](https://en.wikipedia.org/wiki/UDP_hole_punching) for more information). The Discord Voice servers implement functionality (see [IP Discovery](/docs/topics/voice-connections#ip-discovery)) for discovering the local machines remote UDP IP/Port, which can assist in some network configurations.
+import {ManualAnchor} from '/snippets/manualanchor.jsx'
+
+Voice connections operate in a similar fashion to the [Gateway](/developers/docs/events/gateway) connection. However, they use a different set of payloads and a separate UDP-based connection for voice data transmission. Because UDP is used for both receiving and transmitting voice data, your client _must_ be able to receive UDP packets, even through a firewall or NAT (see [UDP Hole Punching](https://en.wikipedia.org/wiki/UDP_hole_punching) for more information). The Discord Voice servers implement functionality (see [IP Discovery](/developers/docs/topics/voice-connections#ip-discovery)) for discovering the local machines remote UDP IP/Port, which can assist in some network configurations.
## Voice Gateway Versioning
-To ensure that you have the most up-to-date information, please use [version 8](/docs/topics/voice-connections#voice-gateway-versioning-gateway-versions). Otherwise, we cannot guarantee that the [Opcodes](/docs/topics/opcodes-and-status-codes#voice) documented here will reflect what you receive over the socket.
+To ensure that you have the most up-to-date information, please use [version 8](/developers/docs/topics/voice-connections#voice-gateway-versioning-gateway-versions). Otherwise, we cannot guarantee that the [Opcodes](/developers/docs/topics/opcodes-and-status-codes#voice) documented here will reflect what you receive over the socket.
Previously if the version query string `v` was omitted the voice gateway would default to version 1. That behavior is being deprecated, in the future you must present a voice gateway version or your voice connection will be rejected.
-:::warn
+
Versions below 4 as well as the default version behavior will be discontinued as of November 18th, 2024. Connections without a version or with a version less than version 4 will be rejected as of this date.
-:::
+
+
Bot users respect the voice channel's user limit, if set. When the voice channel is full, you will not receive the Voice State Update or Voice Server Update events in response to your own Voice State Update. Having `MANAGE_CHANNELS` permission bypasses this limit and allows you to join regardless of the channel being full or not.
-:::
+
## Establishing a Voice Websocket Connection
-Once we retrieve a session_id, token, and endpoint information, we can connect and handshake with the voice server over another secure WebSocket. Unlike the gateway endpoint we receive in an HTTP [Get Gateway](/docs/events/gateway#get-gateway) request, the endpoint received from our [Voice Server Update](/docs/events/gateway-events#voice-server-update) payload does not contain a URL protocol, so some libraries may require manually prepending it with "wss://" before connecting. Once connected to the voice WebSocket endpoint, we can send an [Opcode 0 Identify](/docs/topics/opcodes-and-status-codes#voice) payload with our server_id, user_id, session_id, and token:
+Once we retrieve a session_id, token, and endpoint information, we can connect and handshake with the voice server over another secure WebSocket. Unlike the gateway endpoint we receive in an HTTP [Get Gateway](/developers/docs/events/gateway#get-gateway) request, the endpoint received from our [Voice Server Update](/developers/docs/events/gateway-events#voice-server-update) payload does not contain a URL protocol, so some libraries may require manually prepending it with "wss://" before connecting. Once connected to the voice WebSocket endpoint, we can send an [Opcode 0 Identify](/developers/docs/topics/opcodes-and-status-codes#voice) payload with our server_id, user_id, session_id, and token:
+
`heartbeat_interval` here is an erroneous field and should be ignored. The correct `heartbeat_interval` value comes from the Hello payload.
-:::
+
## Heartbeating
-In order to maintain your WebSocket connection, you need to continuously send heartbeats at the interval determined in [Opcode 8 Hello](/docs/topics/opcodes-and-status-codes#voice):
+In order to maintain your WebSocket connection, you need to continuously send heartbeats at the interval determined in [Opcode 8 Hello](/developers/docs/topics/opcodes-and-status-codes#voice):
+
To support our long-term privacy goals, we will **only support E2EE calls starting on March 1st, 2026** for all audio
and video conversations in direct messages (DMs), group messages (GDMs), voice channels, and Go Live streams on
Discord.
We highly recommend you implement DAVE support as soon as possible to ensure a smooth transition.
-:::
+
This section is a high-level overview of how to support Discord's audio & video end-to-end encryption (DAVE) protocol, centered around the voice gateway opcodes necessary for the protocol. The most thorough documentation on the DAVE protocol is found in the [Protocol Whitepaper](https://daveprotocol.com). You may additionally be able to leverage or refer to our open-source library [libdave](https://github.com/discord/libdave) to assist your implementation. The exact format of the DAVE protocol opcodes is detailed in the [Voice Gateway Opcodes section of the protocol whitepaper](https://daveprotocol.com/#voice-gateway-opcodes).
@@ -224,7 +241,7 @@ When a call is E2EE, all members of the call exchange keys via a [Messaging Laye
### Binary Websocket Messages
-To reduce overhead, some of the new DAVE protocol opcodes are sent as binary instead of JSON text. See the binary column in the [Voice Opcodes Table](/docs/topics/opcodes-and-status-codes#voice) to identify these opcodes. Binary websocket messages have the following format:
+To reduce overhead, some of the new DAVE protocol opcodes are sent as binary instead of JSON text. See the binary column in the [Voice Opcodes Table](/developers/docs/topics/opcodes-and-status-codes#voice) to identify these opcodes. Binary websocket messages have the following format:
| Field | Description | Size |
|-----------------|--------------------------------------------------------------------|----------------|
@@ -232,35 +249,35 @@ To reduce overhead, some of the new DAVE protocol opcodes are sent as binary ins
| Opcode | Unsigned integer opcode value | 1 bytes |
| Payload | Binary message payload (format defined by opcode) | Variable bytes |
-Sequence numbers are only sent from the server to the client, and all server-sent binary opcodes require the sequence number. See [Resuming Voice Connection](/docs/topics/voice-connections#resuming-voice-connection) for further details on how sequence numbers are used when present.
+Sequence numbers are only sent from the server to the client, and all server-sent binary opcodes require the sequence number. See [Resuming Voice Connection](/developers/docs/topics/voice-connections#resuming-voice-connection) for further details on how sequence numbers are used when present.
### Indicating DAVE Protocol Support
-Include the highest DAVE protocol version you support in [Opcode 0 Identify](/docs/topics/opcodes-and-status-codes#voice) as `max_dave_protocol_version`. Sending version 0, or omitting the `max_dave_protocol_version` field, indicates no DAVE protocol support.
+Include the highest DAVE protocol version you support in [Opcode 0 Identify](/developers/docs/topics/opcodes-and-status-codes#voice) as `max_dave_protocol_version`. Sending version 0, or omitting the `max_dave_protocol_version` field, indicates no DAVE protocol support.
-The voice gateway specifies the initial protocol version in [Opcode 4 Session Description](/docs/topics/opcodes-and-status-codes#voice) under `dave_protocol_version`. This may be any non-discontinued protocol version equal to or less than your supported protocol version.
+The voice gateway specifies the initial protocol version in [Opcode 4 Session Description](/developers/docs/topics/opcodes-and-status-codes#voice) under `dave_protocol_version`. This may be any non-discontinued protocol version equal to or less than your supported protocol version.
-:::warn
+
Clients must retain backwards-compatibility of any non-discontinued DAVE protocol versions. The voice gateway selects the lowest shared protocol version for the call.
-:::
+
### Protocol Transitions
The voice gateway negotiates protocol version and MLS group transitions, to ensure the continuity of media being sent for the call. This can occur when the call is upgrading/downgrading to/from E2EE (in the initial transition phase), changing protocol versions, or when the MLS group is changing.
-Some opcodes include a transition ID. After preparing local state necessary to perform the transition, send [Opcode 23 DAVE Protocol Transition Ready](/docs/topics/opcodes-and-status-codes#voice) to indicate to the voice gateway that you are ready to execute the transition. When all participants are ready or when a timeout has been reached, the voice gateway dispatches [Opcode 22 DAVE Protocol Execute Transition](/docs/topics/opcodes-and-status-codes#voice) to confirm execution of the transition. The transition execution is what indicates to media senders that they can begin sending media with the new protocol context (e.g. without E2EE after a downgrade, with a new protocol version after a protocol version change, or using a new key ratchet after a group participant change).
+Some opcodes include a transition ID. After preparing local state necessary to perform the transition, send [Opcode 23 DAVE Protocol Transition Ready](/developers/docs/topics/opcodes-and-status-codes#voice) to indicate to the voice gateway that you are ready to execute the transition. When all participants are ready or when a timeout has been reached, the voice gateway dispatches [Opcode 22 DAVE Protocol Execute Transition](/developers/docs/topics/opcodes-and-status-codes#voice) to confirm execution of the transition. The transition execution is what indicates to media senders that they can begin sending media with the new protocol context (e.g. without E2EE after a downgrade, with a new protocol version after a protocol version change, or using a new key ratchet after a group participant change).
#### Downgrade
-Downgrades to protocol version 0 are announced via [Opcode 21 DAVE Protocol Prepare Transition](/docs/topics/opcodes-and-status-codes#voice). This can occur during the transition phase when a client that does not support the protocol joins the call. When this transition is executed, senders should stop sending media using the protocol format.
+Downgrades to protocol version 0 are announced via [Opcode 21 DAVE Protocol Prepare Transition](/developers/docs/topics/opcodes-and-status-codes#voice). This can occur during the transition phase when a client that does not support the protocol joins the call. When this transition is executed, senders should stop sending media using the protocol format.
#### Protocol Version Change & Upgrade
-Protocol version transitions (including upgrades from protocol version 0) are announced via [Opcode 24 DAVE Protocol Prepare Epoch](/docs/topics/opcodes-and-status-codes#voice). In addition to the `transition_id`, this opcode includes the `epoch_id` for the upcoming MLS epoch.
+Protocol version transitions (including upgrades from protocol version 0) are announced via [Opcode 24 DAVE Protocol Prepare Epoch](/developers/docs/topics/opcodes-and-status-codes#voice). In addition to the `transition_id`, this opcode includes the `epoch_id` for the upcoming MLS epoch.
-Receiving [Opcode 24 DAVE Protocol Prepare Epoch](/docs/topics/opcodes-and-status-codes#voice) with `epoch_id = 1` indicates that a new MLS group is being created. Participants must:
+Receiving [Opcode 24 DAVE Protocol Prepare Epoch](/developers/docs/topics/opcodes-and-status-codes#voice) with `epoch_id = 1` indicates that a new MLS group is being created. Participants must:
- prepare a local MLS group with the parameters appropriate for the DAVE protocol version
-- generate and send [Opcode 26 DAVE MLS Key Package](/docs/topics/opcodes-and-status-codes#voice) to deliver a new MLS key package to the voice gateway
+- generate and send [Opcode 26 DAVE MLS Key Package](/developers/docs/topics/opcodes-and-status-codes#voice) to deliver a new MLS key package to the voice gateway
When the `epoch_id` is greater than 1, the protocol version of the existing MLS group is changing.
@@ -268,11 +285,11 @@ When the transition is executed, senders must start sending media using the new
#### MLS Group Changes
-When the participants of the MLS group must change, existing participants receive an [Opcode 29 DAVE MLS Announce Commit Transition](/docs/topics/opcodes-and-status-codes#voice) whereas new members being added to the group receive [Opcode 30 DAVE MLS Welcome](/docs/topics/opcodes-and-status-codes#voice). Both opcodes include the transition ID and binary MLS Commit or MLS Welcome message.
+When the participants of the MLS group must change, existing participants receive an [Opcode 29 DAVE MLS Announce Commit Transition](/developers/docs/topics/opcodes-and-status-codes#voice) whereas new members being added to the group receive [Opcode 30 DAVE MLS Welcome](/developers/docs/topics/opcodes-and-status-codes#voice). Both opcodes include the transition ID and binary MLS Commit or MLS Welcome message.
-To prepare for the protocol transition, existing group members must apply the commit to progress their local MLS group to the correct next state. [Opcode 23 DAVE Protocol Transition Ready](/docs/topics/opcodes-and-status-codes#voice) is sent when the MLS commit has been processed.
+To prepare for the protocol transition, existing group members must apply the commit to progress their local MLS group to the correct next state. [Opcode 23 DAVE Protocol Transition Ready](/developers/docs/topics/opcodes-and-status-codes#voice) is sent when the MLS commit has been processed.
-Welcomed members send [Opcode 23 DAVE Protocol Transition Ready](/docs/topics/opcodes-and-status-codes#voice) after succesfully joining the group received in the MLS Welcome message.
+Welcomed members send [Opcode 23 DAVE Protocol Transition Ready](/developers/docs/topics/opcodes-and-status-codes#voice) after successfully joining the group received in the MLS Welcome message.
### External Sender
@@ -280,17 +297,17 @@ The voice gateway must be an external sender of the MLS group, so that it can se
DAVE protocol participants only process proposals which arrive from the external sender, and not from any other group members. The external sender only sends Add or Remove proposals.
-The voice gateway uses [Opcode 25 DAVE MLS External Sender Package](/docs/topics/opcodes-and-status-codes#voice) to provide the external sender public key and credential to MLS group participants. This message may be sent immediately on voice gateway connection or at a later time when the call is upgrading to use the DAVE protocol.
+The voice gateway uses [Opcode 25 DAVE MLS External Sender Package](/developers/docs/topics/opcodes-and-status-codes#voice) to provide the external sender public key and credential to MLS group participants. This message may be sent immediately on voice gateway connection or at a later time when the call is upgrading to use the DAVE protocol.
Group creators must include the external sender they receive from the voice gateway in their MLS group extensions when creating the group. Welcomed group members ensure that the expected external sender extension is present in the group they are about to join.
### Joining the MLS Group
-Except for the initial creation of the first group for the call, joining the MLS group always occurs after receiving [Opcode 30 DAVE MLS Welcome](/docs/topics/opcodes-and-status-codes#voice).
+Except for the initial creation of the first group for the call, joining the MLS group always occurs after receiving [Opcode 30 DAVE MLS Welcome](/developers/docs/topics/opcodes-and-status-codes#voice).
#### Key Packages
-To be proposed to be added to the MLS group, pending members must send an MLS key package via [Opcode 26 DAVE MLS Key Package](/docs/topics/opcodes-and-status-codes#voice). Key packages are only used one time, and a new key package must be generated each time pending member is waiting to be added or re-added to the group.
+To be proposed to be added to the MLS group, pending members must send an MLS key package via [Opcode 26 DAVE MLS Key Package](/developers/docs/topics/opcodes-and-status-codes#voice). Key packages are only used one time, and a new key package must be generated each time pending member is waiting to be added or re-added to the group.
##### Identity Public Key
@@ -300,27 +317,27 @@ You can choose to generate a new ephemeral keypair for every protocol call or us
#### Initial Group
-When there is not yet an MLS group (e.g. a transport-only encrypted call is upgrading or two members have just joined a new call) all pending group members create a local group using the MLS parameters defined by the DAVE protocol version and including the voice gateway external sender received via [Opcode 25 DAVE MLS External Sender Package](/docs/topics/opcodes-and-status-codes#voice). Every pending member of the group has the chance to produce the initial commit that creates the MLS group with `epoch = 1`.
+When there is not yet an MLS group (e.g. a transport-only encrypted call is upgrading or two members have just joined a new call) all pending group members create a local group using the MLS parameters defined by the DAVE protocol version and including the voice gateway external sender received via [Opcode 25 DAVE MLS External Sender Package](/developers/docs/topics/opcodes-and-status-codes#voice). Every pending member of the group has the chance to produce the initial commit that creates the MLS group with `epoch = 1`.
Pending group members receive add proposals for every other pending group member from the voice gateway. If an additional pending member joins while there is not yet an MLS group, they receive all in-flight proposal messages.
-Proposal and commit handling follows the same process whether or not there is an established group. See [Proposals and Commits](/docs/topics/voice-connections#proposals-and-commits)
+Proposal and commit handling follows the same process whether or not there is an established group. See [Proposals and Commits](/developers/docs/topics/voice-connections#proposals-and-commits)
#### Welcome
-Pending group members receive a welcome message from another group member which adds them to the MLS group. This is dispatched from the voice gateway via [Opcode 30 DAVE MLS Welcome](/docs/topics/opcodes-and-status-codes#voice).
+Pending group members receive a welcome message from another group member which adds them to the MLS group. This is dispatched from the voice gateway via [Opcode 30 DAVE MLS Welcome](/developers/docs/topics/opcodes-and-status-codes#voice).
#### Invalid Group
-If the group received in an [Opcode 30 DAVE MLS Welcome](/docs/topics/opcodes-and-status-codes#voice) or [Opcode 29 DAVE MLS Announce Commit Transition](/docs/topics/opcodes-and-status-codes#voice) is unprocessable, the member receiving the unprocessable message sends [Opcode 31 DAVE MLS Invalid Commit Welcome](/docs/topics/opcodes-and-status-codes#voice) to the voice gateway. Additionally, the local group state is reset and a new key package is generated and sent to the voice gateway via [Opcode 26 DAVE MLS Key Package](/docs/topics/opcodes-and-status-codes#voice).
+If the group received in an [Opcode 30 DAVE MLS Welcome](/developers/docs/topics/opcodes-and-status-codes#voice) or [Opcode 29 DAVE MLS Announce Commit Transition](/developers/docs/topics/opcodes-and-status-codes#voice) is unprocessable, the member receiving the unprocessable message sends [Opcode 31 DAVE MLS Invalid Commit Welcome](/developers/docs/topics/opcodes-and-status-codes#voice) to the voice gateway. Additionally, the local group state is reset and a new key package is generated and sent to the voice gateway via [Opcode 26 DAVE MLS Key Package](/developers/docs/topics/opcodes-and-status-codes#voice).
This causes the voice gateway to propose the removal and re-addition of the requesting member.
### Proposals and Commits
-The voice gateway dispatches proposals which must be appended or revoked via [Opcode 27 DAVE MLS Proposals](/docs/topics/opcodes-and-status-codes#voice). All members of the established or pending MLS group must append or revoke the proposals they receive, and then produce an MLS commit message and optionally an MLS welcome message (when committing add proposals which add new members) which they send to the voice gateway via [Opcode 28 DAVE MLS Commit Welcome](/docs/topics/opcodes-and-status-codes#voice).
+The voice gateway dispatches proposals which must be appended or revoked via [Opcode 27 DAVE MLS Proposals](/developers/docs/topics/opcodes-and-status-codes#voice). All members of the established or pending MLS group must append or revoke the proposals they receive, and then produce an MLS commit message and optionally an MLS welcome message (when committing add proposals which add new members) which they send to the voice gateway via [Opcode 28 DAVE MLS Commit Welcome](/developers/docs/topics/opcodes-and-status-codes#voice).
-In each epoch, the voice gateway dispatches the "winning" commit via [Opcode 29 DAVE MLS Announce Commit Transition](/docs/topics/opcodes-and-status-codes#voice) and optionally the associated welcome messages via [Opcode 30 DAVE MLS Welcome](/docs/topics/opcodes-and-status-codes#voice). The voice gateway broadcasts the first valid commit and welcome(s) it sees in the given epoch, and drops any commits later received for the out-of-date epoch. All dispatched unrevoked proposals in the epoch must be included in the commit for it to be valid. All members added in the epoch must be welcomed for the welcome to be valid.
+In each epoch, the voice gateway dispatches the "winning" commit via [Opcode 29 DAVE MLS Announce Commit Transition](/developers/docs/topics/opcodes-and-status-codes#voice) and optionally the associated welcome messages via [Opcode 30 DAVE MLS Welcome](/developers/docs/topics/opcodes-and-status-codes#voice). The voice gateway broadcasts the first valid commit and welcome(s) it sees in the given epoch, and drops any commits later received for the out-of-date epoch. All dispatched unrevoked proposals in the epoch must be included in the commit for it to be valid. All members added in the epoch must be welcomed for the welcome to be valid.
### Audio Frame E2EE
@@ -388,7 +405,7 @@ OPUS frames are fully encrypted and no additional data is passed to the AEAD.
Transport encryption between the client and the selective forwarding unit (SFU) is still used even in E2EE calls.
-Voice data sent to discord should be encoded with [Opus](https://www.opus-codec.org/), using two channels (stereo) and a sample rate of 48kHz. Voice Data is sent using a [RTP Header](https://www.rfcreader.com/#rfc3550_line548), followed by encrypted Opus audio data. Voice encryption uses the key passed in [Opcode 4 Session Description](/docs/topics/opcodes-and-status-codes#voice) and the nonce formed with the 12 byte header appended with 12 null bytes to achieve the 24 required by xsalsa20_poly1305. Discord encrypts with the [libsodium](https://download.libsodium.org/doc/) encryption library.
+Voice data sent to discord should be encoded with [Opus](https://www.opus-codec.org/), using two channels (stereo) and a sample rate of 48kHz. Voice Data is sent using a [RTP Header](https://www.rfcreader.com/#rfc3550_line548), followed by encrypted Opus audio data. Voice encryption uses the key passed in [Opcode 4 Session Description](/developers/docs/topics/opcodes-and-status-codes#voice) and the nonce formed with the 12 byte header appended with 12 null bytes to achieve the 24 required by xsalsa20_poly1305. Discord encrypts with the [libsodium](https://download.libsodium.org/doc/) encryption library.
### Transport Encryption Modes
@@ -402,24 +419,25 @@ Voice data sent to discord should be encoded with [Opus](https://www.opus-codec.
| XSalsa20 Poly1305 Suffix | xsalsa20_poly1305_suffix | 24 random bytes | Deprecated |
| XSalsa20 Poly1305 Lite | xsalsa20_poly1305_lite | 32-bit incremental integer value, appended to payload | Deprecated |
-:::warn
+
The deprecated encryption modes above will be discontinued as of November 18th, 2024. As of this date the voice gateway will not allow you to connect with one of the deprecated encryption modes.
-:::
+
-:::warn
+
The nonce has to be stripped from the payload before encrypting and before decrypting the audio data
-:::
+
The RTP size variants determine the unencrypted size of the RTP header in [the same way as SRTP](https://tools.ietf.org/html/rfc3711#section-3.1), which considers CSRCs and (optionally) the extension preamble to be part of the unencrypted header. The deprecated variants use a fixed size unencrypted header for RTP.
-The voice gateway will report what encryption modes are available in [Opcode 2 Ready](/docs/topics/opcodes-and-status-codes#voice).
+The voice gateway will report what encryption modes are available in [Opcode 2 Ready](/developers/docs/topics/opcodes-and-status-codes#voice).
Voice gateway compatible modes will always include `aead_xchacha20_poly1305_rtpsize` but may not include `aead_aes256_gcm_rtpsize` depending on the underlying hardware. You must support `aead_xchacha20_poly1305_rtpsize`. You should prefer to use `aead_aes256_gcm_rtpsize` when it is available.
-Include your selected mode in [Opcode 1 Select Protocol](/docs/topics/opcodes-and-status-codes#voice).
+Include your selected mode in [Opcode 1 Select Protocol](/developers/docs/topics/opcodes-and-status-codes#voice).
-Finally, the voice server will respond with a [Opcode 4 Session Description](/docs/topics/opcodes-and-status-codes#voice) that includes the `mode` and `secret_key`, a 32 byte array used for [transport encryption and sending](/docs/topics/voice-connections#transport-encryption-and-sending-voice) voice data:
+Finally, the voice server will respond with a [Opcode 4 Session Description](/developers/docs/topics/opcodes-and-status-codes#voice) that includes the `mode` and `secret_key`, a 32 byte array used for [transport encryption and sending](/developers/docs/topics/voice-connections#transport-encryption-and-sending-voice) voice data:
+
+You must send at least one [Opcode 5 Speaking](/developers/docs/topics/opcodes-and-status-codes#voice) payload before sending voice data, or you will be disconnected with an invalid SSRC error.
+
-:::info
+
The `delay` property should be set to `0` for bots that use the voice gateway.
-:::
+
### Voice Data Interpolation
@@ -485,8 +505,9 @@ When there's a break in the sent data, the packet transmission shouldn't simply
## Resuming Voice Connection
-When your client detects that its connection has been severed, it should open a new WebSocket connection. Once the new connection has been opened, your client should send an [Opcode 7 Resume](/docs/topics/opcodes-and-status-codes#voice) payload:
+When your client detects that its connection has been severed, it should open a new WebSocket connection. Once the new connection has been opened, your client should send an [Opcode 7 Resume](/developers/docs/topics/opcodes-and-status-codes#voice) payload:
+
+This tutorial was originally written for Glitch, which is no longer available. We're currently updating this tutorial to use a different hosting platform.
+
+
+
All of the sample code used in this tutorial can be found in the [`linked-roles-sample` GitHub repo](https://github.com/discord/linked-roles-sample)
-:::
+
---
## Creating an app
-The first thing we’ll do is create an app through the [developer dashboard](https://discord.com/developers/applications). If you already have an app created, you can jump right to the [Running your app](/docs/tutorials/configuring-app-metadata-for-linked-roles#running-your-app) section.
+The first thing we’ll do is create an app through the [developer dashboard](https://discord.com/developers/applications). If you already have an app created, you can jump right to the [Running your app](/developers/docs/tutorials/configuring-app-metadata-for-linked-roles#running-your-app) section.
-:::info
-Basic steps to create an app are outlined below, but a more detailed walkthrough is in the [Getting Started guide](/docs/quick-start/getting-started).
-:::
+
+Basic steps to create an app are outlined below, but a more detailed walkthrough is in the [Getting Started guide](/developers/docs/quick-start/getting-started).
+
- Navigate to the [developer dashboard](https://discord.com/developers/applications)
- Click **New Application** in the upper right corner, then select a name and create your app
- Click on the **Bot** tab on the left sidebar. On that page, click **Reset Token** and store the token somewhere safe (like in a password manager)
-:::warn
+
+
Bot tokens are used to authorize API requests and carry your bot's permissions, making them highly sensitive. Never share your token or check it into any kind of version control.
-:::
+
+
### Adding scopes
@@ -36,9 +42,9 @@ Apps need approval from installing users to perform actions inside of Discord. S
- Check the `bot` scope
- After the scope is selected, you should see a **Generated URL** which can be used to install your app
-:::info
-See a list of all [OAuth2 scopes](/docs/topics/oauth2#shared-resources-oauth2-scopes), or read more on [user permissions](/docs/topics/permissions) in the documentation.
-:::
+
+See a list of all [OAuth2 scopes](/developers/docs/topics/oauth2#shared-resources-oauth2-scopes), or read more on [user permissions](/developers/docs/topics/permissions) in the documentation.
+
### Installing your app
@@ -54,15 +60,17 @@ All of the code used in the example app can be found in the [GitHub repository](
This guide uses Glitch, which allows you to quickly clone and develop an app from within your browser. There are also instructions on developing locally using ngrok in the README if you'd prefer.
-:::info
+
+
While Glitch is great for development and testing, [it has technical limitations](https://help.glitch.com/kb/article/17-technical-restrictions/) so other hosting providers should be considered for production apps.
-:::
+
+
To start, [remix (or clone) the Glitch project 🎏](https://glitch.com/edit/#!/remix/linked-role-discord-bot)
When you remix the project, you'll see a new Glitch project with a unique name similar to this:
-
+
#### Project structure
@@ -86,29 +94,33 @@ All of the files for the project are on the left-hand side. Here's a quick glimp
There's already some code in your `server.js` file, but you’ll need your app’s token and ID to make requests. All of your credentials can be stored directly in the `.env` file.
-:::warn
+
+
It bears repeating that you should never check any credentials or secrets into source control. The getting started project's `.gitignore` comes pre-loaded with `.env` to prevent it.
-:::
+
+
First, copy your bot user’s token from earlier and paste it in the `DISCORD_TOKEN` variable in your `.env` file.
Next, navigate to your app settings in the developer portal, and navigate to OAuth2 -> General. Copy the Client ID and Client Secret for your application, and paste the values as `DISCORD_CLIENT_ID` and `DISCORD_CLIENT_SECRET` in your `.env`.
-
+
Now, we need to set the Redirect URL that will be used for our OAuth2 flow. Go back to Glitch, and click the `Share` button for your project. Copy the public live URL for your app:
-
+
Go back to the OAuth2 -> General tab in the Discord developer portal, and add a new redirect for your app using the Glitch URL and the `/discord-oauth-callback` route. Copy this URL, then paste it as `DISCORD_REDIRECT_URI` in your `.env`.
Go to the General Information tab in the developer portal, and scroll down to the `Linked Roles Verification Url` field. Paste the base URL to your Glitch app, add the `/linked-role` route, then save.
-:::info
+
+
For the Glitch project used in the screenshots, the verification URL would be `https://adjoining-crawling-yamamomo.glitch.me/linked-role`
-:::
-
+
+
+
Finally, to generate a unique cookie secret, go back to Glitch, and click on the `Terminal` tab. Run the following commands:
@@ -131,7 +143,7 @@ COOKIE_SECRET:
As a one-time step, you must tell Discord which metadata fields you are going to allow admins to use for linked roles associated with your app.
-To configure connection metadata for your app, you'll call the [PUT /users/@me/applications//role-connection](/docs/resources/application-role-connection-metadata#update-application-role-connection-metadata-records) method with [application connection role metadata](/docs/resources/application-role-connection-metadata#application-role-connection-metadata-object). In the sample app, this is handled in [`src/register.js`](https://github.com/discord/linked-roles-sample/blob/main/src/register.js), and can be run via the command line.
+To configure connection metadata for your app, you'll call the [PUT /users/@me/applications/\/role-connection](/developers/docs/resources/application-role-connection-metadata#update-application-role-connection-metadata-records) method with [application connection role metadata](/developers/docs/resources/application-role-connection-metadata#application-role-connection-metadata-object). In the sample app, this is handled in [`src/register.js`](https://github.com/discord/linked-roles-sample/blob/main/src/register.js), and can be run via the command line.
Go back to Glitch, click the **terminal** tab, and run the following command:
@@ -139,7 +151,7 @@ Go back to Glitch, click the **terminal** tab, and run the following command:
$ node src/register.js
```
-
+
## Trying it out
@@ -151,25 +163,27 @@ To try out the app, we'll create a linked role in a server where you have admin
Give the role a name, save it, then click on `Links`. Click the `Add requirement` button, and you should see your bot in the list of available Apps. Click on it, and you will see a setup screen where you can configure specific criteria for your role.
-
+
### Acquiring the role
To acquire your newly created role, click the server name in the upper left corner of the screen, and select `Linked Roles`. Click on your role, and it will present the opportunity to connect your account.
-:::info
+
+
When you connect your account, one of the scopes requested in the OAuth flow is `role_connections.write`, which is required for an app to update a user's role connection information.
-:::
-
+
+
+
Click on the linked role criteria. This should lead to the Discord OAuth2 consent screen. Click `Authorize`, and then return to Discord.
-
+
After returning to Discord, you should see your account granted the linked role.
-
+
Finally, create a new private channel, and add the new linked role.
@@ -177,7 +191,7 @@ Finally, create a new private channel, and add the new linked role.
### Token storage
-This app largely relies on Discord's [OAuth2](/docs/topics/oauth2) implementation to obtain access tokens. This model of user based authentication relies on storing refresh tokens, and using them to acquire access tokens. The example code in [`src/storage.js`](https://github.com/discord/linked-roles-sample/blob/main/src/storage.js) uses in-memory storage to manage these tokens, but for any production deployment a database with persistent storage should be used.
+This app largely relies on Discord's [OAuth2](/developers/docs/topics/oauth2) implementation to obtain access tokens. This model of user based authentication relies on storing refresh tokens, and using them to acquire access tokens. The example code in [`src/storage.js`](https://github.com/discord/linked-roles-sample/blob/main/src/storage.js) uses in-memory storage to manage these tokens, but for any production deployment a database with persistent storage should be used.
### Advanced examples
diff --git a/discord/developers/docs/tutorials/configuring-app-metadata-for-linked-roles.mdx b/discord/developers/docs/tutorials/configuring-app-metadata-for-linked-roles.mdx
new file mode 100644
index 0000000000..801b3a6b3f
--- /dev/null
+++ b/discord/developers/docs/tutorials/configuring-app-metadata-for-linked-roles.mdx
@@ -0,0 +1,187 @@
+---
+title: Configuring App Metadata for Linked Roles
+description: Tutorial for setting up role connection metadata to link external app data with Discord roles.
+---
+
+Linked roles are a type of role in Discord that requires a user to connect to 3rd-party services and meet defined criteria. A role's criteria could just include the user connecting to that service, but it's often more narrow—like having a verified account, having certain stats, or having more than a certain number of followers.
+
+Apps can define their own [role connection metadata](/developers/docs/resources/application-role-connection-metadata), which admins can use to configure linked roles in servers where that app is installed. Apps must also set up an [OAuth2 flow](/developers/docs/topics/oauth2) to allow users to authenticate and grant the required `role_connections.write` scope.
+
+This tutorial walks through building a Discord app in JavaScript with linked roles support.
+
+
+All of the sample code used in this tutorial can be found in the [`linked-roles-sample` GitHub repo](https://github.com/discord/linked-roles-sample)
+
+
+---
+
+## Creating an app
+
+The first thing we’ll do is create an app through the [developer dashboard](https://discord.com/developers/applications). If you already have an app created, you can jump right to the [Running your app](/developers/docs/tutorials/configuring-app-metadata-for-linked-roles#running-your-app) section.
+
+
+Basic steps to create an app are outlined below, but a more detailed walkthrough is in the [Getting Started guide](/developers/docs/quick-start/getting-started).
+
+
+- Navigate to the [developer dashboard](https://discord.com/developers/applications)
+- Click **New Application** in the upper right corner, then select a name and create your app
+- Click on the **Bot** tab on the left sidebar. On that page, click **Reset Token** and store the token somewhere safe (like in a password manager)
+
+
+Bot tokens are used to authorize API requests and carry your bot's permissions, making them highly sensitive. Never share your token or check it into any kind of version control.
+
+
+### Adding scopes
+
+Apps need approval from installing users to perform actions inside of Discord. So before installing your app, let's add some scopes to request during installation.
+
+- Click on `OAuth2` in the left sidebar, then `URL generator`
+- Check the `bot` scope
+- After the scope is selected, you should see a **Generated URL** which can be used to install your app
+
+
+See a list of all [OAuth2 scopes](/developers/docs/topics/oauth2#shared-resources-oauth2-scopes), or read more on [user permissions](/developers/docs/topics/permissions) in the documentation.
+
+
+### Installing your app
+
+Copy the **Generated URL** from above, and paste it into your browser. You’ll be guided through the installation flow, where you should make sure you’re installing the app on a server where you can develop and test.
+
+After installing your app, you can head over to your server and see that it has joined ✨
+
+## Running your app
+
+All of the code used in the example app can be found in the [GitHub repository](https://github.com/discord/linked-roles-sample).
+
+### Remix the project
+
+This guide uses Glitch, which allows you to quickly clone and develop an app from within your browser. There are also instructions on developing locally using ngrok in the README if you'd prefer.
+
+
+While Glitch is great for development and testing, [it has technical limitations](https://help.glitch.com/kb/article/17-technical-restrictions/) so other hosting providers should be considered for production apps.
+
+
+To start, [remix (or clone) the Glitch project 🎏](https://glitch.com/edit/#!/remix/linked-role-discord-bot)
+
+When you remix the project, you'll see a new Glitch project with a unique name similar to this:
+
+
+
+#### Project structure
+
+All of the files for the project are on the left-hand side. Here's a quick glimpse at the structure:
+
+```
+├── assets -> images used in this tutorial
+├── src
+├──├── config.js -> Parsing of local configuration
+├──├── discord.js -> Discord specific auth & API wrapper
+├──├── register.js -> Tool to register the metadata schema
+├──├── server.js -> Main entry point for the application
+├──├── storage.js -> Provider for storing OAuth2 tokens
+├── .env -> your credentials and IDs
+├── .gitignore
+├── package.json
+└── README.md
+```
+
+### Configure your app
+
+There's already some code in your `server.js` file, but you’ll need your app’s token and ID to make requests. All of your credentials can be stored directly in the `.env` file.
+
+
+It bears repeating that you should never check any credentials or secrets into source control. The getting started project's `.gitignore` comes pre-loaded with `.env` to prevent it.
+
+
+First, copy your bot user’s token from earlier and paste it in the `DISCORD_TOKEN` variable in your `.env` file.
+
+Next, navigate to your app settings in the developer portal, and navigate to OAuth2 -> General. Copy the Client ID and Client Secret for your application, and paste the values as `DISCORD_CLIENT_ID` and `DISCORD_CLIENT_SECRET` in your `.env`.
+
+
+
+Now, we need to set the Redirect URL that will be used for our OAuth2 flow. Go back to Glitch, and click the `Share` button for your project. Copy the public live URL for your app:
+
+
+
+Go back to the OAuth2 -> General tab in the Discord developer portal, and add a new redirect for your app using the Glitch URL and the `/discord-oauth-callback` route. Copy this URL, then paste it as `DISCORD_REDIRECT_URI` in your `.env`.
+
+Go to the General Information tab in the developer portal, and scroll down to the `Linked Roles Verification Url` field. Paste the base URL to your Glitch app, add the `/linked-role` route, then save.
+
+
+For the Glitch project used in the screenshots, the verification URL would be `https://adjoining-crawling-yamamomo.glitch.me/linked-role`
+
+
+
+
+Finally, to generate a unique cookie secret, go back to Glitch, and click on the `Terminal` tab. Run the following commands:
+
+```
+$ node
+crypto.randomUUID()
+```
+
+Copy the randomly generated UUID, and paste it into your `.env` as `COOKIE_SECRET`. Your `.env` should look something like this:
+
+```
+DISCORD_CLIENT_ID:
+DISCORD_CLIENT_SECRET:
+DISCORD_TOKEN:
+DISCORD_REDIRECT_URI: https://.glitch.me/discord-oauth-callback
+COOKIE_SECRET:
+```
+
+## Registering your metadata schema
+
+As a one-time step, you must tell Discord which metadata fields you are going to allow admins to use for linked roles associated with your app.
+
+To configure connection metadata for your app, you'll call the [PUT /users/@me/applications/<application_id>/role-connection](/developers/docs/resources/application-role-connection-metadata#update-application-role-connection-metadata-records) method with [application connection role metadata](/developers/docs/resources/application-role-connection-metadata#application-role-connection-metadata-object). In the sample app, this is handled in [`src/register.js`](https://github.com/discord/linked-roles-sample/blob/main/src/register.js), and can be run via the command line.
+
+Go back to Glitch, click the **terminal** tab, and run the following command:
+
+```
+$ node src/register.js
+```
+
+
+
+## Trying it out
+
+Now that you've built your app, let's give it a try both from the server owner and the user's perspective.
+
+### Creating the linked role
+
+To try out the app, we'll create a linked role in a server where you have admin permissions. Open up the **Server Settings**, select **Roles**, and click on `Create Role`.
+
+Give the role a name, save it, then click on `Links`. Click the `Add requirement` button, and you should see your bot in the list of available Apps. Click on it, and you will see a setup screen where you can configure specific criteria for your role.
+
+
+
+### Acquiring the role
+
+To acquire your newly created role, click the server name in the upper left corner of the screen, and select `Linked Roles`. Click on your role, and it will present the opportunity to connect your account.
+
+
+When you connect your account, one of the scopes requested in the OAuth flow is `role_connections.write`, which is required for an app to update a user's role connection information.
+
+
+
+
+Click on the linked role criteria. This should lead to the Discord OAuth2 consent screen. Click `Authorize`, and then return to Discord.
+
+
+
+After returning to Discord, you should see your account granted the linked role.
+
+
+
+Finally, create a new private channel, and add the new linked role.
+
+## Tips & Tricks
+
+### Token storage
+
+This app largely relies on Discord's [OAuth2](/developers/docs/topics/oauth2) implementation to obtain access tokens. This model of user based authentication relies on storing refresh tokens, and using them to acquire access tokens. The example code in [`src/storage.js`](https://github.com/discord/linked-roles-sample/blob/main/src/storage.js) uses in-memory storage to manage these tokens, but for any production deployment a database with persistent storage should be used.
+
+### Advanced examples
+
+For a more complex example using the Fitbit API, see https://github.com/JustinBeckwith/fitbit-discord-bot/.
diff --git a/docs/tutorials/developing-a-user-installable-app.mdx b/discord/developers/docs/tutorials/developing-a-user-installable-app.mdx
similarity index 76%
rename from docs/tutorials/developing-a-user-installable-app.mdx
rename to discord/developers/docs/tutorials/developing-a-user-installable-app.mdx
index 6b2ead5806..9ffa7f51ed 100644
--- a/docs/tutorials/developing-a-user-installable-app.mdx
+++ b/discord/developers/docs/tutorials/developing-a-user-installable-app.mdx
@@ -1,16 +1,21 @@
-# Developing A User-Installable App
+---
+title: Developing A User-Installable App
+description: Tutorial for creating Discord apps that can be installed to user accounts.
+---
+
+import {LinkButton} from '/snippets/linkbutton.jsx'
Discord apps can be installed to servers, users, or both. This guide will walk you through building a basic game integration app that is installable to both Discord users and servers.
-While the tutorial will focus on supporting different [installation contexts](/docs/resources/application#installation-context), we'll be building a basic game integration along the way with a wiki lookup with user-specific bookmarking and a server leaderboard. The app has four commands (`/link`, `/profile`, `/leaderboard`, and `/wiki`) that can be run in different installation and interaction contexts (which are concepts we'll dig into later in the tutorial).
+While the tutorial will focus on supporting different [installation contexts](/developers/docs/resources/application#installation-context), we'll be building a basic game integration along the way with a wiki lookup with user-specific bookmarking and a server leaderboard. The app has four commands (`/link`, `/profile`, `/leaderboard`, and `/wiki`) that can be run in different installation and interaction contexts (which are concepts we'll dig into later in the tutorial).
-
+
- **[GitHub repository](https://github.com/discord/user-install-example)** where the code from this guide lives.
- **[discord-interactions](https://github.com/discord/discord-interactions-js)**, a library that provides types and helper functions for Discord apps.
- **[Express](https://expressjs.com/)**, a popular JavaScript web framework we'll use to create a server where Discord can send requests.
- **[ngrok](https://ngrok.com/)**, a tool that lets us tunnel our local server to a public URL where Discord can send requests.
-
+
---
@@ -18,7 +23,7 @@ While the tutorial will focus on supporting different [installation contexts](/d
Before we dig in, you'll need the project code from the [sample app repository](https://github.com/discord/user-install-example).
-
+
```
├── .env.sample -> sample .env file
├── app.js -> main entrypoint for the app
@@ -29,11 +34,11 @@ Before we dig in, you'll need the project code from the [sample app repository](
├── README.md
└── .gitignore
```
-
+
-:::info
+
We'll be developing our app locally with a little help from [ngrok](https://ngrok.com/), but you can use your preferred development environment.
-:::
+
If you don't have [NodeJS](https://nodejs.org/en/download/) installed, install that first.
@@ -59,7 +64,7 @@ With that out of the way, open your new project in the code editor of your choic
First, you'll need to create an app in the developer portal if you don't have one already:
-Create App
Enter a name for your app, then press **Create**.
@@ -69,9 +74,9 @@ After you create your app, you'll land on the **General Overview** page of the a
While we're in your app's settings, we'll want to get a few sensitive values for your app, like its token and ID.
-:::warn
+
Your token is used to authorize API requests and carry your app's permissions, so they are *highly* sensitive. Make sure to never share your token or check it into any kind of version control.
-:::
+
Back in your project folder, rename the `.env.sample` file to `.env`. `.env` is where we'll store all of your app's credentials.
@@ -85,13 +90,13 @@ Now that you have the credentials you need, we'll configure your app to support
### Add Guild Members intent
-The sample app fetches members in the server when constructing a fake game leaderboard. Getting server members requires a special permission called a [privileged intent](/docs/events/gateway#privileged-intents), so we'll add that to our app.
+The sample app fetches members in the server when constructing a fake game leaderboard. Getting server members requires a special permission called a [privileged intent](/developers/docs/events/gateway#privileged-intents), so we'll add that to our app.
Go to the **Bot** page and find the **Privileged Gateway Intents** section. Toggle "Server Member Intent" to be active.
### Choosing Supported Installation Contexts
-An app's **[installation context](/docs/resources/application#installation-context)** defines how it's installed: to a server, to a user, or both.
+An app's **[installation context](/developers/docs/resources/application#installation-context)** defines how it's installed: to a server, to a user, or both.
We're going to configure our app to support both installation contexts, and while that's a good default for most apps, some apps may only make sense in one context or the other.
@@ -99,11 +104,11 @@ In your app's settings, go to the **Installation** page from the sidebar. Under
### Configuring Default Install Settings
-The default install settings of your app determines the default [scopes](/docs/topics/oauth2#shared-resources-oauth2-scopes) and [bot user permissions](/docs/topics/permissions) for each supported installation context. At the moment, apps installed to a user context only support the `applications.commands` scope (which allows your app to install [commands](/docs/interactions/application-commands)) in the default install settings.
+The default install settings of your app determines the default [scopes](/developers/docs/topics/oauth2#shared-resources-oauth2-scopes) and [bot user permissions](/developers/docs/topics/permissions) for each supported installation context. At the moment, apps installed to a user context only support the `applications.commands` scope (which allows your app to install [commands](/developers/docs/interactions/application-commands)) in the default install settings.
###### Update Install Link
-Before adding default install settings, we need to select Discord Provided Link for the app's [install link](/docs/resources/application#install-links). Under the **Install Link** section, select `Discord Provided Link` from the dropdown if it isn't already selected (it should be by default). Once it's selected, the **Default Install Settings** will appear.
+Before adding default install settings, we need to select Discord Provided Link for the app's [install link](/developers/docs/resources/application#install-links). Under the **Install Link** section, select `Discord Provided Link` from the dropdown if it isn't already selected (it should be by default). Once its selected, the **Default Install Settings** will appear.
###### Adding Default Install Settings
@@ -111,13 +116,13 @@ Under the **Default Install Settings** section:
- For **User Install**, add the `applications.commands` scope
- For **Guild Install**, add the `applications.commands` scope and `bot` scope. When you select `bot`, a new **Permissions** menu will appear to select the bot user's permissions. Select any permissions that you may want for your app—for now, I'll just select `Send Messages`.
-:::info
-Permissions for a bot user are very similar to permissions for other Discord users. Details about permissions, and a list of available permissions is on the [Permissions](/docs/topics/permissions#permissions-bitwise-permission-flags) page.
-:::
+
+Permissions for a bot user are very similar to permissions for other Discord users. Details about permissions, and a list of available permissions is on the [Permissions](/developers/docs/topics/permissions#permissions-bitwise-permission-flags) page.
+
After you've selected the scopes and permissions for your app, click **Save Changes**.
-
+
### Installing your app
@@ -137,17 +142,17 @@ Follow the installation prompt to install your app to your user account. Once it
## Step 2: Setting Up Commands
-Next, we'll register the [application commands](/docs/interactions/application-commands) for our app. But before touching code, it's important to understand the concept of command contexts:
+Next, we'll register the [application commands](/developers/docs/interactions/application-commands) for our app. But before touching code, it's important to understand the concept of command contexts:
-
+
Commands have two context fields that can be set when creating or updating a command which let you limit the supported install methods and surfaces in Discord for that command:
-- **`integration_types`** lets you control which **[installation contexts](/docs/interactions/application-commands#installation-context)** a command is supported (user, guild, or both). For example, the `/link` and `/profile` commands we'll be creating are only available when the app is installed to a user.
-- **`contexts`** lets you set the **[interaction contexts](/docs/interactions/application-commands#interaction-contexts)**, or the surfaces in Discord, where a command can be used (in a guild channel, in your bot user's DM, and within other DMs or GDMs). For example, the `/leaderboard` command we'll be creating is only available when the command is run from a guild channel.
+- **`integration_types`** lets you control which **[installation contexts](/developers/docs/interactions/application-commands#installation-context)** a command is supported (user, guild, or both). For example, the `/link` and `/profile` commands we'll be creating are only available when the app is installed to a user.
+- **`contexts`** lets you set the **[interaction contexts](/developers/docs/interactions/application-commands#interaction-contexts)**, or the surfaces in Discord, where a command can be used (in a guild channel, in your bot user's DM, and within other DMs or GDMs). For example, the `/leaderboard` command we'll be creating is only available when the command is run from a guild channel.
-More information and details about command contexts are in the [contexts](/docs/interactions/application-commands#contexts) documentation, but for now we'll get a better understanding of contexts by using them in our sample app.
-
+More information and details about command contexts are in the [contexts](/developers/docs/interactions/application-commands#contexts) documentation, but for now we'll get a better understanding of contexts by using them in our sample app.
+
### Commands in the sample project
@@ -160,9 +165,9 @@ We'll be setting up four commands for our sample app that all have *slightly* di
| `/profile` | Get information about your game inventory and progress | `USER_INSTALL` | `GUILD`, `BOT_DM`, `PRIVATE_CHANNEL` |
| `/link` | Link your game account to Discord | `USER_INSTALL` | `BOT_DM` |
-:::info
-The supported installation contexts for a command affects which interaction contexts you can set. Specifically, the `PRIVATE_CHANNEL` interaction context can only be included in `contexts` if `USER_INSTALL` is included in `integration_types` for the command. Read details in the [documentation](/docs/interactions/application-commands#contexts).
-:::
+
+The supported installation contexts for a command affects which interaction contexts you can set. Specifically, the `PRIVATE_CHANNEL` interaction context can only be included in `contexts` if `USER_INSTALL` is included in `integration_types` for the command. Read details in the [documentation](/developers/docs/interactions/application-commands#contexts).
+
The payloads for our app's commands are in `commands.js` in the project folder in case you want to change any values or see what the command's context fields (`integration_types` and `contexts`) look like for each of the commands in the table above.
@@ -174,7 +179,7 @@ Now let's register your app's commands so you can see them in Discord. In your p
npm run register
```
-The register command will call the [Create Global Application Command](/docs/interactions/application-commands#create-global-application-command) endpoint for each of the command payloads in `commands.js`.
+The register command will call the [Create Global Application Command](/developers/docs/interactions/application-commands#create-global-application-command) endpoint for each of the command payloads in `commands.js`.
After your new commands have been created, you can go into Discord and look for the commands in the surfaces where we made them available:
- In **channels within the guild you installed your app**, you should see `/leaderboard`, `/wiki`, and `/profile`
@@ -200,11 +205,11 @@ First, go to your project's folder and run the following to start your app:
npm run start
```
-There should be some output indicating your app is running on port 3000. Behind the scenes, our app is ready to handle interactions from Discord, which includes verifying security request headers and responding to `PING` requests. We're skipping over a lot of the details in this tutorial, but details about preparing apps for interactions is in the [Interactions Overview](/docs/interactions/overview#preparing-for-interactions) documentation.
+There should be some output indicating your app is running on port 3000. Behind the scenes, our app is ready to handle interactions from Discord, which includes verifying security request headers and responding to `PING` requests. We're skipping over a lot of the details in this tutorial, but details about preparing apps for interactions is in the [Interactions Overview](/developers/docs/interactions/overview#preparing-for-interactions) documentation.
-:::info
+
By default, the server will listen to requests sent to port 3000, but if you want to change the port, you can specify a `PORT` variable in your `.env` file.
-:::
+
Next, we'll start our ngrok tunnel. If you don't have ngrok installed locally, you can install it by following the instructions on the [ngrok download page](https://ngrok.com/download).
@@ -225,9 +230,9 @@ Go to your [app's settings](https://discord.com/developers/applications) and on
Click **Save Changes** and if all is well, your Interactions Endpoint URL should be verified by Discord.
-:::info
+
If you have troubles verifying your endpoint, make sure both ngrok and your app is running on the same port, and that you've copied the ngrok URL correctly
-:::
+
### Understanding metadata for interactions
@@ -235,7 +240,7 @@ Now that our Interactions Endpoint URL is set up, we should now be able to run o
Back on the command line, our app is logging incoming requests from Discord, so you can see what the request body for your command invocation looked like.
-
+
The payload below is condensed to be more readable, but your interaction request body should look something like this:
```json
@@ -261,15 +266,15 @@ The payload below is condensed to be more readable, but your interaction request
}
```
-
+
-To see which command was run, you can look at the [`data` object](/docs/interactions/receiving-and-responding#interaction-object-interaction-data).
+To see which command was run, you can look at the [`data` object](/developers/docs/interactions/receiving-and-responding#interaction-object-interaction-data).
However, for this tutorial, we're going to focus more on the metadata related to installation and interaction contexts. There are a few metadata fields you'll want to pay attention to when building an app that can be installed to multiple interaction contexts—
###### `context`
-`context` tells you which [interaction context](/docs/interactions/application-commands#interaction-contexts) the command was invoked from. Since I triggered the command from my app's DM the `context` is `1` (or `BOT_DM`).
+`context` tells you which [interaction context](/developers/docs/interactions/application-commands#interaction-contexts) the command was invoked from. Since I triggered the command from my app's DM the `context` is `1` (or `BOT_DM`).
With interaction context, something to keep in mind in `BOT_DM` is only the *DM with your bot user*. If you run the same command in a DM with your bestie, or in a group DM, the interaction context will be `PRIVATE_CHANNEL` (`2`).
@@ -279,11 +284,11 @@ With interaction context, something to keep in mind in `BOT_DM` is only the *DM
The keys in the object are the relevant installation context(s) (`GUILD_INSTALL`/`"0"` and/or `USER_INSTALL`/`"1"`). The values depend on the key, but for `USER_INSTALL` the key will always be the ID of the user that authorized your app.
-:::info
+
`authorizing_integration_owners` is not the same as the user that triggered the interaction. Information about the user that triggered the interaction is in the `user` object.
-:::
+
-Understanding the authorization owner can be helpful when handling interactions from message components for apps installed to a user, which is discussed more in the [message component interactions](/docs/tutorials/developing-a-user-installable-app#using-metadata-for-message-component-interactions) section. Or you can find technical details in the [Authorizing Integration Owners](/docs/interactions/receiving-and-responding#interaction-object-authorizing-integration-owners-object) documentation.
+Understanding the authorization owner can be helpful when handling interactions from message components for apps installed to a user, which is discussed more in the [message component interactions](/developers/docs/tutorials/developing-a-user-installable-app#using-metadata-for-message-component-interactions) section. Or you can find technical details in the [Authorizing Integration Owners](/developers/docs/interactions/receiving-and-responding#interaction-object-authorizing-integration-owners-object) documentation.
###### `app_permissions`
@@ -291,13 +296,13 @@ Understanding the authorization owner can be helpful when handling interactions
In the sample payload, the value is `"442368"`.
-These values can be helpful when deciding how you want your app to [respond to the interaction](/docs/interactions/receiving-and-responding#responding-to-an-interaction). For example, perhaps you want your app to respond ephemerally when a specific command is invoked from a server, which the sample app does for the `/profile` command.
+These values can be helpful when deciding how you want your app to [respond to the interaction](/developers/docs/interactions/receiving-and-responding#responding-to-an-interaction). For example, perhaps you want your app to respond ephemerally when a specific command is invoked from a server, which the sample app does for the `/profile` command.
### Using metadata for command interactions
As mentioned above, the `/profile` command for our app will respond ephemerally, meaning only the invoking user will see the response, when invoked from a server. If it's invoked within a DM with the bot user, it'll respond with a non-ephemeral message. In the project, you can see this logic in `app.js` when handling the `/profile` command:
-
+
Below is the logic for handling the `/profile` command. When the context for the interaction is in a server, we'll make our interaction response ephemeral and add a button so the user can share their profile if they want.
@@ -342,7 +347,7 @@ if (name === 'profile') {
});
}
```
-
+
In the sample app code, we assign the value of `context` in the request body to a new `interactionContext` variable. Based on the context, we modify how we respond to the command interaction. If it was run in a guild or within a G(DM) other than the DM with the app's bot user, `flags` is set to `64` to make the response ephemeral, and a new button component is added so that the user can share their profile if they want.
@@ -352,17 +357,17 @@ Message component interactions can be triggered by any user the component is vis
Consider we added a new `/game` command supported in the `USER_INSTALL` installation context that a user could trigger to send a message to whatever guild or group DM they're in to ask others if they're interested in joining a game match:
-
+
When someone clicks on the button, our app would care about two users when handling the interaction:
1. User B, who clicked the "Join" button so our app can track who is interested in joining the match
2. User A, who ran the `/game` command so our app can tell them who is interested in joining the match
-There are two additional fields to know about that can be helpful in this scenario—
+There are two fields additional fields to know about that can be helpful in this scenario—
###### `interaction_metadata`
-Messages created in response to an interaction will include an [`interaction_metadata` object](/docs/resources/message#message-interaction-metadata-object) which includes metadata related to the interaction.
+Messages created in response to an interaction will include an [`interaction_metadata` object](/developers/docs/resources/message#message-interaction-metadata-object) which includes metadata related to the interaction.
###### `authorizing_integration_owners`
@@ -374,11 +379,11 @@ For user-installed apps, it can be used to differentiate between the user that i
*Yay~!* At this point, you have an app that supports both installation contexts and understand the basics of using metadata to support different contexts. Now you can go explore the documentation for details, or play with the sample app to develop more complex features.
-
-
+
+
Explore the Interactions documentation to learn more about receiving and responding to commands and message components
-
+
GitHub repository with sample project
-
+
diff --git a/docs/tutorials/hosting-on-cloudflare-workers.md b/discord/developers/docs/tutorials/hosting-on-cloudflare-workers.md
similarity index 89%
rename from docs/tutorials/hosting-on-cloudflare-workers.md
rename to discord/developers/docs/tutorials/hosting-on-cloudflare-workers.md
index 682f7361ee..fb011a3ceb 100644
--- a/docs/tutorials/hosting-on-cloudflare-workers.md
+++ b/discord/developers/docs/tutorials/hosting-on-cloudflare-workers.md
@@ -4,19 +4,19 @@ sidebar_label: Hosting on Cloudflare Workers
# Hosting a Reddit API Discord app on Cloudflare Workers
-When building Discord apps, your app can receive common events from the client as [webhooks](/docs/resources/webhook) when users interact with your app through interactions like [application commands](/docs/interactions/application-commands) or [message components](/docs/components/reference).
+When building Discord apps, your app can receive common events from the client as [webhooks](/developers/docs/resources/webhook) when users interact with your app through interactions like [application commands](/developers/docs/interactions/application-commands) or [message components](/developers/docs/components/reference).
Discord will send these events to a pre-configured HTTPS endpoint (called an Interactions Endpoint URL in an app's configuration) as a JSON payload with details about the event.
This tutorial walks through building a Discord app powered by [`r/aww`](https://www.reddit.com/r/aww) using JavaScript:
-
+
All of the code for this app can be found **[on GitHub](https://github.com/discord/cloudflare-sample-app)**.
### Features and technologies used
-- [Discord Interactions API](/docs/interactions/receiving-and-responding) (specifically slash commands)
+- [Discord Interactions API](/developers/docs/interactions/receiving-and-responding) (specifically slash commands)
- [Cloudflare Workers](https://workers.cloudflare.com/) for hosting
- [Reddit API](https://www.reddit.com/dev/api/) to send messages back to the user
@@ -30,23 +30,25 @@ To start, we'll create the app through the [Discord Developer Dashboard](https:/
- Click `New Application`, and choose a name
- Copy your **Public Key** and **Application ID**, and put them somewhere locally (we'll need these later)
-
+
- Now click on the **Bot** tab on the left sidebar.
- Grab the `token` for your bot, and store it somewhere safe (I like to put these tokens in a password manager like [1password](https://1password.com/) or [lastpass](https://www.lastpass.com/)).
-:::warn
+
+
For security reasons, you can only view your bot token once. If you misplace your token, you'll have to generate a new one.
-:::
+
+
## Adding bot permissions
-Now we'll configure the bot with [permissions](/docs/topics/permissions) required to create and use slash commands, as well as send messages in channels.
+Now we'll configure the bot with [permissions](/developers/docs/topics/permissions) required to create and use slash commands, as well as send messages in channels.
- Click on the `OAuth2` tab, and choose the `URL Generator`. Click the `bot` and `applications.commands` scopes.
- Check the boxes next to `Send Messages` and `Use Slash Commands`, then copy the `Generated URL`.
-
+
- Paste the URL into the browser and follow the OAuth flow, selecting the server where you'd like to develop and test your bot.
@@ -54,9 +56,11 @@ Now we'll configure the bot with [permissions](/docs/topics/permissions) require
Cloudflare Workers are a convenient way to host Discord apps due to the free tier, simple development model, and automatically managed environment (no VMs!).
-:::warn
+
+
When using Cloudflare Workers, your app won't be able to access non-ephemeral CDN media. For example, trying to fetch an image like `https://cdn.discordapp.com/attachments/1234/56789/my_image.png` would result in a `403` error. Cloudflare Workers are still able to access ephemeral CDN media.
-:::
+
+
- Visit the [Cloudflare Dashboard](https://dash.cloudflare.com/)
- Click on the `Workers` tab, and create a new service using the same name as your Discord bot
@@ -74,9 +78,11 @@ $ wrangler secret put DISCORD_APPLICATION_ID
You'll also need the Guild ID for the server where your app is installed. This can be found in the URL when you visit any channel in that server.
-:::info
+
+
For example, if my URL was `https://discord.com/channels/123456/789101112`, the Guild ID is the first number—in this case **`123456`**.
-:::
+
+
Once you know your Guild ID, set that variable as well:
@@ -86,9 +92,11 @@ $ wrangler secret put DISCORD_TEST_GUILD_ID
## Running locally
-:::info
+
+
This depends on the beta version of the `wrangler` package, which better supports ESM on Cloudflare Workers.
-:::
+
+
Let's start by cloning the repository and installing dependencies. This requires at least v16 of [Node.js](https://nodejs.org/en/):
@@ -135,7 +143,7 @@ export const INVITE_COMMAND = {
};
```
-The code to register commands lives in `register.js`. Commands can be [registered globally](/docs/interactions/application-commands#create-global-application-command), making them available for all servers with the app installed, or they can be [registered on a single server](/docs/interactions/application-commands#create-guild-application-command).
+The code to register commands lives in `register.js`. Commands can be [registered globally](/developers/docs/interactions/application-commands#create-global-application-command), making them available for all servers with the app installed, or they can be [registered on a single server](/developers/docs/interactions/application-commands#create-guild-application-command).
In this example - we'll just focus on global commands:
@@ -215,13 +223,13 @@ When a user types a slash command, Discord will send an HTTP request to a public
$ npm run ngrok
```
-
+
This is going to bounce requests off of an external endpoint, and forward them to your machine. Copy the HTTPS link provided by the tool. It should look something like `https://8098-24-22-245-250.ngrok.io`.
Now head back to the Discord Developer Dashboard, and update the `Interactions Endpoint URL` for your app:
-
+
This is the process we'll use for local testing and development. When you've published your app to Cloudflare, you will **want to update this field to use your Cloudflare Worker URL.**
@@ -344,12 +352,14 @@ router.post('/', async (request, env) => {
## Next steps
-:::info
+
+
In case you need to reference any of the code, you can find the repo [on GitHub](https://github.com/discord/cloudflare-sample-app)
-:::
+
+
With your app built and deployed, you can start customizing it to be your own:
-- Use **[message components](/docs/components/reference)** in your app to add more interactivity (like buttons and select menus).
+- Use **[message components](/developers/docs/components/reference)** in your app to add more interactivity (like buttons and select menus).
- Take a look at different **[public APIs](https://github.com/public-apis/public-apis)** on GitHub.
- Join the **[Discord Developers server](https://discord.gg/discord-developers)** to ask questions about the API, attend events hosted by the Discord API team, and interact with other developers.
diff --git a/discord/developers/docs/tutorials/hosting-on-cloudflare-workers.mdx b/discord/developers/docs/tutorials/hosting-on-cloudflare-workers.mdx
new file mode 100644
index 0000000000..928d986c74
--- /dev/null
+++ b/discord/developers/docs/tutorials/hosting-on-cloudflare-workers.mdx
@@ -0,0 +1,353 @@
+---
+title: Hosting a Reddit API Discord app on Cloudflare Workers
+sidebarTitle: Hosting on Cloudflare Workers
+description: Tutorial for deploying Discord apps on Cloudflare Workers.
+---
+
+When building Discord apps, your app can receive common events from the client as [webhooks](/developers/docs/resources/webhook) when users interact with your app through interactions like [application commands](/developers/docs/interactions/application-commands) or [message components](/developers/docs/components/reference).
+
+Discord will send these events to a pre-configured HTTPS endpoint (called an Interactions Endpoint URL in an app's configuration) as a JSON payload with details about the event.
+
+This tutorial walks through building a Discord app powered by [`r/aww`](https://www.reddit.com/r/aww) using JavaScript.
+
+All of the code for this app can be found **[on GitHub](https://github.com/discord/cloudflare-sample-app)**.
+
+### Features and technologies used
+
+- [Discord Interactions API](/developers/docs/interactions/receiving-and-responding) (specifically slash commands)
+- [Cloudflare Workers](https://workers.cloudflare.com/) for hosting
+- [Reddit API](https://www.reddit.com/dev/api/) to send messages back to the user
+
+---
+
+## Creating an app on Discord
+
+To start, we'll create the app through the [Discord Developer Dashboard](https://discord.com/developers/applications):
+
+- Visit https://discord.com/developers/applications
+- Click `New Application`, and choose a name
+- Copy your **Public Key** and **Application ID**, and put them somewhere locally (we'll need these later)
+
+
+
+- Now click on the **Bot** tab on the left sidebar.
+- Grab the `token` for your bot, and store it somewhere safe (I like to put these tokens in a password manager like [1password](https://1password.com/) or [lastpass](https://www.lastpass.com/)).
+
+
+For security reasons, you can only view your bot token once. If you misplace your token, you'll have to generate a new one.
+
+
+## Adding bot permissions
+
+Now we'll configure the bot with [permissions](/developers/docs/topics/permissions) required to create and use slash commands, as well as send messages in channels.
+
+- Click on the `OAuth2` tab, and choose the `URL Generator`. Click the `bot` and `applications.commands` scopes.
+- Check the boxes next to `Send Messages` and `Use Slash Commands`, then copy the `Generated URL`.
+
+
+
+- Paste the URL into the browser and follow the OAuth flow, selecting the server where you'd like to develop and test your bot.
+
+## Creating your Cloudflare Worker
+
+Cloudflare Workers are a convenient way to host Discord apps due to the free tier, simple development model, and automatically managed environment (no VMs!).
+
+
+When using Cloudflare Workers, your app won't be able to access non-ephemeral CDN media. For example, trying to fetch an image like `https://cdn.discordapp.com/attachments/1234/56789/my_image.png` would result in a `403` error. Cloudflare Workers are still able to access ephemeral CDN media.
+
+
+- Visit the [Cloudflare Dashboard](https://dash.cloudflare.com/)
+- Click on the `Workers` tab, and create a new service using the same name as your Discord bot
+- Make sure to [install the Wrangler CLI](https://developers.cloudflare.com/workers/cli-wrangler/install-update/) and set it up.
+
+### Storing secrets
+
+The production service needs access to some of the information we saved earlier. To set those variables, run:
+
+```
+$ wrangler secret put DISCORD_TOKEN
+$ wrangler secret put DISCORD_PUBLIC_KEY
+$ wrangler secret put DISCORD_APPLICATION_ID
+```
+
+You'll also need the Guild ID for the server where your app is installed. This can be found in the URL when you visit any channel in that server.
+
+
+For example, if my URL was `https://discord.com/channels/123456/789101112`, the Guild ID is the first number—in this case **`123456`**.
+
+
+Once you know your Guild ID, set that variable as well:
+
+```
+$ wrangler secret put DISCORD_TEST_GUILD_ID
+```
+
+## Running locally
+
+
+This depends on the beta version of the `wrangler` package, which better supports ESM on Cloudflare Workers.
+
+
+Let's start by cloning the repository and installing dependencies. This requires at least v16 of [Node.js](https://nodejs.org/en/):
+
+```
+$ npm install
+```
+
+### Project structure
+
+A brief look at the cloned app's project structure:
+
+```
+├── .github/workflows/ci.yaml -> GitHub Action configuration
+├── src
+├── ├── commands.js -> JSON payloads for commands
+├── ├── reddit.js -> Interactions with the Reddit API
+├── ├── register.js -> Sets up commands with the Discord API
+├── ├── server.js -> Discord app logic and routing
+├── test
+├── ├── test.js -> Tests for app
+├── wrangler.toml -> Configuration for Cloudflare Workers
+├── package.json
+├── README.md
+├── renovate.json -> Configuration for repo automation
+├── .eslintrc.json
+├── .prettierignore
+├── .prettierrc.json
+└── .gitignore
+```
+
+### Registering commands
+
+Before testing our app, we need to register our desired slash commands. For this app, we'll have a `/awwww` command, and a `/invite` command. The name and description for these are kept separate in `commands.js`:
+
+```js
+export const AWW_COMMAND = {
+ name: 'awwww',
+ description: 'Drop some cuteness on this channel.',
+};
+
+export const INVITE_COMMAND = {
+ name: 'invite',
+ description: 'Get an invite link to add the bot to your server',
+};
+```
+
+The code to register commands lives in `register.js`. Commands can be [registered globally](/developers/docs/interactions/application-commands#create-global-application-command), making them available for all servers with the app installed, or they can be [registered on a single server](/developers/docs/interactions/application-commands#create-guild-application-command).
+
+In this example - we'll just focus on global commands:
+
+```js
+import { AWW_COMMAND, INVITE_COMMAND } from './commands.js';
+import fetch from 'node-fetch';
+
+/**
+ * This file is meant to be run from the command line, and is not used by the
+ * application server. It's allowed to use node.js primitives, and only needs
+ * to be run once.
+ */
+
+const token = process.env.DISCORD_TOKEN;
+const applicationId = process.env.DISCORD_APPLICATION_ID;
+
+if (!token) {
+ throw new Error('The DISCORD_TOKEN environment variable is required.');
+}
+if (!applicationId) {
+ throw new Error(
+ 'The DISCORD_APPLICATION_ID environment variable is required.'
+ );
+}
+
+/**
+ * Register all commands globally. This can take o(minutes), so wait until
+ * you're sure these are the commands you want.
+ */
+async function registerGlobalCommands() {
+ const url = `https://discord.com/api/v10/applications/${applicationId}/commands`;
+ await registerCommands(url);
+}
+
+async function registerCommands(url) {
+ const response = await fetch(url, {
+ headers: {
+ 'Content-Type': 'application/json',
+ Authorization: `Bot ${token}`,
+ },
+ method: 'PUT',
+ body: JSON.stringify([AWW_COMMAND, INVITE_COMMAND]),
+ });
+
+ if (response.ok) {
+ console.log('Registered all commands');
+ } else {
+ console.error('Error registering commands');
+ const text = await response.text();
+ console.error(text);
+ }
+ return response;
+}
+
+await registerGlobalCommands();
+```
+
+### Running the server
+
+This command needs to be run locally, once before getting started:
+
+```
+$ DISCORD_TOKEN=**** DISCORD_APPLICATION_ID=**** node src/register.js
+```
+
+We're finally ready to run this code locally! Let's start by running our local development server:
+
+```
+$ npm run dev
+```
+
+### Setting up ngrok
+
+When a user types a slash command, Discord will send an HTTP request to a public endpoint. During local development this can be a little challenging, so we're going to use [a tool called `ngrok`](https://ngrok.com/) to create an HTTP tunnel.
+
+```
+$ npm run ngrok
+```
+
+
+
+This is going to bounce requests off of an external endpoint, and forward them to your machine. Copy the HTTPS link provided by the tool. It should look something like `https://8098-24-22-245-250.ngrok.io`.
+
+Now head back to the Discord Developer Dashboard, and update the `Interactions Endpoint URL` for your app:
+
+
+
+This is the process we'll use for local testing and development. When you've published your app to Cloudflare, you will **want to update this field to use your Cloudflare Worker URL.**
+
+## Deployment
+
+This repository is set up to automatically deploy to Cloudflare Workers when new changes land on the `main` branch. To deploy manually, run `npm run publish`, which uses the `wrangler publish` command under the hood.
+
+Publishing via a GitHub Action requires obtaining an [API Token and your Account ID from Cloudflare](https://developers.cloudflare.com/workers/cli-wrangler/authentication/). These are stored [as secrets in the GitHub repository](https://docs.github.com/en/actions/security-guides/encrypted-secrets), making them available to GitHub Actions.
+
+The following configuration in `.github/workflows/ci.yaml` demonstrates how to tie it all together:
+
+```yaml
+release:
+ if: github.ref == 'refs/heads/main'
+ runs-on: ubuntu-latest
+ needs: [test, lint]
+ steps:
+ - uses: actions/checkout@v2
+ - uses: actions/setup-node@v2
+ with:
+ node-version: 16
+ - run: npm install
+ - run: npm run publish
+ env:
+ CF_API_TOKEN: ${{ secrets.CF_API_TOKEN }}
+ CF_ACCOUNT_ID: ${{ secrets.CF_ACCOUNT_ID }}
+```
+
+## Code deep dive
+
+Most of the interesting code in this app lives in `src/server.js`. Cloudflare Workers require exposing a `fetch` function, which is called as the entry point for each request. This code will largely do two things for us: validate the request is valid and actually came from Discord, and hand the request over to a router to help give us a little more control over execution.
+
+```js
+export default {
+ /**
+ * Every request to a worker will start in the `fetch` method.
+ * Verify the signature with the request, and dispatch to the router.
+ * @param {*} request A Fetch Request object
+ * @param {*} env A map of key/value pairs with env vars and secrets from the cloudflare env.
+ * @returns
+ */
+ async fetch(request, env) {
+ if (request.method === 'POST') {
+ // Using the incoming headers, verify this request actually came from discord.
+ const signature = request.headers.get('x-signature-ed25519');
+ const timestamp = request.headers.get('x-signature-timestamp');
+ const body = await request.clone().arrayBuffer();
+ const isValidRequest = verifyKey(
+ body,
+ signature,
+ timestamp,
+ env.DISCORD_PUBLIC_KEY
+ );
+ if (!isValidRequest) {
+ console.error('Invalid Request');
+ return new Response('Bad request signature.', { status: 401 });
+ }
+ }
+
+ // Dispatch the request to the appropriate route
+ return router.handle(request, env);
+ },
+};
+```
+
+All of the API calls from Discord in this example will be POSTed to `/`. From here, we will use the [`discord-interactions`](https://github.com/discord/discord-interactions-js) npm module to help us interpret the event, and to send results.
+
+```js
+/**
+ * Main route for all requests sent from Discord. All incoming messages will
+ * include a JSON payload described here:
+ * /developers/docs/interactions/receiving-and-responding#interaction-object
+ */
+router.post('/', async (request, env) => {
+ const message = await request.json();
+ console.log(message);
+ if (message.type === InteractionType.PING) {
+ // The `PING` message is used during the initial webhook handshake, and is
+ // required to configure the webhook in the developer portal.
+ console.log('Handling Ping request');
+ return new JsonResponse({
+ type: InteractionResponseType.PONG,
+ });
+ }
+
+ if (message.type === InteractionType.APPLICATION_COMMAND) {
+ // Most user commands will come as `APPLICATION_COMMAND`.
+ switch (message.data.name.toLowerCase()) {
+ case AWW_COMMAND.name.toLowerCase(): {
+ console.log('handling cute request');
+ const cuteUrl = await getCuteUrl();
+ return new JsonResponse({
+ type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
+ data: {
+ content: cuteUrl,
+ },
+ });
+ }
+ case INVITE_COMMAND.name.toLowerCase(): {
+ const applicationId = env.DISCORD_APPLICATION_ID;
+ const INVITE_URL = `https://discord.com/oauth2/authorize?client_id=${applicationId}&scope=applications.commands`;
+ return new JsonResponse({
+ type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
+ data: {
+ content: INVITE_URL,
+ flags: InteractionResponseFlags.EPHEMERAL,
+ },
+ });
+ }
+ default:
+ console.error('Unknown Command');
+ return new JsonResponse({ error: 'Unknown Type' }, { status: 400 });
+ }
+ }
+
+ console.error('Unknown Type');
+ return new JsonResponse({ error: 'Unknown Type' }, { status: 400 });
+});
+```
+
+## Next steps
+
+
+In case you need to reference any of the code, you can find the repo [on GitHub](https://github.com/discord/cloudflare-sample-app)
+
+
+With your app built and deployed, you can start customizing it to be your own:
+
+- Use **[message components](/developers/docs/components/reference)** in your app to add more interactivity (like buttons and select menus).
+- Take a look at different **[public APIs](https://github.com/public-apis/public-apis)** on GitHub.
+- Join the **[Discord Developers server](https://discord.gg/discord-developers)** to ask questions about the API, attend events hosted by the Discord API team, and interact with other developers.
diff --git a/docs/tutorials/upgrading-to-application-commands.md b/discord/developers/docs/tutorials/upgrading-to-application-commands.md
similarity index 65%
rename from docs/tutorials/upgrading-to-application-commands.md
rename to discord/developers/docs/tutorials/upgrading-to-application-commands.md
index b3744a2bd2..01e26ed2a1 100644
--- a/docs/tutorials/upgrading-to-application-commands.md
+++ b/discord/developers/docs/tutorials/upgrading-to-application-commands.md
@@ -4,15 +4,15 @@ sidebar_label: Upgrading to Application Commands
# Upgrading Apps to Use Application Commands
-As [message content has become a privileged intent](https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-FAQ) for verified apps, [application commands](/docs/interactions/application-commands) are the primary way Discord users interact with apps. The three types of commands (slash commands, user commands, and message commands) act as entry points into apps, and can be registered globally or for a subset of guilds.
+As [message content has become a privileged intent](https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-FAQ) for verified apps, [application commands](/developers/docs/interactions/application-commands) are the primary way Discord users interact with apps. The three types of commands (slash commands, user commands, and message commands) act as entry points into apps, and can be registered globally or for a subset of guilds.
This guide is intended to provide developers with apps currently using message content with a resource to walk through implementing and designing commands. Throughout the guide, the terms "application commands" and "commands" are used interchangeably.
-
+
-:::info
-If you are developing an app for the first time, the [commands documentation](/docs/interactions/application-commands) may be a more helpful resource for you.
-:::
+
+If you are developing an app for the first time, the [commands documentation](/developers/docs/interactions/application-commands) may be a more helpful resource for you.
+
Before diving in, it’s worth noting that with the message content changes, apps can still access message content in their DMs with users, as well as when messages are sent that directly `@mentions` their bot user (since there is clear user intent that the bot can read those messages).
@@ -26,21 +26,21 @@ There are three types of application commands: slash commands, user commands, an
### Slash Commands
-[Slash commands](/docs/interactions/application-commands#slash-commands) are the most common type of command. They are accessed by typing a forward slash (`/`) followed by the command’s name, or by using the plus button (+) to the left of the message input.
+[Slash commands](/developers/docs/interactions/application-commands#slash-commands) are the most common type of command. They are accessed by typing a forward slash (`/`) followed by the command’s name, or by using the plus button (+) to the left of the message input.
Slash commands can appear in channels and DMs, so they’re helpful when an action is tied to a channel, a server, or nothing at all.
### User Commands
-[User commands](/docs/interactions/application-commands#user-commands) are in the context menu for users, which is accessed by right-clicking or tapping on any user. They’re helpful when an action is tied to an individual user, like a moderation app adding a timeout to someone.
+[User commands](/developers/docs/interactions/application-commands#user-commands) are in the context menu for users, which is accessed by right-clicking or tapping on any user. They’re helpful when an action is tied to an individual user, like a moderation app adding a timeout to someone.
-:::info
+
Within the context menus for users and messages, the `Apps` submenu will only appear if an app in that server has installed a corresponding command (whether or not an individual user can use the installed command).
-:::
+
### Message Commands
-[Message commands](/docs/interactions/application-commands#message-commands) are in the context menu for messages, which is accessed by right-clicking on a message, or by clicking on the ellipses at the top-right of a message. They’re helpful when an action is tied to a message, like creating a reminder to reply to a message the following day.
+[Message commands](/developers/docs/interactions/application-commands#message-commands) are in the context menu for messages, which is accessed by right-clicking on a message, or by clicking on the ellipses at the top-right of a message. They’re helpful when an action is tied to a message, like creating a reminder to reply to a message the following day.
### After This Section
- Start thinking about how different app features might map to the different types of application commands.
@@ -49,32 +49,32 @@ Within the context menus for users and messages, the `Apps` submenu will only ap
Commands can be registered via HTTP requests after an app is authorized with the `applications.commands` scope. The `applications.commands` scope is also automatically included when an app requests the `bot` scope.
-:::info
-There is a section on [designing commands](/docs/tutorials/upgrading-to-application-commands#designing-for-commands) below implementation details that may be helpful as you start mapping out different commands
-:::
+
+There is a section on [designing commands](/developers/docs/tutorials/upgrading-to-application-commands#designing-for-commands) below implementation details that may be helpful as you start mapping out different commands
+
The API endpoint to register (or create) commands is different depending on its scope:
-- **[Global commands](/docs/interactions/application-commands#making-a-global-command)** are available in all of the servers where your app is installed, and can be created using the [`/applications/{YOUR APP ID}/commands` endpoint](/docs/interactions/application-commands#create-global-application-command). All of your app's global commands will automatically be added to the servers your app is installed in, regardless of whether they were registered before or after installation.
-- **[Guild commands](/docs/interactions/application-commands#making-a-guild-command)** are only available in the servers you explicitly add them to via the API, making them useful for features available only to a subset of guilds. They can be created using the [`/applications/{YOUR APP ID}/guilds/{A GUILD ID}/commands` endpoint](/docs/interactions/application-commands#create-guild-application-command).
+- **[Global commands](/developers/docs/interactions/application-commands#making-a-global-command)** are available in all of the servers where your app is installed, and can be created using the [`/applications/{YOUR APP ID}/commands` endpoint](/developers/docs/interactions/application-commands#create-global-application-command). All of your app's global commands will automatically be added to the servers your app is installed in, regardless of whether they were registered before or after installation.
+- **[Guild commands](/developers/docs/interactions/application-commands#making-a-guild-command)** are only available in the servers you explicitly add them to via the API, making them useful for features available only to a subset of guilds. They can be created using the [`/applications/{YOUR APP ID}/guilds/{A GUILD ID}/commands` endpoint](/developers/docs/interactions/application-commands#create-guild-application-command).
-While most apps won’t need to register more than a handful of commands, apps can have up to 100 global slash commands and 100 guild slash commands with unique names. They can also have 5 global user commands and 5 global message commands. Different limitations apply for global and guild commands, which can be found [in the documentation](/docs/interactions/application-commands#registering-a-command).
+While most apps won’t need to register more than a handful of commands, apps can have up to 100 global slash commands and 100 guild slash commands with unique names. They can also have 5 global user commands and 5 global message commands. Different limitations apply for global and guild commands, which can be found [in the documentation](/developers/docs/interactions/application-commands#registering-a-command).
### Using Options as Parameters
-Command options is an optional field (`options`) that can be defined when creating commands. When used, options will display for the user to fill out during invocation. You can also provide dynamic option suggestions using the `autocomplete` field. Read more about options [in the documentation](/docs/interactions/application-commands#application-command-object-application-command-option-structure).
+Command options is an optional field (`options`) that can be defined when creating commands. When used, options will display for the user to fill out during invocation. You can also provide dynamic option suggestions using the `autocomplete` field. Read more about options [in the documentation](/developers/docs/interactions/application-commands#application-command-object-application-command-option-structure).
-
+
### Using Subcommands to Group Actions
-[Subcommands and subcommand groups](/docs/interactions/application-commands#subcommands-and-subcommand-groups) help organize commands that are related to a shared resource or action. Instead of several top-level commands (like `/add-resource` and `/delete-resource`), you can have one top-level command with several subcommands (like `/resource add` and `/resource delete`).
+[Subcommands and subcommand groups](/developers/docs/interactions/application-commands#subcommands-and-subcommand-groups) help organize commands that are related to a shared resource or action. Instead of several top-level commands (like `/add-resource` and `/delete-resource`), you can have one top-level command with several subcommands (like `/resource add` and `/resource delete`).
Subcommands use the same `options` field as passing parameters, but with a type of `2`.
### Restricting Command Use
-[Application command permissions](/docs/interactions/application-commands#permissions) allow users and apps to restrict command usage in a server. When commands are restricted for a user, they won't appear for them in the client.
+[Application command permissions](/developers/docs/interactions/application-commands#permissions) allow users and apps to restrict command usage in a server. When commands are restricted for a user, they won't appear for them in the client.
If your app currently relies on permissioning, using command permissions can be a way to port them. It also cleans up the command picker UI for users, making it easier for them to find your app’s commands that are most relevant to them.
@@ -114,13 +114,13 @@ Below is a sample payload to create a global slash command with an optional para
#### Default Permissions
-When [creating](/docs/interactions/application-commands#create-global-application-command) or [updating](/docs/interactions/application-commands#edit-global-application-command) a command, you can use the `default_member_permissions` field to restrict the command to a set of bitwise permissions that reflect the default permission flags a user must be granted in order to use the command.
+When [creating](/developers/docs/interactions/application-commands#create-global-application-command) or [updating](/developers/docs/interactions/application-commands#edit-global-application-command) a command, you can use the `default_member_permissions` field to restrict the command to a set of bitwise permissions that reflect the default permission flags a user must be granted in order to use the command.
In addition, the `dm_permission` flag can be used to control whether a global command is available in DMs (not available for guild commands).
#### Updating Permissions
-Permissions for specific roles, users, and channels can be updated by your app if you have the `applications.commands.permissions.update` scope and a [Bearer token](/docs/topics/oauth2) that’s authenticated by a user with the necessary user permissions. Details about updating a command’s permissions are [in the documentation](/docs/interactions/application-commands#permissions).
+Permissions for specific roles, users, and channels can be updated by your app if you have the `applications.commands.permissions.update` scope and a [Bearer token](/developers/docs/topics/oauth2) that’s authenticated by a user with the necessary user permissions. Details about updating a command’s permissions are [in the documentation](/developers/docs/interactions/application-commands#permissions).
### After This Section
@@ -131,34 +131,34 @@ Permissions for specific roles, users, and channels can be updated by your app i
## Handling Commands
-Commands use the [interactions model](/docs/interactions/receiving-and-responding) through HTTP-based outgoing webhooks or the WebSocket-based [Interaction Create gateway event](/docs/events/gateway-events#interaction-create). Regardless of the transit method used to arrive, your app will receive relevant information when a Discord user triggers one of your app’s interactions.
+Commands use the [interactions model](/developers/docs/interactions/receiving-and-responding) through HTTP-based outgoing webhooks or the WebSocket-based [Interaction Create gateway event](/developers/docs/events/gateway-events#interaction-create). Regardless of the transit method used to arrive, your app will receive relevant information when a Discord user triggers one of your app’s interactions.
-:::warn
-If you continue using Gateway events, you’ll still receive message events but the payloads will have empty string or array data for message content-related fields like `content`, `embeds`, `attachments`, and `components` while `poll` will be omitted. You can read more in the [message content intent](/docs/events/gateway#message-content-intent) section.
-:::
+
+If you continue using Gateway events, you’ll still receive message events but the payloads will have empty string or array data for message content-related fields like `content`, `embeds`, `attachments`, and `components` while `poll` will be omitted. You can read more in the [message content intent](/developers/docs/events/gateway#message-content-intent) section.
+
-For commands, this means that each time one of your commands is used, your app will receive information like the command name and the user who triggered it. More information about this information is below in the section on [parsing command payloads](/docs/tutorials/upgrading-to-application-commands#parsing-command-payloads).
+For commands, this means that each time one of your commands is used, your app will receive information like the command name and the user who triggered it. More information about this information is below in the section on [parsing command payloads](/developers/docs/tutorials/upgrading-to-application-commands#parsing-command-payloads).
### Adding an Interactions Endpoint URL
-:::info
-This step is specific to receiving interactions over HTTP. If you prefer to use the [Gateway](/docs/events/gateway), this step won't be applicable to your app.
-:::
+
+This step is specific to receiving interactions over HTTP. If you prefer to use the [Gateway](/developers/docs/events/gateway), this step won't be applicable to your app.
+
Before your app can receive interactions, you’ll need to set up an **Interaction Endpoint URL** in your app settings. This endpoint should be a public URL where Discord can send all interactions-related requests.
However, before adding your URL to your app settings, your endpoint must be set up to handle two things:
-1. **Responding to `PING` events**: When you save a URL in your settings, Discord will send a `POST` request with `type: 1`. To acknowledge this request (and thus verify your endpoint), you should return a `200` response with a payload containing `type: 1`. More information can be found in the [Receiving an Interaction documentation](/docs/interactions/receiving-and-responding#receiving-an-interaction).
-2. **Verifying request signatures**: To ensure that requests are coming from Discord, your endpoint must verify each request using the included headers, specifically `X-Signature-Ed25519` and `X-Signature-Timestamp`. If the signature fails validating, your app should return a `401` response. More information and example code can be found in the [Security and Authorization documentation](/docs/interactions/overview#setting-up-an-endpoint-validating-security-request-headers).
+1. **Responding to `PING` events**: When you save a URL in your settings, Discord will send a `POST` request with `type: 1`. To acknowledge this request (and thus verify your endpoint), you should return a `200` response with a payload containing `type: 1`. More information can be found in the [Receiving an Interaction documentation](/developers/docs/interactions/receiving-and-responding#receiving-an-interaction).
+2. **Verifying request signatures**: To ensure that requests are coming from Discord, your endpoint must verify each request using the included headers, specifically `X-Signature-Ed25519` and `X-Signature-Timestamp`. If the signature fails validating, your app should return a `401` response. More information and example code can be found in the [Security and Authorization documentation](/developers/docs/interactions/overview#setting-up-an-endpoint-validating-security-request-headers).
-:::info
-Many libraries on the [Community Resources page](/docs/developer-tools/community-resources#interactions) simplify verification and interaction request handling by exporting reusable functions and/or handling it automatically.
-:::
+
+Many libraries on the [Community Resources page](/developers/docs/developer-tools/community-resources#interactions) simplify verification and interaction request handling by exporting reusable functions and/or handling it automatically.
+
After your URL is set up to handle signature verification and `PING` requests, you can add your Interaction Endpoint URL by navigating to your app settings from the [developer portal](https://discord.com/developers/applications). On the **General Information** page, you’ll see a field for your **Interactions Endpoint URL**.
-
+
After you paste your URL and click **Save Changes**, Discord will attempt to verify your endpoint.
@@ -168,13 +168,13 @@ If all goes well, your endpoint will successfully save. And if not, you should d
Once your app has a verified endpoint, you should start being able to receive command requests from Discord.
-As mentioned above, these include information relevant to handling the command like its name, the user who invoked it, and the guild and channel it was invoked from. It also includes additional details that could be relevant, like the [command options](/docs/interactions/application-commands#application-command-object-application-command-option-structure) or [locale information](/docs/interactions/application-commands#localization).
+As mentioned above, these include information relevant to handling the command like its name, the user who invoked it, and the guild and channel it was invoked from. It also includes additional details that could be relevant, like the [command options](/developers/docs/interactions/application-commands#application-command-object-application-command-option-structure) or [locale information](/developers/docs/interactions/application-commands#localization).
-Since slash commands (`CHAT_INPUT` commands) are run in the context of a channel, you’ll notice that their payloads don’t contain any information about specific messages. If your app needs the message content, you can use [message commands](/docs/interactions/application-commands#message-commands) which *do* include the message content.
+Since slash commands (`CHAT_INPUT` commands) are run in the context of a channel, you’ll notice that their payloads don’t contain any information about specific messages. If your app needs the message content, you can use [message commands](/developers/docs/interactions/application-commands#message-commands) which *do* include the message content.
-:::info
+
In the getting started guide’s repository, there’s a code sample showing [how to create and handle commands using JavaScript](https://github.com/discord/discord-example-app/blob/main/examples/command.js).
-:::
+
Below is an example payload your app would receive when a user invoked a global command with an option:
@@ -218,7 +218,7 @@ Below is an example payload your app would receive when a user invoked a global
}
```
-To determine how your app should handle an incoming command-related interaction, you can look in the `data` object which contains all of the command-specific information (including any options a user selected). Details about the full interactions object your app receives can be found in the [Interactions documentation](/docs/interactions/receiving-and-responding#interaction-object).
+To determine how your app should handle an incoming command-related interaction, you can look in the `data` object which contains all of the command-specific information (including any options a user selected). Details about the full interactions object your app receives can be found in the [Interactions documentation](/developers/docs/interactions/receiving-and-responding#interaction-object).
### After This Section
@@ -230,15 +230,17 @@ To determine how your app should handle an incoming command-related interaction,
Adding commands to your app can add discoverability and interactivity for users. While porting your app’s features, it’s worth considering how your app will be seen and used inside of the client. This section includes a handful of areas to consider when designing your app’s commands, and what happens after they’re invoked.
-:::info
+
+
CLIs (Command Line Interfaces) can be a helpful analogy when designing Discord commands, their options and subcommands, and how it all fits together into one experience. A good resource for this can be the open source [Command Interface Guidelines](https://clig.dev/).
-:::
+
+
### Choosing a Name
When creating a command, keep the name short and relevant. The name of the command should give users an idea of the action they’re invoking. A description can be a bit more verbose, leaving room to be more explicit about the action and its result.
-And when your app has several commands (and perhaps [subcommands](/docs/interactions/application-commands#subcommands-and-subcommand-groups)), it’s important to keep the naming scheme consistent.
+And when your app has several commands (and perhaps [subcommands](/developers/docs/interactions/application-commands#subcommands-and-subcommand-groups)), it’s important to keep the naming scheme consistent.
#### Examples
@@ -247,13 +249,13 @@ And when your app has several commands (and perhaps [subcommands](/docs/interact
### Collecting User Input
-When commands need a bit of input from a user, you can use the `options` field. Command options can be thought of as parameters to your command. They can be one of many [types](/docs/interactions/application-commands#application-command-object-application-command-option-type), like the standard string or number, or the more Discord-specific role, user, and channel.
+When commands need a bit of input from a user, you can use the `options` field. Command options can be thought of as parameters to your command. They can be one of many [types](/developers/docs/interactions/application-commands#application-command-object-application-command-option-type), like the standard string or number, or the more Discord-specific role, user, and channel.
-Options are great for short input, but if you need user input that’s longer than a couple of words, like a title or description, you can collect form-like input using [modals](/docs/interactions/receiving-and-responding#interaction-response-object-modal) as a response to the command invocation.
+Options are great for short input, but if you need user input that’s longer than a couple of words, like a title or description, you can collect form-like input using [modals](/developers/docs/interactions/receiving-and-responding#interaction-response-object-modal) as a response to the command invocation.
### Scoping a Command
-Commands can optionally be [scoped to specific guilds](/docs/interactions/application-commands#create-guild-application-command), rather than available everywhere your app is installed. Guild commands can be useful when your app has functionality that may not be relevant to all servers like:
+Commands can optionally be [scoped to specific guilds](/developers/docs/interactions/application-commands#create-guild-application-command), rather than available everywhere your app is installed. Guild commands can be useful when your app has functionality that may not be relevant to all servers like:
- When a command is in development
- When a specific command is opt-in or opt-out
@@ -261,9 +263,9 @@ Commands can optionally be [scoped to specific guilds](/docs/interactions/applic
### Responding to a Command
-Interactions (including commands) can have a hand-picked reply using one of the many available [interaction responses](/docs/interactions/receiving-and-responding#responding-to-an-interaction).
+Interactions (including commands) can have a hand-picked reply using one of the many available [interaction responses](/developers/docs/interactions/receiving-and-responding#responding-to-an-interaction).
-The specific response type should be picked based on the situation. Some commands may call for sending a message back to the channel where the command was invoked from, or perhaps just to the specific user who ran the command (for this, the [ephemeral message flag](/docs/interactions/receiving-and-responding#interaction-response-object-messages) can be used). Other commands may necessitate descriptive input from the user, in which case responding with a follow-up modal with text inputs might make the most sense.
+The specific response type should be picked based on the situation. Some commands may call for sending a message back to the channel where the command was invoked from, or perhaps just to the specific user who ran the command (for this, the [ephemeral message flag](/developers/docs/interactions/receiving-and-responding#interaction-response-object-messages) can be used). Other commands may necessitate descriptive input from the user, in which case responding with a follow-up modal with text inputs might make the most sense.
Regardless of the response, it should be picked based on the specific interaction the user is taking.
@@ -273,7 +275,7 @@ For a `/search` command that searches an external service, an app could respond
Ephemeral messages can also contain message components, so when relevant, there could be a button to share the information in the ephemeral message to a channel.
-
+
## Onboarding Users
@@ -287,15 +289,17 @@ As to where to communicate the changes, you can start with any communication cha
You can also inform users about changes within the servers your app is installed in as long as it’s done in a non-intrusive way. If your app has a dedicated channel in posts, that would be a good place.
-:::warn
+
+
Don’t DM all users in a server where your app is installed. It could get your app rate limited, but more importantly, it can be pretty intrusive and might lead to your app being uninstalled.
-:::
+
+
#### Example
The following is an example of an app update that may be sent to communicate the new way to access commands. Depending on the different features your app adopts (like options, subcommands, permissions, etc.), an update message or changelog entry will look very different.
-
+
### Making Help Available
@@ -307,6 +311,6 @@ This can come in the form of a specific command that shows app usage, a message
Hopefully this guide was helpful in considering how to design and implement application commands. Below is a couple of follow-up resources you can use:
-- [Application command documentation](/docs/interactions/application-commands)—I know it's linked a bunch in this guide, but there's a reason!
+- [Application command documentation](/developers/docs/interactions/application-commands)—I know it's linked a bunch in this guide, but there's a reason!
- Help center article on [message content intent workarounds](https://support-dev.discord.com/hc/en-us/articles/6383579033751-Message-Content-Intent-Alternatives-Workarounds)
- The [DDevs server](https://discord.gg/discord-developers) where you can find API updates, ask questions about developing apps, and connect with other developers
diff --git a/discord/developers/docs/tutorials/upgrading-to-application-commands.mdx b/discord/developers/docs/tutorials/upgrading-to-application-commands.mdx
new file mode 100644
index 0000000000..e62a1c13e6
--- /dev/null
+++ b/discord/developers/docs/tutorials/upgrading-to-application-commands.mdx
@@ -0,0 +1,312 @@
+---
+title: Upgrading Apps to Use Application Commands
+sidebarTitle: Upgrading to Application Commands
+description: Migration guide for upgrading from legacy text commands to application commands.
+---
+
+As [message content has become a privileged intent](https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-FAQ) for verified apps, [application commands](/developers/docs/interactions/application-commands) are the primary way Discord users interact with apps. The three types of commands (slash commands, user commands, and message commands) act as entry points into apps, and can be registered globally or for a subset of guilds.
+
+This guide is intended to provide developers with apps currently using message content with a resource to walk through implementing and designing commands. Throughout the guide, the terms "application commands" and "commands" are used interchangeably.
+
+
+
+
+If you are developing an app for the first time, the [commands documentation](/developers/docs/interactions/application-commands) may be a more helpful resource for you.
+
+
+Before diving in, it’s worth noting that with the message content changes, apps can still access message content in their DMs with users, as well as when messages are sent that directly `@mentions` their bot user (since there is clear user intent that the bot can read those messages).
+
+And for apps that use message content in ways that can’t be ported to commands, you should review the [message content intent review policy](https://support-dev.discord.com/hc/en-us/articles/5324827539479) to see if you’re eligible to apply for the privileged intent.
+
+---
+
+## Types of Commands
+
+There are three types of application commands: slash commands, user commands, and message commands. When building your app, whether migrating or starting from scratch, consider which type of command(s) makes sense for a given feature of your app.
+
+### Slash Commands
+
+[Slash commands](/developers/docs/interactions/application-commands#slash-commands) are the most common type of command. They are accessed by typing a forward slash (`/`) followed by the command’s name, or by using the plus button (+) to the left of the message input.
+
+Slash commands can appear in channels and DMs, so they’re helpful when an action is tied to a channel, a server, or nothing at all.
+
+### User Commands
+
+[User commands](/developers/docs/interactions/application-commands#user-commands) are in the context menu for users, which is accessed by right-clicking or tapping on any user. They’re helpful when an action is tied to an individual user, like a moderation app adding a timeout to someone.
+
+
+Within the context menus for users and messages, the `Apps` submenu will only appear if an app in that server has installed a corresponding command (whether or not an individual user can use the installed command).
+
+
+### Message Commands
+
+[Message commands](/developers/docs/interactions/application-commands#message-commands) are in the context menu for messages, which is accessed by right-clicking on a message, or by clicking on the ellipses at the top-right of a message. They’re helpful when an action is tied to a message, like creating a reminder to reply to a message the following day.
+
+### After This Section
+- Start thinking about how different app features might map to the different types of application commands.
+
+## Registering Commands
+
+Commands can be registered via HTTP requests after an app is authorized with the `applications.commands` scope. The `applications.commands` scope is also automatically included when an app requests the `bot` scope.
+
+
+There is a section on [designing commands](/developers/docs/tutorials/upgrading-to-application-commands#designing-for-commands) below implementation details that may be helpful as you start mapping out different commands
+
+
+The API endpoint to register (or create) commands is different depending on its scope:
+
+- **[Global commands](/developers/docs/interactions/application-commands#making-a-global-command)** are available in all of the servers where your app is installed, and can be created using the [`/applications/{YOUR APP ID}/commands` endpoint](/developers/docs/interactions/application-commands#create-global-application-command). All of your app's global commands will automatically be added to the servers your app is installed in, regardless of whether they were registered before or after installation.
+- **[Guild commands](/developers/docs/interactions/application-commands#making-a-guild-command)** are only available in the servers you explicitly add them to via the API, making them useful for features available only to a subset of guilds. They can be created using the [`/applications/{YOUR APP ID}/guilds/{A GUILD ID}/commands` endpoint](/developers/docs/interactions/application-commands#create-guild-application-command).
+
+While most apps won’t need to register more than a handful of commands, apps can have up to 100 global slash commands and 100 guild slash commands with unique names. They can also have 5 global user commands and 5 global message commands. Different limitations apply for global and guild commands, which can be found [in the documentation](/developers/docs/interactions/application-commands#registering-a-command).
+
+### Using Options as Parameters
+
+Command options is an optional field (`options`) that can be defined when creating commands. When used, options will display for the user to fill out during invocation. You can also provide dynamic option suggestions using the `autocomplete` field. Read more about options [in the documentation](/developers/docs/interactions/application-commands#application-command-object-application-command-option-structure).
+
+
+
+### Using Subcommands to Group Actions
+
+[Subcommands and subcommand groups](/developers/docs/interactions/application-commands#subcommands-and-subcommand-groups) help organize commands that are related to a shared resource or action. Instead of several top-level commands (like `/add-resource` and `/delete-resource`), you can have one top-level command with several subcommands (like `/resource add` and `/resource delete`).
+
+Subcommands use the same `options` field as passing parameters, but with a type of `2`.
+
+### Restricting Command Use
+
+[Application command permissions](/developers/docs/interactions/application-commands#permissions) allow users and apps to restrict command usage in a server. When commands are restricted for a user, they won't appear for them in the client.
+
+If your app currently relies on permissioning, using command permissions can be a way to port them. It also cleans up the command picker UI for users, making it easier for them to find your app’s commands that are most relevant to them.
+
+### Example Payload
+
+Below is a sample payload to create a global slash command with an optional parameter:
+
+```json
+{
+ "name": "rock",
+ "type": 1,
+ "description": "Sends a picture of a rock",
+ "options": [
+ {
+ "name": "type",
+ "description": "Type of rock",
+ "type": 3,
+ "required": True,
+ "choices": [
+ {
+ "name": "Igneous",
+ "value": "rock_igneous"
+ },
+ {
+ "name": "Sedimentary",
+ "value": "rock_sedimentary"
+ },
+ {
+ "name": "Metamorphic",
+ "value": "rock_metamorphic"
+ }
+ ]
+ }
+ ]
+ }
+```
+
+#### Default Permissions
+
+When [creating](/developers/docs/interactions/application-commands#create-global-application-command) or [updating](/developers/docs/interactions/application-commands#edit-global-application-command) a command, you can use the `default_member_permissions` field to restrict the command to a set of bitwise permissions that reflect the default permission flags a user must be granted in order to use the command.
+
+In addition, the `dm_permission` flag can be used to control whether a global command is available in DMs (not available for guild commands).
+
+#### Updating Permissions
+
+Permissions for specific roles, users, and channels can be updated by your app if you have the `applications.commands.permissions.update` scope and a [Bearer token](/developers/docs/topics/oauth2) that’s authenticated by a user with the necessary user permissions. Details about updating a command’s permissions are [in the documentation](/developers/docs/interactions/application-commands#permissions).
+
+### After This Section
+
+- Update your app to use the `applications.commands` scope
+- Decide whether each of your commands should be scoped globally (available to all servers) or to a guild (available to specific servers)
+- Decide what permissions your commands may need to run
+- Create your app’s commands using HTTP endpoints
+
+## Handling Commands
+
+Commands use the [interactions model](/developers/docs/interactions/receiving-and-responding) through HTTP-based outgoing webhooks or the WebSocket-based [Interaction Create gateway event](/developers/docs/events/gateway-events#interaction-create). Regardless of the transit method used to arrive, your app will receive relevant information when a Discord user triggers one of your app’s interactions.
+
+
+If you continue using Gateway events, you’ll still receive message events but the payloads will have empty string or array data for message content-related fields like `content`, `embeds`, `attachments`, and `components` while `poll` will be omitted. You can read more in the [message content intent](/developers/docs/events/gateway#message-content-intent) section.
+
+
+For commands, this means that each time one of your commands is used, your app will receive information like the command name and the user who triggered it. More information about this information is below in the section on [parsing command payloads](/developers/docs/tutorials/upgrading-to-application-commands#parsing-command-payloads).
+
+### Adding an Interactions Endpoint URL
+
+
+This step is specific to receiving interactions over HTTP. If you prefer to use the [Gateway](/developers/docs/events/gateway), this step won't be applicable to your app.
+
+
+Before your app can receive interactions, you’ll need to set up an **Interaction Endpoint URL** in your app settings. This endpoint should be a public URL where Discord can send all interactions-related requests.
+
+However, before adding your URL to your app settings, your endpoint must be set up to handle two things:
+
+1. **Responding to `PING` events**: When you save a URL in your settings, Discord will send a `POST` request with `type: 1`. To acknowledge this request (and thus verify your endpoint), you should return a `200` response with a payload containing `type: 1`. More information can be found in the [Receiving an Interaction documentation](/developers/docs/interactions/receiving-and-responding#receiving-an-interaction).
+2. **Verifying request signatures**: To ensure that requests are coming from Discord, your endpoint must verify each request using the included headers, specifically `X-Signature-Ed25519` and `X-Signature-Timestamp`. If the signature fails validating, your app should return a `401` response. More information and example code can be found in the [Security and Authorization documentation](/developers/docs/interactions/overview#setting-up-an-endpoint-validating-security-request-headers).
+
+
+Many libraries on the [Community Resources page](/developers/docs/developer-tools/community-resources#interactions) simplify verification and interaction request handling by exporting reusable functions and/or handling it automatically.
+
+
+After your URL is set up to handle signature verification and `PING` requests, you can add your Interaction Endpoint URL by navigating to your app settings from the [developer portal](https://discord.com/developers/applications). On the **General Information** page, you’ll see a field for your **Interactions Endpoint URL**.
+
+
+
+After you paste your URL and click **Save Changes**, Discord will attempt to verify your endpoint.
+
+If all goes well, your endpoint will successfully save. And if not, you should double check that your app is running with a public endpoint, is verifying request signatures, and is properly responding to `PING` requests.
+
+### Parsing Command Payloads
+
+Once your app has a verified endpoint, you should start being able to receive command requests from Discord.
+
+As mentioned above, these include information relevant to handling the command like its name, the user who invoked it, and the guild and channel it was invoked from. It also includes additional details that could be relevant, like the [command options](/developers/docs/interactions/application-commands#application-command-object-application-command-option-structure) or [locale information](/developers/docs/interactions/application-commands#localization).
+
+Since slash commands (`CHAT_INPUT` commands) are run in the context of a channel, you’ll notice that their payloads don’t contain any information about specific messages. If your app needs the message content, you can use [message commands](/developers/docs/interactions/application-commands#message-commands) which *do* include the message content.
+
+
+In the getting started guide’s repository, there’s a code sample showing [how to create and handle commands using JavaScript](https://github.com/discord/discord-example-app/blob/main/examples/command.js).
+
+
+Below is an example payload your app would receive when a user invoked a global command with an option:
+
+```json
+{
+ "type": 2,
+ "token": "A_UNIQUE_TOKEN",
+ "member": {
+ "user": {
+ "id": "A_USER_ID",
+ "username": "A_USERNAME",
+ "avatar": "GUILD_AVATAR_HASH",
+ "discriminator": "1337",
+ "public_flags": 131141
+ },
+ "roles": ["12345678"],
+ "premium_since": null,
+ "permissions": "2147483647",
+ "pending": false,
+ "nick": null,
+ "mute": false,
+ "joined_at": "2019-04-14T12:14:14.000000+00:00",
+ "is_pending": false,
+ "deaf": false
+ },
+ "id": "INTERACTION_ID",
+ "application_id": "YOUR_APP_ID",
+ "app_permissions": "442368",
+ "guild_id": "A_GUILD_ID",
+ "guild_locale": "en-US",
+ "locale": "en-US",
+ "data": {
+ "options": [{
+ "name": "Igneous",
+ "value": "rock_igneous"
+ }],
+ "name": "rock",
+ "id": "APPLICATION_COMMAND_ID"
+ },
+ "channel_id": "ASSOCIATED_CHANNEL_ID"
+}
+```
+
+To determine how your app should handle an incoming command-related interaction, you can look in the `data` object which contains all of the command-specific information (including any options a user selected). Details about the full interactions object your app receives can be found in the [Interactions documentation](/developers/docs/interactions/receiving-and-responding#interaction-object).
+
+### After This Section
+
+- Setup a public endpoint for your app that verifies request signatures and responds to `PING` events
+- Add your endpoint to your app settings under Interactions Endpoint URL
+- Modify your code (or write new code) to handle the different commands you registered earlier
+
+## Designing for Commands
+
+Adding commands to your app can add discoverability and interactivity for users. While porting your app’s features, it’s worth considering how your app will be seen and used inside of the client. This section includes a handful of areas to consider when designing your app’s commands, and what happens after they’re invoked.
+
+
+CLIs (Command Line Interfaces) can be a helpful analogy when designing Discord commands, their options and subcommands, and how it all fits together into one experience. A good resource for this can be the open source [Command Interface Guidelines](https://clig.dev/).
+
+
+### Choosing a Name
+
+When creating a command, keep the name short and relevant. The name of the command should give users an idea of the action they’re invoking. A description can be a bit more verbose, leaving room to be more explicit about the action and its result.
+
+And when your app has several commands (and perhaps [subcommands](/developers/docs/interactions/application-commands#subcommands-and-subcommand-groups)), it’s important to keep the naming scheme consistent.
+
+#### Examples
+
+- You should use a descriptive name like `/stats` rather than a vague name like `/get` for a command that displays stats to a user.
+- You should use shorter name like `/poll` rather than a verbose name like `/create-new-poll` for a command that creates a new poll. If there are many actions to take related to `/poll`, it might be more intuitive to use a `create` subcommand.
+
+### Collecting User Input
+
+When commands need a bit of input from a user, you can use the `options` field. Command options can be thought of as parameters to your command. They can be one of many [types](/developers/docs/interactions/application-commands#application-command-object-application-command-option-type), like the standard string or number, or the more Discord-specific role, user, and channel.
+
+Options are great for short input, but if you need user input that’s longer than a couple of words, like a title or description, you can collect form-like input using [modals](/developers/docs/interactions/receiving-and-responding#interaction-response-object-modal) as a response to the command invocation.
+
+### Scoping a Command
+
+Commands can optionally be [scoped to specific guilds](/developers/docs/interactions/application-commands#create-guild-application-command), rather than available everywhere your app is installed. Guild commands can be useful when your app has functionality that may not be relevant to all servers like:
+
+- When a command is in development
+- When a specific command is opt-in or opt-out
+- When specific commands are behind a paywall
+
+### Responding to a Command
+
+Interactions (including commands) can have a hand-picked reply using one of the many available [interaction responses](/developers/docs/interactions/receiving-and-responding#responding-to-an-interaction).
+
+The specific response type should be picked based on the situation. Some commands may call for sending a message back to the channel where the command was invoked from, or perhaps just to the specific user who ran the command (for this, the [ephemeral message flag](/developers/docs/interactions/receiving-and-responding#interaction-response-object-messages) can be used). Other commands may necessitate descriptive input from the user, in which case responding with a follow-up modal with text inputs might make the most sense.
+
+Regardless of the response, it should be picked based on the specific interaction the user is taking.
+
+#### Example
+
+For a `/search` command that searches an external service, an app could respond with an ephemeral message rather than posting back into the channel where users may not have context or want messages cluttering the channel.
+
+Ephemeral messages can also contain message components, so when relevant, there could be a button to share the information in the ephemeral message to a channel.
+
+
+
+## Onboarding Users
+
+Once you’ve implemented slash commands (or really any feature for your app), it can be helpful to onboard existing and new users. While every app on Discord is unique, this section tries to generalize some good onboarding strategies, specifically to send updates to existing users.
+
+### Communicating App Updates to Users
+
+When you add new features or make major changes to your app, communicate what they are and how it specifically affects them. What do they need to do differently? What improves? What won’t they be able to do anymore?
+
+As to where to communicate the changes, you can start with any communication channels you own—a support server, blog, or social media account for example.
+
+You can also inform users about changes within the servers your app is installed in as long as it’s done in a non-intrusive way. If your app has a dedicated channel in posts, that would be a good place.
+
+
+Don’t DM all users in a server where your app is installed. It could get your app rate limited, but more importantly, it can be pretty intrusive and might lead to your app being uninstalled.
+
+
+#### Example
+
+The following is an example of an app update that may be sent to communicate the new way to access commands. Depending on the different features your app adopts (like options, subcommands, permissions, etc.), an update message or changelog entry will look very different.
+
+
+
+### Making Help Available
+
+Both new and existing users should always have ways for them to easily find usage instructions and support. Some of this help can come in the form of a support server or website, but you should also have instructions in the client.
+
+This can come in the form of a specific command that shows app usage, a message when someone `@mentions` your bot user, reactively when someone misuses one of your app’s commands, or ideally all of the above.
+
+## Further Resources
+
+Hopefully this guide was helpful in considering how to design and implement application commands. Below is a couple of follow-up resources you can use:
+
+- [Application command documentation](/developers/docs/interactions/application-commands)—I know it's linked a bunch in this guide, but there's a reason!
+- Help center article on [message content intent workarounds](https://support-dev.discord.com/hc/en-us/articles/6383579033751-Message-Content-Intent-Alternatives-Workarounds)
+- The [DDevs server](https://discord.gg/discord-developers) where you can find API updates, ask questions about developing apps, and connect with other developers
diff --git a/discord/docs.json b/discord/docs.json
new file mode 100644
index 0000000000..6397fe44ec
--- /dev/null
+++ b/discord/docs.json
@@ -0,0 +1,342 @@
+{
+ "$schema": "https://mintlify.com/docs.json",
+ "theme": "mint",
+ "name": "Documentation - Discord",
+ "colors": {
+ "primary": "#5865F2",
+ "light": "#5865F2",
+ "dark": "#5865F2"
+ },
+ "appearance": {
+ "default": "dark"
+ },
+ "styling": {
+ "codeblocks": "system",
+ "eyebrows": "breadcrumbs"
+ },
+ "favicon": "/favicon.png",
+ "errors": {
+ "404": {
+ "redirect": false
+ }
+ },
+ "interaction": {
+ "drilldown": false
+ },
+ "contextual": {
+ "options": [
+ "copy",
+ "view",
+ "chatgpt",
+ "claude",
+ "perplexity"
+ ]
+ },
+ "navigation": {
+ "tabs": [
+ {
+ "tab": "Documentation",
+ "groups": [
+ {
+ "group": "Home",
+ "pages": [
+ "developers/docs/intro",
+ "developers/docs/reference"
+ ]
+ },
+ {
+ "group": "Quick Start",
+ "pages": [
+ "developers/docs/quick-start/overview-of-apps",
+ "developers/docs/quick-start/getting-started"
+ ]
+ },
+ {
+ "group": "Interactions",
+ "pages": [
+ "developers/docs/interactions/overview",
+ "developers/docs/interactions/receiving-and-responding",
+ "developers/docs/interactions/application-commands"
+ ]
+ },
+ {
+ "group": "Components",
+ "pages": [
+ "developers/docs/components/overview",
+ "developers/docs/components/using-message-components",
+ "developers/docs/components/using-modal-components",
+ "developers/docs/components/reference"
+ ]
+ },
+ {
+ "group": "Activities",
+ "pages": [
+ "developers/docs/activities/overview",
+ "developers/docs/activities/how-activities-work",
+ "developers/docs/activities/building-an-activity",
+ {
+ "group": "Development Guides",
+ "pages": [
+ "developers/docs/activities/development-guides",
+ "developers/docs/activities/development-guides/local-development",
+ "developers/docs/activities/development-guides/user-actions",
+ "developers/docs/activities/development-guides/mobile",
+ "developers/docs/activities/development-guides/layout",
+ "developers/docs/activities/development-guides/networking",
+ "developers/docs/activities/development-guides/multiplayer-experience",
+ "developers/docs/activities/development-guides/growth-and-referrals",
+ "developers/docs/activities/development-guides/assets-and-metadata",
+ "developers/docs/activities/development-guides/production-readiness"
+ ]
+ },
+ "developers/docs/activities/design-patterns"
+ ]
+ },
+ {
+ "group": "Discord Social SDK",
+ "pages": [
+ "developers/docs/discord-social-sdk/overview",
+ {
+ "group": "Core Concepts",
+ "pages": [
+ "developers/docs/discord-social-sdk/core-concepts",
+ "developers/docs/discord-social-sdk/core-concepts/core-features",
+ "developers/docs/discord-social-sdk/core-concepts/communication-features",
+ "developers/docs/discord-social-sdk/core-concepts/integration-overview",
+ "developers/docs/discord-social-sdk/core-concepts/platform-compatibility",
+ "developers/docs/discord-social-sdk/core-concepts/oauth2-scopes"
+ ]
+ },
+ {
+ "group": "Getting Started",
+ "pages": [
+ "developers/docs/discord-social-sdk/getting-started",
+ "developers/docs/discord-social-sdk/getting-started/using-c++",
+ "developers/docs/discord-social-sdk/getting-started/using-unity",
+ "developers/docs/discord-social-sdk/getting-started/using-unreal-engine"
+ ]
+ },
+ {
+ "group": "Development Guides",
+ "pages": [
+ "developers/docs/discord-social-sdk/development-guides",
+ "developers/docs/discord-social-sdk/development-guides/account-linking-with-discord",
+ "developers/docs/discord-social-sdk/development-guides/account-linking-on-consoles",
+ "developers/docs/discord-social-sdk/development-guides/using-provisional-accounts",
+ "developers/docs/discord-social-sdk/development-guides/creating-a-unified-friends-list",
+ "developers/docs/discord-social-sdk/development-guides/managing-relationships",
+ "developers/docs/discord-social-sdk/development-guides/setting-rich-presence",
+ "developers/docs/discord-social-sdk/development-guides/managing-game-invites",
+ "developers/docs/discord-social-sdk/development-guides/sending-direct-messages",
+ "developers/docs/discord-social-sdk/development-guides/managing-lobbies",
+ "developers/docs/discord-social-sdk/development-guides/linked-channels",
+ "developers/docs/discord-social-sdk/development-guides/managing-voice-chat"
+ ]
+ },
+ {
+ "group": "Design Guidelines",
+ "pages": [
+ "developers/docs/discord-social-sdk/design-guidelines",
+ "developers/docs/discord-social-sdk/design-guidelines/principles",
+ "developers/docs/discord-social-sdk/design-guidelines/signing-in",
+ "developers/docs/discord-social-sdk/design-guidelines/connection-points",
+ "developers/docs/discord-social-sdk/design-guidelines/branding-guidelines",
+ "developers/docs/discord-social-sdk/design-guidelines/unified-friends-list",
+ "developers/docs/discord-social-sdk/design-guidelines/direct-messages",
+ "developers/docs/discord-social-sdk/design-guidelines/chat-history",
+ "developers/docs/discord-social-sdk/design-guidelines/social-settings",
+ "developers/docs/discord-social-sdk/design-guidelines/provisional-accounts",
+ "developers/docs/discord-social-sdk/design-guidelines/status-rich-presence",
+ "developers/docs/discord-social-sdk/design-guidelines/consoles",
+ "developers/docs/discord-social-sdk/design-guidelines/game-friends",
+ "developers/docs/discord-social-sdk/design-guidelines/linked-channels"
+ ]
+ },
+ {
+ "group": "How To",
+ "pages": [
+ "developers/docs/discord-social-sdk/how-to",
+ "developers/docs/discord-social-sdk/how-to/debug-log",
+ "developers/docs/discord-social-sdk/how-to/use-with-discord-apis",
+ "developers/docs/discord-social-sdk/how-to/integrate-moderation",
+ "developers/docs/discord-social-sdk/how-to/market-your-integration",
+ "developers/docs/discord-social-sdk/how-to/handle-special-characters-display-names"
+ ]
+ },
+ "developers/docs/discord-social-sdk/social-sdk-reference"
+ ]
+ },
+ {
+ "group": "Rich Presence",
+ "pages": [
+ "developers/docs/rich-presence/overview",
+ "developers/docs/rich-presence/using-with-the-embedded-app-sdk",
+ "developers/docs/rich-presence/using-with-the-discord-social-sdk",
+ "developers/docs/rich-presence/using-with-the-game-sdk",
+ "developers/docs/rich-presence/best-practices"
+ ]
+ },
+ {
+ "group": "Monetization",
+ "pages": [
+ "developers/docs/monetization/overview",
+ "developers/docs/monetization/enabling-monetization",
+ "developers/docs/monetization/managing-skus",
+ "developers/docs/monetization/implementing-app-subscriptions",
+ "developers/docs/monetization/implementing-one-time-purchases",
+ "developers/docs/monetization/implementing-iap-for-activities"
+ ]
+ },
+ {
+ "group": "Discovery",
+ "pages": [
+ "developers/docs/discovery/overview",
+ "developers/docs/discovery/enabling-discovery",
+ "developers/docs/discovery/best-practices"
+ ]
+ },
+ {
+ "group": "Events",
+ "pages": [
+ "developers/docs/events/overview",
+ "developers/docs/events/gateway",
+ "developers/docs/events/gateway-events",
+ "developers/docs/events/webhook-events"
+ ]
+ },
+ {
+ "group": "Developer Tools",
+ "pages": [
+ "developers/docs/developer-tools/embedded-app-sdk",
+ "developers/docs/developer-tools/community-resources",
+ "developers/docs/developer-tools/game-sdk"
+ ]
+ },
+ {
+ "group": "Resources",
+ "pages": [
+ "developers/docs/resources/application-role-connection-metadata",
+ "developers/docs/resources/application",
+ "developers/docs/resources/audit-log",
+ "developers/docs/resources/auto-moderation",
+ "developers/docs/resources/channel",
+ "developers/docs/resources/emoji",
+ "developers/docs/resources/entitlement",
+ "developers/docs/resources/guild",
+ "developers/docs/resources/guild-scheduled-event",
+ "developers/docs/resources/guild-template",
+ "developers/docs/resources/invite",
+ "developers/docs/resources/lobby",
+ "developers/docs/resources/message",
+ "developers/docs/resources/poll",
+ "developers/docs/resources/sku",
+ "developers/docs/resources/soundboard",
+ "developers/docs/resources/stage-instance",
+ "developers/docs/resources/sticker",
+ "developers/docs/resources/subscription",
+ "developers/docs/resources/user",
+ "developers/docs/resources/voice",
+ "developers/docs/resources/webhook"
+ ]
+ },
+ {
+ "group": "Topics",
+ "pages": [
+ "developers/docs/topics/certified-devices",
+ "developers/docs/topics/oauth2",
+ "developers/docs/topics/opcodes-and-status-codes",
+ "developers/docs/topics/permissions",
+ "developers/docs/topics/rate-limits",
+ "developers/docs/topics/rpc",
+ "developers/docs/topics/teams",
+ "developers/docs/topics/threads",
+ "developers/docs/topics/voice-connections"
+ ]
+ },
+ {
+ "group": "Tutorials",
+ "pages": [
+ "developers/docs/tutorials/configuring-app-metadata-for-linked-roles",
+ "developers/docs/tutorials/developing-a-user-installable-app",
+ "developers/docs/tutorials/hosting-on-cloudflare-workers",
+ "developers/docs/tutorials/upgrading-to-application-commands"
+ ]
+ },
+ {
+ "group": "Policies and Agreements",
+ "pages": [
+ "developers/docs/policies/developer-policy",
+ "developers/docs/policies/developer-terms-of-service"
+ ]
+ }
+ ]
+ },
+ {
+ "tab": "Change Log",
+ "pages": [
+ "developers/docs/change-log"
+ ]
+ }
+ ]
+ },
+ "redirects": [
+ {
+ "source": "/developers/docs",
+ "destination": "/developers/docs/intro"
+ },
+ {
+ "source": "/developers/docs/",
+ "destination": "/developers/docs/intro"
+ },
+ {
+ "source": "/developers/docs/index",
+ "destination": "/developers/docs/intro"
+ }
+ ],
+ "logo": {
+ "light": "/logo/light.svg",
+ "dark": "/logo/dark.svg",
+ "href": "https://discord.com/developers/docs/"
+ },
+ "background": {
+ "color": {
+ "light": "#ffffff",
+ "dark": "#36373e"
+ }
+ },
+ "api": {
+ "playground": {
+ "display": "simple"
+ }
+ },
+ "navbar": {
+ "links": [
+ {
+ "label": "Help Center",
+ "href": "https://support-dev.discord.com/hc/en-us"
+ }
+ ],
+ "primary": {
+ "type": "button",
+ "label": "Developer Portal",
+ "href": "https://discord.com/developers/applications"
+ }
+ },
+ "footer": {
+ "socials": {
+ "github": "https://github.com/discord/discord-api-docs",
+ "discord": "https://discord.gg/discord-developers",
+ "youtube": "https://www.youtube.com/@DiscordDevelopers",
+ "linkedin": "https://www.linkedin.com/showcase/discord-developers"
+ }
+ },
+ "banner" : {
+ "content": "New docs? Check out the [change log](/developers/docs/change-log#next-generation-docs-project) to learn more!",
+ "dismissible": true
+ },
+ "integrations": {
+ "gtm": {
+ "tagId": "G-5CWMJQ1S0X"
+ }
+ }
+}
\ No newline at end of file
diff --git a/discord/favicon.png b/discord/favicon.png
new file mode 100644
index 0000000000..e813e10b9c
Binary files /dev/null and b/discord/favicon.png differ
diff --git a/static/images/1.4vs1.5.webp b/discord/images/1.4vs1.5.webp
similarity index 100%
rename from static/images/1.4vs1.5.webp
rename to discord/images/1.4vs1.5.webp
diff --git a/static/images/activities-presence-example.png b/discord/images/activities-presence-example.png
similarity index 100%
rename from static/images/activities-presence-example.png
rename to discord/images/activities-presence-example.png
diff --git a/discord/images/activities/activities-hero.png b/discord/images/activities/activities-hero.png
new file mode 100644
index 0000000000..56c65a8a0f
Binary files /dev/null and b/discord/images/activities/activities-hero.png differ
diff --git a/discord/images/activities/activity-instance-validation.jpg b/discord/images/activities/activity-instance-validation.jpg
new file mode 100644
index 0000000000..3857dbc42e
Binary files /dev/null and b/discord/images/activities/activity-instance-validation.jpg differ
diff --git a/discord/images/activities/application-test-mode-prod.gif b/discord/images/activities/application-test-mode-prod.gif
new file mode 100644
index 0000000000..ee66fe8963
Binary files /dev/null and b/discord/images/activities/application-test-mode-prod.gif differ
diff --git a/discord/images/activities/bobble-bash.png b/discord/images/activities/bobble-bash.png
new file mode 100644
index 0000000000..989916990c
Binary files /dev/null and b/discord/images/activities/bobble-bash.png differ
diff --git a/discord/images/activities/bobble-league.png b/discord/images/activities/bobble-league.png
new file mode 100644
index 0000000000..51e1f240df
Binary files /dev/null and b/discord/images/activities/bobble-league.png differ
diff --git a/discord/images/activities/chess-victory.png b/discord/images/activities/chess-victory.png
new file mode 100644
index 0000000000..5fcae0d705
Binary files /dev/null and b/discord/images/activities/chess-victory.png differ
diff --git a/discord/images/activities/custom-link-embed.png b/discord/images/activities/custom-link-embed.png
new file mode 100644
index 0000000000..ebc0183d6c
Binary files /dev/null and b/discord/images/activities/custom-link-embed.png differ
diff --git a/discord/images/activities/debug-logs-filtering.gif b/discord/images/activities/debug-logs-filtering.gif
new file mode 100644
index 0000000000..ce8d6429f9
Binary files /dev/null and b/discord/images/activities/debug-logs-filtering.gif differ
diff --git a/discord/images/activities/default_orientation_lock_state.png b/discord/images/activities/default_orientation_lock_state.png
new file mode 100644
index 0000000000..201ae8990a
Binary files /dev/null and b/discord/images/activities/default_orientation_lock_state.png differ
diff --git a/discord/images/activities/eights.png b/discord/images/activities/eights.png
new file mode 100644
index 0000000000..eab453f914
Binary files /dev/null and b/discord/images/activities/eights.png differ
diff --git a/static/images/activities/embedded-app-flow-diagram.svg b/discord/images/activities/embedded-app-flow-diagram.svg
similarity index 100%
rename from static/images/activities/embedded-app-flow-diagram.svg
rename to discord/images/activities/embedded-app-flow-diagram.svg
diff --git a/discord/images/activities/enable-activities.png b/discord/images/activities/enable-activities.png
new file mode 100644
index 0000000000..8fde7e3105
Binary files /dev/null and b/discord/images/activities/enable-activities.png differ
diff --git a/discord/images/activities/encourage-hardware-acceleration-modal.png b/discord/images/activities/encourage-hardware-acceleration-modal.png
new file mode 100644
index 0000000000..85c51fab28
Binary files /dev/null and b/discord/images/activities/encourage-hardware-acceleration-modal.png differ
diff --git a/discord/images/activities/external-link-modal.png b/discord/images/activities/external-link-modal.png
new file mode 100644
index 0000000000..1465b9d56d
Binary files /dev/null and b/discord/images/activities/external-link-modal.png differ
diff --git a/discord/images/activities/invite-dialog.png b/discord/images/activities/invite-dialog.png
new file mode 100644
index 0000000000..d3bf2abe32
Binary files /dev/null and b/discord/images/activities/invite-dialog.png differ
diff --git a/discord/images/activities/join-application.png b/discord/images/activities/join-application.png
new file mode 100644
index 0000000000..c336d4cef9
Binary files /dev/null and b/discord/images/activities/join-application.png differ
diff --git a/discord/images/activities/oauth-flow-diagram.svg b/discord/images/activities/oauth-flow-diagram.svg
new file mode 100644
index 0000000000..6ce500a5a3
--- /dev/null
+++ b/discord/images/activities/oauth-flow-diagram.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/discord/images/activities/oauth2-redirect.png b/discord/images/activities/oauth2-redirect.png
new file mode 100644
index 0000000000..c095c12023
Binary files /dev/null and b/discord/images/activities/oauth2-redirect.png differ
diff --git a/discord/images/activities/share-moment-dialog-example.png b/discord/images/activities/share-moment-dialog-example.png
new file mode 100644
index 0000000000..5ba1121471
Binary files /dev/null and b/discord/images/activities/share-moment-dialog-example.png differ
diff --git a/discord/images/activities/start-activity.png b/discord/images/activities/start-activity.png
new file mode 100644
index 0000000000..2706616a69
Binary files /dev/null and b/discord/images/activities/start-activity.png differ
diff --git a/discord/images/activities/supported-platforms.png b/discord/images/activities/supported-platforms.png
new file mode 100644
index 0000000000..71f6add725
Binary files /dev/null and b/discord/images/activities/supported-platforms.png differ
diff --git a/discord/images/activities/tutorial-auth.png b/discord/images/activities/tutorial-auth.png
new file mode 100644
index 0000000000..d70edcae49
Binary files /dev/null and b/discord/images/activities/tutorial-auth.png differ
diff --git a/discord/images/activities/tutorial-channel-name.png b/discord/images/activities/tutorial-channel-name.png
new file mode 100644
index 0000000000..c2b6a947fe
Binary files /dev/null and b/discord/images/activities/tutorial-channel-name.png differ
diff --git a/discord/images/activities/tutorial-hero.png b/discord/images/activities/tutorial-hero.png
new file mode 100644
index 0000000000..04f72676b2
Binary files /dev/null and b/discord/images/activities/tutorial-hero.png differ
diff --git a/discord/images/activities/url-mapping-do.png b/discord/images/activities/url-mapping-do.png
new file mode 100644
index 0000000000..e5e0ef26a5
Binary files /dev/null and b/discord/images/activities/url-mapping-do.png differ
diff --git a/discord/images/activities/url-mapping-dont.png b/discord/images/activities/url-mapping-dont.png
new file mode 100644
index 0000000000..806aefd7f1
Binary files /dev/null and b/discord/images/activities/url-mapping-dont.png differ
diff --git a/discord/images/activities/url-mapping-tutorial.png b/discord/images/activities/url-mapping-tutorial.png
new file mode 100644
index 0000000000..878a21c9c7
Binary files /dev/null and b/discord/images/activities/url-mapping-tutorial.png differ
diff --git a/static/images/alerts.webp b/discord/images/alerts.webp
similarity index 100%
rename from static/images/alerts.webp
rename to discord/images/alerts.webp
diff --git a/static/images/annotated-presence-data-activities.png b/discord/images/annotated-presence-data-activities.png
similarity index 100%
rename from static/images/annotated-presence-data-activities.png
rename to discord/images/annotated-presence-data-activities.png
diff --git a/static/images/botuser-profile.webp b/discord/images/botuser-profile.webp
similarity index 100%
rename from static/images/botuser-profile.webp
rename to discord/images/botuser-profile.webp
diff --git a/static/images/bp-productpage-app-description.webp b/discord/images/bp-productpage-app-description.webp
similarity index 100%
rename from static/images/bp-productpage-app-description.webp
rename to discord/images/bp-productpage-app-description.webp
diff --git a/static/images/bp-productpage-summary-bad.webp b/discord/images/bp-productpage-summary-bad.webp
similarity index 100%
rename from static/images/bp-productpage-summary-bad.webp
rename to discord/images/bp-productpage-summary-bad.webp
diff --git a/static/images/bp-productpage-summary-good.webp b/discord/images/bp-productpage-summary-good.webp
similarity index 100%
rename from static/images/bp-productpage-summary-good.webp
rename to discord/images/bp-productpage-summary-good.webp
diff --git a/static/images/bp-productpage-tags.webp b/discord/images/bp-productpage-tags.webp
similarity index 100%
rename from static/images/bp-productpage-tags.webp
rename to discord/images/bp-productpage-tags.webp
diff --git a/discord/images/certified-device.png b/discord/images/certified-device.png
new file mode 100644
index 0000000000..b3eb266027
Binary files /dev/null and b/discord/images/certified-device.png differ
diff --git a/static/images/certified-device.webp b/discord/images/certified-device.webp
similarity index 100%
rename from static/images/certified-device.webp
rename to discord/images/certified-device.webp
diff --git a/static/images/cloudflare-general-overview.webp b/discord/images/cloudflare-general-overview.webp
similarity index 100%
rename from static/images/cloudflare-general-overview.webp
rename to discord/images/cloudflare-general-overview.webp
diff --git a/static/images/cloudflare-interactions-endpoint.webp b/discord/images/cloudflare-interactions-endpoint.webp
similarity index 100%
rename from static/images/cloudflare-interactions-endpoint.webp
rename to discord/images/cloudflare-interactions-endpoint.webp
diff --git a/static/images/cloudflare-ngrok.webp b/discord/images/cloudflare-ngrok.webp
similarity index 100%
rename from static/images/cloudflare-ngrok.webp
rename to discord/images/cloudflare-ngrok.webp
diff --git a/static/images/cloudflare-tutorial-demo.webp b/discord/images/cloudflare-tutorial-demo.webp
similarity index 100%
rename from static/images/cloudflare-tutorial-demo.webp
rename to discord/images/cloudflare-tutorial-demo.webp
diff --git a/static/images/cloudflare-url-generator.webp b/discord/images/cloudflare-url-generator.webp
similarity index 100%
rename from static/images/cloudflare-url-generator.webp
rename to discord/images/cloudflare-url-generator.webp
diff --git a/discord/images/command-entry-point.png b/discord/images/command-entry-point.png
new file mode 100644
index 0000000000..eb359e0560
Binary files /dev/null and b/discord/images/command-entry-point.png differ
diff --git a/static/images/command-entry-point.webp b/discord/images/command-entry-point.webp
similarity index 100%
rename from static/images/command-entry-point.webp
rename to discord/images/command-entry-point.webp
diff --git a/discord/images/command-types.png b/discord/images/command-types.png
new file mode 100644
index 0000000000..1497c807f6
Binary files /dev/null and b/discord/images/command-types.png differ
diff --git a/static/images/command-types.webp b/discord/images/command-types.webp
similarity index 100%
rename from static/images/command-types.webp
rename to discord/images/command-types.webp
diff --git a/discord/images/command-with-groups-subcommands-parameters.png b/discord/images/command-with-groups-subcommands-parameters.png
new file mode 100644
index 0000000000..9c35a81e3d
Binary files /dev/null and b/discord/images/command-with-groups-subcommands-parameters.png differ
diff --git a/static/images/command-with-groups-subcommands-parameters.webp b/discord/images/command-with-groups-subcommands-parameters.webp
similarity index 100%
rename from static/images/command-with-groups-subcommands-parameters.webp
rename to discord/images/command-with-groups-subcommands-parameters.webp
diff --git a/discord/images/command-with-groups-subcommands.png b/discord/images/command-with-groups-subcommands.png
new file mode 100644
index 0000000000..af77d45b2b
Binary files /dev/null and b/discord/images/command-with-groups-subcommands.png differ
diff --git a/static/images/command-with-groups-subcommands.webp b/discord/images/command-with-groups-subcommands.webp
similarity index 100%
rename from static/images/command-with-groups-subcommands.webp
rename to discord/images/command-with-groups-subcommands.webp
diff --git a/discord/images/command.png b/discord/images/command.png
new file mode 100644
index 0000000000..cc0c23e7c6
Binary files /dev/null and b/discord/images/command.png differ
diff --git a/static/images/command.webp b/discord/images/command.webp
similarity index 100%
rename from static/images/command.webp
rename to discord/images/command.webp
diff --git a/discord/images/components/action-row.png b/discord/images/components/action-row.png
new file mode 100644
index 0000000000..376bf28294
Binary files /dev/null and b/discord/images/components/action-row.png differ
diff --git a/static/images/components/action-row.webp b/discord/images/components/action-row.webp
similarity index 100%
rename from static/images/components/action-row.webp
rename to discord/images/components/action-row.webp
diff --git a/discord/images/components/channel-select.png b/discord/images/components/channel-select.png
new file mode 100644
index 0000000000..ab89bda496
Binary files /dev/null and b/discord/images/components/channel-select.png differ
diff --git a/static/images/components/channel-select.webp b/discord/images/components/channel-select.webp
similarity index 100%
rename from static/images/components/channel-select.webp
rename to discord/images/components/channel-select.webp
diff --git a/discord/images/components/container.png b/discord/images/components/container.png
new file mode 100644
index 0000000000..68c71c2e58
Binary files /dev/null and b/discord/images/components/container.png differ
diff --git a/static/images/components/container.webp b/discord/images/components/container.webp
similarity index 100%
rename from static/images/components/container.webp
rename to discord/images/components/container.webp
diff --git a/static/images/components/file-upload-modal-example.webp b/discord/images/components/file-upload-modal-example.webp
similarity index 100%
rename from static/images/components/file-upload-modal-example.webp
rename to discord/images/components/file-upload-modal-example.webp
diff --git a/discord/images/components/file.png b/discord/images/components/file.png
new file mode 100644
index 0000000000..28076faa40
Binary files /dev/null and b/discord/images/components/file.png differ
diff --git a/static/images/components/file.webp b/discord/images/components/file.webp
similarity index 100%
rename from static/images/components/file.webp
rename to discord/images/components/file.webp
diff --git a/discord/images/components/hero.png b/discord/images/components/hero.png
new file mode 100644
index 0000000000..5245070138
Binary files /dev/null and b/discord/images/components/hero.png differ
diff --git a/static/images/components/hero.webp b/discord/images/components/hero.webp
similarity index 100%
rename from static/images/components/hero.webp
rename to discord/images/components/hero.webp
diff --git a/discord/images/components/media-gallery.png b/discord/images/components/media-gallery.png
new file mode 100644
index 0000000000..6b567864e3
Binary files /dev/null and b/discord/images/components/media-gallery.png differ
diff --git a/static/images/components/media-gallery.webp b/discord/images/components/media-gallery.webp
similarity index 100%
rename from static/images/components/media-gallery.webp
rename to discord/images/components/media-gallery.webp
diff --git a/discord/images/components/mentionable-select.png b/discord/images/components/mentionable-select.png
new file mode 100644
index 0000000000..07c29c7baf
Binary files /dev/null and b/discord/images/components/mentionable-select.png differ
diff --git a/static/images/components/mentionable-select.webp b/discord/images/components/mentionable-select.webp
similarity index 100%
rename from static/images/components/mentionable-select.webp
rename to discord/images/components/mentionable-select.webp
diff --git a/static/images/components/modal-channel-select.webp b/discord/images/components/modal-channel-select.webp
similarity index 100%
rename from static/images/components/modal-channel-select.webp
rename to discord/images/components/modal-channel-select.webp
diff --git a/discord/images/components/modal-desktop.png b/discord/images/components/modal-desktop.png
new file mode 100644
index 0000000000..0f94dabdf4
Binary files /dev/null and b/discord/images/components/modal-desktop.png differ
diff --git a/static/images/components/modal-label.webp b/discord/images/components/modal-label.webp
similarity index 100%
rename from static/images/components/modal-label.webp
rename to discord/images/components/modal-label.webp
diff --git a/static/images/components/modal-mentionable-select.webp b/discord/images/components/modal-mentionable-select.webp
similarity index 100%
rename from static/images/components/modal-mentionable-select.webp
rename to discord/images/components/modal-mentionable-select.webp
diff --git a/static/images/components/modal-role-select.webp b/discord/images/components/modal-role-select.webp
similarity index 100%
rename from static/images/components/modal-role-select.webp
rename to discord/images/components/modal-role-select.webp
diff --git a/static/images/components/modal-string-select.webp b/discord/images/components/modal-string-select.webp
similarity index 100%
rename from static/images/components/modal-string-select.webp
rename to discord/images/components/modal-string-select.webp
diff --git a/static/images/components/modal-text-display.webp b/discord/images/components/modal-text-display.webp
similarity index 100%
rename from static/images/components/modal-text-display.webp
rename to discord/images/components/modal-text-display.webp
diff --git a/static/images/components/modal-user-select.webp b/discord/images/components/modal-user-select.webp
similarity index 100%
rename from static/images/components/modal-user-select.webp
rename to discord/images/components/modal-user-select.webp
diff --git a/discord/images/components/modal.png b/discord/images/components/modal.png
new file mode 100644
index 0000000000..765426ee09
Binary files /dev/null and b/discord/images/components/modal.png differ
diff --git a/static/images/components/modal.webp b/discord/images/components/modal.webp
similarity index 100%
rename from static/images/components/modal.webp
rename to discord/images/components/modal.webp
diff --git a/discord/images/components/multiple-buttons-example-1.png b/discord/images/components/multiple-buttons-example-1.png
new file mode 100644
index 0000000000..fe8acdd25f
Binary files /dev/null and b/discord/images/components/multiple-buttons-example-1.png differ
diff --git a/static/images/components/multiple-buttons-example-1.webp b/discord/images/components/multiple-buttons-example-1.webp
similarity index 100%
rename from static/images/components/multiple-buttons-example-1.webp
rename to discord/images/components/multiple-buttons-example-1.webp
diff --git a/discord/images/components/multiple-buttons-example-2.png b/discord/images/components/multiple-buttons-example-2.png
new file mode 100644
index 0000000000..f646978dc0
Binary files /dev/null and b/discord/images/components/multiple-buttons-example-2.png differ
diff --git a/static/images/components/multiple-buttons-example-2.webp b/discord/images/components/multiple-buttons-example-2.webp
similarity index 100%
rename from static/images/components/multiple-buttons-example-2.webp
rename to discord/images/components/multiple-buttons-example-2.webp
diff --git a/discord/images/components/premium-button.png b/discord/images/components/premium-button.png
new file mode 100644
index 0000000000..8f566c20b2
Binary files /dev/null and b/discord/images/components/premium-button.png differ
diff --git a/static/images/components/premium-button.webp b/discord/images/components/premium-button.webp
similarity index 100%
rename from static/images/components/premium-button.webp
rename to discord/images/components/premium-button.webp
diff --git a/discord/images/components/role-select.png b/discord/images/components/role-select.png
new file mode 100644
index 0000000000..953881aca1
Binary files /dev/null and b/discord/images/components/role-select.png differ
diff --git a/static/images/components/role-select.webp b/discord/images/components/role-select.webp
similarity index 100%
rename from static/images/components/role-select.webp
rename to discord/images/components/role-select.webp
diff --git a/discord/images/components/section.png b/discord/images/components/section.png
new file mode 100644
index 0000000000..af9d7dd987
Binary files /dev/null and b/discord/images/components/section.png differ
diff --git a/static/images/components/section.webp b/discord/images/components/section.webp
similarity index 100%
rename from static/images/components/section.webp
rename to discord/images/components/section.webp
diff --git a/discord/images/components/separator.png b/discord/images/components/separator.png
new file mode 100644
index 0000000000..f7282988a9
Binary files /dev/null and b/discord/images/components/separator.png differ
diff --git a/static/images/components/separator.webp b/discord/images/components/separator.webp
similarity index 100%
rename from static/images/components/separator.webp
rename to discord/images/components/separator.webp
diff --git a/discord/images/components/string-select.png b/discord/images/components/string-select.png
new file mode 100644
index 0000000000..b8a02c2923
Binary files /dev/null and b/discord/images/components/string-select.png differ
diff --git a/static/images/components/string-select.webp b/discord/images/components/string-select.webp
similarity index 100%
rename from static/images/components/string-select.webp
rename to discord/images/components/string-select.webp
diff --git a/discord/images/components/text-display.png b/discord/images/components/text-display.png
new file mode 100644
index 0000000000..f42211b847
Binary files /dev/null and b/discord/images/components/text-display.png differ
diff --git a/static/images/components/text-display.webp b/discord/images/components/text-display.webp
similarity index 100%
rename from static/images/components/text-display.webp
rename to discord/images/components/text-display.webp
diff --git a/discord/images/components/user-select.png b/discord/images/components/user-select.png
new file mode 100644
index 0000000000..ce64e5c39c
Binary files /dev/null and b/discord/images/components/user-select.png differ
diff --git a/static/images/components/user-select.webp b/discord/images/components/user-select.webp
similarity index 100%
rename from static/images/components/user-select.webp
rename to discord/images/components/user-select.webp
diff --git a/discord/images/cpp-files-sdk.png b/discord/images/cpp-files-sdk.png
new file mode 100644
index 0000000000..e2826574fd
Binary files /dev/null and b/discord/images/cpp-files-sdk.png differ
diff --git a/static/images/cpp-files-sdk.webp b/discord/images/cpp-files-sdk.webp
similarity index 100%
rename from static/images/cpp-files-sdk.webp
rename to discord/images/cpp-files-sdk.webp
diff --git a/discord/images/create-team-owned-app.png b/discord/images/create-team-owned-app.png
new file mode 100644
index 0000000000..d157c0ceb8
Binary files /dev/null and b/discord/images/create-team-owned-app.png differ
diff --git a/static/images/create-team-owned-app.webp b/discord/images/create-team-owned-app.webp
similarity index 100%
rename from static/images/create-team-owned-app.webp
rename to discord/images/create-team-owned-app.webp
diff --git a/static/images/default-presence-activities.png b/discord/images/default-presence-activities.png
similarity index 100%
rename from static/images/default-presence-activities.png
rename to discord/images/default-presence-activities.png
diff --git a/discord/images/demo-gif.gif b/discord/images/demo-gif.gif
new file mode 100644
index 0000000000..54e123f5f3
Binary files /dev/null and b/discord/images/demo-gif.gif differ
diff --git a/static/images/discovery-app-directory-product-page.webp b/discord/images/discovery-app-directory-product-page.webp
similarity index 100%
rename from static/images/discovery-app-directory-product-page.webp
rename to discord/images/discovery-app-directory-product-page.webp
diff --git a/static/images/discovery-app-launcher.webp b/discord/images/discovery-app-launcher.webp
similarity index 100%
rename from static/images/discovery-app-launcher.webp
rename to discord/images/discovery-app-launcher.webp
diff --git a/static/images/discovery-sharing-links.webp b/discord/images/discovery-sharing-links.webp
similarity index 100%
rename from static/images/discovery-sharing-links.webp
rename to discord/images/discovery-sharing-links.webp
diff --git a/discord/images/discovery/app-description.png b/discord/images/discovery/app-description.png
new file mode 100644
index 0000000000..c5f4902de1
Binary files /dev/null and b/discord/images/discovery/app-description.png differ
diff --git a/discord/images/discovery/app-launcher.png b/discord/images/discovery/app-launcher.png
new file mode 100644
index 0000000000..2f5427edfb
Binary files /dev/null and b/discord/images/discovery/app-launcher.png differ
diff --git a/discord/images/discovery/directory-product-page.png b/discord/images/discovery/directory-product-page.png
new file mode 100644
index 0000000000..b780113b8e
Binary files /dev/null and b/discord/images/discovery/directory-product-page.png differ
diff --git a/discord/images/discovery/sharing-links.png b/discord/images/discovery/sharing-links.png
new file mode 100644
index 0000000000..226d8cf100
Binary files /dev/null and b/discord/images/discovery/sharing-links.png differ
diff --git a/discord/images/discovery/summary-bad.png b/discord/images/discovery/summary-bad.png
new file mode 100644
index 0000000000..fa5615a947
Binary files /dev/null and b/discord/images/discovery/summary-bad.png differ
diff --git a/discord/images/discovery/summary-good.png b/discord/images/discovery/summary-good.png
new file mode 100644
index 0000000000..ef23e5a8c6
Binary files /dev/null and b/discord/images/discovery/summary-good.png differ
diff --git a/discord/images/discovery/tags.png b/discord/images/discovery/tags.png
new file mode 100644
index 0000000000..0598e3cffd
Binary files /dev/null and b/discord/images/discovery/tags.png differ
diff --git a/discord/images/events/gateway-lifecycle.svg b/discord/images/events/gateway-lifecycle.svg
new file mode 100644
index 0000000000..34cedcf2b8
--- /dev/null
+++ b/discord/images/events/gateway-lifecycle.svg
@@ -0,0 +1,463 @@
+
diff --git a/discord/images/example-poll.png b/discord/images/example-poll.png
new file mode 100644
index 0000000000..2c934fae52
Binary files /dev/null and b/discord/images/example-poll.png differ
diff --git a/static/images/example-poll.webp b/discord/images/example-poll.webp
similarity index 100%
rename from static/images/example-poll.webp
rename to discord/images/example-poll.webp
diff --git a/static/images/examples-ephemeral-message.png b/discord/images/examples-ephemeral-message.png
similarity index 100%
rename from static/images/examples-ephemeral-message.png
rename to discord/images/examples-ephemeral-message.png
diff --git a/static/images/examples-update-message.png b/discord/images/examples-update-message.png
similarity index 100%
rename from static/images/examples-update-message.png
rename to discord/images/examples-update-message.png
diff --git a/discord/images/frame-wumpus.png b/discord/images/frame-wumpus.png
new file mode 100644
index 0000000000..4f736d0d22
Binary files /dev/null and b/discord/images/frame-wumpus.png differ
diff --git a/static/images/game-overlay-sdk-invite.webp b/discord/images/game-overlay-sdk-invite.webp
similarity index 100%
rename from static/images/game-overlay-sdk-invite.webp
rename to discord/images/game-overlay-sdk-invite.webp
diff --git a/static/images/game-overlay-sdk-voice-settings.webp b/discord/images/game-overlay-sdk-voice-settings.webp
similarity index 100%
rename from static/images/game-overlay-sdk-voice-settings.webp
rename to discord/images/game-overlay-sdk-voice-settings.webp
diff --git a/static/images/game-sdk-presence-example.png b/discord/images/game-sdk-presence-example.png
similarity index 100%
rename from static/images/game-sdk-presence-example.png
rename to discord/images/game-sdk-presence-example.png
diff --git a/static/images/gateway-lifecycle.svg b/discord/images/gateway-lifecycle.svg
similarity index 100%
rename from static/images/gateway-lifecycle.svg
rename to discord/images/gateway-lifecycle.svg
diff --git a/discord/images/getting-started-default-install.png b/discord/images/getting-started-default-install.png
new file mode 100644
index 0000000000..de254df6ff
Binary files /dev/null and b/discord/images/getting-started-default-install.png differ
diff --git a/static/images/getting-started-default-install.webp b/discord/images/getting-started-default-install.webp
similarity index 100%
rename from static/images/getting-started-default-install.webp
rename to discord/images/getting-started-default-install.webp
diff --git a/static/images/getting-started-demo.gif b/discord/images/getting-started-demo copy.gif
similarity index 100%
rename from static/images/getting-started-demo.gif
rename to discord/images/getting-started-demo copy.gif
diff --git a/discord/images/getting-started-demo.gif b/discord/images/getting-started-demo.gif
new file mode 100644
index 0000000000..54e123f5f3
Binary files /dev/null and b/discord/images/getting-started-demo.gif differ
diff --git a/discord/images/getting-started-interactions-endpoint.png b/discord/images/getting-started-interactions-endpoint.png
new file mode 100644
index 0000000000..5d79345a9a
Binary files /dev/null and b/discord/images/getting-started-interactions-endpoint.png differ
diff --git a/static/images/getting-started-interactions-endpoint.webp b/discord/images/getting-started-interactions-endpoint.webp
similarity index 100%
rename from static/images/getting-started-interactions-endpoint.webp
rename to discord/images/getting-started-interactions-endpoint.webp
diff --git a/static/images/interactions-url.webp b/discord/images/interactions-url.webp
similarity index 100%
rename from static/images/interactions-url.webp
rename to discord/images/interactions-url.webp
diff --git a/discord/images/introduction.svg b/discord/images/introduction.svg
new file mode 100644
index 0000000000..788129ff6e
--- /dev/null
+++ b/discord/images/introduction.svg
@@ -0,0 +1,1841 @@
+
+
diff --git a/discord/images/lib-linked-sdk.png b/discord/images/lib-linked-sdk.png
new file mode 100644
index 0000000000..baa0cce836
Binary files /dev/null and b/discord/images/lib-linked-sdk.png differ
diff --git a/static/images/lib-linked-sdk.webp b/discord/images/lib-linked-sdk.webp
similarity index 100%
rename from static/images/lib-linked-sdk.webp
rename to discord/images/lib-linked-sdk.webp
diff --git a/static/images/linked-roles-connect-account.webp b/discord/images/linked-roles-connect-account.webp
similarity index 100%
rename from static/images/linked-roles-connect-account.webp
rename to discord/images/linked-roles-connect-account.webp
diff --git a/static/images/linked-roles-connected.webp b/discord/images/linked-roles-connected.webp
similarity index 100%
rename from static/images/linked-roles-connected.webp
rename to discord/images/linked-roles-connected.webp
diff --git a/static/images/linked-roles-consent-dialog.webp b/discord/images/linked-roles-consent-dialog.webp
similarity index 100%
rename from static/images/linked-roles-consent-dialog.webp
rename to discord/images/linked-roles-consent-dialog.webp
diff --git a/static/images/linked-roles-glitch-share-url.webp b/discord/images/linked-roles-glitch-share-url.webp
similarity index 100%
rename from static/images/linked-roles-glitch-share-url.webp
rename to discord/images/linked-roles-glitch-share-url.webp
diff --git a/static/images/linked-roles-glitch.webp b/discord/images/linked-roles-glitch.webp
similarity index 100%
rename from static/images/linked-roles-glitch.webp
rename to discord/images/linked-roles-glitch.webp
diff --git a/static/images/linked-roles-oauth-config.webp b/discord/images/linked-roles-oauth-config.webp
similarity index 100%
rename from static/images/linked-roles-oauth-config.webp
rename to discord/images/linked-roles-oauth-config.webp
diff --git a/static/images/linked-roles-register.webp b/discord/images/linked-roles-register.webp
similarity index 100%
rename from static/images/linked-roles-register.webp
rename to discord/images/linked-roles-register.webp
diff --git a/static/images/linked-roles-verification-setup.webp b/discord/images/linked-roles-verification-setup.webp
similarity index 100%
rename from static/images/linked-roles-verification-setup.webp
rename to discord/images/linked-roles-verification-setup.webp
diff --git a/static/images/linked-roles-verify-endpoint.webp b/discord/images/linked-roles-verify-endpoint.webp
similarity index 100%
rename from static/images/linked-roles-verify-endpoint.webp
rename to discord/images/linked-roles-verify-endpoint.webp
diff --git a/static/images/mdx-button.webp b/discord/images/mdx-button.webp
similarity index 100%
rename from static/images/mdx-button.webp
rename to discord/images/mdx-button.webp
diff --git a/static/images/mdx-card.webp b/discord/images/mdx-card.webp
similarity index 100%
rename from static/images/mdx-card.webp
rename to discord/images/mdx-card.webp
diff --git a/static/images/mdx-collapsible.webp b/discord/images/mdx-collapsible.webp
similarity index 100%
rename from static/images/mdx-collapsible.webp
rename to discord/images/mdx-collapsible.webp
diff --git a/discord/images/message-command.png b/discord/images/message-command.png
new file mode 100644
index 0000000000..096834662f
Binary files /dev/null and b/discord/images/message-command.png differ
diff --git a/static/images/message-command.webp b/discord/images/message-command.webp
similarity index 100%
rename from static/images/message-command.webp
rename to discord/images/message-command.webp
diff --git a/static/images/modal-desktop.webp b/discord/images/modal-desktop.webp
similarity index 100%
rename from static/images/modal-desktop.webp
rename to discord/images/modal-desktop.webp
diff --git a/static/images/monetization-overview.webp b/discord/images/monetization-overview.webp
similarity index 100%
rename from static/images/monetization-overview.webp
rename to discord/images/monetization-overview.webp
diff --git a/discord/images/monetization/botuser-profile.png b/discord/images/monetization/botuser-profile.png
new file mode 100644
index 0000000000..016359e432
Binary files /dev/null and b/discord/images/monetization/botuser-profile.png differ
diff --git a/discord/images/monetization/multisub.png b/discord/images/monetization/multisub.png
new file mode 100644
index 0000000000..22349c2b4d
Binary files /dev/null and b/discord/images/monetization/multisub.png differ
diff --git a/discord/images/monetization/overview.png b/discord/images/monetization/overview.png
new file mode 100644
index 0000000000..dc450ec99a
Binary files /dev/null and b/discord/images/monetization/overview.png differ
diff --git a/discord/images/monetization/premium-button.png b/discord/images/monetization/premium-button.png
new file mode 100644
index 0000000000..8f566c20b2
Binary files /dev/null and b/discord/images/monetization/premium-button.png differ
diff --git a/discord/images/monetization/premium-items.png b/discord/images/monetization/premium-items.png
new file mode 100644
index 0000000000..1f813936af
Binary files /dev/null and b/discord/images/monetization/premium-items.png differ
diff --git a/discord/images/monetization/sku-benefits.png b/discord/images/monetization/sku-benefits.png
new file mode 100644
index 0000000000..d3dc2d1af6
Binary files /dev/null and b/discord/images/monetization/sku-benefits.png differ
diff --git a/discord/images/monetization/sku_embed.png b/discord/images/monetization/sku_embed.png
new file mode 100644
index 0000000000..1e9c198bc0
Binary files /dev/null and b/discord/images/monetization/sku_embed.png differ
diff --git a/discord/images/monetization/store_embed.png b/discord/images/monetization/store_embed.png
new file mode 100644
index 0000000000..315d14511a
Binary files /dev/null and b/discord/images/monetization/store_embed.png differ
diff --git a/static/images/multiple-buttons-example-1.webp b/discord/images/multiple-buttons-example-1.webp
similarity index 100%
rename from static/images/multiple-buttons-example-1.webp
rename to discord/images/multiple-buttons-example-1.webp
diff --git a/static/images/multiple-buttons-example-2.webp b/discord/images/multiple-buttons-example-2.webp
similarity index 100%
rename from static/images/multiple-buttons-example-2.webp
rename to discord/images/multiple-buttons-example-2.webp
diff --git a/static/images/multisub.webp b/discord/images/multisub.webp
similarity index 100%
rename from static/images/multisub.webp
rename to discord/images/multisub.webp
diff --git a/static/images/new-permissions-flowchart.svg b/discord/images/new-permissions-flowchart copy.svg
similarity index 100%
rename from static/images/new-permissions-flowchart.svg
rename to discord/images/new-permissions-flowchart copy.svg
diff --git a/discord/images/new-permissions-flowchart.svg b/discord/images/new-permissions-flowchart.svg
new file mode 100644
index 0000000000..d946b97dd3
--- /dev/null
+++ b/discord/images/new-permissions-flowchart.svg
@@ -0,0 +1,299 @@
+
diff --git a/discord/images/overview-apps.png b/discord/images/overview-apps.png
new file mode 100644
index 0000000000..707cfd9f99
Binary files /dev/null and b/discord/images/overview-apps.png differ
diff --git a/discord/images/overview-command-desktop.png b/discord/images/overview-command-desktop.png
new file mode 100644
index 0000000000..cb3411ad71
Binary files /dev/null and b/discord/images/overview-command-desktop.png differ
diff --git a/static/images/overview-command-desktop.webp b/discord/images/overview-command-desktop.webp
similarity index 100%
rename from static/images/overview-command-desktop.webp
rename to discord/images/overview-command-desktop.webp
diff --git a/discord/images/overview-components.png b/discord/images/overview-components.png
new file mode 100644
index 0000000000..19ca8b1a13
Binary files /dev/null and b/discord/images/overview-components.png differ
diff --git a/static/images/overview-components.webp b/discord/images/overview-components.webp
similarity index 100%
rename from static/images/overview-components.webp
rename to discord/images/overview-components.webp
diff --git a/discord/images/overview-modals.png b/discord/images/overview-modals.png
new file mode 100644
index 0000000000..410104e8b4
Binary files /dev/null and b/discord/images/overview-modals.png differ
diff --git a/static/images/overview-modals.webp b/discord/images/overview-modals.webp
similarity index 100%
rename from static/images/overview-modals.webp
rename to discord/images/overview-modals.webp
diff --git a/static/images/overview-of-apps-banner.webp b/discord/images/overview-of-apps-banner.webp
similarity index 100%
rename from static/images/overview-of-apps-banner.webp
rename to discord/images/overview-of-apps-banner.webp
diff --git a/static/images/premium-button.webp b/discord/images/premium-button.webp
similarity index 100%
rename from static/images/premium-button.webp
rename to discord/images/premium-button.webp
diff --git a/static/images/premium-items.webp b/discord/images/premium-items.webp
similarity index 100%
rename from static/images/premium-items.webp
rename to discord/images/premium-items.webp
diff --git a/static/images/rich-presence-asset-images.webp b/discord/images/rich-presence-asset-images.webp
similarity index 100%
rename from static/images/rich-presence-asset-images.webp
rename to discord/images/rich-presence-asset-images.webp
diff --git a/static/images/rich-presence-examples.png b/discord/images/rich-presence-examples.png
similarity index 100%
rename from static/images/rich-presence-examples.png
rename to discord/images/rich-presence-examples.png
diff --git a/static/images/rich-presence-invite-image.webp b/discord/images/rich-presence-invite-image.webp
similarity index 100%
rename from static/images/rich-presence-invite-image.webp
rename to discord/images/rich-presence-invite-image.webp
diff --git a/discord/images/rich-presence/actionable.png b/discord/images/rich-presence/actionable.png
new file mode 100644
index 0000000000..bc19ffdb6b
Binary files /dev/null and b/discord/images/rich-presence/actionable.png differ
diff --git a/discord/images/rich-presence/activities-example.png b/discord/images/rich-presence/activities-example.png
new file mode 100644
index 0000000000..35e013b2f0
Binary files /dev/null and b/discord/images/rich-presence/activities-example.png differ
diff --git a/discord/images/rich-presence/all-fields.png b/discord/images/rich-presence/all-fields.png
new file mode 100644
index 0000000000..9778ef895a
Binary files /dev/null and b/discord/images/rich-presence/all-fields.png differ
diff --git a/discord/images/rich-presence/annotated-data-activities.png b/discord/images/rich-presence/annotated-data-activities.png
new file mode 100644
index 0000000000..bbe990ac05
Binary files /dev/null and b/discord/images/rich-presence/annotated-data-activities.png differ
diff --git a/discord/images/rich-presence/asset-images.png b/discord/images/rich-presence/asset-images.png
new file mode 100644
index 0000000000..7ca8681095
Binary files /dev/null and b/discord/images/rich-presence/asset-images.png differ
diff --git a/discord/images/rich-presence/default-activities.png b/discord/images/rich-presence/default-activities.png
new file mode 100644
index 0000000000..1db6748dcc
Binary files /dev/null and b/discord/images/rich-presence/default-activities.png differ
diff --git a/discord/images/rich-presence/examples.png b/discord/images/rich-presence/examples.png
new file mode 100644
index 0000000000..d834cb7c87
Binary files /dev/null and b/discord/images/rich-presence/examples.png differ
diff --git a/discord/images/rich-presence/game-sdk-example.png b/discord/images/rich-presence/game-sdk-example.png
new file mode 100644
index 0000000000..4d986a089b
Binary files /dev/null and b/discord/images/rich-presence/game-sdk-example.png differ
diff --git a/discord/images/rich-presence/good-art.png b/discord/images/rich-presence/good-art.png
new file mode 100644
index 0000000000..20b38a03b4
Binary files /dev/null and b/discord/images/rich-presence/good-art.png differ
diff --git a/discord/images/rich-presence/invite-image.png b/discord/images/rich-presence/invite-image.png
new file mode 100644
index 0000000000..929a4657d8
Binary files /dev/null and b/discord/images/rich-presence/invite-image.png differ
diff --git a/discord/images/rich-presence/legend.png b/discord/images/rich-presence/legend.png
new file mode 100644
index 0000000000..b0416341f0
Binary files /dev/null and b/discord/images/rich-presence/legend.png differ
diff --git a/discord/images/rich-presence/short-strings.png b/discord/images/rich-presence/short-strings.png
new file mode 100644
index 0000000000..9ad0faa532
Binary files /dev/null and b/discord/images/rich-presence/short-strings.png differ
diff --git a/static/images/rp-actionable.webp b/discord/images/rp-actionable.webp
similarity index 100%
rename from static/images/rp-actionable.webp
rename to discord/images/rp-actionable.webp
diff --git a/static/images/rp-all-fields.webp b/discord/images/rp-all-fields.webp
similarity index 100%
rename from static/images/rp-all-fields.webp
rename to discord/images/rp-all-fields.webp
diff --git a/static/images/rp-good-art.webp b/discord/images/rp-good-art.webp
similarity index 100%
rename from static/images/rp-good-art.webp
rename to discord/images/rp-good-art.webp
diff --git a/static/images/rp-legend.webp b/discord/images/rp-legend.webp
similarity index 100%
rename from static/images/rp-legend.webp
rename to discord/images/rp-legend.webp
diff --git a/static/images/rp-short-strings.webp b/discord/images/rp-short-strings.webp
similarity index 100%
rename from static/images/rp-short-strings.webp
rename to discord/images/rp-short-strings.webp
diff --git a/static/images/sku-benefits.webp b/discord/images/sku-benefits.webp
similarity index 100%
rename from static/images/sku-benefits.webp
rename to discord/images/sku-benefits.webp
diff --git a/static/images/sku-custom.webp b/discord/images/sku-custom.webp
similarity index 100%
rename from static/images/sku-custom.webp
rename to discord/images/sku-custom.webp
diff --git a/static/images/sku-unicode.webp b/discord/images/sku-unicode.webp
similarity index 100%
rename from static/images/sku-unicode.webp
rename to discord/images/sku-unicode.webp
diff --git a/static/images/sku_embed.webp b/discord/images/sku_embed.webp
similarity index 100%
rename from static/images/sku_embed.webp
rename to discord/images/sku_embed.webp
diff --git a/static/images/slash-command-options.png b/discord/images/slash-command-options.png
similarity index 100%
rename from static/images/slash-command-options.png
rename to discord/images/slash-command-options.png
diff --git a/discord/images/snowflake-to-datetime.svg b/discord/images/snowflake-to-datetime.svg
new file mode 100644
index 0000000000..73f3da0a60
--- /dev/null
+++ b/discord/images/snowflake-to-datetime.svg
@@ -0,0 +1 @@
+
diff --git a/discord/images/snowflake.png b/discord/images/snowflake.png
new file mode 100644
index 0000000000..c8f4fd1485
Binary files /dev/null and b/discord/images/snowflake.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Brand-02.png b/discord/images/social-sdk/design-guidelines/Brand-02.png
new file mode 100644
index 0000000000..02269ef229
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Brand-02.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Brand-03.png b/discord/images/social-sdk/design-guidelines/Brand-03.png
new file mode 100644
index 0000000000..42d0962df9
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Brand-03.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Brand-04.png b/discord/images/social-sdk/design-guidelines/Brand-04.png
new file mode 100644
index 0000000000..2fd7ab4caf
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Brand-04.png differ
diff --git a/static/images/social-sdk/design-guidelines/ChatHistory-02.webp b/discord/images/social-sdk/design-guidelines/ChatHistory-02.webp
similarity index 100%
rename from static/images/social-sdk/design-guidelines/ChatHistory-02.webp
rename to discord/images/social-sdk/design-guidelines/ChatHistory-02.webp
diff --git a/static/images/social-sdk/design-guidelines/ChatHistory-03.webp b/discord/images/social-sdk/design-guidelines/ChatHistory-03.webp
similarity index 100%
rename from static/images/social-sdk/design-guidelines/ChatHistory-03.webp
rename to discord/images/social-sdk/design-guidelines/ChatHistory-03.webp
diff --git a/discord/images/social-sdk/design-guidelines/ConnectionPoints-02.png b/discord/images/social-sdk/design-guidelines/ConnectionPoints-02.png
new file mode 100644
index 0000000000..f33ce3fac1
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/ConnectionPoints-02.png differ
diff --git a/discord/images/social-sdk/design-guidelines/ConnectionPoints-03.png b/discord/images/social-sdk/design-guidelines/ConnectionPoints-03.png
new file mode 100644
index 0000000000..85559c65fa
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/ConnectionPoints-03.png differ
diff --git a/discord/images/social-sdk/design-guidelines/ConnectionPoints-04.png b/discord/images/social-sdk/design-guidelines/ConnectionPoints-04.png
new file mode 100644
index 0000000000..89ce604340
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/ConnectionPoints-04.png differ
diff --git a/discord/images/social-sdk/design-guidelines/ConnectionPoints-05.png b/discord/images/social-sdk/design-guidelines/ConnectionPoints-05.png
new file mode 100644
index 0000000000..8c48aea151
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/ConnectionPoints-05.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Consoles-01.jpg b/discord/images/social-sdk/design-guidelines/Consoles-01.jpg
new file mode 100644
index 0000000000..fdea7b4a67
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Consoles-01.jpg differ
diff --git a/discord/images/social-sdk/design-guidelines/Consoles-02.jpg b/discord/images/social-sdk/design-guidelines/Consoles-02.jpg
new file mode 100644
index 0000000000..166b861220
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Consoles-02.jpg differ
diff --git a/discord/images/social-sdk/design-guidelines/Consoles-03.jpg b/discord/images/social-sdk/design-guidelines/Consoles-03.jpg
new file mode 100644
index 0000000000..99ade45742
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Consoles-03.jpg differ
diff --git a/discord/images/social-sdk/design-guidelines/Consoles-04.jpg b/discord/images/social-sdk/design-guidelines/Consoles-04.jpg
new file mode 100644
index 0000000000..0a4f506d1d
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Consoles-04.jpg differ
diff --git a/discord/images/social-sdk/design-guidelines/Consoles-05.jpg b/discord/images/social-sdk/design-guidelines/Consoles-05.jpg
new file mode 100644
index 0000000000..c654bd977b
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Consoles-05.jpg differ
diff --git a/discord/images/social-sdk/design-guidelines/Consoles-06.jpg b/discord/images/social-sdk/design-guidelines/Consoles-06.jpg
new file mode 100644
index 0000000000..c889e587a5
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Consoles-06.jpg differ
diff --git a/discord/images/social-sdk/design-guidelines/DMs-02.png b/discord/images/social-sdk/design-guidelines/DMs-02.png
new file mode 100644
index 0000000000..1f098307a4
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/DMs-02.png differ
diff --git a/discord/images/social-sdk/design-guidelines/DMs-03.png b/discord/images/social-sdk/design-guidelines/DMs-03.png
new file mode 100644
index 0000000000..ca7f6cb186
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/DMs-03.png differ
diff --git a/discord/images/social-sdk/design-guidelines/DMs-04.png b/discord/images/social-sdk/design-guidelines/DMs-04.png
new file mode 100644
index 0000000000..8e68feba8b
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/DMs-04.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-01.png b/discord/images/social-sdk/design-guidelines/GameFriends-01.png
new file mode 100644
index 0000000000..e89a537769
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-01.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-02.png b/discord/images/social-sdk/design-guidelines/GameFriends-02.png
new file mode 100644
index 0000000000..d3907aa73d
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-02.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-03.png b/discord/images/social-sdk/design-guidelines/GameFriends-03.png
new file mode 100644
index 0000000000..af7e74e2e4
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-03.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-04.png b/discord/images/social-sdk/design-guidelines/GameFriends-04.png
new file mode 100644
index 0000000000..85ab375edf
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-04.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-05.png b/discord/images/social-sdk/design-guidelines/GameFriends-05.png
new file mode 100644
index 0000000000..e5ee72d173
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-05.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-06.png b/discord/images/social-sdk/design-guidelines/GameFriends-06.png
new file mode 100644
index 0000000000..00e4e9440a
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-06.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-07.png b/discord/images/social-sdk/design-guidelines/GameFriends-07.png
new file mode 100644
index 0000000000..58451b3238
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-07.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-08.png b/discord/images/social-sdk/design-guidelines/GameFriends-08.png
new file mode 100644
index 0000000000..39de2c5e20
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-08.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-09.png b/discord/images/social-sdk/design-guidelines/GameFriends-09.png
new file mode 100644
index 0000000000..a940fd7bcd
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-09.png differ
diff --git a/discord/images/social-sdk/design-guidelines/GameFriends-10.png b/discord/images/social-sdk/design-guidelines/GameFriends-10.png
new file mode 100644
index 0000000000..e60a475212
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/GameFriends-10.png differ
diff --git a/discord/images/social-sdk/design-guidelines/LinkedChannels-04.png b/discord/images/social-sdk/design-guidelines/LinkedChannels-04.png
new file mode 100644
index 0000000000..d89701b672
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/LinkedChannels-04.png differ
diff --git a/discord/images/social-sdk/design-guidelines/LinkedChannels-05.png b/discord/images/social-sdk/design-guidelines/LinkedChannels-05.png
new file mode 100644
index 0000000000..d95e9a4e58
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/LinkedChannels-05.png differ
diff --git a/discord/images/social-sdk/design-guidelines/LinkedChannels-06.png b/discord/images/social-sdk/design-guidelines/LinkedChannels-06.png
new file mode 100644
index 0000000000..0c8286ed5d
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/LinkedChannels-06.png differ
diff --git a/discord/images/social-sdk/design-guidelines/LinkedChannels-07.png b/discord/images/social-sdk/design-guidelines/LinkedChannels-07.png
new file mode 100644
index 0000000000..8ad42cf506
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/LinkedChannels-07.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Principle-02.png b/discord/images/social-sdk/design-guidelines/Principle-02.png
new file mode 100644
index 0000000000..71ef86af82
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Principle-02.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Principle-03.png b/discord/images/social-sdk/design-guidelines/Principle-03.png
new file mode 100644
index 0000000000..97a9a81619
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Principle-03.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Principle-04.png b/discord/images/social-sdk/design-guidelines/Principle-04.png
new file mode 100644
index 0000000000..8e45d44831
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Principle-04.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Principle-05.png b/discord/images/social-sdk/design-guidelines/Principle-05.png
new file mode 100644
index 0000000000..006333f543
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Principle-05.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Principle-06.png b/discord/images/social-sdk/design-guidelines/Principle-06.png
new file mode 100644
index 0000000000..808d10ac0c
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Principle-06.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Principle-07.png b/discord/images/social-sdk/design-guidelines/Principle-07.png
new file mode 100644
index 0000000000..66c7b30071
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Principle-07.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Prov-02.png b/discord/images/social-sdk/design-guidelines/Prov-02.png
new file mode 100644
index 0000000000..8ad43b5062
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Prov-02.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Prov-03.png b/discord/images/social-sdk/design-guidelines/Prov-03.png
new file mode 100644
index 0000000000..7b7a2e3d0b
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Prov-03.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Prov-04.png b/discord/images/social-sdk/design-guidelines/Prov-04.png
new file mode 100644
index 0000000000..a8b14e2926
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Prov-04.png differ
diff --git a/discord/images/social-sdk/design-guidelines/Prov-05.png b/discord/images/social-sdk/design-guidelines/Prov-05.png
new file mode 100644
index 0000000000..f3dfc0d39e
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/Prov-05.png differ
diff --git a/discord/images/social-sdk/design-guidelines/SigningIn-02.png b/discord/images/social-sdk/design-guidelines/SigningIn-02.png
new file mode 100644
index 0000000000..b0881d1805
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/SigningIn-02.png differ
diff --git a/discord/images/social-sdk/design-guidelines/SigningIn-03.png b/discord/images/social-sdk/design-guidelines/SigningIn-03.png
new file mode 100644
index 0000000000..0ca40bc1c1
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/SigningIn-03.png differ
diff --git a/discord/images/social-sdk/design-guidelines/SigningIn-04.png b/discord/images/social-sdk/design-guidelines/SigningIn-04.png
new file mode 100644
index 0000000000..3808f3d78b
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/SigningIn-04.png differ
diff --git a/discord/images/social-sdk/design-guidelines/SigningIn-05.png b/discord/images/social-sdk/design-guidelines/SigningIn-05.png
new file mode 100644
index 0000000000..7f3d91d858
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/SigningIn-05.png differ
diff --git a/discord/images/social-sdk/design-guidelines/SigningIn-06.png b/discord/images/social-sdk/design-guidelines/SigningIn-06.png
new file mode 100644
index 0000000000..3cc5d3a4e6
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/SigningIn-06.png differ
diff --git a/discord/images/social-sdk/design-guidelines/SigningIn-07.png b/discord/images/social-sdk/design-guidelines/SigningIn-07.png
new file mode 100644
index 0000000000..5cb7a1af90
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/SigningIn-07.png differ
diff --git a/discord/images/social-sdk/design-guidelines/SigningIn-08.png b/discord/images/social-sdk/design-guidelines/SigningIn-08.png
new file mode 100644
index 0000000000..10e0d65fd3
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/SigningIn-08.png differ
diff --git a/static/images/social-sdk/design-guidelines/SocialSettings-02.webp b/discord/images/social-sdk/design-guidelines/SocialSettings-02.webp
similarity index 100%
rename from static/images/social-sdk/design-guidelines/SocialSettings-02.webp
rename to discord/images/social-sdk/design-guidelines/SocialSettings-02.webp
diff --git a/static/images/social-sdk/design-guidelines/SocialSettings-03.webp b/discord/images/social-sdk/design-guidelines/SocialSettings-03.webp
similarity index 100%
rename from static/images/social-sdk/design-guidelines/SocialSettings-03.webp
rename to discord/images/social-sdk/design-guidelines/SocialSettings-03.webp
diff --git a/static/images/social-sdk/design-guidelines/SocialSettings-04.webp b/discord/images/social-sdk/design-guidelines/SocialSettings-04.webp
similarity index 100%
rename from static/images/social-sdk/design-guidelines/SocialSettings-04.webp
rename to discord/images/social-sdk/design-guidelines/SocialSettings-04.webp
diff --git a/discord/images/social-sdk/design-guidelines/StatusPresence-02.png b/discord/images/social-sdk/design-guidelines/StatusPresence-02.png
new file mode 100644
index 0000000000..c8be99b2d4
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/StatusPresence-02.png differ
diff --git a/discord/images/social-sdk/design-guidelines/StatusPresence-03.png b/discord/images/social-sdk/design-guidelines/StatusPresence-03.png
new file mode 100644
index 0000000000..eb3f55239c
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/StatusPresence-03.png differ
diff --git a/discord/images/social-sdk/design-guidelines/StatusPresence-04.png b/discord/images/social-sdk/design-guidelines/StatusPresence-04.png
new file mode 100644
index 0000000000..6a9933426b
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/StatusPresence-04.png differ
diff --git a/discord/images/social-sdk/design-guidelines/StatusPresence-05.png b/discord/images/social-sdk/design-guidelines/StatusPresence-05.png
new file mode 100644
index 0000000000..89669c4ffe
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/StatusPresence-05.png differ
diff --git a/discord/images/social-sdk/design-guidelines/StatusPresence-06.png b/discord/images/social-sdk/design-guidelines/StatusPresence-06.png
new file mode 100644
index 0000000000..dae7578002
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/StatusPresence-06.png differ
diff --git a/discord/images/social-sdk/design-guidelines/UFL-02.png b/discord/images/social-sdk/design-guidelines/UFL-02.png
new file mode 100644
index 0000000000..62c8ed066c
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/UFL-02.png differ
diff --git a/discord/images/social-sdk/design-guidelines/UFL-03.png b/discord/images/social-sdk/design-guidelines/UFL-03.png
new file mode 100644
index 0000000000..5adca8c896
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/UFL-03.png differ
diff --git a/discord/images/social-sdk/design-guidelines/UFL-04.png b/discord/images/social-sdk/design-guidelines/UFL-04.png
new file mode 100644
index 0000000000..7a6234ff15
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/UFL-04.png differ
diff --git a/discord/images/social-sdk/design-guidelines/UFL-05.png b/discord/images/social-sdk/design-guidelines/UFL-05.png
new file mode 100644
index 0000000000..b617a2e258
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/UFL-05.png differ
diff --git a/discord/images/social-sdk/design-guidelines/UFL-06.png b/discord/images/social-sdk/design-guidelines/UFL-06.png
new file mode 100644
index 0000000000..6d8d5f1c4f
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/UFL-06.png differ
diff --git a/discord/images/social-sdk/design-guidelines/UFL-07.png b/discord/images/social-sdk/design-guidelines/UFL-07.png
new file mode 100644
index 0000000000..28916851d6
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/UFL-07.png differ
diff --git a/discord/images/social-sdk/design-guidelines/UFL-08.png b/discord/images/social-sdk/design-guidelines/UFL-08.png
new file mode 100644
index 0000000000..2712e1d2fe
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/UFL-08.png differ
diff --git a/discord/images/social-sdk/design-guidelines/animated/Connecting-via-Browser.gif b/discord/images/social-sdk/design-guidelines/animated/Connecting-via-Browser.gif
new file mode 100644
index 0000000000..2fd1fb4c63
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/animated/Connecting-via-Browser.gif differ
diff --git a/discord/images/social-sdk/design-guidelines/animated/Connecting-via-Client.gif b/discord/images/social-sdk/design-guidelines/animated/Connecting-via-Client.gif
new file mode 100644
index 0000000000..8e23dcccf8
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/animated/Connecting-via-Client.gif differ
diff --git a/static/images/social-sdk/design-guidelines/animated/DMs-02.gif b/discord/images/social-sdk/design-guidelines/animated/DMs-02.gif
similarity index 100%
rename from static/images/social-sdk/design-guidelines/animated/DMs-02.gif
rename to discord/images/social-sdk/design-guidelines/animated/DMs-02.gif
diff --git a/discord/images/social-sdk/design-guidelines/animated/LinkedChannel-Setup.gif b/discord/images/social-sdk/design-guidelines/animated/LinkedChannel-Setup.gif
new file mode 100644
index 0000000000..331fb9c474
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/animated/LinkedChannel-Setup.gif differ
diff --git a/discord/images/social-sdk/design-guidelines/animated/LinkedChannel-Unlink.gif b/discord/images/social-sdk/design-guidelines/animated/LinkedChannel-Unlink.gif
new file mode 100644
index 0000000000..09edd3c30f
Binary files /dev/null and b/discord/images/social-sdk/design-guidelines/animated/LinkedChannel-Unlink.gif differ
diff --git a/static/images/social-sdk/design-guidelines/animated/LinkedChannels-02.gif b/discord/images/social-sdk/design-guidelines/animated/LinkedChannels-02.gif
similarity index 100%
rename from static/images/social-sdk/design-guidelines/animated/LinkedChannels-02.gif
rename to discord/images/social-sdk/design-guidelines/animated/LinkedChannels-02.gif
diff --git a/static/images/social-sdk/design-guidelines/animated/LinkedChannels-08.gif b/discord/images/social-sdk/design-guidelines/animated/LinkedChannels-08.gif
similarity index 100%
rename from static/images/social-sdk/design-guidelines/animated/LinkedChannels-08.gif
rename to discord/images/social-sdk/design-guidelines/animated/LinkedChannels-08.gif
diff --git a/static/images/social-sdk/design-guidelines/animated/UFL-06.gif b/discord/images/social-sdk/design-guidelines/animated/UFL-06.gif
similarity index 100%
rename from static/images/social-sdk/design-guidelines/animated/UFL-06.gif
rename to discord/images/social-sdk/design-guidelines/animated/UFL-06.gif
diff --git a/static/images/social-sdk/design-guidelines/starter_pack.webp b/discord/images/social-sdk/design-guidelines/starter_pack.webp
similarity index 100%
rename from static/images/social-sdk/design-guidelines/starter_pack.webp
rename to discord/images/social-sdk/design-guidelines/starter_pack.webp
diff --git a/discord/images/social-sdk/development-guides/authorize_device.png b/discord/images/social-sdk/development-guides/authorize_device.png
new file mode 100644
index 0000000000..7db81bacd9
Binary files /dev/null and b/discord/images/social-sdk/development-guides/authorize_device.png differ
diff --git a/discord/images/social-sdk/development-guides/discord-game-dm-settings.png b/discord/images/social-sdk/development-guides/discord-game-dm-settings.png
new file mode 100644
index 0000000000..f2b6ff9516
Binary files /dev/null and b/discord/images/social-sdk/development-guides/discord-game-dm-settings.png differ
diff --git a/static/images/social-sdk/development-guides/game-invite.webp b/discord/images/social-sdk/development-guides/game-invite.webp
similarity index 100%
rename from static/images/social-sdk/development-guides/game-invite.webp
rename to discord/images/social-sdk/development-guides/game-invite.webp
diff --git a/discord/images/social-sdk/getting-started/partials/error.png b/discord/images/social-sdk/getting-started/partials/error.png
new file mode 100644
index 0000000000..30a54a671b
Binary files /dev/null and b/discord/images/social-sdk/getting-started/partials/error.png differ
diff --git a/discord/images/social-sdk/getting-started/partials/open-anyway.png b/discord/images/social-sdk/getting-started/partials/open-anyway.png
new file mode 100644
index 0000000000..a76fb99d60
Binary files /dev/null and b/discord/images/social-sdk/getting-started/partials/open-anyway.png differ
diff --git a/discord/images/social-sdk/getting-started/partials/security-settings.png b/discord/images/social-sdk/getting-started/partials/security-settings.png
new file mode 100644
index 0000000000..b053189f04
Binary files /dev/null and b/discord/images/social-sdk/getting-started/partials/security-settings.png differ
diff --git a/static/images/social-sdk/getting-started/partials/settings-security.webp b/discord/images/social-sdk/getting-started/partials/settings-security.webp
similarity index 100%
rename from static/images/social-sdk/getting-started/partials/settings-security.webp
rename to discord/images/social-sdk/getting-started/partials/settings-security.webp
diff --git a/static/images/social-sdk/getting-started/unity-sample-preview.webp b/discord/images/social-sdk/getting-started/unity-sample-preview.webp
similarity index 100%
rename from static/images/social-sdk/getting-started/unity-sample-preview.webp
rename to discord/images/social-sdk/getting-started/unity-sample-preview.webp
diff --git a/discord/images/social-sdk/overview/social_sdk_header.png b/discord/images/social-sdk/overview/social_sdk_header.png
new file mode 100644
index 0000000000..e163a5e477
Binary files /dev/null and b/discord/images/social-sdk/overview/social_sdk_header.png differ
diff --git a/static/images/store_embed.webp b/discord/images/store_embed.webp
similarity index 100%
rename from static/images/store_embed.webp
rename to discord/images/store_embed.webp
diff --git a/discord/images/team-page.png b/discord/images/team-page.png
new file mode 100644
index 0000000000..461f136b1d
Binary files /dev/null and b/discord/images/team-page.png differ
diff --git a/static/images/team-page.webp b/discord/images/team-page.webp
similarity index 100%
rename from static/images/team-page.webp
rename to discord/images/team-page.webp
diff --git a/discord/images/transfer-app-to-team.png b/discord/images/transfer-app-to-team.png
new file mode 100644
index 0000000000..aee30c80a3
Binary files /dev/null and b/discord/images/transfer-app-to-team.png differ
diff --git a/static/images/transfer-app-to-team.webp b/discord/images/transfer-app-to-team.webp
similarity index 100%
rename from static/images/transfer-app-to-team.webp
rename to discord/images/transfer-app-to-team.webp
diff --git a/discord/images/tutorials/cloudflare-general-overview.png b/discord/images/tutorials/cloudflare-general-overview.png
new file mode 100644
index 0000000000..eff35d6423
Binary files /dev/null and b/discord/images/tutorials/cloudflare-general-overview.png differ
diff --git a/discord/images/tutorials/cloudflare-interactions-endpoint.png b/discord/images/tutorials/cloudflare-interactions-endpoint.png
new file mode 100644
index 0000000000..6d8017b517
Binary files /dev/null and b/discord/images/tutorials/cloudflare-interactions-endpoint.png differ
diff --git a/discord/images/tutorials/cloudflare-ngrok.png b/discord/images/tutorials/cloudflare-ngrok.png
new file mode 100644
index 0000000000..b64d99b137
Binary files /dev/null and b/discord/images/tutorials/cloudflare-ngrok.png differ
diff --git a/discord/images/tutorials/cloudflare-tutorial-demo.gif b/discord/images/tutorials/cloudflare-tutorial-demo.gif
new file mode 100644
index 0000000000..e61bbd314d
Binary files /dev/null and b/discord/images/tutorials/cloudflare-tutorial-demo.gif differ
diff --git a/discord/images/tutorials/cloudflare-url-generator.png b/discord/images/tutorials/cloudflare-url-generator.png
new file mode 100644
index 0000000000..8e4bc8920f
Binary files /dev/null and b/discord/images/tutorials/cloudflare-url-generator.png differ
diff --git a/discord/images/tutorials/command-types.png b/discord/images/tutorials/command-types.png
new file mode 100644
index 0000000000..aafb9d86f7
Binary files /dev/null and b/discord/images/tutorials/command-types.png differ
diff --git a/discord/images/tutorials/examples-ephemeral-message.png b/discord/images/tutorials/examples-ephemeral-message.png
new file mode 100644
index 0000000000..bc318a0817
Binary files /dev/null and b/discord/images/tutorials/examples-ephemeral-message.png differ
diff --git a/discord/images/tutorials/examples-update-message.png b/discord/images/tutorials/examples-update-message.png
new file mode 100644
index 0000000000..9935ecc13e
Binary files /dev/null and b/discord/images/tutorials/examples-update-message.png differ
diff --git a/discord/images/tutorials/interactions-url.png b/discord/images/tutorials/interactions-url.png
new file mode 100644
index 0000000000..f4f9862fb6
Binary files /dev/null and b/discord/images/tutorials/interactions-url.png differ
diff --git a/discord/images/tutorials/linked-roles-connect-account.png b/discord/images/tutorials/linked-roles-connect-account.png
new file mode 100644
index 0000000000..6f30a20644
Binary files /dev/null and b/discord/images/tutorials/linked-roles-connect-account.png differ
diff --git a/discord/images/tutorials/linked-roles-connected.png b/discord/images/tutorials/linked-roles-connected.png
new file mode 100644
index 0000000000..e0abee8d48
Binary files /dev/null and b/discord/images/tutorials/linked-roles-connected.png differ
diff --git a/discord/images/tutorials/linked-roles-consent-dialog.png b/discord/images/tutorials/linked-roles-consent-dialog.png
new file mode 100644
index 0000000000..329163ec3e
Binary files /dev/null and b/discord/images/tutorials/linked-roles-consent-dialog.png differ
diff --git a/discord/images/tutorials/linked-roles-glitch-shared-url.png b/discord/images/tutorials/linked-roles-glitch-shared-url.png
new file mode 100644
index 0000000000..e1ea49ba65
Binary files /dev/null and b/discord/images/tutorials/linked-roles-glitch-shared-url.png differ
diff --git a/discord/images/tutorials/linked-roles-glitch.png b/discord/images/tutorials/linked-roles-glitch.png
new file mode 100644
index 0000000000..88109b74d9
Binary files /dev/null and b/discord/images/tutorials/linked-roles-glitch.png differ
diff --git a/discord/images/tutorials/linked-roles-oauth-config.png b/discord/images/tutorials/linked-roles-oauth-config.png
new file mode 100644
index 0000000000..fb66f047f1
Binary files /dev/null and b/discord/images/tutorials/linked-roles-oauth-config.png differ
diff --git a/discord/images/tutorials/linked-roles-register.png b/discord/images/tutorials/linked-roles-register.png
new file mode 100644
index 0000000000..dfe6035886
Binary files /dev/null and b/discord/images/tutorials/linked-roles-register.png differ
diff --git a/discord/images/tutorials/linked-roles-verification-setup.png b/discord/images/tutorials/linked-roles-verification-setup.png
new file mode 100644
index 0000000000..b0b29c4e5b
Binary files /dev/null and b/discord/images/tutorials/linked-roles-verification-setup.png differ
diff --git a/discord/images/tutorials/linked-roles-verify-endpoint.png b/discord/images/tutorials/linked-roles-verify-endpoint.png
new file mode 100644
index 0000000000..32f2f1775f
Binary files /dev/null and b/discord/images/tutorials/linked-roles-verify-endpoint.png differ
diff --git a/discord/images/tutorials/slash-command-options.png b/discord/images/tutorials/slash-command-options.png
new file mode 100644
index 0000000000..bf2f7af322
Binary files /dev/null and b/discord/images/tutorials/slash-command-options.png differ
diff --git a/discord/images/tutorials/user-install-game-message.png b/discord/images/tutorials/user-install-game-message.png
new file mode 100644
index 0000000000..89cbcc8378
Binary files /dev/null and b/discord/images/tutorials/user-install-game-message.png differ
diff --git a/discord/images/tutorials/user-install-settings.png b/discord/images/tutorials/user-install-settings.png
new file mode 100644
index 0000000000..516901d859
Binary files /dev/null and b/discord/images/tutorials/user-install-settings.png differ
diff --git a/static/images/url-generator.webp b/discord/images/url-generator.webp
similarity index 100%
rename from static/images/url-generator.webp
rename to discord/images/url-generator.webp
diff --git a/discord/images/user-command.png b/discord/images/user-command.png
new file mode 100644
index 0000000000..ef669dd32a
Binary files /dev/null and b/discord/images/user-command.png differ
diff --git a/static/images/user-command.webp b/discord/images/user-command.webp
similarity index 100%
rename from static/images/user-command.webp
rename to discord/images/user-command.webp
diff --git a/static/images/user-install-game-message.webp b/discord/images/user-install-game-message.webp
similarity index 100%
rename from static/images/user-install-game-message.webp
rename to discord/images/user-install-game-message.webp
diff --git a/static/images/user-install-settings.webp b/discord/images/user-install-settings.webp
similarity index 100%
rename from static/images/user-install-settings.webp
rename to discord/images/user-install-settings.webp
diff --git a/discord/logo/dark.png b/discord/logo/dark.png
new file mode 100644
index 0000000000..11c6612c98
Binary files /dev/null and b/discord/logo/dark.png differ
diff --git a/discord/logo/dark.svg b/discord/logo/dark.svg
new file mode 100644
index 0000000000..d99a9245ff
--- /dev/null
+++ b/discord/logo/dark.svg
@@ -0,0 +1,4 @@
+
diff --git a/discord/logo/dot_dev.svg b/discord/logo/dot_dev.svg
new file mode 100644
index 0000000000..867878bdfe
--- /dev/null
+++ b/discord/logo/dot_dev.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/discord/logo/light.png b/discord/logo/light.png
new file mode 100644
index 0000000000..f88870f616
Binary files /dev/null and b/discord/logo/light.png differ
diff --git a/discord/logo/light.svg b/discord/logo/light.svg
new file mode 100644
index 0000000000..e21d461422
--- /dev/null
+++ b/discord/logo/light.svg
@@ -0,0 +1,4 @@
+
diff --git a/discord/scripts/ga.js b/discord/scripts/ga.js
new file mode 100644
index 0000000000..b607914919
--- /dev/null
+++ b/discord/scripts/ga.js
@@ -0,0 +1,4 @@
+window.dataLayer = window.dataLayer || [];
+function gtag() { dataLayer.push(arguments); }
+gtag('js', new Date());
+gtag('config', 'G-5CWMJQ1S0X');
\ No newline at end of file
diff --git a/discord/snippets/card.mdx b/discord/snippets/card.mdx
new file mode 100644
index 0000000000..5aab8f4649
--- /dev/null
+++ b/discord/snippets/card.mdx
@@ -0,0 +1,23 @@
+export const IntroCard = ({ img, href, title, description }) => {
+ return (
+
+
+
+ 
+
+
+
+ {title}
+
+
+ {description}
+
+
+
+
+ );
+};
\ No newline at end of file
diff --git a/discord/snippets/discord-social-sdk/callouts/console-access.mdx b/discord/snippets/discord-social-sdk/callouts/console-access.mdx
new file mode 100644
index 0000000000..8f746f80df
--- /dev/null
+++ b/discord/snippets/discord-social-sdk/callouts/console-access.mdx
@@ -0,0 +1,3 @@
+
+To use the Discord Social SDK in your console games, you will need to request middleware approval and be an approved developer for the target console. Check out [this article](https://support-dev.discord.com/hc/en-us/articles/30209074764183) to learn more.
+
diff --git a/discord/snippets/discord-social-sdk/callouts/limited-access.mdx b/discord/snippets/discord-social-sdk/callouts/limited-access.mdx
new file mode 100644
index 0000000000..07bb468eae
--- /dev/null
+++ b/discord/snippets/discord-social-sdk/callouts/limited-access.mdx
@@ -0,0 +1,6 @@
+
+This feature is currently available with
+[limited access](/developers/docs/discord-social-sdk/core-concepts/communication-features#limited-access). To apply for full access
+to closed beta features, or to reach out to Discord directly to discuss your game, please fill out
+[this form](https://discord.com/developers/social-sdk-closed-beta-access-request-form).
+
\ No newline at end of file
diff --git a/discord/snippets/discord-social-sdk/callouts/oauth-comms-scopes.mdx b/discord/snippets/discord-social-sdk/callouts/oauth-comms-scopes.mdx
new file mode 100644
index 0000000000..1e20bb44ca
--- /dev/null
+++ b/discord/snippets/discord-social-sdk/callouts/oauth-comms-scopes.mdx
@@ -0,0 +1,7 @@
+
+To utilize this communication feature, you must enable [`Client::GetDefaultCommunicationScopes`] in your OAuth Scope configuration.
+See the [OAuth Scopes Core Concepts Guide](/developers/docs/discord-social-sdk/core-concepts/oauth2-scopes) for more details.
+
+
+{/* Autogenerated Reference Links */}
+[`Client::GetDefaultCommunicationScopes`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a71499da752fbdc2d4326ae0fd36c0dd1
\ No newline at end of file
diff --git a/discord/snippets/discord-social-sdk/callouts/public-client.mdx b/discord/snippets/discord-social-sdk/callouts/public-client.mdx
new file mode 100644
index 0000000000..96fe5d6caf
--- /dev/null
+++ b/discord/snippets/discord-social-sdk/callouts/public-client.mdx
@@ -0,0 +1,3 @@
+
+This method requires enabling **Public Client** for your app. Most games will not want to ship with this enabled. [Learn more](/developers/docs/discord-social-sdk/core-concepts/oauth2-scopes#oauth2-client-types)
+
\ No newline at end of file
diff --git a/discord/snippets/discord-social-sdk/callouts/rate-limit.mdx b/discord/snippets/discord-social-sdk/callouts/rate-limit.mdx
new file mode 100644
index 0000000000..d62d7bb73a
--- /dev/null
+++ b/discord/snippets/discord-social-sdk/callouts/rate-limit.mdx
@@ -0,0 +1,5 @@
+
+This feature is currently available with rate limits.
+To remove the rate limits for your game, please follow
+[Communication Features: Applying for Rate Limit Removal](/developers/docs/discord-social-sdk/core-concepts/communication-features#applying-for-rate-limit-removal).
+
\ No newline at end of file
diff --git a/discord/snippets/discord-social-sdk/callouts/sony.mdx b/discord/snippets/discord-social-sdk/callouts/sony.mdx
new file mode 100644
index 0000000000..7ed72c4255
--- /dev/null
+++ b/discord/snippets/discord-social-sdk/callouts/sony.mdx
@@ -0,0 +1,8 @@
+
+Exception: Prohibited Off-Platform Interactions by Sony
+For integrations experienced on Sony Platforms (e.g. PlayStation 5)…
+
1. **Do not allow access to Account Linking** entry points.
+
2. **Do not allow access to Linked Channels**.
+
3. **Limit messaging and Invites to other players currently playing** the game.
+
4. **Do not display off-platform presence and logos** (including Discord).
+
\ No newline at end of file
diff --git a/discord/snippets/discord-social-sdk/callouts/support.mdx b/discord/snippets/discord-social-sdk/callouts/support.mdx
new file mode 100644
index 0000000000..c8f9c6c069
--- /dev/null
+++ b/discord/snippets/discord-social-sdk/callouts/support.mdx
@@ -0,0 +1,3 @@
+Need help? Join the [Discord Developers Server](https://discord.gg/discord-developers) and share questions in the `#social-sdk-dev-help` channel for support from the community.
+
+If you encounter a bug while working with the Social SDK, please report it here: https://dis.gd/social-sdk-bug-report
diff --git a/discord/snippets/discord-social-sdk/partials/dylib-mac-error.mdx b/discord/snippets/discord-social-sdk/partials/dylib-mac-error.mdx
new file mode 100644
index 0000000000..9ae08b4439
--- /dev/null
+++ b/discord/snippets/discord-social-sdk/partials/dylib-mac-error.mdx
@@ -0,0 +1,14 @@
+
+On Mac you may get the error "libdiscord_partner_sdk.dylib" Not Opened because Apple couldn't verify it. If this happens press **Done** on the popup.
+
+
+
+You'll need to open your **System Settings > Privacy & Security** and scroll down to the **Security** section. It will tell you "libdiscord_partner_sdk.dylib" was blocked to protect your Mac. Press **Open Anyway** and try running again.
+
+
+
+Now when you get the pop up you'll have the option to select **Open Anyway** and it will be able to use it successfully.
+
+
+
+
\ No newline at end of file
diff --git a/discord/snippets/discord-social-sdk/partials/getting-started.mdx b/discord/snippets/discord-social-sdk/partials/getting-started.mdx
new file mode 100644
index 0000000000..e66c14149b
--- /dev/null
+++ b/discord/snippets/discord-social-sdk/partials/getting-started.mdx
@@ -0,0 +1,35 @@
+## Step 1: Create a Discord Developer Team
+
+Before you start, you'll need to create a developer team on the Discord Developer Portal. This team will be used to manage your Discord applications and SDK integrations.
+
+If you already have a team configured, you can skip this step.
+
+1. Create a developer team on the [Discord Developer Portal](https://discord.com/developers/teams).
+
+Later, you can invite your team members to your new team to collaborate on your integration.
+
+---
+
+## Step 2: Create a Discord Application
+
+1. Create a new application on the [Discord Developer Portal](https://discord.com/developers/applications) and assign it to your team.
+3. Add a redirect URL in the `OAuth2` tab:
+ - For desktop applications: `http://127.0.0.1/callback` (this can be changed later).
+ - See [`discordpp::Client::Authorize`](https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ace94a58e27545a933d79db32b387a468) for more details on setting up more advanced redirect URIs.
+4. Enable the `Public Client` toggle in the `OAuth2` tab.
+
+
+This guide requires enabling **Public Client** to allow you to get started with the SDK quickly. Most games will not want to ship as a public client. This setting should be reviewed by your team prior to releasing your game. [Learn more about public clients](/developers/docs/discord-social-sdk/core-concepts/oauth2-scopes#oauth2-client-types).
+
+
+---
+
+## Step 3: Enable Discord Social SDK for Your App
+
+Once you've created your Discord application, you'll need to enable the Discord Social SDK for it.
+
+1. From the [Discord Developer Portal](https://discord.com/developers/applications), select your newly created application from Step 2.
+2. In the left sidebar for your app, locate and click the `Getting Started` link under `Discord Social SDK`.
+3. Fill out the form to share details about your game.
+4. Click `Submit` and the Social SDK will be enabled for your application.
+5. Once enabled, you'll find binaries for the Social SDK under `Downloads`.
\ No newline at end of file
diff --git a/discord/snippets/icons/ActivitiesIcon.jsx b/discord/snippets/icons/ActivitiesIcon.jsx
new file mode 100644
index 0000000000..efccb2c34e
--- /dev/null
+++ b/discord/snippets/icons/ActivitiesIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const ActivitiesIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/AppsIcon.jsx b/discord/snippets/icons/AppsIcon.jsx
new file mode 100644
index 0000000000..cd264fdd6c
--- /dev/null
+++ b/discord/snippets/icons/AppsIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const AppsIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/BookCheckIcon.jsx b/discord/snippets/icons/BookCheckIcon.jsx
new file mode 100644
index 0000000000..7a9776b4ff
--- /dev/null
+++ b/discord/snippets/icons/BookCheckIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const BookCheckIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/BrowserIcon.jsx b/discord/snippets/icons/BrowserIcon.jsx
new file mode 100644
index 0000000000..210d880fc6
--- /dev/null
+++ b/discord/snippets/icons/BrowserIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const BrowserIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/BugIcon.jsx b/discord/snippets/icons/BugIcon.jsx
new file mode 100644
index 0000000000..c632b969c9
--- /dev/null
+++ b/discord/snippets/icons/BugIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const BugIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/ChatDotsIcon.jsx b/discord/snippets/icons/ChatDotsIcon.jsx
new file mode 100644
index 0000000000..86b0cdb4ab
--- /dev/null
+++ b/discord/snippets/icons/ChatDotsIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const ChatDotsIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/ChatIcon.jsx b/discord/snippets/icons/ChatIcon.jsx
new file mode 100644
index 0000000000..43d28ba8bf
--- /dev/null
+++ b/discord/snippets/icons/ChatIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const ChatIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/CircleQuestionIcon.jsx b/discord/snippets/icons/CircleQuestionIcon.jsx
new file mode 100644
index 0000000000..e8cd263aa7
--- /dev/null
+++ b/discord/snippets/icons/CircleQuestionIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const CircleQuestionIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/ClydeIcon.jsx b/discord/snippets/icons/ClydeIcon.jsx
new file mode 100644
index 0000000000..77c6f8136c
--- /dev/null
+++ b/discord/snippets/icons/ClydeIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const ClydeIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/CompassIcon.jsx b/discord/snippets/icons/CompassIcon.jsx
new file mode 100644
index 0000000000..4d565074df
--- /dev/null
+++ b/discord/snippets/icons/CompassIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const CompassIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/ContactsIcon.jsx b/discord/snippets/icons/ContactsIcon.jsx
new file mode 100644
index 0000000000..4139090a7b
--- /dev/null
+++ b/discord/snippets/icons/ContactsIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const ContactsIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/CrownIcon.jsx b/discord/snippets/icons/CrownIcon.jsx
new file mode 100644
index 0000000000..75f04522b2
--- /dev/null
+++ b/discord/snippets/icons/CrownIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const CrownIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/DoorEnterIcon.jsx b/discord/snippets/icons/DoorEnterIcon.jsx
new file mode 100644
index 0000000000..10022c1a4d
--- /dev/null
+++ b/discord/snippets/icons/DoorEnterIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const DoorEnterIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/DpadIcon.jsx b/discord/snippets/icons/DpadIcon.jsx
new file mode 100644
index 0000000000..b84a005a9f
--- /dev/null
+++ b/discord/snippets/icons/DpadIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const DpadIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/ForumIcon.jsx b/discord/snippets/icons/ForumIcon.jsx
new file mode 100644
index 0000000000..06e3fbe0b0
--- /dev/null
+++ b/discord/snippets/icons/ForumIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const ForumIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/GameControllerIcon.jsx b/discord/snippets/icons/GameControllerIcon.jsx
new file mode 100644
index 0000000000..18b454b205
--- /dev/null
+++ b/discord/snippets/icons/GameControllerIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const GameControllerIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/GlobeEarthIcon.jsx b/discord/snippets/icons/GlobeEarthIcon.jsx
new file mode 100644
index 0000000000..1035ccddc0
--- /dev/null
+++ b/discord/snippets/icons/GlobeEarthIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const GlobeEarthIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/GroupIcon.jsx b/discord/snippets/icons/GroupIcon.jsx
new file mode 100644
index 0000000000..7d5a4db816
--- /dev/null
+++ b/discord/snippets/icons/GroupIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const GroupIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/HammerIcon.jsx b/discord/snippets/icons/HammerIcon.jsx
new file mode 100644
index 0000000000..2cd575fe34
--- /dev/null
+++ b/discord/snippets/icons/HammerIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const HammerIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/HashmarkIcon.jsx b/discord/snippets/icons/HashmarkIcon.jsx
new file mode 100644
index 0000000000..8269515ef0
--- /dev/null
+++ b/discord/snippets/icons/HashmarkIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const HashmarkIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/InboxIcon.jsx b/discord/snippets/icons/InboxIcon.jsx
new file mode 100644
index 0000000000..634846b0fb
--- /dev/null
+++ b/discord/snippets/icons/InboxIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const InboxIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/LettersIcon.jsx b/discord/snippets/icons/LettersIcon.jsx
new file mode 100644
index 0000000000..746179e063
--- /dev/null
+++ b/discord/snippets/icons/LettersIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const LettersIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/LinkIcon.jsx b/discord/snippets/icons/LinkIcon.jsx
new file mode 100644
index 0000000000..8554452385
--- /dev/null
+++ b/discord/snippets/icons/LinkIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const LinkIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/ListViewIcon.jsx b/discord/snippets/icons/ListViewIcon.jsx
new file mode 100644
index 0000000000..0f4500c3f0
--- /dev/null
+++ b/discord/snippets/icons/ListViewIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const ListViewIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/MagicDoorIcon.jsx b/discord/snippets/icons/MagicDoorIcon.jsx
new file mode 100644
index 0000000000..063964f002
--- /dev/null
+++ b/discord/snippets/icons/MagicDoorIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const MagicDoorIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/MagicWandIcon.jsx b/discord/snippets/icons/MagicWandIcon.jsx
new file mode 100644
index 0000000000..0d3f7a9be5
--- /dev/null
+++ b/discord/snippets/icons/MagicWandIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const MagicWandIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/PaintPaletteIcon.jsx b/discord/snippets/icons/PaintPaletteIcon.jsx
new file mode 100644
index 0000000000..1be1f298de
--- /dev/null
+++ b/discord/snippets/icons/PaintPaletteIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const PaintPaletteIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/PhoneCallIcon.jsx b/discord/snippets/icons/PhoneCallIcon.jsx
new file mode 100644
index 0000000000..4ac52d4644
--- /dev/null
+++ b/discord/snippets/icons/PhoneCallIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const PhoneCallIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/PlayIcon.jsx b/discord/snippets/icons/PlayIcon.jsx
new file mode 100644
index 0000000000..c8f123d745
--- /dev/null
+++ b/discord/snippets/icons/PlayIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const PlayIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/RobotIcon.jsx b/discord/snippets/icons/RobotIcon.jsx
new file mode 100644
index 0000000000..4d6ea650af
--- /dev/null
+++ b/discord/snippets/icons/RobotIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const RobotIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/ShieldIcon.jsx b/discord/snippets/icons/ShieldIcon.jsx
new file mode 100644
index 0000000000..f7bc297815
--- /dev/null
+++ b/discord/snippets/icons/ShieldIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const ShieldIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/ShopIcon.jsx b/discord/snippets/icons/ShopIcon.jsx
new file mode 100644
index 0000000000..ab6459b5cc
--- /dev/null
+++ b/discord/snippets/icons/ShopIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const ShopIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/SlashBoxIcon.jsx b/discord/snippets/icons/SlashBoxIcon.jsx
new file mode 100644
index 0000000000..663f31327f
--- /dev/null
+++ b/discord/snippets/icons/SlashBoxIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const SlashBoxIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/StarShootingIcon.jsx b/discord/snippets/icons/StarShootingIcon.jsx
new file mode 100644
index 0000000000..10474acfdb
--- /dev/null
+++ b/discord/snippets/icons/StarShootingIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const StarShootingIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/TextControllerIcon.jsx b/discord/snippets/icons/TextControllerIcon.jsx
new file mode 100644
index 0000000000..e53b702912
--- /dev/null
+++ b/discord/snippets/icons/TextControllerIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const TextControllerIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/TrophyIcon.jsx b/discord/snippets/icons/TrophyIcon.jsx
new file mode 100644
index 0000000000..1a1a68744c
--- /dev/null
+++ b/discord/snippets/icons/TrophyIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const TrophyIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/UserIcon.jsx b/discord/snippets/icons/UserIcon.jsx
new file mode 100644
index 0000000000..45fb87df50
--- /dev/null
+++ b/discord/snippets/icons/UserIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const UserIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/UserPlatformIcon.jsx b/discord/snippets/icons/UserPlatformIcon.jsx
new file mode 100644
index 0000000000..97e42eb19b
--- /dev/null
+++ b/discord/snippets/icons/UserPlatformIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const UserPlatformIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/UserPlusIcon.jsx b/discord/snippets/icons/UserPlusIcon.jsx
new file mode 100644
index 0000000000..b0ebfa0f14
--- /dev/null
+++ b/discord/snippets/icons/UserPlusIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const UserPlusIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/UserStatusIcon.jsx b/discord/snippets/icons/UserStatusIcon.jsx
new file mode 100644
index 0000000000..070dd6b887
--- /dev/null
+++ b/discord/snippets/icons/UserStatusIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const UserStatusIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/VoiceNormalIcon.jsx b/discord/snippets/icons/VoiceNormalIcon.jsx
new file mode 100644
index 0000000000..b3e2407762
--- /dev/null
+++ b/discord/snippets/icons/VoiceNormalIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const VoiceNormalIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/icons/WrenchIcon.jsx b/discord/snippets/icons/WrenchIcon.jsx
new file mode 100644
index 0000000000..1918f37b73
--- /dev/null
+++ b/discord/snippets/icons/WrenchIcon.jsx
@@ -0,0 +1,3 @@
+// AUTOGENERATED BY tools/icons/generate-icons.js: DO NOT MODIFY DIRECTLY
+
+export const WrenchIcon = (props) => ();
\ No newline at end of file
diff --git a/discord/snippets/linkbutton.jsx b/discord/snippets/linkbutton.jsx
new file mode 100644
index 0000000000..2157601510
--- /dev/null
+++ b/discord/snippets/linkbutton.jsx
@@ -0,0 +1,7 @@
+export const LinkButton = ({ children, to, color }) => {
+ return (
+
+ {children}
+
+ );
+};
\ No newline at end of file
diff --git a/discord/snippets/manualanchor.jsx b/discord/snippets/manualanchor.jsx
new file mode 100644
index 0000000000..6bc490e278
--- /dev/null
+++ b/discord/snippets/manualanchor.jsx
@@ -0,0 +1,5 @@
+export const ManualAnchor = ({ id }) => {
+ return (
+
+ );
+};
\ No newline at end of file
diff --git a/discord/snippets/monospace.jsx b/discord/snippets/monospace.jsx
new file mode 100644
index 0000000000..3b1a2bb4a6
--- /dev/null
+++ b/discord/snippets/monospace.jsx
@@ -0,0 +1,7 @@
+export const Monospace = ({ method, children }) => {
+ return (
+
+ {children}
+
+ );
+};
\ No newline at end of file
diff --git a/discord/snippets/route.jsx b/discord/snippets/route.jsx
new file mode 100644
index 0000000000..e9540c308e
--- /dev/null
+++ b/discord/snippets/route.jsx
@@ -0,0 +1,8 @@
+export const Route = ({ method, children }) => {
+ return (
+
+ {method}
+ {children}
+
+ );
+};
\ No newline at end of file
diff --git a/discord/snippets/snowflake.jsx b/discord/snippets/snowflake.jsx
new file mode 100644
index 0000000000..dcd42b8a62
--- /dev/null
+++ b/discord/snippets/snowflake.jsx
@@ -0,0 +1,159 @@
+export const Snowflake = () => {
+ return (
+
+
+
+ );
+}
diff --git a/discord/styles/api.css b/discord/styles/api.css
new file mode 100644
index 0000000000..d0a31fd862
--- /dev/null
+++ b/discord/styles/api.css
@@ -0,0 +1,21 @@
+/* Hide link icon for anchors on hover */
+.param-head .absolute {
+ display: none;
+}
+
+.param-head .dark\:text-primary-light:is(.dark *) {
+ color: #929af2;
+ font-weight: bold;
+}
+
+.api-section .py-6 {
+ padding: 0.5rem 0.5rem;
+}
+
+.code-group:first-child {
+ display: none;
+}
+
+#content-side-layout:has(.code-group) {
+ top: 8.5rem;
+}
\ No newline at end of file
diff --git a/discord/styles/changelog.css b/discord/styles/changelog.css
new file mode 100644
index 0000000000..34556fdf6b
--- /dev/null
+++ b/discord/styles/changelog.css
@@ -0,0 +1,6 @@
+#content-area:has(.mdx-content[data-page-href="/src/_props/developers/docs/change-log"]),
+#content-area:has(.mdx-content[data-page-href="/developers/docs/change-log"]) {
+ div#page-context-menu {
+ display: none;
+ }
+}
\ No newline at end of file
diff --git a/discord/styles/fonts.css b/discord/styles/fonts.css
new file mode 100644
index 0000000000..831660693a
--- /dev/null
+++ b/discord/styles/fonts.css
@@ -0,0 +1,49 @@
+/*
+Imports Discord brand font
+ */
+
+ @font-face {
+ font-family: discord;
+ src: url('https://mintlify-assets.b-cdn.net/fonts/discord/discord.woff2');
+ }
+ @font-face {
+ font-family: "gg sans";
+ font-weight: 200;
+ src: url('https://mintlify-assets.b-cdn.net/fonts/discord/gg_200.woff2')
+ }
+
+ @font-face {
+ font-family: "gg sans";
+ font-weight: 400;
+ src: url('https://mintlify-assets.b-cdn.net/fonts/discord/gg_400.woff2');
+ }
+
+ @font-face {
+ font-family: "gg sans";
+ font-weight: 600;
+ src: url('https://mintlify-assets.b-cdn.net/fonts/discord/gg_600.woff2');
+ }
+
+@font-face {
+ font-family: "gg sans";
+ font-weight: 800;
+ src: url('https://mintlify-assets.b-cdn.net/fonts/discord/gg_800.woff2')
+}
+
+body {
+ font-family: "gg sans", var(--font-inter), -apple-system, BlinkMacSystemFont, "Segoe UI", system-ui, sans-serif;
+ font-weight: 400;
+}
+
+h1, h2, h3, h4, h5, h6 {
+ font-family: "gg sans", var(--font-inter), -apple-system, BlinkMacSystemFont, "Segoe UI", system-ui, sans-serif;
+ font-weight: 600;
+}
+
+.\[\&_\*\:not\(h1\2c h2\2c h3\2c h4\2c h5\2c h6\2c h1_\*\2c h2_\*\2c h3_\*\2c h4_\*\2c h5_\*\2c h6_\*\)\]\:font-bodyWeight :not(h1,h2,h3,h4,h5,h6,h1 *,h2 *,h3 *,h4 *,h5 *,h6 *) {
+ font-weight: 400;
+}
+
+
+
+
diff --git a/discord/styles/homepage.css b/discord/styles/homepage.css
new file mode 100644
index 0000000000..13ff1f9e14
--- /dev/null
+++ b/discord/styles/homepage.css
@@ -0,0 +1,62 @@
+#homepage-hero {
+ display: grid;
+
+ margin: -1rem auto 1.5rem auto;
+ background-image: url(https://mintlify-assets.b-cdn.net/discord-back.png);
+ background-size: cover;
+ background-position: center;
+ grid-area: 1/1;
+ border-radius: var(--radius-lg);
+
+ #hero-text {
+ display: flex;
+ grid-area: 1/1;
+ align-self: center;
+ margin: 2rem;
+ gap: 1rem;
+ color: white;
+ }
+
+ #hero-tagline {
+ font-size: 2rem;
+ line-height: 2rem;
+ font-family: 'discord';
+ margin: 2rem 0 0.5rem 0;
+ color: white;
+ }
+
+ #hero-image {
+ width: 300px;
+ height: 300px;
+ display: none;
+ }
+}
+
+@media (min-width: 1024px) {
+ #homepage-hero {
+ #hero-image {
+ display: block;
+ }
+ #hero-tagline {
+ font-size: 4rem;
+ line-height: 4rem;
+ margin-bottom: 0rem;
+ }
+ #hero-text {
+ margin: 4rem;
+ }
+ }
+}
+
+#content-area:has(.mdx-content[data-page-href="/src/_props/developers/docs/intro"]),
+#content-area:has(.mdx-content[data-page-href="/developers/docs/intro"]) {
+ padding-right: 1rem;
+
+ div:has(h1#page-title) {
+ display: none;
+ }
+
+ div#page-context-menu {
+ display: none;
+ }
+}
\ No newline at end of file
diff --git a/discord/styles/linkbutton.css b/discord/styles/linkbutton.css
new file mode 100644
index 0000000000..2f11276640
--- /dev/null
+++ b/discord/styles/linkbutton.css
@@ -0,0 +1,15 @@
+.MDXLinkButton {
+ display: block;
+ color: white !important;
+ font-size: 15px;
+ padding: 10px 16px;
+ border-radius: var(--radius-xs);
+ width: fit-content;
+ height: fit-content;
+ box-sizing: border-box;
+ line-height: 18px;
+
+ &.brand {
+ background-color: var(--brand-500);
+ }
+}
\ No newline at end of file
diff --git a/discord/styles/manualanchor.css b/discord/styles/manualanchor.css
new file mode 100644
index 0000000000..7b9bdbb908
--- /dev/null
+++ b/discord/styles/manualanchor.css
@@ -0,0 +1,10 @@
+
+.MDXManualAnchor {
+ display: inline;
+ width: 100px;
+ height: 10px;
+ background-color: red;
+ position: relative;
+ top: -120px;
+ visibility: hidden;
+}
\ No newline at end of file
diff --git a/discord/styles/monospace.css b/discord/styles/monospace.css
new file mode 100644
index 0000000000..63bb56546a
--- /dev/null
+++ b/discord/styles/monospace.css
@@ -0,0 +1,6 @@
+.MDXMonospace {
+ font-family: var(--font-jetbrains-mono), ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace;
+ font-feature-settings: normal;
+ font-variation-settings: normal;
+ font-size: 1em;
+}
\ No newline at end of file
diff --git a/discord/styles/route.css b/discord/styles/route.css
new file mode 100644
index 0000000000..3406cff0e7
--- /dev/null
+++ b/discord/styles/route.css
@@ -0,0 +1,47 @@
+.MDXRoute {
+ display: flex;
+ align-items: center;
+
+ .verb {
+ font-size: 14px;
+ color: var(--white-500);
+ background-color: var(--primary-600);
+ border: 1px solid var(--primary-500);
+ font-family: var(--font-code);
+ text-transform: uppercase;
+ margin-right: 10px;
+ padding: 4px 8px;
+ padding-bottom: 1.5px;
+ border-radius: var(--radius-md);
+ }
+
+ .url {
+ font-family: var(--font-code);
+ font-size: 16px;
+ }
+
+ .delete {
+ background-color: var(--red-630);
+ border: 1px solid var(--red-500);
+ }
+
+ .get {
+ background-color: var(--brand-700);
+ border: 1px solid var(--brand-530);
+ }
+
+ .patch {
+ background-color: var(--yellow-530);
+ border: 1px solid var(--yellow-400);
+ }
+
+ .post {
+ background-color: var(--green-500);
+ border: 1px solid var(--green-360);
+ }
+
+ .put {
+ background-color: var(--orange-600);
+ border: 1px solid var(--orange-430);
+ }
+}
\ No newline at end of file
diff --git a/discord/styles/snowflake.css b/discord/styles/snowflake.css
new file mode 100644
index 0000000000..a8ab862c13
--- /dev/null
+++ b/discord/styles/snowflake.css
@@ -0,0 +1,52 @@
+
+/* Light mode styles */
+html[style*="color-scheme: light"] .MDXSnowflake {
+ text {
+ fill: black;
+ }
+
+ .arrow {
+ fill: oklab(0.251834 0.00131807 -0.008479);
+ }
+}
+
+html[style*="color-scheme: dark"] .MDXSnowflake {
+ text {
+ fill: white;
+ }
+}
+
+.MDXSnowflake {
+ display: flex;
+ justify-content: center;
+ margin-top: 40px;
+ margin-bottom: 40px;
+
+
+ .arrow {
+ fill: oklab(0.751834 0.00131807 -0.008479);
+ }
+
+ .header {
+ font-weight: bold;
+ font-size: 16px;
+
+ &.group1 {
+ fill: oklab(0.747617 0.00671133 -0.126112);
+ }
+
+ &.group2 {
+ fill: oklab(0.773758 0.0289854 0.0857202);
+ }
+
+ &.group3 {
+ fill: oklab(0.723746 0.150768 0.055049);
+ }
+
+ &.group4 {
+ fill: oklab(0.700146 -0.0932133 -0.0629166);
+ }
+ }
+
+
+}
diff --git a/discord/styles/theme.css b/discord/styles/theme.css
new file mode 100644
index 0000000000..ab00989448
--- /dev/null
+++ b/discord/styles/theme.css
@@ -0,0 +1,536 @@
+/*
+Below are tweaks to Mintlify theme CSS.
+ */
+
+ /*
+Mintlify's way of setting background color can
+cause black flashes at bottom of page
+ */
+body {
+ background-color: #ffffff;
+
+}
+body:is(.dark *) {
+ background-color: #36373e;
+}
+
+/* Allow the content to stretch as wide as the page body */
+#content-container {
+ max-width: unset;
+}
+
+/* Set page width of navigation items */
+.max-w-8xl,
+/* Set page width of content */
+.peer.is-not-center~.peer-\[\.is-not-center\]\:max-w-8xl {
+ max-width: 110rem;
+}
+
+/*
+Make HRs thicker
+*/
+hr {
+ border: none;
+ margin: 48px 0;
+ height: 1px;
+ background-color: #e6e6e7;
+}
+
+hr:is(.dark *) {
+ background-color: #606169;
+}
+/*
+.prose is the container for the main markdown content
+ */
+.prose,.prose-sm {
+ font-size: 1rem;
+ line-height: 1.5rem;
+ /* Turn all text white */
+ p :is(.dark *) {
+ color: white;
+ }
+
+ /*
+ Ensure code tags don't wrap when inline in text
+ */
+ code {
+ white-space: pre;
+ overflow-x: auto;
+ overflow-y: hidden;
+ line-height: 1.1rem;
+ }
+
+ code span {
+ font-size: 0.85rem;
+ line-height: 1rem;
+ }
+
+ .code-block {
+ margin-top: 1.5rem;
+ margin-bottom: 1.5rem;
+ }
+
+ /* .accordion {
+ border-radius: var(--radius-sm);
+
+ summary {
+ border-radius: calc(var(--radius-sm) -1px) var(--radius-sm) 0 0;
+ }
+ } */
+
+ /*
+ Ensure lists have reasonable padding
+ */
+ li {
+ margin: 0px;
+ }
+ /*
+ Make title bold
+ */
+ h1, h2, h3, h4, h5, h6 {
+ font-weight: bold;
+
+ /* Hide link icon for anchors on hover */
+ .absolute {
+ display: none;
+ }
+ }
+
+ /*
+ Make bold, strong tags bold
+ */
+ b, strong {
+ font-weight: 800;
+ }
+
+ [data-component-part=update-label] {
+ font-size: 1rem;
+ }
+ /*
+ Make changelog tags resemble tags
+ */
+ [data-component-part=update-tag] {
+ opacity: 0.7;
+ padding: 0.1rem 0.3rem;
+ display: inline-block;
+ font-size: 0.8rem;
+ border: 1px solid #e6e6e7;
+ }
+ [data-component-part=update-tag]:is(.dark *) {
+ opacity: 0.5;
+ border-color: white;
+ }
+}
+
+/*
+This pushes all shades of gray to a full white,
+which is more similar to legacy docs.
+
+However it may add some visual clutter.
+ */
+.text-gray-200:is(.light *),
+.text-gray-400:is(.light *),
+.text-gray-500:is(.light *),
+.text-gray-600:is(.light *),
+.text-gray-800:is(.light *) {
+ color: black;
+ --tw-text-opacity: 1;
+}
+
+.dark\:text-gray-200:is(.dark *),
+.dark\:text-gray-400:is(.dark *),
+.dark\:text-gray-500:is(.dark *),
+.dark\:text-gray-600:is(.dark *),
+.dark\:text-gray-800:is(.dark *) {
+ color: white;
+}
+
+/*
+Remove eyebrow / breadcrumbs
+ */
+.eyebrow {
+ display: none;
+}
+
+/*
+Style left-hand navigation headers
+ */
+#sidebar-title {
+ font-family: "gg sans","Noto Sans","Helvetica Neue",Helvetica,Arial,sans-serif;
+ text-transform: uppercase;
+ font-size: 12px;
+ line-height: 1.3333333333333333;
+ font-weight: 600;
+}
+
+/*
+Indent left-hand navigation areas
+ */
+#sidebar-group {
+ margin-left: 1rem;
+
+ li > a, [data-group-tag] > div {
+ padding: 0.1rem;
+ padding-right: 0.5rem;
+ border-radius: var(--radius-sm);
+ }
+
+}
+
+/*
+Reduce spacing between left-hand categories
+ */
+#navigation-items > div:not(:first-of-type) {
+ margin-top: 1rem;
+}
+
+
+.dark\:text-primary-light:is(.dark *) {
+ color: rgba(255, 255, 255, 0.8);
+}
+
+/* Inline code blocks */
+:not(pre)>code:is(.dark *) {
+ background-color: #232428;
+ color: white;
+}
+
+/*
+Darken table of contents (right hand) items
+ */
+.toc-item a {
+ opacity: 0.7;
+ border-width: 0px;
+}
+
+/*
+Lighten table of contents selected item
+ */
+.toc-item a.dark\:text-primary-light:is(.dark *) {
+ opacity: 1;
+ color: white;
+}
+
+/*
+Hide table of contents items below top depth in tree
+ */
+.toc-item:not([data-depth="0"]) {
+ text-decoration: underline;
+ display: none;
+}
+
+/*
+Tighten spacing between table of contents items
+ */
+.toc-item a {
+ padding: 0px;
+}
+
+/*
+Style anchor tags as blue without underline
+ */
+.prose a:is(.dark *):not(.card), .prose a:is(.dark *) code, .prose a:is(.dark *) strong{
+ color: #7aaef3;
+ text-decoration: none;
+ border-bottom: 0px;
+}
+
+/*
+Fix code blocks inside links that break page width
+ */
+.prose a code {
+ white-space: pre-wrap;
+ word-break: break-all;
+ overflow-wrap: break-word;
+ max-width: 100%;
+}
+
+/*
+Fix MDXRoute components breaking page width on mobile
+ */
+@media (max-width: 768px) {
+ .MDXRoute {
+ flex-wrap: wrap;
+ gap: 0.5rem;
+ }
+
+ .MDXRoute .url {
+ word-break: break-all;
+ overflow-wrap: break-word;
+ max-width: 100%;
+ flex: 1;
+ min-width: 0;
+ }
+}
+
+/*
+Fix inline code blocks breaking page width in prose content
+ */
+.prose code:not(pre code) {
+ word-break: break-all;
+ overflow-wrap: break-word;
+ white-space: pre-wrap;
+ max-width: 100%;
+}
+
+.callout {
+ padding: 0.5rem 1rem;
+ border-radius: var(--radius-sm);
+}
+
+.callout code {
+ white-space: pre-wrap;
+ word-break: break-word;
+ overflow-wrap: break-word;
+}
+
+/* Expand tables horizontally */
+.prose table {
+ display: table;
+ /* Uncomment this and the th,td,tr below to wrap tables */
+ table-layout: fixed;
+}
+
+th, td, tr {
+ word-wrap: break-word;
+}
+
+td {
+ overflow: hidden;
+}
+
+td code {
+ white-space: pre-wrap;
+ word-break: break-word;
+ overflow-wrap: break-word;
+}
+
+/*
+Set table header styles
+ */
+table > thead > tr > th {
+ font-family: "gg sans","Noto Sans","Helvetica Neue",Helvetica,Arial,sans-serif;
+ text-transform: uppercase;
+ font-size: 12px;
+ line-height: 1.3333333333333333;
+ font-weight: 800 !important;
+ text-align: left;
+}
+
+/*
+Add padding to table cells
+ */
+.prose th, .prose td {
+ padding: 0.5rem;
+ padding-inline: 0.5rem;
+}
+
+/*
+Set default table row color
+ */
+
+tr:is(.dark *) {
+ background-color: #323338;
+ border-bottom: 2px solid #161718;
+}
+
+/*
+Alternate table row colors with darker color
+ */
+tr:nth-child(even) {
+ background-color: #ebedef;
+}
+tr:nth-child(even):is(.dark *) {
+ background-color: #232428;
+}
+
+.dark\:bg-zinc-500\/10:is(.dark *) {
+ background-color: #353c4b;
+ border-color: #05aafc;
+}
+
+/*
+Hide bottom of page pagination
+ */
+#pagination {
+ display: none;
+}
+
+/*
+On change log only, we remove some HR spacing
+*/
+[data-page-title="Change Log"] {
+ hr {
+ padding: 0px;
+ margin: 0px;
+ }
+}
+
+/*
+Shrink and lighten accordian description
+ */
+[data-component-part=accordion-description] {
+ font-size: 0.8rem;
+ opacity: 0.7;
+}
+
+
+/*
+ Move content up to cover eyebrow / breadcrumb space, but only when wide (see media queries below)
+*/
+#content-container > div:first-of-type {
+ padding-top: 8rem;
+}
+
+/*
+Very slightly shrink left hand nav
+*/
+#sidebar {
+ width: 17rem;
+}
+
+/*
+Hide breadcrumbs when there is only one item
+*/
+header > div > .flex-row > div {
+ display: none;
+}
+
+@media (min-width: 1024px) {
+ /* Middle breakpoint */
+ /*
+ Show breadcrumbs when the page is wide and there are multiple items
+ */
+ header > div > .flex-row > div:not(:only-child) {
+ display: flex;
+ }
+
+ /* Content mostly at top when not mobile */
+ #content-container > div:first-of-type {
+ padding-top: 1.5rem;
+ }
+
+ #content-container #content-side-layout {
+ padding-top: 0rem;
+ }
+
+ /* Widen main content on left and right */
+ #content-area:not(:has(div div.not-found-container)) {
+ margin-left: -5rem;
+ margin-right: 1rem;
+ }
+ /*
+ Hide TOC when only one category
+ */
+ #sidebar:has(#navigation-items > ul:only-child) {
+ display: none;
+
+ + #content-container:has([data-page-title="Change Log"]) {
+ margin-left: -17rem;
+ }
+ }
+}
+
+@media (min-width: 1280px) {
+ /* Wide breakpoint */
+
+ /* Remove gap between main content and right TOC */
+ .gap-12 {
+ gap: 0rem;
+ }
+
+ /*
+ Move TOC up to cover eyebrow / breadcrumb space
+ */
+ #table-of-contents {
+ padding-top: 1.5rem;
+ }
+}
+
+/* Fix LEGACY tag in nav */
+.dark .nav-tag-pill {
+ background-color: black;
+}
+
+.nav-tag-pill {
+ padding: 0.1rem 0.2rem;
+ border-radius: var(--radius-sm);
+}
+
+.mdx-content {
+ margin-top: 1rem;
+}
+
+/* Set sidebar icon color */
+[data-title="Developer Terms of Service"] svg, [data-title="Developer Policy"] svg {
+ display: none;
+}
+[data-title] > a > svg:first-child:is(.dark *) {
+ display: block;
+ background-color: white;
+}
+
+/* Add some spacing to icons on cards and set a suble background color */
+[data-component-part=card-icon] {
+ width: 54px;
+ height: 54px;
+ padding: 15px;
+ margin-right: 0.5rem;
+ background-color: rgba(255, 255, 255, 0.05);
+ border-radius: var(--radius-sm);
+ align-self: start;
+ margin-top: 0.5rem;
+}
+
+[data-component-part=card-icon]:is(.light *) {
+ background-color: rgba(0, 0, 0, 0.05);
+}
+
+/* Light mode overrides */
+html[style*="color-scheme: light"] {
+ /* Style inline code blocks with light background */
+ .prose code:not(pre code) {
+ background-color: #f0f1f5;
+ }
+
+
+ .prose :where(a):not(:where([class~=not-prose],[class~=not-prose] *)) {
+ border-bottom: none;
+ color: rgb(var(--primary));
+ }
+}
+
+.chat-assistant-floating-input, #assistant-bar-placeholder {
+ display: none;
+}
+
+#banner {
+ a, a:visited {
+ color: white;
+ font-weight: bold;
+ }
+
+ a:hover {
+ border-bottom: 1px solid white;
+ }
+}
+
+/* Add top margin when banner is present - mobile only */
+@media (max-width: 1023px) {
+ body:has(#banner) #content-container {
+ margin-top: 64px;
+ }
+
+ /* Override banner styling on mobile */
+ #banner {
+ button {
+ position: relative;
+ top: unset;
+ right: unset;
+ display: flex;
+ --tw-translate-y: 0;
+ padding: 10px;
+ }
+ font-size: 0.9rem;
+ }
+}
\ No newline at end of file
diff --git a/discord/styles/variables.css b/discord/styles/variables.css
new file mode 100644
index 0000000000..993a228b4b
--- /dev/null
+++ b/discord/styles/variables.css
@@ -0,0 +1,483 @@
+:root {
+ /* Border Radius */
+ --radius-none: 0px;
+ --radius-xs: 4px;
+ --radius-sm: 8px;
+ --radius-md: 12px;
+ --radius-lg: 16px;
+
+ /* Colors */
+ --saturation-factor: 1;
+ --red-100: hsl(var(--red-100-hsl) / 1);
+ --red-100-hsl: 350 calc(var(--saturation-factor, 1) * 75%) 98.431%;
+ --red-130: hsl(var(--red-130-hsl) / 1);
+ --red-130-hsl: 0 calc(var(--saturation-factor, 1) * 83.333%) 97.647%;
+ --red-160: hsl(var(--red-160-hsl) / 1);
+ --red-160-hsl: 0 calc(var(--saturation-factor, 1) * 90.909%) 95.686%;
+ --red-200: hsl(var(--red-200-hsl) / 1);
+ --red-200-hsl: 358.125 calc(var(--saturation-factor, 1) * 88.889%) 92.941%;
+ --red-230: hsl(var(--red-230-hsl) / 1);
+ --red-230-hsl: 358.696 calc(var(--saturation-factor, 1) * 85.185%) 89.412%;
+ --red-260: hsl(var(--red-260-hsl) / 1);
+ --red-260-hsl: 359.077 calc(var(--saturation-factor, 1) * 89.041%) 85.686%;
+ --red-300: hsl(var(--red-300-hsl) / 1);
+ --red-300-hsl: 358.588 calc(var(--saturation-factor, 1) * 91.398%) 81.765%;
+ --red-330: hsl(var(--red-330-hsl) / 1);
+ --red-330-hsl: 358.857 calc(var(--saturation-factor, 1) * 91.304%) 77.451%;
+ --red-345: hsl(var(--red-345-hsl) / 1);
+ --red-345-hsl: 358.168 calc(var(--saturation-factor, 1) * 92.908%) 72.353%;
+ --red-360: hsl(var(--red-360-hsl) / 1);
+ --red-360-hsl: 358.471 calc(var(--saturation-factor, 1) * 91.813%) 66.471%;
+ --red-400: hsl(var(--red-400-hsl) / 1);
+ --red-400-hsl: 358.659 calc(var(--saturation-factor, 1) * 87.317%) 59.804%;
+ --red-430: hsl(var(--red-430-hsl) / 1);
+ --red-430-hsl: 358.16 calc(var(--saturation-factor, 1) * 68.776%) 53.529%;
+ --red-460: hsl(var(--red-460-hsl) / 1);
+ --red-460-hsl: 358.705 calc(var(--saturation-factor, 1) * 59.149%) 46.078%;
+ --red-500: hsl(var(--red-500-hsl) / 1);
+ --red-500-hsl: 359.504 calc(var(--saturation-factor, 1) * 60.199%) 39.412%;
+ --red-530: hsl(var(--red-530-hsl) / 1);
+ --red-530-hsl: 358.919 calc(var(--saturation-factor, 1) * 63.429%) 34.314%;
+ --red-560: hsl(var(--red-560-hsl) / 1);
+ --red-560-hsl: 358.788 calc(var(--saturation-factor, 1) * 63.871%) 30.392%;
+ --red-600: hsl(var(--red-600-hsl) / 1);
+ --red-600-hsl: 358.636 calc(var(--saturation-factor, 1) * 64.706%) 26.667%;
+ --red-630: hsl(var(--red-630-hsl) / 1);
+ --red-630-hsl: 358.5 calc(var(--saturation-factor, 1) * 65.574%) 23.922%;
+ --red-660: hsl(var(--red-660-hsl) / 1);
+ --red-660-hsl: 359.155 calc(var(--saturation-factor, 1) * 65.138%) 21.373%;
+ --red-700: hsl(var(--red-700-hsl) / 1);
+ --red-700-hsl: 358.125 calc(var(--saturation-factor, 1) * 66.667%) 18.824%;
+ --red-730: hsl(var(--red-730-hsl) / 1);
+ --red-730-hsl: 358.929 calc(var(--saturation-factor, 1) * 66.667%) 16.471%;
+ --red-760: hsl(var(--red-760-hsl) / 1);
+ --red-760-hsl: 358.846 calc(var(--saturation-factor, 1) * 70.27%) 14.51%;
+ --red-800: hsl(var(--red-800-hsl) / 1);
+ --red-800-hsl: 358.636 calc(var(--saturation-factor, 1) * 68.75%) 12.549%;
+ --red-830: hsl(var(--red-830-hsl) / 1);
+ --red-830-hsl: 358.378 calc(var(--saturation-factor, 1) * 67.273%) 10.784%;
+ --red-860: hsl(var(--red-860-hsl) / 1);
+ --red-860-hsl: 0 calc(var(--saturation-factor, 1) * 66.667%) 9.412%;
+ --red-900: hsl(var(--red-900-hsl) / 1);
+ --red-900-hsl: 0 calc(var(--saturation-factor, 1) * 70%) 7.843%;
+ --orange-100: hsl(var(--orange-100-hsl) / 1);
+ --orange-100-hsl: 18 calc(var(--saturation-factor, 1) * 100%) 98.039%;
+ --orange-130: hsl(var(--orange-130-hsl) / 1);
+ --orange-130-hsl: 23.333 calc(var(--saturation-factor, 1) * 100%) 96.471%;
+ --orange-160: hsl(var(--orange-160-hsl) / 1);
+ --orange-160-hsl: 21.29 calc(var(--saturation-factor, 1) * 93.939%) 93.529%;
+ --orange-200: hsl(var(--orange-200-hsl) / 1);
+ --orange-200-hsl: 21.25 calc(var(--saturation-factor, 1) * 92.308%) 89.804%;
+ --orange-230: hsl(var(--orange-230-hsl) / 1);
+ --orange-230-hsl: 23.514 calc(var(--saturation-factor, 1) * 92.5%) 84.314%;
+ --orange-260: hsl(var(--orange-260-hsl) / 1);
+ --orange-260-hsl: 23.301 calc(var(--saturation-factor, 1) * 94.495%) 78.627%;
+ --orange-300: hsl(var(--orange-300-hsl) / 1);
+ --orange-300-hsl: 25.468 calc(var(--saturation-factor, 1) * 94.558%) 71.176%;
+ --orange-330: hsl(var(--orange-330-hsl) / 1);
+ --orange-330-hsl: 27 calc(var(--saturation-factor, 1) * 94.737%) 62.745%;
+ --orange-345: hsl(var(--orange-345-hsl) / 1);
+ --orange-345-hsl: 28.342 calc(var(--saturation-factor, 1) * 87.665%) 55.49%;
+ --orange-360: hsl(var(--orange-360-hsl) / 1);
+ --orange-360-hsl: 26.145 calc(var(--saturation-factor, 1) * 71.315%) 50.784%;
+ --orange-400: hsl(var(--orange-400-hsl) / 1);
+ --orange-400-hsl: 25.443 calc(var(--saturation-factor, 1) * 67.521%) 45.882%;
+ --orange-430: hsl(var(--orange-430-hsl) / 1);
+ --orange-430-hsl: 24.681 calc(var(--saturation-factor, 1) * 69.458%) 39.804%;
+ --orange-460: hsl(var(--orange-460-hsl) / 1);
+ --orange-460-hsl: 23.538 calc(var(--saturation-factor, 1) * 72.222%) 35.294%;
+ --orange-500: hsl(var(--orange-500-hsl) / 1);
+ --orange-500-hsl: 22.314 calc(var(--saturation-factor, 1) * 76.101%) 31.176%;
+ --orange-530: hsl(var(--orange-530-hsl) / 1);
+ --orange-530-hsl: 21.869 calc(var(--saturation-factor, 1) * 76.978%) 27.255%;
+ --orange-560: hsl(var(--orange-560-hsl) / 1);
+ --orange-560-hsl: 21.474 calc(var(--saturation-factor, 1) * 77.236%) 24.118%;
+ --orange-600: hsl(var(--orange-600-hsl) / 1);
+ --orange-600-hsl: 22.857 calc(var(--saturation-factor, 1) * 79.245%) 20.784%;
+ --orange-630: hsl(var(--orange-630-hsl) / 1);
+ --orange-630-hsl: 22.105 calc(var(--saturation-factor, 1) * 79.167%) 18.824%;
+ --orange-660: hsl(var(--orange-660-hsl) / 1);
+ --orange-660-hsl: 22.388 calc(var(--saturation-factor, 1) * 78.824%) 16.667%;
+ --orange-700: hsl(var(--orange-700-hsl) / 1);
+ --orange-700-hsl: 21.724 calc(var(--saturation-factor, 1) * 76.316%) 14.902%;
+ --orange-730: hsl(var(--orange-730-hsl) / 1);
+ --orange-730-hsl: 21.923 calc(var(--saturation-factor, 1) * 78.788%) 12.941%;
+ --orange-760: hsl(var(--orange-760-hsl) / 1);
+ --orange-760-hsl: 21.333 calc(var(--saturation-factor, 1) * 78.947%) 11.176%;
+ --orange-800: hsl(var(--orange-800-hsl) / 1);
+ --orange-800-hsl: 21 calc(var(--saturation-factor, 1) * 80%) 9.804%;
+ --orange-830: hsl(var(--orange-830-hsl) / 1);
+ --orange-830-hsl: 20 calc(var(--saturation-factor, 1) * 76.744%) 8.431%;
+ --orange-860: hsl(var(--orange-860-hsl) / 1);
+ --orange-860-hsl: 20 calc(var(--saturation-factor, 1) * 72.973%) 7.255%;
+ --orange-900: hsl(var(--orange-900-hsl) / 1);
+ --orange-900-hsl: 25.714 calc(var(--saturation-factor, 1) * 72.414%) 5.686%;
+ --yellow-100: hsl(var(--yellow-100-hsl) / 1);
+ --yellow-100-hsl: 33.75 calc(var(--saturation-factor, 1) * 100%) 96.863%;
+ --yellow-130: hsl(var(--yellow-130-hsl) / 1);
+ --yellow-130-hsl: 31.304 calc(var(--saturation-factor, 1) * 100%) 95.49%;
+ --yellow-160: hsl(var(--yellow-160-hsl) / 1);
+ --yellow-160-hsl: 32.727 calc(var(--saturation-factor, 1) * 100%) 91.373%;
+ --yellow-200: hsl(var(--yellow-200-hsl) / 1);
+ --yellow-200-hsl: 35 calc(var(--saturation-factor, 1) * 97.297%) 85.49%;
+ --yellow-230: hsl(var(--yellow-230-hsl) / 1);
+ --yellow-230-hsl: 36.637 calc(var(--saturation-factor, 1) * 96.581%) 77.059%;
+ --yellow-260: hsl(var(--yellow-260-hsl) / 1);
+ --yellow-260-hsl: 40.656 calc(var(--saturation-factor, 1) * 96.825%) 62.941%;
+ --yellow-300: hsl(var(--yellow-300-hsl) / 1);
+ --yellow-300-hsl: 40.421 calc(var(--saturation-factor, 1) * 86.364%) 56.863%;
+ --yellow-330: hsl(var(--yellow-330-hsl) / 1);
+ --yellow-330-hsl: 40 calc(var(--saturation-factor, 1) * 75.309%) 52.353%;
+ --yellow-345: hsl(var(--yellow-345-hsl) / 1);
+ --yellow-345-hsl: 39.545 calc(var(--saturation-factor, 1) * 70.968%) 48.627%;
+ --yellow-360: hsl(var(--yellow-360-hsl) / 1);
+ --yellow-360-hsl: 39.018 calc(var(--saturation-factor, 1) * 74.429%) 42.941%;
+ --yellow-400: hsl(var(--yellow-400-hsl) / 1);
+ --yellow-400-hsl: 37.792 calc(var(--saturation-factor, 1) * 78.571%) 38.431%;
+ --yellow-430: hsl(var(--yellow-430-hsl) / 1);
+ --yellow-430-hsl: 37.447 calc(var(--saturation-factor, 1) * 84.431%) 32.745%;
+ --yellow-460: hsl(var(--yellow-460-hsl) / 1);
+ --yellow-460-hsl: 36.279 calc(var(--saturation-factor, 1) * 87.755%) 28.824%;
+ --yellow-500: hsl(var(--yellow-500-hsl) / 1);
+ --yellow-500-hsl: 35.5 calc(var(--saturation-factor, 1) * 93.75%) 25.098%;
+ --yellow-530: hsl(var(--yellow-530-hsl) / 1);
+ --yellow-530-hsl: 34.857 calc(var(--saturation-factor, 1) * 92.92%) 22.157%;
+ --yellow-560: hsl(var(--yellow-560-hsl) / 1);
+ --yellow-560-hsl: 33.83 calc(var(--saturation-factor, 1) * 94%) 19.608%;
+ --yellow-600: hsl(var(--yellow-600-hsl) / 1);
+ --yellow-600-hsl: 34.815 calc(var(--saturation-factor, 1) * 93.103%) 17.059%;
+ --yellow-630: hsl(var(--yellow-630-hsl) / 1);
+ --yellow-630-hsl: 34.521 calc(var(--saturation-factor, 1) * 92.405%) 15.49%;
+ --yellow-660: hsl(var(--yellow-660-hsl) / 1);
+ --yellow-660-hsl: 34.688 calc(var(--saturation-factor, 1) * 91.429%) 13.725%;
+ --yellow-700: hsl(var(--yellow-700-hsl) / 1);
+ --yellow-700-hsl: 34.286 calc(var(--saturation-factor, 1) * 90.323%) 12.157%;
+ --yellow-730: hsl(var(--yellow-730-hsl) / 1);
+ --yellow-730-hsl: 32.941 calc(var(--saturation-factor, 1) * 92.727%) 10.784%;
+ --yellow-760: hsl(var(--yellow-760-hsl) / 1);
+ --yellow-760-hsl: 32.727 calc(var(--saturation-factor, 1) * 91.667%) 9.412%;
+ --yellow-800: hsl(var(--yellow-800-hsl) / 1);
+ --yellow-800-hsl: 32.432 calc(var(--saturation-factor, 1) * 90.244%) 8.039%;
+ --yellow-830: hsl(var(--yellow-830-hsl) / 1);
+ --yellow-830-hsl: 31.875 calc(var(--saturation-factor, 1) * 88.889%) 7.059%;
+ --yellow-860: hsl(var(--yellow-860-hsl) / 1);
+ --yellow-860-hsl: 32.308 calc(var(--saturation-factor, 1) * 86.667%) 5.882%;
+ --yellow-900: hsl(var(--yellow-900-hsl) / 1);
+ --yellow-900-hsl: 36 calc(var(--saturation-factor, 1) * 83.333%) 4.706%;
+ --green-100: hsl(var(--green-100-hsl) / 1);
+ --green-100-hsl: 136.667 calc(var(--saturation-factor, 1) * 90%) 96.078%;
+ --green-130: hsl(var(--green-130-hsl) / 1);
+ --green-130-hsl: 136.875 calc(var(--saturation-factor, 1) * 94.118%) 93.333%;
+ --green-160: hsl(var(--green-160-hsl) / 1);
+ --green-160-hsl: 140.952 calc(var(--saturation-factor, 1) * 91.304%) 86.471%;
+ --green-200: hsl(var(--green-200-hsl) / 1);
+ --green-200-hsl: 143.478 calc(var(--saturation-factor, 1) * 93.496%) 75.882%;
+ --green-230: hsl(var(--green-230-hsl) / 1);
+ --green-230-hsl: 146.323 calc(var(--saturation-factor, 1) * 86.592%) 64.902%;
+ --green-260: hsl(var(--green-260-hsl) / 1);
+ --green-260-hsl: 145.605 calc(var(--saturation-factor, 1) * 75.12%) 59.02%;
+ --green-300: hsl(var(--green-300-hsl) / 1);
+ --green-300-hsl: 146.323 calc(var(--saturation-factor, 1) * 65.401%) 53.529%;
+ --green-330: hsl(var(--green-330-hsl) / 1);
+ --green-330-hsl: 146.494 calc(var(--saturation-factor, 1) * 63.115%) 47.843%;
+ --green-345: hsl(var(--green-345-hsl) / 1);
+ --green-345-hsl: 146.939 calc(var(--saturation-factor, 1) * 65.919%) 43.725%;
+ --green-360: hsl(var(--green-360-hsl) / 1);
+ --green-360-hsl: 145.385 calc(var(--saturation-factor, 1) * 65%) 39.216%;
+ --green-400: hsl(var(--green-400-hsl) / 1);
+ --green-400-hsl: 142.703 calc(var(--saturation-factor, 1) * 60.656%) 35.882%;
+ --green-430: hsl(var(--green-430-hsl) / 1);
+ --green-430-hsl: 141.522 calc(var(--saturation-factor, 1) * 56.098%) 32.157%;
+ --green-460: hsl(var(--green-460-hsl) / 1);
+ --green-460-hsl: 141.481 calc(var(--saturation-factor, 1) * 56.643%) 28.039%;
+ --green-500: hsl(var(--green-500-hsl) / 1);
+ --green-500-hsl: 141.37 calc(var(--saturation-factor, 1) * 58.4%) 24.51%;
+ --green-530: hsl(var(--green-530-hsl) / 1);
+ --green-530-hsl: 140.308 calc(var(--saturation-factor, 1) * 60.748%) 20.98%;
+ --green-560: hsl(var(--green-560-hsl) / 1);
+ --green-560-hsl: 138.621 calc(var(--saturation-factor, 1) * 61.702%) 18.431%;
+ --green-600: hsl(var(--green-600-hsl) / 1);
+ --green-600-hsl: 139.245 calc(var(--saturation-factor, 1) * 65.432%) 15.882%;
+ --green-630: hsl(var(--green-630-hsl) / 1);
+ --green-630-hsl: 140 calc(var(--saturation-factor, 1) * 66.667%) 14.118%;
+ --green-660: hsl(var(--green-660-hsl) / 1);
+ --green-660-hsl: 139.091 calc(var(--saturation-factor, 1) * 68.75%) 12.549%;
+ --green-700: hsl(var(--green-700-hsl) / 1);
+ --green-700-hsl: 141 calc(var(--saturation-factor, 1) * 74.074%) 10.588%;
+ --green-730: hsl(var(--green-730-hsl) / 1);
+ --green-730-hsl: 138.333 calc(var(--saturation-factor, 1) * 78.261%) 9.02%;
+ --green-760: hsl(var(--green-760-hsl) / 1);
+ --green-760-hsl: 140 calc(var(--saturation-factor, 1) * 84.615%) 7.647%;
+ --green-800: hsl(var(--green-800-hsl) / 1);
+ --green-800-hsl: 139.286 calc(var(--saturation-factor, 1) * 82.353%) 6.667%;
+ --green-830: hsl(var(--green-830-hsl) / 1);
+ --green-830-hsl: 137.5 calc(var(--saturation-factor, 1) * 80%) 5.882%;
+ --green-860: hsl(var(--green-860-hsl) / 1);
+ --green-860-hsl: 132.632 calc(var(--saturation-factor, 1) * 70.37%) 5.294%;
+ --green-900: hsl(var(--green-900-hsl) / 1);
+ --green-900-hsl: 128.571 calc(var(--saturation-factor, 1) * 58.333%) 4.706%;
+ --blue-100: hsl(var(--blue-100-hsl) / 1);
+ --blue-100-hsl: 210 calc(var(--saturation-factor, 1) * 80%) 98.039%;
+ --blue-130: hsl(var(--blue-130-hsl) / 1);
+ --blue-130-hsl: 210 calc(var(--saturation-factor, 1) * 87.5%) 96.863%;
+ --blue-160: hsl(var(--blue-160-hsl) / 1);
+ --blue-160-hsl: 208.889 calc(var(--saturation-factor, 1) * 87.097%) 93.922%;
+ --blue-200: hsl(var(--blue-200-hsl) / 1);
+ --blue-200-hsl: 206.25 calc(var(--saturation-factor, 1) * 92.308%) 89.804%;
+ --blue-230: hsl(var(--blue-230-hsl) / 1);
+ --blue-230-hsl: 205.135 calc(var(--saturation-factor, 1) * 92.5%) 84.314%;
+ --blue-260: hsl(var(--blue-260-hsl) / 1);
+ --blue-260-hsl: 204.231 calc(var(--saturation-factor, 1) * 94.545%) 78.431%;
+ --blue-300: hsl(var(--blue-300-hsl) / 1);
+ --blue-300-hsl: 202.649 calc(var(--saturation-factor, 1) * 97.419%) 69.608%;
+ --blue-330: hsl(var(--blue-330-hsl) / 1);
+ --blue-330-hsl: 200.957 calc(var(--saturation-factor, 1) * 100%) 59.02%;
+ --blue-345: hsl(var(--blue-345-hsl) / 1);
+ --blue-345-hsl: 199.524 calc(var(--saturation-factor, 1) * 100%) 49.412%;
+ --blue-360: hsl(var(--blue-360-hsl) / 1);
+ --blue-360-hsl: 202.562 calc(var(--saturation-factor, 1) * 100%) 47.451%;
+ --blue-400: hsl(var(--blue-400-hsl) / 1);
+ --blue-400-hsl: 206.809 calc(var(--saturation-factor, 1) * 100%) 46.078%;
+ --blue-430: hsl(var(--blue-430-hsl) / 1);
+ --blue-430-hsl: 212.208 calc(var(--saturation-factor, 1) * 100%) 45.294%;
+ --blue-460: hsl(var(--blue-460-hsl) / 1);
+ --blue-460-hsl: 213.589 calc(var(--saturation-factor, 1) * 100%) 40.98%;
+ --blue-500: hsl(var(--blue-500-hsl) / 1);
+ --blue-500-hsl: 213.297 calc(var(--saturation-factor, 1) * 100%) 35.686%;
+ --blue-530: hsl(var(--blue-530-hsl) / 1);
+ --blue-530-hsl: 212.129 calc(var(--saturation-factor, 1) * 100%) 30.392%;
+ --blue-560: hsl(var(--blue-560-hsl) / 1);
+ --blue-560-hsl: 211.765 calc(var(--saturation-factor, 1) * 100%) 26.667%;
+ --blue-600: hsl(var(--blue-600-hsl) / 1);
+ --blue-600-hsl: 211.017 calc(var(--saturation-factor, 1) * 100%) 23.137%;
+ --blue-630: hsl(var(--blue-630-hsl) / 1);
+ --blue-630-hsl: 211.132 calc(var(--saturation-factor, 1) * 100%) 20.784%;
+ --blue-660: hsl(var(--blue-660-hsl) / 1);
+ --blue-660-hsl: 211.579 calc(var(--saturation-factor, 1) * 100%) 18.627%;
+ --blue-700: hsl(var(--blue-700-hsl) / 1);
+ --blue-700-hsl: 211.765 calc(var(--saturation-factor, 1) * 100%) 16.667%;
+ --blue-730: hsl(var(--blue-730-hsl) / 1);
+ --blue-730-hsl: 210.833 calc(var(--saturation-factor, 1) * 100%) 14.118%;
+ --blue-760: hsl(var(--blue-760-hsl) / 1);
+ --blue-760-hsl: 211.429 calc(var(--saturation-factor, 1) * 100%) 12.353%;
+ --blue-800: hsl(var(--blue-800-hsl) / 1);
+ --blue-800-hsl: 211.111 calc(var(--saturation-factor, 1) * 100%) 10.588%;
+ --blue-830: hsl(var(--blue-830-hsl) / 1);
+ --blue-830-hsl: 212.5 calc(var(--saturation-factor, 1) * 100%) 9.412%;
+ --blue-860: hsl(var(--blue-860-hsl) / 1);
+ --blue-860-hsl: 213.488 calc(var(--saturation-factor, 1) * 100%) 8.431%;
+ --blue-900: hsl(var(--blue-900-hsl) / 1);
+ --blue-900-hsl: 213.333 calc(var(--saturation-factor, 1) * 100%) 7.059%;
+ --teal-100: hsl(var(--teal-100-hsl) / 1);
+ --teal-100-hsl: 193.333 calc(var(--saturation-factor, 1) * 69.231%) 97.451%;
+ --teal-130: hsl(var(--teal-130-hsl) / 1);
+ --teal-130-hsl: 192 calc(var(--saturation-factor, 1) * 83.333%) 95.294%;
+ --teal-160: hsl(var(--teal-160-hsl) / 1);
+ --teal-160-hsl: 190.5 calc(var(--saturation-factor, 1) * 83.333%) 90.588%;
+ --teal-200: hsl(var(--teal-200-hsl) / 1);
+ --teal-200-hsl: 188.333 calc(var(--saturation-factor, 1) * 85.714%) 83.529%;
+ --teal-230: hsl(var(--teal-230-hsl) / 1);
+ --teal-230-hsl: 187.934 calc(var(--saturation-factor, 1) * 88.321%) 73.137%;
+ --teal-260: hsl(var(--teal-260-hsl) / 1);
+ --teal-260-hsl: 188.276 calc(var(--saturation-factor, 1) * 81.921%) 65.294%;
+ --teal-300: hsl(var(--teal-300-hsl) / 1);
+ --teal-300-hsl: 188.903 calc(var(--saturation-factor, 1) * 72.77%) 58.235%;
+ --teal-330: hsl(var(--teal-330-hsl) / 1);
+ --teal-330-hsl: 189.375 calc(var(--saturation-factor, 1) * 65.574%) 52.157%;
+ --teal-345: hsl(var(--teal-345-hsl) / 1);
+ --teal-345-hsl: 189.677 calc(var(--saturation-factor, 1) * 62.753%) 48.431%;
+ --teal-360: hsl(var(--teal-360-hsl) / 1);
+ --teal-360-hsl: 189.718 calc(var(--saturation-factor, 1) * 63.964%) 43.529%;
+ --teal-400: hsl(var(--teal-400-hsl) / 1);
+ --teal-400-hsl: 189.6 calc(var(--saturation-factor, 1) * 63.452%) 38.627%;
+ --teal-430: hsl(var(--teal-430-hsl) / 1);
+ --teal-430-hsl: 190.459 calc(var(--saturation-factor, 1) * 63.006%) 33.922%;
+ --teal-460: hsl(var(--teal-460-hsl) / 1);
+ --teal-460-hsl: 190.515 calc(var(--saturation-factor, 1) * 64.238%) 29.608%;
+ --teal-500: hsl(var(--teal-500-hsl) / 1);
+ --teal-500-hsl: 190.465 calc(var(--saturation-factor, 1) * 65.152%) 25.882%;
+ --teal-530: hsl(var(--teal-530-hsl) / 1);
+ --teal-530-hsl: 190.263 calc(var(--saturation-factor, 1) * 66.667%) 22.353%;
+ --teal-560: hsl(var(--teal-560-hsl) / 1);
+ --teal-560-hsl: 189.565 calc(var(--saturation-factor, 1) * 69.697%) 19.412%;
+ --teal-600: hsl(var(--teal-600-hsl) / 1);
+ --teal-600-hsl: 188.852 calc(var(--saturation-factor, 1) * 71.765%) 16.667%;
+ --teal-630: hsl(var(--teal-630-hsl) / 1);
+ --teal-630-hsl: 189.643 calc(var(--saturation-factor, 1) * 73.684%) 14.902%;
+ --teal-660: hsl(var(--teal-660-hsl) / 1);
+ --teal-660-hsl: 188.4 calc(var(--saturation-factor, 1) * 75.758%) 12.941%;
+ --teal-700: hsl(var(--teal-700-hsl) / 1);
+ --teal-700-hsl: 189.13 calc(var(--saturation-factor, 1) * 79.31%) 11.373%;
+ --teal-730: hsl(var(--teal-730-hsl) / 1);
+ --teal-730-hsl: 189 calc(var(--saturation-factor, 1) * 80%) 9.804%;
+ --teal-760: hsl(var(--teal-760-hsl) / 1);
+ --teal-760-hsl: 188.571 calc(var(--saturation-factor, 1) * 81.395%) 8.431%;
+ --teal-800: hsl(var(--teal-800-hsl) / 1);
+ --teal-800-hsl: 188 calc(var(--saturation-factor, 1) * 83.333%) 7.059%;
+ --teal-830: hsl(var(--teal-830-hsl) / 1);
+ --teal-830-hsl: 188.889 calc(var(--saturation-factor, 1) * 87.097%) 6.078%;
+ --teal-860: hsl(var(--teal-860-hsl) / 1);
+ --teal-860-hsl: 187.826 calc(var(--saturation-factor, 1) * 85.185%) 5.294%;
+ --teal-900: hsl(var(--teal-900-hsl) / 1);
+ --teal-900-hsl: 189 calc(var(--saturation-factor, 1) * 90.909%) 4.314%;
+ --white: hsl(var(--white-hsl) / 1);
+ --white-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-100: hsl(var(--white-100-hsl) / 1);
+ --white-100-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-130: hsl(var(--white-130-hsl) / 1);
+ --white-130-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-160: hsl(var(--white-160-hsl) / 1);
+ --white-160-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-200: hsl(var(--white-200-hsl) / 1);
+ --white-200-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-230: hsl(var(--white-230-hsl) / 1);
+ --white-230-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-260: hsl(var(--white-260-hsl) / 1);
+ --white-260-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-300: hsl(var(--white-300-hsl) / 1);
+ --white-300-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-330: hsl(var(--white-330-hsl) / 1);
+ --white-330-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-345: hsl(var(--white-345-hsl) / 1);
+ --white-345-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-360: hsl(var(--white-360-hsl) / 1);
+ --white-360-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-400: hsl(var(--white-400-hsl) / 1);
+ --white-400-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-430: hsl(var(--white-430-hsl) / 1);
+ --white-430-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-460: hsl(var(--white-460-hsl) / 1);
+ --white-460-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-500: hsl(var(--white-500-hsl) / 1);
+ --white-500-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 100%;
+ --white-530: hsl(var(--white-530-hsl) / 1);
+ --white-530-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 90.98%;
+ --white-560: hsl(var(--white-560-hsl) / 1);
+ --white-560-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 81.176%;
+ --white-600: hsl(var(--white-600-hsl) / 1);
+ --white-600-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 67.843%;
+ --white-630: hsl(var(--white-630-hsl) / 1);
+ --white-630-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 58.824%;
+ --white-660: hsl(var(--white-660-hsl) / 1);
+ --white-660-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 51.373%;
+ --white-700: hsl(var(--white-700-hsl) / 1);
+ --white-700-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 40%;
+ --white-730: hsl(var(--white-730-hsl) / 1);
+ --white-730-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 37.255%;
+ --white-760: hsl(var(--white-760-hsl) / 1);
+ --white-760-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 34.51%;
+ --white-800: hsl(var(--white-800-hsl) / 1);
+ --white-800-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 30.196%;
+ --white-830: hsl(var(--white-830-hsl) / 1);
+ --white-830-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 23.137%;
+ --white-860: hsl(var(--white-860-hsl) / 1);
+ --white-860-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 14.902%;
+ --white-900: hsl(var(--white-900-hsl) / 1);
+ --white-900-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 5.098%;
+ --black: hsl(var(--black-hsl) / 1);
+ --black-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-100: hsl(var(--black-100-hsl) / 1);
+ --black-100-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 94.902%;
+ --black-130: hsl(var(--black-130-hsl) / 1);
+ --black-130-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 90.98%;
+ --black-160: hsl(var(--black-160-hsl) / 1);
+ --black-160-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 85.49%;
+ --black-200: hsl(var(--black-200-hsl) / 1);
+ --black-200-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 80%;
+ --black-230: hsl(var(--black-230-hsl) / 1);
+ --black-230-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 74.118%;
+ --black-260: hsl(var(--black-260-hsl) / 1);
+ --black-260-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 67.451%;
+ --black-300: hsl(var(--black-300-hsl) / 1);
+ --black-300-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 60%;
+ --black-330: hsl(var(--black-330-hsl) / 1);
+ --black-330-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 47.843%;
+ --black-345: hsl(var(--black-345-hsl) / 1);
+ --black-345-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 40%;
+ --black-360: hsl(var(--black-360-hsl) / 1);
+ --black-360-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 36.078%;
+ --black-400: hsl(var(--black-400-hsl) / 1);
+ --black-400-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 20%;
+ --black-430: hsl(var(--black-430-hsl) / 1);
+ --black-430-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 14.51%;
+ --black-460: hsl(var(--black-460-hsl) / 1);
+ --black-460-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 7.843%;
+ --black-500: hsl(var(--black-500-hsl) / 1);
+ --black-500-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-530: hsl(var(--black-530-hsl) / 1);
+ --black-530-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-560: hsl(var(--black-560-hsl) / 1);
+ --black-560-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-600: hsl(var(--black-600-hsl) / 1);
+ --black-600-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-630: hsl(var(--black-630-hsl) / 1);
+ --black-630-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-660: hsl(var(--black-660-hsl) / 1);
+ --black-660-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-700: hsl(var(--black-700-hsl) / 1);
+ --black-700-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-730: hsl(var(--black-730-hsl) / 1);
+ --black-730-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-760: hsl(var(--black-760-hsl) / 1);
+ --black-760-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-800: hsl(var(--black-800-hsl) / 1);
+ --black-800-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-830: hsl(var(--black-830-hsl) / 1);
+ --black-830-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-860: hsl(var(--black-860-hsl) / 1);
+ --black-860-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --black-900: hsl(var(--black-900-hsl) / 1);
+ --black-900-hsl: 0 calc(var(--saturation-factor, 1) * 0%) 0%;
+ --brand-100: hsl(var(--brand-100-hsl) / 1);
+ --brand-100-hsl: 240 calc(var(--saturation-factor, 1) * 77.778%) 98.235%;
+ --brand-130: hsl(var(--brand-130-hsl) / 1);
+ --brand-130-hsl: 235.714 calc(var(--saturation-factor, 1) * 87.5%) 96.863%;
+ --brand-160: hsl(var(--brand-160-hsl) / 1);
+ --brand-160-hsl: 234.545 calc(var(--saturation-factor, 1) * 84.615%) 94.902%;
+ --brand-200: hsl(var(--brand-200-hsl) / 1);
+ --brand-200-hsl: 236 calc(var(--saturation-factor, 1) * 83.333%) 92.941%;
+ --brand-230: hsl(var(--brand-230-hsl) / 1);
+ --brand-230-hsl: 235.5 calc(var(--saturation-factor, 1) * 86.957%) 90.98%;
+ --brand-260: hsl(var(--brand-260-hsl) / 1);
+ --brand-260-hsl: 235.2 calc(var(--saturation-factor, 1) * 86.207%) 88.627%;
+ --brand-300: hsl(var(--brand-300-hsl) / 1);
+ --brand-300-hsl: 235.161 calc(var(--saturation-factor, 1) * 86.111%) 85.882%;
+ --brand-330: hsl(var(--brand-330-hsl) / 1);
+ --brand-330-hsl: 234.75 calc(var(--saturation-factor, 1) * 85.106%) 81.569%;
+ --brand-345: hsl(var(--brand-345-hsl) / 1);
+ --brand-345-hsl: 234.783 calc(var(--saturation-factor, 1) * 85.185%) 78.824%;
+ --brand-360: hsl(var(--brand-360-hsl) / 1);
+ --brand-360-hsl: 235.152 calc(var(--saturation-factor, 1) * 86.087%) 77.451%;
+ --brand-400: hsl(var(--brand-400-hsl) / 1);
+ --brand-400-hsl: 234.677 calc(var(--saturation-factor, 1) * 86.111%) 71.765%;
+ --brand-430: hsl(var(--brand-430-hsl) / 1);
+ --brand-430-hsl: 235 calc(var(--saturation-factor, 1) * 85.714%) 69.804%;
+ --brand-460: hsl(var(--brand-460-hsl) / 1);
+ --brand-460-hsl: 234.93 calc(var(--saturation-factor, 1) * 85.542%) 67.451%;
+ --brand-500: hsl(var(--brand-500-hsl) / 1);
+ --brand-500-hsl: 234.935 calc(var(--saturation-factor, 1) * 85.556%) 64.706%;
+ --brand-530: hsl(var(--brand-530-hsl) / 1);
+ --brand-530-hsl: 234.857 calc(var(--saturation-factor, 1) * 66.667%) 58.824%;
+ --brand-560: hsl(var(--brand-560-hsl) / 1);
+ --brand-560-hsl: 234.72 calc(var(--saturation-factor, 1) * 51.44%) 52.353%;
+ --brand-600: hsl(var(--brand-600-hsl) / 1);
+ --brand-600-hsl: 234.857 calc(var(--saturation-factor, 1) * 46.667%) 44.118%;
+ --brand-630: hsl(var(--brand-630-hsl) / 1);
+ --brand-630-hsl: 235.385 calc(var(--saturation-factor, 1) * 46.667%) 38.235%;
+ --brand-660: hsl(var(--brand-660-hsl) / 1);
+ --brand-660-hsl: 234.75 calc(var(--saturation-factor, 1) * 47.059%) 33.333%;
+ --brand-700: hsl(var(--brand-700-hsl) / 1);
+ --brand-700-hsl: 235.161 calc(var(--saturation-factor, 1) * 46.97%) 25.882%;
+ --brand-730: hsl(var(--brand-730-hsl) / 1);
+ --brand-730-hsl: 234.828 calc(var(--saturation-factor, 1) * 46.774%) 24.314%;
+ --brand-760: hsl(var(--brand-760-hsl) / 1);
+ --brand-760-hsl: 234.34 calc(var(--saturation-factor, 1) * 46.903%) 22.157%;
+ --brand-800: hsl(var(--brand-800-hsl) / 1);
+ --brand-800-hsl: 234.894 calc(var(--saturation-factor, 1) * 47.475%) 19.412%;
+ --brand-830: hsl(var(--brand-830-hsl) / 1);
+ --brand-830-hsl: 235 calc(var(--saturation-factor, 1) * 47.368%) 14.902%;
+ --brand-860: hsl(var(--brand-860-hsl) / 1);
+ --brand-860-hsl: 234.783 calc(var(--saturation-factor, 1) * 46.939%) 9.608%;
+ --brand-900: hsl(var(--brand-900-hsl) / 1);
+ --brand-900-hsl: 232.5 calc(var(--saturation-factor, 1) * 50%) 3.137%;
+}
\ No newline at end of file
diff --git a/discord/vale/config/vocabularies/Discord/accept.txt b/discord/vale/config/vocabularies/Discord/accept.txt
new file mode 100644
index 0000000000..62fee0dd27
--- /dev/null
+++ b/discord/vale/config/vocabularies/Discord/accept.txt
@@ -0,0 +1,288 @@
+_asset
+_banner
+_event
+_id
+ACKs
+afk
+anonymized
+API's
+api
+applicationId
+application_id
+app_id
+Arctis
+Astley
+audioinput
+authed
+Autoincrementing
+authentication
+backoff
+badging
+bigint
+bitfield
+bitfields
+bitmask
+bitrate
+Bitrate
+bitwise
+Bitwise
+Blurple
+boolean
+booleans
+bot's
+breakpoint
+bytearray
+bynweekday
+byweekday
+clientId
+cloudflared
+cmd
+comms
+composable
+cooldown
+Ciphertext
+ciphertext
+crosspost
+Crosspost
+crossposted
+cron
+crypto
+CSRCs
+CTAs
+Currated
+currentSize
+custom_id
+cya
+datapoint
+datapoints
+deadbeef
+deallocated
+Deeplink
+deduplicated
+Deletable
+deserialize
+devs
+Devs
+dialogs
+deauthorized
+deduped
+discordSdk
+discrim
+DLLs
+DMs
+dms
+DMing
+dnd
+downsample
+dropoff
+endian
+Enums
+enums
+entity_type
+embed's
+evt
+expirations
+extensibly
+falsy
+Figma
+Fitbit
+Fraggers
+framerate
+FString
+gameplay
+gank
+GDMs
+gif
+GIFs
+gifs
+gifv
+globbing
+guild_id
+hardcode
+Heartbeating
+heya
+heyo
+hoges
+hostname
+Hypesquad
+ie
+image_id
+incentivized
+Incentivized
+Inclusivity
+inexhaustive
+influencer
+influencers
+instanceId
+interaction_token
+invitable
+inviter
+ip
+joinSecret
+keypair
+largeImage
+largeText
+laterz
+launchable
+leaderboard
+leaderboards
+Lotties
+Lua
+lurkable
+maxSize
+mediaUrl
+mentionables
+message_id
+modmins
+ngrok
+ngrok's
+nsfw
+nullable
+Nullable
+num_shards
+Ogg
+ogg
+onwards
+param
+passthrough
+pdb
+performant
+permissioning
+pid
+pingable
+Playstation
+prepending
+primary_color
+proxied
+pseudocode
+qos
+querystring
+rasterized
+realtime
+reapprove
+redistributable
+redstone
+referrer_id
+renderable
+repurpose
+requester's
+requestor
+Sandscape
+sandboxed
+scrollback
+SDKs
+shaders
+shard_id
+Sharding
+sharding
+shareLink
+signum
+signalHandler
+Sku
+sku
+sku_ids
+skus
+SKUs
+slowmode
+smallImage
+smallText
+social_layer
+Soundshare
+spectateSecret
+Spotify
+Stahp
+steamId
+Steamworks
+Struture
+Subcommand
+subcommand
+Subcommands
+subcommands
+submenu
+Substring
+substrings
+Supa
+templated
+threadsafe
+toolbelt
+toolkits
+tooltips
+touchpoints
+tts
+twitchusername
+uhm
+ulong
+unarchive
+Unarchiving
+unarchiving
+unarchived
+Unencrypted
+unencrypted
+unicode
+Unlinking
+unlinks
+Unmerging
+unmerge
+unmerging
+Unpublish
+unpublish
+Unpublishing
+unpublishing
+unprocessable
+unranked
+Unrenderable
+Unsyncing
+unsynced
+untappable
+upsell
+upsells
+upserts
+URIs
+urls
+user_id
+userId
+UUIDs
+UIs
+version_number
+videoinput
+VMs
+Vulkan
+walkthrough
+Walkthrough
+webserver
+websockets
+Woah
+Wordmark
+wordmark
+wss
+Wumpus
+wumpus
+Xbox
+youtube
+zlib
+zombied
+zstd
+command_id
+channel_id
+prepended
+glibc
+timeframe
+rollout
+whitepaper
+Whitepaper
+deeplinking
+deauthorization
+distros
+starter_pack
+guildId
+unmerges
+unmerged
+application_asset_id
+dateutil
+setActivity
+ratelimit
+audiooutput
+startTimestamp
+partySize
+partyMax
+Wump
\ No newline at end of file
diff --git a/discord/vale/config/vocabularies/Mintlify/accept.txt b/discord/vale/config/vocabularies/Mintlify/accept.txt
new file mode 100644
index 0000000000..8799898d5a
--- /dev/null
+++ b/discord/vale/config/vocabularies/Mintlify/accept.txt
@@ -0,0 +1,267 @@
+Mintlify
+mintlify
+VSCode
+openapi
+OpenAPI
+Github
+APIs
+
+repo
+npm
+dev
+
+Lorem
+ipsum
+impsum
+amet
+
+const
+myName
+myObject
+bearerAuth
+favicon
+topbar
+url
+borderRadius
+args
+modeToggle
+ModeToggle
+isHidden
+autoplay
+
+_italic_
+Strikethrough
+Blockquotes
+Blockquote
+Singleline
+Multiline
+
+onboarding
+
+async
+await
+boolean
+enum
+func
+impl
+init
+instanceof
+typeof
+params
+stdin
+stdout
+stderr
+stdout
+stdin
+var
+const
+let
+null
+undefined
+struct
+bool
+
+cors
+csrf
+env
+xhr
+xhr2
+jwt
+oauth
+websocket
+localhost
+middleware
+runtime
+webhook
+stdin
+stdout
+
+json
+yaml
+yml
+md
+txt
+tsx
+jsx
+css
+scss
+html
+png
+jpg
+svg
+
+cdn
+cli
+css
+dom
+dto
+env
+git
+gui
+http
+https
+ide
+jvm
+mvc
+orm
+rpc
+sdk
+sql
+ssh
+ssl
+tcp
+tls
+uri
+url
+ux
+ui
+
+nodejs
+npm
+yarn
+pnpm
+eslint
+pytest
+golang
+rustc
+kubectl
+mongo
+postgres
+redis
+
+JavaScript
+TypeScript
+Python
+Ruby
+Rust
+Go
+Golang
+Java
+Kotlin
+Swift
+Node.js
+NodeJS
+Deno
+
+React
+Vue
+Angular
+Next.js
+Nuxt
+Express
+Django
+Flask
+Spring
+Laravel
+Redux
+Vuex
+TensorFlow
+PostgreSQL
+MongoDB
+Redis
+PNPM
+
+Docker
+Kubernetes
+AWS
+Azure
+GCP
+Terraform
+Jenkins
+CircleCI
+GitLab
+Heroku
+
+Git
+git
+GitHub
+GitLab
+Bitbucket
+VSCode
+Visual Studio Code
+IntelliJ
+WebStorm
+ESLint
+eslint
+Prettier
+prettier
+Webpack
+webpack
+Vite
+vite
+Babel
+babel
+Jest
+jest
+Mocha
+Cypress
+Postman
+
+HTTP
+HTTPS
+OAuth
+JWT
+GraphQL
+REST
+WebSocket
+TCP/IP
+
+NPM
+Yarn
+PNPM
+Pip
+PIP
+Cargo
+RubyGems
+
+Swagger
+OpenAPI
+Markdown
+MDX
+Storybook
+TypeDoc
+JSDoc
+
+MySQL
+PostgreSQL
+MongoDB
+Redis
+Elasticsearch
+DynamoDB
+
+Linux
+Unix
+macOS
+iOS
+
+Firefox
+Chromium
+WebKit
+
+config
+ctx
+desc
+dir
+elem
+err
+len
+msg
+num
+obj
+prev
+proc
+ptr
+req
+res
+str
+tmp
+val
+vars
+
+todo
+href
+lang
+nav
+prev
+next
+toc
diff --git a/docs/activities/development-guides.mdx b/docs/activities/development-guides.mdx
deleted file mode 100644
index 976b799836..0000000000
--- a/docs/activities/development-guides.mdx
+++ /dev/null
@@ -1,151 +0,0 @@
----
-sidebar_label: Development Guides
-showTOC: true
-subpages:
- - development-guides/local-development.mdx
- - development-guides/user-actions.mdx
- - development-guides/mobile.mdx
- - development-guides/layout.mdx
- - development-guides/networking.mdx
- - development-guides/multiplayer-experience.mdx
- - development-guides/growth-and-referrals.mdx
- - development-guides/assets-and-metadata.mdx
- - development-guides/production-readiness.mdx
----
-
-[Home](/docs/intro) > [Activities](/docs/activities/overview) > Development Guides
-
-# Activity Development Guides
-
-These guides include suggested development practices, SDK commands, and user flows for you to consider while building your Activity. These will help to provide your users with a consistent and clear experience while interacting with your application.
-
-## Local Development
-
-
- Get up and running with a local development application.
-
-
- How to launch your app on mobile and desktop Discord clients.
-
-
- Configure the Discord proxy to allow network requests to necessary external endpoints.
-
-
- How to use the various levels of logging while building your application.
-
-
-
-## User Actions
-
-
- Open an external link from within your app.
-
-
- Open the Application Channel Invite dialog within Discord.
-
-
- Open a dialog to share media from your application to a channel, DM, or GDM.
-
-
- Configure a command that allows users to open your Activity from the App Launcher.
-
-
- Open a dialog to enable hardware acceleration for compute-intensive applications.
-
-
-
-## Mobile
-
-
- Update your application settings to support iOS and Android.
-
-
- Ensure that your app's assets fall within mobile-safe areas.
-
-
- Respond to thermal state changes surfaced from iOS and Android.
-
-
-
-## Layout
-
-
- Configure and subscribe to changes in application orientation.
-
-
- Subscribe to layout mode changes to update your application's user interface.
-
-
-
-## Networking
-
-
- Working with our Activity Proxy
-
-
- Generate a full URL when working with network requests.
-
-
- Allow network requests to external resources from inside the Discord proxy.
-
-
- Keep things safe and secure in your Activity.
-
-
-
-## Multiplayer Experience
-
-
- Managing instances to ensure users join the same instance as their friends.
-
-
- Use the SDK to fetch the users currently connected to an instance.
-
-
- Retrieve and render the usernames and avatars of users connected to your application.
-
-
- Validating activity sessions are via a Discord client before adding them to an instance's session.
-
-
-
-## Growth and Referrals
-
-
- Encourage your users to share links to your activity by adding tracking and offering rewards for engagement.
-
-
-
- For off-platform sharing of rewards, promotions, or limited time experiences.
-
-
-
- An API to be able to generate ephemeral links with a customizable embed.
-
-
-
-## Assets & Metadata
-
-
- Best practices for configuring how your application shows up in Discord.
-
-
- Best practices for configuring how your application shows up in Discord.
-
-
-
-## Production Readiness
-
-
- Manage asset caching in your application and the Discord Activity proxy.
-
-
- Stay within rate limits to keep the fun going in your Activity.
-
-
- Network routing considerations when preparing your Activity for production use.
-
-
- Future-proof your application and support new commands as they become available in the SDK.
-
-
diff --git a/docs/change-log.mdx b/docs/change-log.mdx
deleted file mode 100644
index 3bb9c66ef7..0000000000
--- a/docs/change-log.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
----
-showTOC: false
----
-
-# Change Log
-
-Discover the latest updates, new features, and bug fixes on the Discord Developer Platform. To join in on the conversation, join the [Discord Developers Server](https://discord.com/invite/discord-developers).
-
-/widget`:
-
-* `/guilds//embed`
-
-Removed in favor of `/guilds//widget.json`:
-
-* `/servers//embed.json`
-* `/servers//widget.json`
-* `/guilds//embed.json`
-
-Removed in favor of `/guilds//widget.png`:
-
-* `/guilds//embed.png`
-
-Removed in favor of `/channels//messages/bulk-delete`:
-
-* `/channels//messages/bulk_delete/`
-
-Removed in favor of `/invites//`:
-
-* `/invite//`
diff --git a/docs/change-log/2020-10-27-gateway-v6-intent-restrictions.md b/docs/change-log/2020-10-27-gateway-v6-intent-restrictions.md
deleted file mode 100644
index ce0ccc1d4a..0000000000
--- a/docs/change-log/2020-10-27-gateway-v6-intent-restrictions.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Gateway v6 Intent Restrictions"
-date: "2020-10-27"
----
-
-The v6 gateway now applies the restrictions for gateway intents. This means the new chunking limitations are now in effect, regardless of intents being used. See [Request Guild Members](/docs/events/gateway-events#request-guild-members) for further details.
-Additionally, if privileged intents are not enabled in the application dashboard the bot will not receive the events for those intents.
-
-All other intents are always enabled by default unless specified otherwise by the identify payload. We have made a support article to explain some of the changes and resulting issues with more details: [Gateway Update FAQ](https://dis.gd/gwupdate)
diff --git a/docs/change-log/2020-11-13-stickers.md b/docs/change-log/2020-11-13-stickers.md
deleted file mode 100644
index 77ea376a79..0000000000
--- a/docs/change-log/2020-11-13-stickers.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Stickers"
-date: "2020-11-13"
----
-
-Stickers are now documented as part of the [message](/docs/resources/message#message-object) object.
diff --git a/docs/change-log/2020-11-16-inline-replies.md b/docs/change-log/2020-11-16-inline-replies.md
deleted file mode 100644
index f8bc843872..0000000000
--- a/docs/change-log/2020-11-16-inline-replies.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Inline Replies"
-date: "2020-11-16"
----
-
-Inline Replies have been added to our documentation. They behave differently in v6 and v8, so be cautious in your implementation:
-
-* Inline replies are type `19` in v8, but remain type `0` in v6
-* You can now add a `message_reference` on message create to create a reply
-* A new field `referenced_message` has been added to the [Message Object](/docs/resources/message#message-object)
-* A new field `replied_user` has been added to the [Allowed Mentions Object](/docs/resources/message#allowed-mentions-object)
-* [Message Create](/docs/events/gateway-events#message-create) gateway event is guaranteed to have a `referenced_message` if the message created is a reply. Otherwise, that field is not guaranteed.
diff --git a/docs/change-log/2020-12-15-slash-commands-and-interactions.md b/docs/change-log/2020-12-15-slash-commands-and-interactions.md
deleted file mode 100644
index a04de4e9d7..0000000000
--- a/docs/change-log/2020-12-15-slash-commands-and-interactions.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Slash Commands and Interactions"
-date: "2020-12-15"
----
-
-Slash Commands are here! There's a *lot* to cover, so go check out specific documentation under [Slash Commands](/docs/interactions/application-commands).
-
-Slash Commands include some new features for webhooks as well:
-
-* Webhooks can now update previously-sent messages from the same webhook using [Edit Webhook Message](/docs/resources/webhook#edit-webhook-message) and [Delete Webhook Message](/docs/resources/webhook#delete-webhook-message)
-
-This PR also documents the `application` field on the `READY` gateway event, which is a partial [application object](/docs/resources/application#application-object) containing `id` and `flags`.
diff --git a/docs/change-log/2021-01-22-change-to-permission-checking-when-creating-channels.md b/docs/change-log/2021-01-22-change-to-permission-checking-when-creating-channels.md
deleted file mode 100644
index 2d5a07ba15..0000000000
--- a/docs/change-log/2021-01-22-change-to-permission-checking-when-creating-channels.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Change to Permission Checking when Creating Channels"
-date: "2021-01-22"
----
-
-Permission overwrites in the guild channel creation endpoint are now validated against the permissions your bot has in the guild. Permission overwrites specified in the request body when creating guild channels will now require your bot to also have the permissions being applied. Setting `MANAGE_ROLES` permission in channel overwrites is only possible for guild administrators or users with `MANAGE_ROLES` as a permission overwrite in the channel.
diff --git a/docs/change-log/2021-02-09-slash-commands-in-dms.md b/docs/change-log/2021-02-09-slash-commands-in-dms.md
deleted file mode 100644
index 6a0b840dac..0000000000
--- a/docs/change-log/2021-02-09-slash-commands-in-dms.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Slash Commands in DMs"
-date: "2021-02-09"
----
-
-Slash Commands are now supported in DMs with bots. Due to this change, some of the fields on the [Interaction object](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure) have been made optional. Newly optional fields don't reflect any behavior changes in Slash Commands within guilds; they are to support commands in the context of a DM only.
diff --git a/docs/change-log/2021-03-05-changes-to-slash-command-response-types-and-flags.md b/docs/change-log/2021-03-05-changes-to-slash-command-response-types-and-flags.md
deleted file mode 100644
index baebbddf8f..0000000000
--- a/docs/change-log/2021-03-05-changes-to-slash-command-response-types-and-flags.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Changes to Slash Command Response Types and Flags"
-date: "2021-03-05"
----
-
-Changes to interaction response types have been made to support better designs for application commands:
-
-* Type `2` `Acknowledge` has been deprecated
-* Type `3` `ChannelMessage` has been deprecated
-* Type `5` `AcknowledgeWithSource` has been renamed to `DeferredChannelMessageWithSource`
-
-These deprecated types will be removed and break on **April 9, 2021**.
-
-Additionally, `flags` has been documented on [InteractionApplicationCommandCallbackData](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-data-structure). Setting `flags` to `64` will make the interaction response ephemeral.
diff --git a/docs/change-log/2021-03-15-large-bot-sharding-lowered-to-150-000-guilds.md b/docs/change-log/2021-03-15-large-bot-sharding-lowered-to-150-000-guilds.md
deleted file mode 100644
index 6c07f37302..0000000000
--- a/docs/change-log/2021-03-15-large-bot-sharding-lowered-to-150-000-guilds.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Large Bot Sharding Lowered to 150,000 Guilds"
-date: "2021-03-15"
----
-
-There have been reports that sessions have higher frequency of errors when starting if a bot has joined too many guilds (the gateway connection times out). To account for this we have lowered the requirement for large bot sharding down to 150,000 guilds in order to improve reliability.
diff --git a/docs/change-log/2021-04-05-application-command-permissions.md b/docs/change-log/2021-04-05-application-command-permissions.md
deleted file mode 100644
index 70bf603a04..0000000000
--- a/docs/change-log/2021-04-05-application-command-permissions.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "Application Command Permissions"
-date: "2021-04-05"
----
-
-Need to keep some of your commands safe from prying eyes, or only available to the right people? Commands now support [command permissions](/docs/interactions/application-commands#permissions)!
-
-You can enable or disable a command (guild or global) for a specific user or role in a guild. For now, users will still be able to see the commands, but won't be able to use them.
-
-New routes have been added to support this functionality:
-
-* [`GET Guild Application Command Permissions`](/docs/interactions/application-commands#get-guild-application-command-permissions)
-* [`GET Application Command Permissions`](/docs/interactions/application-commands#get-application-command-permissions)
-* [`PUT Application Command Permissions`](/docs/interactions/application-commands#batch-edit-application-command-permissions)
-
-A `default_permission` field has also been added to the [ApplicationCommand](/docs/interactions/application-commands#application-command-object-application-command-structure) model. This field allows you to disable commands for everyone in a guild by default, if you prefer to make some of your commands an opt-in experience.
diff --git a/docs/change-log/2021-04-28-api-v9.md b/docs/change-log/2021-04-28-api-v9.md
deleted file mode 100644
index de2d875350..0000000000
--- a/docs/change-log/2021-04-28-api-v9.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "API v9"
-date: "2021-04-28"
----
-
-API v9 is now available.
-
-API v9 includes support for [threads](/docs/topics/threads), an upcoming feature. Older API versions will not receive any Gateway Events for threads, so it is important to update soon! We've prepared a [migration guide](/docs/topics/threads) to help make the upgrade process very straightforward.
-
-This documentation is being published early so bots can have at least two months to upgrade before threads launch.
-
-Additionally, API v9 also removes the `/channels/:id/messages/:id/suppress-embeds` route.
diff --git a/docs/change-log/2021-05-26-buttons-and-message-components.md b/docs/change-log/2021-05-26-buttons-and-message-components.md
deleted file mode 100644
index 5b73b6eda9..0000000000
--- a/docs/change-log/2021-05-26-buttons-and-message-components.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Buttons and Message Components"
-date: "2021-05-26"
----
-
-Message components are now available with our first two components: a layout-based `ActionRow` and...buttons!
-
-You can now include buttons on messages sent by your app, whether they're bot messages or responses to interactions. [Learn more about message components](/docs/components/overview).
-
-The addition of message components means new fields and response types:
-
-* An optional `components` field has been added to the [message object](/docs/resources/message#message-object)
-* New response types `6` and `7` have been added for [interaction responses](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-type), valid only for component-based interactions
diff --git a/docs/change-log/2021-06-10-support-for-multiple-embeds-in-message-routes.md b/docs/change-log/2021-06-10-support-for-multiple-embeds-in-message-routes.md
deleted file mode 100644
index 49a77f9a39..0000000000
--- a/docs/change-log/2021-06-10-support-for-multiple-embeds-in-message-routes.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Support for Multiple Embeds in Message Routes"
-date: "2021-06-10"
----
-
-Message routes now accept an embeds array in addition to the existing embed field. Bots can now send up to 10 embeds per message, to be consistent with webhook behavior. The existing embed field is considered deprecated and will be removed in the next API version.
diff --git a/docs/change-log/2021-06-30-select-menu-components.md b/docs/change-log/2021-06-30-select-menu-components.md
deleted file mode 100644
index 2a1aab356d..0000000000
--- a/docs/change-log/2021-06-30-select-menu-components.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Select Menu Components"
-date: "2021-06-30"
----
-
-Select Menus are now part of the components API! They're the greatest thing since the invention of buttons yesterday. Select menus allow you to offer users a choice of one or many options in a friendly UI-based way.
-
-Select menus can be used like other [message components](/docs/components/overview). Learn all the specifics in the [documentation](/docs/components/reference#string-select).
diff --git a/docs/change-log/2021-08-10-user-and-message-commands.md b/docs/change-log/2021-08-10-user-and-message-commands.md
deleted file mode 100644
index 3810d54d01..0000000000
--- a/docs/change-log/2021-08-10-user-and-message-commands.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "User and Message Commands"
-date: "2021-08-10"
----
-
-[User commands](/docs/interactions/application-commands#user-commands) and [message commands](/docs/interactions/application-commands#message-commands) are now live! These commands appear on context menus for users and messages, with more to come in the future.
-
-Context menu commands are a type of application command. The "Slash Commands" documentation page has been renamed to "Application Commands" and split out by type to show this.
diff --git a/docs/change-log/2021-09-16-updated-thread-permissions.md b/docs/change-log/2021-09-16-updated-thread-permissions.md
deleted file mode 100644
index 89cb16fc9d..0000000000
--- a/docs/change-log/2021-09-16-updated-thread-permissions.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Updated Thread Permissions"
-date: "2021-09-16"
----
-
-Thread permissions have been updated and simplified:
-
-* "Use Public Threads" is now "Create Public Threads", which allows users to create public threads and announcement threads in a channel, even if they cannot send messages in that channel.
-* "Use Private Threads" is now "Create Private Threads", which allows users to create private threads in a channel, even if they cannot send messages in that channel.
-
-A new permission has also been added:
-
-* "Send Messages in Threads", which allows users to send a message in a thread. The "Send Messages" permission has no effect in threads: users **must** have "Send Messages in Threads" to send a message in a thread. This allows for setups where a user can participate in a thread but cannot send a message in the parent channel (like a thread on an announcement post).
diff --git a/docs/change-log/2021-10-27-application-command-autocomplete-interactions.md b/docs/change-log/2021-10-27-application-command-autocomplete-interactions.md
deleted file mode 100644
index 6266d52dff..0000000000
--- a/docs/change-log/2021-10-27-application-command-autocomplete-interactions.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Application Command Autocomplete Interactions"
-date: "2021-10-27"
----
-
-Autocomplete interactions are now available, allowing application commands to provide server completed options. Check out [the autocomplete interaction docs](/docs/interactions/application-commands#autocomplete) for more information.
diff --git a/docs/change-log/2021-11-23-guild-scheduled-events.md b/docs/change-log/2021-11-23-guild-scheduled-events.md
deleted file mode 100644
index f2dd642e49..0000000000
--- a/docs/change-log/2021-11-23-guild-scheduled-events.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "Guild Scheduled Events"
-date: "2021-11-23"
----
-
-* Add official support for `guild_scheduled_events` field on `Guild` resource sent with `GUILD_CREATE` event
-
-#### Nov 18, 2021
-
-* Breaking change for return type for `GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}/users`
-* Add `with_user_count` query param for `GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}`
-* Return additional `creator` field by default in response for `GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}`
-* More details and clarification for the guild scheduled events feature.
-* Document support for `before` and `after` query params for `GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}/users`
-
-#### Nov 15, 2021
-
-Add new documentation for the recently released Guild Scheduled Events feature.
diff --git a/docs/change-log/2021-12-20-guild-member-timeouts.md b/docs/change-log/2021-12-20-guild-member-timeouts.md
deleted file mode 100644
index d48cb84615..0000000000
--- a/docs/change-log/2021-12-20-guild-member-timeouts.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Guild Member Timeouts"
-date: "2021-12-20"
----
-
-Add new documentation for the recently released guild member timeout feature.
diff --git a/docs/change-log/2022-02-08-interaction-modals-and-application-command-attachment-option-type.md b/docs/change-log/2022-02-08-interaction-modals-and-application-command-attachment-option-type.md
deleted file mode 100644
index 53742cfbc0..0000000000
--- a/docs/change-log/2022-02-08-interaction-modals-and-application-command-attachment-option-type.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Interaction Modals and Application Command Attachment Option Type"
-date: "2022-02-08"
----
-
-Interaction modals are now available, allowing applications to prompt users for further detailed input. Check out [the modal docs](/docs/interactions/receiving-and-responding#interaction-response-object-modal) for more information.
-
-Application Commands can now add an attachment option type. See [the option type table](/docs/interactions/application-commands#application-command-object-application-command-option-type) for more information.
diff --git a/docs/change-log/2022-02-14-api-v10.md b/docs/change-log/2022-02-14-api-v10.md
deleted file mode 100644
index cb647a2452..0000000000
--- a/docs/change-log/2022-02-14-api-v10.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "API v10"
-date: "2022-02-14"
----
-
-* API v8 is now deprecated.
-* `GET /channels/{channel.id}/threads/active` is decommissioned in favor of [`GET /guilds/{guild.id}/threads/active`](/docs/resources/guild#list-active-guild-threads).
-* Starting in v10, you must specify the message content intent (`1 << 15`) to receive content-related fields in message dispatches. Read more in the [Gateway Intents documentation](/docs/events/gateway#gateway-intents).
-* To specify a reason for an administrative action in audit logs, apps must now pass the `X-Audit-Log-Reason` header rather than the `reason` parameter for all endpoints. Read more in the [Audit Logs documentation](/docs/resources/audit-log).
-* Message routes (like [`POST /channels/{channel.id}/messages`](/docs/resources/message#create-message)) now use the `embeds` field (an array of embed objects) instead of `embed`.
-* The `summary` field for [applications](/docs/resources/application) now returns an empty string for all API versions.
-* The `name` and `description` fields for [Achievements](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Achievements.md#achievement-struct) are now strings, and localization info is now passed in new `name_localizations` and `description_localizations` dictionaries. This change standardizes localization to match [Application Commands](/docs/interactions/application-commands#localization). Read details in the [Achievements documentation](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Achievements.md#achievement-struct).
-* Existing attachments must be specified when [`PATCH`ing messages with new attachments](/docs/reference#editing-message-attachments). Any attachments not specified will be removed and replaced with the specified list
-* Requests to v10 and higher will no longer be supported on `discordapp.com` (this does **not** affect `cdn.discordapp.com`)
-
-#### Upcoming changes
-
-* API v6 and v7 will be decommissioned **in early 2023**
-* `MESSAGE_CONTENT` is becoming a privileged intent for verified bots in 75+ servers **on August 31, 2022**. Read details in [the FAQ](https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-FAQ) or follow [the guide](/docs/tutorials/upgrading-to-application-commands) on updating your app.
-* The `summary` field for applications will be removed in the next API version (v11)
diff --git a/docs/change-log/2022-03-31-guild-bans-pagination.md b/docs/change-log/2022-03-31-guild-bans-pagination.md
deleted file mode 100644
index a1146427f7..0000000000
--- a/docs/change-log/2022-03-31-guild-bans-pagination.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Guild Bans Pagination"
-date: "2022-03-31"
----
-
-The `GET /guilds/{guild.id}/bans` endpoint has been migrated to require pagination to improve reliability and stability. Check out the [endpoint docs](/docs/resources/guild#get-guild-bans) for more information.
diff --git a/docs/change-log/2022-04-06-forum-channels.md b/docs/change-log/2022-04-06-forum-channels.md
deleted file mode 100644
index a26809c6fa..0000000000
--- a/docs/change-log/2022-04-06-forum-channels.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Forum Channels"
-date: "2022-04-06"
----
-
-Added new channel type, `GUILD_FORUM` (15). A `GUILD_FORUM` channel is an unreleased feature that is very similar (from an API perspective) to a `GUILD_TEXT` channel, except only threads can be created in that channel; messages cannot be sent directly in that channel. Check out the [forums topic](/docs/topics/threads#forums) for more information.
diff --git a/docs/change-log/2022-04-27-updated-command-permissions.md b/docs/change-log/2022-04-27-updated-command-permissions.md
deleted file mode 100644
index 0e14717a47..0000000000
--- a/docs/change-log/2022-04-27-updated-command-permissions.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: "Updated Command Permissions"
-date: "2022-04-27"
-breaking: true
----
-
-Application command permissions have been updated to add more granular control and access to commands in Discord. You can read the major changes below, and [the updated documentation](/docs/interactions/application-commands#permissions) for details.
-
-#### Breaking changes
-
-* Bearer tokens are now required to edit command permissions. Bearer tokens are tokens tied to an authenticating user's permissions, and can be [retrieved using OAuth](/docs/topics/oauth2). The user must have permission to manage the guild and roles.
-* [`applications.commands.permissions.update`](/docs/topics/oauth2#shared-resources-oauth2-scopes) scope was added as a requirement to edit command permissions.
-* Disabled the batch editing endpoint ([`PUT /applications/{application.id}/guilds/{guild.id}/commands/permissions`](/docs/interactions/application-commands#batch-edit-application-command-permissions)).
-
-#### Other changes
-
-* Created a [`CHANNEL` command permission type](/docs/interactions/application-commands#application-command-permissions-object-application-command-permission-type)
-* Increase permission limit from `10` to `100`
-* [constant (`guild_id - 1`)](/docs/interactions/application-commands#application-command-permissions-object-application-command-permissions-constants) to represent all channels in command permissions
-* Added `default_member_permissions` field, which is a bitwise OR-ed set of [permissions](/docs/topics/permissions#permissions-bitwise-permission-flags), expressed as a string. This replaces the `default_permission` field, which will soon be deprecated.
-* Added `dm_permission`, which is a boolean flag used to indicate whether a command is available in DMs (only for global application commands). If no value is passed, the global command will be visible in DMs.
-* Added `APPLICATION_COMMAND_PERMISSIONS_UPDATE` [gateway](/docs/events/gateway-events#application-command-permissions-update) event and `APPLICATION_COMMAND_PERMISSION_UPDATE` [audit log](/docs/resources/audit-log) event.
diff --git a/docs/change-log/2022-06-16-auto-moderation.md b/docs/change-log/2022-06-16-auto-moderation.md
deleted file mode 100644
index f9f85f6e28..0000000000
--- a/docs/change-log/2022-06-16-auto-moderation.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Auto Moderation"
-date: "2022-06-16"
----
-
-Add new [Auto Moderation feature](/docs/resources/auto-moderation) which enables guilds to moderate message content based on keywords, harmful links, and unwanted spam. This change includes:
-
-* New endpoints for [creating](/docs/resources/auto-moderation#create-auto-moderation-rule), [updating](/docs/resources/auto-moderation#modify-auto-moderation-rule), and [deleting](/docs/resources/auto-moderation#delete-auto-moderation-rule) Auto Moderation rules
-* New gateway events emitted when Auto Moderation rules are [created](/docs/events/gateway-events#auto-moderation-rule-create) (`AUTO_MODERATION_RULE_CREATE`), [updated](/docs/events/gateway-events#auto-moderation-rule-update) (`AUTO_MODERATION_RULE_UPDATE `), and [deleted](/docs/events/gateway-events#auto-moderation-rule-delete) (`AUTO_MODERATION_RULE_DELETE `). Requires the `AUTO_MODERATION_CONFIGURATION` (`1 << 20`) intent
-* New gateway event emitted when an [action is executed](/docs/events/gateway-events#auto-moderation-action-execution) (`AUTO_MODERATION_ACTION_EXECUTION`). Requires the `AUTO_MODERATION_EXECUTION` (`1 << 21`) intent
-* New [audit log entries](/docs/resources/audit-log#audit-log-entry-object-audit-log-events) when rules are created (`AUTO_MODERATION_RULE_CREATE`), updated (`AUTO_MODERATION_RULE_UPDATE`), or deleted (`AUTO_MODERATION_RULE_DELETE`), or when Auto Moderation performs an action (`AUTO_MODERATION_BLOCK_MESSAGE`)
diff --git a/docs/change-log/2022-06-17-updated-connection-property-field-names.md b/docs/change-log/2022-06-17-updated-connection-property-field-names.md
deleted file mode 100644
index 351f326920..0000000000
--- a/docs/change-log/2022-06-17-updated-connection-property-field-names.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Updated Connection Property Field Names"
-date: "2022-06-17"
----
-
-The `$` prefix in [identify connection properties](/docs/events/gateway-events#identify-identify-connection-properties) are deprecated. The new field names are `os`, `browser`, and `device`. When passed, the `$`-prefixed names will resolve to the new ones.
-
-In API v11, support for the previous field names (`$os`, `$browser`, and `$device`) will be removed.
diff --git a/docs/change-log/2022-06-21-message-content-in-auto-moderation-events.md b/docs/change-log/2022-06-21-message-content-in-auto-moderation-events.md
deleted file mode 100644
index 25fa593f02..0000000000
--- a/docs/change-log/2022-06-21-message-content-in-auto-moderation-events.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: "Message Content in Auto Moderation events"
-date: "2022-06-21"
-breaking: true
----
-
-In API v10, the `MESSAGE_CONTENT` (`1 << 15`) intent is now required to receive non-empty values for the `content` and `matched_content` fields in [`AUTO_MODERATION_ACTION_EXECUTION`](/docs/events/gateway-events#auto-moderation-action-execution) gateway events. This matches the intended behavior for message content across the API.
diff --git a/docs/change-log/2022-06-29-calculated-permissions-in-interaction-payloads.md b/docs/change-log/2022-06-29-calculated-permissions-in-interaction-payloads.md
deleted file mode 100644
index 4725d09906..0000000000
--- a/docs/change-log/2022-06-29-calculated-permissions-in-interaction-payloads.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Calculated Permissions in Interaction Payloads"
-date: "2022-06-29"
----
-
-Interaction payloads now contain an `app_permissions` field whose value is the computed [permissions](/docs/topics/permissions#permissions-bitwise-permission-flags) for a bot or app in the context of a specific interaction (including any channel overwrites). Similar to other permission fields, the value of `app_permissions` is a bitwise OR-ed set of permissions expressed as a string. Read details in the [interactions documentation](/docs/interactions/receiving-and-responding#interaction-object).
-
-For apps without a bot user (or without the `bot` scope), the value of `app_permissions` will be the same as the permissions for `@everyone`, but limited to the permissions that can be used in interaction responses (currently `ATTACH_FILES`, `EMBED_LINKS`, `MENTION_EVERYONE`, and `USE_EXTERNAL_EMOJIS`).
diff --git a/docs/change-log/2022-06-29-changes-to-bot-permissions-for-interactions-and-webhooks.md b/docs/change-log/2022-06-29-changes-to-bot-permissions-for-interactions-and-webhooks.md
deleted file mode 100644
index 5db2faefd1..0000000000
--- a/docs/change-log/2022-06-29-changes-to-bot-permissions-for-interactions-and-webhooks.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: "Changes to Bot Permissions for Interactions and Webhooks"
-date: "2022-06-29"
-breaking: true
----
-
-#### Upcoming Changes
-
-:::warn
-`MENTION_EVERYONE`, `SEND_TTS_MESSAGES` and `USE_EXTERNAL_EMOJIS` are the only permissions that will be affected by this change. In a previous version of this changelog, it was indicated that `ATTACH_FILES` and `EMBED_LINKS` would be affected but this is no longer the case.
-:::
-
-Starting **August 3, 2022**, the way some of a bot's `MENTION_EVERYONE`, `SEND_TTS_MESSAGES` and `USE_EXTERNAL_EMOJIS` [permissions](/docs/topics/permissions#permissions) are calculated is changing in two cases:
-
-* When **responding to an [interaction](/docs/interactions/receiving-and-responding)** (like application commands or message components)
-* When **executing a [webhook](/docs/resources/webhook) that the bot created**
-
-Going forward, in the above cases, a bot’s `MENTION_EVERYONE`, `SEND_TTS_MESSAGES` and `USE_EXTERNAL_EMOJIS` permissions will be calculated based on the permissions its granted, *including* any [overwrites](/docs/topics/permissions#permission-overwrites). Previously, a bot’s permissions in these cases relied only on those granted to `@everyone`.
-
-This change *only* applies to bots. The permissions for an app without a bot user (or without the `bot` scope) will still depend on `@everyone`.
-
-#### Updating Your App
-
-If your bot wants to use the `MENTION_EVERYONE`, `SEND_TTS_MESSAGES` or `USE_EXTERNAL_EMOJIS` permissions when responding to interactions or executing a webhook, **ensure that the bot was installed (or explicitly granted) with them**.
-
-Note that even if your bot is installed with certain permissions, they can be changed using overwrites. For interactions, you can use the [`app_permissions` field](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure) to determine your app or bot's contextual permissions before replying.
diff --git a/docs/change-log/2022-07-01-add-subcommand-groups-and-subcommands-to-message-interaction-objects.md b/docs/change-log/2022-07-01-add-subcommand-groups-and-subcommands-to-message-interaction-objects.md
deleted file mode 100644
index 06ab2203f9..0000000000
--- a/docs/change-log/2022-07-01-add-subcommand-groups-and-subcommands-to-message-interaction-objects.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: "Add Subcommand Groups and Subcommands to Message Interaction Objects"
-date: "2022-07-01"
-breaking: true
----
-
-While this is a breaking change, most apps only rely on interaction responses (`INTERACTION_CREATE`), *not* message interaction objects (`MESSAGE_CREATE`). [Interaction responses](/docs/interactions/receiving-and-responding#interaction-object-interaction-data) are unaffected by this change.
-
-#### Upcoming Changes
-
-Starting **July 18, 2022**, the `name` field for [message interaction objects](/docs/interactions/receiving-and-responding#message-interaction-object) will now include subcommands and subcommand groups in the value (along with the existing top-level command). In the future, we recommend not relying on this message interaction field.
-
-The format of the value will be the different command levels (if they exist), separated by spaces:
-` `
-
-The `name` field is only seen on messages that are a response to an interaction without an existing message, so interaction objects for message components don’t include this field.
-
-#### Updating your app
-
-Most apps only rely on interaction responses, not message interaction objects.
-
-We don't recommend that your app relies on the `name` field for message interactions objects, but if it does you should update your app to handle subcommands and subcommand groups that your app may encounter.
-
-As an example of the change, pretend your app had a command `/role` with subcommands `add` and `remove`. Currently, the `name` field in the original interaction payload would contain `role`. If you responded to that interaction with a message then fetched its contents, the `name` field for that message interaction object would contain `role` as well.
-
-After this change, the `name` field for the original interaction payload will still contain `role`. However, now if you responded to that interaction with a message then fetched its contents, the `name` field for that message interaction object would contain `role add` or `role remove`.
diff --git a/docs/change-log/2022-07-01-min-and-max-length-for-command-options.md b/docs/change-log/2022-07-01-min-and-max-length-for-command-options.md
deleted file mode 100644
index 0f98617868..0000000000
--- a/docs/change-log/2022-07-01-min-and-max-length-for-command-options.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Min and Max Length for Command Options"
-date: "2022-07-01"
----
-
-Application [command options](/docs/interactions/application-commands#application-command-object-application-command-option-structure) of type `STRING` now includes optional `min_length` and `max_length` fields to control the length of text a user can input.
-
-The value of `min_length` must be greater or equal to `0`, and the value of `max_length` must be greater or equal to `1`.
diff --git a/docs/change-log/2022-07-13-upcoming-permissions-change-to-webhook-routes.md b/docs/change-log/2022-07-13-upcoming-permissions-change-to-webhook-routes.md
deleted file mode 100644
index 5c4d943417..0000000000
--- a/docs/change-log/2022-07-13-upcoming-permissions-change-to-webhook-routes.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Upcoming Permissions Change to Webhook Routes"
-date: "2022-07-13"
----
-
-On August 8th, 2022 we will begin requiring the `VIEW_CHANNEL (1 << 10)` permission for webhook routes which require `MANAGE_WEBHOOKS (1 << 29)`, to align with our documented behavior. We don't expect that many applications will be affected by this, but in case you are, please ensure you have updated permissions needed for accessing the following routes:
-
-* [`GET /webhooks/{webhook.id}`](/docs/resources/webhook#get-webhook)
-* [`DELETE /webhooks/{webhook.id}`](/docs/resources/webhook#delete-webhook)
-* [`PATCH /webhooks/{webhook.id}`](/docs/resources/webhook#modify-webhook)
-* [`GET /channels/{channel.id}/webhooks`](/docs/resources/webhook#get-channel-webhooks)
-* [`POST /channels/{channel.id}/webhooks`](/docs/resources/webhook#create-webhook)
diff --git a/docs/change-log/2022-08-09-session-specific-gateway-resume-urls.md b/docs/change-log/2022-08-09-session-specific-gateway-resume-urls.md
deleted file mode 100644
index 372e85d8ed..0000000000
--- a/docs/change-log/2022-08-09-session-specific-gateway-resume-urls.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Session-specific Gateway Resume URLs"
-date: "2022-08-09"
----
-
-:::warn
-Starting on **September 12, 2022**, apps that aren’t using the new `resume_gateway_url` field to resume gateway sessions will be disconnected significantly faster than normal.
-:::
-
-A new `resume_gateway_url` field has been added to the [Ready](/docs/events/gateway-events#ready) gateway event to support session-specific gateway connections. The value of `resume_gateway_url` is a session-specific URL that should be used when resuming the gateway session after a disconnect. Previously, `wss://gateway.discord.gg` was used to connect *and* resume sessions, but should now only be used during the connection.
-
-At the moment, the value of `resume_gateway_url` will always be `wss://gateway.discord.gg` to give developers more time to adopt the new field. In the near future, the value will change to the session-specific URLs.
diff --git a/docs/change-log/2022-08-22-slash-command-mentions.md b/docs/change-log/2022-08-22-slash-command-mentions.md
deleted file mode 100644
index 5f7c452374..0000000000
--- a/docs/change-log/2022-08-22-slash-command-mentions.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Slash Command Mentions"
-date: "2022-08-22"
----
-
-This week, [Slash Command mentions](/docs/reference#message-formatting) are rolling out across all Discord clients (for Android, mentions are limited to the [React Native client](https://discord.com/blog/android-react-native-framework-update)). Clicking a Slash Command mention will auto-populate the command in the user's message input.
-
-Slash Command mentions use the following format: ``. You can also use `` and `` for subcommands and subcommand groups.
diff --git a/docs/change-log/2022-09-01-message-content-is-a-privileged-intent.md b/docs/change-log/2022-09-01-message-content-is-a-privileged-intent.md
deleted file mode 100644
index 871f445f18..0000000000
--- a/docs/change-log/2022-09-01-message-content-is-a-privileged-intent.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: "Message Content is a Privileged Intent"
-date: "2022-09-01"
-breaking: true
----
-
-As of today, [message content](/docs/events/gateway#message-content-intent) is a privileged intent for all verified apps *and* apps eligible for verification. More details about why it's becoming a privileged intent and how to apply for it is in the [Help Center FAQ](https://support-dev.discord.com/hc/articles/4404772028055-Message-Content-Privileged-Intent-FAQ).
-
-Any app that does not have the message content intent configured in its app's settings within the Developer Portal will receive empty values in fields that expose message content across Discord's APIs (including the `content`, `embeds`, `attachments`, and `components` fields). These restrictions do not apply for messages that a bot or app sends, in DMs that it receives, or in messages in which it is mentioned.
-
-#### If your app is verified
-
-Verified apps and verification-eligible apps must be approved for the message content intent to receive message content. If your verified app isn’t approved, or doesn’t account for the new message content restrictions, it will break for users.
-
-##### Temporary Message Content Intent
-
-Verified apps or apps that have submitted for verification can temporarily opt-in to a grace period which will allow your app to continue receiving message content until October 1. However, if you opt-in to the grace period, your app will be prevented from joining any additional servers until you opt-out. More details are in the [Help Center article](https://support-dev.discord.com/hc/en-us/articles/8561391080471).
-
-#### If your app is unverified
-
-Unverified apps must still must enable the intent in your app’s settings within the Developer Portal.
-
-Existing unverified apps will automatically have the message content intent toggled on in their settings. New unverified apps will have to manually toggle the intent in the Developer Portal.
diff --git a/docs/change-log/2022-09-14-forum-channels-release.md b/docs/change-log/2022-09-14-forum-channels-release.md
deleted file mode 100644
index c94ee3f568..0000000000
--- a/docs/change-log/2022-09-14-forum-channels-release.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Forum Channels Release"
-date: "2022-09-14"
----
-
-Forum channels ([`GUILD_FORUM` or `15`](/docs/resources/channel#channel-object-channel-types)) have been released to all community servers. `GUILD_FORUM` channels are a new channel type that only supports threads, which display differently than in text (`GUILD_TEXT`) channels.
-
-Check out the [forums topic](/docs/topics/threads#forums) for more information on the relevant APIs and technical details, and the [Forums FAQ](https://support.discord.com/hc/en-us/articles/6208479917079-Forum-Channels-FAQ#h_01G69FJQWTWN88HFEHK7Z6X79N) for more about the feature.
diff --git a/docs/change-log/2022-09-21-auto-moderation-spam-and-mention-spam-trigger-types.md b/docs/change-log/2022-09-21-auto-moderation-spam-and-mention-spam-trigger-types.md
deleted file mode 100644
index 4837b24829..0000000000
--- a/docs/change-log/2022-09-21-auto-moderation-spam-and-mention-spam-trigger-types.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Auto Moderation Spam and Mention Spam Trigger Types"
-date: "2022-09-21"
----
-
-Two new [trigger types](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) were added to Auto Moderation:
-
-* `MENTION_SPAM` blocks messages that mention more than a set number of unique server members or roles. Apps can define the number (up to 50) using the `mention_total_limit` field in the [trigger metadata object](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) when creating or updating an Auto Moderation rule.
-* `SPAM` blocks links and messages that are identified as spam.
-
-More information can be found in the [Auto Moderation documentation](/docs/resources/auto-moderation).
diff --git a/docs/change-log/2022-09-22-default-sort-order-for-forum-channels.md b/docs/change-log/2022-09-22-default-sort-order-for-forum-channels.md
deleted file mode 100644
index 26186c61c4..0000000000
--- a/docs/change-log/2022-09-22-default-sort-order-for-forum-channels.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Default Sort Order for Forum Channels"
-date: "2022-09-22"
----
-
-`default_sort_order` is an optional field in the [channel object](/docs/resources/channel) that indicates how the threads in a [forum channel](/docs/topics/threads#forums) will be sorted for users by default. Setting `default_sort_order` requires the `MANAGE_CHANNELS` permission.
-
-If `default_sort_order` hasn't been set, its value will be `null`.
diff --git a/docs/change-log/2022-10-13-new-select-menu-components.md b/docs/change-log/2022-10-13-new-select-menu-components.md
deleted file mode 100644
index 8704c710e5..0000000000
--- a/docs/change-log/2022-10-13-new-select-menu-components.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "New Select Menu Components"
-date: "2022-10-13"
----
-
-Four new select menu [component types](/docs/components/reference#component-object-component-types) have been added to make it easier to populate selects with common resources in Discord:
-
-* User select (type `5`)
-* Role select (type `6`)
-* Mentionable (user *and* role) select (type `7`)
-* Channel select (type `8`)
-
-The new select menu components are defined similarly to the existing string select menu—with the exception of not including the `options` field and, within channel select menus, having the option to include a `channel_types` field. The [select menu interaction](/docs/components/reference#user-select-examples) apps receive also contain a [`resolved` field](/docs/components/reference#user-select-examples) for the new components.
-
-More details can be found in the updated [select menu documentation](/docs/components/reference#component-object-component-types).
diff --git a/docs/change-log/2022-10-20-delete-ephemeral-messages.md b/docs/change-log/2022-10-20-delete-ephemeral-messages.md
deleted file mode 100644
index 5c57fe9185..0000000000
--- a/docs/change-log/2022-10-20-delete-ephemeral-messages.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Delete Ephemeral Messages"
-date: "2022-10-20"
----
-
-Ephemeral interaction responses and follow-ups can now be deleted with a valid interaction token using the following endpoints:
-
-* [`DELETE /webhooks///messages/@original`](/docs/interactions/receiving-and-responding#delete-original-interaction-response)
-* [`DELETE /webhooks///messages/`](/docs/interactions/receiving-and-responding#delete-followup-message)
-
-As a reminder, interaction tokens stay valid for up to 15 minutes after the interaction occurs. Details can be found in the [interaction documentation](/docs/interactions/receiving-and-responding).
diff --git a/docs/change-log/2022-11-04-add-auto-moderation-regex-support.md b/docs/change-log/2022-11-04-add-auto-moderation-regex-support.md
deleted file mode 100644
index 006cfd8f10..0000000000
--- a/docs/change-log/2022-11-04-add-auto-moderation-regex-support.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Add Auto Moderation Regex Support"
-date: "2022-11-04"
----
-
-Auto Moderation rules with [trigger\_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) `KEYWORD` now support
-a `regex_patterns` field in its [trigger\_metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types).
-Regex patterns are a powerful way to describe many keywords all at once using one expression. Only Rust flavored regex is supported, which can be tested in online editors such as [Rustexp](https://rustexp.lpil.uk/).
diff --git a/docs/change-log/2022-11-09-gamesdk-feature-deprecation.md b/docs/change-log/2022-11-09-gamesdk-feature-deprecation.md
deleted file mode 100644
index 00b1b88c7f..0000000000
--- a/docs/change-log/2022-11-09-gamesdk-feature-deprecation.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: "GameSDK Feature Deprecation"
-date: "2022-11-09"
-breaking: true
----
-
-To help keep us focused on the features, improvements, and gaming-related experiences that Discord users love, we are deprecating the following pieces of the GameSDK **starting today**, and decommissioning them on **Tuesday, May 2, 2023**:
-
- * [Achievements](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Achievements.md)
- * [Applications](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Applications.md)
- * [Voice](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Discord_Voice.md)
- * [Images](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Images.md)
- * [Lobbies](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Lobbies.md)
- * [Networking](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Networking.md)
- * [Relationships](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Relationships.md)
- * [Storage](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Storage.md)
- * [Store](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Store.mdmd)
-
-This deprecation period will last until **Tuesday May 2, 2023**, after which these pieces will be decommissioned and no longer work. The other pieces of the GameSDK will continue to be supported.
-
-We know that Discord is an important place for people to find belonging, and that using your Discord identity in games is a crucial part of that sense of belonging. You’ll still be able to use the GameSDK to integrate Rich Presence, relationships, entitlements, basic user information, and the overlay.
diff --git a/docs/change-log/2022-11-17-upcoming-application-command-permission-changes.md b/docs/change-log/2022-11-17-upcoming-application-command-permission-changes.md
deleted file mode 100644
index 13d21a536f..0000000000
--- a/docs/change-log/2022-11-17-upcoming-application-command-permission-changes.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: "Upcoming Application Command Permission Changes"
-date: "2022-11-17"
-breaking: true
----
-
-Based on feedback, we’re updating permissions for [application commands](/docs/interactions/application-commands) to simplify permission management and to make command permissions more closely resemble other permissions systems in Discord.
-
-Server admins can begin to opt-in to the command permission changes outlined here on a per-server basis **starting on December 16, 2022**. However, changes will not be applied to all servers **until late January or early February**.
-
-:::info
-Current permissions behavior is documented in [the application commands documentation](/docs/interactions/application-commands#permissions) and in [the changelog for the previous permissions update](/docs/change-log#updated-command-permissions)
-:::
-
-These changes are focused on how configured permissions are used by Discord clients, so most apps will be unaffected. However, if your app uses the [Update Permissions endpoint](/docs/interactions/application-commands#edit-application-command-permissions) (`PUT /applications//guilds//commands//permissions`), you may need to make updates and should read these changes carefully.
-
-#### Types of command permission configurations
-
-:::info
-The following information isn’t changing, but it’s helpful context to understand the changes.
-:::
-
-Discord’s clients determine whether a user can see or invoke a command based on three different permission configurations:
-
-* **Command-level permissions** are set up by an admin for a specific *command* in their server. These permissions affect only a specific command.
-* **App-level permissions** are set up by an admin for a specific *app* in their server. These permissions affect all commands for an app.
-* **`default_member_permissions`** are set up by an app when creating or updating a command. `default_member_permissions` apply to that command in *all* servers (unless an override exists). More information about `default_member_permissions` is [in the documentation](/docs/interactions/application-commands#application-command-permissions-object-using-default-permissions).
-
-The concepts of these permission configurations are not changing. But then of course, the question becomes…
-
-### What's changing?
-
-There are two changes around command permissions:
-
-1. The logic used to apply permission configurations to a user in a given context within Discord clients
-2. New `APPLICATION_COMMAND_PERMISSIONS_V2` guild feature flag to indicate whether that guild is using the old permissions logic or the new (upcoming) logic.
-
-Let's go deeper into both of these.
-
-#### 1. How permission configurations are applied in Discord
-
-##### Current behavior:
-
-Currently, these systems are **mutually-exclusive**, meaning that only one type of permission configuration is used to determine whether a user can invoke a command.
-
-With this current system, there is a clear hierarchy: command-level permission configurations take precedence (if present), then app-level permission configurations (if present), and finally `default_member_permissions` if neither are present.
-
-The implication of the current permissions system means that:
-
-* If any command-level permissions are configured, all app-level permissions and `default_member_permissions` are ignored for that command.
-* If any app-level permissions are configured, `default_member_permissions` is ignored for *all* of that app’s commands.
-
-This system leads to unintentional permission escalations, and can force moderators to manually re-define their app-level configurations to make small tweaks on the command-level.
-
-##### Upcoming behavior:
-
-The new system removes the mutual exclusion aspect, meaning that the different types of permission configurations work together rather than independently—specifically, more than one may be used to determine whether a user can invoke a command.
-
-**`default_member_permissions` continues to act as a “default” that a developer can set when creating or updating a command.**
-
-**App-level permission configurations now act as the "base" configuration.**
-
-App-level configurations define who is allowed to use the app and where. These will work *together* with `default_member_permissions`, meaning if a user is granted access via an app-level permission configuration, they will still be restricted to the `default_member_permissions` for each command (by default). No more accidentally granting `/ban` which requires `BAN_MEMBERS` to `@BotMemers` just because you gave them access to the app!
-
-**Command-level permission configurations now act as an “override” of the app-level.**
-
-Command-level configurations override what is present at the app-level *and* any restrictions set by `default_member_permissions`. This means that an admin can explicitly grant a user access to a specific command even if they are denied access on the app-level *or* if they don't have permissions that meet that command's `default_member_permissions`.
-
-If a command-level configuration does not exist for the given context, the system will fall back to looking at the app-level configuration.
-
-##### Flowchart for command permissions logic
-
-Below is a simplified flowchart that illustrates how permissions will be applied by the Discord client after the new changes take effect.
-
-
-
-#### 2. `APPLICATION_COMMAND_PERMISSIONS_V2` Guild Feature
-
-We added a new [`APPLICATION_COMMAND_PERMISSIONS_V2` feature flag](/docs/resources/guild#guild-object-guild-features) which indicates whether that server is using **the current permissions logic**.
-
-* If the flag *is* present, that server is using the old command permissions behavior.
-* If the flag *is not* present, that server has migrated from the old command permissions behavior to the new behavior.
-
-### Am I affected?
-
-Your app will only be affected if it uses the [`PUT /applications//guilds//commands//permissions`](/docs/interactions/application-commands#edit-application-command-permissions) endpoint. This is a pretty restricted endpoint used to manage and update application command permissions on behalf of admins, meaning that it requires the `applications.commands.permissions.update` scope.
-
-**If your app doesn’t use this endpoint, there’s nothing you need to prepare for these changes.**
-
-If your app does use this endpoint, you should read the section on preparing for changes below.
-
-### How do I prepare for the changes?
-
-To prepare for these changes, you should take two steps:
-
-**1. Use the `APPLICATION_COMMAND_PERMISSIONS_V2` flag**
-
-Use this flag to determine which permissions logic that server is using. While the transition from the old behavior to the new behavior is happening, you may need two code paths depending on if the flag is present or not.
-
-```py
-if 'APPLICATION_COMMAND_PERMISSIONS_V2' in guild.features:
- # Use current behaviors when interacting with endpoint
-else:
- # Use new permissions behaviors when interacting with endpoint
-```
-
-:::info
-If you don’t have access to guild features already through Gateway events, you can fetch that information using the [`GET /guilds/` endpoint](/docs/resources/guild#get-guild).
-:::
-
-**2. Modify the behavior based on your use case**
-
-After you know what permissions behavior the server is using, you should update how you handle that server specifically.
-
-To understand what changes you need to make, you should look at the assumptions users have when your app updates their server’s commands permissions. Do you have a web dashboard where admins update permissions? If so, analyze the logic of that dashboard and what your permission configurations are trying to do to map them to the new permissions behavior. Do you document what your app is doing in regards to certain command permissions you’re configuring on behalf of the admin? If so, map that documentation to the new behavior.
-
-If you are unsure, you can communicate with your admin users to ask if your new logic meets their expectations.
-
-#### What happens if I don’t update my app?
-
-If your app is affected and you don’t update it, permissions behavior that your app configures may not match what you or the users of your app expect.
-
-#### How long do I have to update my app?
-
-The new `APPLICATION_COMMAND_PERMISSIONS_V2` flag is already live, and you should start seeing it in guilds’ feature flags.
-
-The new permissions behavior will roll out **on December 16, 2022**. On this date, admins will begin to see a banner that allows them to *optionally* move their server to the new behavior.
-
-In **late January or early February**, all servers will be migrated to the new behavior. We'll post another changelog at this point, at which time you can remove any logic around the old permissions behavior.
diff --git a/docs/change-log/2022-11-22-add-auto-moderation-allow-list-for-keyword-rules-and-increase-max-keyword-rules-per-guild-limit.md b/docs/change-log/2022-11-22-add-auto-moderation-allow-list-for-keyword-rules-and-increase-max-keyword-rules-per-guild-limit.md
deleted file mode 100644
index 0d85293a43..0000000000
--- a/docs/change-log/2022-11-22-add-auto-moderation-allow-list-for-keyword-rules-and-increase-max-keyword-rules-per-guild-limit.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Add Auto Moderation Allow List for Keyword Rules and Increase Max Keyword Rules Per Guild Limit"
-date: "2022-11-22"
----
-
-* Auto Moderation rules with [trigger\_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) `KEYWORD` now support an `allow_list` field in its [trigger\_metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata). Any message content that matches an `allow_list` keyword will be ignored by the Auto Moderation `KEYWORD` rule. Each `allow_list` keyword can be a multi-word phrase and can contain [wildcard symbols](/docs/resources/auto-moderation#auto-moderation-rule-object-keyword-matching-strategies).
-* Increase maximum number of rules with `KEYWORD` [trigger\_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) per guild from 3 to 5
-* Increase maximum length for each regex pattern in the `regex_patterns` [trigger\_metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) field from 75 to 260.
diff --git a/docs/change-log/2022-12-12-add-application-connections-metadata-and-linked-roles.md b/docs/change-log/2022-12-12-add-application-connections-metadata-and-linked-roles.md
deleted file mode 100644
index d1bdb0560d..0000000000
--- a/docs/change-log/2022-12-12-add-application-connections-metadata-and-linked-roles.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "Add Application Connections Metadata and Linked Roles"
-date: "2022-12-12"
----
-
-Introducing [linked roles](https://discord.com/blog/connected-accounts-functionality-boost-linked-roles) as well as the ability for all developers to set up their own linked roles with an application. This includes:
-
-* New [`role_connections_verification_url`](/docs/resources/application#application-object) that can be set in the developer portal in order for the application to render as potential verification option for linked roles.
-* [Application metadata](/docs/resources/application-role-connection-metadata#application-role-connection-metadata-object) to specify more detailed linked role requirements.
-* New endpoints to [retrieve](/docs/resources/application-role-connection-metadata#get-application-role-connection-metadata-records) (`GET /applications//role-connections/metadata`) and [update](/docs/resources/application-role-connection-metadata#update-application-role-connection-metadata-records) (`PUT /applications//role-connections/metadata`) application connection metadata.
-* New [`role_connections.write`](/docs/topics/oauth2#shared-resources-oauth2-scopes) OAuth2 scope required to authenticate the below requests.
-* Endpoints to [retrieve](/docs/resources/user#get-current-user-application-role-connection) (`GET /users/@me/applications/{application.id}/role-connection`) and [update](/docs/resources/user#update-current-user-application-role-connection) (`PUT /users/@me/applications/{application.id}/role-connection`) a user's role connections, both of which return an [application role connection](/docs/resources/user#application-role-connection-object) object.
-
-:::info
-For a quick rundown on how to get started using linked roles, refer to the [tutorial](/docs/tutorials/configuring-app-metadata-for-linked-roles).
-:::
diff --git a/docs/change-log/2022-12-13-add-default-layout-setting-for-forum-channels.md b/docs/change-log/2022-12-13-add-default-layout-setting-for-forum-channels.md
deleted file mode 100644
index 496a459d23..0000000000
--- a/docs/change-log/2022-12-13-add-default-layout-setting-for-forum-channels.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Add Default Layout setting for Forum channels"
-date: "2022-12-13"
----
-
-`default_forum_layout` is an optional field in the [channel object](/docs/resources/channel) that indicates the default layout for posts in a [forum channel](/docs/topics/threads#forums). A value of 1 (`LIST_VIEW`) indicates that posts will be displayed as a chronological list, and 2 (`GALLERY_VIEW`) indicates they will be displayed as a collection of tiles. If `default_forum_layout` hasn't been set, the value will be `0`.
-
-Setting `default_forum_layout` requires the `MANAGE_CHANNELS` permission.
diff --git a/docs/change-log/2023-01-09-thread-member-details-and-pagination.md b/docs/change-log/2023-01-09-thread-member-details-and-pagination.md
deleted file mode 100644
index d0f89fea58..0000000000
--- a/docs/change-log/2023-01-09-thread-member-details-and-pagination.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Thread Member Details and Pagination"
-date: "2023-01-09"
-breaking: true
----
-
-A new `member` field was added to the [thread member object](/docs/resources/channel#thread-member-object). `member` is a [guild member object](/docs/resources/guild#guild-member-object) that will be included within returned thread member objects when the new `with_member` field is set to `true` in the [List Thread Members](/docs/resources/channel#list-thread-members) (`GET /channels//thread-members`) and [Get Thread Member](/docs/resources/channel#get-thread-member) (`GET /channels//thread-members/`) endpoints.
-
-Setting `with_member` to `true` will also enable pagination for the [List Thread Members](/docs/resources/channel#list-thread-members) endpoint. When the results are paginated, you can use the new `after` and `limit` fields to fetch additional thread members and limit the number of thread members returned. By default, `limit` is 100.
-
-#### Upcoming Changes
-
-Starting in API v11, [List Thread Members](/docs/resources/channel#list-thread-members) (`GET /channels//thread-members`) will *always* return paginated results, regardless of whether `with_member` is passed or not.
diff --git a/docs/change-log/2023-01-18-guild-audit-log-events.md b/docs/change-log/2023-01-18-guild-audit-log-events.md
deleted file mode 100644
index 0bbb3ac208..0000000000
--- a/docs/change-log/2023-01-18-guild-audit-log-events.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Guild Audit Log Events"
-date: "2023-01-18"
----
-
-At long last, a new [`GUILD_AUDIT_LOG_ENTRY_CREATE`](/docs/events/gateway-events#guild-audit-log-entry-create) event has been added to the gateway, allowing your application to react to moderation actions in guilds. The `VIEW_AUDIT_LOG` permission is required in order to receive these events, and the [`GUILD_MODERATION` intent](/docs/events/gateway#gateway-intents) needs to be set when connecting to the gateway.
diff --git a/docs/change-log/2023-02-08-increase-auto-moderation-keyword-limits.md b/docs/change-log/2023-02-08-increase-auto-moderation-keyword-limits.md
deleted file mode 100644
index 8a6e6d61bc..0000000000
--- a/docs/change-log/2023-02-08-increase-auto-moderation-keyword-limits.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: "Increase Auto Moderation Keyword Limits"
-date: "2023-02-08"
----
-
-* Increase maximum number of rules with `KEYWORD` [trigger\_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) per guild from 5 to 6
-* Increase maximum length for each keyword in the `keyword_filter` and `allow_list` [trigger\_metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) fields from 30 to 60.
diff --git a/docs/change-log/2023-02-10-update-to-locked-threads.md b/docs/change-log/2023-02-10-update-to-locked-threads.md
deleted file mode 100644
index 930be22417..0000000000
--- a/docs/change-log/2023-02-10-update-to-locked-threads.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "Update to Locked Threads"
-date: "2023-02-10"
----
-
-### Upcoming Changes
-
-Currently, threads in Discord (including forum posts) can either be archived or both locked and archived. Starting on **March 6, 2023**, threads will be able to be locked *without* being archived, which will slightly change the meaning of the [`locked` field](/docs/resources/channel#thread-metadata-object-thread-metadata-structure).
-
-`locked` currently indicates that a thread cannot be reopened by a user without the [`MANAGE_THREADS` (`1 << 34`) permission](/docs/topics/permissions#permissions-bitwise-permission-flags), but it doesn't restrict user activity within active (meaning non-archived) threads. After this change, users (including bot users) without the `MANAGE_THREADS` permission will be more restricted in locked threads. Users won't be able to create or update messages in locked threads, or update properties like its title or tags. Additionally, some user activity like deleting messages and adding or removing reactions will *only* be allowed in locked threads if that thread is also active (or un-archived).
-
-If a user or bot user has the `MANAGE_THREADS` permission, they will still be able to make changes to the thread and messages. The upcoming change does not affect the meaning of the [`archived` field](/docs/resources/channel#thread-metadata-object-thread-metadata-structure) or the behavior of a thread that is both locked and archived.
-
-### How do I prepare for this change?
-
-If your app is interacting with threads (including forum posts), it should check the state of the `locked` and/or `archived` field for the thread to understand which actions it can or cannot perform. It should also be prepared to handle any errors that it may receive when a thread is locked.
diff --git a/docs/change-log/2023-02-24-add-auto-moderation-custom-message-action-metadata-field.md b/docs/change-log/2023-02-24-add-auto-moderation-custom-message-action-metadata-field.md
deleted file mode 100644
index 4aaf655a63..0000000000
--- a/docs/change-log/2023-02-24-add-auto-moderation-custom-message-action-metadata-field.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Add Auto Moderation custom_message Action Metadata Field"
-date: "2023-02-24"
----
-
-Add new `custom_message` [action metadata](/docs/resources/auto-moderation#auto-moderation-action-object-action-metadata) for the `BLOCK_MESSAGE` [action type](/docs/resources/auto-moderation#auto-moderation-action-object-action-types)). You can now specify a custom string for every Auto Moderation rule that will be shown to members whenever the rule blocks their message. This can be used as an additional explanation for why a message was blocked and as a chance to help members understand your server's rules and guidelines.
diff --git a/docs/change-log/2023-04-06-interaction-channel-data.md b/docs/change-log/2023-04-06-interaction-channel-data.md
deleted file mode 100644
index 05d0ec8c58..0000000000
--- a/docs/change-log/2023-04-06-interaction-channel-data.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Interaction Channel Data"
-date: "2023-04-06"
----
-
-Interactions now contain a `channel` field which is a partial channel object and guaranteed to contain `id` and `type`. We recommend that you begin using this channel field to identify the source channel of the interaction, and may deprecate the existing `channel_id` field in the future. See the [interaction documentation](/docs/interactions/receiving-and-responding#interaction-object) for more details.
diff --git a/docs/change-log/2023-04-14-bot-users-added-to-all-new-apps.md b/docs/change-log/2023-04-14-bot-users-added-to-all-new-apps.md
deleted file mode 100644
index 6f3eecd7f0..0000000000
--- a/docs/change-log/2023-04-14-bot-users-added-to-all-new-apps.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Bot users added to all new apps"
-date: "2023-04-14"
----
-
-Starting today, [bot users](/docs/topics/oauth2#bot-vs-user-accounts) will be added to all newly-created apps. Settings and configuration options for bot users remain the same, and can still be accessed on the **Bot** page within your [app's settings](https://discord.com/developers/applications).
-
-If your app doesn't need or want a bot user associated with it, you can refrain from adding the [`bot` scope](/docs/topics/oauth2#shared-resources-oauth2-scopes) when installing your app.
diff --git a/docs/change-log/2023-05-03-unique-usernames-on-discord.md b/docs/change-log/2023-05-03-unique-usernames-on-discord.md
deleted file mode 100644
index 38b52d6761..0000000000
--- a/docs/change-log/2023-05-03-unique-usernames-on-discord.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: "Unique usernames on Discord"
-date: "2023-05-03"
----
-
-:::warn
-Bot users will stay on the legacy username system for now. More details can be found on the [Developer Help Center article](https://dis.gd/app-usernames).
-:::
-
-Discord’s username system is changing. Discriminators are being removed and new, unique usernames and display names are being introduced. You can read more details about how changes to the username system affects non-bot users in the [general Help Center article](https://dis.gd/usernames). To learn how it impacts bot users specifically, you can read the [Developer Help Center article](https://dis.gd/app-usernames).
-
-This changelog focuses only on the technical changes to be aware of to update your app's code.
-
-### Identifying migrated users
-
-The new username system will rollout to users over time rather than all at once. The value of a single zero (`"0"`) in the [`discriminator` field](/docs/resources/user#user-object-user-structure) on a user will indicate that the user has been migrated to the new username system. Note that the discriminator for migrated users will *not* be 4-digits like a standard discriminator (it is `"0"`, not `"0000"`). The value of the `username` field will become the migrated user's unique username.
-
-After migration of all users is complete, the `discriminator` field may be removed.
-
-#### Example migrated user
-
-```json
-{
- "id": "80351110224678912",
- "username": "nelly",
- "discriminator": "0",
- "global_name": "Nelly",
- "avatar": "8342729096ea3675442027381ff50dfe",
- "verified": true,
- "email": "nelly@discord.com",
- "flags": 64,
- "banner": "06c16474723fe537c283b8efa61a30c8",
- "accent_color": 16711680,
- "premium_type": 1,
- "public_flags": 64
-}
-```
-
-### Display names
-
-As part of the new username system, standard Discord users can define a non-unique display name. This value will be a new `global_name` field with a max length of 32 characters. If the user has not set a display name, `global_name` will be null.
-
-### Default avatars
-
-For users with migrated accounts, default avatar URLs will be based on the user ID instead of the discriminator. The URL can now be calculated using `(user_id >> 22) % 6`. Users on the legacy username system will continue using `discriminator % 5`.
diff --git a/docs/change-log/2023-05-05-add-join-raid-and-mention-raid-fields.md b/docs/change-log/2023-05-05-add-join-raid-and-mention-raid-fields.md
deleted file mode 100644
index d510c0a11f..0000000000
--- a/docs/change-log/2023-05-05-add-join-raid-and-mention-raid-fields.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: "Add Join Raid and Mention Raid fields"
-date: "2023-05-05"
----
-
-* Add Auto Moderation `mention_raid_protection_enabled` [trigger\_metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) field for the `MENTION_SPAM` [trigger\_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types). If this field and its parent `MENTION_SPAM` rule are enabled, Auto Moderation provides baseline detection against sudden spikes in mention activity that are normally indicative of mention raids.
-* Add `safety_alerts_channel_id` [guild](/docs/resources/guild#guild-object) field and [`RAID_ALERTS_DISABLED` guild feature flag](/docs/resources/guild#guild-object-guild-features) which are associated with join raid protection
diff --git a/docs/change-log/2023-08-01-new-guild-media-channel-type.md b/docs/change-log/2023-08-01-new-guild-media-channel-type.md
deleted file mode 100644
index 09fc576d35..0000000000
--- a/docs/change-log/2023-08-01-new-guild-media-channel-type.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "New GUILD_MEDIA channel type"
-date: "2023-08-01"
----
-
-* Add the [`GUILD_MEDIA` (16) channel type](/docs/resources/channel#channel-object-channel-types). `GUILD_MEDIA` channels only support threads, similar to `GUILD_FORUM` channels.
-
-Read the [media channel topic](/docs/topics/threads#media-channels) for more information on the relevant APIs and technical details, or the [media channel Help Center Article](https://creator-support.discord.com/hc/en-us/articles/14346342766743) for more about the feature.
diff --git a/docs/change-log/2023-08-02-public-preview-of-openapi-3.1-specification.md b/docs/change-log/2023-08-02-public-preview-of-openapi-3.1-specification.md
deleted file mode 100644
index 20190f5a24..0000000000
--- a/docs/change-log/2023-08-02-public-preview-of-openapi-3.1-specification.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Public Preview of OpenAPI 3.1 Specification"
-date: "2023-08-02"
----
-
-We're introducing an [OpenAPI 3.1 spec](https://github.com/discord/discord-api-spec) in public preview to make it easier and more reliable to develop with the HTTP API. While our current developer documentation requires manual reviews and updates, the OpenAPI spec is generated from the source code which means it better reflects the nooks, crannies, and nuances of the Discord API.
-
-:::warn
-The public preview of the OpenAPI spec is subject to breaking changes without advance notice, and should not be used within production environments. If you see something that looks incorrect or can be improved, you can [open an issue](https://github.com/discord/discord-api-spec/issues).
-:::
-
-The public spec can be found in the new [`discord-api-spec` repository on GitHub](https://github.com/discord/discord-api-spec).
diff --git a/docs/change-log/2023-08-08-activity-state-for-bot-users.md b/docs/change-log/2023-08-08-activity-state-for-bot-users.md
deleted file mode 100644
index 433b994c4b..0000000000
--- a/docs/change-log/2023-08-08-activity-state-for-bot-users.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Activity State for Bot Users"
-date: "2023-08-08"
----
-
-The `state` field in [activity objects](/docs/events/gateway-events#activity-object) can now be set when [updating presence](/docs/events/gateway-events#update-presence) for a bot user. The value of `state` will appear as a custom status for the bot user when an [activity's `type`](/docs/events/gateway-events#activity-object-activity-types) is set to `4`, or as additional data under an activity's name for other activity types.
diff --git a/docs/change-log/2023-08-10-embed-debugger.md b/docs/change-log/2023-08-10-embed-debugger.md
deleted file mode 100644
index cfc592485f..0000000000
--- a/docs/change-log/2023-08-10-embed-debugger.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Embed Debugger"
-date: "2023-08-10"
----
-
-We've released a new [Embed Debugger tool](https://discord.com/developers/embeds) that shows you how a URL's metadata will be parsed and rendered as a link embed within the Discord client. Use it to preview your site's embed, or debug why your site's link embed isn't working as expected.
diff --git a/docs/change-log/2023-08-23-team-member-roles.md b/docs/change-log/2023-08-23-team-member-roles.md
deleted file mode 100644
index 5b25ace460..0000000000
--- a/docs/change-log/2023-08-23-team-member-roles.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Team Member Roles"
-date: "2023-08-23"
----
-
-You can now select roles other than admin when inviting users or configuring members of a team. There are four [role types](/docs/topics/teams#team-member-roles-team-member-role-types) that a team member can be assigned: owner, admin, developer, or read-only. The team member object now has an additional [`role` field](/docs/topics/teams#data-models-team-member-object), which is a string representing the member's current role.
-
-Details about team member roles are in the updated [Teams documentation](/docs/topics/teams#team-member-roles).
diff --git a/docs/change-log/2023-09-22-default-value-in-auto-populated-select-menus.md b/docs/change-log/2023-09-22-default-value-in-auto-populated-select-menus.md
deleted file mode 100644
index 6a4713319c..0000000000
--- a/docs/change-log/2023-09-22-default-value-in-auto-populated-select-menus.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Default Value in Auto-populated Select Menus"
-date: "2023-09-22"
----
-
-A new `default_values` field was added for user (`5`), role (`6`), mentionable (`7`), and channel (`8`) [select menu components](/docs/components/reference). `default_values` is a list of [default value objects](/docs/components/reference#user-select-select-default-value-structure), which each include an `id` (the snowflake value for the resource), as well as a corresponding `type` (either `"user"`, `"role"`, or `"channel"`).
diff --git a/docs/change-log/2023-09-26-premium-app-subscriptions-available-in-the-us.md b/docs/change-log/2023-09-26-premium-app-subscriptions-available-in-the-us.md
deleted file mode 100644
index ac26f16d98..0000000000
--- a/docs/change-log/2023-09-26-premium-app-subscriptions-available-in-the-us.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: "Premium App Subscriptions Available in the US"
-date: "2023-09-26"
-topics:
-- "Premium Apps"
----
-
-Starting today, eligible US-based developers can monetize their verified apps with App Subscriptions. [App Subscriptions](/docs/monetization/overview) let you to charge your users for premium functionality with a recurring, monthly subscription.
-
-* Manage subscription SKUs in the Developer Portal
-* View monetization analytics in the Developer Portal
-* Team owners can setup and manage payouts in Developer Portal
-* New endpoints for working with [SKUs](/docs/resources/sku) and [Entitlements](/docs/resources/entitlement):
- * [List SKUs](/docs/resources/sku#list-skus) `GET /applications//skus`
- * [List Entitlements](/docs/resources/entitlement#list-entitlements) `GET /applications//entitlements`
- * [Create Test Entitlement](/docs/resources/entitlement#create-test-entitlement) `POST /applications//entitlements`
- * [Delete Test Entitlement](/docs/resources/entitlement#delete-test-entitlement) `DELETE /applications//entitlements/`
-* [Gateway Events](/docs/events/gateway-events#entitlements) for working with entitlements: `ENTITLEMENT_CREATE`, `ENTITLEMENT_UPDATE`, `ENTITLEMENT_DELETE`
-* New [`PREMIUM_REQUIRED (10)` interaction response type](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-type) is available to prompt users to upgrade
-* New `entitlements` field, which is an array of [entitlement](/docs/resources/entitlement) objects, available in interaction data payloads when [receiving and responding to interactions](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure)
-
-To learn more about eligibility details and how to enable monetization for your app, check out the [Monetization Overview](/docs/monetization/overview).
diff --git a/docs/change-log/2023-10-17-global-rate-limit-added-to-discord.com.md b/docs/change-log/2023-10-17-global-rate-limit-added-to-discord.com.md
deleted file mode 100644
index 5a2123a8ba..0000000000
--- a/docs/change-log/2023-10-17-global-rate-limit-added-to-discord.com.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "Global Rate Limit added to discordapp.com/*"
-date: "2023-10-17"
----
-
-We have added a global rate limit for API requests made to `discordapp.com/*` and may further restrict requests in the future.
-
-To limit impact on your app, please make sure you are making calls to `discord.com/*`.
-
-This does **not** apply for `cdn.discordapp.com`.
-
-Refer to the [API Reference](/docs/reference) for more info on which url(s) to use when building on the REST API
-
-* [February 14, 2022 Change Log](/docs/change-log#api-v10): Requests to v10 and higher will no longer be supported on `discordapp.com` (this does not affect `cdn.discordapp.com`)
-* [May 4, 2020 #api-announcements](https://discord.com/channels/613425648685547541/697138785317814292/706944540971630662)
diff --git a/docs/change-log/2023-10-19-premium-app-subscriptions-now-available-in-the-eu-and-uk.md b/docs/change-log/2023-10-19-premium-app-subscriptions-now-available-in-the-eu-and-uk.md
deleted file mode 100644
index 90dd558764..0000000000
--- a/docs/change-log/2023-10-19-premium-app-subscriptions-now-available-in-the-eu-and-uk.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Premium App Subscriptions Now Available in the EU and UK"
-date: "2023-10-19"
-topics:
-- "Premium Apps"
----
-
-Starting today, eligible developers based in EU and UK can now monetize their verified apps with App Subscriptions. [App Subscriptions](/docs/monetization/overview) let you to charge your users for premium functionality with a recurring, monthly subscription.
-
-:::info
-New features for Premium App Subscriptions are documented in the [App Subscriptions overview](/docs/monetization/overview) and in [the changelog for the previous App Subscriptions release](/docs/change-log#premium-app-subscriptions-available-in-the-us).
-:::
-
-To learn more about eligibility details and how to enable monetization for your app, check out the [Monetization Overview](/docs/monetization/overview).
diff --git a/docs/change-log/2023-11-01-fix-message-edit-interaction-response-permissions.md b/docs/change-log/2023-11-01-fix-message-edit-interaction-response-permissions.md
deleted file mode 100644
index ed2e1eaadd..0000000000
--- a/docs/change-log/2023-11-01-fix-message-edit-interaction-response-permissions.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Fix Message Edit Interaction Response Permissions"
-date: "2023-11-01"
----
-
-Behavior for message edit interaction response actions like [updating interaction responses](/docs/interactions/receiving-and-responding#edit-original-interaction-response) and [sending follow-up messages](/docs/interactions/receiving-and-responding#followup-messages) have been updated to follow a bot user's permissions.
-
-Previously, some message edit interaction response actions would use the default permissions rather than a bot user's permissions.
diff --git a/docs/change-log/2023-11-29-premium-app-subscriptions-new-ways-for-testing-app-subscriptions.md b/docs/change-log/2023-11-29-premium-app-subscriptions-new-ways-for-testing-app-subscriptions.md
deleted file mode 100644
index 00eff1b453..0000000000
--- a/docs/change-log/2023-11-29-premium-app-subscriptions-new-ways-for-testing-app-subscriptions.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Premium App Subscriptions: New Ways for Testing App Subscriptions"
-date: "2023-11-29"
-topics:
-- "Premium Apps"
----
-
-Following feedback on Premium App Subscriptions, we've made it easier for developers to test their app subscriptions. The goal is to provide you with flexibility during testing and prevent you from having to use live payment methods.
-
-* Team members will automatically receive a 100% discount on a subscription for your app, allowing you to test the end-to-end payment flow
-* Developers can create and delete [test entitlements](/docs/resources/entitlement#create-test-entitlement) to toggle access to an application's premium features
-
-Read more about [Testing your App Subscriptions Implementation](/docs/monetization/implementing-app-subscriptions#testing-your-app-subscription-implementation) for details.
diff --git a/docs/change-log/2023-12-01-experimenting-with-end-to-end-encryption-for-voice-video.md b/docs/change-log/2023-12-01-experimenting-with-end-to-end-encryption-for-voice-video.md
deleted file mode 100644
index 9a160350d2..0000000000
--- a/docs/change-log/2023-12-01-experimenting-with-end-to-end-encryption-for-voice-video.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: "Experimenting with End-to-End Encryption for Voice & Video"
-date: "2023-12-01"
-topics:
-- "Voice"
----
-
-#### What’s Happening?
-
-As outlined in [a blog post earlier this year](https://discord.com/blog/encryption-for-voice-and-video-on-discord), we are experimenting with end-to-end encryption (e2ee) for voice and video channels.
-
-End-to-end encryption is designed to only allow the participants in a call to decipher its contents. One of the protocols we’re experimenting with is called Messaging Layer Security, which we believe would allow us to deliver end-to-end encryption at scale. Intermediaries, including platforms like Discord, are unable to access the content of communications encrypted with end-to-end encryption.
-
-#### How do I prepare for the changes?
-
-During this testing phase, there is nothing developers need to do to support end-to-end encryption. Voice channels will automatically downgrade to documented, non-e2ee protocols when a bot user joins the channel. This is transparent to the connecting client but may result in a slight delay between establishing a connection and receiving audio.
-
-#### What is planned for the future?
-
-We will be continuing our testing and will share updates along with developer documentation and sample code once it is available.
-
-Once this information is published, we will provide developers with a substantial timeframe to implement end-to-end encryption when interacting with voice and video.
diff --git a/docs/change-log/2023-12-15-clarification-on-permission-splits-for-expressions-and-events.md b/docs/change-log/2023-12-15-clarification-on-permission-splits-for-expressions-and-events.md
deleted file mode 100644
index f73e002f4f..0000000000
--- a/docs/change-log/2023-12-15-clarification-on-permission-splits-for-expressions-and-events.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "Clarification on Permission Splits for Expressions and Events"
-date: "2023-12-15"
----
-
-:::info
-The existing behavior for `MANAGE_GUILD_EXPRESSIONS` and `MANAGE_EVENTS` will **not be changing**. These permissions will continue to allow your bot users to create, update and delete expressions/events. No action will be needed if you plan to continue using these permissions.
-:::
-
-To support added controls for expressions and events, new [permissions](/docs/topics/permissions#permissions) were added for users and roles in July 2023:
-
-* `CREATE_GUILD_EXPRESSIONS`: `1 << 43`
-* `CREATE_EVENTS`: `1 << 44`
-
-These allow for creating new expressions and events, as well as editing and deleting those created by the current user.
-
-:::warn
-These were rolled out in July 2023 to users and roles and have been added to our developer documentation but **are not yet available to app developers**. We will share an update here when these new permissions are available in your apps.
-:::
diff --git a/docs/change-log/2023-12-19-limit-number-of-fields-in-embeds.md b/docs/change-log/2023-12-19-limit-number-of-fields-in-embeds.md
deleted file mode 100644
index 4755aa684a..0000000000
--- a/docs/change-log/2023-12-19-limit-number-of-fields-in-embeds.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Limit Number of Fields in Embeds"
-date: "2023-12-19"
----
-
-[Embed objects](/docs/resources/message#embed-object) are now limited more explicitly to 25 [embed fields](/docs/resources/message#embed-object-embed-field-structure). If you pass more than 25 fields within the an embed's `fields` property, an error will be returned.
-
-Previously, only the first 25 embed fields would be displayed within the embed but no error was returned.
diff --git a/docs/change-log/2024-00-20-soundboard-api.md b/docs/change-log/2024-00-20-soundboard-api.md
deleted file mode 100644
index 570b60a16a..0000000000
--- a/docs/change-log/2024-00-20-soundboard-api.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Soundboard API"
-date: "2024-09-20"
----
-
-[Soundboard](/docs/resources/soundboard) is now available in the API! Apps can now [get](/docs/resources/soundboard#list-default-soundboard-sounds) soundboard sounds, [modify](/docs/resources/soundboard#modify-guild-soundboard-sound) them, [send](/docs/resources/soundboard#send-soundboard-sound) them in voice channels, and listen to other users playing them!
diff --git a/docs/change-log/2024-02-12-enforced-nonces-on-create-message-endpoint.md b/docs/change-log/2024-02-12-enforced-nonces-on-create-message-endpoint.md
deleted file mode 100644
index ec6047161c..0000000000
--- a/docs/change-log/2024-02-12-enforced-nonces-on-create-message-endpoint.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Enforced Nonces on Create Message Endpoint"
-date: "2024-02-12"
----
-
-The [Create message](/docs/resources/message#create-message) endpoint now supports an `enforce_nonce` parameter. When set to true, the message will be deduped for the same sender within a few minutes. If a message was created with the same nonce, no new message will be created and the previous message will be returned instead. This behavior will become the default for this endpoint in a future API version.
diff --git a/docs/change-log/2024-03-15-guild-prune-requiring.md b/docs/change-log/2024-03-15-guild-prune-requiring.md
deleted file mode 100644
index 662f2611a6..0000000000
--- a/docs/change-log/2024-03-15-guild-prune-requiring.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Guild Prune Requiring"
-date: "2024-03-15"
-breaking: true
----
-
-The [Get Guild Prune Count](/docs/resources/guild#get-guild-prune-count) and [Begin Guild Prune](/docs/resources/guild#begin-guild-prune)
-endpoints now require the `MANAGE_GUILD` permission alongside the existing `KICK_MEMBERS` requirement `₍^ >ヮ<^₎ .ᐟ.ᐟ`.
diff --git a/docs/change-log/2024-03-18-discord-activities-developer-preview-of-the-embedded-app-sdk.md b/docs/change-log/2024-03-18-discord-activities-developer-preview-of-the-embedded-app-sdk.md
deleted file mode 100644
index 0895b7fa8a..0000000000
--- a/docs/change-log/2024-03-18-discord-activities-developer-preview-of-the-embedded-app-sdk.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "Discord Activities: Developer Preview of the Embedded App SDK"
-date: "2024-03-18"
-topics:
-- "Embedded App SDK"
-- "Activities"
----
-
-Discord Developers can now build Activities!
-
-Activities are interactive, multiplayer experiences that run in an iframe in Discord. In order to make the communication between your experience and Discord, we've introduced the Embedded App SDK to assist in communicating between your app and the Discord client.
-
-* New [Discord Activities](/docs/activities/overview) developer docs with a tutorial, code samples, development guides, and design principles.
-* The Embedded App SDK is now available via [npm](https://npmjs.com/package/@discord/embedded-app-sdk) and [GitHub](http://github.com/discord/embedded-app-sdk).
-* The [Embedded App SDK Reference](/docs/developer-tools/embedded-app-sdk) is now available.
-
-To learn more about how to get started building your own Activity, check out the [Activities Overview](/docs/activities/overview).
diff --git a/docs/change-log/2024-03-18-user-installable-apps-preview.md b/docs/change-log/2024-03-18-user-installable-apps-preview.md
deleted file mode 100644
index 078de6b426..0000000000
--- a/docs/change-log/2024-03-18-user-installable-apps-preview.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: "User-Installable Apps Preview"
-date: "2024-03-18"
-topics:
-- "User Apps"
----
-
-Apps can now be installed to users—making them easier to install, discover, and access across Discord. User-installed apps can be used across all of a user's servers, within their (G)DMs, and in DMs with the app's bot user.
-
-When creating or updating your app, you can choose which installation types your app supports on the **Installation** page in your [app's settings](https://discord.com/developers/applications). To quickly get started, you can follow the new [Developing a User-Installable App tutorial](/docs/tutorials/developing-a-user-installable-app) or read details about the new changes below.
-
-This change introduces new concepts and fields across the API that apps will now encounter—
-
-###### API Changes
-
-**Concepts:**
-
-* [Installation context](/docs/resources/application#installation-context) defines how an app was installed: to a user, a guild (server), or both. Currently, apps will default to only support the guild installation context, but the default may change in the future.
-* Commands can also support one or both installation contexts, with the default being the same as the app's supported installation context(s) at the time of command creation.
-* [Interaction context](/docs/interactions/application-commands#interaction-contexts) defines where a command can be used in Discord—within guilds, DM with your app's bot user, and/or within group DMs and DMs other than with your app's bot user.
-* The installation flow for apps have been updated so users can select whether they want to install an app to their account or to a server.
-
-**API Fields:**
-
-* New `integration_types_config` field for [Applications](/docs/resources/application#application-object) include the default scopes and permissions for app's supported installation contexts
-* New `integration_types` and `contexts` fields for [Commands](/docs/interactions/application-commands#application-command-object-application-command-structure) are the supported [installation](/docs/interactions/application-commands#installation-context) and [interaction](/docs/interactions/application-commands#interaction-contexts) contexts (respectively) for the command. Read [command contexts](/docs/interactions/application-commands#contexts) documentation for details.
-* New `context` field for [Interactions](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure) indicates the [interaction context](/docs/interactions/application-commands#interaction-contexts) where an interaction was triggered from.
-* New `authorizing_integration_owners` field for [Interactions](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure) includes a mapping of installation contexts that the interaction was authorized for, to related snowflakes for that context. Read [Authorizing Integration Owners Object](/docs/interactions/receiving-and-responding#interaction-object-authorizing-integration-owners-object) for details.
-* `app_permissions` is now always serialized for interactions to indicate what [permissions](/docs/topics/permissions#permissions-bitwise-permission-flags) your app has access to in the context its' responding. For (G)DMs with other users, it will include the `ATTACH_FILES | EMBED_LINKS | MENTION_EVERYONE`, and for DMs with the app's bot user it will also contain `USE_EXTERNAL_EMOJIS` for the bot’s DM
-* New `interaction_metadata` on [Messages](/docs/resources/message#message-object) that are created as part of an interaction response (either a response or follow-up). See [Message Interaction Metadata Object](/docs/resources/message#message-interaction-metadata-object) for details.
-* `dm_permission` field for [Commands](/docs/interactions/application-commands#application-command-object-application-command-structure) is deprecated. Apps should use `contexts` instead.
-* `interaction` field for [Messages](/docs/resources/message#message-object) is deprecated. Apps should use `interaction_metadata` instead.
-
-###### Limitations and Known Issues
-
-* During the preview, interaction responses for the user installation context will be forced to be ephemeral in servers with over 25 members. Forced ephemerality is enforced at the client-level, so your app does not need to manually pay attention to server size, and will not receive errors via the API.
-* All [follow-up messages](/docs/interactions/receiving-and-responding#followup-messages) are currently forced to be ephemeral in DMs
-* Follow-up messages have a bug where they will not correctly respect user permissions
diff --git a/docs/change-log/2024-04-02-csv-export-for-premium-app-analytics.md b/docs/change-log/2024-04-02-csv-export-for-premium-app-analytics.md
deleted file mode 100644
index 822894bfbf..0000000000
--- a/docs/change-log/2024-04-02-csv-export-for-premium-app-analytics.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "CSV Export for Premium App Analytics"
-date: "2024-04-02"
----
-
-For apps with [Monetization](/docs/monetization/overview) enabled, we have released the ability to export your SKU analytics to CSV. These exports allow you to use your preferred data tools to report on your premium offerings.
-
-You can find the export at the bottom of the `Monetization → Analytics` tab of your app to export data points such as `sales_count`, `sales_amount`, `sales_currencies`, `cancellation_count`, `refund_amount`, and `refund_count`, aggregated by each of your offerings for the selected month.
diff --git a/docs/change-log/2024-04-23-modify-guild-member-flags-field-permissions.md b/docs/change-log/2024-04-23-modify-guild-member-flags-field-permissions.md
deleted file mode 100644
index 71adb19bf8..0000000000
--- a/docs/change-log/2024-04-23-modify-guild-member-flags-field-permissions.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Modify Guild Member flags field permissions"
-date: "2024-04-23"
----
-
-Update permissions necessary to modify the `flags` field when calling the [Modify Guild Member](/docs/resources/guild#modify-guild-member) endpoint.
diff --git a/docs/change-log/2024-04-24-premium-apps-one-time-purchases-and-store.md b/docs/change-log/2024-04-24-premium-apps-one-time-purchases-and-store.md
deleted file mode 100644
index 6ce8562e40..0000000000
--- a/docs/change-log/2024-04-24-premium-apps-one-time-purchases-and-store.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: "Premium Apps: One-Time Purchases and Store"
-date: "2024-04-24"
----
-
-Two new features are now available for Premium Apps: One-Time Purchases and Stores.
-
-**One-Time Purchases**
-
-* **Durable Items**: A one-time purchase that is permanent and is not subject to either renewal or consumption, such as lifetime access to an app's premium features.
-* **Consumable Items**: A one-time, non-renewable purchase that provides access, such as a temporary power-up or boost in a game.
-
-Learn more about [Implementing One-Time Purchases](/docs/monetization/implementing-one-time-purchases).
-
-**A Store for Your Premium App**
-
-We have also introduced a Store for your Premium App to showcase your app subscriptions and one-time purchase items. You can now create a unique Store page within the developer portal and add your published subscription SKUs or one-time purchase SKUs to your store view, allowing your users to buy these items from your App Directory or Bot User Profile.
-
-To explore these features, eligibility details, and how to enable monetization for your app, check out the [Monetization Overview](/docs/monetization/overview).
-
-**API Documentation Updates**
-
-The following were added to our public Monetization documentation with this update:
-
-* New [SKU Object Types](/docs/resources/sku#sku-object-sku-types)
-* New [Entitlement Object Types](/docs/resources/entitlement#entitlement-object-entitlement-types)
-* [Consume an Entitlement](/docs/resources/entitlement#consume-an-entitlement) API endpoint
-* `consumed` field on the [Entitlement](/docs/resources/entitlement) resource
diff --git a/docs/change-log/2024-05-31-auto-moderation-member-profile-rule.md b/docs/change-log/2024-05-31-auto-moderation-member-profile-rule.md
deleted file mode 100644
index 59313f9694..0000000000
--- a/docs/change-log/2024-05-31-auto-moderation-member-profile-rule.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: "Auto Moderation Member Profile Rule"
-date: "2024-05-31"
----
-
-* Add Auto Moderation `MEMBER_PROFILE` rule [trigger\_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types). This rule type will check if a member's profile contains disallowed keywords.
-* Add Auto Moderation `BLOCK_MEMBER_INTERACTION` [action type](/docs/resources/auto-moderation#auto-moderation-action-object-action-types) currently available for the `MEMBER_PROFILE` rule [trigger\_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types). This action will "quarantine" the member to some extent and prevent them from performing most interactions within a specific server.
diff --git a/docs/change-log/2024-06-17-premium-apps-new-premium-button-style-deep-linking-url-schemes.md b/docs/change-log/2024-06-17-premium-apps-new-premium-button-style-deep-linking-url-schemes.md
deleted file mode 100644
index 0fc8dc6306..0000000000
--- a/docs/change-log/2024-06-17-premium-apps-new-premium-button-style-deep-linking-url-schemes.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: "Premium Apps: New Premium Button Style & Deep Linking URL Schemes"
-date: "2024-06-17"
----
-
-**New Premium Button Style**
-
-Introduces a new `premium` [button style](/docs/components/reference#button-button-styles) to be used with a `sku_id` which points to an active [SKU](/docs/resources/sku#sku-object). This allows developers to customize their premium experience by returning specific subscription or one-time purchase products.
-
-Learn more about using [button components with interactions](/docs/components/reference#button).
-
-:::warn
-This change deprecates Interaction Response Type 10
-:::
-
-The `PREMIUM_REQUIRED (10)` interaction response type is now deprecated in favor of using custom premium buttons. This will continue to function but may be eventually unsupported. It is recommended to migrate your bots to use the more flexible [premium button component](/docs/components/reference#button-button-styles).
-
-Learn more about [gating features with premium interactions](/docs/monetization/implementing-app-subscriptions#prompting-users-to-subscribe).
-
-**Deep Linking URL Schemes for SKUs and Store**
-
-Introduces two new url schemes for linking directly to the Application Directory. When these links are used in chat, they are rendered as rich embeds that users can interact with to launch an app's store or open a SKU detail modal.
-
-* New [Store URL Scheme](/docs/monetization/managing-skus#linking-to-your-store): `https://discord.com/application-directory/:appID/store`
-* New [SKU URL Scheme](/docs/monetization/managing-skus#linking-to-a-specific-sku): `https://discord.com/application-directory/:appID/store/:skuID`
diff --git a/docs/change-log/2024-06-27-user-installed-apps-general-availability.md b/docs/change-log/2024-06-27-user-installed-apps-general-availability.md
deleted file mode 100644
index 86923c9485..0000000000
--- a/docs/change-log/2024-06-27-user-installed-apps-general-availability.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: "User-Installed Apps General Availability"
-date: "2024-06-27"
-breaking: true
----
-
-Back in March, we announced [the beta for user-installed apps](/docs/change-log#userinstallable-apps-preview). After listening and making updates based on feedback from developers and modmins, we're excited to announce that user-installed apps are now considered generally available and can be used in all servers (regardless of size).
-
-With this update, there are a few API and behavioral updates for user-installed apps.
-
-###### API Updates
-
-* `user_id` has been removed from the `interaction_metadata` field on messages. Instead, you can use the `id` field in the nested `user` object. See the [Message Interaction Metadata Object](/docs/resources/message#message-interaction-metadata-object) for details.
-* User-installed apps are now limited to creating a maximum of 5 [follow-ups](/docs/interactions/receiving-and-responding#followup-messages) when responding to interactions. This only affects the [Create Followup Message endpoint](/docs/interactions/receiving-and-responding#create-followup-message), and apps installed to the server are unaffected.
-* On [Interactions](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure), the value of `authorizing_integration_owners` is now correctly serialized as a string. Previously, the `"0"` value was incorrectly serialized as a number.
-* `app_permissions` on [Interactions](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure) now correctly represents the permissions for user-installed apps. Previously, the value was incorrect for user-installed apps.
-* Updating a message can result in a `400` response if the content of the message was blocked by AutoMod, which may be particularly important for [deferred messages](/docs/interactions/receiving-and-responding#responding-to-an-interaction).
-* Interaction responses are no longer forced to be ephemeral for servers with over 25 members.
-
-###### New `Use External Apps` Permission
-
-A new [`USE_EXTERNAL_APPS` (`1 << 50`) permission](/docs/topics/permissions#permissions-bitwise-permission-flags) was added, and is enabled for servers by default. The new permission lets modmins control whether user-installed apps can post public replies in a server. If `Use External Apps` is disabled and your app is *not* installed to the server, your app’s responses will be ephemeral for the end user.
-
-Read more in the [Moderating Apps on Discord Help Center article](https://support.discord.com/hc/en-us/articles/23957313048343-Moderating-Apps-on-Discord#h_01HZQQQEADYVN2CM4AX4EZGKHM).
-
-###### Updated Defaults for New Apps
-
-* Newly-created apps now default to having both "User Install" *and* "Guild Install" [installation contexts](/docs/resources/application#installation-context) enabled. This can be updated in the **Installation** tab in an [app's settings](https://discord.com/developers/applications).
-* Newly-created apps now default to using the "Discord Provided Link" [install link](/docs/resources/application#install-links). This can be updated in the **Installation** tab in an [app's settings](https://discord.com/developers/applications).
-* If Discord Provided Link is selected as the install link type, `application.commands` scope is added to both installation contexts.
diff --git a/docs/change-log/2024-07-09-banners-in-get-current-user-guilds.md b/docs/change-log/2024-07-09-banners-in-get-current-user-guilds.md
deleted file mode 100644
index 01bd2d7777..0000000000
--- a/docs/change-log/2024-07-09-banners-in-get-current-user-guilds.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Banners in Get Current User Guilds"
-date: "2024-07-09"
----
-
-[`GET /users/@me/guilds`](/docs/resources/user#get-current-user-guilds) now includes each guild's `banner` field! This enables apps using OAuth2 with the `guilds` scope to display guild banners.
diff --git a/docs/change-log/2024-07-15-message-forwarding-rollout.md b/docs/change-log/2024-07-15-message-forwarding-rollout.md
deleted file mode 100644
index effebd5e77..0000000000
--- a/docs/change-log/2024-07-15-message-forwarding-rollout.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: "Message Forwarding rollout"
-date: "2024-07-15"
----
-
-We are slowly rolling out the message forwarding feature to users. This feature allows callers to create a message using `message_reference.type = FORWARD` and have the API generate a `message_snapshot` for the sent message. The feature has [some limitations](/docs/resources/message#message-reference-types) and the snapshot is a minimal version of a standard `MessageObject`, but does capture the core parts of a message.
-
-The resulting message will look something like:
-
-```json
-{
- "id": "1255957733279273083",
- "message_reference": {
- "type": 1, // Forward
- ...
- }
- "message_snapshots": [
- {
- "message": {
- "content": "original message",
- "embeds": [...],
- "attachments": [...],
- ...
- }
- }
- ],
- ...
-}
-```
-
-We have applied stricter rate limits for this feature based on the following:
-
-* number of forwards sent by the user
-* total attachment size
-
-###### API Updates since preview
-
-This was [previously announced](https://discord.com/channels/613425648685547541/697138785317814292/1233463756160503859) but note that the final API has a few changes since the API was first previewed:
-
-* [`message snapshot`](/docs/resources/message#message-snapshot-object) objects don't include a `guild` field anymore since the `message_reference` already provides that information
-* forwarded messages have a distinctive `message_reference` type of `FORWARD` now
diff --git a/docs/change-log/2024-07-16-member-banners.md b/docs/change-log/2024-07-16-member-banners.md
deleted file mode 100644
index 96796b6029..0000000000
--- a/docs/change-log/2024-07-16-member-banners.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: "Guild Member Banners"
-date: "2024-07-16"
-breaking: false
----
-
-Apps can now access guild member profile banners via the API and Gateway! The [guild member object](/docs/resources/guild#guild-member-object) now includes a `banner` field which can be used to create the [guild member banner URL](/docs/reference#image-formatting).
\ No newline at end of file
diff --git a/docs/change-log/2024-07-17-activities-proxy-csp-update.md b/docs/change-log/2024-07-17-activities-proxy-csp-update.md
deleted file mode 100644
index f5a8b24617..0000000000
--- a/docs/change-log/2024-07-17-activities-proxy-csp-update.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: "Activities Proxy CSP Update"
-date: "2024-07-17"
-breaking: true
-topics:
-- "Activities"
-- "Embedded App SDK"
----
-
-:::warn
-This change is outdated. We have since updated the Activities Proxy CSP and the use of `/.proxy/` is no longer required. For the latest information, please refer to [this changelog](/docs/change-log#remove-proxy-from-discord-activity-proxy-path).
-:::
-
-This change will be rolled out to all existing applications on **August 28, 2024**.
-
-We will be updating our Content Security Policy (CSP) for the Activities Domain (`https://.discordsays.com`). This represents a **breaking change** for **all Activities**, and as such we have a migration plan in order.
-
-our CSP will be updated as follows:
-
-* all requests must be made through `https://.discordsays.com/.proxy/`, and requests to other paths on the `discordsays.com` domain will be blocked.
-* requests to `https://discord.com/api/` will be permitted, but other paths on the `discord.com` domain will be blocked.
-* Only allowed paths on `cdn.discordapp.com` and `media.discordapp.net` will be permitted such as `/attachments/`, `/icons/`, and `/avatars/`.
-* nested child iframes must also mount paths prepended by `/.proxy/`
-
-As of [embedded-app-sdk v1.4.0](https://github.com/discord/embedded-app-sdk/releases/tag/v1.4.0) we have updated `patchUrlMappings` to automatically route requests through `/.proxy/`, so updating your SDK version calling `patchUrlMappings` is a good first step. If you are unfamiliar with `patchUrlMappings`, please consult the [documentation](/docs/activities/development-guides/networking#using-external-resources).
-
-All Application IDs created after `07/17/2024 12:00:00` UTC (applicationID greater than `1263102905548800000`) will also automatically have the new CSP applied. Testing your production code on a new application created after this date is a suggested way for developers to test compliance with this new CSP.
diff --git a/docs/change-log/2024-07-18-application-emoji.md b/docs/change-log/2024-07-18-application-emoji.md
deleted file mode 100644
index 936e991605..0000000000
--- a/docs/change-log/2024-07-18-application-emoji.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Application Emoji"
-date: "2024-07-18"
----
-
-You can now upload emojis for your application in your [app's settings](https://discord.com/developers/applications) and use them as custom emojis anywhere on Discord.
-
-* Up to 2000 emojis per app
-* Support for user-installable apps
-* Can be [managed via the API](/docs/resources/emoji#create-application-emoji) with a bot token
diff --git a/docs/change-log/2024-07-25-supported-activity-types-for-set-activity.md b/docs/change-log/2024-07-25-supported-activity-types-for-set-activity.md
deleted file mode 100644
index e56f9c1faa..0000000000
--- a/docs/change-log/2024-07-25-supported-activity-types-for-set-activity.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Supported Activity Types for SET_ACTIVITY"
-date: "2024-07-25"
----
-
-The [`SET_ACTIVITY` RPC command](/docs/topics/rpc#setactivity) has been updated to support 3 additional [activity types](/docs/events/gateway-events#activity-object-activity-types): Listening (`2`), Watching (`3`), and Competing (`5`). Previously, it only accepted Playing (`0`).
-
-:::warn
-The [Game SDK](/docs/developer-tools/game-sdk#activities) has not been updated to support setting [`ActivityType`](/docs/developer-tools/game-sdk#activitytype-enum), and is still limited to read-only (to handle events that you receive from Discord).
-:::
diff --git a/docs/change-log/2024-08-05-voice-state-endpoints.md b/docs/change-log/2024-08-05-voice-state-endpoints.md
deleted file mode 100644
index 3b4b23172d..0000000000
--- a/docs/change-log/2024-08-05-voice-state-endpoints.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Voice State Endpoints"
-date: "2024-08-05"
-topics:
-- "Voice"
-- "HTTP API"
----
-
-Voice states can now be accessed over the HTTP API! Apps can use the new [Get Current User Voice State](/docs/resources/voice#get-current-user-voice-state) and [Get User Voice State](/docs/resources/voice#get-user-voice-state) endpoints to fetch a user's voice state without a Gateway connection.
diff --git a/docs/change-log/2024-08-09-user-app-install-count.md b/docs/change-log/2024-08-09-user-app-install-count.md
deleted file mode 100644
index 9d1a917aaf..0000000000
--- a/docs/change-log/2024-08-09-user-app-install-count.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "User App Install Count"
-date: "2024-08-09"
-topics:
-- "User Apps"
----
-
-We've added an approximate user install count to the [Application object](/docs/resources/application#application-object) for user-installable apps. You can also view an app's install counts in the developer portal.
diff --git a/docs/change-log/2024-08-12-get-guild-role-endpoint.md b/docs/change-log/2024-08-12-get-guild-role-endpoint.md
deleted file mode 100644
index 3258729758..0000000000
--- a/docs/change-log/2024-08-12-get-guild-role-endpoint.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Get Guild Role Endpoint"
-date: "2024-08-12"
-topics:
-- "HTTP API"
----
-
-Need to get just one role, not the whole role list? Use the new [Get Guild Role](/docs/resources/guild#get-guild-role) endpoint to fetch a single role by ID.
diff --git a/docs/change-log/2024-08-13-voice-encryption-modes.md b/docs/change-log/2024-08-13-voice-encryption-modes.md
deleted file mode 100644
index 27e13b6c60..0000000000
--- a/docs/change-log/2024-08-13-voice-encryption-modes.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Voice Encryption Modes"
-date: "2024-08-13"
-topics:
-- "Voice"
----
-
-Added documentation for voice [encryption modes](/docs/topics/voice-connections#transport-encryption-modes) `aead_aes256_gcm_rtpsize` and `aead_xchacha20_poly1305_rtpsize` while announcing the deprecation of all `xsalsa20_poly1305*` variants and `aead_aes256_gcm`. Deprecated encryption modes will be discontinued as of November 18th, 2024.
-
-:::danger
-Deprecated encryption modes will be discontinued as of November 18th, 2024.
-:::
diff --git a/docs/change-log/2024-08-13-voice-gateway-version-8-and-deprecation-of-versions-older-than-4.md b/docs/change-log/2024-08-13-voice-gateway-version-8-and-deprecation-of-versions-older-than-4.md
deleted file mode 100644
index 4e1fbd40f4..0000000000
--- a/docs/change-log/2024-08-13-voice-gateway-version-8-and-deprecation-of-versions-older-than-4.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "Voice Gateway Version 8 and Deprecation of Versions < 4"
-date: "2024-08-13"
-topics:
-- "Gateway"
-- "Voice"
----
-
-We are officially deprecating some very old voice gateway versions (> 7 years ago).
-
-* The voice gateway now supports a resume which re-sends lost messages. Use voice gateway version 8 and refer to [Buffered Resume](/docs/topics/voice-connections#buffered-resume).
-* We have removed the default option for voice gateway version. Once this is deprecated, you must pass a voice gateway version.
-
-:::danger
-You will be required to pass a voice gateway version and deprecated voice gateway versions will be discontinued as of November 18th, 2024. See [Voice Gateway Versioning](/docs/topics/voice-connections#voice-gateway-versioning) for futher details.
-:::
diff --git a/docs/change-log/2024-08-26-entry-point-commands.md b/docs/change-log/2024-08-26-entry-point-commands.md
deleted file mode 100644
index 6f868a962e..0000000000
--- a/docs/change-log/2024-08-26-entry-point-commands.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "Entry Point Commands"
-date: "2024-08-26"
-topics:
-- "Activities"
-- "Interactions"
----
-
-Apps with [Activities](/docs/activities/overview) enabled can now create [Entry Point commands](/docs/interactions/application-commands#entry-point-commands) using the `PRIMARY_ENTRY_POINT` (type `4`) [command type](/docs/interactions/application-commands#application-command-object-application-command-types). Apps are limited to one globally-scoped Entry Point command, which appears in the App Launcher.
-
-When creating or updating an Entry Point command, an [Entry Point handler](/docs/interactions/application-commands#application-command-object-entry-point-command-handler-types) can be defined using the [`handler` field](/docs/interactions/application-commands#application-command-object-application-command-structure). The `handler` field determines whether your app wants to manually handle responding to the interaction:
-- If the value is `DISCORD_LAUNCH_ACTIVITY` (`2`), Discord will automatically handle the interaction and send a follow-up message to the channel where the Entry Point command was invoked from.
-- If the value is `APP_HANDLER` (`1`), your app will receive an interaction token and will be responsible for responding to the interaction. In this case, you can launch your Activity using the `LAUNCH_ACTIVITY` (type `12`) [interaction callback](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-type).
-
-More details about Entry Point commands can be found in the [Application Commands documentation](/docs/interactions/application-commands#entry-point-commands) and in the [Activity development guide](/docs/activities/development-guides/user-actions#setting-up-an-entry-point-command).
-
-### Default Entry Point Commands
-
-Starting today, when you enable Activities in your [app's settings](http://discord.com/developers/applications), a [default Entry Point command](/docs/interactions/application-commands#default-entry-point-command) called "Launch" will automatically be created for your app. This can be customized or deleted like other commands if you want to update the name or handler type.
diff --git a/docs/change-log/2024-08-26-launching-activities-via-interactions.md b/docs/change-log/2024-08-26-launching-activities-via-interactions.md
deleted file mode 100644
index 674281d66d..0000000000
--- a/docs/change-log/2024-08-26-launching-activities-via-interactions.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Launching Activities in Response to Interactions"
-date: "2024-08-26"
-topics:
-- "Activities"
-- "Interactions"
----
-
-[Activities](/docs/activities/overview) can now be launched as a response to interactions using the `LAUNCH_ACTIVITY` (type `12`) [interaction callback type](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-type). `LAUNCH_ACTIVITY` can be used in response to `APPLICATION_COMMAND`, `MESSAGE_COMPONENT`, and `MODAL_SUBMIT` [interaction types](/docs/interactions/receiving-and-responding#interaction-object-interaction-type).
diff --git a/docs/change-log/2024-08-28-subscription-api-and-entitlement-migration.md b/docs/change-log/2024-08-28-subscription-api-and-entitlement-migration.md
deleted file mode 100644
index 87d237801d..0000000000
--- a/docs/change-log/2024-08-28-subscription-api-and-entitlement-migration.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-title: "Premium Apps: Entitlement Migration and New Subscription API"
-date: "2024-08-28"
-topics:
-- "Premium Apps"
-breaking: true
----
-
-:::info
-Updates to this Change Log entry was published on **October 7, 2024** to reflect up-to-date information. See the [new Change Log entry](/docs/change-log#updates-to-entitlement-migration-guide) for details on updates.
-:::
-
-We are migrating our entitlement system to a new behavior where entitlements will not end until explicitly canceled, representing a breaking change for subscription management. We are introducing a [Subscription API](/docs/resources/subscription) and [Subscription Events](/docs/events/gateway-events#subscriptions) to allow handling subscription-related events.
-
-:::warn
-This change will be rolled out to all existing applications that have entitlements for user and guild subscription SKUs, starting on October 1, 2024.
-:::
-
-#### Entitlement Migration Details
-
-- `ENTITLEMENT_CREATE` events will now be triggered with a null `ends_at` value for all ongoing subscriptions, indicating an indefinite entitlement.
-- `ENTITLEMENT_UPDATE` events will occur only when a subscription ends, with the `ends_at` value indicating the end date.
-- Discord-managed Subscription entitlements will have an `type` value of `PURCHASE` (type `1`) instead of `APPLICATION_SUBSCRIPTION` (type `8`).
-
-### Migration Plan & Guide:
-
-As of **October 1, 2024**, all existing entitlements that grant access to user-subscription and guild-subscription SKUs will automatically transfer to the new system on their renewal date. This means we will have a month-long migration window to allow all of your entitlements to migrate to the new system upon renewal.
-
-Developers are advised to update their systems to handle the new `ENTITLEMENT_CREATE` and `ENTITLEMENT_UPDATE` events according to the following migration guide before the rollout date to avoid service disruptions.
-
-### Introducing a New Subscription API
-
-With the new entitlement behavior, entitlements for subscription SKUs will no longer emit events at the start of a new subscription billing period. Instead, subscription lifecycle management can be handled through the new [Subscription API](/docs/monetization/implementing-app-subscriptions#using-the-subscription-api).
-Developers should refer to the [Subscription resource](/docs/resources/subscription) for information on calling the Subscription API and responding to Subscription events. For in-depth implementation details, see our [Implementing App Subscriptions](/docs/monetization/implementing-app-subscriptions#using-the-subscription-api) guide. You can start using this API now.
-
-### Monetization Documentation Updates
-
-As part of these changes, we've updated the documentation for Premium Apps.
-
-- Created a new [Enabling Monetization](/docs/monetization/enabling-monetization) page to cover setting up your team, managing payouts, and enabling monetization for your apps
-- Created a new [Managing SKUs](/docs/monetization/managing-skus#creating-a-sku) page to document how to create, update, publish, and promote your SKUs
-- Moved and added [Entitlement](/docs/resources/entitlement), [SKU](/docs/resources/sku) and [Subscription](/docs/resources/subscription) resources to the **Resources** section
-- Updated guides for [Implementing App Subscriptions](/docs/monetization/implementing-app-subscriptions) and [Implementing One-Time Purchases](/docs/monetization/implementing-one-time-purchases)
-
-### Subscription Entitlement Migration Guide
-
-Starting on **October 1, 2024**, we will be migrating our existing entitlement system to a new behavior where **entitlements do not expire until explicitly canceled**. This migration guide outlines the changes and impacts of this migration on developers and guides how to manage these changes effectively.
-
-:::warn
-With this update, entitlements for subscription SKUs will no longer emit events when a new subscription billing period begins. If you need to know when a subscription has been renewed, use the new [Subscription API](/docs/resources/subscription) and related [Subscription Gateway Events](/docs/events/gateway-events#subscriptions).
-:::
-
-### Current System
-
-Currently, entitlements for Subscription SKUs purchased through Discord have:
-
-- An `ends_at` date that corresponds to the subscription interval. This date is updated at each billing cycle.
-- A entitlement `type` value of `APPLICATION_SUBSCRIPTION` (type `8`).
-- An `ENTITLEMENT_UPDATE` event is triggered at the start of each new subscription period.
-
-### New System
-
-Post-migration, entitlements for Subscription SKUs purchased through Discord will:
-
-- No longer have an end date (`ends_at` will be `null`) until the user decides to cancel the subscription.
-- Now have an entitlement `type` value of `PURCHASE` (type `1`).
-- No `ENTITLEMENT_UPDATE` events will be triggered until the subscription is canceled.
-
-### Migration Timeline
-
-- **Migration Start Date:** October 1, 2024
-- **Migration End Date:** November 1, 2024
-
-### Migration Impacts
-
-### 1) Existing Entitlements Scheduled to Renew
-
-- **During Migration Window:**
- - These will automatically transfer to the new system.
- - A new `ENTITLEMENT_CREATE` event will be triggered to indicate the migration. This does not indicate a net new entitlement.
- - No further events will be generated until the entitlement ends, which will then trigger an `ENTITLEMENT_UPDATE` event.
- - The `ends_at` value in the `ENTITLEMENT_UPDATE` event and in the Entitlement API will indicate the timestamp when the entitlement ends.
-
-### 2) Existing Entitlements Set to End
-
-- **During Migration Window:**
- - These entitlements will naturally expire and not renew under the new system.
- - No new entitlement events will be generated for these cases.
-
-### Developer Actions
-
-- **Pre-Migration:**
- - Review and understand the new entitlement event structure.
- - Adjust your system to handle `ends_at` being null, which now indicates an indefinite entitlement.
- - Adjust your system not to expect type `APPLICATION_SUBSCRIPTION` (type `8`) for Discord-managed subscription entitlements.
-- **Post-Migration:**
- - Monitor for `ENTITLEMENT_CREATE`, `ENTITLEMENT_UPDATE`, `SUBSCRIPTION_CREATE`, and `SUBSCRIPTION_UPDATE` events.
- - Update any references to an entitlement `ends_at` timestamps, which now indicate the ending of an entitlement. If you need to know when a subscription's period ends, use the [Subscription API](/docs/resources/subscription) and related [Subscription Gateway Events](/docs/events/gateway-events#subscriptions).
-
-
-- The Entitlement Migration begins on October 1, 2024
-- You have an existing user subscription that has an existing `ends_at` timestamp for October 10, 2024.
-- If the subscription renews successfully, you will receive an `ENTITLEMENT_CREATE` event on October 10, 2024, with an `ends_at` value of null
-- ~~If you receive an `ENTITLEMENT_UPDATE` event with an `ends_at` timestamp, the entitlement for this subscription is expected to end at the timestamp value unless you receive subsequent `ENTITLEMENT_UPDATE` events between the cancellation and the `ends_at` value.~~
-
diff --git a/docs/change-log/2024-09-04-add-polls-when-editing-deferred-interaction-responses.md b/docs/change-log/2024-09-04-add-polls-when-editing-deferred-interaction-responses.md
deleted file mode 100644
index 6b4bb2efce..0000000000
--- a/docs/change-log/2024-09-04-add-polls-when-editing-deferred-interaction-responses.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Add Polls when Editing Deferred Interaction Responses"
-date: "2024-09-04"
-topics:
-- "Interactions"
----
-
-You can now create a poll while editing a deferred interaction response with the [Edit Original Interaction Response](/docs/interactions/receiving-and-responding#edit-original-interaction-response) endpoint. Poll away!
diff --git a/docs/change-log/2024-09-17-voice-e2ee-dave-protocol.md b/docs/change-log/2024-09-17-voice-e2ee-dave-protocol.md
deleted file mode 100644
index a1b08e9069..0000000000
--- a/docs/change-log/2024-09-17-voice-e2ee-dave-protocol.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: "Voice End-to-End Encryption (DAVE Protocol)"
-date: "2024-09-17"
-topics:
-- "Voice"
----
-
-Introduced [high-level documentation](/docs/topics/voice-connections) for Discord's Audio and Video End-to-End Encryption (DAVE) protocol, and the [new voice gateway opcodes](/docs/topics/opcodes-and-status-codes#voice) required to support it
-
-### **Developer Impact**
-
-Starting September 2024, Discord is migrating voice and video in DMs, Group DMs, voice channels, and Go Live streams to use end-to-end encryption (E2EE).
-
-**Who this affects:** Any libraries or apps that support [Voice Connections](/docs/topics/voice-connections).
-
-You are not immediately required to support the E2EE protocol, as calls will automatically upgrade/downgrade to/from E2EE depending on the support of clients in the call.
-
-### **Implementing E2EE Voice**
-
-We have added high-level documentation for Discord's Audio and Video End-to-End Encryption (DAVE) protocol, and the new voice gateway opcodes required to support it.
-
-The most thorough documentation on the DAVE protocol is found in the [Protocol Whitepaper](https://daveprotocol.com/). You can also use our open-source library [libdave](https://github.com/discord/libdave) to assist with your implementation. The exact format of the DAVE protocol opcodes is detailed in the [Voice Gateway Opcodes section of the protocol whitepaper](https://daveprotocol.com/#voice-gateway-opcodes).
-
-### **Future Deprecation and Discontinuation of Non-E2EE Voice**
-
-Non-E2EE connections to voice in DMs, Group DMs, voice channels, and Go Live streams will eventually be deprecated and discontinued.
-
-In 2025, all official Discord clients will support the protocol and it will be an enforced requirement to connect to the end-to-end encryption-eligible audio/video session types listed above.
-
-Once a timeline for deprecation and discontinuation is finalized, we will share details and developers will have **at least six months** to implement before we sunset non-E2EE voice connections.
-
-Read more about Discord's Audio and Video End-to-End Encryption (DAVE) protocol:
-
-- [Meet DAVE: Discord's New End-to-End Encryption for Audio & Video](https://discord.com/blog/meet-dave-e2ee-for-audio-video)
-- [DAVE Protocol Whitepaper](https://daveprotocol.com/)
-- [libdave open-source library on GitHub](https://github.com/discord/libdave)
\ No newline at end of file
diff --git a/docs/change-log/2024-09-26-activities-general-availability.md b/docs/change-log/2024-09-26-activities-general-availability.md
deleted file mode 100644
index b4488cb0e8..0000000000
--- a/docs/change-log/2024-09-26-activities-general-availability.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: "Activities General Availability"
-date: "2024-09-26"
-topics:
-- "Activities"
-- "Embedded App SDK"
-- "Premium Apps"
----
-
-Following up on [the rollout of the App Launcher](https://discord.com/blog/discover-more-ways-to-play-with-apps-now-anywhere-on-discord), we’re excited to announce that [Activities](/docs/activities/overview) are now generally available for developers. In addition to API stability, this means that apps with Activities can now be [verified](https://support-dev.discord.com/hc/en-us/articles/23926564536471-How-Do-I-Get-My-App-Verified), [discoverable](/docs/discovery/enabling-discovery) in the App Directory, and [implement monetization](/docs/monetization/overview).
-
-### Recent API Updates
-
-Since the developer preview was announced, there have been a few important API updates:
-
-- Activities can now enable and implement monetization features, and [`getEntitlements`](/docs/developer-tools/embedded-app-sdk#getentitlements),[`getSkus`](/docs/developer-tools/embedded-app-sdk#getskus), and [`startPurchase`](/docs/developer-tools/embedded-app-sdk#startpurchase) are generally available in the Embedded App SDK.
-- New [Get Application Activity Instance](/docs/resources/application#get-application-activity-instance) endpoint to make [managing Activity instances](/docs/activities/development-guides/multiplayer-experience#activity-instance-management) easier.
-- Apps with Activities can create an [Entry Point command (type `4`)](/docs/interactions/application-commands#entry-point-commands), which are the primary entry point for Activities in the App Launcher. When new apps enable Activities, a [default Entry Point command](/docs/interactions/application-commands#default-entry-point-command) will be created for the app. Read the [original change log](/docs/change-log#entry-point-commands) and the [Entry Point command guide](/docs/activities/development-guides/user-actions#setting-up-an-entry-point-command) for details.
-- Activities can now be launched in response to interactions using the `LAUNCH_ACTIVITY` (type `12`) [interaction callback type](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-type) for `APPLICATION_COMMAND`, `MESSAGE_COMPONENT`, and `MODAL_SUBMIT` [interaction types](/docs/interactions/receiving-and-responding#interaction-object-interaction-type).
-- Apps can now be installed to users (in addition to servers). After [setting up your installation contexts](/docs/resources/application#setting-supported-installation-contexts), make sure to request the `application.commands` scope when authorizing with users to make sure your Activity is available for them across their Discord servers, DMs, and Group DMs.
-- In August, there were updates to the Content Security Policy (CSP) for Activities that limits how you can make requests to external resources when building Activities. Read [the change log](/docs/change-log#activities-proxy-csp-update) and the guide on [using external resources](/docs/activities/development-guides/networking#using-external-resources) for details.
-
-### Documentation Updates
-
-We’ve also added and improved the documentation for Activities and the Embedded App SDK to make it easier to build:
-
-- New reference documentation for [Monetization](/docs/monetization/overview) SDK commands: [`getEntitlements`](/docs/developer-tools/embedded-app-sdk#getentitlements),[`getSkus`](/docs/developer-tools/embedded-app-sdk#getskus), and [`startPurchase`](/docs/developer-tools/embedded-app-sdk#startpurchase)
-- Updated [Embedded App SDK Reference](/docs/developer-tools/embedded-app-sdk) documentation that adds signatures and arguments
-- Updated development guides for [Activity Instance Management](/docs/activities/development-guides/multiplayer-experience#activity-instance-management) and [Activity Proxy Considerations](/docs/activities/development-guides/networking#activity-proxy-considerations) when using external resources
-- New guide on implementing [In-App Purchases (IAP) for Activities](/docs/monetization/implementing-iap-for-activities)
-- New guides for [Verification and Discovery Surfaces](/docs/discovery/overview)
-- New guide on [Using Rich Presence with the Embedded App SDK](/docs/rich-presence/using-with-the-embedded-app-sdk)
diff --git a/docs/change-log/2024-10-04-updates-to-entitlement-migration-guide.md b/docs/change-log/2024-10-04-updates-to-entitlement-migration-guide.md
deleted file mode 100644
index cac73ebaa1..0000000000
--- a/docs/change-log/2024-10-04-updates-to-entitlement-migration-guide.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Updates to Entitlement Migration Guide"
-date: "2024-10-07"
-topics:
-- "Premium Apps"
----
-
-The entitlement migration started on **October 1, 2024** and will continue through 11:59PM PST on **November 1, 2024**.
-
-We updated our previous entitlement migration guide to provide more up-to-date information on impacts of developer impacts. Here's a summary of the changes we made:
-
-- The migration will run through November 1, 2024 to ensure that any entitlements that are set to renew in October will be properly migrated to the new entitlement system upon renewal.
-- `ENTITLEMENT_UPDATE` events will only occur when a subscription ends.
-- The value of the `ends_at` in `ENTITLEMENT_UPDATE` events indicate the timestamp for **when the entitlement is no longer valid**.
-- The `ends_at` value on the [entitlement object](/docs/resources/entitlement#entitlement-object) is set when the subscription ends.
-- To receive the value of when a subscription was canceled, you should listen for the `SUBSCRIPTION_UPDATE` events or use the [Subscription API](/docs/resources/subscription).
-
-View the [updated migration guide](/docs/change-log#premium-apps-entitlement-migration-and-new-subscription-api).
-
-To see a full diff of the changes, refer to this pull request: [Entitlement Migration Guide Updates](https://github.com/discord/discord-api-docs/pull/7201).
\ No newline at end of file
diff --git a/docs/change-log/2024-10-25-event-webhooks.md b/docs/change-log/2024-10-25-event-webhooks.md
deleted file mode 100644
index 0ca8c6f5b6..0000000000
--- a/docs/change-log/2024-10-25-event-webhooks.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "Webhook Events"
-date: "2024-10-25"
-topics:
-- "Events"
-- "User Apps"
-
----
-
-You can now subscribe to a limited number of HTTP-based outgoing [webhook events](/docs/events/webhook-events#event-types) after [configuring a webhook events URL](/docs/events/webhook-events#configuring-a-webhook-events-url). Currently, 3 events are available: `APPLICATION_AUTHORIZED`, `ENTITLEMENT_CREATE`, and `QUEST_USER_ENROLLMENT`. Read the [webhook events](/docs/events/webhook-events) documentation for details on subscribing and using webhook events.
-
-:::info
-When developing [user-installable apps](/docs/resources/application#user-context), [Application Authorized](/docs/events/webhook-events#application-authorized) (which is not available via [the Gateway](/docs/events/gateway)) is useful to receive events when your app was installed to a user or server.
-:::
-
-:::warn
-`ENTITLEMENT_CREATE` is the only monetization-related event available using webhook events, so you should still use the Gateway for [entitlement-related events](/docs/events/gateway-events#entitlements). Other monetization-related events will be supported via webhook events soon.
-:::
\ No newline at end of file
diff --git a/docs/change-log/2024-11-05-post-entitlement-migration-update.md b/docs/change-log/2024-11-05-post-entitlement-migration-update.md
deleted file mode 100644
index 228512e5c5..0000000000
--- a/docs/change-log/2024-11-05-post-entitlement-migration-update.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "Entitlement Migration Completed"
-date: "2024-11-05"
-topics:
-- "Premium Apps"
----
-
-The [entitlement migration](/docs/change-log#premium-apps-entitlement-migration-and-new-subscription-api) which began on **October 1, 2024**, has been successfully completed as of **November 1, 2024**.
-
-### What's Changed
-
-- The documentation has been updated to reflect the new entitlement system as the standard behavior.
-- `ENTITLEMENT_UPDATE` event for subscription-related entitlements now only occur when the subscription ends.
-- The `ends_at` value on the [entitlement object](/docs/resources/entitlement#entitlement-object) is now set when the subscription ends.
-- To determine when a subscription was canceled, listen for `SUBSCRIPTION_UPDATE` events or use the [Subscription API](/docs/resources/subscription) to retrieve the subscription's `status` and `canceled_at` timestamp.
-
-For more details about the migration process, please refer to the [migration guide](/docs/change-log#updates-to-entitlement-migration-guide).
\ No newline at end of file
diff --git a/docs/change-log/2024-12-12-premium-apps-multiple-subscription-tiers.md b/docs/change-log/2024-12-12-premium-apps-multiple-subscription-tiers.md
deleted file mode 100644
index 8973656e44..0000000000
--- a/docs/change-log/2024-12-12-premium-apps-multiple-subscription-tiers.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: "Premium Apps: Multiple Subscription Tiers"
-date: "2024-12-12"
-topics:
-- "Premium Apps"
----
-
-Developers with monetization enabled can now create and publish multiple subscription SKUs of the same type for their app. This allows developers to offer different subscription tiers with varying benefits and pricing. Users can upgrade and downgrade between published subscription SKUs.
-
-### What's Changed
-
-#### Developer Portal
-- Under the `Monetization` tab, you can now publish multiple subscription SKUs of the same type for your app.
-
-#### App's Store Page
-- When multiple subscription SKUs are published: Users can now upgrade or downgrade between different published subscription SKUs.
-
-#### User App Subscription Settings
-- When multiple subscription SKUs are published: Users can now upgrade or downgrade between different published subscription SKUs.
-- These settings are available under `User Settings → Subscriptions → App Subscriptions`.
-
-#### Subscription Object
-- New field `renewal_sku_ids` added to the [subscription object](/docs/resources/subscription#subscription-object) response for `SUBSCRIPTION_UPDATE` events and API endpoints.
-- `renewal_sku_ids` is a list of snowflakes that indicate the SKU(s) that the user will be subscribed to at renewal.
-
-#### Updated Guide: Managing SKUs
-- The [Managing SKUs](/docs/monetization/managing-skus#creating-a-sku) guide has been updated to include information about creating and managing multiple subscription SKUs.
-
-#### Updated Guide: Implementing App Subscriptions
-- The [Implementing App Subscriptions](/docs/monetization/implementing-app-subscriptions#supporting-upgrades-and-downgrades) guide has been updated to include information about supporting upgrades and downgrades between multiple subscription SKUs.
\ No newline at end of file
diff --git a/docs/change-log/2024-12-17-updated-file-upload-limit.md b/docs/change-log/2024-12-17-updated-file-upload-limit.md
deleted file mode 100644
index 25c7e15133..0000000000
--- a/docs/change-log/2024-12-17-updated-file-upload-limit.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "Default File Upload Limit Change"
-date: "2024-12-16"
-breaking: true
-topics:
-- "HTTP API"
-- "Interactions"
----
-
-On January 16, 2025, the default file upload limit will change from 25 MiB to 10 MiB.
-
-While this limit is already active for users and bot users, it hasn't yet been applied to webhooks.
-
-- This change will take effect on January 16, 2025.
-- The 10 MiB limit will apply to both webhooks and interaction responses.
-
-For more information, check out [our documentation on file uploads](/docs/reference#uploading-files).
\ No newline at end of file
diff --git a/docs/change-log/2025-03-17-introducing-the-discord-social-sdk.md b/docs/change-log/2025-03-17-introducing-the-discord-social-sdk.md
deleted file mode 100644
index 4da78fc441..0000000000
--- a/docs/change-log/2025-03-17-introducing-the-discord-social-sdk.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: "Introducing the Discord Social SDK"
-date: "2025-03-17"
-topics:
-- "Discord Social SDK"
----
-
-Developers can now use the Discord Social SDK to build social features into their games, enabling friends lists, cross-platform messaging, voice and more for all players — with or without a Discord account.
-
-Discord Social SDK offers features that enhance connectivity and player engagement, including:
-
-- Account Linking
-- Provisional Accounts
-- Rich Presence
-- Deeplink Game Invites
-
-Additionally, available in a closed beta to support in-game communications:
-
-- Cross-Platform Messaging
-- Linked Channels
-- Voice Chat
-
-Developers can request expanded access to these available features via the closed beta.
-
-#### Discord Social SDK Developer Resources
-
-New resources are available in the Developer Portal to help you get started with the Discord Social SDK:
-
-- [Getting Started Guides](/docs/discord-social-sdk/getting-started) for C++, Unity and Unreal Engine.
-- [Development Guides](/docs/discord-social-sdk/development-guides) for building your game's social features.
-- [Design Guidelines](/docs/discord-social-sdk/design-guidelines) for designing your game's social features.
-- [SDK Reference](http://discord.com/developers/docs/social-sdk/index.html) is now available.
-- The Discord Social SDK binaries are available for download in the Developer Portal after enabling the Discord Social SDK for your application.
-
-To learn more about building with the Discord Social SDK, check out the [Discord Social SDK Overview](/docs/discord-social-sdk/overview).
diff --git a/docs/change-log/2025-04-03-per-attachment-file-upload-limit.md b/docs/change-log/2025-04-03-per-attachment-file-upload-limit.md
deleted file mode 100644
index 724d69f327..0000000000
--- a/docs/change-log/2025-04-03-per-attachment-file-upload-limit.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "Per-Attachment File Upload Behavior for Apps"
-date: "2025-04-03"
-breaking: false
-topics:
-- "HTTP API"
-- "Interactions"
----
-
-Starting today, file upload limits for apps are checked per-attachment rather than per-message. This change makes the app attachment behavior the same as when a user uploads multiple attachments on a single message.
-
-- File size limits now apply to each individual attachment
-- Previously, limits were applied to the combined size of all attachments in a message
-- This aligns app attachment handling with user attachment behavior
-
-The interaction payload will also include a new `attachment_size_limit` key that specifies the maximum allowed attachment size. This limit may be higher than the default attachment size limit, depending on the guild's boost status or the invoking user's Nitro status.
-
-For more information, check out [our documentation on file uploads](/docs/reference#uploading-files).
\ No newline at end of file
diff --git a/docs/change-log/2025-04-11-incentivized-links.md b/docs/change-log/2025-04-11-incentivized-links.md
deleted file mode 100644
index b3c6a1bcde..0000000000
--- a/docs/change-log/2025-04-11-incentivized-links.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "Custom Incentivized Links"
-date: "2025-04-11"
-topics:
-- "Activities"
-- "Embedded App SDK"
----
-
-### Custom Incentivized Links for Activities
-
-Custom Incentivized Links are used to customize how your incentivized link embed appears to users. You can create them in the developer portal or generate them from within your activity. Incentivized Links can be used as referral links, promotions, deep-linking into your activity, and more.
-
-- shareLink will now let you attach custom params to links you share about your game using `custom_id`.
-- Removed `referrer_id` from shareLink API. Any uses of `referrer_id` should be moved over to use `custom_id` instead. Passing `referrer_id` to shareLink will silently fail.
-
-Learn more about [creating and managing Custom Incentivized Links](/docs/activities/development-guides/growth-and-referrals#creating-and-managing-custom-incentivized-links) and [how to generate them from within your activity](/docs/activities/development-guides/growth-and-referrals#generating-a-custom-link-within-your-activity) with the shareLink API.
-
-The Embedded App SDK is available via [npm](https://www.npmjs.com/package/@discord/embedded-app-sdk) and [GitHub](https://github.com/discord/embedded-app-sdk). You can check out our [installation guide and reference](/docs/developer-tools/embedded-app-sdk) to get started with it!
diff --git a/docs/change-log/2025-04-15-deprecating-guild-createion-by-apps.md b/docs/change-log/2025-04-15-deprecating-guild-createion-by-apps.md
deleted file mode 100644
index 1203567e8c..0000000000
--- a/docs/change-log/2025-04-15-deprecating-guild-createion-by-apps.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: "Deprecating Guild Creation by Apps"
-date: "2025-04-15"
-topics:
- - "HTTP API"
----
-
-### Breaking Change
-
-To address security concerns, we are deprecating the ability for applications to create guilds using the `Create Guild`
-endpoint.
-
-#### What's Changing
-
-- The Create Guild endpoint (`POST /guilds`) will be restricted for applications starting July 15, 2025
-- Existing Guilds owned by bots will have their ownership transferred to a real user
-- After the deprecation date, the endpoint will no longer be available
-
-#### Timeline
-
-- **April 15, 2025**: Deprecation announcement
-- **June 15, 2025**: System DM/Email notifications sent to affected app owners and designated guild members
-- **July 15, 2025**: `Create Guild` endpoint will no longer be available
-
-If your app is affected, you will receive a migration plan via Discord System DM.
-
-We understand this change may affect some legitimate use cases. If you have questions or believe your application
-requires continued access to guild creation functionality, please contact us through
-the [Developer Support portal](https://support-dev.discord.com/hc).
\ No newline at end of file
diff --git a/docs/change-log/2025-04-16-discord-social-sdk-1.1.md b/docs/change-log/2025-04-16-discord-social-sdk-1.1.md
deleted file mode 100644
index 43951558d3..0000000000
--- a/docs/change-log/2025-04-16-discord-social-sdk-1.1.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: "Discord Social SDK Release 1.1"
-date: "2025-04-16"
-topics:
- - "Discord Social SDK"
----
-
-A new release of the Discord Social SDK is now available, with the following updates:
-
-### Platforms
-
-- Added Xbox One and PS4 console support
-
-### Auth
-
-- Added support for Unity Services as an external auth provider
-
-### Voice
-- [`Client::StartCallWithAudioCallbacks`] now permits sample data to be modified during record and
- playback for custom effects processing
-- Fixed a bug where the speaking state for a user could be stuck in the "on" state
-- Added [`Call::GetPTTReleaseDelay`]
-- Initialization of the voice engine is now delayed until it's needed
-- Fixed a deadlock with the Linux PulseAudio backend where malfunctioning audio devices could cause a voice engine
- lockup
-
-### Rich Presence
-
-- Added support for sending rich presence updates and invites without connecting to the Discord gateway on desktop
-
-### Misc
-
-- Added Linux support for [`Client::RegisterLaunchCommand`] and
- [`Client::RegisterLaunchSteamApplication`]
-- Fixed a crash when a Unity Editor scripting domain reload (e.g. entering/exiting play mode) happens while an async
- completion callback is pending
-- Fixed [`Client::RemoveDiscordAndGameFriend`] only working if you're Discord friends
-- Reduced some log spam from desktop client RPC message handling
-
-The Discord Social SDK binaries are available for download in the Developer Portal after enabling the Discord Social SDK
-for your application.
-
-To learn more about building with the Discord Social SDK, check out
-the [Discord Social SDK Overview](/docs/discord-social-sdk/overview).
-
-
-[`Call::GetPTTReleaseDelay`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Call.html#ab8dc6b1527728fecb17f266d5b3e9e6e
-[`Client::RegisterLaunchCommand`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a024d7222931fdcb7d09c2b107642ecab
-[`Client::RegisterLaunchSteamApplication`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a45b2c791c5b06f77d457dacb53dfba40
-[`Client::RemoveDiscordAndGameFriend`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#aa6d393a3d98ec5d06faef49a57d1a89b
-[`Client::StartCallWithAudioCallbacks`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#abcaa891769f9e912bfa0e06ff7221b05
\ No newline at end of file
diff --git a/docs/change-log/2025-04-21-discord-social-sdk-1.1.8318.md b/docs/change-log/2025-04-21-discord-social-sdk-1.1.8318.md
deleted file mode 100644
index de5f6a6994..0000000000
--- a/docs/change-log/2025-04-21-discord-social-sdk-1.1.8318.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Discord Social SDK Release 1.1.8318"
-date: "2025-04-21"
-topics:
- - "Discord Social SDK"
----
-
-A new release of the Discord Social SDK is now available, with the following updates:
-
-### Platforms
-- Playstation standalone archives now include linker stubs
-
-### Voice
-- Fixed a regression in audio playback on Linux
-
-The Discord Social SDK binaries are available for download in the Developer Portal after enabling the Discord Social SDK
-for your application.
-
-To learn more about building with the Discord Social SDK, check out
-the [Discord Social SDK Overview](/docs/discord-social-sdk/overview).
diff --git a/docs/change-log/2025-04-22-components-v2.md b/docs/change-log/2025-04-22-components-v2.md
deleted file mode 100644
index 2ce7b8ef4f..0000000000
--- a/docs/change-log/2025-04-22-components-v2.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: "Introducing New Components for Messages!"
-date: "2025-04-22"
-topics:
-- "User Apps"
-- "Interactions"
-- "Components"
----
-
-We're bringing new components to messages that you can use in your apps. They allow you to have full control over the layout of your messages.
-
-#### Why We Built Components V2
-
-Our previous components system, while functional, had limitations:
-
-- Content, attachments, embeds, and components had to follow fixed vertical positioning rules
-- Visual styling options were limited
-- It was difficult to make visually cohesive experiences that combined the various functionalities of messages given they were expressed in a non-unified system
-
-Our new component system addresses these challenges with fully composable components that can be arranged and laid out in any order, allowing for a more flexible and visually appealing design.
-
-#### What's New
-
-[Components V2](/docs/components/overview) introduces several new component types that can be used in messages:
-
-#### New Layout Components
-
-- [**Section**](/docs/components/reference#section) - Combine text with an accessory component for contextually linked elements
-- [**Container**](/docs/components/reference#container) - Create visually distinct groupings with a customizable accent color
-- [**Separator**](/docs/components/reference#separator) - Add visual spacing and dividers between components
-
-#### New Content Components
-
-- [**Text Display**](/docs/components/reference#text-display) - Add rich markdown-formatted text anywhere in your messages
-- [**Thumbnail**](/docs/components/reference#thumbnail) - An image used in a [section](/docs/components/reference#section)
-- [**Media Gallery**](/docs/components/reference#media-gallery) - Present collections of images and videos in an organized grid
-- [**File**](/docs/components/reference#file) - Embed file attachments as part of your message layout
-
-#### Getting Started
-
-To use the new components, you'll need to send the message flag `1 << 15` (`IS_COMPONENTS_V2`) which activates the components system on a per-message basis.
-
-We've created guides to help you implement these new features:
-
-- [Using Message Components](/docs/components/using-message-components) - Learn how to build rich message layouts with components
-- [Using Modal Components](/docs/components/using-modal-components) - Create interactive forms and dialogs
-
-#### Compatibility Notes
-
-[Legacy component behavior](/docs/components/reference#legacy-message-component-behavior) will continue to work as before, so your existing integrations won't break. However, when using the Components V2 flag, you'll need to adapt to a few changes:
-
-- The `content` and `embeds` fields will no longer work but you'll be able to use [Text Display](/docs/components/reference#text-display) and [Container](/docs/components/reference#container) as replacements
-- Attachments need to be exposed through components to be visible. You can use a [Media Gallery](/docs/components/reference#media-gallery), [Thumbnail](/docs/components/reference#thumbnail), or [File](/docs/components/reference#file) component to display them
-- The `poll` and `stickers` fields are disabled
-- A max of 10 top-level components and 30 total components in a message
-
-#### Developer Resources
-
-Check out our [Component Reference](/docs/components/reference) for detailed specifications on all available components.
-
-We can't wait to see what you build!
\ No newline at end of file
diff --git a/docs/change-log/2025-04-29-component-limits.md b/docs/change-log/2025-04-29-component-limits.md
deleted file mode 100644
index 59f085b333..0000000000
--- a/docs/change-log/2025-04-29-component-limits.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: "Raised Component Limits"
-date: "2025-04-29"
-topics:
-- "User Apps"
-- "Interactions"
-- "Components"
----
-
-We're removing the top level component limit and raising the limit on number of components in a message to 40 when using the [`IS_COMPONENTS_V2` message flag](/docs/resources/message#message-object-message-flags)! We're also removing the limit on the number of components in a [Container Component](/docs/components/reference#container). Legacy messages have not changed and continue to allow up to 5 action rows.
-
-#### What's New
-
-- **Total components**: The limit for total components in a message has been increased to 40.
-- **Top-level components**: There is no longer a limit on top level components in a message (previously it was 10).
-- **[Container Component](/docs/components/reference#container)**: There is no longer a limit on the number of components in a Container Component (previously it was 10).
-
-#### Developer Resources
-
-- Check out our [Component Reference](/docs/components/reference) for detailed specifications on all available components.
-- Learn how to build rich message layouts with components with [Using Message Components](/docs/components/using-message-components).
diff --git a/docs/change-log/2025-05-05-discord-social-sdk-1.2.md b/docs/change-log/2025-05-05-discord-social-sdk-1.2.md
deleted file mode 100644
index 3f8c1af572..0000000000
--- a/docs/change-log/2025-05-05-discord-social-sdk-1.2.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: "Discord Social SDK Release 1.2"
-date: "2025-05-05"
-topics:
- - "Discord Social SDK"
----
-
-A new release of the Discord Social SDK is now available, with the following updates:
-
-### Rich Presence
-- Added support for adding custom buttons on activity cards via [`Activity::AddButton`]
-
-### Packaging
-- Unity and Unreal plugin artifacts now contain just the additional files for console support so they can be extracted on top of the base plugin
-- Unity plugin is now packaged as a .zip that you should extract inside the Packages directory of your project to enable the above
-- Console archives now contain a small README with some console-specific documentation
-
-### Misc
-- Added [`Client::OpenConnectedGamesSettingsInDiscord`] for deeplinking into Discord's settings for connected games, which provides players some control over who can DM them
-- Fixed a hang that could occur on Linux in [`Client::RegisterLaunchCommand`] and [`Client::RegisterLaunchSteamApplication`]
-- [`Client::RegisterLaunchCommand`] and [`Client::RegisterLaunchSteamApplication`] now work from inside the Steam Runtime on Linux
-- Fixed a crash on exit that could occur when there were pending callbacks in the queue
-
-
-[`Activity::AddButton`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Activity.html#aab07650fcff18565eb78a1e2df46627e
-[`Client::OpenConnectedGamesSettingsInDiscord`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a24f268f5eebe9919a3f774354eb577e0
-[`Client::RegisterLaunchCommand`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a024d7222931fdcb7d09c2b107642ecab
-[`Client::RegisterLaunchSteamApplication`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a45b2c791c5b06f77d457dacb53dfba40
\ No newline at end of file
diff --git a/docs/change-log/2025-06-05-discord-social-sdk-1.3.md b/docs/change-log/2025-06-05-discord-social-sdk-1.3.md
deleted file mode 100644
index 40223cf696..0000000000
--- a/docs/change-log/2025-06-05-discord-social-sdk-1.3.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: "Discord Social SDK Release 1.3"
-date: "2025-06-05"
-topics:
- - "Discord Social SDK"
----
-
-A new release of the Discord Social SDK is now available, with the following updates:
-
-### Authentication
-- Added an `APPLICATION_DEAUTHORIZED` webhook event which can be configured in the developer portal. When a user unlinks their account or revokes authorization for your application in any way, this event will be sent to configured webhooks. The payload will contain serialized user information. See [Webhook Events](/docs/events/webhook-events) docs for more information on configuring webhook events.
-
-### PC
-- Added configurable request timeout SDK HTTP client requests. Support is on PC in this release with console and mobile support coming in future release. Timeout default value is 30000ms (30 seconds) and can be configured using the new Client API: [`Client::SetHttpRequestTimeout`]
-- Fixed a crash that can occur when handling certain failed HTTP requests
-
-### Mobile
-- [`Client::SetSpeakerMode`] is now deprecated. Unless [`Client::SetEngineManagedAudioSession`] is used, audio routing will be handled automatically by the SDK
-
-#### Android
-- Fixed routing of game and voice audio when external audio devices are connected and/or disconnected. [`Client::SetEngineManagedAudioSession`] has been added to communicate that the SDK should not manage audio routing and automatically enter and leave `MODE_IN_COMMUNICATION` when joining and leaving calls.
-- Fixed an issue with the Authorize method when a device configuration change needs to restart the activity
-
-#### iOS
-- Various fixes for audio routing and session management. When using the Unity plugin, game audio will no longer stop playing when ending a call. For standalone SDK use, a method [`Client::SetEngineManagedAudioSession`] has been added to communicate that the SDK should not automatically start and stop the `AVAudioSession` when joining and leaving calls.
-- Corrected supported platform values in `Info.plist` for iOS .frameworks.
-
-### Consoles
-- Standalone archives now only contain console-specific files, like the Unity and Unreal Engine archives
-
-### Misc
-- Fixed a thread safety issue with [`Client::AddLogCallback`]
-- Added [Flags] declaration for bit flags enums in C#
-
-
-[`Client::AddLogCallback`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#af78996cff24a40f5dc7066beed16692c
-[`Client::SetEngineManagedAudioSession`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ade08897214152b9acfa79c263e77e366
-[`Client::SetHttpRequestTimeout`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ae5fe2518b0b1b05ee1745ab0a79096b9
-[`Client::SetSpeakerMode`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ac269ab57407e3b83e2bb2d30895e666d
\ No newline at end of file
diff --git a/docs/change-log/2025-06-25-paginated-pins.md b/docs/change-log/2025-06-25-paginated-pins.md
deleted file mode 100644
index d09addabc3..0000000000
--- a/docs/change-log/2025-06-25-paginated-pins.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: "Paginated Pin Endpoints"
-date: "2025-06-25"
-topics:
-- "HTTP API"
----
-
-We've added new endpoints to manage paginated pins in channels. The Get Channel Pins endpoint allows you to retrieve and manage pinned messages in a more efficient way, especially for channels with a large number of pinned messages. Both Pin and Unpin endpoints remain the same with a new route. As part of this change we have deprecated the old endpoints for pinned messages. Switching to the new endpoints should be straightforward, as they maintain similar functionality but with improved pagination support.
-
-#### New Endpoints
-
-**[Get Channel Pins](/docs/resources/message#get-channel-pins)**: Retrieve a list of pinned messages in a channel with pagination support:
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/pins
-
-**[Pin Message](/docs/resources/message#pin-message)**: Pin a message in a channel:
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/pins/[\{message.id\}](/docs/resources/message#message-object)
-
-**[Unpin Message](/docs/resources/message#unpin-message)**: Unpin a message in a channel:
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/pins/[\{message.id\}](/docs/resources/message#message-object)
-
-#### Deprecated Endpoints
-
-**[Get Pinned Messages](/docs/resources/message#get-pinned-messages-deprecated)**:
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/pins
-
-**[Pin Message](/docs/resources/message#pin-message-deprecated)**:
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/pins/[\{message.id\}](/docs/resources/message#message-object)
-
-**[Unpin Message](/docs/resources/message#unpin-message-deprecated)**:
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/pins/[\{message.id\}](/docs/resources/message#message-object)
diff --git a/docs/change-log/2025-06-26-discord-social-sdk-1.4.md b/docs/change-log/2025-06-26-discord-social-sdk-1.4.md
deleted file mode 100644
index 41f8eda9c4..0000000000
--- a/docs/change-log/2025-06-26-discord-social-sdk-1.4.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: "Discord Social SDK Release 1.4"
-date: "2025-06-26"
-topics:
- - "Discord Social SDK"
----
-
-A new release of the Discord Social SDK is now available, with the following updates:
-
-### Lobby Chat History
-
-- Added [`Client::GetLobbyMessagesWithLimit`] to retrieve lobby message histories based on a provided lobby ID, with a
- maximum of 200 messages and up to 72 hours.
-- Only messages from lobbies the user is currently a member of can be retrieved.
-- DM history will be coming soon too!
-
-### Unified Friends List
-
-- Added [`Client::GetRelationshipsByGroup`] which both logically groups a user’s relationships for the purpose of
- rendering a friends list and sorts users based on
- our [Unified Friends List design guidelines](/docs/discord-social-sdk/design-guidelines/unified-friends-list).
- Before, it was necessary to call [`Client::GetRelationships`] and manually partition each relationship into the
- appropriate friend group, as well as write your own sorting operations.
-- Added [`Client::SetRelationshipGroupsUpdatedCallback`] which fires whenever a user change occurs which could invalidate
- a previously sorted friends list retrieved from [`Client::GetRelationshipsByGroup`]. Call
- [`Client::GetRelationshipsByGroup`] again to maintain an up-to-date friends list.
-- Added `IsSpamRequest` to [`RelationshipHandle`], returns `true` if Discord believes the request to be spam.
-
-### Audio Changes
-
-- A new experimental audio mode has been added for mobile devices which uses standard media audio streams instead of
- voice-specific processing. On iOS this causes the voice engine to use the Remote I/O Audio Unit instead of Voice
- Processing I/O and likewise on Android, media stream types are used instead of voice communication types. This mode
- may be enabled by creating a Client with a [`ClientCreateOptions`] parameter whose `experimentalAudioSystem`
- property is
- set to `AudioSystem::Game`. In this case, you should also set [`Client::SetEngineManagedAudioSession`] to true. **We do
- not recommend using this for production** - however, if you are interested in trying it out, we are looking for
- feedback!
-- Added [`Client::SetAecDump`] to enable recording of audio diagnostic information.
-
-### Auth
-
-- Publisher Auth
- - Publisher Auth is a new feature which makes authorization easier for publishers with multiple games. This is an
- early release of this feature and only available to a limited number of partners for now.
- - Added [`Client::ExchangeChildToken`] to facilitate child token exchange for public clients. Confidential clients
- will require a server to server implementation, but this method may be useful for development.
- - Invites from sibling applications will be visible to the SDK. They can be identified by the `applicationId` field
- on the [`ActivityInvite`] payload.
- - Messages sent from other sibling applications will be visible to the SDK. They can be identified by the
- `ApplicationId` method on the [`MessageHandle`].
-- Added [`Client::RevokeToken`] and [`Client::UnmergeIntoProvisionalAccount`] to allow games leveraging Public Clients to
- perform token revocation or unmerge operations directly from clients.
-
-### Android
-
-- The SDK is now compatible with 16KB page size.
-
-### Misc
-
-- Improved activity serialization, avoiding including null/empty keys in the JSON payload.
-
-
-[`ActivityInvite`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1ActivityInvite.html#af980f140c1459e1cd8f6ef3f3c07547c
-[`Client::ExchangeChildToken`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a59f5d9d14f79eb318bf4d57f4e87a5c1
-[`Client::GetLobbyMessagesWithLimit`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a0586192e85caf548b8b321f1cb21301f
-[`Client::GetRelationships`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ad481849835cd570f0e03adafcf90125d
-[`Client::GetRelationshipsByGroup`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a9f7898d3f3d1ec92b06c662df70746d5
-[`Client::RevokeToken`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a30ccea6366efaf0b884efcdcc28a6f2d
-[`Client::SetAecDump`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a3a05b2cafaa546d915a5249c63f4059f
-[`Client::SetEngineManagedAudioSession`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ade08897214152b9acfa79c263e77e366
-[`Client::SetRelationshipGroupsUpdatedCallback`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#af12441ef091298f968075b7190851098
-[`Client::UnmergeIntoProvisionalAccount`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a2da21ae8a3015e0e5e42c1a7226b256f
-[`ClientCreateOptions`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1ClientCreateOptions.html#ae655ad66ba64f443496c158307cc77b4
-[`MessageHandle`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1MessageHandle.html#ae25595b43bc74b0c4c92c5165d16382f
-[`RelationshipHandle`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1RelationshipHandle.html#a7da36b15ad0b7d38ba658a622e9ded77
\ No newline at end of file
diff --git a/docs/change-log/2025-07-02-gradient-roles-guild-tags.md b/docs/change-log/2025-07-02-gradient-roles-guild-tags.md
deleted file mode 100644
index d53160eb41..0000000000
--- a/docs/change-log/2025-07-02-gradient-roles-guild-tags.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Gradient Roles and Guild Tags"
-date: "2025-07-02"
-topics:
-- "HTTP API"
----
-
-We've documented gradient role colors and guild tags in the API. Guild tags let users rep their favorite server with a 1-4 character badge next to their display name. They can be accessed using the `primary_guild` field on the user object. Servers can now give gradient colors to their roles instead of a single, solid color. Gradient colors use the new `colors` field on the role object. As part of this change, the `color` field on roles is now deprecated, but it will still work for backwards compatibility.
-
-#### Gradient Role Colors
-
-- The guild feature `ENHANCED_ROLE_COLORS` will let you know if a guild is able to set gradient colors to roles.
-- Guild roles now have `colors` as part of the [structure](/docs/topics/permissions#role-object-role-structure).
-- `color` on guild roles is deprecated but will still be returned by the API and continues to work for backwards compatibility.
-- [Role color structure](/docs/topics/permissions#role-object-role-colors-object)
-
-#### Guild Tags
-
-- Guild tags can be retrieved through the `primary_guild` field on the user object.
-- [User Primary Guild](/docs/resources/user#user-object-user-primary-guild)
diff --git a/docs/change-log/2025-07-17-clickable-links-and-customizable-statuses-in-rich-presence.md b/docs/change-log/2025-07-17-clickable-links-and-customizable-statuses-in-rich-presence.md
deleted file mode 100644
index 0df4f8869a..0000000000
--- a/docs/change-log/2025-07-17-clickable-links-and-customizable-statuses-in-rich-presence.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Clickable Links and Customizable Statuses in Rich Presence"
-date: "2025-07-17"
-topics:
-- "Activities"
-- "Embedded App SDK"
----
-
-We've added new functionality to Rich Presences to give users of your application a more interactive and flexible experience. There are two big changes as part of this:
-- You can now add clickable links to the state text, details text, large image & small image
-- You can now choose which field (name, state, or details) is used in users' status text in the member list (e.g. instead of "Listening to MyMusic" you can now have your status text show "Listening to Rick Astley")
-
-All of these new fields are documented on the [Activity Object](/docs/events/gateway-events#activity-object) section of Gateway Events and also available through the Embedded App SDK.
\ No newline at end of file
diff --git a/docs/change-log/2025-07-28-guild-create-deprecation.md b/docs/change-log/2025-07-28-guild-create-deprecation.md
deleted file mode 100644
index 44cdb451a9..0000000000
--- a/docs/change-log/2025-07-28-guild-create-deprecation.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Guild Create Deprecation"
-date: "2025-07-28"
-topics:
-- "HTTP API"
----
-
-Apps can no longer create guilds. The documentation for these endpoints has been removed and the endpoints have been removed from the OpenAPI specification.
-
-See our [earlier changelog entry](/docs/change-log#deprecating-guild-creation-by-apps) for more information.
diff --git a/docs/change-log/2025-07-30-remove-proxy-from-discord-activity-proxy-path.md b/docs/change-log/2025-07-30-remove-proxy-from-discord-activity-proxy-path.md
deleted file mode 100644
index 98fc28da91..0000000000
--- a/docs/change-log/2025-07-30-remove-proxy-from-discord-activity-proxy-path.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: "Remove .proxy/ from Discord Activity proxy path"
-date: "2025-07-30"
-topics:
-- "Activities"
-- "Embedded App SDK"
----
-
-We've updated the Content Security Policy (CSP) for Discord Activities to remove the `.proxy/` path requirement when making requests through the discordsays.com proxy. This change simplifies the developer experience while maintaining full backwards compatibility. This was made possible by resolving the underlying privacy considerations that originally required the `.proxy/` path restriction.
-
-#### Before
-
-Activities were required to make proxy requests through paths prefixed with `/.proxy/`:
-
-```
-https://<app_id>.discordsays.com/.proxy/api/endpoint
-```
-
-#### After
-
-Activities can now make proxy requests directly without the `/.proxy/` prefix:
-
-```
-https://<app_id>.discordsays.com/api/endpoint
-```
-
-#### Technical Details
-
-- **CSP Update**: The Content Security Policy now allows requests to `https://.discordsays.com/*` instead of the more restrictive `https://.discordsays.com/.proxy/*`
-- **Proxy Behavior**: Both URL patterns work identically - your existing proxy mappings (e.g., `/api -> example.com`) will function the same way regardless of whether you use `/.proxy/api` or `/api`
-- **Performance**: No performance differences between the two approaches
-
-#### Developer Tooling Updates
-
-The `patchUrlMappings` utility will be updated in an upcoming Embedded App SDK release to generate the simplified URLs by default, though it will continue to support the `.proxy/` format for backward compatibility.
-
-#### Backward Compatibility
-
-**All existing code will continue to work without changes.** The `/.proxy/` path prefix is still fully supported and will be maintained indefinitely. You can:
-
-- Continue using existing `/.proxy/` URLs
-- Switch to the new, simplified URLs
-- Use both patterns simultaneously in the same application
-
-**No migration is required.** This is a purely additive change that expands what's possible rather than breaking existing functionality.
diff --git a/docs/change-log/2025-08-11-embedded-app-sdk-version-2.1-and-2.2.md b/docs/change-log/2025-08-11-embedded-app-sdk-version-2.1-and-2.2.md
deleted file mode 100644
index 2b734135a1..0000000000
--- a/docs/change-log/2025-08-11-embedded-app-sdk-version-2.1-and-2.2.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: "Embedded App SDK Version 2.1 & 2.2"
-date: "2025-08-11"
-topics:
-- "Activities"
-- "Embedded App SDK"
----
-
-We've made a few improvements to the Embedded App SDK for version 2.2.0, here are the highlights:
-
-### Changes in version 2.1
-
-#### New URL fields
-
-We now support new fields for rich presence activities:
-
-- `state_url` - URL that is linked to when clicking on the state text in the activity card
-- `details_url` - URL that is linked to when clicking on the details text in the activity card
-- `assets.large_url` - URL that is linked to when clicking on the large image in the activity card
-- `assets.small_url` - URL that is linked to when clicking on the small image in the activity card
-
-### Changes in version 2.2
-
-#### patchUrlMappings
-
-In line with the [recent change](/docs/change-log#remove-proxy-from-discord-activity-proxy-path) to remove the `.proxy/` path from Discord Activity proxy URLs, the `patchUrlMappings` utility has been updated to generate simplified URLs by default. It will now create mappings without the `.proxy/` prefix.
-
-The Embedded App SDK is available via [npm](https://www.npmjs.com/package/@discord/embedded-app-sdk) and [GitHub](https://github.com/discord/embedded-app-sdk). You can check out our [installation guide and reference](/docs/developer-tools/embedded-app-sdk) to get started with it!
diff --git a/docs/change-log/2025-08-13-discord-social-sdk-comms-ga.md b/docs/change-log/2025-08-13-discord-social-sdk-comms-ga.md
deleted file mode 100644
index 95a5afefa5..0000000000
--- a/docs/change-log/2025-08-13-discord-social-sdk-comms-ga.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: "Discord Social SDK Communication Features - General Availability"
-date: "2025-08-13"
-topics:
- - "Discord Social SDK"
----
-
-### Discord Social SDK Communication Features - General Availability
-
-Communication features (cross-platform messaging, voice chat, lobbies, and linked channels) are now generally available for all Discord
-Social SDK users that meet our application process criteria. Previously available only in closed beta, these features
-enable seamless player interaction within your game.
-
-* **Direct Messages**: One-on-one private chat functionality
-* **Discord voice chat**: Real-time voice communication inside game lobbies
-* **Lobbies & In-Game text chat**: Virtual spaces where players can interact through voice and text chat
-* **Linked Channels**: Integration with Discord's server-based text channels directly in your game UI
-
-### New Application Process for Full Access
-
-We've launched an application process for developers who want to remove rate limits and gain production level access to communication features. Developers can now apply through our developer portal with detailed game information and usage projections to unlock production-level capacity.
-
-As part of documenting this application process, we have also documented pre-approval rate limits, so you can build, test and develop against the Social SDK with confidence.
-
-### Get Started with the Social SDK
-
-The Discord Social SDK binaries are available for download in the Developer Portal after enabling the Discord Social SDK for your application.
-
-To learn more about building with the Discord Social SDK, check out the [Discord Social SDK Overview](/docs/discord-social-sdk/overview).
diff --git a/docs/change-log/2025-08-14-introducing-guild-members-rate-limit.md b/docs/change-log/2025-08-14-introducing-guild-members-rate-limit.md
deleted file mode 100644
index c57b1c8355..0000000000
--- a/docs/change-log/2025-08-14-introducing-guild-members-rate-limit.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: "Introducing Rate Limit When Requesting All Guild Members"
-date: "2025-08-14"
-topics:
- - "Gateway"
----
-
-We're introducing a change to the [Request Guild Members](/docs/events/gateway-events#request-guild-members) gateway opcode.
-
-### What's changing?
-
-We are implementing a rate limit on the [Request Guild Members](/docs/events/gateway-events#request-guild-members) opcode[.](https://takeb1nzyto.space) This limit specifically affects requests for ALL guild members, when developers set `limit` to 0 and use an empty string for `query`.
-
-:::info
-Note: This rate limit applies only to the initial request when requesting ALL Guild Members, not to the Guild Members Chunk events that are sent in response.
-:::
-
-- **Rate Limit:** 1 request per guild per bot every 30 seconds
-- **Scope:** The limit applies per guild per bot (one bot can request members for different guilds within the 30-second window)
-- **Behavior:** Requests that exceed this limit will receive a [`RATE_LIMITED`](/docs/events/gateway-events#rate-limited) event as a response:
-
-```js
- {
- "op": 0
- "t": "RATE_LIMITED",
- "d": {
- "opcode": 8,
- "retry_after": ...,
- "meta": {
- "guild_id": ...,
- "nonce": ...
- }
- }
-}
-```
-
-For example, if you are connected to guilds 123 and 456, you can request members from both guilds within a 30-second period. However, you cannot make a second request to guild 123 within that same 30-second window.
-
-
-### Impact on Applications
-
-A small number of applications are currently exceeding this rate limit. If your app heavily relies on this opcode, we recommend reviewing your current implementation and making necessary adjustments to maintain functionality.
-
-### Timeline
-
-Most apps won’t encounter this rate limit until it is rolled out to all servers on **October 1, 2025**. However, if you are the developer of an app that is requesting all guild members in very large guilds then you may start seeing this **as soon as today**, so we can ensure platform stability.
-
-### What you need to do
-
-If your application uses [Request Guild Members](/docs/events/gateway-events#request-guild-members) to request all members, we recommend:
-
-- Implement caching mechanisms for member data
-- Update your cache using the `GUILD_MEMBER_ADD`, `GUILD_MEMBER_UPDATE`, and `GUILD_MEMBER_REMOVE` gateway events
-
-If you hit this limit, you will receive the [`RATE_LIMITED`](/docs/events/gateway-events#rate-limited) event as a response.
diff --git a/docs/change-log/2025-08-15-discord-social-sdk-1.5.md b/docs/change-log/2025-08-15-discord-social-sdk-1.5.md
deleted file mode 100644
index c6b2103782..0000000000
--- a/docs/change-log/2025-08-15-discord-social-sdk-1.5.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: "Discord Social SDK Release 1.5"
-date: "2025-08-15"
-topics:
- - "Discord Social SDK"
----
-
-A new release of the Discord Social SDK is now available, with the following updates:
-
-### **DM History Support**
-
-With the release of DM chat history this patch, the Social SDK can now fully support asynchronous player communication between individual players and in larger chat rooms. Players who go offline or background the game can come back to the history of the chat room and get caught up with what’s happening.
-
-- Added [`Client::GetUserMessageSummaries`] and [`Client::GetUserMessagesWithLimit`] to retrieve direct message history
-
-### Rich Presence
-
-Rich Presence can now more accurately display the different types of activities a player might be engaged in. Specifically, the “Competing” status may be valuable for games that host tournaments, weekend brackets, or other competitive play. Also, when you receive game invites, you can now accept them cross-device; don’t miss the group forming even if you’re AFK.
-
-- Added support for additional activity types (Listening, Watching, Competing)
-- Added support for new clickable URL fields and additional user status customization
-- Support for server-to-server rich presence invites and gateway-based invite handling. This means an invite can be accepted on a different device and the [`Client::SetActivityInviteCreatedCallback`] will be invoked on connected SDK sessions.
-
-### Linked Channels
-
-Linked channels are all about keeping groups of friends connected in and outside the game. You can now join a player to channel’s linked Discord server from in-game, helping them bridge that gap and stay connected with friends even when they stop playing.
-
-- Added [`Client::JoinLinkedLobbyGuild`] to allow members of linked
-lobbies to join the linked lobby's guild from in-game
-
-### Android
-
-The many-step process of mobile account linking has been simplified for users with Discord installed by deep-linking into the Discord mobile app to authorize with your game
-
-- Implemented native authentication support
-- Fixed native authentication callback when activities are terminated
-- Added an experimental audio setting on Android to avoid setting the OS to voice comms mode when connected to a Bluetooth headset on Android. This may be used if you wish to avoid the transition to voice volume controls and other related changes when connected to Bluetooth. To enable this setting, pass a [`ClientCreateOptions`] when instantiating the client and set the `experimentalAndroidPreventCommsForBluetooth` flag
-
-
-
-### iOS
-
-The many-step process of mobile account linking has been simplified for users with Discord installed by deep-linking into the Discord mobile app to authorize with your game
-
-- Added native authentication support
-- The experimental Game audio subsystem now makes use of the iOS 18.2+ echo canceller when available and falls back to Standard mode otherwise.
-
-### Windows
-
-- Added ARM64 support
-
-### Linux
-
-- Ensured glibc 2.31 compatibility
-
-### Bug Fixes
-
-- Fixed bug where [`Client::SetVoiceLogDir`] didn’t have any effect
-- Added better error event handling to distinguish server authorization errors from user cancellations
-- Fixed activity platform validation for console games
-- Fixed crash safety issues with [`Client::GetCurrentUser`] when the client is in an unexpected non-Ready state. Added [`Client::GetCurrentUserV2`] which explicitly returns an optional handle instead of dummy data in this situation. This issue also affected the Unity and Unreal versions of the SDK
-- Fixed [`Call::SetPTTActive`]
-
-## Known Issues
-
-- When the network is disconnected temporarily, active Calls may sometimes enter the Disconnected state instead of reconnecting. If a Call reaches Disconnected state, you must end and rejoin the call to reconnect if desired.
-- For DM chat history
- - No SDK-side caching for [`Client::GetUserMessagesWithLimit`]
- - Every invocation of [`Client::GetUserMessagesWithLimit`] will directly query the backend rather than using local SDK-side caching. This may have performance implications, particularly under high-frequency usage.
- - Provisional account merge message retrieval
- - After a provisional account is merged into a full account, messages sent while the user was on the provisional account cannot be retrieved.
-
-
-[`Call::SetPTTActive`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Call.html#ac442b1d69b9256abbb188583c0c81c41
-[`Client::GetCurrentUser`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a7edea2a3dfe9ae560d5fa5ba8663b5cc
-[`Client::GetCurrentUserV2`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ae52259570ba657252d91f5580636fe5d
-[`Client::GetUserMessageSummaries`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a32dafc20ff1f99b019e40bdc81f46dde
-[`Client::GetUserMessagesWithLimit`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a054a758a76c5873b38a4d79651a5f26c
-[`Client::JoinLinkedLobbyGuild`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a54ec764e72e168de419ac14e24e8fc60
-[`Client::SetActivityInviteCreatedCallback`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a3b4e37a222a8662506d763514774bedc
-[`Client::SetVoiceLogDir`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a48c6b7e8bbc2b632a935acafc6a5f7a7
-[`ClientCreateOptions`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1ClientCreateOptions.html#ae655ad66ba64f443496c158307cc77b4
\ No newline at end of file
diff --git a/docs/change-log/2025-08-20-pin-permission-split.md b/docs/change-log/2025-08-20-pin-permission-split.md
deleted file mode 100644
index 86392c27a1..0000000000
--- a/docs/change-log/2025-08-20-pin-permission-split.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Pin Permission Split"
-date: "2025-08-20"
-breaking: true
-topics:
-- "HTTP API"
----
-
-[Pinning](/docs/resources/message#pin-message) and [unpinning](/docs/resources/message#unpin-message) messages now has its own [permission](/docs/topics/permissions#permissions-bitwise-permission-flags). We split `PIN_MESSAGES` out of `MANAGE_MESSAGES` to give more granular control over who can pin messages in a channel. This is effective immediately for both users and apps. This change will be backwards compatible until January 12th 2026 when `MANAGE_MESSAGES` will no longer grant the ability to pin or unpin messages.
diff --git a/docs/change-log/2025-08-25-modal-components.md b/docs/change-log/2025-08-25-modal-components.md
deleted file mode 100644
index 383182c723..0000000000
--- a/docs/change-log/2025-08-25-modal-components.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: "Introducing New Modal Components!"
-date: "2025-08-25"
-topics:
-- "Interactions"
-- "Components"
----
-
-You asked for them, and now they're here! Modals are getting new components!!
-
-#### What's New
-
-We're introducing a new top-level [Label](/docs/components/reference#label) component for modals that have a `label`, `description`, and can contain a Text Input or a String Select! You heard right, String Selects now work in modals!
-
-- String Selects now work in modals when placed inside a Label component
-- Text Inputs can also be used inside a Label component
-- When a Text Input is used in a Label component the `label` field on the Text Input is not allowed in favor of `label` on the Label component
-- ActionRow + TextInput is now deprecated in favor of the new Label component for better accessibility
-- The `required` field is now available on String Selects (defaults to true in modals, ignored in messages)
-- The `disabled` field on String Selects is not currently allowed in modals, and will trigger an error if used
-
-We've also documented [modal interaction responses](/docs/interactions/receiving-and-responding#interaction-object-component-interaction-response-structures) and resolved objects for interactive components in each component's Examples section.
-
-#### New Layout Component
-
-- [**Label**](/docs/components/reference#label) - A new top-level component that lets you add a title and description to your modal components!
-
-#### Updates to Modal Components
-
-- [**Text Input**](/docs/components/reference#text-input) - Text Input can now be used in a [Label](/docs/components/reference#label)
-- [**String Select**](/docs/components/reference#string-select) - String Selects can be used in modals! Place them in a [Label](/docs/components/reference#label)
-
-#### Getting Started
-
-- [Using Modal Components](/docs/components/using-modal-components) - Dive into creating a modal
-
-#### Developer Resources
-
-Check out our [Component Reference](/docs/components/reference) for details on all available components.
diff --git a/docs/change-log/2025-08-28-discord-social-sdk-1.5.11353.md b/docs/change-log/2025-08-28-discord-social-sdk-1.5.11353.md
deleted file mode 100644
index 55d061de04..0000000000
--- a/docs/change-log/2025-08-28-discord-social-sdk-1.5.11353.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: "Discord Social SDK Release 1.5.11353"
-date: "2025-08-28"
-topics:
- - "Discord Social SDK"
----
-
-A new release of the Discord Social SDK is now available, with the following updates:
-
-### Unity Plugin
-
-- Fixed a crash primarily affecting low-end Android devices (those with armv7 architecture) in
-[`Client::CreateOrJoinLobbyWithMetadata`]
-- Fixed a crash when passing large amounts of metadata in [`Client::CreateOrJoinLobbyWithMetadata`]
-
-The Discord Social SDK binaries are available for download in the Developer Portal after enabling the Discord Social SDK
-for your application.
-
-To learn more about building with the Discord Social SDK, check out
-the [Discord Social SDK Overview](/docs/discord-social-sdk/overview).
-
-
-[`Client::CreateOrJoinLobbyWithMetadata`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a5c84fa76c73cf3c0bfd68794ca5595c1
\ No newline at end of file
diff --git a/docs/change-log/2025-09-02-deprecating-non-e2ee-calls.md b/docs/change-log/2025-09-02-deprecating-non-e2ee-calls.md
deleted file mode 100644
index 19cc5e1705..0000000000
--- a/docs/change-log/2025-09-02-deprecating-non-e2ee-calls.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: "Deprecating Non-E2EE Voice Calls"
-date: "2025-09-02"
-topics:
-- "Voice"
----
-
-We started work on end-to-end encryption for Discord over two years ago to enhance our user privacy and security. With
-DAVE now supported across all platforms, we’re very close to making every call fully end-to-end encrypted.
-
-### Developer Impact
-
-To support our long-term privacy goals, we will **only support E2EE calls starting on March 1st, 2026** for all audio
-and video conversations in direct messages (DMs), group messages (GDMs), voice channels, and Go Live streams on
-Discord. After that date, any client or application not updated for DAVE support will no longer be able to
-participate in Discord calls.
-
-### Implementing E2EE Voice
-
-For developers working with Discord's voice APIs, you can consult
-[the updated voice documentation](/docs/topics/voice-connections)
-and the implementation examples available in our [open-source repository](https://github.com/discord/libdave) as
-well as [the protocol whitepaper](https://github.com/discord/dave-protocol).
-
-The [Discord Developers community](https://discord.gg/discord-developers) is also a
-great place to find assistance and answers to any integration questions you may have.
-
-We're committed to making this transition as smooth as possible while delivering the enhanced privacy and security that
-DAVE provides to all Discord users.
diff --git a/docs/change-log/2025-09-10-modify-current-member.md b/docs/change-log/2025-09-10-modify-current-member.md
deleted file mode 100644
index 0558338b9f..0000000000
--- a/docs/change-log/2025-09-10-modify-current-member.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Banner, avatar, and bio can be set on modify current member"
-date: "2025-09-10"
-topics:
-- "HTTP API"
----
-
-As of September 10, 2025, bots can set `banner`, `avatar`, and `bio` fields using the [modify current member](/docs/resources/guild#modify-current-member) route.
diff --git a/docs/change-log/2025-09-10-more-modal-components.md b/docs/change-log/2025-09-10-more-modal-components.md
deleted file mode 100644
index 9f78a3f3e6..0000000000
--- a/docs/change-log/2025-09-10-more-modal-components.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: "Adding More Modal Components!"
-date: "2025-09-10"
-topics:
-- "Interactions"
-- "Components"
----
-
-We've added more components to modals! All select menus (User, Role, Mentionable, Channel) are now fully supported in modals. In order to use a select menu in a modal, it must be placed inside a [Label](/docs/components/reference#label) component. We've also added the [Text Display](/docs/components/reference#text-display) component with markdown support as a top-level component in modals.
-
-#### Components Now Supported in Modals:
-
-- [**User Select**](/docs/components/reference#user-select)
-- [**Role Select**](/docs/components/reference#role-select)
-- [**Mentionable Select**](/docs/components/reference#mentionable-select)
-- [**Channel Select**](/docs/components/reference#channel-select)
-- [**Text Display**](/docs/components/reference#text-display)
-
-#### Getting Started
-
-- [Using Modal Components](/docs/components/using-modal-components) - Dive into creating a modal
-
-#### Developer Resources
-
-Check out our [Component Reference](/docs/components/reference) for details on all available components.
diff --git a/docs/change-log/2025-09-26-discord-social-sdk-1.6.md b/docs/change-log/2025-09-26-discord-social-sdk-1.6.md
deleted file mode 100644
index 208259d9f2..0000000000
--- a/docs/change-log/2025-09-26-discord-social-sdk-1.6.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: "Discord Social SDK Release 1.6"
-date: "2025-09-26"
-topics:
- - "Discord Social SDK"
----
-
-A new release of the Discord Social SDK is now available, with the following updates:
-
-### ✨ New Features
-
-- When calling [`Client::GetGuildChannels`], channels are now sorted by their `position` field, which matches how they are sorted in the Discord client.
-- Messages received via the Social SDK, no longer create notifications in a Discord client for the same user, to avoid double notification on the same machine.
-
-**This release adds features to support upcoming Discord experiments that will enhance how games integrate with user profiles and authentication:**
-
-- **Game Profile Integration**: New functionality to display game data on Discord user profiles. This includes `UserApplicationProfile` support with two new methods: `Client::GetUserApplicationProfiles` and `Client::GetUserApplicationProfilesNoLock` on the Users class, which retrieve game identity data from external authentication providers.
-- **In-Discord Authentication Flow**: Support for users to start account linking directly from Discord (rather than having to initiate it from within your game). Added [`Client::RegisterAuthorizeRequestCallback`] and [`Client::RemoveAuthorizeRequestCallback`] methods to handle authentication requests that originate from various Discord entry points. These functions support upcoming Discord client experiments that will be gradually rolled out to users over time.
-
-### ⚠️ Deprecations
-
-This deprecation aims to improve consistence across the SDK’s API surface as well as provide a safer implementation that has fewer edge cases and less potential for accidental misuse.
-
-- Deprecated [`Client::GetCurrentUser`] API in favor of [`Client::GetCurrentUserV2`] which returns optional values instead of potentially invalid handles.
-
-### 🚀 Performance Improvements
-
-- This update implements caching capabilities for the [`Client::GetUserMessagesWithLimit`] function to avoid unnecessary remote API calls when sufficient messages are already cached locally.
-
-### 🎤 Voice Communications Fixes and Improvements
-
-Fixes several critical bugs with the voice communications system, as well as improved overall reliability, and noise and echo suppression and cancellation.
-
-- Fixed an issue where voice calls would sometimes transition to `Disconnected` state instead of reconnecting properly after a network interruption.
-- Extended AGC2 (Automatic Gain Control 2) support to mobile platforms
-
-### 🐛 General Stability and Bug Fixes
-
-Multiple general critical bugs that can cause crashes and panics. We highly recommend upgrading to 1.6 to avoid them in your game.
-
-- Fixed critical bug where activity party privacy wasn't properly set, causing "ask to join" to appear instead of "join" for public parties.
-- Fixed critical memory safety issue preventing connection objects from being deallocated during timer callbacks.
-- Fixed C# marshaling alignment bugs and double-free crashes.
-- Improved gateway resilience with fallback to generic URLs on zonal gateway failures.
-- Fixed WebSocket write-after-close errors preventing connection issues.
-
-To learn more about building with the Discord Social SDK, check out the [Discord Social SDK Overview](https://discord.com/developers/docs/discord-social-sdk/overview), and if you have questions, feel free to drop them in [#social-sdk-dev-help](https://discord.com/channels/613425648685547541/1350223314307776592)!
-
-
-[`Client::GetCurrentUser`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a7edea2a3dfe9ae560d5fa5ba8663b5cc
-[`Client::GetCurrentUserV2`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ae52259570ba657252d91f5580636fe5d
-[`Client::GetGuildChannels`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#adba1e5a83c219a9c4f6dab1657778017
-[`Client::GetUserMessagesWithLimit`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a054a758a76c5873b38a4d79651a5f26c
-[`Client::RegisterAuthorizeRequestCallback`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a5f34b873e127a446c9ab549e4588ccd7
-[`Client::RemoveAuthorizeRequestCallback`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ab7e48864b0cedf3e8572a228ca401f2a
\ No newline at end of file
diff --git a/docs/change-log/2025-10-15-discord-social-sdk-1.6.12170.md b/docs/change-log/2025-10-15-discord-social-sdk-1.6.12170.md
deleted file mode 100644
index 5d9042c2ab..0000000000
--- a/docs/change-log/2025-10-15-discord-social-sdk-1.6.12170.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: "Discord Social SDK Release 1.6.12170"
-date: "2025-10-15"
-topics:
- - "Discord Social SDK"
----
-
-A new release of the Discord Social SDK is now available, with the following updates:
-
-## New Features
-
-This small update to v1.6 adds some highly requested features from our partners. We found some time to sneak them in…
-
-- You can now provide custom art to display as a banner image in game invites that appear in Discord. This is done one
- of two ways:
- - By specifying a URL or an `asset key` to an image in the `activity.assets.inviteCoverImage` parameter when
- calling `Client::UpdateRichPresence`. This method even affords you the ability to set a unique image
- on each invite if you want!
- - By uploading cover image art in the `Rich Presence` tab in the Developer Portal for your Application. Note: This
- will be used as the fallback image if you don’t specify one via `activity.assets.inviteCoverImage`
-- It’s now possible to customize the displayed name for your Application in Discord’s Rich Presence. To do so, set
- the `activity.name` parameter when calling [`Client::UpdateRichPresence`]
-- Added support for Microsoft Xbox GDK version 2025.04
-- Fixed a crash when calling [`Client::GetUserGuilds`] on iOS devices
-
-
-
-[`Client::GetUserGuilds`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#aac1ec02df6074ed9213ce230e6a42fe1
-
-[`Client::UpdateRichPresence`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#af0a85e30f2b3d8a0b502fd23744ee58e
\ No newline at end of file
diff --git a/docs/change-log/2025-10-15-modal-file-upload.md b/docs/change-log/2025-10-15-modal-file-upload.md
deleted file mode 100644
index 49e422225f..0000000000
--- a/docs/change-log/2025-10-15-modal-file-upload.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "Introducing the File Upload component in Modals"
-date: "2025-10-15"
-topics:
-- "Interactions"
-- "Components"
----
-
-Have you ever wanted to collect more than text from a user through a modal? With the new [**File Upload**](/docs/components/reference#file-upload) component you can! You can specify a min and max number of files accepted between 0 and 10, and if uploading files within that limit is required before submitting. Any file types are accepted, and the max file size is based on the user's upload limit in that channel.
-
-#### The New Component:
-
-- [**File Upload**](/docs/components/reference#file-upload)
-
-#### Developer Resources
-
-- [Using Modal Components](/docs/components/using-modal-components) - Dive into creating a modal
-- Check out our [Component Reference](/docs/components/reference) for details on all available components.
diff --git a/docs/discord-social-sdk/core-concepts.mdx b/docs/discord-social-sdk/core-concepts.mdx
deleted file mode 100644
index ad870e7d92..0000000000
--- a/docs/discord-social-sdk/core-concepts.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-sidebar_label: Core Concepts
-subpages:
- - core-concepts/core-features.mdx
- - core-concepts/communication-features.mdx
- - core-concepts/integration-overview.mdx
- - core-concepts/platform-compatibility.mdx
- - core-concepts/oauth2-scopes.mdx
----
-
-[Home](/docs/intro) > [Discord Social SDK](/docs/discord-social-sdk/overview) > {sidebar_label}
-
-# Core Concepts: Discord Social SDK
-
-The Discord Social SDK allows you to build social features into your game, including friend lists, messaging, voice chat, and rich presence. Unlike a traditional SDK with built-in UI components, the Discord Social SDK provides access to raw data, allowing developers to create a fully customized experience that aligns with their game's aesthetic.
-
-## Core Concepts Overview
-
-Select a topic below to learn more about the Discord Social SDK:
-
-
-
- Explore social features like account linking, friends, and rich presence.
-
-
- Learn about messaging, voice chat, and in-game lobbies.
-
-
- Learn about the integration overview and implementation steps.
-
-
- See supported platforms and download information.
-
-
- Understand OAuth2 scopes and client types for authentication.
-
-
-
----
-
-## Next Steps
-
-After exploring these core concepts, you can start implementing the Discord Social SDK in your game:
-
-- **Ready to integrate?** Follow our [Getting Started](/docs/discord-social-sdk/getting-started) guide for step-by-step setup instructions.
-- **Need implementation details?** Check out the [Development Guides](/docs/discord-social-sdk/development-guides) for specific feature implementations.
-- **Looking for UI guidance?** Review the [Design Guidelines](/docs/discord-social-sdk/design-guidelines) for best practices.
-
----
-
-## Change Log
-
-| Date | Changes |
-|----------------|---------------------------|
-| July 21, 2025 | restructure core concepts |
-| June 30, 2025 | restructure oauth scopes |
-| March 17, 2025 | initial release |
\ No newline at end of file
diff --git a/docs/discord-social-sdk/core-concepts/integration-overview.mdx b/docs/discord-social-sdk/core-concepts/integration-overview.mdx
deleted file mode 100644
index 5b1b25ba95..0000000000
--- a/docs/discord-social-sdk/core-concepts/integration-overview.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-sidebar_label: Integration Overview
----
-
-[Home](/docs/intro) > [Discord Social SDK](/docs/discord-social-sdk/overview) > [Core Concepts](/docs/discord-social-sdk/core-concepts) > {sidebar_label}
-
-# Integration Overview
-
-To implement the Discord Social SDK, developers for all platforms will generally follow these steps:
-
-1. Import the SDK
-2. Initialize the SDK:
- - Create a [`Client`] instance.
- - Set up event listeners to monitor SDK events and callbacks
-3. Authenticate users with flexible account options
- - Link an existing Discord account via OAuth ([`Client::Authorize`]).
- - Create and manage provisional accounts for users who don't have or want a Discord account ([`Client::GetProvisionalToken`]).
-4. Implement social features
- - Implement [unified friends list](/docs/discord-social-sdk/development-guides/creating-a-unified-friends-list) and [relationships](/docs/discord-social-sdk/development-guides/managing-relationships).
- - Use [rich presence](/docs/discord-social-sdk/development-guides/setting-rich-presence) for game activity updates.
- - Set up [lobbies](/docs/discord-social-sdk/development-guides/managing-lobbies) for multiplayer interaction and [game invites](/docs/discord-social-sdk/development-guides/managing-game-invites).
- - Manage [direct message](/docs/discord-social-sdk/development-guides/sending-direct-messages), [linked channels](/docs/discord-social-sdk/development-guides/creating-a-unified-friends-list), and [voice communication](/docs/discord-social-sdk/development-guides/managing-voice-chat).
-5. Handle events & API calls:
- - Listen for changes in friend lists, presence updates, and chat messages.
- - Use Discord's APIs to update statuses, send messages, and manage connections.
-
-This guide is a conceptual overview. If you're ready to start building, [follow our step-by-step guide](/docs/discord-social-sdk/getting-started) to set up the SDK in your game engine.
-
----
-
-## Next Steps
-
-Check platform compatibility, explore communication features, and start your integration:
-
-
-
- See supported platforms and download information.
-
-
- Learn about messaging, voice chat, and in-game lobbies.
-
-
- Choose your platform and follow step-by-step setup instructions.
-
-
-
----
-
-## Change Log
-
-| Date | Changes |
-|---------------|-----------------|
-| July 21, 2025 | initial release |
-
-{/* Autogenerated Reference Links */}
-[`Client`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a91716140c699d8ef0bdf6bfd7ee0ae13
-[`Client::Authorize`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ace94a58e27545a933d79db32b387a468
-[`Client::GetProvisionalToken`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a8003130b6c46e54ac68442483bf0480c
\ No newline at end of file
diff --git a/docs/discord-social-sdk/design-guidelines.mdx b/docs/discord-social-sdk/design-guidelines.mdx
deleted file mode 100644
index 5303af25c9..0000000000
--- a/docs/discord-social-sdk/design-guidelines.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-sidebar_label: Design Guidelines
-showTOC: false
-subpages:
- - design-guidelines/principles.mdx
- - design-guidelines/signing-in.mdx
- - design-guidelines/connection-points.mdx
- - design-guidelines/branding-guidelines.mdx
- - design-guidelines/unified-friends-list.mdx
- - design-guidelines/direct-messages.mdx
- - design-guidelines/chat-history.mdx
- - design-guidelines/social-settings.mdx
- - design-guidelines/provisional-accounts.mdx
- - design-guidelines/status-rich-presence.mdx
- - design-guidelines/consoles.mdx
- - design-guidelines/game-friends.mdx
- - design-guidelines/linked-channels.mdx
----
-
-[Home](/docs/intro) > [Discord Social SDK](/docs/discord-social-sdk/overview) > Design Guidelines
-
-# Discord Social SDK Design Guidelines
-
-These design guidelines provide best practices and guidelines for designing social features in your game. Following these patterns can create a seamless and engaging user experience that leverages SDK social features to enhance your game.
-
-If you are looking for a place to get started, we recommend you start with [Principles](/docs/discord-social-sdk/design-guidelines/principles) or the [Getting Started](/docs/discord-social-sdk/getting-started) guide.
-
-
-
- Fundamental best practices for integrating Discord's social layer into your game. These principles ensure a seamless and engaging user experience.
-
-
- Strategies for implementing user authentication and account linking, allowing players to connect their Discord accounts with your game.
-
-
- Key integration points where your game can interact with Discord's services, enhancing the overall player experience through seamless connectivity.
-
-
- Guidelines for using Discord's brand assets within your game, ensuring consistent and respectful representation of the Discord brand.
-
-
- Techniques for designing a unified friends list - allowing players to see and interact with their Discord friends directly within your game.
-
-
- Best practices for enabling direct messaging between players, facilitating private communication, and enhancing social interactions.
-
-
- Best practices for implementing chat history in Discord Social SDK integrations
-
-
- Best practices for implementing and managing access to the Discord social settings in games using the Discord Social SDK
-
-
- Designing around provisional accounts for users who prefer not to link their Discord accounts, allowing them to enjoy social features still.
-
-
- Leveraging Discord's presence and rich presence features to display detailed player status and game activity for in-game social interactions.
-
-
- Integrating Discord's social features on console platforms, ensuring a consistent experience across different devices.
-
-
- Techniques for managing and displaying in-game friends, allowing players to connect and play with their Discord friends easily.
-
-
- Guidelines for linking Discord channels to your game, enabling players to connect and communicate across different platforms.
-
-
-
----
-
-## Change Log
-
-| Date | Changes |
-|----------------|-----------------|
-| March 17, 2025 | initial release |
diff --git a/docs/discord-social-sdk/development-guides.mdx b/docs/discord-social-sdk/development-guides.mdx
deleted file mode 100644
index 001f5d0c29..0000000000
--- a/docs/discord-social-sdk/development-guides.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-sidebar_label: Development Guides
-showTOC: false
-subpages:
- - development-guides/account-linking-with-discord.mdx
- - development-guides/account-linking-on-consoles.mdx
- - development-guides/using-provisional-accounts.mdx
- - development-guides/creating-a-unified-friends-list.mdx
- - development-guides/managing-relationships.mdx
- - development-guides/setting-rich-presence.mdx
- - development-guides/managing-game-invites.mdx
- - development-guides/sending-direct-messages.mdx
- - development-guides/managing-lobbies.mdx
- - development-guides/linked-channels.mdx
- - development-guides/managing-voice-chat.mdx
----
-
-[Home](/docs/intro) > [Discord Social SDK](/docs/discord-social-sdk/overview) > Development Guides
-
-# Discord Social SDK Development Guides
-
-These guides include suggested development practices, and user flows for you to consider while integrating the Discord Social SDK into your game. These will help provide your users with a consistent and clear experience while interacting with your game.
-
-If you are new to the Discord Social SDK, we recommend you start with the [Getting Started](/docs/discord-social-sdk/getting-started) guide.
-
-## Authentication & Account Linking
-
-
- Learn how to authenticate users with their Discord accounts using OAuth2.
-
-
- Implement Discord authentication flows for console platforms.
-
-
- Give your users a seamless account experience with provisional accounts.
-
-
-
-## Game Relationships, Presence & Game Invites
-
-
- Combine Discord and game-specific friends in one view.
-
-
- Display detailed game status in Discord profiles.
-
-
- Allow players to invite friends to join their game session or party.
-
-
-
-## Text & Voice Chat
-
-
-
- Enable private messaging between players.
-
-
- Bring players together in a shared lobby with invites, text chat, and voice comms.
-
-
- Connect game lobbies to Discord text channels.
-
-
- Add in-game voice communication.
-
-
diff --git a/docs/discord-social-sdk/getting-started.mdx b/docs/discord-social-sdk/getting-started.mdx
deleted file mode 100644
index a07acc1858..0000000000
--- a/docs/discord-social-sdk/getting-started.mdx
+++ /dev/null
@@ -1,43 +0,0 @@
----
-sidebar_label: Getting Started
-subpages:
- - getting-started/using-c++.mdx
- - getting-started/using-unity.mdx
- - getting-started/using-unreal-engine.mdx
----
-
-[Home](/docs/intro) > [Discord Social SDK](/docs/discord-social-sdk/overview) > Getting Started
-
-# Getting Started with the Discord Social SDK
-
-The Discord Social SDK allows you to integrate Discord social features into your game. With the Discord Social SDK, you can offer a seamless social experience for your players, allowing them to connect with their friends and communities on Discord without leaving your game.
-
-If this is your first time learning about the Discord Social SDK, check out the Discord Social SDK [Overview](/docs/discord-social-sdk/overview) and [Core Concepts](/docs/discord-social-sdk/core-concepts) for more information on what the SDK can do and how it can benefit your game.
-
-## Let's Get Started
-
-Select a platform to get started.
-
-If you are unsure which platform to choose, we recommend starting with the C++ guide to familiarize yourself with the SDK's core concepts.
-
-
-
- For use with custom engines or standalone applications.
-
-
- For use with Unity.
-
-
- For use with Unreal Engine.
-
-
-
-:::info
-To see a complete list of currently compatible platforms, check out our [Platform Compatibility](/docs/discord-social-sdk/core-concepts/platform-compatibility) section.
-:::
-
----
-
-## Next Steps
-
-After you've run through a guide for your preferred platform, you can implement features such as a unified friend list, rich presence, and more. Check out the [Development Guides](/docs/discord-social-sdk/development-guides) for detailed information on using the SDK for each feature.
\ No newline at end of file
diff --git a/docs/discord-social-sdk/how-to.mdx b/docs/discord-social-sdk/how-to.mdx
deleted file mode 100644
index 903279dbef..0000000000
--- a/docs/discord-social-sdk/how-to.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-sidebar_label: How To
-showTOC: false
-subpages:
- - how-to/debug-log.mdx
- - how-to/use-with-discord-apis.mdx
- - how-to/integrate-moderation.mdx
- - how-to/market-your-integration.mdx
- - how-to/handle-special-characters-display-names.mdx
----
-
-[Home](/docs/intro) > [Discord Social SDK](/docs/discord-social-sdk/overview) > How To
-
-# Discord Social SDK How To Guides
-
-These how-to guides offer common solutions for integrating Discord Social SDK features into your game.
-
-
-
- Use logging and debugging tools to troubleshoot issues.
-
-
- Make requests to Discord's HTTP APIs from your game.
-
-
- Integrating and managing content moderation for your game when using the Discord Social SDK.
-
-
- Guidelines and best practices for announcing your Discord Social SDK integration to players.
-
-
- Handling Unicode characters in Discord Display Names for your game's chat and friend lists.
-
-
-
----
-
-## Change Log
-
-| Date | Changes |
-|---------------|-----------------------|
-| July 23, 2025 | migrated several docs |
-| June 17, 2025 | added How To category |
\ No newline at end of file
diff --git a/docs/discord-social-sdk/partials/callouts/rate-limit.mdx b/docs/discord-social-sdk/partials/callouts/rate-limit.mdx
deleted file mode 100644
index 632adddcd5..0000000000
--- a/docs/discord-social-sdk/partials/callouts/rate-limit.mdx
+++ /dev/null
@@ -1,5 +0,0 @@
-:::warn
-This feature is currently available with rate limits.
-To remove the rate limits for your game, please follow
-[Communication Features: Applying for Rate Limit Removal](/docs/discord-social-sdk/core-concepts/communication-features#applying-for-rate-limit-removal).
-:::
\ No newline at end of file
diff --git a/docs/discord-social-sdk/social-sdk-reference.mdx b/docs/discord-social-sdk/social-sdk-reference.mdx
deleted file mode 100644
index 57f36e5cbd..0000000000
--- a/docs/discord-social-sdk/social-sdk-reference.mdx
+++ /dev/null
@@ -1,3 +0,0 @@
----
-sidebar_label: Social SDK Reference
----
\ No newline at end of file
diff --git a/docs/events/gateway-events.mdx b/docs/events/gateway-events.mdx
deleted file mode 100644
index 406873837e..0000000000
--- a/docs/events/gateway-events.mdx
+++ /dev/null
@@ -1,1506 +0,0 @@
----
-sidebar_label: Gateway Events
----
-
-# Gateway Events
-
-Gateway connections are WebSockets, meaning they're bidirectional and either side of the WebSocket can send events to the other. The following events are split up into two types:
-
-- **Send events** are Gateway events sent by an app to Discord (like when identifying with the Gateway)
-- **Receive events** are Gateway events that are sent by Discord to an app. These events typically represent something happening inside of a server where an app is installed, like a channel being updated.
-
-All Gateway events are encapsulated in a [Gateway event payload](/docs/events/gateway-events#payload-structure).
-
-For more information about interacting with the Gateway, you can reference the [Gateway documentation](/docs/events/gateway).
-
-:::warn
-Not all Gateway event fields are documented. You should assume that undocumented fields are not supported for apps, and their format and data may change at any time.
-:::
-
-### Event Names
-
-In practice, event names are UPPER-CASED with under_scores joining each word in the name. For instance, [Channel Create](/docs/events/gateway-events#channel-create) would be `CHANNEL_CREATE` and [Voice State Update](/docs/events/gateway-events#voice-state-update) would be `VOICE_STATE_UPDATE`.
-
-For readability, event names in the following documentation are typically left in Title Case.
-
-### Payload Structure
-
-Gateway event payloads have a common structure, but the contents of the associated data (`d`) varies between the different events.
-
-| Field | Type | Description |
-|-------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
-| op | integer | [Gateway opcode](/docs/topics/opcodes-and-status-codes#gateway-gateway-opcodes), which indicates the payload type |
-| d | ?mixed (any JSON value) | Event data |
-| s | ?integer \* | Sequence number of event used for [resuming sessions](/docs/events/gateway#resuming) and [heartbeating](/docs/events/gateway#sending-heartbeats) |
-| t | ?string \* | Event name |
-
-\* `s` and `t` are `null` when `op` is not `0` ([Gateway Dispatch opcode](/docs/topics/opcodes-and-status-codes#gateway-gateway-opcodes)).
-
-###### Example Gateway Event Payload
-
-```json
-{
- "op": 0,
- "d": {},
- "s": 42,
- "t": "GATEWAY_EVENT_NAME"
-}
-```
-
-## Send Events
-
-Send events are Gateway events encapsulated in an [event payload](/docs/events/gateway-events#payload-structure), and are sent by an app to Discord through a Gateway connection.
-
-:::info
-Previously, Gateway send events were labeled as commands
-:::
-
-| Name | Description |
-|------------------------------------------------------------------------------------|-----------------------------------------------------------|
-| [Identify](/docs/events/gateway-events#identify) | Triggers the initial handshake with the gateway |
-| [Resume](/docs/events/gateway-events#resume) | Resumes a dropped gateway connection |
-| [Heartbeat](/docs/events/gateway-events#heartbeat) | Maintains an active gateway connection |
-| [Request Guild Members](/docs/events/gateway-events#request-guild-members) | Requests members for a guild |
-| [Request Soundboard Sounds](/docs/events/gateway-events#request-soundboard-sounds) | Requests soundboard sounds in a set of guilds |
-| [Update Voice State](/docs/events/gateway-events#update-voice-state) | Joins, moves, or disconnects the app from a voice channel |
-| [Update Presence](/docs/events/gateway-events#update-presence) | Updates an app's presence |
-
-#### Identify
-
-Used to trigger the initial handshake with the gateway.
-
-Details about identifying is in the [Gateway documentation](/docs/events/gateway#identifying).
-
-###### Identify Structure
-
-| Field | Type | Description | Default |
-|------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|---------|
-| token | string | Authentication token | - |
-| properties | object | [Connection properties](/docs/events/gateway-events#identify-identify-connection-properties) | - |
-| compress? | boolean | Whether this connection supports compression of packets | false |
-| large_threshold? | integer | Value between 50 and 250, total number of members where the gateway will stop sending offline members in the guild member list | 50 |
-| shard? | array of two integers (shard_id, num_shards) | Used for [Guild Sharding](/docs/events/gateway#sharding) | - |
-| presence? | [update presence](/docs/events/gateway-events#update-presence) object | Presence structure for initial presence information | - |
-| intents | integer | [Gateway Intents](/docs/events/gateway#gateway-intents) you wish to receive | - |
-
-###### Identify Connection Properties
-
-| Field | Type | Description |
-|---------|--------|-----------------------|
-| os | string | Your operating system |
-| browser | string | Your library name |
-| device | string | Your library name |
-
-:::warn
-These fields originally were $ prefixed (i.e: `$browser`) but [this syntax is deprecated](/docs/change-log#updated-connection-property-field-names). While they currently still work, it is recommended to move to non-prefixed fields.
-:::
-
-###### Example Identify
-
-```json
-{
- "op": 2,
- "d": {
- "token": "my_token",
- "properties": {
- "os": "linux",
- "browser": "disco",
- "device": "disco"
- },
- "compress": true,
- "large_threshold": 250,
- "shard": [0, 1],
- "presence": {
- "activities": [{
- "name": "Cards Against Humanity",
- "type": 0
- }],
- "status": "dnd",
- "since": 91879201,
- "afk": false
- },
- // This intent represents 1 << 0 for GUILDS, 1 << 1 for GUILD_MEMBERS, and 1 << 2 for GUILD_BANS
- // This connection will only receive the events defined in those three intents
- "intents": 7
- }
-}
-```
-
-#### Resume
-
-Used to replay missed events when a disconnected client resumes.
-
-Details about resuming are in the [Gateway documentation](/docs/events/gateway#resuming).
-
-###### Resume Structure
-
-| Field | Type | Description |
-|------------|---------|-------------------------------|
-| token | string | Session token |
-| session_id | string | Session ID |
-| seq | integer | Last sequence number received |
-
-###### Example Resume
-
-```json
-{
- "op": 6,
- "d": {
- "token": "randomstring",
- "session_id": "evenmorerandomstring",
- "seq": 1337
- }
-}
-```
-
-#### Heartbeat
-
-Used to maintain an active gateway connection. Must be sent every `heartbeat_interval` milliseconds after the [Opcode 10 Hello](/docs/events/gateway-events#hello) payload is received. The inner `d` key is the last sequence number—`s`—received by the client. If you have not yet received one, send `null`.
-
-Details about heartbeats are in the [Gateway documentation](/docs/events/gateway#sending-heartbeats).
-
-###### Example Heartbeat
-
-```json
-{
- "op": 1,
- "d": 251
-}
-```
-
-#### Request Guild Members
-
-Used to request all members for a guild or a list of guilds. When initially connecting, if you don't have the `GUILD_PRESENCES` [Gateway Intent](/docs/events/gateway#gateway-intents), or if the guild is over 75k members, it will only send members who are in voice, plus the member for you (the connecting user). Otherwise, if a guild has over `large_threshold` members (value in the [Gateway Identify](/docs/events/gateway-events#identify)), it will only send members who are online, have a role, have a nickname, or are in a voice channel, and if it has under `large_threshold` members, it will send all members. If a client wishes to receive additional members, they need to explicitly request them via this operation. The server will send [Guild Members Chunk](/docs/events/gateway-events#guild-members-chunk) events in response with up to 1000 members per chunk until all members that match the request have been sent.
-
-Due to our privacy and infrastructural concerns with this feature, there are some limitations that apply:
-
-- `GUILD_PRESENCES` intent is required to set `presences = true`. Otherwise, it will always be false
-- `GUILD_MEMBERS` intent is required to request the entire member list—`(query=‘’, limit=0<=n)`
-- You will be limited to requesting 1 `guild_id` per request
-- Requesting a prefix (`query` parameter) will return a maximum of 100 members
-- Requesting `user_ids` will continue to be limited to returning 100 members
-
-:::info
-We are introducing a new rate limit to the Request Guild Members opcode. See [Introducing Rate Limit When Requesting All Guild Members](/docs/change-log/2025-08-14-introducing-guild-members-rate-limit) for more information and timeline on this new rate limit.
-:::
-
-###### Request Guild Members Structure
-
-| Field | Type | Description | Required |
-|------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
-| guild_id | snowflake | ID of the guild to get members for | true |
-| query? | string | string that username starts with, or an empty string to return all members | one of query or user_ids |
-| limit | integer | maximum number of members to send matching the `query`; a limit of `0` can be used with an empty string `query` to return all members | true when specifying query |
-| presences? | boolean | used to specify if we want the presences of the matched members | false |
-| user_ids? | snowflake or array of snowflakes | used to specify which users you wish to fetch | one of query or user_ids |
-| nonce? | string | nonce to identify the [Guild Members Chunk](/docs/events/gateway-events#guild-members-chunk) response | false |
-
-:::info
-Nonce can only be up to 32 bytes. If you send an invalid nonce it will be ignored and the reply member_chunk(s) will not have a nonce set.
-:::
-
-###### Example Request Guild Members
-
-```json
-{
- "op": 8,
- "d": {
- "guild_id": "41771983444115456",
- "query": "",
- "limit": 0
- }
-}
-```
-
-#### Request Soundboard Sounds
-
-Used to request soundboard sounds for a list of guilds. The server will send [Soundboard Sounds](/docs/events/gateway-events#soundboard-sounds) events for each guild in response.
-
-###### Request Soundboard Sounds Structure
-
-| Field | Type | Description |
-|-----------|---------------------|------------------------------------------------|
-| guild_ids | array of snowflakes | IDs of the guilds to get soundboard sounds for |
-
-###### Example Request Soundboard Sounds
-
-```json
-{
- "op": 31,
- "d": {
- "guild_ids": ["613425648685547541", "81384788765712384"]
- }
-}
-```
-
-#### Update Voice State
-
-Sent when a client wants to join, move, or disconnect from a voice channel.
-
-###### Gateway Voice State Update Structure
-
-| Field | Type | Description |
-|------------|------------|----------------------------------------------------------------------|
-| guild_id | snowflake | ID of the guild |
-| channel_id | ?snowflake | ID of the voice channel client wants to join (null if disconnecting) |
-| self_mute | boolean | Whether the client is muted |
-| self_deaf | boolean | Whether the client deafened |
-
-###### Example Gateway Voice State Update
-
-```json
-{
- "op": 4,
- "d": {
- "guild_id": "41771983423143937",
- "channel_id": "127121515262115840",
- "self_mute": false,
- "self_deaf": false
- }
-}
-```
-
-#### Update Presence
-
-Sent by the client to indicate a presence or status update.
-
-###### Gateway Presence Update Structure
-
-| Field | Type | Description |
-|------------|--------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|
-| since | ?integer | Unix time (in milliseconds) of when the client went idle, or null if the client is not idle |
-| activities | array of [activity](/docs/events/gateway-events#activity-object) objects | User's activities |
-| status | string | User's new [status](/docs/events/gateway-events#update-presence-status-types) |
-| afk | boolean | Whether or not the client is afk |
-
-###### Status Types
-
-| Status | Description |
-|-----------|--------------------------------|
-| online | Online |
-| dnd | Do Not Disturb |
-| idle | AFK |
-| invisible | Invisible and shown as offline |
-| offline | Offline |
-
-###### Example Gateway Presence Update
-
-```json
-{
- "op": 3,
- "d": {
- "since": 91879201,
- "activities": [{
- "name": "Save the Oxford Comma",
- "type": 0
- }],
- "status": "online",
- "afk": false
- }
-}
-```
-
-## Receive Events
-
-Receive events are Gateway events encapsulated in an [event payload](/docs/events/gateway-events#payload-structure), and are sent by Discord to an app through a Gateway connection. Receive events correspond to events that happen in a Discord server where the app is installed.
-
-| Name | Description |
-|--------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
-| [Hello](/docs/events/gateway-events#hello) | Defines the heartbeat interval |
-| [Ready](/docs/events/gateway-events#ready) | Contains the initial state information |
-| [Resumed](/docs/events/gateway-events#resumed) | Response to [Resume](/docs/events/gateway-events#resume) |
-| [Reconnect](/docs/events/gateway-events#reconnect) | Server is going away, client should reconnect to gateway and resume |
-| [Rate Limited](/docs/events/gateway-events#rate-limited) | Application was rate limited for a gateway opcode |
-| [Invalid Session](/docs/events/gateway-events#invalid-session) | Failure response to [Identify](/docs/events/gateway-events#identify) or [Resume](/docs/events/gateway-events#resume) or invalid active session |
-| [Application Command Permissions Update](/docs/events/gateway-events#application-command-permissions-update) | Application command permission was updated |
-| [Auto Moderation Rule Create](/docs/events/gateway-events#auto-moderation-rule-create) | Auto Moderation rule was created |
-| [Auto Moderation Rule Update](/docs/events/gateway-events#auto-moderation-rule-update) | Auto Moderation rule was updated |
-| [Auto Moderation Rule Delete](/docs/events/gateway-events#auto-moderation-rule-delete) | Auto Moderation rule was deleted |
-| [Auto Moderation Action Execution](/docs/events/gateway-events#auto-moderation-action-execution) | Auto Moderation rule was triggered and an action was executed (e.g. a message was blocked) |
-| [Channel Create](/docs/events/gateway-events#channel-create) | New guild channel created |
-| [Channel Update](/docs/events/gateway-events#channel-update) | Channel was updated |
-| [Channel Delete](/docs/events/gateway-events#channel-delete) | Channel was deleted |
-| [Channel Pins Update](/docs/events/gateway-events#channel-pins-update) | Message was pinned or unpinned |
-| [Thread Create](/docs/events/gateway-events#thread-create) | Thread created, also sent when being added to a private thread |
-| [Thread Update](/docs/events/gateway-events#thread-update) | Thread was updated |
-| [Thread Delete](/docs/events/gateway-events#thread-delete) | Thread was deleted |
-| [Thread List Sync](/docs/events/gateway-events#thread-list-sync) | Sent when gaining access to a channel, contains all active threads in that channel |
-| [Thread Member Update](/docs/events/gateway-events#thread-member-update) | [Thread member](/docs/resources/channel#thread-member-object) for the current user was updated |
-| [Thread Members Update](/docs/events/gateway-events#thread-members-update) | Some user(s) were added to or removed from a thread |
-| [Entitlement Create](/docs/events/gateway-events#entitlement-create) | Entitlement was created |
-| [Entitlement Update](/docs/events/gateway-events#entitlement-update) | Entitlement was updated or renewed |
-| [Entitlement Delete](/docs/events/gateway-events#entitlement-delete) | Entitlement was deleted |
-| [Guild Create](/docs/events/gateway-events#guild-create) | Lazy-load for unavailable guild, guild became available, or user joined a new guild |
-| [Guild Update](/docs/events/gateway-events#guild-update) | Guild was updated |
-| [Guild Delete](/docs/events/gateway-events#guild-delete) | Guild became unavailable, or user left/was removed from a guild |
-| [Guild Audit Log Entry Create](/docs/events/gateway-events#guild-audit-log-entry-create) | A guild audit log entry was created |
-| [Guild Ban Add](/docs/events/gateway-events#guild-ban-add) | User was banned from a guild |
-| [Guild Ban Remove](/docs/events/gateway-events#guild-ban-remove) | User was unbanned from a guild |
-| [Guild Emojis Update](/docs/events/gateway-events#guild-emojis-update) | Guild emojis were updated |
-| [Guild Stickers Update](/docs/events/gateway-events#guild-stickers-update) | Guild stickers were updated |
-| [Guild Integrations Update](/docs/events/gateway-events#guild-integrations-update) | Guild integration was updated |
-| [Guild Member Add](/docs/events/gateway-events#guild-member-add) | New user joined a guild |
-| [Guild Member Remove](/docs/events/gateway-events#guild-member-remove) | User was removed from a guild |
-| [Guild Member Update](/docs/events/gateway-events#guild-member-update) | Guild member was updated |
-| [Guild Members Chunk](/docs/events/gateway-events#guild-members-chunk) | Response to [Request Guild Members](/docs/events/gateway-events#request-guild-members) |
-| [Guild Role Create](/docs/events/gateway-events#guild-role-create) | Guild role was created |
-| [Guild Role Update](/docs/events/gateway-events#guild-role-update) | Guild role was updated |
-| [Guild Role Delete](/docs/events/gateway-events#guild-role-delete) | Guild role was deleted |
-| [Guild Scheduled Event Create](/docs/events/gateway-events#guild-scheduled-event-create) | Guild scheduled event was created |
-| [Guild Scheduled Event Update](/docs/events/gateway-events#guild-scheduled-event-update) | Guild scheduled event was updated |
-| [Guild Scheduled Event Delete](/docs/events/gateway-events#guild-scheduled-event-delete) | Guild scheduled event was deleted |
-| [Guild Scheduled Event User Add](/docs/events/gateway-events#guild-scheduled-event-user-add) | User subscribed to a guild scheduled event |
-| [Guild Scheduled Event User Remove](/docs/events/gateway-events#guild-scheduled-event-user-remove) | User unsubscribed from a guild scheduled event |
-| [Guild Soundboard Sound Create](/docs/events/gateway-events#guild-soundboard-sound-create) | Guild soundboard sound was created |
-| [Guild Soundboard Sound Update](/docs/events/gateway-events#guild-soundboard-sound-update) | Guild soundboard sound was updated |
-| [Guild Soundboard Sound Delete](/docs/events/gateway-events#guild-soundboard-sound-delete) | Guild soundboard sound was deleted |
-| [Guild Soundboard Sounds Update](/docs/events/gateway-events#guild-soundboard-sounds-update) | Guild soundboard sounds were updated |
-| [Soundboard Sounds](/docs/events/gateway-events#soundboard-sounds) | Response to [Request Soundboard Sounds](/docs/events/gateway-events#request-soundboard-sounds) |
-| [Integration Create](/docs/events/gateway-events#integration-create) | Guild integration was created |
-| [Integration Update](/docs/events/gateway-events#integration-update) | Guild integration was updated |
-| [Integration Delete](/docs/events/gateway-events#integration-delete) | Guild integration was deleted |
-| [Interaction Create](/docs/events/gateway-events#interaction-create) | User used an interaction, such as an [Application Command](/docs/interactions/application-commands) |
-| [Invite Create](/docs/events/gateway-events#invite-create) | Invite to a channel was created |
-| [Invite Delete](/docs/events/gateway-events#invite-delete) | Invite to a channel was deleted |
-| [Message Create](/docs/events/gateway-events#message-create) | Message was created |
-| [Message Update](/docs/events/gateway-events#message-update) | Message was edited |
-| [Message Delete](/docs/events/gateway-events#message-delete) | Message was deleted |
-| [Message Delete Bulk](/docs/events/gateway-events#message-delete-bulk) | Multiple messages were deleted at once |
-| [Message Reaction Add](/docs/events/gateway-events#message-reaction-add) | User reacted to a message |
-| [Message Reaction Remove](/docs/events/gateway-events#message-reaction-remove) | User removed a reaction from a message |
-| [Message Reaction Remove All](/docs/events/gateway-events#message-reaction-remove-all) | All reactions were explicitly removed from a message |
-| [Message Reaction Remove Emoji](/docs/events/gateway-events#message-reaction-remove-emoji) | All reactions for a given emoji were explicitly removed from a message |
-| [Presence Update](/docs/events/gateway-events#presence-update) | User was updated |
-| [Stage Instance Create](/docs/events/gateway-events#stage-instance-create) | Stage instance was created |
-| [Stage Instance Update](/docs/events/gateway-events#stage-instance-update) | Stage instance was updated |
-| [Stage Instance Delete](/docs/events/gateway-events#stage-instance-delete) | Stage instance was deleted or closed |
-| [Subscription Create](/docs/events/gateway-events#subscription-create) | Premium App Subscription was created |
-| [Subscription Update](/docs/events/gateway-events#subscription-update) | Premium App Subscription was updated |
-| [Subscription Delete](/docs/events/gateway-events#subscription-delete) | Premium App Subscription was deleted |
-| [Typing Start](/docs/events/gateway-events#typing-start) | User started typing in a channel |
-| [User Update](/docs/events/gateway-events#user-update) | Properties about the user changed |
-| [Voice Channel Effect Send](/docs/events/gateway-events#voice-channel-effect-send) | Someone sent an effect in a voice channel the current user is connected to |
-| [Voice State Update](/docs/events/gateway-events#voice-state-update) | Someone joined, left, or moved a voice channel |
-| [Voice Server Update](/docs/events/gateway-events#voice-server-update) | Guild's voice server was updated |
-| [Webhooks Update](/docs/events/gateway-events#webhooks-update) | Guild channel webhook was created, update, or deleted |
-| [Message Poll Vote Add](/docs/events/gateway-events#message-poll-vote-add) | User voted on a poll |
-| [Message Poll Vote Remove](/docs/events/gateway-events#message-poll-vote-remove) | User removed a vote on a poll |
-
-#### Hello
-
-Sent on connection to the websocket. Defines the heartbeat interval that an app should heartbeat to.
-
-###### Hello Structure
-
-| Field | Type | Description |
-|--------------------|---------|---------------------------------------------------------|
-| heartbeat_interval | integer | Interval (in milliseconds) an app should heartbeat with |
-
-###### Example Hello
-
-```json
-{
- "op": 10,
- "d": {
- "heartbeat_interval": 45000
- }
-}
-```
-
-#### Ready
-
-The ready event is dispatched when a client has completed the initial handshake with the gateway (for new sessions). The ready event can be the largest and most complex event the gateway will send, as it contains all the state required for a client to begin interacting with the rest of the platform.
-
-`guilds` are the guilds of which your bot is a member. They start out as unavailable when you connect to the gateway. As they become available, your bot will be notified via [Guild Create](/docs/events/gateway-events#guild-create) events.
-
-###### Ready Event Fields
-
-| Field | Type | Description |
-|--------------------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|
-| v | integer | [API version](/docs/reference#api-versioning-api-versions) |
-| user | [user](/docs/resources/user#user-object) object | Information about the user including email |
-| guilds | array of [Unavailable Guild](/docs/resources/guild#unavailable-guild-object) objects | Guilds the user is in |
-| session_id | string | Used for resuming connections |
-| resume_gateway_url | string | Gateway URL for resuming connections |
-| shard? | array of two integers (shard_id, num_shards) | [Shard information](/docs/events/gateway#sharding) associated with this session, if sent when identifying |
-| application | partial [application object](/docs/resources/application#application-object) | Contains `id` and `flags` |
-
-#### Resumed
-
-The resumed event is dispatched when a client has sent a [resume payload](/docs/events/gateway-events#resume) to the gateway (for resuming existing sessions).
-
-#### Reconnect
-
-The reconnect event is dispatched when a client should reconnect to the gateway (and resume their existing session, if they have one). This can occur at any point in the gateway connection lifecycle, even before/in place of receiving a [Hello](/docs/events/gateway-events#hello) event. A few seconds after the reconnect event is dispatched, the connection may be closed by the server.
-
-###### Example Gateway Reconnect
-
-```json
-{
- "op": 7,
- "d": null
-}
-```
-
-#### Invalid Session
-
-Sent to indicate one of at least three different situations:
-
-- the gateway could not initialize a session after receiving an [Opcode 2 Identify](/docs/events/gateway-events#identify)
-- the gateway could not resume a previous session after receiving an [Opcode 6 Resume](/docs/events/gateway-events#resume)
-- the gateway has invalidated an active session and is requesting client action
-
-The inner `d` key is a boolean that indicates whether the session may be resumable. See [Connecting](/docs/events/gateway#connecting) and [Resuming](/docs/events/gateway#resuming) for more information.
-
-###### Example Gateway Invalid Session
-
-```json
-{
- "op": 9,
- "d": false
-}
-```
-
-### Application Commands
-
-#### Application Command Permissions Update
-
-`APPLICATION_COMMAND_PERMISSIONS_UPDATE` event, sent when an application command's permissions are updated. The inner payload is an [application command permissions](/docs/interactions/application-commands#application-command-permissions-object-guild-application-command-permissions-structure) object.
-
-### Auto Moderation
-
-All [Auto Moderation](/docs/resources/auto-moderation) related events are only sent to bot users which have the `MANAGE_GUILD` permission.
-
-#### Auto Moderation Rule Create
-
-Sent when a rule is created. The inner payload is an [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) object.
-
-#### Auto Moderation Rule Update
-
-Sent when a rule is updated. The inner payload is an [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) object.
-
-#### Auto Moderation Rule Delete
-
-Sent when a rule is deleted. The inner payload is an [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) object.
-
-#### Auto Moderation Action Execution
-
-Sent when a rule is triggered and an action is executed (e.g. when a message is blocked).
-
-###### Auto Moderation Action Execution Event Fields
-
-| Field | Type | Description |
-|--------------------------|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
-| guild_id | snowflake | ID of the guild in which action was executed |
-| action | [auto moderation action](/docs/resources/auto-moderation#auto-moderation-action-object) object | Action which was executed |
-| rule_id | snowflake | ID of the rule which action belongs to |
-| rule_trigger_type | [trigger_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) | Trigger type of rule which was triggered |
-| user_id | snowflake | ID of the user which generated the content which triggered the rule |
-| channel_id? | snowflake | ID of the channel in which user content was posted |
-| message_id? | snowflake | ID of any user message which content belongs to * |
-| alert_system_message_id? | snowflake | ID of any system auto moderation messages posted as a result of this action ** |
-| content *** | string | User-generated text content |
-| matched_keyword | ?string | Word or phrase configured in the rule that triggered the rule |
-| matched_content *** | ?string | Substring in content that triggered the rule |
-
-\* `message_id` will not exist if message was blocked by [Auto Moderation](/docs/resources/auto-moderation) or content was not part of any message
-
-\*\* `alert_system_message_id` will not exist if this event does not correspond to an action with type `SEND_ALERT_MESSAGE`
-
-\*\*\* `MESSAGE_CONTENT` (`1 << 15`) [gateway intent](/docs/events/gateway#gateway-intents) is required to receive the `content` and `matched_content` fields
-
-### Channels
-
-#### Channel Create
-
-Sent when a new guild channel is created, relevant to the current user. The inner payload is a [channel](/docs/resources/channel#channel-object) object.
-
-#### Channel Update
-
-Sent when a channel is updated. The inner payload is a [channel](/docs/resources/channel#channel-object) object. This is not sent when the field `last_message_id` is altered. To keep track of the last_message_id changes, you must listen for [Message Create](/docs/events/gateway-events#message-create) events (or [Thread Create](/docs/events/gateway-events#thread-create) events for `GUILD_FORUM` and `GUILD_MEDIA` channels).
-
-This event may reference roles or guild members that no longer exist in the guild.
-
-#### Channel Delete
-
-Sent when a channel relevant to the current user is deleted. The inner payload is a [channel](/docs/resources/channel#channel-object) object.
-
-#### Thread Create
-
-Sent when a thread is created, relevant to the current user, or when the current user is added to a thread. The inner payload is a [channel](/docs/resources/channel#channel-object) object.
-
-- When a thread is created, includes an additional `newly_created` boolean field.
-- When being added to an existing private thread, includes a [thread member](/docs/resources/channel#thread-member-object) object.
-
-#### Thread Update
-
-Sent when a thread is updated. The inner payload is a [channel](/docs/resources/channel#channel-object) object. This is not sent when the field `last_message_id` is altered. To keep track of the last_message_id changes, you must listen for [Message Create](/docs/events/gateway-events#message-create) events.
-
-#### Thread Delete
-
-Sent when a thread relevant to the current user is deleted. The inner payload is a subset of the [channel](/docs/resources/channel#channel-object) object, containing just the `id`, `guild_id`, `parent_id`, and `type` fields.
-
-#### Thread List Sync
-
-Sent when the current user _gains_ access to a channel.
-
-###### Thread List Sync Event Fields
-
-| Field | Type | Description |
-|--------------|--------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| guild_id | snowflake | ID of the guild |
-| channel_ids? | array of snowflakes | Parent channel IDs whose threads are being synced. If omitted, then threads were synced for the entire guild. This array may contain channel_ids that have no active threads as well, so you know to clear that data. |
-| threads | array of [channel](/docs/resources/channel#channel-object) objects | All active threads in the given channels that the current user can access |
-| members | array of [thread member](/docs/resources/channel#thread-member-object) objects | All thread member objects from the synced threads for the current user, indicating which threads the current user has been added to |
-
-#### Thread Member Update
-
-Sent when the [thread member](/docs/resources/channel#thread-member-object) object for the current user is updated. The inner payload is a [thread member](/docs/resources/channel#thread-member-object) object with an extra `guild_id` field. This event is documented for completeness, but unlikely to be used by most bots. For bots, this event largely is just a signal that you are a member of the thread. See the [threads docs](/docs/topics/threads) for more details.
-
-###### Thread Member Update Event Extra Fields
-
-| Field | Type | Description |
-|----------|-----------|-----------------|
-| guild_id | snowflake | ID of the guild |
-
-
-#### Thread Members Update
-
-Sent when anyone is added to or removed from a thread. If the current user does not have the `GUILD_MEMBERS` [Gateway Intent](/docs/events/gateway#gateway-intents), then this event will only be sent if the current user was added to or removed from the thread.
-
-###### Thread Members Update Event Fields
-
-| Field | Type | Description |
-|---------------------|--------------------------------------------------------------------------------|-----------------------------------------------------------|
-| id | snowflake | ID of the thread |
-| guild_id | snowflake | ID of the guild |
-| member_count | integer | Approximate number of members in the thread, capped at 50 |
-| added_members?\* | array of [thread member](/docs/resources/channel#thread-member-object) objects | Users who were added to the thread |
-| removed_member_ids? | array of snowflakes | ID of the users who were removed from the thread |
-
-\* In this gateway event, the thread member objects will also include the [guild member](/docs/resources/guild#guild-member-object) and nullable [presence](/docs/events/gateway-events#presence) objects for each added thread member.
-
-#### Channel Pins Update
-
-Sent when a message is pinned or unpinned in a text channel. This is not sent when a pinned message is deleted.
-
-###### Channel Pins Update Event Fields
-
-| Field | Type | Description |
-|---------------------|--------------------|---------------------------------------------------------|
-| guild_id? | snowflake | ID of the guild |
-| channel_id | snowflake | ID of the channel |
-| last_pin_timestamp? | ?ISO8601 timestamp | Time at which the most recent pinned message was pinned |
-
-### Entitlements
-
-#### Entitlement Create
-
-:::warn
-Note: The`ENTITLEMENT_CREATE` event behavior changed on October 1, 2024. Please see the [Change Log and Entitlement Migration Guide](/docs/change-log#premium-apps-entitlement-migration-and-new-subscription-api) for more information on what changed.
-:::
-
-Sent when an entitlement is created. The inner payload is an [entitlement](/docs/resources/entitlement#entitlement-object) object.
-
-#### Entitlement Update
-
-:::warn
-Note: The`ENTITLEMENT_UPDATE` event behavior changed on October 1, 2024. Please see the [Change Log and Entitlement Migration Guide](/docs/change-log#premium-apps-entitlement-migration-and-new-subscription-api) for more information on what changed.
-:::
-
-Sent when an entitlement is updated. The inner payload is an [entitlement](/docs/resources/entitlement#entitlement-object) object.
-
-For subscription entitlements, this event is triggered only when a user's subscription ends, providing an `ends_at` timestamp that indicates the end of the entitlement.
-
-#### Entitlement Delete
-
-Sent when an entitlement is deleted. The inner payload is an [entitlement](/docs/resources/entitlement#entitlement-object) object.
-
-Entitlement deletions are infrequent, and occur when:
-
-- Discord issues a refund for a subscription
-- Discord removes an entitlement from a user via internal tooling
-- Discord deletes an app-managed entitlement they created via the API
-
-Entitlements are _not_ deleted when they expire.
-
-### Guilds
-
-#### Guild Create
-
-This event can be sent in three different scenarios:
-
-1. When a user is initially connecting, to lazily load and backfill information for all unavailable guilds sent in the [Ready](/docs/events/gateway-events#ready) event. Guilds that are unavailable due to an outage will send a [Guild Delete](/docs/events/gateway-events#guild-delete) event.
-2. When a Guild becomes available again to the client.
-3. When the current user joins a new Guild.
-
-:::info
-During an outage, the guild object in scenarios 1 and 3 may be marked as unavailable.
-:::
-
-The inner payload can be:
-
-- An available Guild: a [guild](/docs/resources/guild#guild-object) object with extra fields, as noted below.
-- An unavailable Guild: an [unavailable guild](/docs/resources/guild#unavailable-guild-object) object.
-
-###### Guild Create Extra Fields
-
-| Field | Type | Description |
-|------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
-| joined_at | ISO8601 timestamp | When this guild was joined at |
-| large | boolean | `true` if this is considered a large guild |
-| unavailable? | boolean | `true` if this guild is unavailable due to an outage |
-| member_count | integer | Total number of members in this guild |
-| voice_states | array of partial [voice state](/docs/resources/voice#voice-state-object) objects | States of members currently in voice channels; lacks the `guild_id` key |
-| members | array of [guild member](/docs/resources/guild#guild-member-object) objects | Users in the guild |
-| channels | array of [channel](/docs/resources/channel#channel-object) objects | Channels in the guild |
-| threads | array of [channel](/docs/resources/channel#channel-object) objects | All active threads in the guild that current user has permission to view |
-| presences | array of partial [presence update](/docs/events/gateway-events#presence-update) objects | Presences of the members in the guild, will only include non-offline members if the size is greater than `large threshold` |
-| stage_instances | array of [stage instance](/docs/resources/stage-instance#stage-instance-object) objects | Stage instances in the guild |
-| guild_scheduled_events | array of [guild scheduled event](/docs/resources/guild-scheduled-event#guild-scheduled-event-object) objects | Scheduled events in the guild |
-| soundboard_sounds | array of [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) objects | Soundboard sounds in the guild |
-
-:::warn
-If your bot does not have the `GUILD_PRESENCES` [Gateway Intent](/docs/events/gateway#gateway-intents), or if the guild has over 75k members, members and presences returned in this event will only contain your bot and users in voice channels.
-:::
-
-#### Guild Update
-
-Sent when a guild is updated. The inner payload is a [guild](/docs/resources/guild#guild-object) object.
-
-#### Guild Delete
-
-Sent when a guild becomes or was already unavailable due to an outage, or when the user leaves or is removed from a guild. The inner payload is an [unavailable guild](/docs/resources/guild#unavailable-guild-object) object. If the `unavailable` field is not set, the user was removed from the guild.
-
-#### Guild Audit Log Entry Create
-
-Sent when a guild audit log entry is created. The inner payload is an [Audit Log Entry](/docs/resources/audit-log#audit-log-entry-object) object with an extra `guild_id` key. This event is only sent to bots with the `VIEW_AUDIT_LOG` permission.
-
-###### Guild Audit Log Entry Create Event Extra Fields
-
-| Field | Type | Description |
-|----------|-----------|-----------------|
-| guild_id | snowflake | ID of the guild |
-
-#### Guild Ban Add
-
-Sent when a user is banned from a guild.
-
-###### Guild Ban Add Event Fields
-
-| Field | Type | Description |
-|----------|---------------------------------------------------|---------------------|
-| guild_id | snowflake | ID of the guild |
-| user | a [user](/docs/resources/user#user-object) object | User who was banned |
-
-#### Guild Ban Remove
-
-Sent when a user is unbanned from a guild.
-
-###### Guild Ban Remove Event Fields
-
-| Field | Type | Description |
-|----------|---------------------------------------------------|-----------------------|
-| guild_id | snowflake | ID of the guild |
-| user | a [user](/docs/resources/user#user-object) object | User who was unbanned |
-
-#### Guild Emojis Update
-
-Sent when a guild's emojis have been updated.
-
-###### Guild Emojis Update Event Fields
-
-| Field | Type | Description |
-|----------|-----------|-------------------------------------------------------|
-| guild_id | snowflake | ID of the guild |
-| emojis | array | Array of [emojis](/docs/resources/emoji#emoji-object) |
-
-#### Guild Stickers Update
-
-Sent when a guild's stickers have been updated.
-
-###### Guild Stickers Update Event Fields
-
-| Field | Type | Description |
-|----------|-----------|-------------------------------------------------------------|
-| guild_id | snowflake | ID of the guild |
-| stickers | array | Array of [stickers](/docs/resources/sticker#sticker-object) |
-
-#### Guild Integrations Update
-
-Sent when a guild integration is updated.
-
-###### Guild Integrations Update Event Fields
-
-| Field | Type | Description |
-|----------|-----------|-------------------------------------------------|
-| guild_id | snowflake | ID of the guild whose integrations were updated |
-
-#### Guild Member Add
-
-:::warn
-If using [Gateway Intents](/docs/events/gateway#gateway-intents), the `GUILD_MEMBERS` intent will be required to receive this event.
-:::
-
-Sent when a new user joins a guild. The inner payload is a [guild member](/docs/resources/guild#guild-member-object) object with an extra `guild_id` key:
-
-###### Guild Member Add Extra Fields
-
-| Field | Type | Description |
-|----------|-----------|-----------------|
-| guild_id | snowflake | ID of the guild |
-
-#### Guild Member Remove
-
-:::warn
-If using [Gateway Intents](/docs/events/gateway#gateway-intents), the `GUILD_MEMBERS` intent will be required to receive this event.
-:::
-
-Sent when a user is removed from a guild (leave/kick/ban).
-
-###### Guild Member Remove Event Fields
-
-| Field | Type | Description |
-|----------|---------------------------------------------------|----------------------|
-| guild_id | snowflake | ID of the guild |
-| user | a [user](/docs/resources/user#user-object) object | User who was removed |
-
-#### Guild Member Update
-
-:::warn
-If using [Gateway Intents](/docs/events/gateway#gateway-intents), the `GUILD_MEMBERS` intent will be required to receive this event.
-:::
-
-Sent when a guild member is updated. This will also fire when the user object of a guild member changes.
-
-###### Guild Member Update Event Fields
-
-| Field | Type | Description |
-|-------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| guild_id | snowflake | ID of the guild |
-| roles | array of snowflakes | User role ids |
-| user | a [user](/docs/resources/user#user-object) object | User |
-| nick? | ?string | Nickname of the user in the guild |
-| avatar | ?string | Member's [guild avatar hash](/docs/reference#image-formatting) |
-| banner | ?string | Member's [guild banner hash](/docs/reference#image-formatting) |
-| joined_at | ?ISO8601 timestamp | When the user joined the guild |
-| premium_since? | ?ISO8601 timestamp | When the user starting [boosting](https://support.discord.com/hc/en-us/articles/360028038352-Server-Boosting-) the guild |
-| deaf? | boolean | Whether the user is deafened in voice channels |
-| mute? | boolean | Whether the user is muted in voice channels |
-| pending? | boolean | Whether the user has not yet passed the guild's [Membership Screening](/docs/resources/guild#membership-screening-object) requirements |
-| communication_disabled_until? | ?ISO8601 timestamp | When the user's [timeout](https://support.discord.com/hc/en-us/articles/4413305239191-Time-Out-FAQ) will expire and the user will be able to communicate in the guild again, null or a time in the past if the user is not timed out |
-| flags? | integer | [Guild member flags](/docs/resources/guild#guild-member-object-guild-member-flags) represented as a bit set, defaults to 0 |
-| avatar_decoration_data? | ?[avatar decoration data](/docs/resources/user#avatar-decoration-data-object) | Data for the member's guild avatar decoration |
-
-#### Guild Members Chunk
-
-Sent in response to [Guild Request Members](/docs/events/gateway-events#request-guild-members).
-You can use the `chunk_index` and `chunk_count` to calculate how many chunks are left for your request.
-
-###### Guild Members Chunk Event Fields
-
-| Field | Type | Description |
-|-------------|----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|
-| guild_id | snowflake | ID of the guild |
-| members | array of [guild member](/docs/resources/guild#guild-member-object) objects | Set of guild members |
-| chunk_index | integer | Chunk index in the expected chunks for this response (`0 <= chunk_index < chunk_count`) |
-| chunk_count | integer | Total number of expected chunks for this response |
-| not_found? | array | When passing an invalid ID to `REQUEST_GUILD_MEMBERS`, it will be returned here |
-| presences? | array of [presence](/docs/events/gateway-events#presence) objects | When passing `true` to `REQUEST_GUILD_MEMBERS`, presences of the returned members will be here |
-| nonce? | string | Nonce used in the [Guild Members Request](/docs/events/gateway-events#request-guild-members) |
-
-#### Guild Role Create
-
-Sent when a guild role is created.
-
-###### Guild Role Create Event Fields
-
-| Field | Type | Description |
-|----------|-------------------------------------------------------|-----------------------|
-| guild_id | snowflake | ID of the guild |
-| role | a [role](/docs/topics/permissions#role-object) object | Role that was created |
-
-#### Guild Role Update
-
-Sent when a guild role is updated.
-
-###### Guild Role Update Event Fields
-
-| Field | Type | Description |
-|----------|-------------------------------------------------------|-----------------------|
-| guild_id | snowflake | ID of the guild |
-| role | a [role](/docs/topics/permissions#role-object) object | Role that was updated |
-
-#### Guild Role Delete
-
-Sent when a guild role is deleted.
-
-###### Guild Role Delete Event Fields
-
-| Field | Type | Description |
-|----------|-----------|-----------------|
-| guild_id | snowflake | ID of the guild |
-| role_id | snowflake | ID of the role |
-
-#### Guild Scheduled Event Create
-
-Sent when a guild scheduled event is created. The inner payload is a [guild scheduled event](/docs/resources/guild-scheduled-event#guild-scheduled-event-object) object.
-
-#### Guild Scheduled Event Update
-
-Sent when a guild scheduled event is updated. The inner payload is a [guild scheduled event](/docs/resources/guild-scheduled-event#guild-scheduled-event-object) object.
-
-#### Guild Scheduled Event Delete
-
-Sent when a guild scheduled event is deleted. The inner payload is a [guild scheduled event](/docs/resources/guild-scheduled-event#guild-scheduled-event-object) object.
-
-#### Guild Scheduled Event User Add
-
-Sent when a user has subscribed to a guild scheduled event.
-
-###### Guild Scheduled Event User Add Event Fields
-
-| Field | Type | Description |
-|--------------------------|-----------|---------------------------------|
-| guild_scheduled_event_id | snowflake | ID of the guild scheduled event |
-| user_id | snowflake | ID of the user |
-| guild_id | snowflake | ID of the guild |
-
-#### Guild Scheduled Event User Remove
-
-Sent when a user has unsubscribed from a guild scheduled event.
-
-###### Guild Scheduled Event User Remove Event Fields
-
-| Field | Type | Description |
-|--------------------------|-----------|---------------------------------|
-| guild_scheduled_event_id | snowflake | ID of the guild scheduled event |
-| user_id | snowflake | ID of the user |
-| guild_id | snowflake | ID of the guild |
-
-#### Guild Soundboard Sound Create
-
-Sent when a guild soundboard sound is created. The inner payload is a [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) object.
-
-#### Guild Soundboard Sound Update
-
-Sent when a guild soundboard sound is updated. The inner payload is a [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) object.
-
-#### Guild Soundboard Sound Delete
-
-Sent when a guild soundboard sound is deleted.
-
-###### Guild Soundboard Sound Delete Event Fields
-
-| Field | Type | Description |
-|----------|-----------|----------------------------------|
-| sound_id | snowflake | ID of the sound that was deleted |
-| guild_id | snowflake | ID of the guild the sound was in |
-
-#### Guild Soundboard Sounds Update
-
-Sent when multiple guild soundboard sounds are updated.
-
-###### Guild Soundboard Sounds Update Event Fields
-
-| Field | Type | Description |
-|-------------------|-----------------------------------------------------------------------------------------|-------------------------------|
-| soundboard_sounds | array of [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) objects | The guild's soundboard sounds |
-| guild_id | snowflake | ID of the guild |
-
-#### Soundboard Sounds
-
-Includes a guild's list of soundboard sounds. Sent in response to [Request Soundboard Sounds](/docs/events/gateway-events#request-soundboard-sounds).
-
-###### Soundboard Sounds Event Fields
-
-| Field | Type | Description |
-|-------------------|-----------------------------------------------------------------------------------------|-------------------------------|
-| soundboard_sounds | array of [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) objects | The guild's soundboard sounds |
-| guild_id | snowflake | ID of the guild |
-
-### Integrations
-
-#### Integration Create
-
-Sent when an integration is created. The inner payload is an [integration](/docs/resources/guild#integration-object) object with `user` omitted and an additional `guild_id` key:
-
-###### Integration Create Event Additional Fields
-
-| Field | Type | Description |
-|----------|-----------|-----------------|
-| guild_id | snowflake | ID of the guild |
-
-#### Integration Update
-
-Sent when an integration is updated. The inner payload is an [integration](/docs/resources/guild#integration-object) object with `user` omitted and an additional `guild_id` key:
-
-###### Integration Update Event Additional Fields
-
-| Field | Type | Description |
-|----------|-----------|-----------------|
-| guild_id | snowflake | ID of the guild |
-
-#### Integration Delete
-
-Sent when an integration is deleted.
-
-###### Integration Delete Event Fields
-
-| Field | Type | Description |
-|-----------------|-----------|---------------------------------------------------------------|
-| id | snowflake | Integration ID |
-| guild_id | snowflake | ID of the guild |
-| application_id? | snowflake | ID of the bot/OAuth2 application for this discord integration |
-
-### Invites
-
-All [Invite](/docs/resources/invite) related events are only sent to bot users with the `MANAGE_CHANNELS` permission on the channel.
-
-#### Invite Create
-
-Sent when a new invite to a channel is created.
-
-###### Invite Create Event Fields
-
-| Field | Type | Description |
-|---------------------|------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
-| channel_id | snowflake | Channel the invite is for |
-| code | string | Unique invite [code](/docs/resources/invite#invite-object) |
-| created_at | ISO8601 timestamp | Time at which the invite was created |
-| guild_id? | snowflake | Guild of the invite |
-| inviter? | [user](/docs/resources/user#user-object) object | User that created the invite |
-| max_age | integer | How long the invite is valid for (in seconds) |
-| max_uses | integer | Maximum number of times the invite can be used |
-| target_type? | integer | [Type of target](/docs/resources/invite#invite-object-invite-target-types) for this voice channel invite |
-| target_user? | [user](/docs/resources/user#user-object) object | User whose stream to display for this voice channel stream invite |
-| target_application? | partial [application](/docs/resources/application#application-object) object | Embedded application to open for this voice channel embedded application invite |
-| temporary | boolean | Whether or not the invite is temporary (invited users will be kicked on disconnect unless they're assigned a role) |
-| uses | integer | How many times the invite has been used (always will be 0) |
-| expires_at | ?ISO8601 timestamp | the expiration date of this invite |
-
-#### Invite Delete
-
-Sent when an invite is deleted.
-
-###### Invite Delete Event Fields
-
-| Field | Type | Description |
-|------------|-----------|------------------------------------------------------------|
-| channel_id | snowflake | Channel of the invite |
-| guild_id? | snowflake | Guild of the invite |
-| code | string | Unique invite [code](/docs/resources/invite#invite-object) |
-
-### Messages
-
-:::warn
-Unlike persistent messages, ephemeral messages are sent directly to the user and the bot who sent the message rather than through the guild channel. Because of this, ephemeral messages are tied to the [`DIRECT_MESSAGES` intent](/docs/events/gateway#list-of-intents), and the message object won't include `guild_id` or `member`.
-:::
-
-#### Message Create
-
-Sent when a message is created. The inner payload is a [message](/docs/resources/message#message-object) object with the following extra fields:
-
-###### Message Create Extra Fields
-
-| Field | Type | Description |
-|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|
-| guild_id? | snowflake | ID of the guild the message was sent in - unless it is an ephemeral message |
-| member? | partial [guild member](/docs/resources/guild#guild-member-object) object | Member properties for this message's author. Missing for ephemeral messages and messages from webhooks |
-| mentions | array of [user](/docs/resources/user#user-object) objects, optionally with an additional partial [member](/docs/resources/guild#guild-member-object) field | Users specifically mentioned in the message |
-
-#### Message Update
-
-Sent when a message is updated. The inner payload is a [message](/docs/resources/message#message-object) object with the same extra fields as [MESSAGE_CREATE](/docs/events/gateway-events#message-create).
-
-:::warn
-The value for `tts` will always be false in message updates.
-:::
-
-#### Message Delete
-
-Sent when a message is deleted.
-
-###### Message Delete Event Fields
-
-| Field | Type | Description |
-|------------|-----------|-------------------|
-| id | snowflake | ID of the message |
-| channel_id | snowflake | ID of the channel |
-| guild_id? | snowflake | ID of the guild |
-
-#### Message Delete Bulk
-
-Sent when multiple messages are deleted at once.
-
-###### Message Delete Bulk Event Fields
-
-| Field | Type | Description |
-|------------|---------------------|---------------------|
-| ids | array of snowflakes | IDs of the messages |
-| channel_id | snowflake | ID of the channel |
-| guild_id? | snowflake | ID of the guild |
-
-#### Message Reaction Add
-
-Sent when a user adds a reaction to a message.
-
-###### Message Reaction Add Event Fields
-
-| Field | Type | Description |
-|--------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------|
-| user_id | snowflake | ID of the user |
-| channel_id | snowflake | ID of the channel |
-| message_id | snowflake | ID of the message |
-| guild_id? | snowflake | ID of the guild |
-| member? | [member](/docs/resources/guild#guild-member-object) object | Member who reacted if this happened in a guild |
-| emoji | a partial [emoji](/docs/resources/emoji#emoji-object) object | Emoji used to react - [example](/docs/resources/emoji#emoji-object-standard-emoji-example) |
-| message_author_id? | snowflake | ID of the user who authored the message which was reacted to |
-| burst | boolean | true if this is a super-reaction |
-| burst_colors? | array of strings | Colors used for super-reaction animation in "#rrggbb" format |
-| type | integer | The [type of reaction](/docs/resources/message#get-reactions-reaction-types) |
-
-#### Message Reaction Remove
-
-Sent when a user removes a reaction from a message.
-
-###### Message Reaction Remove Event Fields
-
-| Field | Type | Description |
-|------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------|
-| user_id | snowflake | ID of the user |
-| channel_id | snowflake | ID of the channel |
-| message_id | snowflake | ID of the message |
-| guild_id? | snowflake | ID of the guild |
-| emoji | a partial [emoji](/docs/resources/emoji#emoji-object) object | Emoji used to react - [example](/docs/resources/emoji#emoji-object-standard-emoji-example) |
-| burst | boolean | true if this was a super-reaction |
-| type | integer | The [type of reaction](/docs/resources/message#get-reactions-reaction-types) |
-
-#### Message Reaction Remove All
-
-Sent when a user explicitly removes all reactions from a message.
-
-###### Message Reaction Remove All Event Fields
-
-| Field | Type | Description |
-|------------|-----------|-------------------|
-| channel_id | snowflake | ID of the channel |
-| message_id | snowflake | ID of the message |
-| guild_id? | snowflake | ID of the guild |
-
-#### Message Reaction Remove Emoji
-
-Sent when a bot removes all instances of a given emoji from the reactions of a message.
-
-###### Message Reaction Remove Emoji Event Fields
-
-| Field | Type | Description |
-|------------|------------------------------------------------------------|------------------------|
-| channel_id | snowflake | ID of the channel |
-| guild_id? | snowflake | ID of the guild |
-| message_id | snowflake | ID of the message |
-| emoji | [partial emoji object](/docs/resources/emoji#emoji-object) | Emoji that was removed |
-
-### Presence
-
-#### Presence Update
-
-:::warn
-If you are using [Gateway Intents](/docs/events/gateway#gateway-intents), you _must_ specify the `GUILD_PRESENCES` intent in order to receive Presence Update events
-:::
-
-A user's presence is their current state on a guild. This event is sent when a user's presence or info, such as name or avatar, is updated.
-
-:::warn
-The user object within this event can be partial, the only field which must be sent is the `id` field, everything else is optional. Along with this limitation, no fields are required, and the types of the fields are **not** validated. Your client should expect any combination of fields and types within this event.
-:::
-
-###### Presence Update Event Fields
-
-| Field | Type | Description |
-|---------------|--------------------------------------------------------------------------|----------------------------------------------|
-| user | [user](/docs/resources/user#user-object) object | User whose presence is being updated |
-| guild_id | snowflake | ID of the guild |
-| status | string | Either "idle", "dnd", "online", or "offline" |
-| activities | array of [activity](/docs/events/gateway-events#activity-object) objects | User's current activities |
-| client_status | [client_status](/docs/events/gateway-events#client-status-object) object | User's platform-dependent status |
-
-#### Client Status Object
-
-Active sessions are indicated with an "online", "idle", or "dnd" string per platform. If a user is offline or invisible, the corresponding field is not present.
-
-| Field | Type | Description |
-|----------|--------|-----------------------------------------------------------------------------------|
-| desktop? | string | User's status set for an active desktop (Windows, Linux, Mac) application session |
-| mobile? | string | User's status set for an active mobile (iOS, Android) application session |
-| web? | string | User's status set for an active web (browser, bot user) application session |
-
-#### Activity Object
-
-###### Activity Structure
-
-| Field | Type | Description |
-|----------------------|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| name | string | Activity's name |
-| type | integer | [Activity type](/docs/events/gateway-events#activity-object-activity-types) |
-| url? | ?string | Stream URL, is validated when type is 1 |
-| created_at | integer | Unix timestamp (in milliseconds) of when the activity was added to the user's session |
-| timestamps? | [timestamps](/docs/events/gateway-events#activity-object-activity-timestamps) object | Unix timestamps for start and/or end of the game |
-| application_id? | snowflake | Application ID for the game |
-| status_display_type? | ?integer | [Status display type](/docs/events/gateway-events#activity-object-status-display-types); controls which field is displayed in the user's status text in the member list |
-| details? | ?string | What the player is currently doing |
-| details_url? | ?string | URL that is linked when clicking on the details text |
-| state? | ?string | User's current party status, or text used for a custom status |
-| state_url? | ?string | URL that is linked when clicking on the state text |
-| emoji? | ?[emoji](/docs/events/gateway-events#activity-object-activity-emoji) object | Emoji used for a custom status |
-| party? | [party](/docs/events/gateway-events#activity-object-activity-party) object | Information for the current party of the player |
-| assets? | [assets](/docs/events/gateway-events#activity-object-activity-assets) object | Images for the presence and their hover texts |
-| secrets? | [secrets](/docs/events/gateway-events#activity-object-activity-secrets) object | Secrets for Rich Presence joining and spectating |
-| instance? | boolean | Whether or not the activity is an instanced game session |
-| flags? | integer | [Activity flags](/docs/events/gateway-events#activity-object-activity-flags) `OR`d together, describes what the payload includes |
-| buttons? | array of [buttons](/docs/events/gateway-events#activity-object-activity-buttons) | Custom buttons shown in the Rich Presence (max 2) |
-
-:::info
-Bot users are only able to set `name`, `state`, `type`, and `url`.
-:::
-
-###### Activity Types
-
-| ID | Name | Format | Example |
-|----|-----------|-----------------------|--------------------------------------|
-| 0 | Playing | Playing `{name}` | "Playing Rocket League" |
-| 1 | Streaming | Streaming `{details}` | "Streaming Rocket League" |
-| 2 | Listening | Listening to `{name}` | "Listening to Spotify" |
-| 3 | Watching | Watching `{name}` | "Watching YouTube Together" |
-| 4 | Custom | `{emoji}` `{state}` | ":smiley: I am cool" |
-| 5 | Competing | Competing in `{name}` | "Competing in Arena World Champions" |
-
-:::info
-The streaming type currently only supports Twitch and YouTube. Only `https://twitch.tv/` and `https://youtube.com/` urls will work.
-:::
-
-###### Status Display Types
-
-| ID | Name | Example |
-|----|---------|----------------------------------------|
-| 0 | Name | "Listening to Spotify" |
-| 1 | State | "Listening to Rick Astley" |
-| 2 | Details | "Listening to Never Gonna Give You Up" |
-
-:::info
-This applies to all activity types. "Listening" was used to serve as a consistent example of what the different fields might be used for.
-:::
-
-###### Activity Timestamps
-
-| Field | Type | Description |
-|--------|---------|----------------------------------------------------------|
-| start? | integer | Unix time (in milliseconds) of when the activity started |
-| end? | integer | Unix time (in milliseconds) of when the activity ends |
-
-:::info
-For Listening and Watching activities, you can include both start and end timestamps to display a time bar.
-:::
-
-###### Activity Emoji
-
-| Field | Type | Description |
-|-----------|-----------|-------------------------------|
-| name | string | Name of the emoji |
-| id? | snowflake | ID of the emoji |
-| animated? | boolean | Whether the emoji is animated |
-
-###### Activity Party
-
-| Field | Type | Description |
-|-------|------------------------------------------------|---------------------------------------------------|
-| id? | string | ID of the party |
-| size? | array of two integers (current_size, max_size) | Used to show the party's current and maximum size |
-
-###### Activity Assets
-
-| Field | Type | Description |
-|---------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| large_image? | string | See [Activity Asset Image](/docs/events/gateway-events#activity-object-activity-asset-image) |
-| large_text? | string | Text displayed when hovering over the large image of the activity |
-| large_url? | string | URL that is opened when clicking on the large image |
-| small_image? | string | See [Activity Asset Image](/docs/events/gateway-events#activity-object-activity-asset-image) |
-| small_text? | string | Text displayed when hovering over the small image of the activity |
-| small_url? | string | URL that is opened when clicking on the small image |
-| invite_cover_image? | string | See [Activity Asset Image](/docs/events/gateway-events#activity-object-activity-asset-image). Displayed as a banner on a [Game Invite](/docs/discord-social-sdk/development-guides/managing-game-invites). |
-
-###### Activity Asset Image
-
-Activity asset images are arbitrary strings which usually contain snowflake IDs or prefixed image IDs. Treat data within this field carefully, as it is user-specifiable and not sanitized.
-
-To use an external image via media proxy, specify the URL as the field's value when sending. You will only receive the `mp:` prefix via the gateway.
-
-| Type | Format | Image URL |
-|-------------------|--------------------------|----------------------------------------------------------------------------|
-| Application Asset | `{application_asset_id}` | See [Application Asset Image Formatting](/docs/reference#image-formatting) |
-| Media Proxy Image | `mp:{image_id}` | `https://media.discordapp.net/{image_id}` |
-
-###### Activity Secrets
-
-| Field | Type | Description |
-|-----------|--------|---------------------------------------|
-| join? | string | Secret for joining a party |
-| spectate? | string | Secret for spectating a game |
-| match? | string | Secret for a specific instanced match |
-
-###### Activity Flags
-
-| Name | Value |
-|-----------------------------|----------|
-| INSTANCE | `1 << 0` |
-| JOIN | `1 << 1` |
-| SPECTATE | `1 << 2` |
-| JOIN_REQUEST | `1 << 3` |
-| SYNC | `1 << 4` |
-| PLAY | `1 << 5` |
-| PARTY_PRIVACY_FRIENDS | `1 << 6` |
-| PARTY_PRIVACY_VOICE_CHANNEL | `1 << 7` |
-| EMBEDDED | `1 << 8` |
-
-###### Activity Buttons
-
-When received over the gateway, the `buttons` field is an array of strings, which are the button labels. Bots cannot access a user's activity button URLs. When sending, the `buttons` field must be an array of the below object:
-
-| Field | Type | Description |
-|-------|--------|--------------------------------------------------------|
-| label | string | Text shown on the button (1-32 characters) |
-| url | string | URL opened when clicking the button (1-512 characters) |
-
-###### Example Activity
-
-```json
-{
- "details": "24H RL Stream for Charity",
- "state": "Rocket League",
- "name": "Twitch",
- "type": 1,
- "url": "https://www.twitch.tv/discord"
-}
-```
-
-###### Example Activity with Rich Presence
-
-```json
-{
- "name": "Rocket League",
- "type": 0,
- "application_id": "379286085710381999",
- "state": "In a Match",
- "details": "Ranked Duos: 2-1",
- "timestamps": {
- "start": 15112000660000
- },
- "party": {
- "id": "9dd6594e-81b3-49f6-a6b5-a679e6a060d3",
- "size": [2, 2]
- },
- "assets": {
- "large_image": "351371005538729000",
- "large_text": "DFH Stadium",
- "small_image": "351371005538729111",
- "small_text": "Silver III"
- },
- "secrets": {
- "join": "025ed05c71f639de8bfaa0d679d7c94b2fdce12f",
- "spectate": "e7eb30d2ee025ed05c71ea495f770b76454ee4e0",
- "match": "4b2fdce12f639de8bfa7e3591b71a0d679d7c93f"
- }
-}
-```
-
-:::warn
-Clients may only update their game status 5 times per 20 seconds.
-:::
-
-#### Typing Start
-
-Sent when a user starts typing in a channel.
-
-###### Typing Start Event Fields
-
-| Field | Type | Description |
-|------------|------------------------------------------------------------|--------------------------------------------------------|
-| channel_id | snowflake | ID of the channel |
-| guild_id? | snowflake | ID of the guild |
-| user_id | snowflake | ID of the user |
-| timestamp | integer | Unix time (in seconds) of when the user started typing |
-| member? | [member](/docs/resources/guild#guild-member-object) object | Member who started typing if this happened in a guild |
-
-#### User Update
-
-Sent when properties about the current bot's user change. Inner payload is a [user](/docs/resources/user#user-object) object.
-
-### Voice
-
-#### Voice Channel Effect Send
-
-Sent when someone sends an effect, such as an emoji reaction or a soundboard sound, in a voice channel the current user is connected to.
-
-###### Voice Channel Effect Send Event Fields
-
-| Field | Type | Description |
-|-----------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
-| channel_id | snowflake | ID of the channel the effect was sent in |
-| guild_id | snowflake | ID of the guild the effect was sent in |
-| user_id | snowflake | ID of the user who sent the effect |
-| emoji? | ?[emoji](/docs/resources/emoji#emoji-object) object | The emoji sent, for emoji reaction and soundboard effects |
-| animation_type? | ?integer | The [type of emoji animation](/docs/events/gateway-events#voice-channel-effect-send-animation-types), for emoji reaction and soundboard effects |
-| animation_id? | integer | The ID of the emoji animation, for emoji reaction and soundboard effects |
-| sound_id? | snowflake or integer | The ID of the soundboard sound, for soundboard effects |
-| sound_volume? | double | The volume of the soundboard sound, from 0 to 1, for soundboard effects |
-
-###### Animation Types
-
-| Type | Value | Description |
-|---------|-------|---------------------------------------------|
-| PREMIUM | 0 | A fun animation, sent by a Nitro subscriber |
-| BASIC | 1 | The standard animation |
-
-#### Voice State Update
-
-Sent when someone joins/leaves/moves voice channels. Inner payload is a [voice state](/docs/resources/voice#voice-state-object) object.
-
-#### Voice Server Update
-
-Sent when a guild's voice server is updated. This is sent when initially connecting to voice, and when the current voice instance fails over to a new server.
-
-:::warn
-A null endpoint means that the voice server allocated has gone away and is trying to be reallocated. You should attempt to disconnect from the currently connected voice server, and not attempt to reconnect until a new voice server is allocated.
-:::
-
-###### Voice Server Update Event Fields
-
-| Field | Type | Description |
-|----------|-----------|---------------------------------------|
-| token | string | Voice connection token |
-| guild_id | snowflake | Guild this voice server update is for |
-| endpoint | ?string | Voice server host |
-
-###### Example Voice Server Update Payload
-
-```json
-{
- "token": "my_token",
- "guild_id": "41771983423143937",
- "endpoint": "sweetwater-12345.discord.media:2048"
-}
-```
-
-### Webhooks
-
-#### Webhooks Update
-
-Sent when a guild channel's webhook is created, updated, or deleted.
-
-###### Webhooks Update Event Fields
-
-| Field | Type | Description |
-|------------|-----------|-------------------|
-| guild_id | snowflake | ID of the guild |
-| channel_id | snowflake | ID of the channel |
-
-### Interactions
-
-#### Interaction Create
-
-Sent when a user uses an [Application Command](/docs/interactions/application-commands) or [Message Component](/docs/components/reference#component-object). Inner payload is an [Interaction](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure).
-
-### Stage Instances
-
-#### Stage Instance Create
-
-Sent when a [Stage instance](/docs/resources/stage-instance) is created (i.e. the Stage is now "live"). Inner payload is a [Stage instance](/docs/resources/stage-instance#stage-instance-object)
-
-#### Stage Instance Update
-
-Sent when a [Stage instance](/docs/resources/stage-instance) has been updated. Inner payload is a [Stage instance](/docs/resources/stage-instance#stage-instance-object)
-
-#### Stage Instance Delete
-
-Sent when a [Stage instance](/docs/resources/stage-instance) has been deleted (i.e. the Stage has been closed). Inner payload is a [Stage instance](/docs/resources/stage-instance#stage-instance-object)
-
-### Subscriptions
-
-#### Subscription Create
-
-:::info
-Subscription status should not be used to grant perks. Use [entitlements](/docs/resources/entitlement#entitlement-object) as an indication of whether a user should have access to a specific SKU. See our guide on [Implementing App Subscriptions](/docs/monetization/implementing-app-subscriptions) for more information.
-:::
-
-Sent when a [Subscription](/docs/resources/subscription) for a Premium App is created. Inner payload is a [Subscription](/docs/resources/subscription#subscription-object).
-
-A Subscription's `status` can be either **inactive** or **active** when this event is received. You will receive subsequent `SUBSCRIPTION_UPDATE` events if the `status` is updated to **active**. As a best practice, you should not grant any perks to users until the entitlements are created.
-
-#### Subscription Update
-
-Sent when a [Subscription](/docs/resources/subscription) for a Premium App has been updated. Inner payload is a [Subscription](/docs/resources/subscription#subscription-object) object.
-
-#### Subscription Delete
-
-Sent when a [Subscription](/docs/resources/subscription) for a Premium App has been deleted. Inner payload is a [Subscription](/docs/resources/subscription#subscription-object) object.
-
-### Polls
-
-#### Message Poll Vote Add
-
-Sent when a user votes on a poll. If the poll allows multiple selection, one event will be sent per answer.
-
-###### Message Poll Vote Add Fields
-
-| Field | Type | Description |
-|------------|-----------|-------------------|
-| user_id | snowflake | ID of the user |
-| channel_id | snowflake | ID of the channel |
-| message_id | snowflake | ID of the message |
-| guild_id? | snowflake | ID of the guild |
-| answer_id | integer | ID of the answer |
-
-#### Message Poll Vote Remove
-
-Sent when a user removes their vote on a poll. If the poll allows for multiple selections, one event will be sent per answer.
-
-###### Message Poll Vote Remove Fields
-
-| Field | Type | Description |
-|------------|-----------|-------------------|
-| user_id | snowflake | ID of the user |
-| channel_id | snowflake | ID of the channel |
-| message_id | snowflake | ID of the message |
-| guild_id? | snowflake | ID of the guild |
-| answer_id | integer | ID of the answer |
-
-### Rate Limits
-
-#### Rate Limited
-
-Sent when an app encounters a gateway rate limit for an event, such as [Request Guild Members](/docs/events/gateway-events#request-guild-members).
-
-:::info
-See changelog for [Introducing Rate Limit When Requesting All Guild Members](/docs/change-log#introducing-rate-limit-when-requesting-all-guild-members) for more information and timeline on this new rate limit.
-:::
-
-###### Rate Limited Fields
-
-| Field | Type | Description |
-|-------------|---------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
-| opcode | integer | [Gateway opcode](/docs/topics/opcodes-and-status-codes#gateway-gateway-opcodes) of the event that was rate limited |
-| retry_after | float | The number of seconds to wait before submitting another request |
-| meta | [Rate Limit Metadata for Opcode](/docs/events/gateway-events#rate-limited-rate-limit-metadata-for-opcode-structure) | Metadata for the event that was rate limited |
-
-###### Rate Limit Metadata for Opcode Structure
-
-| Opcode | Type |
-|--------|-----------------------------------------------------------------------------------------------------------------------------------------|
-| 8 | [Request Guild Member Rate Limit Metadata](/docs/events/gateway-events#rate-limited-request-guild-member-rate-limit-metadata-structure) |
-
-###### Request Guild Member Rate Limit Metadata Structure
-
-| Field | Type | Description |
-|----------|-----------|-------------------------------------------------------------------------------------------------------|
-| guild_id | snowflake | ID of the guild to get members for |
-| nonce? | string | nonce to identify the [Guild Members Chunk](/docs/events/gateway-events#guild-members-chunk) response |
diff --git a/docs/events/overview.mdx b/docs/events/overview.mdx
deleted file mode 100644
index c18bd6c004..0000000000
--- a/docs/events/overview.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-sidebar_label: Overview
----
-
-# Overview of Events
-
-Apps can listen to events happening in Discord to stay up-to-date with changes and updates to servers, users, and even your app. The following sections cover basic information about the different transport methods that can be used to receive events, and link out to relevant documentation.
-
-## Receiving Events
-
-There are many event types that can be accessed using different transport methods:
-- **[Gateway events](/docs/events/overview#using-gateway)** are sent over a WebSocket connection between your app and Discord, and is the primary way to receive and send events. **Most events are only available via Gateway connections.**
-- **[Webhook events](/docs/events/overview#using-webhooks)** are sent to your app's Webhook Event URL over HTTP.
-- **[SDK events](/docs/events/overview#using-the-embedded-app-sdk)** are sent to your app when using the Embedded App SDK.
-
-Read details about each way to receive events in the sections below.
-
-### Using Gateway
-
-Gateway events are the primary way apps can listen and send events. Most events related to resources in Discord, like updates to channels, guilds, roles, and messages, are only available over [Gateway](/docs/events/gateway).
-
-Gateway events are sent over a WebSocket-based [Gateway connection](/docs/events/gateway#connections) between Discord and your app. To receive Gateway events, your app must open and maintain a persistent Gateway connection which you can read details about in the [Gateway documentation](/docs/events/gateway#connections). To make receiving Gateway events simpler, we suggest using a [developer library](/docs/developer-tools/community-resources#libraries) which helps setup, maintain, and handle common pitfalls with Gateway connections (like [rate limits](/docs/events/gateway#rate-limiting)).
-
-Details about receiving events using the Gateway API is in the [Gateway documentation](/docs/events/gateway#receiving-events), and the full list of available Gateway events is in the [Gateway Events documentation](/docs/events/gateway-events).
-
-### Using Webhooks
-
-Webhook events let you receive a small number of events over HTTP. While many events aren't supported over HTTP, some events like [Application Authorized](/docs/events/webhook-events#application-authorized) (sent when your app is installed to a user or server) aren't available using other transport methods like Gateway.
-
-Find the [list of webhook events](/docs/events/webhook-events#event-types) and details about subscribing and handling them in the [Webhook Events documentation](/docs/events/webhook-events).
-
-
-### Using the Embedded App SDK
-
-When developing [Activities](/docs/activities/overview), you can listen to a collection of [SDK events](/docs/developer-tools/embedded-app-sdk#sdk-events), like updates to a user's voice status or screen orientation. To listen to SDK events, you can call [`subscribe()`](/docs/developer-tools/embedded-app-sdk#subscribe) with the SDK event name.
-
-Details about listening to events using the Embedded App SDK is in the [Embedded App SDK documentation](/docs/developer-tools/embedded-app-sdk).
-
-## Next Steps
-
-
-
- Gateway is the primary apps receive events on Discord. Read details about using the Gateway and receiving Gateway Events.
-
-
- Read details about receiving and responding a small number of HTTP-based Webhook Events.
-
-
- Read details about subscribing and receiving events specific to your Activity using the Embedded App SDK.
-
-
-
-
diff --git a/docs/interactions/receiving-and-responding.mdx b/docs/interactions/receiving-and-responding.mdx
deleted file mode 100644
index d76d8427a8..0000000000
--- a/docs/interactions/receiving-and-responding.mdx
+++ /dev/null
@@ -1,464 +0,0 @@
----
-sidebar_label: Receiving and Responding
----
-
-# Interactions
-
-An **[Interaction](/docs/interactions/receiving-and-responding#interaction-object)** is the message that your application receives when a user uses an application command or a message component.
-
-For [Slash Commands](/docs/interactions/application-commands#slash-commands), it includes the values that the user submitted.
-
-For [User Commands](/docs/interactions/application-commands#user-commands) and [Message Commands](/docs/interactions/application-commands#message-commands), it includes the resolved user or message on which the action was taken.
-
-For [Message Components](/docs/components/reference) it includes identifying information about the component that was used. It will also include some metadata about how the interaction was triggered: the `guild_id`, `channel`, `member` and other fields. You can find all the values in our data models below.
-
-### Interaction Object
-
-###### Interaction Structure
-
-| Field | Type | Description |
-|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| id | snowflake | ID of the interaction |
-| application_id | snowflake | ID of the application this interaction is for |
-| type | [interaction type](/docs/interactions/receiving-and-responding#interaction-object-interaction-type) | Type of interaction |
-| data?\* | [interaction data](/docs/interactions/receiving-and-responding#interaction-object-interaction-data) | Interaction data payload |
-| guild? | [partial guild](/docs/resources/guild#guild-object) object | Guild that the interaction was sent from |
-| guild_id? | snowflake | Guild that the interaction was sent from |
-| channel? | [partial channel](/docs/resources/channel#channel-object) object | Channel that the interaction was sent from |
-| channel_id? | snowflake | Channel that the interaction was sent from |
-| member?\*\* | [guild member](/docs/resources/guild#guild-member-object) object | Guild member data for the invoking user, including permissions |
-| user? | [user](/docs/resources/user#user-object) object | User object for the invoking user, if invoked in a DM |
-| token | string | Continuation token for responding to the interaction |
-| version | integer | Read-only property, always `1` |
-| message? | [message](/docs/resources/message#message-object) object | For components or modals triggered by components, the message they were attached to |
-| app_permissions\*\*\* | string | Bitwise set of permissions the app has in the source location of the interaction |
-| locale?\*\*\*\* | string | Selected [language](/docs/reference#locales) of the invoking user |
-| guild_locale? | string | [Guild's preferred locale](/docs/resources/guild#guild-object), if invoked in a guild |
-| entitlements | array of [entitlement](/docs/resources/entitlement#entitlement-object) objects | For [monetized apps](/docs/monetization/overview), any entitlements for the invoking user, representing access to premium [SKUs](/docs/resources/sku) |
-| authorizing_integration_owners | dictionary with keys of [application integration types](/docs/resources/application#application-object-application-integration-types) | Mapping of installation contexts that the interaction was authorized for to related user or guild IDs. See [Authorizing Integration Owners Object](/docs/interactions/receiving-and-responding#interaction-object-authorizing-integration-owners-object) for details |
-| context? | [interaction context type](/docs/interactions/receiving-and-responding#interaction-object-interaction-context-types) | Context where the interaction was triggered from |
-| attachment_size_limit | integer | Attachment size limit in bytes |
-
-\* This is always present on application command, message component, and modal submit interaction types. It is optional for future-proofing against new interaction types
-
-\*\* `member` is sent when the interaction is invoked in a guild, and `user` is sent when invoked in a DM
-
-\*\*\* `app_permissions` includes `ATTACH_FILES | EMBED_LINKS | MENTION_EVERYONE` permissions for (G)DMs with other users, and additionally includes `USE_EXTERNAL_EMOJIS` for DMs with the app's bot user
-
-\*\*\*\* This is available on all interaction types except PING
-
-###### Interaction Type
-
-| Name | Value |
-|----------------------------------|-------|
-| PING | 1 |
-| APPLICATION_COMMAND | 2 |
-| MESSAGE_COMPONENT | 3 |
-| APPLICATION_COMMAND_AUTOCOMPLETE | 4 |
-| MODAL_SUBMIT | 5 |
-
-###### Interaction Context Types
-
-Context in Discord where an interaction can be used, or where it was triggered from. Details about using interaction contexts for application commands is in the [commands context documentation](/docs/interactions/application-commands#interaction-contexts).
-
-| Name | Type | Description |
-|-----------------|------|--------------------------------------------------------------------------------|
-| GUILD | 0 | Interaction can be used within servers |
-| BOT_DM | 1 | Interaction can be used within DMs with the app's bot user |
-| PRIVATE_CHANNEL | 2 | Interaction can be used within Group DMs and DMs other than the app's bot user |
-
-###### Authorizing Integration Owners Object
-
-The `authorizing_integration_owners` field includes details about the authorizing user or server for the installation(s) relevant to the interaction. For apps installed to a user, it can be used to tell the difference between the authorizing user and the user that triggered an interaction (like a message component).
-
-A key will only be present if the following are true:
-- The app has been authorized to the [installation context](/docs/resources/application#application-object-application-integration-types) corresponding to the key (`GUILD_INSTALL` or `USER_INSTALL`)
-- The interaction is supported in the source [interaction context](/docs/interactions/receiving-and-responding#interaction-object-interaction-context-types) (`GUILD`, `BOT_DM`, or `PRIVATE_CHANNEL`) for the installation context corresponding to the key
-- And for command invocations, the command must be supported in the installation context (using [`integration_types`](/docs/interactions/application-commands#contexts))
-
-The values in `authorizing_integration_owners` depend on the key—
-
-- If the key is `GUILD_INSTALL` (`"0"`), the value depends on the source of the interaction:
- - The value will be the guild ID if the interaction is triggered from a server
- - The value will be `"0"` if the interaction is triggered from a DM with the app's bot user
-- If the key is `USER_INSTALL` (`"1"`), the value will be the ID of the authorizing user
-
-###### Interaction Data
-
-While the `data` field is guaranteed to be present for all [interaction types](/docs/interactions/receiving-and-responding#interaction-object-interaction-type) besides `PING`, its structure will vary. The following tables detail the inner `data` payload for each interaction type.
-
-| Interaction Type | Interaction Data |
-|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
-| PING (`1`) | N / A |
-| APPLICATION_COMMAND (`2`) | [Application Command Data Structure](/docs/interactions/receiving-and-responding#interaction-object-application-command-data-structure) |
-| MESSAGE_COMPONENT (`3`) | [Message Component Data Structure](/docs/interactions/receiving-and-responding#interaction-object-message-component-data-structure) |
-| APPLICATION_COMMAND_AUTOCOMPLETE (`4`) | [Application Command Data Structure](/docs/interactions/receiving-and-responding#interaction-object-application-command-data-structure) |
-| MODAL_SUBMIT (`5`) | [Modal Submit Data Structure](/docs/interactions/receiving-and-responding#interaction-object-modal-submit-data-structure) |
-
-
-###### Application Command Data Structure
-
-:::info
-Sent in `APPLICATION_COMMAND` and `APPLICATION_COMMAND_AUTOCOMPLETE` interactions.
-:::
-
-| Field | Type | Description |
-|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| id | snowflake | [`ID`](/docs/interactions/application-commands#application-command-object-application-command-structure) of the invoked command |
-| name | string | [`name`](/docs/interactions/application-commands#application-command-object-application-command-structure) of the invoked command |
-| type | integer | [`type`](/docs/interactions/application-commands#application-command-object-application-command-structure) of the invoked command |
-| resolved? | [resolved data](/docs/interactions/receiving-and-responding#interaction-object-resolved-data-structure) | Converted users + roles + channels + attachments |
-| options?\* | array of [application command interaction data option](/docs/interactions/receiving-and-responding#interaction-object-application-command-interaction-data-option-structure) | Params + values from the user |
-| guild_id? | snowflake | ID of the guild the command is registered to |
-| target_id? | snowflake | ID of the user or message targeted by a [user](/docs/interactions/application-commands#user-commands) or [message](/docs/interactions/application-commands#message-commands) command |
-
-\* This [can be partial](/docs/interactions/application-commands#autocomplete) when in response to `APPLICATION_COMMAND_AUTOCOMPLETE`
-
-###### Message Component Data Structure
-
-| Field | Type | Description |
-|----------------|---------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|
-| custom_id | string | [`custom_id`](/docs/components/reference#anatomy-of-a-component-custom-id) of the component |
-| component_type | integer | [type](/docs/components/reference#component-object-component-types) of the component |
-| values?\* | array of [select option values](/docs/components/reference#string-select-select-option-structure) | Values the user selected in a [select menu](/docs/components/reference#string-select) component |
-| resolved? | [resolved data](/docs/interactions/receiving-and-responding#interaction-object-resolved-data-structure) | Resolved entities from selected options |
-
-\* This is always present for select menu components
-
-###### Modal Submit Data Structure
-
-| Field | Type | Description |
-|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|
-| custom_id | string | The custom ID provided for the modal |
-| components | array of [component interaction response](/docs/interactions/receiving-and-responding#interaction-object-component-interaction-response-structures) | Values submitted by the user |
-| resolved? | [resolved data](/docs/interactions/receiving-and-responding#interaction-object-resolved-data-structure) | Resolved entities from selected options |
-
-###### Component Interaction Response Structures
-
-| Component |
-|-----------------------------------------------------------------------------------------------------------------------|
-| [String Select](/docs/components/reference#string-select-string-select-interaction-response-structure) |
-| [Text Input](/docs/components/reference#text-input-text-input-interaction-response-structure) |
-| [User Select](/docs/components/reference#user-select-user-select-interaction-response-structure) |
-| [Role Select](/docs/components/reference#role-select-role-select-interaction-response-structure) |
-| [Mentionable Select](/docs/components/reference#mentionable-select-mentionable-select-interaction-response-structure) |
-| [Channel Select](/docs/components/reference#channel-select-channel-select-interaction-response-structure) |
-| [Text Display](/docs/components/reference#text-display-text-display-interaction-response-structure) |
-| [Label](/docs/components/reference#label-label-interaction-response-structure) |
-| [File Upload](/docs/components/reference#file-upload-file-upload-interaction-response-structure) |
-
-###### Resolved Data Structure
-
-:::info
-If data for a Member is included, data for its corresponding User will also be included.
-:::
-
-| Field | Type | Description |
-|---------------|------------------------------------------------------------------------------------------|---------------------------------|
-| users? | Map of Snowflakes to [user](/docs/resources/user#user-object) objects | IDs and User objects |
-| members?\* | Map of Snowflakes to [partial member](/docs/resources/guild#guild-member-object) objects | IDs and partial Member objects |
-| roles? | Map of Snowflakes to [role](/docs/topics/permissions#role-object) objects | IDs and Role objects |
-| channels?\*\* | Map of Snowflakes to [partial channel](/docs/resources/channel#channel-object) objects | IDs and partial Channel objects |
-| messages? | Map of Snowflakes to [partial messages](/docs/resources/message#message-object) objects | IDs and partial Message objects |
-| attachments? | Map of Snowflakes to [attachment](/docs/resources/message#attachment-object) objects | IDs and attachment objects |
-
-\* Partial `Member` objects are missing `user`, `deaf` and `mute` fields
-
-\*\* Partial `Channel` objects only have `id`, `name`, `type`, `permissions`, `last_message_id`, `last_pin_timestamp`, `nsfw`, `parent_id`, `guild_id`, `flags`, `rate_limit_per_user`, `topic` and `position` fields. Threads will also have the `thread_metadata` field.
-
-###### Application Command Interaction Data Option Structure
-
-All options have names, and an option can either be a parameter and input value--in which case `value` will be set--or it can denote a subcommand or group--in which case it will contain a top-level key and another array of `options`.
-
-`value` and `options` are mutually exclusive.
-
-| Field | Type | Description |
-|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
-| name | string | Name of the parameter |
-| type | integer | Value of [application command option type](/docs/interactions/application-commands#application-command-object-application-command-option-type) |
-| value? | string, integer, double, or boolean | Value of the option resulting from user input |
-| options? | array of [application command interaction data option](/docs/interactions/receiving-and-responding#interaction-object-application-command-interaction-data-option-structure) | Present if this option is a group or subcommand |
-| focused? | boolean | `true` if this option is the currently focused option for autocomplete |
-
-### Message Interaction Object
-
-This is sent on the [message object](/docs/resources/message#message-object) when the message is a response to an Interaction without an existing message.
-
-:::info
-This means responses to [Message Components](/docs/components/reference) do not include this property, instead including a [message reference](/docs/resources/message#message-reference-structure) object as components _always_ exist on preexisting messages.
-:::
-
-###### Message Interaction Structure
-
-| Field | Type | Description |
-|---------|-----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| id | snowflake | ID of the interaction |
-| type | [interaction type](/docs/interactions/receiving-and-responding#interaction-object-interaction-type) | Type of interaction |
-| name | string | Name of the [application command](/docs/interactions/application-commands#application-command-object-application-command-structure), including subcommands and subcommand groups |
-| user | [user object](/docs/resources/user#user-object) | User who invoked the interaction |
-| member? | [partial member](/docs/resources/guild#guild-member-object) object | Member who invoked the interaction in the guild |
-
-## Receiving an Interaction
-
-When a user interacts with your app, your app will receive an **[Interaction](/docs/interactions/receiving-and-responding#interaction-object)**. Your app can receive an interaction in one of two ways:
-
-- Via [Interaction Create](/docs/events/gateway-events#interaction-create) gateway event
-- Via outgoing webhook
-
-These two methods are **mutually exclusive**; you can _only_ receive Interactions one of the two ways. The `INTERACTION_CREATE` [Gateway Event](/docs/events/gateway-events#interaction-create) may be handled by connected clients, while the webhook method detailed below does not require a connected client.
-
-If you want to receive interactions via HTTP-based outgoing webhooks, you must configure an Interactions Endpoint URL for your app. You can read about preparing and adding an Interactions Endpoint URL to your app in the [Preparing for Interactions](/docs/interactions/overview#preparing-for-interactions) section in Interactions Overview.
-
-### Interaction Metadata
-
-An [Interaction](/docs/interactions/receiving-and-responding#interaction-object) includes metadata to aid your application in handling it as well as `data` specific to the interaction type. You can find samples for each interaction type on their respective pages:
-
-- [Slash Commands](/docs/interactions/application-commands#slash-commands-example-interaction)
-- [User Commands](/docs/interactions/application-commands#user-commands-example-interaction)
-- [Message Commands](/docs/interactions/application-commands#message-commands-example-interaction)
-- [Message Components](/docs/components/using-message-components)
-- [Modal Components](/docs/components/using-modal-components)
-
-An explanation of all the fields can be found in our [data models](/docs/interactions/receiving-and-responding#interaction-object).
-
-Now that you've gotten the data from the user, it's time to respond to them.
-
-## Responding to an Interaction
-
-Interactions--both receiving and responding--are webhooks under the hood. So responding to an Interaction is just like sending a webhook request!
-
-:::info
-Interaction responses have the same header requirements as normal HTTP API requests. See [here](/docs/reference#http-api) for further information.
-:::
-
-There are a number of ways you can respond to an interaction:
-
-### Interaction Response Object
-
-###### Interaction Response Structure
-
-| Field | Type | Description |
-|-------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|
-| type | [interaction callback type](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-type) | Type of response |
-| data? | [interaction callback data](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-data-structure) | An optional response message |
-
-###### Interaction Callback Type
-
-| Name | Value | Description |
-|-----------------------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| PONG | 1 | ACK a `Ping` |
-| CHANNEL_MESSAGE_WITH_SOURCE | 4 | Respond to an interaction with a message |
-| DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE | 5 | ACK an interaction and edit a response later, the user sees a loading state |
-| DEFERRED_UPDATE_MESSAGE\* | 6 | For components, ACK an interaction and edit the original message later; the user does not see a loading state |
-| UPDATE_MESSAGE\* | 7 | For components, edit the message the component was attached to |
-| APPLICATION_COMMAND_AUTOCOMPLETE_RESULT | 8 | Respond to an autocomplete interaction with suggested choices |
-| MODAL\*\* | 9 | Respond to an interaction with a popup modal |
-| PREMIUM_REQUIRED | 10 | [**Deprecated**](/docs/change-log#premium-apps-new-premium-button-style-deep-linking-url-schemes); respond to an interaction with an upgrade button, only available for apps with [monetization](/docs/monetization/overview) enabled |
-| LAUNCH_ACTIVITY | 12 | Launch the Activity associated with the app. Only available for apps with [Activities](/docs/activities/overview) enabled |
-
-\* Only valid for [component-based](/docs/components/reference) interactions
-
-\*\* Not available for `MODAL_SUBMIT` and `PING` interactions.
-
-###### Interaction Callback Data Structure
-
-###### Messages
-
-Not all message fields are currently supported.
-
-
-| Field | Type | Description |
-|-------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| tts? | boolean | Whether the response is TTS |
-| content? | string | Message content |
-| embeds? | array of [embeds](/docs/resources/message#embed-object) | Supports up to 10 embeds |
-| allowed_mentions? | [allowed mentions](/docs/resources/message#allowed-mentions-object) | [Allowed mentions](/docs/resources/message#allowed-mentions-object) object |
-| flags? \* | integer | [Message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (only `SUPPRESS_EMBEDS`, `EPHEMERAL`, `IS_COMPONENTS_V2`, `IS_VOICE_MESSAGE`, and `SUPPRESS_NOTIFICATIONS` can be set) |
-| components? | array of [components](/docs/components/reference#component-object) | Message components |
-| attachments? \*\* | array of partial [attachment](/docs/resources/message#attachment-object) objects | Attachment objects with filename and description |
-| poll? | [poll](/docs/resources/poll#poll-create-request-object) request object | Details about the poll |
-
-\* If you create a callback with the [type](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-type) `DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE` the only valid [message flag](/docs/resources/message#message-object-message-flags) you may use is `EPHEMERAL`. If you'd like to create a component based message with `IS_COMPONENTS_V2` you must do that with the [edit original response](/docs/interactions/receiving-and-responding#edit-original-interaction-response) endpoint, not this one.
-
-\*\* See [Uploading Files](/docs/reference#uploading-files) for details.
-
-###### Autocomplete
-
-| Field | Type | Description |
-|---------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|
-| choices | array of [choices](/docs/interactions/application-commands#application-command-object-application-command-option-choice-structure) | autocomplete choices (max of 25 choices) |
-
-###### Modal
-
-| Field | Type | Description |
-|------------|--------------------------------------------------------------------|----------------------------------------------------------------|
-| custom_id | string | Developer-defined identifier for the modal, max 100 characters |
-| title | string | Title of the popup modal, max 45 characters |
-| components | array of [components](/docs/components/reference#component-object) | Between 1 and 5 (inclusive) components that make up the modal |
-
-:::warn
-If your application responds with user data, you should use [`allowed_mentions`](/docs/resources/message#allowed-mentions-object) to filter which mentions in the content actually ping.
-:::
-
-## Interaction Callback
-
-When responding to an interaction received, you can make a `POST` request to `/interactions///callback`. `interaction_id` is the unique id of that individual Interaction from the received payload. `interaction_token` is the unique token for that interaction from the received payload.
-
-If you are receiving Interactions over the gateway, you **have to respond via HTTP**. Responses to Interactions **are not sent as commands over the gateway**.
-
-**If you send this request for an interaction received over HTTP, respond to the original HTTP request with a 202 and no body.**
-
-```py
-import requests
-
-url = "https://discord.com/api/v10/interactions///callback"
-
-json = {
- "type": 4,
- "data": {
- "content": "Congrats on sending your command!"
- }
-}
-r = requests.post(url, json=json)
-```
-
-:::info
-Interaction `tokens` are valid for **15 minutes** and can be used to send followup messages but you **must send an initial response within 3 seconds of receiving the event**. If the 3 second deadline is exceeded, the token will be invalidated.
-:::
-
-
- If you receive interactions over HTTP, your server can also respond to the received `POST` request. You'll want to respond with a `200` status code (if everything went well), as well as specifying a `type` and `data`, which is an [Interaction Response](/docs/interactions/receiving-and-responding#interaction-response-object) object:
-
- ```py
- @app.route('/', methods=['POST'])
- def my_command():
- if request.json["type"] == 1:
- return jsonify({
- "type": 1
- })
-
- else:
- return jsonify({
- "type": 4,
- "data": {
- "tts": False,
- "content": "Congrats on sending your command!",
- "embeds": [],
- "allowed_mentions": { "parse": [] }
- }
- })
- ```
-
-
-###### Interaction Callback Response Object
-
-| Field | Type | Description |
-|-------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|
-| interaction | [interaction callback object](/docs/interactions/receiving-and-responding#interaction-callback-interaction-callback-object) | The interaction object associated with the interaction response. |
-| resource? | [interaction resource object](/docs/interactions/receiving-and-responding#interaction-callback-interaction-callback-resource-object) | The resource that was created by the interaction response. |
-
-###### Interaction Callback Object
-
-| Field | Type | Description |
-|-----------------------------|-----------|-----------------------------------------------------------------------------------------------------|
-| id | snowflake | ID of the interaction |
-| type | integer | [Interaction type](/docs/interactions/receiving-and-responding#interaction-object-interaction-type) |
-| activity_instance_id? | string | Instance ID of the Activity if one was launched or joined |
-| response_message_id? | snowflake | ID of the message that was created by the interaction |
-| response_message_loading? | boolean | Whether the message is in a loading state |
-| response_message_ephemeral? | boolean | Whether the response message is ephemeral |
-
-###### Interaction Callback Resource Object
-
-| Field | Type | Description |
-|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|
-| type | integer | [Interaction callback type](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-type) |
-| activity_instance?\* | [Activity instance resource](/docs/interactions/receiving-and-responding#interaction-callback-interaction-callback-activity-instance-resource) | Represents the Activity launched by this interaction. |
-| message?\*\* | [message object](/docs/resources/message#message-object) | Message created by the interaction. |
-
-\* Only present if type is `LAUNCH_ACTIVITY`.
-
-\*\* Only present if type is either `CHANNEL_MESSAGE_WITH_SOURCE` or `UPDATE_MESSAGE`.
-
-###### Interaction Callback Activity Instance Resource
-
-| Field | Type | Description |
-|-------|--------|------------------------------------------------------------|
-| id | string | Instance ID of the Activity if one was launched or joined. |
-
-
-## Followup Messages
-
-Sometimes, you want to send followup messages to a user after responding to an interaction. Or, you may want to edit your original response. Whether you receive Interactions over the gateway or by outgoing webhook, you can use the following endpoints to edit your initial response or send followup messages:
-
-- [`PATCH /webhooks///messages/@original`](/docs/interactions/receiving-and-responding#edit-original-interaction-response) to edit your initial response to an Interaction
-- [`DELETE /webhooks///messages/@original`](/docs/interactions/receiving-and-responding#delete-original-interaction-response) to delete your initial response to an Interaction
-- [`POST /webhooks//`](/docs/interactions/receiving-and-responding#create-followup-message) to send a new followup message
-- [`PATCH /webhooks///messages/`](/docs/interactions/receiving-and-responding#edit-followup-message) to edit a message sent with that `token`
-
-:::info
-Interactions webhooks share the same rate limit properties as normal webhooks.
-:::
-
-Interaction tokens are valid for **15 minutes**, meaning you can respond to an interaction within that amount of time.
-
-### Endpoints
-
-:::info
-The endpoints below are not bound to the application's [Global Rate Limit](/docs/topics/rate-limits#global-rate-limit).
-:::
-
-## Create Interaction Response
-/interactions/[\{interaction.id\}](/docs/interactions/receiving-and-responding#interaction-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/callback
-
-Create a response to an Interaction. Body is an [interaction response](/docs/interactions/receiving-and-responding#interaction-response-object). Returns `204` unless `with_response` is set to `true` which returns `200` with the body as [interaction callback response](/docs/interactions/receiving-and-responding#interaction-callback-interaction-callback-response-object).
-
-This endpoint also supports file attachments similar to the webhook endpoints. Refer to [Uploading Files](/docs/reference#uploading-files) for details on uploading files and `multipart/form-data` requests.
-
-###### Query String Params
-
-| Field | Type | Description |
-|----------------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| with_response? | [boolean](/docs/reference#boolean-query-strings) | Whether to include an [interaction callback object](/docs/interactions/receiving-and-responding#interaction-callback-interaction-callback-response-object) as the response |
-
-
-## Get Original Interaction Response
-/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/@original
-
-Returns the initial Interaction response. Functions the same as [Get Webhook Message](/docs/resources/webhook#get-webhook-message).
-
-## Edit Original Interaction Response
-/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/@original
-
-Edits the initial Interaction response. Functions the same as [Edit Webhook Message](/docs/resources/webhook#edit-webhook-message).
-
-## Delete Original Interaction Response
-/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/@original
-
-Deletes the initial Interaction response. Returns `204 No Content` on success.
-
-## Create Followup Message
-/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)
-
-:::info
-Apps are limited to 5 followup messages per interaction if it was initiated from a user-installed app and isn't installed in the server (meaning the [authorizing integration owners object](/docs/interactions/receiving-and-responding#interaction-object-authorizing-integration-owners-object) only contains `USER_INSTALL`)
-:::
-
-Create a followup message for an Interaction. Functions the same as [Execute Webhook](/docs/resources/webhook#execute-webhook), but `wait` is always true. The `thread_id`, `avatar_url`, and `username` parameters are not supported when using this endpoint for interaction followups. You can use the `EPHEMERAL` [message flag](/docs/resources/message#message-object-message-flags) `1 << 6` (64) to send a message that only the user can see. You can also use the `IS_COMPONENTS_V2` [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (32768) to send a [component](/docs/components/reference)-based message.
-
-When using this endpoint directly after responding to an interaction with `DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE`, this endpoint will function as [Edit Original Interaction Response](/docs/interactions/receiving-and-responding#edit-original-interaction-response) for backwards compatibility. In this case, no new message will be created, and the loading message will be edited instead. The ephemeral flag will be ignored, and the value you provided in the initial defer response will be preserved, as an existing message's ephemeral state cannot be changed. This behavior is deprecated, and you should use the [Edit Original Interaction Response](/docs/interactions/receiving-and-responding#edit-original-interaction-response) endpoint in this case instead.
-
-## Get Followup Message
-/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/[\{message.id\}](/docs/resources/message#message-object)
-
-Returns a followup message for an Interaction. Functions the same as [Get Webhook Message](/docs/resources/webhook#get-webhook-message).
-
-## Edit Followup Message
-/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/[\{message.id\}](/docs/resources/message#message-object)
-
-Edits a followup message for an Interaction. Functions the same as [Edit Webhook Message](/docs/resources/webhook#edit-webhook-message).
-
-## Delete Followup Message
-/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/[\{message.id\}](/docs/resources/message#message-object)
-
-Deletes a followup message for an Interaction. Returns `204 No Content` on success.
diff --git a/docs/intro.mdx b/docs/intro.mdx
deleted file mode 100644
index 815df361e3..0000000000
--- a/docs/intro.mdx
+++ /dev/null
@@ -1,87 +0,0 @@
----
-showTOC: false
-sidebar_label: Intro
-title: Intro
----
-
-
-
- Develop apps, bots, and integrations to enhance the Discord experience.
-
-
- Build multiplayer games and social experiences that run directly in Discord.
-
-
- Add rich social features into your game across desktop, mobile, and console.
-
-
-
-## Apps: Extend Discord with Custom Integrations
-
-Enhance the Discord experience with custom apps, commands, and integrations.
-
-
-
- Learn the fundamentals of building Discord apps and commands.
-
-
- Create a bot user that plays "rock, paper, scissors" with users.
-
-
- Create custom commands and interactions for your app.
-
-
-
-## Activities: Build Multiplayer Games in Discord
-
-Use the Embedded App SDK to create real-time games and social experiences that users can launch directly inside Discord.
-
-
-
- Discover how Activities work in Discord.
-
-
- Build and test an Activity using the Embedded App SDK.
-
-
- Best practices for multiplayer, game design, and player experience.
-
-
-
-## Discord Social SDK: Bring Social Features to Your Game
-
-Enable rich presence, voice chat, and more to create a seamless social experience for your players and grow your game.
-
-
-
- Explore rich presence, relationships, voice chat, and more.
-
-
- Start here for a step-by-step guide to adding social features to your game.
-
-
- Best practices for integrating Discord Social SDK features into your game.
-
-
-
-## Find Support
-
-Connect with the developer community, report issues, and stay updated with API changes.
-
-
-
- Get support, API announcements, and participate in developer events.
-
-
- Submit API bugs, feature requests, or contribute to the documentation.
-
-
- Find articles, FAQs, and reach out to Discord's developer support team.
-
-
diff --git a/docs/policies-and-agreements/developer-policy.md b/docs/policies-and-agreements/developer-policy.md
deleted file mode 100644
index 25da6ab0ac..0000000000
--- a/docs/policies-and-agreements/developer-policy.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-sidebar_label: Developer Policy
----
-
-# Discord Developer Policy
-
-:::info
-We’re updating our Developer Terms of Service and Developer Policy, effective July 8, 2024. Please review the updated Policy below and Terms [here](/docs/policies-and-agreements/developer-terms-of-service). If you access or use the APIs on or after July 8, 2024, it means you agree to the updated Policy and Terms. Until then, the current [Developer Terms of Service](https://github.com/discord/discord-api-docs/blob/e5cd463cd1412df2e55fce8ecb81e7d1ed5755b0/docs/policies_and_agreements/Developer_Terms_of_Service.md) and [Developer Policy](https://github.com/discord/discord-api-docs/blob/e5cd463cd1412df2e55fce8ecb81e7d1ed5755b0/docs/policies_and_agreements/Developer_Policy.md) will apply.
-:::
-
-## Effective date: July 8, 2024
-
-## Last updated: June 6, 2024
-
-*For a link to the previous policy, please see **[here](https://github.com/discord/discord-api-docs/blob/e5cd463cd1412df2e55fce8ecb81e7d1ed5755b0/docs/policies_and_agreements/Developer_Policy.md)**. For a translated version in your selected language, as available, please see **[here](https://support-dev.discord.com/hc/articles/8563934450327)**.*
-
-Discord is a place where developers can come to build cool experiences to further the way that people connect. As Discord continues to grow and support our developers, it’s important to be transparent about the responsibilities and our expectations of developers and their Applications. This document sets forth the rules developers will need to follow to develop and operate their Applications.
-
-## Introduction
-
-This Discord Developer Policy is incorporated into the [Discord Developer Terms of Service](/docs/policies-and-agreements/developer-terms-of-service) (“Developer Terms”), and you agree that it applies to your access to and use of our APIs in addition to the Developer Terms and other Terms. Capitalized terms not otherwise defined herein (including “API Data” and “Application”) have the meaning assigned to them in the Developer Terms. For clarity, the term “including” as used herein means “including without limitation.”
-
-As described in the Developer Terms (including Section 9), we may take enforcement actions for any Enforcement Reason, including if we believe you or your Application have violated this Developer Policy. If you come across an Application that you believe violates any of these policies, [please report it to us](https://support.discord.com/hc/en-us/requests/new).
-
-Please check back here regularly, as we may update these policies from time to time, and your continued access to or use of the APIs after such updates go into effect means you accept and agree to them. Additional terms and policies may also apply to your access to or use of certain APIs (including as described in or available via our [Developer Portal](/docs/intro) or [Help Center](https://support-dev.discord.com/hc/en-us/categories/360000656491)).
-
-## Monetization Requirements
-
-All Applications attempting to monetize through our services must abide by Discord’s [Monetization Terms](https://support.discord.com/hc/en-us/articles/5330075836311) and [Monetization Policy](https://support.discord.com/hc/en-us/articles/10575066024983).
-
-Beginning on October 7, 2024, in regions where Discord supports monetization through its Premium Apps products, all developers who offer paid features or capabilities for their Application will be required to:
-
-- (i) support purchase of such features or capabilities through Discord’s Premium Apps products; and,
-- (ii) offer such features or capabilities at prices on Discord that are no higher than the prices at which they are offered through other payment options.
-
-“Paid features or capabilities” can include things like subscriptions to your Application, access to certain features or content, one-time purchases, recurring subscriptions, and more. Only paid features or capabilities that are offerings supported by Discord’s Premium Apps products will be subject to these requirements. As new types of offerings are supported via Discord’s Premium Apps products, developers will be given a reasonable period of time to implement them into their Application, if applicable.
-
-## Protect Discord users
-
-**1. Do not modify a Discord user’s account without explicit permission from the Discord user.** Functionality that intends to make any changes to a Discord account (e.g., adding the account to a server) must clearly and properly inform the Discord account owner of the changes and receive explicit permission to enact the changes.
-
-**2. Do not initiate processes on a user or server’s behalf without first obtaining their permission.** The manner of providing the option for permission must be clearly labeled and apparent, and contain an accurate description of the purpose or feature being enabled.
-
-**3. Do not enable your Application to bypass or circumvent Discord’s privacy, safety, and/or security features.** Your Application must respect user decisions to opt out of or block the Application, as applicable. Your Application must respect users’ ability to remove the Application from spaces (e.g., servers or channels) where it is present.
-
-**4. Do not collect, solicit, or deceive users into providing passwords or other credentials.** Under no circumstances may you or your Application request or attempt to obtain login credentials from Discord users. This includes information such as passwords or account access or login tokens.
-
-**5. Do not contact users on Discord without their explicit permission.** This includes frequently sending unsolicited direct messages and/or sending direct messages not directly related to maintaining or improving an Application's functionality.
-
-**6. Do not target users with advertisements or marketing.** Messaging to Discord users from any Application or developer team should be relevant to the function of the Application and may not contain material unrelated to an Application’s function or information.
-
-**7. Do not contact users outside of Discord without their explicit permission.** You should not contact Discord users outside of the Discord platform using API Data (including any data obtained, disclosed, or inferred through the use of your Application).
-
-## Respect Our Platform Rules
-**8. Do not use the APIs for any dangerous or illegal activity.** This includes, but is not limited to, activities that facilitate or promote:
-
-- Risks to physical safety;
-- Environmental damage;
-- Financial scams; or,
-- Illegal online gambling.
-
-**9. Do not direct your Application to people who are under the age of 13 or the minimum age required by the laws in their applicable countries.** As described in our [Terms of Service](https://discord.com/terms#2), our services are only for people who are at least 13 years old and meet the minimum age required by the laws in their applicable countries.
-- Additionally, you will ensure your Application is properly rated based on its content (e.g., game ratings), as required by applicable laws or otherwise requested by Discord, and will display such ratings in a manner that is clear and visible to users prior to their authorization or use (e.g., in your Application's profile).
-
-**10. Do not use the APIs in any way to violate, or to enable or promote others to violate, the [Discord Community Guidelines](https://dis.gd/guidelines).** As described in the Developer Terms, you are responsible for ensuring that your Application is not used to violate any of the Terms. We will take into consideration the abundance, explicit negligence, and intentional enabling of violating behavior when assessing appropriate enforcement. Prohibited behaviors and activities include, but are not limited to, those that:
-- Enable the digital creation of illegal media (e.g., child-harm content, non-consensual pornography);
-- Distribute adult content to users under the age of 18, or without age-restricted labels (where applicable) to users ages 18 and older; or,
- - Unless your Application is labeled as age-restricted, you will make sure your Application is appropriate for users under the age of 18 and complies with all applicable laws (including those applicable to users under the age of 18).
-- Enable, promote, or organize any type of on- or off-platform harassment.
-
-**11. Do not display, post, or promote violent or violent extremist content, messages, or images.** This includes the fields in an Application’s Settings page in the Discord Developer Portal.
-
-**12. Do not impersonate other Applications, Discord employees or partners, or Discord services.** This includes deception via your and your Application’s account and identity. Note that we allow clearly labeled satire, parody, and fan accounts.
-
-**13. Do not misrepresent or fraudulently manipulate engagement.** This includes participating in, enabling, or promoting the inflation of server membership with bot or user accounts. This also includes automating messages to be sent for the purpose of maintaining activity in a Discord server.
-
-**14. Do not evade permanent Discord-level enforcement actions.** Developers of Applications removed for violating our Developer Policy may not recreate the same or substantially similar Applications.
-
-In addition to the rules above, developers must: (1.) provide users of their Application with a way to report issues or violations relating to the Application or its use (including violations of our platform rules and other Terms); and, (2.) review such reports and take appropriate action.
-
-Additionally, developers should use commercially reasonable efforts to make themselves available for feedback or user support regarding their Application.
-
-## Handle Data with Care
-
-**15. Do not use API Data for any purpose outside of what is necessary to provide your stated functionality.** You may not request, access, or use API Data for any purpose other than as necessary to provide your Application’s stated (and approved through App Review, as applicable) functionality; provided that you may also use API Data for the purpose of improving your Application only if it has been aggregated or de-identified such that it cannot be associated with, or used to identify, any individual.
-
-**16. Do not use API Data to:** profile Discord users, their identities, or their relationships with other users; to discriminate against anyone based on protected characteristics (as defined in our [Community Guidelines](https://dis.gd/guidelines)); or, for eligibility considerations for benefits or for purposes such as employment, housing, insurance, or otherwise.
-Furthermore, you may not, and may not use your Application to, obtain API Data or transmit data to Discord (i) of persons under the age of 13 or the minimum age required by law in their jurisdiction (if older) or (ii) that includes protected health information, financial information, or other sensitive information under applicable law, except to the extent specifically allowed by our Terms for a given Discord service or if necessary to process a financial transaction as enabled by a Discord service.
-
-**17. Do not disclose API Data to data brokers, advertising networks or services, or any other monetization-related service.**
-
-**18. Do not sell, license, or otherwise commercialize API Data or any of Discord’s services (as defined in our [Terms of Service](https://discord.com/terms), e.g., Nitro subscriptions).**
-
-**19. Do not attempt to re-identify, de-anonymize, unscramble, unencrypt, or reverse hash or reverse engineer API Data from the form in which you obtain it.**
-
-**20. Do not mine or scrape any data, content, or information available on or through Discord services (as defined in our Terms of Service).**
-
-**21. Do not use message content obtained through the APIs to train machine learning or AI models (including large language models) unless express permission is granted by Discord.**
-
-Note that we require developers to notify Discord and affected users of potential unauthorized access to API Data, as described in Section 5 of the Developer Terms.
-
-For the avoidance of doubt, the above policies apply in addition to the terms relating to API Data described in the Developer Terms (including Section 5 (User Privacy and Security)), and use of data includes how you access, collect, store, retain, transmit, share, and otherwise process it.
-
-## API Limits
-As described in the [Developer Terms](/docs/policies-and-agreements/developer-terms-of-service), Discord may set and enforce limits on your use of the APIs (e.g., by limiting the number of API requests that you may make, or the number of users you may serve) at our sole discretion. You agree to, and will not attempt to circumvent, such limitations we set for each API.
-
-If you would like to use any API beyond these limits, you must obtain Discord’s express written consent. Discord may, at our discretion, decline such request or condition acceptance on your agreement to additional terms and/or charges for such use.
diff --git a/docs/policies-and-agreements/developer-terms-of-service.md b/docs/policies-and-agreements/developer-terms-of-service.md
deleted file mode 100644
index 28928081e2..0000000000
--- a/docs/policies-and-agreements/developer-terms-of-service.md
+++ /dev/null
@@ -1,260 +0,0 @@
----
-sidebar_label: Developer Terms of Service
----
-
-# Discord Developer Terms of Service
-
-:::info
-We’re updating our Developer Terms of Service and Developer Policy, effective July 8, 2024. Please review the updated Terms below and Policy [here](/docs/policies-and-agreements/developer-policy). If you access or use the APIs on or after July 8, 2024, it means you agree to the updated Terms and Policy. Until then, the current [Developer Terms of Service](https://github.com/discord/discord-api-docs/blob/e5cd463cd1412df2e55fce8ecb81e7d1ed5755b0/docs/policies_and_agreements/Developer_Terms_of_Service.md) and [Developer Policy](https://github.com/discord/discord-api-docs/blob/e5cd463cd1412df2e55fce8ecb81e7d1ed5755b0/docs/policies_and_agreements/Developer_Policy.md) will apply.
-:::
-
-## Effective date: July 8, 2024
-
-## Last updated: June 6, 2024
-
-*For a link to the previous terms, please see **[here](https://github.com/discord/discord-api-docs/blob/e5cd463cd1412df2e55fce8ecb81e7d1ed5755b0/docs/policies_and_agreements/Developer_Policy.md)**. For a translated version in your selected language, as available, please see **[here](https://support-dev.discord.com/hc/articles/8562894815383)**.*
-
-Welcome! Thank you for your interest in Discord’s APIs, software development kits (“DDSDKs”), and other developer products and services and associated software (including those described in or available via our [Developer Portal](/docs/intro) (collectively, "APIs" or “Developer Platform”).
-
-These Developer Terms of Service (“Developer Terms”) apply to your access to and use of the APIs and set forth the legal obligations between us and you.
-
-When we say “Discord,” “we,” “us,” and “our” in these Developer Terms of Service, we mean Discord Inc., unless otherwise set forth in additional terms applicable to a given API.
-
-When we say “Terms” in these Developer Terms, we mean, collectively, these Developer Terms, our [Developer Documentation](/docs/intro) and any other applicable documentation we make available (“Documentation”), our [Discord Developer Policy](/docs/policies-and-agreements/developer-policy), our [Terms of Service](https://discord.com/terms) (including our [Discord Community Guidelines](https://discord.com/guidelines)), and any other applicable terms, policies, and guidelines we make available (including in our [Developer Portal](/docs/intro) or [Help Center](https://support-dev.discord.com/hc)). If there is a conflict between these Developer Terms and any additional terms, then these Developer Terms will control for that conflict. If you use other Discord services in connection with the APIs, then the terms for those other services also apply to you. Additional defined terms are described in Section 13 (Definitions) below.
-
-Important Note: Section 12(e) (Choice of Law; Dispute Resolution) incorporates the [dispute resolution provision](https://discord.com/terms#settling-disputes-between-you-and-discord) from our [Terms of Service](https://discord.com/terms), which includes an arbitration clause and class action waiver that applies to all U.S.-based Discord users. Please read this section carefully as it may significantly affect your legal rights, including your right to file a lawsuit in court.
-
-## Section 1: Acceptance of the Terms and Registration
-
-### a. Accepting the Terms
-
-By accepting these Developer Terms of Service, creating or operating an Application, or otherwise accessing or using our APIs, you agree to comply with the Terms and that the Terms control your relationship with us. You also confirm and agree that (i) you are at least 13 years of age and meet the minimum age required by the laws in your country, and (ii) if you are not old enough to have authority to consent to the Terms in your country, that your parent or legal guardian must agree to the Terms on your behalf. If you are a parent or legal guardian, and your teenager accesses or uses the APIs, then the Terms also apply to you and you are responsible for your teenager’s activity. Please read all the Terms carefully.
-
-You may not use the APIs and may not accept the Terms if you are barred from using or receiving the APIs under the applicable laws of the United States or other countries, including the country in which you are a resident or from which you use the APIs.
-
-If you are using the APIs on behalf of an entity, you represent and warrant that you have authority to bind that entity to the Terms and by accepting the Terms, you are doing so on behalf of that entity (and all references to "you" in the Terms refer to that entity).
-
-### b. Registration & Application Information
-
-You may be required or requested to provide certain information about yourself (such as identification or contact details or materials) and your Application (such as details about its functionality) as part of the registration process for access to the APIs (including when you create your Application), or as part of your continued use of the APIs (including in the Developer Portal or during App Review). You will ensure such information is accurate, complete, and up-to-date at all times. Without limiting the foregoing, you will maintain a clear and accurate description of your Application in its user-facing profiles. You will not misrepresent or mask your, or your Application’s, identity in the Developer Portal, as part of any registration process or App Review, or when using the APIs. We will use information about you to confirm your identity and as otherwise described in our [Privacy Policy](https://discord.com/privacy).
-
-## Section 2: Use of the APIs
-
-### a. License to you
-Subject to your compliance with the Terms, we grant you a limited, non-exclusive, non-sublicensable, non-transferable, non-assignable, revocable license to access and use the APIs and Documentation we make available to you solely as necessary to integrate with, develop, and operate your Application to the extent permitted under the Terms (including the [Developer Policy](/docs/policies-and-agreements/developer-policy). We reserve all rights, title, and interest not expressly granted in the Terms and you may not access or use the APIs or Documentation except as set forth in the Terms.
-
-## b. Restrictions
-
-You will not (and will not attempt to or permit or enable others to): (a) reverse engineer or otherwise derive source code, trade secrets, or know-how from the APIs, except to the extent this restriction is prohibited by applicable laws; (b) modify, create derivative works, copy, reproduce, redistribute, rent, lease, sell, or syndicate access to the APIs; or (c) access or use the APIs in any way that (i) is not in accordance with the applicable Documentation, (ii) compromises, breaks, or circumvents any of our technical processes or security measures, (iii) poses a security vulnerability to users, us (including our systems or networks), or any third party, or (iv) exceeds any API rate, call, or other usage limits we set in our sole discretion (including as set forth in the Developer Policy or the applicable Documentation) or that we believe constitutes excessive or abusive usage.
-
-### c. Open Source Software
-
-Some of the software required by or included in our APIs may be offered under an open source license, as may be listed in the Documentation. Open source software licenses constitute separate written agreements. To the limited extent the open source software license expressly supersedes the Terms, the open source license instead sets forth your agreement with Discord solely for the applicable open source software.
-
-### d. Developer Credentials
-
-You will use any developer credentials (such as your Application ID, passwords, keys, tokens, and client secrets) we assign to you solely with your Application and the applicable APIs (and will not permit or enable any other Application to use them) and will treat them as Discord confidential information (as described below). Without limiting the foregoing, you will keep API keys and tokens encrypted in any files or other materials accessible by third parties (other than your Service Providers, subject to Section 12(a)). For the avoidance of doubt, developer credentials may not be embedded in open source projects.
-
-### e. Eligibility
-
-As part of the APIs, we may make certain features available to you that require you to meet additional criteria in order to be eligible to access them (e.g., to enable your Application to be discoverable on or through Discord services). For the avoidance of doubt, your access to and use of such features will be subject to your compliance with the then-current applicable eligibility criteria and other policies (in addition to all other Terms).
-
-## Section 3: Use of App Content and Your Application
-
-### a. License
-
-You grant us a non-exclusive, transferable, sublicensable, royalty-free, worldwide license to run, publicly display and perform, distribute, reproduce, modify, host, translate, store, and otherwise use your Application and App Content in connection with operating, developing, and improving the APIs and other Discord services; provided that the right to reproduce does not apply to the Application. This license is to allow us to, among other things: enable users to install and use your Application in Discord servers; display and provide information about you (including your name and Brand Features) and your Application to users (including in profile and product pages); frame and link to, place content around, and limit commands from your Application; make your Application discoverable by users on or through Discord services (including in search results, categories, and collections with other Applications); attribute you as the source of App Content; and analyze your Application and App Content for performance and compliance. For clarity, the things we do under this license will depend in part on your Application, App Content, and how you use the APIs. For example, if your Application is a bot integration that you host and deploy on your own, then we would not need to host your Application. This license will remain in effect with respect to App Content after the Terms end. We will not be subject to any terms or policies associated with your Application or App Content (even if we click to agree). You will ensure that your Application and App Content do not introduce any viruses, worms, defects, Trojan horses, malware, spyware, adware, or other items of a destructive nature to the APIs or other Discord services.
-
-### b. Users
-
-You are solely responsible for your Application (including its development, operation, maintenance, support, distribution, use, and content). You will require users to comply with all applicable laws and regulations and the Terms (including our [Terms of Service](https://discord.com/terms)) in connection with their use of your Application (and will not permit or enable them to violate any of the foregoing). If you have a separate terms of service or other agreement to apply to users’ use of your Application, you agree (i) such agreement is solely between you and the user and we will not have any responsibility or liability thereunder and (ii) such agreement may not and will not supersede, modify, or be inconsistent with the Terms, which will supersede if there is any conflict or inconsistency with your agreement.
-
-## Section 4: Compliance with Laws & Third-Party Rights
-
-You and your Application will (and you will require those acting on your behalf and your users to): (i) comply with all applicable laws and regulations; (ii) not infringe or violate any third-party rights (including intellectual or other proprietary rights or rights of privacy or publicity); (iii) not access or use the APIs in a manner that is deceptive, unethical, false, misleading, or encourages or promotes illegal activity or infringement or violation of third-party rights; and (iv) not violate any other terms or policies with Discord. For clarity and without limiting the foregoing, you and your Application will comply with any third-party agreements, terms, or policies applicable to making your Application available in any Discord client (including app store or other developer guidelines or requirements imposed by Apple, Google, or others). If we believe you or your Application have caused Discord to be in violation of any of these third-party agreements, terms, or policies, we may remove your Application or take other enforcement actions as described in Section 9.
-
-You represent and warrant that you have obtained and will maintain all necessary rights (including from your users) to grant us the licenses, permissions, and other rights in the Terms (including those in Sections 3(a) and 8(d)) and to operate your Application (including to display, distribute, and provide all information, data, and other content therein and to access, use, and otherwise process users’ API Data and other data).
-
-## Section 5: User Privacy and Security
-
-### a. Implement Good Privacy Practices
-
-Without limiting Section 4, you will comply with all applicable privacy laws and regulations, including the European Union’s General Data Protection Regulation (GDPR) and the ePrivacy Directive, the UK General Data Protection Regulation, Brazil’s Lei Geral de Proteção de Dados (LGPD), the California Consumer Privacy Act (CCPA), and the California Privacy Rights Act (CPRA). You will provide and adhere to a privacy policy for your Application that is compliant with applicable privacy laws and clearly, accurately, and fully describes to users of your Application what data you collect, how you use and share such data with us and third parties, and how users can request deletion of such data. For the avoidance of doubt, how you use data includes how you access, collect, store, retain, transmit, share, and otherwise process it. You may only use API Data in accordance with your privacy policy, applicable laws and regulations, and the Terms. You agree that your privacy policy may not and will not supersede, modify, or be inconsistent with the Terms, which will supersede if there is any conflict or inconsistency with your privacy policy. You will maintain publicly available, up-to-date links to your privacy policy in the Developer Portal and make it easily accessible to users from your Application.
-
-### b. API Data Sharing & Retention
-
-You will not share API Data with any third party, except in the following circumstances, subject to compliance with the Terms and applicable laws and regulations: (i) with a Service Provider; (ii) to the extent required under applicable laws or regulations; and (iii) when a user of your Application expressly directs you to share their API Data with the third party (and you will provide us proof thereof upon request).
-
-Except to the extent you are required to retain API Data under applicable laws or regulations, you will (1) promptly update the API Data upon request from us or the applicable user, and (2) promptly delete the API Data when: (a) retaining it is no longer necessary for your Application’s stated (and approved through App Review, as applicable) functionality that is permitted under the Terms; (b) you stop operating your Application (whether on your own, due to an enforcement action by us, or otherwise); (c) we request you delete it; (d) the applicable user requests you delete it; or (e) required by applicable laws or regulations. You will give users an easily accessible way to ask for their API Data to be modified and deleted. If you have received API Data in error, you will immediately tell us, delete it, and provide proof of deletion upon our request.
-
-### c. Implement Good Security
-
-You will, and will require those acting on your behalf to, use commercially reasonable efforts to protect API Data from unauthorized access or use (including, for the avoidance of doubt, destruction, loss, alteration, disclosure, distribution, or other compromise). These efforts will include: (i) encryption of the data at rest and (ii) maintaining administrative, physical, and technical safeguards that are designed to prevent unauthorized access and use and comply with applicable laws and regulations (including relating to data security and privacy). You will promptly report to your users any unauthorized access or use of their data to the extent required by applicable laws or regulations. You will also promptly notify us and provide us with requested information about any incidents of unauthorized access or use of any API Data or any incidents that are reasonably likely to compromise the security, confidentiality, or integrity of your systems (or the systems of those acting on your behalf) that process API Data. In the event of any of the foregoing incidents, you will immediately begin to remediate it and reasonably cooperate with us, including by keeping us regularly updated about the incident and its impact on API Data, remediation actions being taken, and your compliance with any notification or other requirements under applicable laws and regulations.
-
-## Section 6: Monitoring & App Review
-
-The APIs are designed to help you enhance your Application. You agree to respond promptly to our requests to verify and audit your compliance with these Terms. YOU AGREE THAT DISCORD MAY MONITOR USE OF THE APIS TO ENSURE QUALITY, IMPROVE DISCORD APIs AND OTHER SERVICES, AND VERIFY YOUR COMPLIANCE WITH THE TERMS. You will not interfere with this monitoring. Discord may use any technical means to overcome such interference.
-
-Without limiting the foregoing, we may also require that you submit your Application for our review and approval in various circumstances (e.g., to approve access to certain APIs or API Data, when use of your Application reaches certain thresholds, when you request a transfer of ownership or rights relating to your Application, or to review compliance with the Terms) (“App Review”). You will cooperate with App Review and provide and maintain accurate and complete information as we request (including in the Developer Portal). If your Application has been approved through App Review, you will not materially change your Application’s functionality (including the scope of API Data you collect or how you use or share it) beyond its reviewed stated purpose, unless you first re-submit your Application, and receive our approval, through App Review.
-
-Periodically, we may also request (including through the Developer Portal) information, certifications, and attestations relating to your access to or use of the APIs or API Data, which you will provide to us in the requested time frame and form and which you will ensure are accurate and complete. If you are an entity, such certifications and attestations must be provided by an authorized representative.
-
-## Section 7: IP and Confidentiality
-
-### a. IP Ownership and Feedback
-
-Discord does not acquire ownership in your Application, and you do not acquire ownership of any rights in our APIs, API Data, Documentation, or Discord confidential information or any derivative works of any of the foregoing.
-Our APIs and API Data contain some third-party content (such as text, images, videos, audio, or software). This content is the sole responsibility of the person that makes it available and you are solely responsible for your decision to use or distribute any of this content. While we may sometimes review content to determine whether it is illegal or violates our policies or the Terms and we may remove or refuse to display content, we make no representations or warranties about the content or any decisions we make regarding it. Finally, API Data may be subject to intellectual property rights, and, if so, you may not use it unless you are licensed to do so by the owner of that API Data or are otherwise permitted by law. Your access to the API Data may be restricted, limited, or filtered in accordance with applicable law, regulation, and policy.
-
-If you provide suggestions or other feedback about our APIs, Documentation, or any other Discord services, then you grant us a non-exclusive, perpetual, irrevocable, sublicensable, transferable license to use the feedback and ideas generated from the feedback without any restrictions, attribution, or compensation to you.
-
-### b. Discord Copyright and IP Policy
-
-We respond to notices of alleged IP infringement and terminate the accounts of repeat infringers according to the process set out in the U.S. Digital Millennium Copyright Act (DMCA) and [Discord’s Copyright & IP Policy](https://support.discord.com/hc/en-us/articles/4410339349655-Discord-s-Copyright-IP-Policy). If you think somebody is violating your IP and want to notify us, you can find information about submitting notices in the foregoing policy.
-Without limiting Section 4, you will comply with the DMCA to receive and respond to notices of claimed infringement with respect to any user or other third-party content provided to or contained in your Application.
-
-### c. Confidential Matters
-
-Our communications to you and our APIs may contain Discord confidential information. Discord confidential information includes any materials, communications, and information that are marked or designated confidential or that would normally be considered confidential under the circumstances (including any nonpublic information). Without limiting the foregoing, your participation in any research or feedback surveys or sessions or in any experimentation, testing, or use of APIs we make available to you that are not generally publicly available (including any information you receive, and feedback you provide us, in connection therewith) are Discord confidential information. If you receive any Discord confidential information, then you (i) will keep it confidential using no less than reasonable care to protect it and will only use it as necessary for your permitted use of the applicable APIs under the Terms and to provide us feedback, and (ii) will not disclose it to any third party without Discord's prior written consent, except to the extent (1) required by law with reasonable prior notice to us unless prohibited by court order or (2) necessary for a Service Provider to provide you services subject to Section 12(a).
-
-## Section 8: Brand Features; Attribution
-
-### a. Brand Features
-
-"Brand Features" means the trade names, trademarks, service marks, logos, domain names, and other distinctive brand features of each party. Except where expressly stated, the Terms do not grant either party any right, title, or interest in or to the other party's Brand Features. All use by you of Discord’s Brand Features (including any goodwill associated therewith) will inure to the benefit of Discord. All use by us of your Brand Features (including any goodwill associated therewith) will inure to your benefit.
-
-### b. Attribution
-
-All Applications will provide proper attribution(s) as required by Discord (including as may be described in the applicable Documentation). Subject to your compliance with the Terms, Discord grants you a limited, revocable, non-transferable, non-assignable, non-sublicensable, non-exclusive license while the Terms are in effect solely to display Discord’s Brand Features for required attribution(s) or in an incidental manner while promoting or advertising your Application, only in accordance with the Terms and Discord’s Brand Guidelines. You understand and agree that Discord has the sole discretion to determine whether your attribution(s) and use of Discord's Brand Features are in accordance with the above requirements and guidelines.
-
-### c. Publicity
-
-You will not make any statement (including in any promotions or advertisements of your Application) regarding your access to or use of the APIs which suggests partnership with, sponsorship by, or endorsement by Discord without Discord prior written approval in each instance.
-
-### d. Promotional and Marketing Use
-
-You grant us a non-exclusive, transferable, sublicensable, royalty-free, worldwide license to use your name and Brand Features, your Application’s name and icon, and produce and distribute App Content and incidental depictions (including screenshots, videos, or other content) from your Application, in the course of promoting, marketing, or demonstrating the APIs or other Discord services you are using or your Application (including in our discovery surfaces). This license will remain in effect for existing materials and instances even if the Terms are terminated.
-
-## Section 9: Termination
-
-### a. Termination
-
-You may terminate the Terms by discontinuing your (including your Application’s and those acting on your behalf) access to and use of the APIs at any time with or without notice. Discord reserves the right to terminate the Terms with you, or discontinue, suspend, or limit the APIs or any portion or feature or your access thereto, if there is an Enforcement Reason or at our convenience upon notice to you. If there is an Enforcement Reason, we may, at our discretion, also take other enforcement actions, including the following: issue warnings or notifications to you or the users; identify and require or request corrective actions from you; remove, suspend, or limit your Application or App Content; remove any approval we have provided for your Application through App Review; remove badges we’ve issued to you or your Application; require you to stop using and delete API Data; terminate, suspend, or limit your user or developer account with Discord or your developer credentials; terminate your other agreements with Discord or your ability to use other Discord services; report you or your Application to law enforcement (as we deem appropriate); or take legal action or any other action we consider to be appropriate. Enforcement actions and reviews may be automated or manual. While we may take such actions with or without notice to you, including while we investigate, we value transparency and work hard to give you context for the decisions we make where appropriate. You can appeal any enforcement action we take under these Terms through this [form](https://dis.gd/app-appeal) or options we may make available via our services.
-Without limiting any of the foregoing, we may also limit, suspend, or terminate your Application’s access tokens or any other means of access to the APIs that have not been used or accessed within at least the prior 30-day period, with or without notice to you.
-
-### b. Your Obligations Post-Termination
-
-Upon any termination of the Terms or discontinuation of your access to the APIs, you will (and will require those acting on your behalf to) immediately stop using the APIs and developer credentials, cease all use of the Discord Brand Features, and delete any cached or stored API Data you have in your possession or control or was otherwise collected by your Application, and all rights granted to you under the Terms (including in Sections 2 and 8(b)) will immediately cease. Discord may independently communicate with any account owner whose account(s) are associated with your Application and developer credentials to provide notice of the termination of your right to use an API.
-
-### c. Surviving Provisions
-
-When the Terms come to an end, those terms that by their nature are intended to continue indefinitely will continue to apply, including Sections 2(b), 3 - 7, 8(c) and (d), 9(b) and (c), and 10-13.
-
-## Section 10: Liability for our APIs
-
-### a. WARRANTIES
-
-NEITHER DISCORD NOR ITS AFFILIATES, SUPPLIERS, OR DISTRIBUTORS MAKE ANY SPECIFIC PROMISES ABOUT THE APIs, API DATA, DOCUMENTATION, OR ANY DISCORD SERVICES. FOR EXAMPLE, WE DON'T MAKE ANY COMMITMENTS OR WARRANTIES ABOUT THE SPECIFIC FUNCTIONS OF THE APIs OR THE RELIABILITY, AVAILABILITY, ACCURACY, QUALITY, APPROPRIATENESS, LEGALITY, ORIGIN, SAFETY, USEFULNESS, OR ABILITY TO MEET YOUR NEEDS OF THE APIs, API DATA, OR DOCUMENTATION. YOU ACKNOWLEDGE THAT WE DO NOT WARRANT THAT THE APIs WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE, AND WE MAY CHANGE, SUSPEND, OR DISCONTINUE THE AVAILABILITY OF THE APIs AT ANY TIME. WE PROVIDE THE APIs, API DATA, AND DOCUMENTATION "AS IS" AND YOU USE THEM AT YOUR SOLE RISK.
-
-SOME JURISDICTIONS PROVIDE FOR CERTAIN WARRANTIES, LIKE THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. EXCEPT AS EXPRESSLY PROVIDED FOR IN THE TERMS, TO THE EXTENT PERMITTED BY LAW, WE EXCLUDE ALL WARRANTIES, GUARANTEES, CONDITIONS, REPRESENTATIONS, AND UNDERTAKINGS.
-
-### b. LIMITATION OF LIABILITY
-
-TO THE EXTENT PERMITTED BY LAW, DISCORD, AND DISCORD’S SUPPLIERS AND DISTRIBUTORS, WILL NOT BE RESPONSIBLE FOR LOST PROFITS, REVENUES, OR DATA; FINANCIAL LOSSES; OR INDIRECT, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES.
-TO THE EXTENT PERMITTED BY LAW, THE TOTAL LIABILITY OF DISCORD, AND ITS AFFILIATES, SUPPLIERS, AND DISTRIBUTORS, UNDER OR ARISING OUT OF THE TERMS, INCLUDING FOR ANY IMPLIED WARRANTIES, IS LIMITED TO THE GREATER OF (I) AMOUNT YOU PAID US TO USE THE APPLICABLE APIS (OR, IF WE CHOOSE, TO SUPPLYING YOU THE APIS AGAIN) DURING THE SIX MONTHS BEFORE YOU FIRST ASSERT A CLAIM OR (II) $100 (OR THE EQUIVALENT IN YOUR LOCAL CURRENCY).
-DISCORD IS NOT LIABLE FOR THE CONDUCT OR CONTENT, WHETHER ONLINE OR OFFLINE, OF ANY USER OF DISCORD SERVICES. IN ALL CASES, DISCORD, AND ITS AFFILIATES, SUPPLIERS, AND DISTRIBUTORS, WILL NOT BE LIABLE FOR ANY EXPENSE, LOSS, OR DAMAGE THAT IS NOT REASONABLY FORESEEABLE.
-
-### c. Indemnification
-
-Unless prohibited by applicable law, you will defend (at our option), indemnify, and hold harmless Discord, and its affiliates, directors, officers, employees, and users, from and against all claims, liabilities, damages, losses, costs, fees (including legal and accounting fees), and expenses relating to:
-- access to or use of the APIs or API Data by you, those acting on your behalf, your Application, or your users (including any incidents of unauthorized access to or use of API Data);
-- actual or alleged violation the Terms by you, those acting on your behalf, your Application, or your users;
-- actual or alleged infringement of any third-party right (including intellectual property or other proprietary rights or rights to privacy or publicity) by you, those acting on your behalf, your Application, or your users; or
-- your Application, App Content, your Brand Features, or any content, data, technology, information, or materials provided or contributed by or through you, those acting on your behalf, your Application, or your users.
-
-You will not settle any claim without our prior written consent. We may, at our sole discretion, elect to assume control of the defense and settlement of any claim.
-
-## Section 11: International Transfers
-
-### a. EEA Transfers
-
-This Section 11(a) applies to the extent that the API Data includes personal data controlled by Discord Netherlands BV (“Discord EU Data”) and you transfer the Discord EU Data to a territory outside of the European Economic Area that, at the time of such transfer, does not have a positive adequacy decision from the European Commission under Article 45 GDPR (each, an “EEA Data Transfer”).
-
-In each instance of an EEA Data Transfer, your use of Discord EU Data is subject to your compliance with the standard contractual clauses in European Commission Decision (EU) 2021/914 (“Clauses”) as they relate to controller-to-controller transfers as described in Module One.
-
-In each instance, you agree that for the purposes of Section IV, Clauses 17 and 18 in the Clauses, Option 1 and Option (b) shall apply respectively and the Member State shall be the Netherlands. Nothing in this Section 11(a) is intended to vary or modify the Clauses. For the purposes of the Appendix to the Clauses, the following will apply:
-
-- For the purposes of Annex I(A) to the Clauses, Discord Netherlands BV is the "data exporter" and you are the "data importer" as defined in the Clauses.
-- For the purposes of Annex I(B) to the Clauses:
- - “Categories of data subjects” are the users who visit, access, use, or otherwise interact with your Application and the services of Discord Netherlands BV;
- - "Categories of personal data" are Discord EU Data, which includes profile information, communications between users, photos and videos, location information, information about use of your Application and other products and services, payment information, device information, information from third-party partners or Discord, or as otherwise set forth in the Discord Privacy Policy;
- - "Sensitive data" is personal data about a person's racial or ethnic origin, political opinions, religious or philosophical beliefs, trade-union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person's sex life or sexual orientation, criminal convictions or alleged commission of an offence;
- - "Frequency of the transfer" is on a continuous basis to the extent required to fulfill the purpose set forth directly below;
- - “Nature and purpose of the data transfer(s)" is the provision of your Application by you to users pursuant to these Terms and your applicable terms and privacy policy; and
- - "Period for which personal data will be retained" is as described in the Terms and in any case not longer than necessary for a legitimate business purpose in accordance with the Terms and applicable laws or regulations (including rights of erasure and similar rights for individuals), unless applicable laws require the Discord EU Data be retained for a longer period, in which case you shall only retain such Discord EU Data for the period required by such applicable laws.
-- For the purposes of Annex I(C) to the Clauses, the competent supervisory authority will be the Dutch Data Protection Authority (Autoriteit Persoonsgegevens); and
-- For the purposes of Annex II to the Clauses, you will implement and maintain the technical and organisational security measures set out in the Terms, including those in Section 5 (“User Privacy and Security”) and such other measures as we may require from time to time.
-
-### b. UK Transfers
-
-This Section 11(b) on UK transfers shall apply to the extent that the API Data includes personal data controlled by Discord Netherlands BV that is subject to the UK GDPR (as defined in the UK's Data Protection Act 2018 ("DPA")) (“Discord UK Data”) and the transfer of such Discord UK Data to a territory outside of the United Kingdom that, at the time of such transfer, does not have a positive adequacy decision from the Secretary of State in accordance with the relevant provisions of the UK GDPR and the DPA (“UK Data Transfer”).
-
-Whenever there is a UK Data Transfer, your use of Discord UK Data is subject to your compliance with the Approved Addendum (which is hereby incorporated by reference into these Developer Terms and is deemed to have been entered into and completed as set out below). Nothing in this Section 11(b) is intended to vary or modify the Approved Addendum. All defined terms used below shall have the meanings given to them in the Approved Addendum. For the purpose of the Approved Addendum, the following will apply:
-- In Table 1 of the Approved Addendum, the parties' details are as follows:
- - Discord Netherlands BV is the "data exporter" and you are the "data importer" as defined in the Approved Addendum.
-The parties details and key contact information are:
- - Discord Netherlands BV, Schiphol Boulevard 195, 1118 BG Schiphol, Netherlands, and the contact person's details are as notified by the data exporter to the data importer from time to time.
- - Developer's details and key contact information are your details notified to Discord Netherlands BV from time to time.
- - The parties agree that execution of the Terms by the parties shall constitute execution of the Approved Addendum.
-- For the purposes of Table 2 of the Approved Addendum, the selected modules of the Approved EU SCCs shall be Module 1 (controller to controller).
-- Table 3 of the Approved Addendum shall be populated as follows:
- - Annex 1A: List of Parties: See Table 1 references above and the activities relevant to the data transferred are as described in the Terms.
- - Annex 1B: Description of Transfer: The information in Section 11(a) above shall apply, albeit references to "Discord EU Data" shall be replaced with "Discord UK Data".
- - Annex II: Technical and organizational measures: For the purposes of Annex II, you will implement and maintain the technical and organisational security measures set out in the Terms, including those in Section 5 (“User Privacy and Security”) and such other measures as we may require from time to time.
-- In Table 4 of the UK Addendum, the data exporter may end the UK Addendum in accordance with the terms of the UK Addendum.
-
-## Section 12: General Provisions
-
-### a. Service Providers
-
-Before using a Service Provider, you will require them to first agree in writing to only access and use the APIs and API Data for you and at your direction to provide you services to develop or operate your Application in compliance with the Terms, and for no other purpose (including their own). For the avoidance of doubt, Service Providers are acting on your behalf. You will ensure that each Service Provider complies with the Terms as if they are in your place, and you are solely responsible and liable for their acts and omissions, including noncompliance. When you stop using a Service Provider, you will ensure they immediately cease using the APIs and API Data and promptly delete all API Data in their possession or control. Upon notice, we may prohibit your use of any Service Provider if we reasonably believe that they have violated the Terms or they are negatively impacting us, the APIs or our other services, API Data, or the users, and you will promptly stop using them.
-
-### b. Modification
-
-We may change these Developer Terms from time to time. If we make a material change to these Developer Terms, we will provide you with reasonable notice prior to the change taking effect (e.g., at the email address or Discord ID we have on file for you or in the Developer Portal), unless the changes are urgent. If you continue to access or use the APIs or API Data after the changes have taken effect, it means that you agree to the changes. If you do not agree, you must stop using the APIs and API Data. You can review the most current version of these Developer Terms at any time by visiting this page.
-
-### c. U.S. Federal Agency Entities
-
-The APIs and Documentation were developed solely at private expense and are commercial computer software and related documentation within the meaning of the applicable U.S. Federal Acquisition Regulation and agency supplements thereto.
-
-### d. Export Control
-
-You represent and warrant that you are not located in, or affiliated with the government of North Korea and are not included on any U.S. or E.U. list of prohibited or restricted parties. If you are located in any other country, including those subject to a comprehensive U.S. or E.U. sanction or embargo, your use of the APIs and any other Discord services must be in compliance with U.S. and E.U. laws and must not cause Discord to be in violation of such laws. If you request access to, download, or use any APIs that are not generally publicly available, you also represent and warrant that you are not located in Syria or the Crimea region of Ukraine, and are not affiliated with a government of such regions or the governments of Cuba or Iran. In addition, if your Application incorporates Discord software or SDKs, it may be subject to U.S. export controls governing its export, reexport, and transfer. You are responsible for determining the applicable restrictions and obtaining any necessary export approvals for your Application under the applicable laws. You may not permit your Application to be hosted, accessed, or used (i) in North Korea or by any U.S. or E.U. list of prohibited or restricted parties; or (ii) in any other country or region subject to comprehensive U.S. or E.U. government embargo (including Cuba, Iran, Syria, and the Crimea, Donetsk People's Republic, or the Luhansk People's Republic regions of Ukraine) unless that use is authorized by the U.S. and other relevant authorities, for example the general licenses issued by the U.S. Office of Foreign Assets Control for services incident to the exchange of personal communications over the Internet (such as instant messaging, chat and email, social networking, sharing of photos and movies, web browsing, and blogging).
-
-### e. Choice of Law; Dispute Resolution
-
-Subject to Section 11 above with respect to the governing law that applies to International Data Transfers, the [“Settling disputes between you and Discord” section in our Terms of Service](https://discord.com/terms#settling-disputes-between-you-and-discord) applies, where references to “the services” or “our services” will mean the APIs, “these terms” will mean these Developer Terms of Service, and the date for emailing an opt-out notice is within 30 days of July 8, 2024 or when you first create an Application, whichever is later.
-
-### f. General Legal Terms
-
-To the extent permitted by law, we each agree to contract in the English language and if we provide a translation of the Terms, we do so for your convenience only and the English Terms will solely govern our relationship. The term “including” means “including without limitation.” The Terms do not create any third party beneficiary rights or any agency, partnership, or joint venture. Nothing in the Terms will limit either party's ability to seek injunctive relief. We are not liable for failure or delay in performance to the extent caused by circumstances beyond our reasonable control. If you do not comply with the Terms, and Discord does not take action right away, this does not mean that Discord is giving up any rights that it may have (such as taking action in the future). If it turns out that a particular term is not enforceable, this will not affect any other terms. The Terms are the entire agreement between you and Discord relating to its subject and supersede any prior or contemporaneous agreements on that subject (unless, and solely to the extent, you and Discord have entered into a separate written agreement to expressly supersede). For information about how to contact Discord, please visit our [Terms of Service](https://discord.com/terms).
-
-You may not assign, sublicense, delegate, or otherwise transfer any of your rights or obligations under the Terms (including any sale, license, or other transfer of ownership of your Application) to any third party without the prior written consent of Discord. For clarity, upon a Discord-approved transfer, the Terms apply to the transferee as “you” (including with respect to the operation of the Application and any processing of API Data, whether obtained before or after the transfer) and they assume the obligations and liabilities of the transferor under the Terms. Any transfer in violation of this provision is null and void. Any change of control or material ownership of you is hereby deemed an assignment. These Terms are non-exclusive. You acknowledge that Discord may develop products or services that may compete with, or are similar to, Applications or any other products or services.
-
-## Section 13: Definitions
-
-- “APIs” (or “Developer Platform”) means, collectively, Discord’s APIs, software development kits (“SDKs”), and other developer services and associated software (including those described in or available via our [Developer Portal](/docs/intro)).
-- “API Data” means any data, information, or other content you obtain through the APIs (including personal data). API Data includes your developer credentials and access tokens.
-- “App Content” means any data, information, technology, materials, or other content that you or those acting on your behalf add to our services or otherwise make available to us in connection with the APIs or your Application (including as submitted, posted, or displayed by or through your Application).
-- “App Review” has the meaning set forth in Section 6.
-- “Application” (or “app”) means any application (including any bot, game, activity, website, or other client) that accesses or uses our APIs or to which we have assigned an Application ID. “your Application” means any Application that you own or operate. References made to API Client in existing terms, policies, agreements, or Documentation will now mean Application.
-- “Approved Addendum” means the International Data Transfer Addendum to the Clauses, Version B1.0, issued by the UK Information Commissioner’s Office and laid before the Parliament in accordance with s119A of the Data Protection Act 2018, in force 21 March 2022, as may be amended by the Information Commissioner.
-- “Brand Features” has the meaning set forth in Section 8(a).
-- “Clauses” has the meaning set forth in Section 11(a).
-- “Discord EU Data” has the meaning set forth in Section 11(a).
-- “Discord services” (or “our services") has the meaning set forth in our [Terms of Service](https://discord.com/terms) for Discord’s services.
-- “Discord UK Data” has the meaning set forth in Section 11(b).
-- “EEA Data Transfer” has the meaning set forth in Section 11(a).
-- “Enforcement Reasons” mean if we believe (i) you or your Application have or may have violated any of the Terms (including by enabling or permitting violations of our [Terms of Service](https://discord.com/terms) or other Terms by users) or is negatively impacting us, the APIs or other Discord services, or our users; (ii) your Discord user account has been compromised or it is otherwise suspended or terminated; (iii) it is necessary to comply with applicable laws or regulations or otherwise required by court order or other governmental authority; or (iv) it is necessary to protect ourselves from legal or regulatory liability.
-- “Service Provider” means a person or entity you use to provide you services to develop or operate your Application.
-- “UK Data Transfer” has the meaning set forth in Section 11(b).
diff --git a/docs/policies-and-agreements/store-distribution-agreement.md b/docs/policies-and-agreements/store-distribution-agreement.md
deleted file mode 100644
index 2dfc3df141..0000000000
--- a/docs/policies-and-agreements/store-distribution-agreement.md
+++ /dev/null
@@ -1,179 +0,0 @@
-# Discord Store Distribution Agreement for Developers (Self-Service)
-
-This Discord Store Distribution Agreement for Developers (“Agreement”) is by and between Discord, Inc., with a principal office located at 444 De Haro Street, San Francisco, California 94107 (“Discord”), and the person or entity identified in the “Legal Name” field in connection with the process of agreeing to this Agreement (“Developer”). Such process is referred to in this Agreement as the “Agreement Process”. The effective date of this Agreement is date on which Discord provides Developer with notice of its acceptance (“Effective Date”).
-
-BY ELECTRONICALLY SIGNING THIS AGREEMENT OR CLICKING THE “I AGREE” OR SIMILAR BUTTON AS PART OF THE AGREEMENT PROCESS, DEVELOPER IS AGREEING TO BE BOUND BY THIS AGREEMENT.
-
-### 1\. Definitions
-
-1.1 “**Affiliate**” means, with respect to an entity, a person or entity that controls, is controlled by, or is under common control with such entity.
-
-1.2 “**App(s)**” means the Developer games or other applications specified in connection with the Agreement Process and provided by Developer to Discord for distribution via the Discord Store, including, upon delivery to Discord, any App Updates, Error corrections for, and any Localized Versions of such Apps. Apps include only the versions of such games or applications that operate on Windows, Macintosh, or Linux operating systems, or other operating systems supported by Discord Store in the future.
-
-1.3 “**App-Related Content**” means any online content, features or software specific to an App that is made available by Developer for purchase, download or online access separately from the App, whether through in- application purchase transactions or otherwise (for example, but without limiting the foregoing, App-themed virtual items, expansion packs, additional filters, codecs, stock multimedia, game scenarios or levels, additional functionality, etc.). App-Related Content also includes any services provided with respect to an App in exchange for a subscription payment.
-
-1.4 “**App Term**” means the time period during which an App may be made generally available in the entire Territory for use by and/or distribution to Discord Store Account Owners on the Discord Store.
-
-1.5 “**App Updates**” means any updates, corrections, and enhancements provided by Developer for use by any end user of the Apps and shall include any such updates, corrections, and enhancements made available to third parties or end users.
-
-1.6 “**Demo Version**” means any demonstration versions of the Apps, if any.
-
-1.7 “**Developer Marks**” means the trademarks, including logos, used by Developer for the Apps.
-
-1.8 “**Discord Marks**” means Discord’s trademarks and logos that Discord provides to Developer for use in accordance with this Agreement.
-
-1.9 “**Discord SDK**” means Discord’s rich presence or other software development kits made available by Discord to Developer for use in accordance with this Agreement.
-
-1.10 “**Discord Software**” means the Discord SDK, the Discord Store SDK, and any other Discord software made available by Discord to Developer (for example, the API as defined in the Developer TOS) for use in accordance with this Agreement.
-
-1.11 “**Discord Store**” means Discord’s online app distribution platform. For the purposes of this Agreement, “Discord Store” does not include any content from Developer, Discord, or other third parties.
-
-1.12 “**Discord Store Account Owner**” means an end user of one or more of the Apps who has obtained a Discord Store account, agreed to Discord’s Discord Store Subscriber Agreement, and licensed a version of the Apps via the Discord Store.
-
-1.13 “**Discord Store SDK**” means the software development toolkit for the Discord Store that is delivered to or made available to Developer for its use in accordance with this Agreement.
-
-1.14 “**General Availability Date**” or “GA Date” means, for each App, the date such App is first made generally available in the entire Territory for use by and/or distribution to Discord Store Account Owners on the Discord Store. For clarity, the GA Date shall not be the first date of any beta testing or other limited availability.
-
-1.15 “**Gross Revenue**” means revenue actually received and booked by Discord from its users in accordance with its standard accounting processes from Discord’s distribution of the Apps via the Discord Store pursuant to this Agreement.
-
-1.16 “**Localized Version**” means any versions of the Apps created for specific languages or jurisdictions.
-
-1.17 “**Net Revenue**” means Gross Revenue less (a) actual amounts attributed to returns, user fraud, charge-backs and refunds; (b) amounts collected for VAT (defined below); and (c) any amounts paid to third-party payment processors and money-transmitters.
-
-1.18 “**Primary Platform**” means the operating system on which the majority of usage occurred during the seven (7) day period following the date of purchase (or free download) of an App, provided that if no usage occurred during that period, the Primary Platform shall be the operating system on which the Discord Store Account Owner purchased (or downloaded for free) the App,
-
-1.19 “**Ratings Information**” means ratings information about the Apps obtained from ratings boards or government authorities (including, but not limited to, the ESRB).
-
-1.20 “**Sales Data**” means non-personally identifiable sales data for Discord Store Account Owners that is retained by Discord and typically analyzed by Discord for its own computer games, including but not limited to sales rates by country.
-
-1.21 “**Territory**” means (a) worldwide or (b) the jurisdictions authorized for distribution by Developer on Discord Store, if Developer has restricted an App’s distribution territory through the online tools provided by Discord for this purpose.
-
-1.22 “**VAT**” means any value added tax, goods and services tax or any other similar tax, including any sales tax, service tax, gross receipt tax, or use tax imposed by any governmental authority in any country at any level.
-
-### 2\. Rights and Licenses
-
-2.1 **Apps License.** Developer hereby grants to Discord a license: (a) to copy, perform, display, modify, create derivative works of, and use the Apps for general access and as necessary to (i) enable the use and distribution of the Apps (including Demo Versions, Localized Versions and App Updates) via Discord Store, and (ii) support Discord Store Account Owners as described in this Agreement; and (b) to copy, perform, display, modify, create derivative works of, and use, transmit, sell, license and otherwise distribute the Apps via Discord Store to Discord Store Account Owners in the Territory. The foregoing license (the “Apps License”) shall be non-exclusive and worldwide. The only fees payable for the Apps License shall be as set forth in Section 6.1 of this Agreement. Any Territory restrictions shall apply to the sale or initial distribution of the App. Developer acknowledges and agrees that Discord Store Account Owners may receive subsequent distributions of Apps from locations outside the Territory.
-
-2.2 **Appointment as Agent and Commissionaire.** Developer hereby appoints Discord as (i) its agent for the marketing and delivery of the Apps to Discord Store Account Owners located in the United States and (ii) its commissionaire (Agent with Developer as undisclosed Principal) for the marketing and delivery of Apps to Discord Store Account Owners located in the rest of the world. Developer hereby acknowledges that Discord will market and make the Apps available for download. In furtherance of Discord's appointment under this Section, Developer hereby authorizes and instructs Discord to:
-
-(a) be merchant of record at the Discord Store and issue invoices for the purchase price payable by Discord Store Account Owners for the Apps; and
-
-(b) otherwise use Apps, Information and associated metadata as may be reasonably necessary in the marketing and delivery of the Apps.
-
-The parties acknowledge and agree that their relationship is, and shall be, that of principal and agent (U.S.), or principal and commissionaire (non-U.S.), as the case may be, and that Developer, as principal, is, and shall be, solely responsible for any and all claims and liabilities involving or relating to, the Apps. For completeness' sake, (i) Discord Store Account Owners located in the United States will enter into a license agreement for Apps with Developer (effectuated by Discord in the name of and on behalf of Developer), and (ii) Discord Store Account Owners located in the rest of the world will enter into a license agreement for Apps with Discord (but for the risk and account of Developer).
-
-2.3 **Marketing License.** Developer hereby grants to Discord a royalty-free license, during the Term, to copy, perform, display, create derivative works of, use, and distribute (a) the Developer Marks and (b) materials from the Apps (for example, screenshots), marketing material (for example, videos), and ratings information in connection with the promotion, marketing, licensing, sale, and distribution of the Apps and the exercise of Discord’s other rights under this Agreement. The foregoing license shall be non-exclusive and worldwide.
-
-2.4 **Discord Store and Discord Software License.** Discord hereby grants to Developer a non-exclusive, royalty-free, license, during the Term, to use the Discord Store solely as necessary to fulfill Developer’s obligations under this Agreement. Developer’s use of the Discord Software shall be subject to the Discord Developer Terms of Service currently located at https://discord.com/developers/docs/legal (the “Developer TOS”).
-
-2.5 **Discord Trademark License.** Subject to Discord’s prior written approval in each case, Discord hereby grants to Developer a non-exclusive, royalty-free, license, during the Term, to publicly display the Discord Marks solely in marketing materials for the Apps. All such use of the Discord Marks must be in accordance with, Discord’s trademark and other brand guidelines made available to Developer.
-
-2.6 **Open Source Software.** Except as otherwise expressly agreed in writing, Developer shall not distribute via Discord Store, or combine any Discord materials with, open source or other software that is licensed under terms that purport to bind Discord to contractual obligations (e.g., the GNU General Public License or Lesser General Public License).
-
-2.7 **License Upon Termination.** In addition, upon termination of this Agreement, Developer hereby grants to Discord a non-exclusive, worldwide, perpetual, irrevocable, fully-paid-up license to use, reproduce, transmit and distribute the Apps and any error corrections in object code form via electronic delivery solely to Discord Store Account Owners that have licensed a Discord distributed version of the Apps prior to the date of any termination of this Agreement, and Developer will continue to give Discord Store Account Owners access to online features of the App on an equal, non-discriminatory basis with other users, for so long as Developer supports such online features.
-
-2.8 **Reservation of Rights.** Except as expressly provided herein, Developer retains all right, title and interest in and to the Apps and the Developer Marks, and Discord retains all right, title and interest in and to Discord Store, the Discord Software, and the Discord Marks. Each party reserves all rights not expressly granted in this Agreement.
-
-### 3\. App Submissions
-
-3.1 **Submission.** Developer shall submit each App (or Localized Version) to Discord for distribution via the Discord Store concurrently with the first commercial release of each App (or Localized Version), or, if already commercially released as of the Effective Date, within thirty (30) days of the Effective Date. Developer shall also submit to Discord any Localized Versions when generally available, but in no event later than they are provided to any other third party for commercial release. All submissions must be in object code form, and in the format reasonably requested by Discord. Developer will ensure that any password needed to access its Discord Store account is treated as Confidential Information, and agrees that it will be responsible for any use of that password, whether by Developer or any third party.
-
-3.2 **Testing.** Before submitting any software to Discord, Developer shall perform quality assurance and other error and bug testing of the Apps (including any Localized Versions and all App Updates), in a professional manner consistent with industry standards. Discord may also conduct hardware and software compatibility and performance testing on the Apps, either itself or via a third party.
-
-3.3 **Compatibility.** Developer shall make the Apps compatible with Discord Store services that Developer may choose to use. Developer shall use reasonable efforts to maintain compatibility of the Apps with future versions of Discord Store.
-
-3.4 **App-Related Content.** If Developer distributes an App and App-Related Content for that App via any channel other than Discord Store, Developer will deliver the App-Related Content to Discord simultaneously to enable Discord to make such App-Related Content available to Discord Store Account Owners. In addition, to the extent any App supports the sale of digital items or digital currency for use in the App, Developer shall not allow or facilitate the redemption or exchange of such digital items or digital currency for real-world currency.
-
-3.5 **No Links to Other Stores.** Developer will ensure that Apps distributed via Discord Store will not include functionality from or links or references to any store other than Discord Store, or any other payment or purchase facility.
-
-3.6 **User Reviews.** Discord may, in its discretion, make available a user review system for Apps. Developer shall not manipulate the user review system for Apps, including but not limited to soliciting positive reviews in exchange for value.
-
-3.7 **Ratings Information.** Discord will facilitate Developer’s inclusion of Ratings Information for Apps in the Discord Store. Developer agrees to provide via the Discord Store current and accurate Ratings Information for each App.
-
-3.8 **Privacy and App Sales Data.** Subject to Discord’s privacy policy, the current version of which is located at discord.com/privacy, (the “Discord Privacy Policy”) the Discord Store Subscriber Agreement, applicable laws and any other obligations Discord has to a third party or otherwise, Discord will provide Developer with Sales Data for the Apps. The Discord Privacy Policy is hereby incorporated into this Agreement.
-
-### 4\. Marketing and Publicity
-
-4.1 **Marketing.** Discord may, at its own expense and sole discretion, market and promote the Apps via Discord Store and other channels, including but not limited to the Discord and Discord Store web sites and shall include the right to distribute promotional copies of the App(s).
-
-4.2 **Press Releases and Press Accounts.** Discord and Developer may reference in public statements the fact that the Apps are or will be available on Discord Store; however, any press release about the other Party shall be subject to the prior approval of the other Party. Discord may make the Apps available to journalists via press subscription accounts free-of- charge in order to enable such journalists to evaluate and review the Apps.
-
-4.3 **Demo Versions.** If Developer releases a Demo Version outside of the Discord Store that includes a reference regarding the method(s) to purchase the App, Developer shall cooperate with Discord to include a reference to Discord Store in that version.
-
-### 5\. Support
-
-5.1 **Developer Support to Discord.** Developer shall with respect to each App: (a) correct within a reasonable period of time all material bugs, errors, or defects in the Apps (collectively, “Errors”) of which Discord informs Developer; (b) deliver all App Updates when made available to any other third party; (c) provide such other reasonable additional support as Discord may reasonably request. If, in Discord's sole judgment, an App contains Errors or is otherwise of insufficient quality to meet Discord’s standards, it may suspend the availability of such App in the Discord Store. In the event Discord has suspended the availability of all Apps under this Agreement, it may terminate this Agreement for convenience. In addition, Developer must implement the Discord Store SDK in a manner that is safe and secure for the Discord Store Account Owner. Discord may, but shall not be obligated to, correct any security vulnerabilities in Developer’s implementation of the Discord Store SDK and Developer shall provide assistance with such corrections as requested by Discord. If Discord cannot reasonably correct any such vulnerabilities, or Discord determines that Developer should correct them, Developer shall correct such vulnerabilities.
-
-5.2 **Developer Support to End Users.** Developer will provide support to Discord Store Account Owners who have acquired a copy of the Apps, at the same level that Developer provides customer support for such applications made available directly or via other channels. Such support shall include but not be limited to responding to questions and assisting customers in the diagnosis and correction of issues encountered in using the Apps.
-
-5.3 **Discord End User Support.** Provided that Developer has complied with its support obligations in this Section 5, Discord will provide a reasonable level of support for issues related to Discord Store reported by Discord Store Account Owners.
-
-### 6\. Revenue, Reporting, and Payments
-
-6.1 **Licensee Fees or Other Fees.** Within thirty (30) days after the end of each calendar month, Discord will provide to Developer a report of Gross Revenue and Net Revenue for such month (each a “Monthly Report”). Each Monthly Report will contain activity for the current month as well as any Net Revenue adjustments for prior months reported by payment processors in the current month. Unless mutually agreed by Discord and Developer in a separate written agreement executed by both parties, Discord will pay to Developer ninety percent (90%) of the Net Revenue on the Monthly Report (the “License Fees”) within thirty (30) days after the Monthly Report is published, in no event later than sixty (60) days from the end of the of the calendar month covered by the Monthly Report. For completeness' sake, the remaining ten percent (10%) of the Net Revenue retained by Discord shall be payment of the consideration by Developer to Discord for the services and activities performed by Discord under this Agreement. Developer acknowledges and agrees that Discord, in the course of acting as agent or commissionaire of Developer, is hosting the Apps, and is allowing the download of those Apps by Discord Store Account Owners, on behalf of or respectively for the risk and account of Developer. All of the Apps and App-Related Content shall be marketed by Discord, on behalf of Developer, to Discord Store Account Owners at the prices established by Developer. Developer may change the price for any Apps or App-Related Content at any time, at Developer’s discretion, upon notice to Discord. As agent or commissionaire for Developer, Discord shall be solely responsible for the collection of all prices payable by Discord Store Account Owners for Apps acquired by those Discord Store Account Owners.
-
-6.2 **Taxes.** In the event that any remittance made by Discord to Developer is subject to any VAT, the full amount of such VAT shall be solely for the account of Developer, and will not reduce Discord's fee amount to which Discord is entitled on such transaction. To the extent required under applicable law, Discord will deduct the full amount of such VAT from the amount owed to Developer, and will pay the full amount withheld to the competent tax authorities. Discord will use commercially reasonably efforts to obtain, and to furnish to Developer, copies of official tax receipts or similar evidence of payment, confirming payment of such VAT to the competent tax authorities. Developer will indemnify and hold Discord harmless against any and all claims by any competent tax authorities for any underpayment of any VAT, and any penalties and/or interest thereon, including, but not limited to, underpayments attributable to any erroneous claim or representation by Developer as to its entitlement to, or any disqualification of Developer for, the benefit of a reduced rate of withholding tax..
-
-6.3 **Minimum Monthly Payment and Negative Amounts.** In the event amounts due to Developer for a given month do not exceed one hundred U.S. dollars ($100), Discord may elect to not remit payment for that month, and may instead accumulate payments due until they exceed one hundred U.S. dollars ($100) as of the end of a future monthly payment cycle. Also, to the extent that the payment calculation in a Monthly Report results in a negative amount, that negative amount will be carried forward and deducted from any future amounts otherwise payable to Developer by Discord under this Agreement.
-
-6.4 **Multi-Platform Apps.** To the extent that Developer has submitted to Discord Store versions of an App for multiple operating systems (for example, a Mac version, and a Windows version) such versions shall be sold together as a single "hybrid" App unit on Discord Store. Accordingly, a Mac version of any App, a Windows version of an App, and a Linux version of an App shall not be considered separate sales when calculating the payments due to Developer hereunder.
-
-### 7\. Term
-
-7.1 **Term.** The term of this Agreement (“Term”) shall begin on the Effective Date and continue until the end of the latest App Term for any App unless earlier terminated in accordance with this Agreement.
-
-7.2 **App Term.** With respect to each App, the App Term shall commence on the GA Date for such App and continue for one (1) year (the “Initial App Term”); and shall automatically renew for successive one (1) year periods ("Renewal Term") until terminated by either party pursuant to Section 7.3 or Section 7.4 below.
-
-7.3 **Termination for Cause.** Either party may terminate this Agreement upon written notice at any time if the other party is in breach of this Agreement and has failed to cure that breach within thirty (30) days after written notice of that breach. In addition, either party may terminate this Agreement immediately upon written notice if the other party (a) becomes insolvent or makes an assignment for the benefit of creditors; (b) files a petition, or has a third party file a petition with respect to it, under any bankruptcy or similar statute; or (c) materially breaches this Agreement and such breach is not capable of cure.
-
-7.4 **Termination for Convenience.** Either party may terminate this Agreement for convenience (with or without cause), during any Renewal Term, by providing the other party with thirty (30) days prior written notice of such termination, provided that during such period the parties have reasonably discussed and agreed on a process for sunsetting the Apps (a “Sunset Process”). In the event that a Sunset Process has not been agreed upon within such 30-day period, or the Sunset Process requires that this Agreement remain fully in force for longer than such 30-day period, this Agreement will not terminate until the completion of the Sunset Process.. In addition, Discord may terminate this Agreement immediately at any time upon written notice to Developer in the event that Discord (a) determines in its discretion that any or all Apps are not suitable for distribution via the Discord Store or (b) ceases to operate the Discord Store or the self-service portion of the Discord Store.
-
-7.5 **Survival.** Sections 2.5, 2.6, 3.1 - 3.7, 5.2 (only with respect to supporting Discord Store Account Owners that have licensed an App prior to termination or expiration), 6 (only with respect to amounts that accrued prior to termination or expiration), 7.5, and 8 - 13, and any then-existing Discord Store Account Owner licenses to Apps, shall survive any termination or expiration of this Agreement.
-
-### 8\. Warranties and Disclaimer
-
-8.1 **Mutual Representations and Warranties.** Each party represents and warrants that (a) this Agreement has been duly and validly executed and delivered by such party; (b) it has all necessary power and authority to execute and perform its obligations under this Agreement; and (c) its execution and performance of this Agreement will not violate any applicable law or regulation or violate any rights of, or breach any obligation owed to, a third party.
-
-8.2 **Developer Representations and Warranties.** Developer represents and warrants that (a) it originally created the Apps (which, for purposes of this Section 8.2, include Demo Versions, Localized Versions and App Updates) and the Developer Marks, or otherwise has the rights necessary to grant the licenses and to fulfill its obligations under this Agreement; (b) the Apps will conform to any documentation for the Apps; (c) the Apps and the Developer Marks do not infringe any right of any third party, including but not limited to any intellectual property right or right of publicity or privacy; (d) the Apps do not violate any terms of the Discord Store Subscriber Agreement; (e) it is in compliance with and will comply with all applicable laws and regulations, and its privacy policy, in connection with this Agreement, including but not limited to its use of any end user data supplied by Discord to Developer under this Agreement; (f) it has all necessary rights to any content or information it submits to Discord through the Discord Store partner portal or using any Discord Store-provided partner or publishing tools; and (g) the Apps do not contain any software viruses, trojan horses, or any other harmful or malicious code. Developer further represents and warrants that neither it nor its agents are on any list maintained by the United States Treasury Department’s Office of Foreign Assets Control (“OFAC”) of persons, entities, or prohibited or restricted jurisdictions (“Restricted List”) and Developer shall promptly notify Discord in writing if it is no longer in compliance with, or is likely to become noncompliant with, the foregoing representation or warranty. In such event, or if Developer or any of its agents are on any OFAC Restricted List, Discord, in addition to any other remedies, shall have the right to terminate this Agreement immediately without providing Developer an opportunity to cure.
-
-8.3 **Disclaimer. EXCEPT AS OTHERWISE EXPRESSLY PROVIDED HEREIN, EACH PARTY DISCLAIMS ALL WARRANTIES, INCLUDING THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, TITLE, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE, AND ALL MATERIAL PROVIDED BY SUCH PARTY HEREUNDER IS PROVIDED “AS IS” AND WITHOUT WARRANTY OR REPRESENTATION.**
-
-### 9\. Indemnification
-
-Developer will indemnify, defend (upon Discord’s written request), and hold harmless Discord and its Affiliates, successors, officers, directors and employees from any loss, liability, expense or damage (including attorneys’ fees) (“Liabilities”) arising out of any third party action, cause of action, claim or demand (each, a “Claim”) alleging a breach by Developer of its representations and warranties under Section 8 of this Agreement. Discord will promptly notify Developer of a Claim, provided that any delay in providing such notice shall relieve Developer of its obligations only to the extent that such delay materially prejudiced Developer. If Discord requests Developer to defend a Claim, Discord shall give Developer sole control of the defense of the Claim, provided that Developer shall not settle or otherwise dispose of any Claim in any manner that imposes fault or other liability on Discord. Discord may, at its own expense, participate in any such defense with its own counsel.
-
-### 10\. Limitation of Liability
-
-EXCEPT FOR BREACH OF SECTION 12 (CONFIDENTIALITY), IN NO EVENT SHALL DISCORD BE LIABLE FOR (A) ANY SPECIAL, INCIDENTAL, INDIRECT, PUNITIVE OR CONSEQUENTIAL DAMAGES OR (B) ANY DAMAGES IN EXCESS OF (IN THE AGGREGATE) THE AMOUNTS PAID OR PAYABLE UNDER THIS AGREEMENT ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT OR ANY PROVISION HEREIN, REGARDLESS OF THE LEGAL THEORY UPON WHICH ANY CLAIM FOR SUCH DAMAGES IS BASED. THE FOREGOING EXCLUSIONS AND LIMITATIONS SHALL APPLY TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-
-### 11\. Governing Law, Jurisdiction, and Venue
-
-This Agreement will be governed by and construed in accordance with the laws of the State of California, without reference to conflicts of laws principles. Any claim or dispute between the parties that arises in whole or in part from this Agreement or Developer’s use of the Discord Store shall be decided exclusively by a court of competent jurisdiction located in Santa Clara County, California. Developer hereby consents to, and waives all defenses with respect to, venue and jurisdiction in the state and federal courts of Santa Clara County, California.
-
-### 12\. Confidentiality
-
-12.1 "**Confidential Information**" means all non-public information that is identified as being confidential or which should reasonably be understood to be confidential, which includes without limitation, information relating to released or unreleased products, marketing or promotion of any product, financial information, business policies or practices, personnel, pricing and sales information, technology, computer programs, unpublished works of original authorship, trade secrets, or information received from third parties that the disclosing party is obligated to treat as confidential. Without limiting the foregoing, the terms of this Agreement and Sales Data shall be Discord’s Confidential Information. Confidential Information shall not include information that: (i) is or becomes generally known or available by publication, commercial use or otherwise through no fault of the receiving party; (ii) is known by the receiving party without restriction at the time of disclosure; (iii) is independently developed by the receiving party without the use of any Confidential Information received from the disclosing party; or (iv) is lawfully obtained without restriction from a third party that has the right to make such disclosure.
-
-12.2 The receiving party shall use Confidential Information it receives solely in connection with its performance under this Agreement, and shall disclose such Confidential Information only to employees and contractors who have a need to know such Confidential Information for purposes of this Agreement and are bound by written confidentiality obligations at least as restrictive as those herein. The receiving party shall protect Confidential Information from unauthorized disclosure and use with the same degree of care that it uses to protect its own Confidential Information, but in no event less than reasonable care.
-
-12.3 Notwithstanding the foregoing, the receiving party may disclose Confidential Information as necessary to comply with any court order or applicable law or regulation, provided that such party to the extent reasonably possible gives prior written notice to the other party of the possibility of such disclosure and to resist or limit disclosure, including without limitation reasonably cooperating with the other party in seeking a protective order or other similar relief.
-
-12.4 After termination of this Agreement or receiving earlier written request from the other party, the receiving party shall promptly return or delete the Confidential Information received from the disclosing party.
-
-### 13\. General Provisions
-
-13.1 **Independent Contractor.** The parties to this Agreement are independent contractors. This Agreement does not create any joint venture, partnership, or other business entity.
-
-13.2 **Notices.** Any notices required by this Agreement must be sent in writing via overnight delivery by a nationally recognized courier service (e.g., FedEx) or first-class mail, signature required and shall be deemed effective upon signature acknowledging receipt by the party receiving notice. All such notices must be addressed to the receiving party at the address stated at the top of this Agreement with attention to the individual executing this Agreement on behalf of such party.
-
-13.3 **Assignment.** Neither party may assign or otherwise transfer this Agreement or its rights hereunder without the other party’s prior written consent, except that such consent shall not be required for (a) a party to transfer this Agreement to an Affiliate or in connection with a merger, acquisition, or other corporate combination, or the sale of all or substantially all of such party’s assets, provided that the successor party is not a competitor of the non-transferring party and the transferring party provides prompt notice of such transfer; or (b) Discord to assign, or sublicense some or all of, its rights under this Agreement to any of its Affiliates or to a subcontractor. Such transfer or assignment shall not relieve the transferring or assigning party of its obligations hereunder. Any attempted transfer or assignment by either party in violation of this Section shall be void and of no effect and will constitute a breach by the party attempting such transfer or assignment. This Agreement will be binding upon any permitted successor.
-
-13.4 **Headings.** The section headings used herein are for convenience only and shall not be given any legal import.
-
-13.5 **Severability.** If any provision of this Agreement is found by a court of competent jurisdiction to be invalid, the parties nevertheless agree that the court should endeavor to give effect to the parties' intentions as reflected in the provision, and the other provisions of this Agreement shall remain in full force and effect.
-
-13.6 **No Waiver.** The failure of a party to exercise or enforce any right or provision of this Agreement shall not constitute a waiver of such right or provision, and no waiver by either party of any breach or default hereunder shall be deemed to be a waiver of any preceding or subsequent breach or default.
-
-13.7 **Modifications.** This Agreement may not be modified except by a written agreement dated signed on behalf of Discord and Developer by their respective duly authorized representatives.
-
-13.8 **Complete Agreement.** This Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous communications and agreements between the parties with respect to such subject matter. Neither party has relied in entering into this Agreement on any statement, inducement or representation that is not set forth in this Agreement. Each party agrees that electronic signatures may be used to authenticate this writing and, if so used, will have the same force and effect as manual signatures.
diff --git a/docs/quick-start/overview-of-apps.mdx b/docs/quick-start/overview-of-apps.mdx
deleted file mode 100644
index 068c0c0481..0000000000
--- a/docs/quick-start/overview-of-apps.mdx
+++ /dev/null
@@ -1,103 +0,0 @@
----
-sidebar_label: Overview of Apps
----
-
-# Overview of Discord Apps
-
-
-
-Discord apps customize, extend, and enhance Discord for millions of users. Whether you're a developer interested in building an Activity, customizing servers, or integrating a game, apps are the container to bring your idea to life.
-
-On this page we'll answer the questions:
-
-- [What can apps do?](/docs/quick-start/overview-of-apps#what-can-apps-do)
-- [Where are apps installed?](/docs/quick-start/overview-of-apps#where-are-apps-installed)
-- [What APIs can apps use?](/docs/quick-start/overview-of-apps#what-apis-can-apps-use)
-
----
-
-## What can apps do?
-
-You will discover the full possibility of apps as you explore the documentation and start building, but for now let's take a glance at some features you can build and integrate as you're developing your app.
-
-### Send and manage messages
-
-Messages are a core part of Discord, and that's true for apps too. Apps can send messages in a few ways—they can call the **[Create Message endpoint](/docs/resources/message#create-message)**, create and execute [webhooks](/docs/resources/webhook), or respond with a message when responding to an [interaction](/docs/interactions/overview). Apps can also manage messages if they have the proper permissions, which is covered more in the [Message documentation](/docs/resources/message).
-
-### Interact with users
-
-Apps can use **[interactions](/docs/interactions/overview)** to create more engaging and intuitive experiences for users. When sending messages, apps can send interactive components like [buttons](/docs/components/reference#button) and [select menus](/docs/components/reference#string-select) in the `components` field. Apps can also open form-like modals or launch an Activity [in response to interactions](/docs/interactions/receiving-and-responding#interaction-response-object-modal).
-
-### Build embedded games and experiences
-
-Using the [Embedded App SDK](/docs/developer-tools/embedded-app-sdk), apps can create **[Activities](/docs/activities/overview)** which are cross-platform interactive games and social experiences in Discord. They run in iframes in Discord, where people who play games are already hanging out.
-
-### Customize servers
-
-With the right API endpoints and proper [permissions](/docs/topics/permissions), apps can customize the experience of using and moderating servers by accessing and customizing all sorts of resources core to Discord—including [users](/docs/resources/user), [channels](/docs/resources/channel), and [AutoMod](/docs/resources/auto-moderation) to name a few. Explore the **Resources** documentation category to learn about the different Discord resources and how apps can use them.
-
-### Update user metadata and presence
-
-Apps can update a Discord's user metadata with data from a party game or app in a few ways. Apps can also update a user's profile with actionable data from a game or app by integrating **[Rich Presence](/docs/rich-presence/overview)**. Apps can also use **[role connection metadata](/docs/resources/application-role-connection-metadata)** to associate third-party metadata (like stats or account type) with Discord users, which server admins can use to set up roles based on. You can explore more in the [configuring metadata for linked roles](/docs/tutorials/configuring-app-metadata-for-linked-roles) tutorial.
-
-### Add premium features
-
-**[App subscriptions](/docs/monetization/implementing-app-subscriptions)** let apps charge users and/or servers for premium functionality on a recurring basis natively within Discord. You can read more about eligibility and adding monetization features to your app in the [Monetization](/docs/monetization/overview) documentation.
-
-### ...and more
-
-This developer documentation is full of nooks and crannies with all sorts of features to explore. Discover the possibilities by exploring more of the docs, or by [building your own app](https://discord.com/developers/applications).
-
----
-
-## Where are apps installed?
-
-Discord apps can be installed in two different contexts:
-
-1. Apps installed **to a server** (called a [guild](/docs/resources/guild) throughout the API) by a user with the Manage Server ([`MANAGE_GUILD`](/docs/topics/permissions#permissions-bitwise-permission-flags)) permission. Apps installed to a server can only be used within that server and DMs with the app's bot user, and are visible to all server members.
-2. Apps installed **to a user account**. Apps installed to a user are visible *only* to that user, across all of their servers, DMs, and Group DMs by default.
-
-The installation contexts that an app supports can be limited by the developer when [setting up the app](/docs/resources/application#setting-supported-installation-contexts). Details about installation contexts are in the [Application resource documentation](/docs/resources/application#installation-context).
-
----
-
-## What APIs can apps use?
-
-There are a handful of different APIs that you can pick and choose from based on your app's functionality and which Discord features you want to access. Below is a quick overview of the main APIs on the Discord developer platform, but you can read more details and information about API usage in the [API reference](/docs/reference).
-
-### HTTP API
-
-The **HTTP API** is a REST API that lets you interact and modify core Discord resources like [channels](/docs/resources/channel), [servers (or guilds)](/docs/resources/guild), [users](/docs/resources/user), and [messages](/docs/resources/message#message-object).
-
-Use the HTTP API to:
-- Retrieve information about a resource
-- Create, update, or delete a resource
-
-Read details about using the HTTP API in the [API reference](/docs/reference#http-api).
-
-### Gateway API
-
-The **Gateway API** lets you receive event data over a WebSocket anytime an [event](/docs/events/gateway-events) occurs in a server where your app is installed.
-
-Use the Gateway API to:
-- Receive events happening in Discord
-
-Read details about using the Gateway API in the [API reference](/docs/reference#gateway-websocket-api).
-
----
-
-## Start Building
-
-Well, would you look at the time? With the basics out of the way, it's time to start building your Discord app! You can explore the rest of the documentation, go to your [Apps](https://discord.com/developers/applications), or explore the beginner resources below.
-
-
-
- Tutorial to develop your first Discord app with interactive components
-
-
- Tutorial to develop an Activity using the Embedded App SDK
-
-
- Explore community-built library and tools to speed up and simplify development
-
-
diff --git a/docs/resources/auto-moderation.mdx b/docs/resources/auto-moderation.mdx
deleted file mode 100644
index 40141afdb2..0000000000
--- a/docs/resources/auto-moderation.mdx
+++ /dev/null
@@ -1,294 +0,0 @@
-# Auto Moderation
-
-Auto Moderation is a feature which allows each [guild](/docs/resources/guild) to set up rules that trigger based on some criteria. For example, a rule can trigger whenever a message contains a specific keyword.
-
-Rules can be configured to automatically execute actions whenever they trigger. For example, if a user tries to send a message which contains a certain keyword, a rule can trigger and block the message before it is sent.
-
-### Auto Moderation Rule Object
-
-###### Auto Moderation Rule Structure
-
-| Field | Type | Description |
-|------------------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|
-| id | snowflake | the id of this rule |
-| guild_id | snowflake | the id of the guild which this rule belongs to |
-| name | string | the rule name |
-| creator_id | snowflake | the user which first created this rule |
-| event_type | integer | the rule [event type](/docs/resources/auto-moderation#auto-moderation-rule-object-event-types) |
-| trigger_type | integer | the rule [trigger type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) |
-| trigger_metadata | object | the rule [trigger metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) |
-| actions | array of [action](/docs/resources/auto-moderation#auto-moderation-action-object) objects | the actions which will execute when the rule is triggered |
-| enabled | boolean | whether the rule is enabled |
-| exempt_roles | array of snowflakes | the role ids that should not be affected by the rule (Maximum of 20) |
-| exempt_channels | array of snowflakes | the channel ids that should not be affected by the rule (Maximum of 50) |
-
-###### Example Auto Moderation Rule
-
-```json
-{
- "id": "969707018069872670",
- "guild_id": "613425648685547541",
- "name": "Keyword Filter 1",
- "creator_id": "423457898095789043",
- "trigger_type": 1,
- "event_type": 1,
- "actions": [
- {
- "type": 1,
- "metadata": { "custom_message": "Please keep financial discussions limited to the #finance channel" }
- },
- {
- "type": 2,
- "metadata": { "channel_id": "123456789123456789" }
- },
- {
- "type": 3,
- "metadata": { "duration_seconds": 60 }
- }
- ],
- "trigger_metadata": {
- "keyword_filter": ["cat*", "*dog", "*ana*", "i like c++"],
- "regex_patterns": ["(b|c)at", "^(?:[0-9]{1,3}\\.){3}[0-9]{1,3}$"]
- },
- "enabled": true,
- "exempt_roles": ["323456789123456789", "423456789123456789"],
- "exempt_channels": ["523456789123456789"]
-}
-```
-
-###### Trigger Types
-Characterizes the type of content which can trigger the rule.
-
-| Trigger Type | Value | Description | Max per Guild |
-|----------------|-------|-----------------------------------------------------------------------------|---------------|
-| KEYWORD | 1 | check if content contains words from a user defined list of keywords | 6 |
-| SPAM | 3 | check if content represents generic spam | 1 |
-| KEYWORD_PRESET | 4 | check if content contains words from internal pre-defined wordsets | 1 |
-| MENTION_SPAM | 5 | check if content contains more unique mentions than allowed | 1 |
-| MEMBER_PROFILE | 6 | check if member profile contains words from a user defined list of keywords | 1 |
-
-###### Trigger Metadata
-
-Additional data used to determine whether a rule should be triggered. Different fields are relevant based on the
-value of [trigger_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types).
-
-| Field | Type | Associated Trigger Types | Description |
-|---------------------------------|-------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------|
-| keyword_filter | array of strings * | KEYWORD, MEMBER_PROFILE | substrings which will be searched for in content (Maximum of 1000) |
-| regex_patterns | array of strings ** | KEYWORD, MEMBER_PROFILE | regular expression patterns which will be matched against content (Maximum of 10) |
-| presets | array of [keyword preset types](/docs/resources/auto-moderation#auto-moderation-rule-object-keyword-preset-types) | KEYWORD_PRESET | the internally pre-defined wordsets which will be searched for in content |
-| allow_list | array of strings *** | KEYWORD, KEYWORD_PRESET, MEMBER_PROFILE | substrings which should not trigger the rule (Maximum of 100 or 1000) |
-| mention_total_limit | integer | MENTION_SPAM | total number of unique role and user mentions allowed per message (Maximum of 50) |
-| mention_raid_protection_enabled | boolean | MENTION_SPAM | whether to automatically detect mention raids |
-
-\* A keyword can be a phrase which contains multiple words. [Wildcard symbols](/docs/resources/auto-moderation#auto-moderation-rule-object-keyword-matching-strategies) can be used to customize how each keyword will be matched. Each keyword must be 60 characters or less.
-
-\** Only Rust flavored regex is currently supported, which can be tested in online editors such as [Rustexp](https://rustexp.lpil.uk/). Each regex pattern must be 260 characters or less.
-
-\*** Each `allow_list` keyword can be a phrase which contains multiple words. [Wildcard symbols](/docs/resources/auto-moderation#auto-moderation-rule-object-keyword-matching-strategies) can be used to customize how each keyword will be matched. Rules with `KEYWORD` [trigger_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) accept a maximum of 100 keywords. Rules with `KEYWORD_PRESET` [trigger_type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) accept a maximum of 1000 keywords.
-
-###### Trigger Metadata Field Limits
-
-| Field | Trigger Types | MAX ARRAY LENGTH | MAX CHARACTERS PER STRING |
-|----------------|-------------------------|------------------|---------------------------|
-| keyword_filter | KEYWORD, MEMBER_PROFILE | 1000 | 60 |
-| regex_patterns | KEYWORD, MEMBER_PROFILE | 10 | 260 |
-| allow_list | KEYWORD, MEMBER_PROFILE | 100 | 60 |
-| allow_list | KEYWORD_PRESET | 1000 | 60 |
-
-
-###### Keyword Preset Types
-
-| Preset Type | Value | Description |
-|----------------|-------|--------------------------------------------------------------|
-| PROFANITY | 1 | words that may be considered forms of swearing or cursing |
-| SEXUAL_CONTENT | 2 | words that refer to sexually explicit behavior or activity |
-| SLURS | 3 | personal insults or words that may be considered hate speech |
-
-
-###### Event Types
-
-Indicates in what event context a rule should be checked.
-
-| Event Type | Value | Description |
-|---------------|-------|-----------------------------------------------------|
-| MESSAGE_SEND | 1 | when a member sends or edits a message in the guild |
-| MEMBER_UPDATE | 2 | when a member edits their profile |
-
-
-###### Keyword Matching Strategies
-
-Use the wildcard symbol (`*`) at the beginning or end of a keyword to define how it should be matched. All keywords are case insensitive.
-
-**Prefix** - word must start with the keyword
-
-| Keyword | Matches |
-|-----------|---------------------------------------|
-| cat\* | **cat**ch, **Cat**apult, **CAt**tLE |
-| tra\* | **tra**in, **tra**de, **TRA**ditional |
-| the mat\* | **the mat**rix |
-
-
-**Suffix** - word must end with the keyword
-
-| Keyword | Matches |
-|-----------|-------------------------------------|
-| \*cat | wild**cat**, copy**Cat** |
-| \*tra | ex**tra**, ul**tra**, orches**TRA** |
-| \*the mat | brea**the mat** |
-
-
-**Anywhere** - keyword can appear anywhere in the content
-
-| Keyword | Matches |
-|-------------|-----------------------------|
-| \*cat\* | lo**cat**ion, edu**Cat**ion |
-| \*tra\* | abs**tra**cted, ou**tra**ge |
-| \*the mat\* | brea**the mat**ter |
-
-
-**Whole Word** - keyword is a full word or phrase and must be surrounded by whitespace
-
-| Keyword | Matches |
-|---------|-------------|
-| cat | **cat** |
-| train | **train** |
-| the mat | **the mat** |
-
-
-### Auto Moderation Action Object
-
-An action which will execute whenever a rule is triggered.
-
-###### Auto Moderation Action Structure
-
-| Field | Type | Description |
-|-------------|--------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|
-| type | [action type](/docs/resources/auto-moderation#auto-moderation-action-object-action-types) | the type of action |
-| metadata? * | [action metadata](/docs/resources/auto-moderation#auto-moderation-action-object-action-metadata) | additional metadata needed during execution for this specific action type |
-
-\* Can be omitted based on `type`. See the `Associated Action Types` column in [action metadata](/docs/resources/auto-moderation#auto-moderation-action-object-action-metadata) to understand which `type` values require `metadata` to be set.
-
-###### Action Types
-
-| Action Type | Value | Description |
-|--------------------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| BLOCK_MESSAGE | 1 | blocks a member's message and prevents it from being posted. A custom explanation can be specified and shown to members whenever their message is blocked. |
-| SEND_ALERT_MESSAGE | 2 | logs user content to a specified channel |
-| TIMEOUT | 3 | timeout user for a specified duration * |
-| BLOCK_MEMBER_INTERACTION | 4 | prevents a member from using text, voice, or other interactions |
-
-\* A `TIMEOUT` action can only be set up for `KEYWORD` and `MENTION_SPAM` rules. The `MODERATE_MEMBERS` permission is required to use the `TIMEOUT` action type.
-
-
-###### Action Metadata
-
-Additional data used when an action is executed. Different fields are relevant based on the
-value of [action type](/docs/resources/auto-moderation#auto-moderation-action-object-action-types).
-
-| Field | Type | Associated Action Types | Description | Constraints |
-|------------------|-----------|-------------------------|----------------------------------------------------------------------------------------|--------------------------------------|
-| channel_id | snowflake | SEND_ALERT_MESSAGE | channel to which user content should be logged | existing channel |
-| duration_seconds | integer | TIMEOUT | timeout duration in seconds | maximum of 2419200 seconds (4 weeks) |
-| custom_message? | string | BLOCK_MESSAGE | additional explanation that will be shown to members whenever their message is blocked | maximum of 150 characters |
-
-
-### Auto Moderation Permission Requirements
-
-Users are required to have the `MANAGE_GUILD` permission to access all Auto Moderation resources.
-Some [action types](/docs/resources/auto-moderation#auto-moderation-action-object-action-types) require additional permissions, e.g. the `TIMEOUT` action type requires an additional `MODERATE_MEMBERS` permission.
-
-## List Auto Moderation Rules for Guild
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules
-
-Get a list of all rules currently configured for the guild. Returns a list of [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) objects for the given guild.
-
-:::info
-This endpoint requires the `MANAGE_GUILD` [permission](/docs/resources/auto-moderation#auto-moderation-permission-requirements).
-:::
-
-## Get Auto Moderation Rule
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules/[\{auto_moderation_rule.id\}](/docs/resources/auto-moderation#auto-moderation-rule-object)
-
-Get a single rule. Returns an [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) object.
-
-:::info
-This endpoint requires the `MANAGE_GUILD` [permission](/docs/resources/auto-moderation#auto-moderation-permission-requirements).
-:::
-
-## Create Auto Moderation Rule
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules
-
-Create a new rule. Returns an [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) on success. Fires an [Auto Moderation Rule Create](/docs/events/gateway-events#auto-moderation-rule-create) Gateway event.
-
-:::info
-This endpoint requires the `MANAGE_GUILD` [permission](/docs/resources/auto-moderation#auto-moderation-permission-requirements).
-:::
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|---------------------|------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|
-| name | string | the rule name |
-| event_type | integer | the [event type](/docs/resources/auto-moderation#auto-moderation-rule-object-event-types) |
-| trigger_type | integer | the [trigger type](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) |
-| trigger_metadata? * | object | the [trigger metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) |
-| actions | array of [action](/docs/resources/auto-moderation#auto-moderation-action-object) objects | the actions which will execute when the rule is triggered |
-| enabled? | boolean | whether the rule is enabled (False by default) |
-| exempt_roles? | array of snowflakes | the role ids that should not be affected by the rule (Maximum of 20) |
-| exempt_channels? | array of snowflakes | the channel ids that should not be affected by the rule (Maximum of 50) |
-
-\* Can be omitted based on `trigger_type`. See the `Associated Trigger Types` column in [trigger metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) to understand which `trigger_type` values require `trigger_metadata` to be set.
-
-:::info
-See [Trigger Types](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types) for limits on how many rules of each trigger type can be created per guild.
-:::
-
-
-## Modify Auto Moderation Rule
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules/[\{auto_moderation_rule.id\}](/docs/resources/auto-moderation#auto-moderation-rule-object)
-
-Modify an existing rule. Returns an [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) on success. Fires an [Auto Moderation Rule Update](/docs/events/gateway-events#auto-moderation-rule-update) Gateway event.
-
-:::info
-Requires `MANAGE_GUILD` [permissions](/docs/resources/auto-moderation#auto-moderation-permission-requirements).
-:::
-
-:::info
-All parameters for this endpoint are optional.
-:::
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|---------------------|------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|
-| name | string | the rule name |
-| event_type | integer | the [event type](/docs/resources/auto-moderation#auto-moderation-rule-object-event-types) |
-| trigger_metadata? * | object | the [trigger metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) |
-| actions | array of [action](/docs/resources/auto-moderation#auto-moderation-action-object) objects | the actions which will execute when the rule is triggered |
-| enabled | boolean | whether the rule is enabled |
-| exempt_roles | array of snowflakes | the role ids that should not be affected by the rule (Maximum of 20) |
-| exempt_channels | array of snowflakes | the channel ids that should not be affected by the rule (Maximum of 50) |
-
-\* Can be omitted based on `trigger_type`. See the `Associated Trigger Types` column in [trigger metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) to understand which `trigger_type` values require `trigger_metadata` to be set.
-
-## Delete Auto Moderation Rule
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules/[\{auto_moderation_rule.id\}](/docs/resources/auto-moderation#auto-moderation-rule-object)
-
-Delete a rule. Returns a `204` on success. Fires an [Auto Moderation Rule Delete](/docs/events/gateway-events#auto-moderation-rule-delete) Gateway event.
-
-:::info
-This endpoint requires the `MANAGE_GUILD` [permission](/docs/resources/auto-moderation#auto-moderation-permission-requirements).
-:::
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
diff --git a/docs/resources/emoji.mdx b/docs/resources/emoji.mdx
deleted file mode 100644
index f69fe6ce62..0000000000
--- a/docs/resources/emoji.mdx
+++ /dev/null
@@ -1,230 +0,0 @@
----
-sidebar_label: Emoji
----
-
-# Emoji Resource
-
-:::warn
-Routes for controlling emojis do not follow the normal rate limit conventions. These routes are specifically limited on a per-guild basis to prevent abuse. This means that the quota returned by our APIs may be inaccurate, and you may encounter 429s.
-:::
-
-### Emoji Object
-
-###### Emoji Structure
-
-| Field | Type | Description |
-|-----------------|------------------------------------------------------------------|---------------------------------------------------------------------------|
-| id | ?snowflake | [emoji id](/docs/reference#image-formatting) |
-| name | ?string (can be null only in reaction emoji objects) | emoji name |
-| roles? | array of [role](/docs/topics/permissions#role-object) object ids | roles allowed to use this emoji |
-| user? | [user](/docs/resources/user#user-object) object | user that created this emoji |
-| require_colons? | boolean | whether this emoji must be wrapped in colons |
-| managed? | boolean | whether this emoji is managed |
-| animated? | boolean | whether this emoji is animated |
-| available? | boolean | whether this emoji can be used, may be false due to loss of Server Boosts |
-
-###### Premium Emoji
-
-Roles with the `integration_id` tag being the guild's guild_subscription integration are considered subscription roles.
-An emoji cannot have both subscription roles and non-subscription roles.
-Emojis with subscription roles are considered premium emoji, and count toward a separate limit of 25.
-Emojis cannot be converted between normal and premium after creation.
-
-###### Emoji Formats
-
-Emoji can be uploaded as JPEG, PNG, GIF, WebP, and AVIF formats. All emoji (regardless of original format) can be served as WebP. We highly recommend that developers use the `.webp` extension when fetching emoji so they're rendered as WebP for maximum performance and compatibility. The Discord client uses WebP for all emoji displayed in-app.
-
-Still WebP emoji can be requested using the `.webp` file extension. For animated WebP emoji, use the `.webp` extension with the `?animated=true` query parameter.
-
-###### Application-Owned Emoji
-
-An application can own up to 2000 emojis that can only be used by that app.
-App emojis can be managed using the API with a bot token, or using the app's settings in the portal.
-The `USE_EXTERNAL_EMOJIS` permission is not required to use app emojis.
-The `user` field of an app emoji object represents the team member that uploaded the emoji from the app's settings, or the bot user if uploaded using the API.
-
-###### Emoji Example
-
-```json
-{
- "id": "41771983429993937",
- "name": "LUL",
- "roles": ["41771983429993000", "41771983429993111"],
- "user": {
- "username": "Luigi",
- "discriminator": "0002",
- "id": "96008815106887111",
- "avatar": "5500909a3274e1812beb4e8de6631111",
- "public_flags": 131328
- },
- "require_colons": true,
- "managed": false,
- "animated": false
-}
-```
-
-###### Standard Emoji Example
-
-```json
-{
- "id": null,
- "name": "🔥"
-}
-```
-
-###### Custom Emoji Examples
-
-:::info
-In `MESSAGE_REACTION_ADD`, `MESSAGE_REACTION_REMOVE` and `MESSAGE_REACTION_REMOVE_EMOJI` gateway events `animated` will be returned for animated emoji.
-:::
-
-:::info
-In `MESSAGE_REACTION_ADD` and `MESSAGE_REACTION_REMOVE` gateway events `name` may be `null` when custom emoji data is not available (for example, if it was deleted from the guild).
-:::
-
-```json
-{
- "id": "41771983429993937",
- "name": "LUL",
- "animated": true
-}
-```
-
-```json
-{
- "id": "41771983429993937",
- "name": null
-}
-```
-
-## List Guild Emojis
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/emojis
-
-Returns a list of [emoji](/docs/resources/emoji#emoji-object) objects for the given guild. Includes `user` fields if the bot has the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission.
-
-## Get Guild Emoji
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/emojis/[\{emoji.id\}](/docs/resources/emoji#emoji-object)
-
-Returns an [emoji](/docs/resources/emoji#emoji-object) object for the given guild and emoji IDs. Includes the `user` field if the bot has the `MANAGE_GUILD_EXPRESSIONS` permission, or if the bot created the emoji and has the the `CREATE_GUILD_EXPRESSIONS` permission.
-
-## Create Guild Emoji
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/emojis
-
-Create a new emoji for the guild. Requires the `CREATE_GUILD_EXPRESSIONS` permission. Returns the new [emoji](/docs/resources/emoji#emoji-object) object on success. Fires a [Guild Emojis Update](/docs/events/gateway-events#guild-emojis-update) Gateway event.
-
-:::warn
-Emojis and animated emojis have a maximum file size of 256 KiB. Attempting to upload an emoji larger than this limit will fail and return 400 Bad Request and an error message, but not a [JSON status code](/docs/topics/opcodes-and-status-codes#json).
-:::
-
-:::info
-We highly recommend that developers use the `.webp` extension when fetching emoji so they're rendered as WebP for maximum performance and compatibility. See the [Emoji Formats](/docs/resources/emoji#emoji-object-emoji-formats) section above for more details.
-:::
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|-------|------------------------------------------|---------------------------------|
-| name | string | name of the emoji |
-| image | [image data](/docs/reference#image-data) | the 128x128 emoji image |
-| roles | array of snowflakes | roles allowed to use this emoji |
-
-## Modify Guild Emoji
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/emojis/[\{emoji.id\}](/docs/resources/emoji#emoji-object)
-
-Modify the given emoji. For emojis created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other emojis, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns the updated [emoji](/docs/resources/emoji#emoji-object) object on success. Fires a [Guild Emojis Update](/docs/events/gateway-events#guild-emojis-update) Gateway event.
-
-:::info
-All parameters to this endpoint are optional.
-:::
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|-------|----------------------|---------------------------------|
-| name | string | name of the emoji |
-| roles | ?array of snowflakes | roles allowed to use this emoji |
-
-## Delete Guild Emoji
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/emojis/[\{emoji.id\}](/docs/resources/emoji#emoji-object)
-
-Delete the given emoji. For emojis created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other emojis, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns `204 No Content` on success. Fires a [Guild Emojis Update](/docs/events/gateway-events#guild-emojis-update) Gateway event.
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-## List Application Emojis
-/applications/[\{application.id\}](/docs/resources/application#application-object)/emojis
-
-Returns an object containing a list of [emoji](/docs/resources/emoji#emoji-object) objects for the given application under the `items` key. Includes a `user` object for the team member that uploaded the emoji from the app's settings, or for the bot user if uploaded using the API.
-
-```json
-{
- "items": [
- {
- "id": "41771983429993937",
- "name": "LUL",
- "roles": [],
- "user": {
- "username": "Luigi",
- "discriminator": "0002",
- "id": "96008815106887111",
- "avatar": "5500909a3274e1812beb4e8de6631111",
- "public_flags": 131328
- },
- "require_colons": true,
- "managed": false,
- "animated": false
- }
- ]
-}
-```
-
-## Get Application Emoji
-/applications/[\{application.id\}](/docs/resources/application#application-object)/emojis/[\{emoji.id\}](/docs/resources/emoji#emoji-object)
-
-Returns an [emoji](/docs/resources/emoji#emoji-object) object for the given application and emoji IDs. Includes the `user` field.
-
-## Create Application Emoji
-/applications/[\{application.id\}](/docs/resources/application#application-object)/emojis
-
-Create a new emoji for the application. Returns the new [emoji](/docs/resources/emoji#emoji-object) object on success.
-
-:::warn
-Emojis and animated emojis have a maximum file size of 256 KiB. Attempting to upload an emoji larger than this limit will fail and return 400 Bad Request and an error message, but not a [JSON status code](/docs/topics/opcodes-and-status-codes#json).
-:::
-
-:::info
-We highly recommend that developers use the `.webp` extension when fetching emoji so they're rendered as WebP for maximum performance and compatibility. See the [Emoji Formats](/docs/resources/emoji#emoji-object-emoji-formats) section above for more details.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|-------|------------------------------------------|-------------------------|
-| name | string | name of the emoji |
-| image | [image data](/docs/reference#image-data) | the 128x128 emoji image |
-
-## Modify Application Emoji
-/applications/[\{application.id\}](/docs/resources/application#application-object)/emojis/[\{emoji.id\}](/docs/resources/emoji#emoji-object)
-
-Modify the given emoji. Returns the updated [emoji](/docs/resources/emoji#emoji-object) object on success.
-
-###### JSON Params
-
-| Field | Type | Description |
-|-------|--------|-------------------|
-| name | string | name of the emoji |
-
-## Delete Application Emoji
-/applications/[\{application.id\}](/docs/resources/application#application-object)/emojis/[\{emoji.id\}](/docs/resources/emoji#emoji-object)
-
-Delete the given emoji. Returns `204 No Content` on success.
diff --git a/docs/resources/guild-template.mdx b/docs/resources/guild-template.mdx
deleted file mode 100644
index 063b218bdd..0000000000
--- a/docs/resources/guild-template.mdx
+++ /dev/null
@@ -1,144 +0,0 @@
----
-sidebar_label: Guild Template
----
-
-# Guild Template Resource
-
-### Guild Template Object
-
-Represents a code that when used, creates a guild based on a snapshot of an existing guild.
-
-###### Guild Template Structure
-
-| Field | Type | Description |
-|-------------------------|------------------------------------------------------------|----------------------------------------------------------------------------------|
-| code | string | the template code (unique ID) |
-| name | string | template name |
-| description | ?string | the description for the template |
-| usage_count | integer | number of times this template has been used |
-| creator_id | snowflake | the ID of the user who created the template |
-| creator | [user](/docs/resources/user#user-object) object | the user who created the template |
-| created_at | ISO8601 timestamp | when this template was created |
-| updated_at | ISO8601 timestamp | when this template was last synced to the source guild |
-| source_guild_id | snowflake | the ID of the guild this template is based on |
-| serialized_source_guild | partial [guild](/docs/resources/guild#guild-object) object | the guild snapshot this template contains; placeholder IDs are given as integers |
-| is_dirty | ?boolean | whether the template has unsynced changes |
-
-###### Example Guild Template Object
-
-```json
-{
- "code": "hgM48av5Q69A",
- "name": "Friends & Family",
- "description": "",
- "usage_count": 49605,
- "creator_id": "132837293881950208",
- "creator": {
- "id": "132837293881950208",
- "username": "hoges",
- "avatar": "79b0d9f8c340f2d43e1f78b09f175b62",
- "discriminator": "0001",
- "public_flags": 129
- },
- "created_at": "2020-04-02T21:10:38+00:00",
- "updated_at": "2020-05-01T17:57:38+00:00",
- "source_guild_id": "678070694164299796",
- "serialized_source_guild": {
- "name": "Friends & Family",
- "description": null,
- "region": "us-west",
- "verification_level": 0,
- "default_message_notifications": 0,
- "explicit_content_filter": 0,
- "preferred_locale": "en-US",
- "afk_timeout": 300,
- "roles": [
- {
- "id": 0,
- "name": "@everyone",
- "permissions": 104324689,
- "color": 0,
- "hoist": false,
- "mentionable": false
- }
- ],
- "channels": [
- {
- "name": "Text Channels",
- "position": 1,
- "topic": null,
- "bitrate": 64000,
- "user_limit": 0,
- "nsfw": false,
- "rate_limit_per_user": 0,
- "parent_id": null,
- "permission_overwrites": [],
- "id": 1,
- "type": 4
- },
- {
- "name": "general",
- "position": 1,
- "topic": null,
- "bitrate": 64000,
- "user_limit": 0,
- "nsfw": false,
- "rate_limit_per_user": 0,
- "parent_id": 1,
- "permission_overwrites": [],
- "id": 2,
- "type": 0
- }
- ],
- "afk_channel_id": null,
- "system_channel_id": 2,
- "system_channel_flags": 0,
- "icon_hash": null
- },
- "is_dirty": null
-}
-```
-
-## Get Guild Template
-/guilds/templates/[\{template.code\}](/docs/resources/guild-template#guild-template-object)
-
-Returns a [guild template](/docs/resources/guild-template#guild-template-object) object for the given code.
-
-## Get Guild Templates
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/templates
-
-Returns an array of [guild template](/docs/resources/guild-template#guild-template-object) objects. Requires the `MANAGE_GUILD` permission.
-
-## Create Guild Template
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/templates
-
-Creates a template for the guild. Requires the `MANAGE_GUILD` permission. Returns the created [guild template](/docs/resources/guild-template#guild-template-object) object on success.
-
-###### JSON Params
-
-| Field | Type | Description |
-|--------------|---------|-------------------------------------------------|
-| name | string | name of the template (1-100 characters) |
-| description? | ?string | description for the template (0-120 characters) |
-
-## Sync Guild Template
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/templates/[\{template.code\}](/docs/resources/guild-template#guild-template-object)
-
-Syncs the template to the guild's current state. Requires the `MANAGE_GUILD` permission. Returns the [guild template](/docs/resources/guild-template#guild-template-object) object on success.
-
-## Modify Guild Template
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/templates/[\{template.code\}](/docs/resources/guild-template#guild-template-object)
-
-Modifies the template's metadata. Requires the `MANAGE_GUILD` permission. Returns the [guild template](/docs/resources/guild-template#guild-template-object) object on success.
-
-###### JSON Params
-
-| Field | Type | Description |
-|--------------|---------|-------------------------------------------------|
-| name? | string | name of the template (1-100 characters) |
-| description? | ?string | description for the template (0-120 characters) |
-
-## Delete Guild Template
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/templates/[\{template.code\}](/docs/resources/guild-template#guild-template-object)
-
-Deletes the template. Requires the `MANAGE_GUILD` permission. Returns the deleted [guild template](/docs/resources/guild-template#guild-template-object) object on success.
diff --git a/docs/resources/invite.mdx b/docs/resources/invite.mdx
deleted file mode 100644
index 333c1f3e03..0000000000
--- a/docs/resources/invite.mdx
+++ /dev/null
@@ -1,173 +0,0 @@
----
-sidebar_label: Invite
----
-
-# Invite Resource
-
-### Invite Object
-
-Represents a code that when used, adds a user to a guild or group DM channel.
-
-###### Invite Structure
-
-| Field | Type | Description |
-|-----------------------------|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
-| type | integer | the [type of invite](/docs/resources/invite#invite-object-invite-types) |
-| code | string | the invite code (unique ID) |
-| guild? | partial [guild](/docs/resources/guild#guild-object) object | the guild this invite is for |
-| channel | ?partial [channel](/docs/resources/channel#channel-object) object | the channel this invite is for |
-| inviter? | [user](/docs/resources/user#user-object) object | the user who created the invite |
-| target_type? | integer | the [type of target](/docs/resources/invite#invite-object-invite-target-types) for this voice channel invite |
-| target_user? | [user](/docs/resources/user#user-object) object | the user whose stream to display for this voice channel stream invite |
-| target_application? | partial [application](/docs/resources/application#application-object) object | the embedded application to open for this voice channel embedded application invite |
-| approximate_presence_count? | integer | approximate count of online members, returned from the `GET /invites/` endpoint when `with_counts` is `true` |
-| approximate_member_count? | integer | approximate count of total members, returned from the `GET /invites/` endpoint when `with_counts` is `true` |
-| expires_at | ?ISO8601 timestamp | the expiration date of this invite |
-| guild_scheduled_event? | [guild scheduled event](/docs/resources/guild-scheduled-event#guild-scheduled-event-object) object | guild scheduled event data, only included if `guild_scheduled_event_id` contains a valid guild scheduled event id |
-| flags? | integer | [guild invite flags](/docs/resources/invite#invite-object-guild-invite-flags) for guild invites |
-
-###### Invite Types
-
-| Type | Value |
-|----------|-------|
-| GUILD | 0 |
-| GROUP_DM | 1 |
-| FRIEND | 2 |
-
-###### Invite Target Types
-
-| Type | Value |
-|----------------------|-------|
-| STREAM | 1 |
-| EMBEDDED_APPLICATION | 2 |
-
-###### Guild Invite Flags
-
-| Flag | Value | Description |
-|-----------------|----------|---------------------------------------------------|
-| IS_GUEST_INVITE | `1 << 0` | this invite is a guest invite for a voice channel |
-
-###### Example Invite Object
-
-```json
-{
- "type": 0,
- "code": "0vCdhLbwjZZTWZLD",
- "guild": {
- "id": "165176875973476352",
- "name": "CS:GO Fraggers Only",
- "splash": null,
- "banner": null,
- "description": "Very good description",
- "icon": null,
- "features": ["NEWS", "DISCOVERABLE"],
- "verification_level": 2,
- "vanity_url_code": null,
- "nsfw_level": 0,
- "premium_subscription_count": 5
- },
- "channel": {
- "id": "165176875973476352",
- "name": "illuminati",
- "type": 0
- },
- "inviter": {
- "id": "115590097100865541",
- "username": "speed",
- "avatar": "deadbeef",
- "discriminator": "7653",
- "public_flags": 131328
- },
- "target_type": 1,
- "target_user": {
- "id": "165176875973476352",
- "username": "bob",
- "avatar": "deadbeef",
- "discriminator": "1234",
- "public_flags": 64
- }
-}
-```
-
-### Invite Metadata Object
-
-Extra information about an invite, will extend the [invite](/docs/resources/invite#invite-object) object.
-
-###### Invite Metadata Structure
-
-| Field | Type | Description |
-|------------|-------------------|------------------------------------------------------|
-| uses | integer | number of times this invite has been used |
-| max_uses | integer | max number of times this invite can be used |
-| max_age | integer | duration (in seconds) after which the invite expires |
-| temporary | boolean | whether this invite only grants temporary membership |
-| created_at | ISO8601 timestamp | when this invite was created |
-
-###### Example Invite Metadata
-
-```json
-{
- "uses": 0,
- "max_uses": 0,
- "max_age": 0,
- "temporary": false,
- "created_at": "2016-03-31T19:15:39.954000+00:00"
-}
-```
-
-### Invite Stage Instance Object
-
-:::warn
-This is deprecated.
-:::
-
-###### Invite Stage Instance Structure
-
-| Field | Type | Description |
-|-------------------|------------------------------------------------------------------------------------|----------------------------------------------------|
-| members | array of partial [guild member](/docs/resources/guild#guild-member-object) objects | the members speaking in the Stage |
-| participant_count | integer | the number of users in the Stage |
-| speaker_count | integer | the number of users speaking in the Stage |
-| topic | string | the topic of the Stage instance (1-120 characters) |
-
-###### Example Invite Stage Instance
-
-```json
-{
- "topic": "The debate is over: diet is better than regular",
- "participant_count": 200,
- "speaker_count": 5 ,
- "members": [
- {
- "roles": [],
- "nick": "NOT API SUPPORT",
- "avatar": null,
- "premium_since": null,
- "joined_at": "2015-04-26T06:26:56.936000+00:00",
- "pending": false,
- "user": {}
- }
- ]
-}
-```
-
-## Get Invite
-/invites/[\{invite.code\}](/docs/resources/invite#invite-object)
-
-Returns an [invite](/docs/resources/invite#invite-object) object for the given code.
-
-###### Query String Params
-
-| Field | Type | Description |
-|---------------------------|--------------------------------------------------|-------------------------------------------------------------|
-| with_counts? | [boolean](/docs/reference#boolean-query-strings) | whether the invite should contain approximate member counts |
-| guild_scheduled_event_id? | snowflake | the guild scheduled event to include with the invite |
-
-## Delete Invite
-/invites/[\{invite.code\}](/docs/resources/invite#invite-object)
-
-Delete an invite. Requires the `MANAGE_CHANNELS` permission on the channel this invite belongs to, or `MANAGE_GUILD` to remove any invite across the guild. Returns an [invite](/docs/resources/invite#invite-object) object on success. Fires an [Invite Delete](/docs/events/gateway-events#invite-delete) Gateway event.
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
diff --git a/docs/resources/lobby.mdx b/docs/resources/lobby.mdx
deleted file mode 100644
index c3b08eedef..0000000000
--- a/docs/resources/lobby.mdx
+++ /dev/null
@@ -1,173 +0,0 @@
----
-sidebar_label: Lobby
----
-
-# Lobby Resource
-
-### Lobby Object
-
-Represents a lobby within Discord. See [Managing Lobbies](/docs/discord-social-sdk/development-guides/managing-lobbies) for more information.
-
-###### Lobby Structure
-
-| Field | Type | Description |
-|-----------------|----------------------------------------------------------------------------|---------------------------------------------------------------------|
-| id | snowflake | the id of this channel |
-| application_id | snowflake | application that created the lobby |
-| metadata | ?dict\ | dictionary of string key/value pairs. The max total length is 1000. |
-| members | array of [lobby member](/docs/resources/lobby#lobby-member-object) objects | members of the lobby |
-| linked_channel? | channel object | the guild channel linked to the lobby |
-
-### Lobby Member Object
-
-Represents a member of a lobby, including optional metadata and flags.
-
-###### Lobby Member Structure
-
-| Field | Type | Description |
-|-----------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
-| id | snowflake | the id of the user |
-| metadata? | ?dict\ | dictionary of string key/value pairs. The max total length is 1000. |
-| flags? | integer | [lobby member flags](/docs/resources/lobby#lobby-member-object-lobby-member-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |
-
-###### Lobby Member Flags
-
-| Flag | Value | Description |
-|--------------|--------|-----------------------------------------|
-| CanLinkLobby | `1<<0` | user can link a text channel to a lobby |
-
-
-###### Example Lobby Object
-
-```json
-{
- "id": "96008815106887111",
- "application_id": "41771983429993937",
- "metadata": {
- "topic": "we need more redstone",
- },
- "members": [
- {
- "id": "41771983429993000",
- "metadata": null,
- "flags": 1
- }
- ]
-}
-```
-
-## Create Lobby
-/lobbies
-
-Creates a new lobby, adding any of the specified members to it, if provided.
-
-Returns a [lobby](/docs/resources/lobby#lobby-object) object.
-
-:::info
-[Discord Social SDK](/docs/discord-social-sdk/overview) clients will not be able to join or leave a lobby created using this API, such as [`Client::CreateOrJoinLobby`]. See [Managing Lobbies](/docs/discord-social-sdk/development-guides/managing-lobbies) for more information.
-:::
-
-### JSON Params
-
-| Field | Type | Description |
-|-----------------------|----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| metadata? | ?dict\ | optional dictionary of string key/value pairs. The max total length is 1000. |
-| members? | array of [lobby member](/docs/resources/lobby#lobby-member-object) objects | optional array of up to 25 users to be added to the lobby |
-| idle_timeout_seconds? | integer | seconds to wait before shutting down a lobby after it becomes idle. Value can be between 5 and 604800 (7 days). See [`LobbyHandle`] for more details on this behavior. |
-
-#### Lobby Member JSON Params
-
-| Field | Type | Description |
-|-----------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
-| id | snowflake | Discord user id of the user to add to the lobby |
-| metadata? | ?dict\ | optional dictionary of string key/value pairs. The max total length is 1000. |
-| flags? | integer | [lobby member flags](/docs/resources/lobby#lobby-member-object-lobby-member-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |
-
-## Get Lobby
-/lobbies/[\{lobby.id\}](/docs/resources/lobby#lobby-object)
-
-Returns a [lobby](/docs/resources/lobby#lobby-object) object for the specified lobby id, if it exists.
-
-## Modify Lobby
-/lobbies/[\{lobby.id\}](/docs/resources/lobby#lobby-object)
-
-Modifies the specified lobby with new values, if provided.
-
-Returns the updated [lobby](/docs/resources/lobby#lobby-object) object.
-
-### JSON Params
-
-| Field | Type | Description |
-|-----------------------|----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| metadata? | ?dict\ | optional dictionary of string key/value pairs. The max total length is 1000. Overwrites any existing metadata. |
-| members? | array of [lobby member](/docs/resources/lobby#lobby-member-object) objects | optional array of up to 25 users to replace the lobby members with. If provided, lobby members not in this list will be removed from the lobby. |
-| idle_timeout_seconds? | integer | seconds to wait before shutting down a lobby after it becomes idle. Value can be between 5 and 604800 (7 days). See [`LobbyHandle`] for more details on this behavior. |
-
-## Delete Lobby
-/lobbies/[\{lobby.id\}](/docs/resources/lobby#lobby-object)
-
-Deletes the specified lobby if it exists.
-
-It is safe to call even if the lobby is already deleted as well.
-
-Returns nothing.
-
-## Add a Member to a Lobby
-/lobbies/[\{lobby.id\}](/docs/resources/lobby#lobby-object)/members/[\{user.id\}](/docs/resources/user#user-object)
-
-Adds the provided user to the specified lobby. If called when the user is already a member of the lobby will update fields such as metadata on that user instead.
-
-Returns the [lobby member](/docs/resources/lobby#lobby-member-object) object.
-
-### JSON Params
-
-| Field | Type | Description |
-|-----------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
-| metadata? | ?dict\ | optional dictionary of string key/value pairs. The max total length is 1000. |
-| flags? | integer | [lobby member flags](/docs/resources/lobby#lobby-member-object-lobby-member-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |
-
-## Remove a Member from a Lobby
-/lobbies/[\{lobby.id\}](/docs/resources/lobby#lobby-object)/members/[\{user.id\}](/docs/resources/user#user-object)
-
-Removes the provided user from the specified lobby. It is safe to call this even if the user is no longer a member of the lobby, but will fail if the lobby does not exist.
-
-Returns nothing.
-
-## Leave Lobby
-/lobbies/[\{lobby.id\}](/docs/resources/lobby#lobby-object)/members/@me
-
-Removes the current user from the specified lobby. It is safe to call this even if the user is no longer a member of the lobby, but will fail if the lobby does not exist.
-
-Uses `Bearer` token for authorization.
-
-Returns nothing.
-
-## Link Channel to Lobby
-/lobbies/[\{lobby.id\}](/docs/resources/lobby#lobby-object)/channel-linking
-
-Links an existing text channel to a lobby. See [Linked Channels](/docs/discord-social-sdk/development-guides/linked-channels) for more information.
-
-Uses `Bearer` token for authorization and user must be a lobby member with `CanLinkLobby` [lobby member flag](/docs/resources/lobby#lobby-member-object-lobby-member-flags).
-
-Returns a [lobby](/docs/resources/lobby#lobby-object) object with a linked channel.
-
-### JSON Params
-
-| Field | Type | Description |
-|-------------|-----------|------------------------------------------------------------------------------------------------------------------------|
-| channel_id? | snowflake | the id of the channel to link to the lobby. If not provided, will unlink any currently linked channels from the lobby. |
-
-## Unlink Channel from Lobby
-/lobbies/[\{lobby.id\}](/docs/resources/lobby#lobby-object)/channel-linking
-
-Unlinks any currently linked channels from the specified lobby.
-
-Send a request to this endpoint with an empty body to unlink any currently linked channels from the specified lobby.
-
-Uses `Bearer` token for authorization and user must be a lobby member with `CanLinkLobby` [lobby member flag](/docs/resources/lobby#lobby-member-object-lobby-member-flags).
-
-Returns a [lobby](/docs/resources/lobby#lobby-object) object without a linked channel.
-
-{/* Autogenerated Reference Links */}
-[`Client::CreateOrJoinLobby`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#a8b4e195555ecaa89ccdfc0acd28d3512
-[`LobbyHandle`]: https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1LobbyHandle.html#a04cebab69ab0e7fb930346a14a87e843
\ No newline at end of file
diff --git a/docs/resources/poll.mdx b/docs/resources/poll.mdx
deleted file mode 100644
index 2543a894d8..0000000000
--- a/docs/resources/poll.mdx
+++ /dev/null
@@ -1,149 +0,0 @@
----
-sidebar_label: Poll
----
-
-# Poll Resource
-
-A poll is... well... a poll! It holds information about a poll!
-
-
-
-### Poll Object
-
-The poll object has a lot of levels and nested structures. It was also designed
-to support future extensibility, so some fields may appear to be more complex than
-necessary.
-
-###### Poll Object Structure
-
-| Field | Type | Description |
-|-------------------|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|
-| question | [Poll Media Object](/docs/resources/poll#poll-media-object-poll-media-object-structure) | The question of the poll. Only `text` is supported. |
-| answers | List of [Poll Answer Objects](/docs/resources/poll#poll-answer-object-poll-answer-object-structure) | Each of the answers available in the poll. |
-| expiry | ?IS08601 timestamp | The time when the poll ends. |
-| allow_multiselect | boolean | Whether a user can select multiple answers |
-| layout_type | integer | The [layout type](/docs/resources/poll#layout-type) of the poll |
-| results? | [Poll Results Object](/docs/resources/poll#poll-results-object-poll-results-object-structure) | The results of the poll |
-
-`expiry` is marked as nullable to support non-expiring polls in the future, but all polls have an expiry currently.
-
-### Poll Create Request Object
-
-This is the request object used when creating a poll across the different endpoints.
-It is similar but not exactly identical to the main [poll object](/docs/resources/poll#poll-object-poll-object-structure).
-The main difference is that the request has `duration` which eventually becomes `expiry`.
-
-###### Poll Create Request Object Structure
-
-| Field | Type | Description |
-|--------------------|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|
-| question | [Poll Media Object](/docs/resources/poll#poll-media-object-poll-media-object-structure) | The question of the poll. Only `text` is supported. |
-| answers | List of [Poll Answer Objects](/docs/resources/poll#poll-answer-object-poll-answer-object-structure) | Each of the answers available in the poll, up to 10 |
-| duration? | integer | Number of hours the poll should be open for, up to 32 days. Defaults to 24 |
-| allow_multiselect? | boolean | Whether a user can select multiple answers. Defaults to false |
-| layout_type? | integer | The [layout type](/docs/resources/poll#layout-type) of the poll. Defaults to... DEFAULT! |
-
-### Layout Type
-
-We might have different layouts for polls in the future.
-For now though, this number will be 1.
-
-| Type | ID | Description |
-|---------|----|--------------------------------|
-| DEFAULT | 1 | The, uhm, default layout type. |
-
-### Poll Media Object
-
-The poll media object is a common object that backs both the question and answers.
-The intention is that it allows us to extensibly add new ways to display things in the future.
-For now, `question` only supports `text`, while answers can have an optional `emoji`.
-
-###### Poll Media Object Structure
-
-| Field | Type | Description |
-|--------|-----------------------------------------------------|------------------------|
-| text? | string | The text of the field |
-| emoji? | partial [emoji](/docs/resources/emoji#emoji-object) | The emoji of the field |
-
-`text` should always be non-null for both questions and answers, but please do not depend on that in the future.
-The maximum length of `text` is 300 for the question, and 55 for any answer.
-
-When creating a poll answer with an emoji, one only needs to send either the `id` (custom emoji) or `name` (default emoji) as the only field.
-
-### Poll Answer Object
-
-The `answer_id` is a number that labels each answer.
-As an implementation detail, it currently starts at 1 for the first answer and goes up sequentially.
-We recommend against depending on this sequence.
-
-Currently, there is a maximum of 10 answers per poll.
-
-###### Poll Answer Object Structure
-
-| Field | Type | Description |
-|-------------|-----------------------------------------------------------------------------------------|------------------------|
-| answer_id\* | integer | The ID of the answer |
-| poll_media | [Poll Media Object](/docs/resources/poll#poll-media-object-poll-media-object-structure) | The data of the answer |
-
-\* Only sent as part of responses from Discord's API/Gateway.
-
-### Poll Results Object
-
-In a nutshell, this contains the number of votes for each answer.
-
-The `results` field may be not present in certain responses where, as an implementation detail, we do not fetch the poll results in our backend.
-This should be treated as "unknown results", as opposed to "no results". You can keep using the results if you have previously received them through other means.
-
-Also due to the intricacies of counting at scale, while a poll is in progress the results may not be perfectly accurate.
-They usually are accurate, and shouldn't deviate significantly -- it's just difficult to make guarantees.
-
-To compensate for this, after a poll is finished there is a background job which performs a final, accurate tally of votes.
-This tally concludes once `is_finalized` is `true`. Polls that have ended will also always contain results.
-
-If `answer_counts` does not contain an entry for a particular answer, then there are no votes for that answer.
-
-###### Poll Results Object Structure
-
-| Field | Type | Description |
-|---------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------|
-| is_finalized | boolean | Whether the votes have been precisely counted |
-| answer_counts | List of [Poll Answer Count Object](/docs/resources/poll#poll-results-object-poll-answer-count-object-structure) | The counts for each answer |
-
-###### Poll Answer Count Object Structure
-
-| Field | Type | Description |
-|----------|---------|------------------------------------------------|
-| id | integer | The `answer_id` |
-| count | integer | The number of votes for this answer |
-| me_voted | boolean | Whether the current user voted for this answer |
-
-# Poll Endpoints
-
-For creating a poll, see [Create Message](/docs/resources/message#create-message). After creation, the poll message cannot be edited.
-
-Apps are not allowed to vote on polls. No rights! :)
-
-## Get Answer Voters
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/polls/[\{message.id\}](/docs/resources/message#message-object)/answers/[\{answer_id\}](/docs/resources/poll#poll-answer-object)
-
-Get a list of users that voted for this specific answer.
-
-###### Query String Params
-
-| Field | Type | Description | Default |
-|--------|-----------|---------------------------------------|---------|
-| after? | snowflake | Get users after this user ID | absent |
-| limit? | integer | Max number of users to return (1-100) | 25 |
-
-###### Response Body
-
-| Field | Type | Description |
-|-------|---------------------------------------------------|---------------------------------|
-| users | array of [user](/docs/resources/user#user-object) | Users who voted for this answer |
-
-## End Poll
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/polls/[\{message.id\}](/docs/resources/message#message-object)/expire
-
-Immediately ends the poll. You cannot end polls from other users.
-
-Returns a [message](/docs/resources/message#message-object) object. Fires a [Message Update](/docs/events/gateway-events#message-update) Gateway event.
diff --git a/docs/resources/soundboard.mdx b/docs/resources/soundboard.mdx
deleted file mode 100644
index f723d282b1..0000000000
--- a/docs/resources/soundboard.mdx
+++ /dev/null
@@ -1,150 +0,0 @@
----
-sidebar_label: Soundboard
----
-
-# Soundboard Resource
-
-Users can play soundboard sounds in voice channels, triggering a [Voice Channel Effect Send](/docs/events/gateway-events#voice-channel-effect-send) Gateway event for users connected to the voice channel.
-
-There is a set of [default sounds](/docs/resources/soundboard#list-default-soundboard-sounds) available to all users. Soundboard sounds can also be [created in a guild](/docs/resources/soundboard#create-guild-soundboard-sound); users will be able to use the sounds in the guild, and Nitro subscribers can use them in all guilds.
-
-Soundboard sounds in a set of guilds can be retrieved over the Gateway using [Request Soundboard Sounds](/docs/events/gateway-events#request-soundboard-sounds).
-
-### Soundboard Sound Object
-
-###### Soundboard Sound Structure
-
-| Field | Type | Description |
-|------------|-------------------------------------------------|---------------------------------------------------------------------------|
-| name | string | the name of this sound |
-| sound_id | snowflake | the id of this sound |
-| volume | double | the volume of this sound, from 0 to 1 |
-| emoji_id | ?snowflake | the id of this sound's custom emoji |
-| emoji_name | ?string | the unicode character of this sound's standard emoji |
-| guild_id? | snowflake | the id of the guild this sound is in |
-| available | boolean | whether this sound can be used, may be false due to loss of Server Boosts |
-| user? | [user](/docs/resources/user#user-object) object | the user who created this sound |
-
-###### Example Default Soundboard Sound
-
-```json
-{
- "name": "quack",
- "sound_id": "1",
- "volume": 1.0,
- "emoji_id": null,
- "emoji_name": "🦆",
- "available": true
-}
-```
-
-###### Example Guild Soundboard Sound
-
-```json
-{
- "name": "Yay",
- "sound_id": "1106714396018884649",
- "volume": 1,
- "emoji_id": "989193655938064464",
- "emoji_name": null,
- "guild_id": "613425648685547541",
- "available": true
-}
-```
-
-### Sound Files
-
-A soundboard sound can be retrieved in MP3 or Ogg format at the URL:
-
-```
-https://cdn.discordapp.com/soundboard-sounds/{sound_id}
-```
-
-## Send Soundboard Sound
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/send-soundboard-sound
-
-Send a soundboard sound to a voice channel the user is connected to. Fires a [Voice Channel Effect Send](/docs/events/gateway-events#voice-channel-effect-send) Gateway event.
-
-Requires the `SPEAK` and `USE_SOUNDBOARD` permissions, and also the `USE_EXTERNAL_SOUNDS` permission if the sound is from a different server. Additionally, requires the user to be connected to the voice channel, having a [voice state](/docs/resources/voice#voice-state-object) without `deaf`, `self_deaf`, `mute`, or `suppress` enabled.
-
-###### JSON Params
-
-| Field | Type | Description |
-|------------------|-----------|--------------------------------------------------------------------------------------------------|
-| sound_id | snowflake | the id of the soundboard sound to play |
-| source_guild_id? | snowflake | the id of the guild the soundboard sound is from, required to play sounds from different servers |
-
-## List Default Soundboard Sounds
-/soundboard-default-sounds
-
-Returns an array of [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) objects that can be used by all users.
-
-## List Guild Soundboard Sounds
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/soundboard-sounds
-
-Returns a list of the guild's soundboard sounds. Includes `user` fields if the bot has the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission.
-
-###### Response Structure
-
-| Field | Type |
-|-------|-----------------------------------------------------------------------------------------|
-| items | array of [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) objects |
-
-## Get Guild Soundboard Sound
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/soundboard-sounds/[\{sound.id\}](/docs/resources/soundboard#soundboard-sound-object)
-
-Returns a [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) object for the given sound id. Includes the `user` field if the bot has the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission.
-
-## Create Guild Soundboard Sound
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/soundboard-sounds
-
-Create a new soundboard sound for the guild. Requires the `CREATE_GUILD_EXPRESSIONS` permission. Returns the new [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) object on success. Fires a [Guild Soundboard Sound Create](/docs/events/gateway-events#guild-soundboard-sound-create) Gateway event.
-
-:::info
-Soundboard sounds have a max file size of 512kb and a max duration of 5.2 seconds.
-:::
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|-------------|------------|------------------------------------------------------------------------------------------------|
-| name | string | name of the soundboard sound (2-32 characters) |
-| sound | data uri | the mp3 or ogg sound data, base64 encoded, similar to [image data](/docs/reference#image-data) |
-| volume? | ?double | the volume of the soundboard sound, from 0 to 1, defaults to 1 |
-| emoji_id? | ?snowflake | the id of the custom emoji for the soundboard sound |
-| emoji_name? | ?string | the unicode character of a standard emoji for the soundboard sound |
-
-## Modify Guild Soundboard Sound
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/soundboard-sounds/[\{sound.id\}](/docs/resources/soundboard#soundboard-sound-object)
-
-Modify the given soundboard sound. For sounds created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other sounds, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns the updated [soundboard sound](/docs/resources/soundboard#soundboard-sound-object) object on success. Fires a [Guild Soundboard Sound Update](/docs/events/gateway-events#guild-soundboard-sound-update) Gateway event.
-
-:::warn
-All parameters to this endpoint are optional.
-:::
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|------------|------------|--------------------------------------------------------------------|
-| name | string | name of the soundboard sound (2-32 characters) |
-| volume | ?double | the volume of the soundboard sound, from 0 to 1 |
-| emoji_id | ?snowflake | the id of the custom emoji for the soundboard sound |
-| emoji_name | ?string | the unicode character of a standard emoji for the soundboard sound |
-
-## Delete Guild Soundboard Sound
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/soundboard-sounds/[\{sound.id\}](/docs/resources/soundboard#soundboard-sound-object)
-
-Delete the given soundboard sound. For sounds created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other sounds, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns `204 No Content` on success. Fires a [Guild Soundboard Sound Delete](/docs/events/gateway-events#guild-soundboard-sound-delete) Gateway event.
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
diff --git a/docs/resources/sticker.mdx b/docs/resources/sticker.mdx
deleted file mode 100644
index ac0fa4bfac..0000000000
--- a/docs/resources/sticker.mdx
+++ /dev/null
@@ -1,190 +0,0 @@
----
-sidebar_label: Sticker
----
-
-# Sticker Resource
-
-### Sticker Object
-
-Represents a sticker that can be sent in messages.
-
-###### Sticker Structure
-
-| Field | Type | Description |
-|-------------|-------------------------------------------------|---------------------------------------------------------------------------------------|
-| id | snowflake | [id of the sticker](/docs/reference#image-formatting) |
-| pack_id? | snowflake | for standard stickers, id of the pack the sticker is from |
-| name | string | name of the sticker |
-| description | ?string | description of the sticker |
-| tags\* | string | autocomplete/suggestion tags for the sticker (max 200 characters) |
-| type | integer | [type of sticker](/docs/resources/sticker#sticker-object-sticker-types) |
-| format_type | integer | [type of sticker format](/docs/resources/sticker#sticker-object-sticker-format-types) |
-| available? | boolean | whether this guild sticker can be used, may be false due to loss of Server Boosts |
-| guild_id? | snowflake | id of the guild that owns this sticker |
-| user? | [user](/docs/resources/user#user-object) object | the user that uploaded the guild sticker |
-| sort_value? | integer | the standard sticker's sort order within its pack |
-
-\* A comma separated list of keywords is the format used in this field by standard stickers, but this is just a convention.
-Incidentally the client will always use a name generated from an emoji as the value of this field when creating or modifying a guild sticker.
-
-###### Sticker Types
-
-| Type | Value | Description |
-|----------|-------|-------------------------------------------------------|
-| STANDARD | 1 | an official sticker in a pack |
-| GUILD | 2 | a sticker uploaded to a guild for the guild's members |
-
-###### Sticker Format Types
-
-| Type | Value |
-|--------|-------|
-| PNG | 1 |
-| APNG | 2 |
-| LOTTIE | 3 |
-| GIF | 4 |
-
-###### Example Sticker
-
-```json
-{
- "id": "749054660769218631",
- "name": "Wave",
- "tags": "wumpus, hello, sup, hi, oi, heyo, heya, yo, greetings, greet, welcome, wave, :wave, :hello, :hi, :hey, hey, \ud83d\udc4b, \ud83d\udc4b\ud83c\udffb, \ud83d\udc4b\ud83c\udffc, \ud83d\udc4b\ud83c\udffd, \ud83d\udc4b\ud83c\udffe, \ud83d\udc4b\ud83c\udfff, goodbye, bye, see ya, later, laterz, cya",
- "type": 1,
- "format_type": 3,
- "description": "Wumpus waves hello",
- "pack_id": "847199849233514549",
- "sort_value": 12
-}
-```
-
-### Sticker Item Object
-
-The smallest amount of data required to render a sticker. A partial sticker object.
-
-###### Sticker Item Structure
-
-| Field | Type | Description |
-|-------------|-----------|---------------------------------------------------------------------------------------|
-| id | snowflake | id of the sticker |
-| name | string | name of the sticker |
-| format_type | integer | [type of sticker format](/docs/resources/sticker#sticker-object-sticker-format-types) |
-
-### Sticker Pack Object
-
-Represents a pack of standard stickers.
-
-###### Sticker Pack Structure
-
-| Field | Type | Description |
-|-------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------|
-| id | snowflake | id of the sticker pack |
-| stickers | array of [sticker](/docs/resources/sticker#sticker-object) objects | the stickers in the pack |
-| name | string | name of the sticker pack |
-| sku_id | snowflake | id of the pack's SKU |
-| cover_sticker_id? | snowflake | id of a sticker in the pack which is shown as the pack's icon |
-| description | string | description of the sticker pack |
-| banner_asset_id? | snowflake | id of the sticker pack's [banner image](/docs/reference#image-formatting) |
-
-###### Example Sticker Pack
-
-```json
-{
- "id": "847199849233514549",
- "stickers": [],
- "name": "Wumpus Beyond",
- "sku_id": "847199849233514547",
- "cover_sticker_id": "749053689419006003",
- "description": "Say hello to Wumpus!",
- "banner_asset_id": "761773777976819732"
-}
-```
-
-## Get Sticker
-/stickers/[\{sticker.id\}](/docs/resources/sticker#sticker-object)
-
-Returns a [sticker](/docs/resources/sticker#sticker-object) object for the given sticker ID.
-
-## List Sticker Packs
-/sticker-packs
-
-Returns a list of available sticker packs.
-
-###### Response Structure
-
-| Field | Type |
-|---------------|------------------------------------------------------------------------------|
-| sticker_packs | array of [sticker pack](/docs/resources/sticker#sticker-pack-object) objects |
-
-## Get Sticker Pack
-/sticker-packs/[\{pack.id\}](/docs/resources/sticker#sticker-pack-object)
-
-Returns a [sticker pack](/docs/resources/sticker#sticker-pack-object) object for the given sticker pack ID.
-
-## List Guild Stickers
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/stickers
-
-Returns an array of [sticker](/docs/resources/sticker#sticker-object) objects for the given guild. Includes `user` fields if the bot has the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission.
-
-## Get Guild Sticker
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/stickers/[\{sticker.id\}](/docs/resources/sticker#sticker-object)
-
-Returns a [sticker](/docs/resources/sticker#sticker-object) object for the given guild and sticker IDs. Includes the `user` field if the bot has the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission.
-
-## Create Guild Sticker
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/stickers
-
-Create a new sticker for the guild. Send a `multipart/form-data` body. Requires the `CREATE_GUILD_EXPRESSIONS` permission. Returns the new [sticker](/docs/resources/sticker#sticker-object) object on success. Fires a [Guild Stickers Update](/docs/events/gateway-events#guild-stickers-update) Gateway event.
-
-Every guilds has five free sticker slots by default, and each Boost level will grant access to more slots.
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-:::warn
-Lottie stickers can only be uploaded on guilds that have either the `VERIFIED` and/or the `PARTNERED` [guild feature](/docs/resources/guild#guild-object-guild-features).
-:::
-
-:::warn
-Uploaded stickers are constrained to 5 seconds in length for animated stickers, and 320 x 320 pixels.
-:::
-
-###### Form Params
-
-| Field | Type | Description |
-|-------------|---------------|----------------------------------------------------------------------------------------|
-| name | string | name of the sticker (2-30 characters) |
-| description | string | description of the sticker (empty or 2-100 characters) |
-| tags | string | autocomplete/suggestion tags for the sticker (max 200 characters) |
-| file | file contents | the sticker file to upload, must be a PNG, APNG, GIF, or Lottie JSON file, max 512 KiB |
-
-## Modify Guild Sticker
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/stickers/[\{sticker.id\}](/docs/resources/sticker#sticker-object)
-
-Modify the given sticker. For stickers created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other stickers, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns the updated [sticker](/docs/resources/sticker#sticker-object) object on success. Fires a [Guild Stickers Update](/docs/events/gateway-events#guild-stickers-update) Gateway event.
-
-:::info
-All parameters to this endpoint are optional.
-:::
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|-------------|---------|-------------------------------------------------------------------|
-| name | string | name of the sticker (2-30 characters) |
-| description | ?string | description of the sticker (2-100 characters) |
-| tags | string | autocomplete/suggestion tags for the sticker (max 200 characters) |
-
-## Delete Guild Sticker
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/stickers/[\{sticker.id\}](/docs/resources/sticker#sticker-object)
-
-Delete the given sticker. For stickers created by the current user, requires either the `CREATE_GUILD_EXPRESSIONS` or `MANAGE_GUILD_EXPRESSIONS` permission. For other stickers, requires the `MANAGE_GUILD_EXPRESSIONS` permission. Returns `204 No Content` on success. Fires a [Guild Stickers Update](/docs/events/gateway-events#guild-stickers-update) Gateway event.
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
diff --git a/docs/resources/webhook.mdx b/docs/resources/webhook.mdx
deleted file mode 100644
index dbd6cc5dde..0000000000
--- a/docs/resources/webhook.mdx
+++ /dev/null
@@ -1,341 +0,0 @@
----
-sidebar_label: Webhook
----
-
-# Webhook Resource
-
-Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.
-
-Apps can also subscribe to webhook events (i.e. outgoing webhooks) when events happen *in* Discord, which is detailed in the [Webhook Events](/docs/events/webhook-events) documentation.
-
-### Webhook Object
-
-Used to represent a webhook.
-
-###### Webhook Structure
-
-| Field | Type | Description |
-|-------------------|------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|
-| id | snowflake | the id of the webhook |
-| type | integer | the [type](/docs/resources/webhook#webhook-object-webhook-types) of the webhook |
-| guild_id? | ?snowflake | the guild id this webhook is for, if any |
-| channel_id | ?snowflake | the channel id this webhook is for, if any |
-| user? | [user](/docs/resources/user#user-object) object | the user this webhook was created by (not returned when getting a webhook with its token) |
-| name | ?string | the default name of the webhook |
-| avatar | ?string | the default user avatar [hash](/docs/reference#image-formatting) of the webhook |
-| token? | string | the secure token of the webhook (returned for Incoming Webhooks) |
-| application_id | ?snowflake | the bot/OAuth2 application that created this webhook |
-| source_guild? * | partial [guild](/docs/resources/guild#guild-object) object | the guild of the channel that this webhook is following (returned for Channel Follower Webhooks) |
-| source_channel? * | partial [channel](/docs/resources/channel#channel-object) object | the channel that this webhook is following (returned for Channel Follower Webhooks) |
-| url? | string | the url used for executing the webhook (returned by the [webhooks](/docs/topics/oauth2#webhooks) OAuth2 flow) |
-
-\* These fields will be absent if the webhook creator has since lost access to the guild where the followed channel resides
-
-###### Webhook Types
-
-:::info
-These types don't include [webhook events](/docs/events/webhook-events), which are outgoing webhooks sent to your app by Discord. See [Webhook Events](/docs/events/webhook-events) for details.
-:::
-
-| Value | Name | Description |
-|-------|------------------|----------------------------------------------------------------------------------------------------------------|
-| 1 | Incoming | Incoming Webhooks can post messages to channels with a generated token |
-| 2 | Channel Follower | Channel Follower Webhooks are internal webhooks used with Channel Following to post new messages into channels |
-| 3 | Application | Application webhooks are webhooks used with Interactions |
-
-###### Example Incoming Webhook
-
-```json
-{
- "name": "test webhook",
- "type": 1,
- "channel_id": "199737254929760256",
- "token": "3d89bb7572e0fb30d8128367b3b1b44fecd1726de135cbe28a41f8b2f777c372ba2939e72279b94526ff5d1bd4358d65cf11",
- "avatar": null,
- "guild_id": "199737254929760256",
- "id": "223704706495545344",
- "application_id": null,
- "user": {
- "username": "test",
- "discriminator": "7479",
- "id": "190320984123768832",
- "avatar": "b004ec1740a63ca06ae2e14c5cee11f3",
- "public_flags": 131328
- }
-}
-```
-
-###### Example Channel Follower Webhook
-
-```json
-{
- "type": 2,
- "id": "752831914402115456",
- "name": "Guildy name",
- "avatar": "bb71f469c158984e265093a81b3397fb",
- "channel_id": "561885260615255432",
- "guild_id": "56188498421443265",
- "application_id": null,
- "source_guild": {
- "id": "56188498421476534",
- "name": "Guildy name",
- "icon": "bb71f469c158984e265093a81b3397fb"
- },
- "source_channel": {
- "id": "5618852344134324",
- "name": "announcements"
- },
- "user": {
- "username": "test",
- "discriminator": "7479",
- "id": "190320984123768832",
- "avatar": "b004ec1740a63ca06ae2e14c5cee11f3",
- "public_flags": 131328
- }
-}
-```
-
-###### Example Application Webhook
-
-```json
-{
- "type": 3,
- "id": "658822586720976555",
- "name": "Clyde",
- "avatar": "689161dc90ac261d00f1608694ac6bfd",
- "channel_id": null,
- "guild_id": null,
- "application_id": "658822586720976555"
-}
-```
-
-## Create Webhook
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/webhooks
-
-Creates a new webhook and returns a [webhook](/docs/resources/webhook#webhook-object) object on success. Requires the `MANAGE_WEBHOOKS` permission. Fires a [Webhooks Update](/docs/events/gateway-events#webhooks-update) Gateway event.
-
-An error will be returned if a webhook name (`name`) is not valid. A webhook name is valid if:
-
-- It does not contain the substrings `clyde` or `discord` (case-insensitive)
-- It follows the nickname guidelines in the [Usernames and Nicknames](/docs/resources/user#usernames-and-nicknames) documentation, with an exception that webhook names can be up to 80 characters
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|---------|-------------------------------------------|---------------------------------------|
-| name | string | name of the webhook (1-80 characters) |
-| avatar? | ?[image data](/docs/reference#image-data) | image for the default webhook avatar |
-
-## Get Channel Webhooks
-/channels/[\{channel.id\}](/docs/resources/channel#channel-object)/webhooks
-
-Returns a list of channel [webhook](/docs/resources/webhook#webhook-object) objects. Requires the `MANAGE_WEBHOOKS` permission.
-
-## Get Guild Webhooks
-/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/webhooks
-
-Returns a list of guild [webhook](/docs/resources/webhook#webhook-object) objects. Requires the `MANAGE_WEBHOOKS` permission.
-
-## Get Webhook
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)
-
-Returns the new [webhook](/docs/resources/webhook#webhook-object) object for the given id.
-
-This request requires the `MANAGE_WEBHOOKS` permission unless the application making the request owns the
-webhook. [(see: webhook.application_id)](/docs/resources/webhook#webhook-object)
-
-## Get Webhook with Token
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)
-
-Same as above, except this call does not require authentication and returns no user in the webhook object.
-
-## Modify Webhook
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)
-
-Modify a webhook. Requires the `MANAGE_WEBHOOKS` permission. Returns the updated [webhook](/docs/resources/webhook#webhook-object) object on success. Fires a [Webhooks Update](/docs/events/gateway-events#webhooks-update) Gateway event.
-
-:::info
-All parameters to this endpoint are optional
-:::
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-###### JSON Params
-
-| Field | Type | Description |
-|------------|-------------------------------------------|----------------------------------------------------|
-| name | string | the default name of the webhook |
-| avatar | ?[image data](/docs/reference#image-data) | image for the default webhook avatar |
-| channel_id | snowflake | the new channel id this webhook should be moved to |
-
-## Modify Webhook with Token
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)
-
-Same as above, except this call does not require authentication, does not accept a `channel_id` parameter in the body, and does not return a user in the webhook object.
-
-## Delete Webhook
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)
-
-Delete a webhook permanently. Requires the `MANAGE_WEBHOOKS` permission. Returns a `204 No Content` response on success. Fires a [Webhooks Update](/docs/events/gateway-events#webhooks-update) Gateway event.
-
-:::info
-This endpoint supports the `X-Audit-Log-Reason` header.
-:::
-
-## Delete Webhook with Token
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)
-
-Same as above, except this call does not require authentication.
-
-## Execute Webhook
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)
-
-Refer to [Uploading Files](/docs/reference#uploading-files) for details on attachments and `multipart/form-data` requests. Returns a message or `204 No Content` depending on the `wait` query parameter.
-
-:::info
-Note that when sending a message, you must provide a value for at **least one of** `content`, `embeds`, `components`, `file`, or `poll`.
-:::
-
-:::info
-If the webhook channel is a forum or media channel, you must provide either `thread_id` in the query string params, or `thread_name` in the JSON/form params. If `thread_id` is provided, the message will send in that thread. If `thread_name` is provided, a thread with that name will be created in the channel.
-:::
-
-:::warn
-Discord may strip certain characters from message content, like invalid unicode characters or characters which cause unexpected message formatting. If you are passing user-generated strings into message content, consider sanitizing the data to prevent unexpected behavior and using `allowed_mentions` to prevent unexpected mentions.
-:::
-
-###### Query String Params
-
-| Field | Type | Description | Required |
-|-----------------|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
-| wait | [boolean](/docs/reference#boolean-query-strings) | waits for server confirmation of message send before response, and returns the created message body (defaults to `false`; when `false` a message that is not saved does not return an error) | false |
-| thread_id | snowflake | Send a message to the specified thread within a webhook's channel. The thread will automatically be unarchived. | false |
-| with_components | [boolean](/docs/reference#boolean-query-strings) | whether to respect the `components` field of the request. When enabled, allows application-owned webhooks to use all components and non-owned webhooks to use non-interactive components. (defaults to `false`) | false |
-
-###### JSON/Form Params
-
-| Field | Type | Description | Required |
-|-------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|
-| content | string | the message contents (up to 2000 characters) | one of content, file, embeds, poll |
-| username | string | override the default username of the webhook | false |
-| avatar_url | string | override the default avatar of the webhook | false |
-| tts | boolean | true if this is a TTS message | false |
-| embeds | array of up to 10 [embed](/docs/resources/message#embed-object) objects | embedded `rich` content | one of content, file, embeds, poll |
-| allowed_mentions | [allowed mention object](/docs/resources/message#allowed-mentions-object) | allowed mentions for the message | false |
-| components \* | array of [message component](/docs/components/reference#component-object) | the components to include with the message | false |
-| files[n] \*\* | file contents | the contents of the file being sent | one of content, file, embeds, poll |
-| payload_json \*\* | string | JSON encoded body of non-file params | `multipart/form-data` only |
-| attachments \*\* | array of partial [attachment](/docs/resources/message#attachment-object) objects | attachment objects with filename and description | false |
-| flags \*\*\* | integer | [message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (only `SUPPRESS_EMBEDS`, `SUPPRESS_NOTIFICATIONS` and `IS_COMPONENTS_V2` can be set) | false |
-| thread_name | string | name of thread to create (requires the webhook channel to be a forum or media channel) | false |
-| applied_tags | array of snowflakes | array of tag ids to apply to the thread (requires the webhook channel to be a forum or media channel) | false |
-| poll | [poll](/docs/resources/poll#poll-create-request-object) request object | A poll! | one of content, file, embeds, poll |
-
-\* Application-owned webhooks can always send components. Non-application-owned webhooks cannot send interactive components, and the `components` field will be ignored unless they set the `with_components` query param.
-
-\*\* See [Uploading Files](/docs/reference#uploading-files) for details.
-
-\*\*\* When the flag `IS_COMPONENTS_V2` is set, the webhook message can only contain `components`. Providing `content`, `embeds`, `files[n]` or `poll` will fail with a 400 BAD REQUEST response.
-
-:::info
-For the webhook embed objects, you can set every field except `type` (it will be `rich` regardless of if you try to set it), `provider`, `video`, and any `height`, `width`, or `proxy_url` values for images.
-:::
-
-## Execute Slack-Compatible Webhook
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)/slack
-
-Refer to [Slack's documentation](https://api.slack.com/incoming-webhooks) for more information. We do not support Slack's `channel`, `icon_emoji`, `mrkdwn`, or `mrkdwn_in` properties.
-
-###### Query String Params
-
-| Field | Type | Description | Required |
-|-----------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
-| thread_id | snowflake | id of the thread to send the message in | false |
-| wait | [boolean](/docs/reference#boolean-query-strings) | waits for server confirmation of message send before response (defaults to `true`; when `false` a message that is not saved does not return an error) | false |
-
-## Execute GitHub-Compatible Webhook
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)/github
-
-[Add a new webhook](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks) to your GitHub repo (in the repo's settings), and use this endpoint as the "Payload URL." You can choose what events your Discord channel receives by choosing the "Let me select individual events" option and selecting individual events for the new webhook you're configuring. The supported [events](https://docs.github.com/en/webhooks/webhook-events-and-payloads) are `commit_comment`, `create`, `delete`, `fork`, `issue_comment`, `issues`, `member`, `public`, `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `release`, `watch`, `check_run`, `check_suite`, `discussion`, and `discussion_comment`.
-
-###### Query String Params
-
-| Field | Type | Description | Required |
-|-----------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
-| thread_id | snowflake | id of the thread to send the message in | false |
-| wait | [boolean](/docs/reference#boolean-query-strings) | waits for server confirmation of message send before response (defaults to `true`; when `false` a message that is not saved does not return an error) | false |
-
-## Get Webhook Message
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)/messages/[\{message.id\}](/docs/resources/message#message-object)
-
-Returns a previously-sent webhook message from the same token. Returns a [message](/docs/resources/message#message-object) object on success.
-
-###### Query String Params
-
-| Field | Type | Description | Required |
-|-----------|-----------|------------------------------------|----------|
-| thread_id | snowflake | id of the thread the message is in | false |
-
-## Edit Webhook Message
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)/messages/[\{message.id\}](/docs/resources/message#message-object)
-
-Edits a previously-sent webhook message from the same token. Returns a [message](/docs/resources/message#message-object) object on success.
-
-When the `content` field is edited, the arrays `mentions` and `mention_roles` and the boolean `mention_everyone` in the message object will be reconstructed from scratch based on the new content. When the message flag `IS_COMPONENTS_V2` is set, the reconstructed arrays and boolean are based on the edited content in the `components` array. The `allowed_mentions` field of the edit request controls how this happens. If there is no explicit `allowed_mentions` in the edit request, the content will be parsed with _default_ allowances, that is, without regard to whether or not an `allowed_mentions` was present in the request that originally created the message.
-
-Refer to [Uploading Files](/docs/reference#uploading-files) for details on attachments and `multipart/form-data` requests.
-Any provided files will be **appended** to the message. To remove or replace files you will have to supply the `attachments` field which specifies the files to retain on the message after edit.
-
-:::warn
-Starting with API v10, the `attachments` array must contain all attachments that should be present after edit, including **retained and new** attachments provided in the request body.
-:::
-
-:::info
-All parameters to this endpoint are optional and nullable.
-:::
-
-###### Query String Params
-
-| Field | Type | Description | Required |
-|-----------------|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
-| thread_id | snowflake | id of the thread the message is in | false |
-| with_components | [boolean](/docs/reference#boolean-query-strings) | whether to respect the `components` field of the request. When enabled, allows application-owned webhooks to use all components and non-owned webhooks to use non-interactive components. (defaults to `false`) | false |
-
-###### JSON/Form Params
-
-| Field | Type | Description |
-|---------------------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| content | string | the message contents (up to 2000 characters) |
-| embeds | array of up to 10 [embed](/docs/resources/message#embed-object) objects | embedded `rich` content |
-| flags \* | integer | [message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (`SUPPRESS_EMBEDS` and `IS_COMPONENTS_V2` only) |
-| allowed_mentions | [allowed mention object](/docs/resources/message#allowed-mentions-object) | allowed mentions for the message |
-| components \*\* | array of [message component](/docs/components/reference#component-object) | the components to include with the message |
-| files[n] \*\*\* | file contents | the contents of the file being sent/edited |
-| payload_json \*\*\* | string | JSON encoded body of non-file params (multipart/form-data only) |
-| attachments \*\*\* | array of partial [attachment](/docs/resources/message#attachment-object) objects | attached files to keep and possible descriptions for new files |
-| poll \*\*\*\* | [poll](/docs/resources/poll#poll-create-request-object) request object | A poll! |
-
-\* The `SUPPRESS_EMBEDS` flag can be both set and unset, while the `IS_COMPONENTS_V2` flag can only be set. When the `IS_COMPONENTS_V2` flag is set, any of the used `content`, `embeds`, `files[n]` or `poll` values in the initial message must be set to `null` first, otherwise it will fail with a 400 BAD REQUEST response.
-
-\*\* Application-owned webhooks can always send components. Non-application-owned webhooks cannot send interactive components, and the `components` field will be ignored unless they set the `with_components` query param.
-
-\*\*\* See [Uploading Files](/docs/reference#uploading-files) for details.
-
-\*\*\*\* Polls can only be added when editing a deferred interaction response.
-
-## Delete Webhook Message
-/webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)/messages/[\{message.id\}](/docs/resources/message#message-object)
-
-Deletes a message that was created by the webhook. Returns a `204 No Content` response on success.
-
-###### Query String Params
-
-| Field | Type | Description | Required |
-|-----------|-----------|------------------------------------|----------|
-| thread_id | snowflake | id of the thread the message is in | false |
diff --git a/docs/rich-presence/overview.mdx b/docs/rich-presence/overview.mdx
deleted file mode 100644
index 23d2524a37..0000000000
--- a/docs/rich-presence/overview.mdx
+++ /dev/null
@@ -1,109 +0,0 @@
----
-sidebar_label: Overview
----
-
-# Overview of Rich Presence
-
-
-
-Rich Presence lets you display actionable data in a Discord user's profile about what they're up to in your game or app. The data you choose to display is up to you—whether it's a user's score, the duration they've been playing your game, what they're listening to on your platform, or something else.
-
----
-
-## Choosing an SDK
-
-There are three options when integrating Rich Presence. Depending on what you're building, you'll want to choose the right SDK for your project:
-
-- The **[Discord Social SDK](/docs/rich-presence/overview#discord-social-sdk)** allows you to build social features into your game or app, including friends lists, game invites, and more.
-- The **[Embedded App SDK](/docs/rich-presence/overview#embedded-app-sdk)** should be used if you're building an [Activity](/docs/activities/overview) in Discord.
-- The **[Game SDK (legacy)](/docs/rich-presence/overview#game-sdk)** can be used if you're building an off-platform game or app and you want to integrate it into Discord.
-
-All SDKs use similar underlying primitives (like the [`SET_ACTIVITY` RPC command](/docs/topics/rpc#setactivity)), so a lot is the same between them. But there are a few differences, like feature compatibility, which is covered in the sections below.
-
-:::info
-Rich Presence data appears publicly on your Discord profile, so during development you should use a test account that only belongs to your private development server(s).
-:::
-
-### Discord Social SDK
-
-The [Discord Social SDK](/docs/discord-social-sdk/overview) is used for building social features directly into your game. When a user is playing your game, you can show what they're up to in their Discord profile and even prompt their friends to join in with game invites.
-
-When integrating Rich Presence with an off-platform game, data can be shown about what a user is up to in your game. A "Join" button can also be configured to allow a user's friends to jump into their game and enable sending game invites.
-
-[Read about using Rich Presence with the Discord Social SDK](/docs/rich-presence/using-with-the-discord-social-sdk)
-
-### Embedded App SDK
-
-The [Embedded App SDK](/docs/developer-tools/embedded-app-sdk) is used to build Activities, which are multiplayer games and social experiences hosted in an iframe within Discord. The SDK handles communication between Discord and the Activity and helps integrate platform features (like Rich Presence!).
-
-After a user joins an Activity, Rich Presence can be used to dynamically show data about what that user is doing or playing, as well as prompt others to join in and play along.
-
-[Read about using Rich Presence with the Embedded App SDK](/docs/rich-presence/using-with-the-embedded-app-sdk)
-
-### Game SDK
-
-:::warn
-**The Game SDK has been archived.**
-
-We recommend using the [Discord Social SDK](/docs/discord-social-sdk/overview) for new projects.
-
-Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/docs/discord-social-sdk/overview) for new features and updates.
-:::
-
-The [Game SDK](/docs/developer-tools/game-sdk) makes it easier to build 3rd party games and integrate them with Discord. While many features of the Game SDK are deprecated, it can still be used for a few use cases (like integrating Rich Presence!).
-
-When integrating Rich Presence with an off-platform game, data can be shown about what a user is up to in your game. A "Join" button can also be configured to allow a user's friends to jump into their game.
-
-[Read about using Rich Presence with the Game SDK](/docs/rich-presence/using-with-the-game-sdk)
-
-## Adding Custom Art Assets
-
-While integrating Rich Presence, you'll likely want to upload custom art assets for your app. **For all Rich Presence assets, it's highly recommended to make them 1024 x 1024**.
-
-To add custom assets for Rich Presence, navigate to your [app's settings](https://discord.com/developers/applications) and click **Rich Presence** on the left-hand sidebar. On the **Art Assets** page, there are two different types of assets you can upload.
-
-### Invite Image
-
-The Rich Presence invite image appears when [invites](/docs/developer-tools/game-sdk#sendinvite) are sent for a 3rd party game or app using the [Game SDK](/docs/rich-presence/overview#game-sdk). After uploading an invite image for your app, you can see a preview of it to the right (under "IRL Invite Image Example").
-
-:::info
-The invite image can be ignored if you're building using the [Embedded App SDK](/docs/rich-presence/overview#embedded-app-sdk). Invites sent using the Embedded App SDK's[`openInviteDialog()`](/docs/developer-tools/embedded-app-sdk#openinvitedialog) use the Activity's cover art.
-:::
-
-
-
-### Assets
-
-Up to 300 custom assets can be added for your app to use when setting Rich Presence for a Discord user. These assets can be anything that help orient others to what a user is doing inside of your Activity or 3rd party game.
-
-If you need more than 300 custom assets or want to use images stored somewhere else, you can also [specify an external URL](/docs/events/gateway-events#activity-object-activity-asset-image) as long it still has the proper dimensions and size.
-
-:::info
-For tips on choosing assets, take a look at the [Rich Presence best practices guide](/docs/rich-presence/best-practices#have-interesting-expressive-art).
-:::
-
-When uploading Rich Presence assets, **the asset keys will automatically be changed to lowercase**. You can see this reflected in your app's settings after saving a newly-uploaded asset, and should keep it in mind when referencing any asset keys in your code.
-
-
-
-### Using the Visualizer
-
-:::warn
-The Rich Presence visualizer currently uses an outdated Discord UI, but can still be helpful as a quick-and-dirty reference for what your Rich Presence data will look like in Discord.
-:::
-
-In your app's settings, there's a Rich Presence visualizer to make it easier to see what your uploaded [assets](/docs/rich-presence/overview#assets) will look like in the context of a Discord profile. To access the visualizer, navigate to your [app's settings](https://discord.com/developers/applications) and click **Rich Presence** on the left-hand sidebar. On the **Visualizer** page, you can fill out some custom strings, party information, and select your uploaded assets to see a preview.
-
-## Start Building
-
-
-
- Guide on using Rich Presence in the Embedded App SDK while you're building an Activity
-
-
- Guide on using Rich Presence in the Game SDK
-
-
- Best practices and launch checklist for when you're integrating Rich Presence with your game or app
-
-
\ No newline at end of file
diff --git a/docs/rich-presence/using-with-the-discord-social-sdk.mdx b/docs/rich-presence/using-with-the-discord-social-sdk.mdx
deleted file mode 100644
index 73c75c5c13..0000000000
--- a/docs/rich-presence/using-with-the-discord-social-sdk.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-sidebar_label: Using with the Discord Social SDK
----
-
-# Using Rich Presence with the Discord Social SDK
-
-
-When developing a game, the [Discord Social SDK](/docs/discord-social-sdk/overview) makes it easy to integrate Rich Presence to display details about what a user is up to inside of your game or social experience.
-
-:::info
-Not sure if you should be building with the Discord Social SDK? Read through [Choosing an SDK](/docs/rich-presence/overview#choosing-an-sdk) to understand your options when integrating Rich Presence with your app.
-:::
-
-
-## Understanding Rich Presence Data
-
-Before we dig in, it's helpful to understand what Rich Presence data you can set when updating a user's presence data. Let's just take a look at what we're working with:
-
-
-
-:::info
-For tips on designing Rich Presence, take a look at the [Rich Presence best practices guide](/docs/rich-presence/best-practices).
-:::
-
-## Setting Rich Presence Data
-
-Check out our [Setting Rich Presence](/docs/discord-social-sdk/development-guides/setting-rich-presence) guide and our to learn how to set custom presence data for your players using the Discord Social SDK.
-
-- [Design Guidelines: Status & Rich Presence](/docs/discord-social-sdk/design-guidelines/status-rich-presence)
-
-
diff --git a/docs/rich-presence/using-with-the-embedded-app-sdk.mdx b/docs/rich-presence/using-with-the-embedded-app-sdk.mdx
deleted file mode 100644
index d04a93cf81..0000000000
--- a/docs/rich-presence/using-with-the-embedded-app-sdk.mdx
+++ /dev/null
@@ -1,159 +0,0 @@
----
-sidebar_label: Using with the Embedded App SDK
----
-
-# Using Rich Presence with the Embedded App SDK
-
-When developing an [Activity](/docs/activities/overview), the [Embedded App SDK](/docs/developer-tools/embedded-app-sdk) makes it easy to integrate Rich Presence to display details about what a user is up to inside of your game or social experience.
-
-Rich Presence data can be thought of as an extension of your Activity—and leveling it up just a *little* makes it more interesting and relevant to the user playing your Activity (and their friends that might want to jump in and play). This guide provides an overview of the platform and technical knowledge you need to integrate Rich Presence with your existing Activity.
-
-:::info
-Not sure if you should be building with the Embedded App SDK? Read through [Choosing an SDK](/docs/rich-presence/overview#choosing-an-sdk) to understand your options when integrating Rich Presence with your app.
-:::
-
-The rest of the guide assumes you've already developed an [app](/docs/quick-start/overview-of-apps) that can launch an Activity. If you aren't at that point quite yet, you should follow the guide on [building your first Activity](/docs/activities/building-an-activity) before continuing.
-
-## Understanding Rich Presence Data
-
-### Default Rich Presence Data
-
-By default, when a user is connected to your Activity, the app's icon will appear on their profile. If the user viewing the profile has the ability to join, an "Ask to Join" button will be displayed as well.
-
-
-
-While this is okay, it's pretty limited and doesn't provide much context about what a user is actually *doing* inside of the Activity. In the following sections, we'll take a look at what richer and more actionable presence can look like.
-
-### Custom Rich Presence Data
-
-Now let's see what custom presence data can look like when a user joins your Activity. The [types for these fields](/docs/rich-presence/using-with-the-embedded-app-sdk#setactivity-fields) and [examples](/docs/rich-presence/using-with-the-embedded-app-sdk#setactivity-example) are in the sections below, but for now let's just get an idea of what we're working with:
-
-
-
-A few small things to note about the above image:
-1. `large_image` and `small_image` are both in the `assets` object, which you can see below in the [table below](/docs/rich-presence/using-with-the-embedded-app-sdk#activity-partial-object). They're labeled with the object's keys to make it more clear how they appear in a Discord profile.
-2. You can't set App Name when setting presence—it's always the name configured in your [app's settings](https://discord.com/developers/applications).
-3. The state `(1 of max_party)` badge will only render when a party field is provided. Otherwise, state will be shown in a line of text below details.
-
-## Updating Presence
-
-When updating Rich Presence data using the Embedded App SDK, the only real command you need to use is **[`setActivity()`](/docs/developer-tools/embedded-app-sdk#setactivity)**. Under the hood, `setActivity()` calls the RPC [`SET_ACTIVITY` command](/docs/topics/rpc#setactivity) with the features and fields available when you're building an Activity.
-
-
-As you start exploring the Rich Presence docs, you'll start seeing the word "activity" a *lot*. The "activities" referenced in docs (like the [RPC ones](/docs/topics/rpc#setactivity)) aren't related to the Activities you're building with the Embedded App SDK.
-
-When Rich Presence was introduced, the underlying object that contains presence data was called an "activity" (long before the Embedded App SDK), which is what the RPC [`SET_ACTIVITY` command](/docs/topics/rpc#setactivity) is referencing. And that's *also* why the Embedded App SDK's wrapper around the RPC command is called `setActivity()` yet isn't really related to setting the state for the kind of Activity that *you're* building.
-
-We know, it's confusing ¯\\\_(⊙︿⊙)\_/¯ — the naming was logical at the time because it was really about the user's activity in a 3rd party game or service, but now it sorta feels like activity-ception. Understanding the nuances here aren't super important, and it's why we have guides like this one. But as they say...the more you (at least sort of) know.
-
-
-### rpc.activities.write Scope
-
-To display custom Rich Presence data for a user, your app will need to be authorized with the [`rpc.activities.write` scope](/docs/topics/oauth2#shared-resources-oauth2-scopes) for that user.
-
-To request the scope, your [`authorize()`](/docs/developer-tools/embedded-app-sdk#authorize) call might look something like this:
-
-
-
-:::info
-The following example only focuses on calling `authorize()`. Follow the [Building an Activity guide](/docs/activities/building-an-activity) for more details on topics like installing and instantiating the Embedded App SDK.
-:::
-
-```js
-// Authorize with Discord Client
-const { code } = await discordSdk.commands.authorize({
- client_id: import.meta.env.VITE_DISCORD_CLIENT_ID,
- response_type: "code",
- state: "",
- prompt: "none",
- scope: [
- "identify",
- "rpc.activities.write"
- ],
-});
-```
-
-
-### setActivity Fields
-
-When calling [`setActivity()`](/docs/developer-tools/embedded-app-sdk#setactivity), you are expected to pass a partial [activity object](/docs/events/gateway-events#activity-object-activity-structure).
-
-Below is a table with many of the available fields for the activity partial. Some were left out since they don't have an effect for Activities.
-
-#### Activity partial object
-
-:::info
-All of the fields on the partial object are optional and nullable
-:::
-
-| field | type | description |
-|------------|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|
-| type | integer | [Activity](/docs/events/gateway-events#activity-object-activity-types) type, which determines the header text for the Rich Presence data |
-| state | string | User's current party status |
-| details | string | What the player is currently doing in your Activity |
-| timestamps | [timestamps](/docs/events/gateway-events#activity-object-activity-timestamps) object | Unix timestamps to display start and/or end times |
-| assets | [assets](/docs/events/gateway-events#activity-object-activity-assets) object | Images used for the Rich Presence data (and their hover texts) |
-| party | [party](/docs/events/gateway-events#activity-object-activity-party) object | Information for the current party of the player |
-
-### setActivity Example
-
-Now let's take a look at more of a real example. Take a look at the Rich Presence data below that is for an Activity:
-
-
-
-To create this sort of Rich Presence, here is what the `setActivity()` code would look like:
-
-
-
-:::info
-The following example only focuses on using `setActivity()`. Follow the [Building an Activity guide](/docs/activities/building-an-activity) for more details on topics like instantiating the Embedded App SDK and authenticating users.
-:::
-```js
-await discordSdk.commands.setActivity({
- activity: {
- type: 0,
- details: 'Traveling with a group',
- state: 'In Mainframe',
- assets: {
- large_image: 'main-game-image',
- large_text: 'in a group',
- small_image: 'map-mainframe',
- small_text: 'in mainframe'
- },
- timestamps: {
- start: 1723137832
- },
- party: {
- size: [2,4]
- }
- }
-});
-```
-
-
-## Using External Custom Assets
-
-Typically when building an Activity, you need to be aware of the proxy and [how to use external resources](/docs/activities/development-guides/networking#using-external-resources). However, lucikly for you (and the writer of this guide), image URLs in fields for features like Rich Presence don't need to jump through any extra hoops.
-
-As mentioned in the [Rich Presence overview](/docs/rich-presence/overview#assets), you have more than 300 custom assets or if you want to use your stored images from somewhere else, you can specify an external URL for `large_image` or `small_image` within the `assets` object.
-
-
-
-:::info
-The following example only focuses on using `setActivity()`. Follow the [Building an Activity guide](/docs/activities/building-an-activity) for more details on topics like instantiating the Embedded App SDK and authenticating users.
-:::
-```js
-await discordSdk.commands.setActivity({
- activity: {
- type: 2,
- state: 'Broken Hearts and Code (club edit)',
- details: 'DJ Wump',
- assets: {
- large_image: 'https://example.com/album-covers/dj-wump/broken-code-and-hearts-club-edit.jpg',
- large_text: 'Listening to a track',
- }
- }
-});
-```
-
-
diff --git a/index.js b/index.js
deleted file mode 100644
index f053ebf797..0000000000
--- a/index.js
+++ /dev/null
@@ -1 +0,0 @@
-module.exports = {};
diff --git a/static/images/activities/activities-hero.webp b/static/images/activities/activities-hero.webp
deleted file mode 100644
index fa9f7c5cf6..0000000000
Binary files a/static/images/activities/activities-hero.webp and /dev/null differ
diff --git a/static/images/activities/activity-instance-validation.webp b/static/images/activities/activity-instance-validation.webp
deleted file mode 100644
index 4e11535574..0000000000
Binary files a/static/images/activities/activity-instance-validation.webp and /dev/null differ
diff --git a/static/images/activities/application-test-mode-prod.webp b/static/images/activities/application-test-mode-prod.webp
deleted file mode 100644
index 378e5718c4..0000000000
Binary files a/static/images/activities/application-test-mode-prod.webp and /dev/null differ
diff --git a/static/images/activities/bobble-bash.webp b/static/images/activities/bobble-bash.webp
deleted file mode 100644
index 2e0d013092..0000000000
Binary files a/static/images/activities/bobble-bash.webp and /dev/null differ
diff --git a/static/images/activities/bobble-league.webp b/static/images/activities/bobble-league.webp
deleted file mode 100644
index f4b570dca0..0000000000
Binary files a/static/images/activities/bobble-league.webp and /dev/null differ
diff --git a/static/images/activities/chess-victory.webp b/static/images/activities/chess-victory.webp
deleted file mode 100644
index 57ae1ef6c3..0000000000
Binary files a/static/images/activities/chess-victory.webp and /dev/null differ
diff --git a/static/images/activities/custom-link-embed.webp b/static/images/activities/custom-link-embed.webp
deleted file mode 100644
index e14bd18041..0000000000
Binary files a/static/images/activities/custom-link-embed.webp and /dev/null differ
diff --git a/static/images/activities/debug-logs-filtering.webp b/static/images/activities/debug-logs-filtering.webp
deleted file mode 100644
index e588836ca5..0000000000
Binary files a/static/images/activities/debug-logs-filtering.webp and /dev/null differ
diff --git a/static/images/activities/default_orientation_lock_state.webp b/static/images/activities/default_orientation_lock_state.webp
deleted file mode 100644
index 9dc4d92160..0000000000
Binary files a/static/images/activities/default_orientation_lock_state.webp and /dev/null differ
diff --git a/static/images/activities/eights.webp b/static/images/activities/eights.webp
deleted file mode 100644
index adaf0a25e1..0000000000
Binary files a/static/images/activities/eights.webp and /dev/null differ
diff --git a/static/images/activities/enable-activities.webp b/static/images/activities/enable-activities.webp
deleted file mode 100644
index 9a7b8694df..0000000000
Binary files a/static/images/activities/enable-activities.webp and /dev/null differ
diff --git a/static/images/activities/encourage-hardware-acceleration-modal.webp b/static/images/activities/encourage-hardware-acceleration-modal.webp
deleted file mode 100644
index ac27d5c15d..0000000000
Binary files a/static/images/activities/encourage-hardware-acceleration-modal.webp and /dev/null differ
diff --git a/static/images/activities/external-link-modal.webp b/static/images/activities/external-link-modal.webp
deleted file mode 100644
index 37f88a6d52..0000000000
Binary files a/static/images/activities/external-link-modal.webp and /dev/null differ
diff --git a/static/images/activities/invite-dialog.webp b/static/images/activities/invite-dialog.webp
deleted file mode 100644
index e88ba76e0b..0000000000
Binary files a/static/images/activities/invite-dialog.webp and /dev/null differ
diff --git a/static/images/activities/join-application.webp b/static/images/activities/join-application.webp
deleted file mode 100644
index 69797180a6..0000000000
Binary files a/static/images/activities/join-application.webp and /dev/null differ
diff --git a/static/images/activities/oauth-flow-diagram.svg b/static/images/activities/oauth-flow-diagram.svg
deleted file mode 100644
index e644050c51..0000000000
--- a/static/images/activities/oauth-flow-diagram.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/static/images/activities/oauth2-redirect.webp b/static/images/activities/oauth2-redirect.webp
deleted file mode 100644
index 2cdb336af0..0000000000
Binary files a/static/images/activities/oauth2-redirect.webp and /dev/null differ
diff --git a/static/images/activities/share-moment-dialog-example.webp b/static/images/activities/share-moment-dialog-example.webp
deleted file mode 100644
index bd3c8b6d70..0000000000
Binary files a/static/images/activities/share-moment-dialog-example.webp and /dev/null differ
diff --git a/static/images/activities/start-activity.webp b/static/images/activities/start-activity.webp
deleted file mode 100644
index 6041d42920..0000000000
Binary files a/static/images/activities/start-activity.webp and /dev/null differ
diff --git a/static/images/activities/supported-platforms.webp b/static/images/activities/supported-platforms.webp
deleted file mode 100644
index e736bcdbb5..0000000000
Binary files a/static/images/activities/supported-platforms.webp and /dev/null differ
diff --git a/static/images/activities/tutorial-auth.webp b/static/images/activities/tutorial-auth.webp
deleted file mode 100644
index c8fa2f7546..0000000000
Binary files a/static/images/activities/tutorial-auth.webp and /dev/null differ
diff --git a/static/images/activities/tutorial-channel-name.webp b/static/images/activities/tutorial-channel-name.webp
deleted file mode 100644
index 4a29930e6d..0000000000
Binary files a/static/images/activities/tutorial-channel-name.webp and /dev/null differ
diff --git a/static/images/activities/tutorial-hero.webp b/static/images/activities/tutorial-hero.webp
deleted file mode 100644
index 3dfada4199..0000000000
Binary files a/static/images/activities/tutorial-hero.webp and /dev/null differ
diff --git a/static/images/activities/url-mapping-do.webp b/static/images/activities/url-mapping-do.webp
deleted file mode 100644
index 4ee4ad7bc4..0000000000
Binary files a/static/images/activities/url-mapping-do.webp and /dev/null differ
diff --git a/static/images/activities/url-mapping-dont.webp b/static/images/activities/url-mapping-dont.webp
deleted file mode 100644
index ebdfa4f9f9..0000000000
Binary files a/static/images/activities/url-mapping-dont.webp and /dev/null differ
diff --git a/static/images/activities/url-mapping-tutorial.webp b/static/images/activities/url-mapping-tutorial.webp
deleted file mode 100644
index 2642f6526e..0000000000
Binary files a/static/images/activities/url-mapping-tutorial.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Brand-02.webp b/static/images/social-sdk/design-guidelines/Brand-02.webp
deleted file mode 100644
index 0b2bf8cddc..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Brand-02.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Brand-03.webp b/static/images/social-sdk/design-guidelines/Brand-03.webp
deleted file mode 100644
index 4badb33ef5..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Brand-03.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Brand-04.webp b/static/images/social-sdk/design-guidelines/Brand-04.webp
deleted file mode 100644
index 98b0ce16fe..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Brand-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/ConnectionPoints-03.webp b/static/images/social-sdk/design-guidelines/ConnectionPoints-03.webp
deleted file mode 100644
index bc7f476ea5..0000000000
Binary files a/static/images/social-sdk/design-guidelines/ConnectionPoints-03.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/ConnectionPoints-04.webp b/static/images/social-sdk/design-guidelines/ConnectionPoints-04.webp
deleted file mode 100644
index 07bc34b844..0000000000
Binary files a/static/images/social-sdk/design-guidelines/ConnectionPoints-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/ConnectionPoints-05.webp b/static/images/social-sdk/design-guidelines/ConnectionPoints-05.webp
deleted file mode 100644
index 9490690523..0000000000
Binary files a/static/images/social-sdk/design-guidelines/ConnectionPoints-05.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Consoles-02.webp b/static/images/social-sdk/design-guidelines/Consoles-02.webp
deleted file mode 100644
index 681cfb3c09..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Consoles-02.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Consoles-03.webp b/static/images/social-sdk/design-guidelines/Consoles-03.webp
deleted file mode 100644
index 0bd58fa800..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Consoles-03.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Consoles-04.webp b/static/images/social-sdk/design-guidelines/Consoles-04.webp
deleted file mode 100644
index ba10e2d148..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Consoles-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Consoles-05.webp b/static/images/social-sdk/design-guidelines/Consoles-05.webp
deleted file mode 100644
index 50f1b420be..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Consoles-05.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Consoles-06.webp b/static/images/social-sdk/design-guidelines/Consoles-06.webp
deleted file mode 100644
index 390e35f911..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Consoles-06.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/DMs-03.webp b/static/images/social-sdk/design-guidelines/DMs-03.webp
deleted file mode 100644
index b0e509c2a5..0000000000
Binary files a/static/images/social-sdk/design-guidelines/DMs-03.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/DMs-04.webp b/static/images/social-sdk/design-guidelines/DMs-04.webp
deleted file mode 100644
index 08812efd63..0000000000
Binary files a/static/images/social-sdk/design-guidelines/DMs-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/GameFriends-02.webp b/static/images/social-sdk/design-guidelines/GameFriends-02.webp
deleted file mode 100644
index dfe73b6fb1..0000000000
Binary files a/static/images/social-sdk/design-guidelines/GameFriends-02.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/GameFriends-03.webp b/static/images/social-sdk/design-guidelines/GameFriends-03.webp
deleted file mode 100644
index 259f7f5419..0000000000
Binary files a/static/images/social-sdk/design-guidelines/GameFriends-03.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/GameFriends-04.webp b/static/images/social-sdk/design-guidelines/GameFriends-04.webp
deleted file mode 100644
index 4723fdd023..0000000000
Binary files a/static/images/social-sdk/design-guidelines/GameFriends-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/GameFriends-05.webp b/static/images/social-sdk/design-guidelines/GameFriends-05.webp
deleted file mode 100644
index aa3908ae26..0000000000
Binary files a/static/images/social-sdk/design-guidelines/GameFriends-05.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/GameFriends-06.webp b/static/images/social-sdk/design-guidelines/GameFriends-06.webp
deleted file mode 100644
index abbee0638a..0000000000
Binary files a/static/images/social-sdk/design-guidelines/GameFriends-06.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/GameFriends-07.webp b/static/images/social-sdk/design-guidelines/GameFriends-07.webp
deleted file mode 100644
index 8c8e304704..0000000000
Binary files a/static/images/social-sdk/design-guidelines/GameFriends-07.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/GameFriends-08.webp b/static/images/social-sdk/design-guidelines/GameFriends-08.webp
deleted file mode 100644
index 90deeade66..0000000000
Binary files a/static/images/social-sdk/design-guidelines/GameFriends-08.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/GameFriends-09.webp b/static/images/social-sdk/design-guidelines/GameFriends-09.webp
deleted file mode 100644
index c10b5ab071..0000000000
Binary files a/static/images/social-sdk/design-guidelines/GameFriends-09.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/GameFriends-10.webp b/static/images/social-sdk/design-guidelines/GameFriends-10.webp
deleted file mode 100644
index 213bef9dd1..0000000000
Binary files a/static/images/social-sdk/design-guidelines/GameFriends-10.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/LinkedChannels-04.webp b/static/images/social-sdk/design-guidelines/LinkedChannels-04.webp
deleted file mode 100644
index 0d8b24f4b5..0000000000
Binary files a/static/images/social-sdk/design-guidelines/LinkedChannels-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/LinkedChannels-05.webp b/static/images/social-sdk/design-guidelines/LinkedChannels-05.webp
deleted file mode 100644
index 6d09cf065f..0000000000
Binary files a/static/images/social-sdk/design-guidelines/LinkedChannels-05.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/LinkedChannels-06.webp b/static/images/social-sdk/design-guidelines/LinkedChannels-06.webp
deleted file mode 100644
index 0ac5e574d4..0000000000
Binary files a/static/images/social-sdk/design-guidelines/LinkedChannels-06.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/LinkedChannels-07.webp b/static/images/social-sdk/design-guidelines/LinkedChannels-07.webp
deleted file mode 100644
index 800703edc3..0000000000
Binary files a/static/images/social-sdk/design-guidelines/LinkedChannels-07.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Principle-03.webp b/static/images/social-sdk/design-guidelines/Principle-03.webp
deleted file mode 100644
index b52e636a47..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Principle-03.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Principle-04.webp b/static/images/social-sdk/design-guidelines/Principle-04.webp
deleted file mode 100644
index b38cceee73..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Principle-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Principle-05.webp b/static/images/social-sdk/design-guidelines/Principle-05.webp
deleted file mode 100644
index ed0e262fb4..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Principle-05.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Principle-06.webp b/static/images/social-sdk/design-guidelines/Principle-06.webp
deleted file mode 100644
index 37cd2e784f..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Principle-06.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Principle-07.webp b/static/images/social-sdk/design-guidelines/Principle-07.webp
deleted file mode 100644
index cb604d69ad..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Principle-07.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Prov-02.webp b/static/images/social-sdk/design-guidelines/Prov-02.webp
deleted file mode 100644
index ec407aa279..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Prov-02.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Prov-03.webp b/static/images/social-sdk/design-guidelines/Prov-03.webp
deleted file mode 100644
index d2accb4826..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Prov-03.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Prov-04.webp b/static/images/social-sdk/design-guidelines/Prov-04.webp
deleted file mode 100644
index 8fc171591c..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Prov-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/Prov-05.webp b/static/images/social-sdk/design-guidelines/Prov-05.webp
deleted file mode 100644
index c0d0768d7b..0000000000
Binary files a/static/images/social-sdk/design-guidelines/Prov-05.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/SigningIn-02.webp b/static/images/social-sdk/design-guidelines/SigningIn-02.webp
deleted file mode 100644
index dbe0bee267..0000000000
Binary files a/static/images/social-sdk/design-guidelines/SigningIn-02.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/SigningIn-05.webp b/static/images/social-sdk/design-guidelines/SigningIn-05.webp
deleted file mode 100644
index 1f31f41df0..0000000000
Binary files a/static/images/social-sdk/design-guidelines/SigningIn-05.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/SigningIn-06.webp b/static/images/social-sdk/design-guidelines/SigningIn-06.webp
deleted file mode 100644
index 6688ece0de..0000000000
Binary files a/static/images/social-sdk/design-guidelines/SigningIn-06.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/SigningIn-07.webp b/static/images/social-sdk/design-guidelines/SigningIn-07.webp
deleted file mode 100644
index b0b44ffe85..0000000000
Binary files a/static/images/social-sdk/design-guidelines/SigningIn-07.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/SigningIn-08.webp b/static/images/social-sdk/design-guidelines/SigningIn-08.webp
deleted file mode 100644
index 30cd576ad7..0000000000
Binary files a/static/images/social-sdk/design-guidelines/SigningIn-08.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/StatusPresence-02.webp b/static/images/social-sdk/design-guidelines/StatusPresence-02.webp
deleted file mode 100644
index fae0204a62..0000000000
Binary files a/static/images/social-sdk/design-guidelines/StatusPresence-02.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/StatusPresence-03.webp b/static/images/social-sdk/design-guidelines/StatusPresence-03.webp
deleted file mode 100644
index 1bd3cf6656..0000000000
Binary files a/static/images/social-sdk/design-guidelines/StatusPresence-03.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/StatusPresence-04.webp b/static/images/social-sdk/design-guidelines/StatusPresence-04.webp
deleted file mode 100644
index 1779f5a150..0000000000
Binary files a/static/images/social-sdk/design-guidelines/StatusPresence-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/StatusPresence-05.webp b/static/images/social-sdk/design-guidelines/StatusPresence-05.webp
deleted file mode 100644
index 10cfde0061..0000000000
Binary files a/static/images/social-sdk/design-guidelines/StatusPresence-05.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/StatusPresence-06.webp b/static/images/social-sdk/design-guidelines/StatusPresence-06.webp
deleted file mode 100644
index cfde921624..0000000000
Binary files a/static/images/social-sdk/design-guidelines/StatusPresence-06.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/UFL-02.webp b/static/images/social-sdk/design-guidelines/UFL-02.webp
deleted file mode 100644
index eda3d45053..0000000000
Binary files a/static/images/social-sdk/design-guidelines/UFL-02.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/UFL-03.webp b/static/images/social-sdk/design-guidelines/UFL-03.webp
deleted file mode 100644
index 27cdb10190..0000000000
Binary files a/static/images/social-sdk/design-guidelines/UFL-03.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/UFL-04.webp b/static/images/social-sdk/design-guidelines/UFL-04.webp
deleted file mode 100644
index 042be47379..0000000000
Binary files a/static/images/social-sdk/design-guidelines/UFL-04.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/UFL-05.webp b/static/images/social-sdk/design-guidelines/UFL-05.webp
deleted file mode 100644
index 43e1205ff0..0000000000
Binary files a/static/images/social-sdk/design-guidelines/UFL-05.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/UFL-07.webp b/static/images/social-sdk/design-guidelines/UFL-07.webp
deleted file mode 100644
index 4603c86e00..0000000000
Binary files a/static/images/social-sdk/design-guidelines/UFL-07.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/UFL-08.webp b/static/images/social-sdk/design-guidelines/UFL-08.webp
deleted file mode 100644
index ae143b87c7..0000000000
Binary files a/static/images/social-sdk/design-guidelines/UFL-08.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/animated/Connecting-via-Browser.webp b/static/images/social-sdk/design-guidelines/animated/Connecting-via-Browser.webp
deleted file mode 100644
index e80c91f098..0000000000
Binary files a/static/images/social-sdk/design-guidelines/animated/Connecting-via-Browser.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/animated/Connecting-via-Client.webp b/static/images/social-sdk/design-guidelines/animated/Connecting-via-Client.webp
deleted file mode 100644
index e2712b31a5..0000000000
Binary files a/static/images/social-sdk/design-guidelines/animated/Connecting-via-Client.webp and /dev/null differ
diff --git a/static/images/social-sdk/design-guidelines/animated/LinkedChannel-Setup.webp b/static/images/social-sdk/design-guidelines/animated/LinkedChannel-Setup.webp
deleted file mode 100644
index 246c75450c..0000000000
Binary files a/static/images/social-sdk/design-guidelines/animated/LinkedChannel-Setup.webp and /dev/null differ
diff --git a/static/images/social-sdk/development-guides/authorize_device.webp b/static/images/social-sdk/development-guides/authorize_device.webp
deleted file mode 100644
index 7b1edd6307..0000000000
Binary files a/static/images/social-sdk/development-guides/authorize_device.webp and /dev/null differ
diff --git a/static/images/social-sdk/development-guides/discord-game-dm-settings.webp b/static/images/social-sdk/development-guides/discord-game-dm-settings.webp
deleted file mode 100644
index 82ce3c041a..0000000000
Binary files a/static/images/social-sdk/development-guides/discord-game-dm-settings.webp and /dev/null differ
diff --git a/static/images/social-sdk/getting-started/partials/error.webp b/static/images/social-sdk/getting-started/partials/error.webp
deleted file mode 100644
index 89633291aa..0000000000
Binary files a/static/images/social-sdk/getting-started/partials/error.webp and /dev/null differ
diff --git a/static/images/social-sdk/getting-started/partials/open-anyway.webp b/static/images/social-sdk/getting-started/partials/open-anyway.webp
deleted file mode 100644
index 8fcd47f55f..0000000000
Binary files a/static/images/social-sdk/getting-started/partials/open-anyway.webp and /dev/null differ
diff --git a/static/images/social-sdk/integrating-moderation/message-receiving.svg b/static/images/social-sdk/integrating-moderation/message-receiving.svg
deleted file mode 100644
index b108affd72..0000000000
--- a/static/images/social-sdk/integrating-moderation/message-receiving.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/static/images/social-sdk/integrating-moderation/message-sending.svg b/static/images/social-sdk/integrating-moderation/message-sending.svg
deleted file mode 100644
index d348e9a9c5..0000000000
--- a/static/images/social-sdk/integrating-moderation/message-sending.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/static/images/social-sdk/integrating-moderation/platform-bans.svg b/static/images/social-sdk/integrating-moderation/platform-bans.svg
deleted file mode 100644
index 68a9c01dfc..0000000000
--- a/static/images/social-sdk/integrating-moderation/platform-bans.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/static/images/social-sdk/overview/social_sdk_header.webp b/static/images/social-sdk/overview/social_sdk_header.webp
deleted file mode 100644
index b18e330f44..0000000000
Binary files a/static/images/social-sdk/overview/social_sdk_header.webp and /dev/null differ
diff --git a/.prettierrc.json b/tools/.prettierrc.json
similarity index 100%
rename from .prettierrc.json
rename to tools/.prettierrc.json
diff --git a/tools/checkBuild.ts b/tools/checkBuild.ts
index b8a18e1f7d..f4c5aded44 100644
--- a/tools/checkBuild.ts
+++ b/tools/checkBuild.ts
@@ -6,7 +6,7 @@ const args = process.argv.slice(2);
const bail = args.includes("--bail");
const ROOT_DIR = path.join(import.meta.dirname, "..");
-const DOCS_DIR = path.join(ROOT_DIR, "docs");
+const DOCS_DIR = path.join(ROOT_DIR, "discord", "developers", "docs");
const extensions = [".mdx", ".md"];
let hasErrors = false;
diff --git a/tools/checkLinks.ts b/tools/checkLinks.ts
deleted file mode 100644
index 47be96bc7a..0000000000
--- a/tools/checkLinks.ts
+++ /dev/null
@@ -1,216 +0,0 @@
-import { readdirSync, statSync, readFileSync } from "node:fs";
-import path from "node:path";
-import chalk from "chalk";
-import * as github from "@actions/core";
-import * as yaml from "js-yaml";
-const cwd = process.env.GITHUB_ACTIONS ? process.env.GITHUB_WORKSPACE! : process.cwd();
-
-interface Frontmatter {
- title?: string;
- date?: string;
- breaking: boolean;
-}
-
-function importDirectory(directory: string, extensions: string[], subdirectories = true) {
- try {
- const output = new Map();
- const files = readdirSync(directory);
- for (const fileOrPath of files) {
- const currentPath = path.join(directory, fileOrPath);
- if (statSync(currentPath).isDirectory()) {
- if (!subdirectories) continue;
- const subdir = importDirectory(currentPath, extensions, subdirectories);
- if (!subdir) continue;
- for (const [name, read] of subdir) {
- output.set(`/${fileOrPath}${name}`, read);
- }
- continue;
- }
- const currentPathParts = path.parse(currentPath);
- if (!extensions.some((ex) => ex === currentPathParts.ext)) continue;
- const read = readFileSync(currentPath, "utf8");
- output.set(`/${currentPathParts.name}`, read);
- }
- return output;
- } catch {
- // Directory likely does not exist, we should be able to safely discard this error
- return null;
- }
-}
-
-function printResults(resultMap: Map): void {
- let output = "\n";
- let total = 0;
- for (const [resultFile, resultArr] of resultMap) {
- if (resultArr.length <= 0) continue;
- const filePath = path.join(cwd, resultFile);
- output += `${chalk.underline(filePath)}\n`;
- output += resultArr.reduce((result, props) => {
- total += 1;
- return `${result} ${props.startLine ?? ""}:${props.startColumn ?? ""}-${props.endColumn ?? ""} ${chalk.yellow(
- "warning",
- )} ${props.title ?? ""}\n`;
- }, "");
- output += "\n";
- }
- output += "\n";
- if (total > 0) {
- output += chalk.red.bold(`\u2716 ${total} problem${total === 1 ? "" : "s"}\n`);
- }
- console.log(output);
-}
-
-function annotateResults(resultMap: Map): void {
- let total = 0;
- for (const [resultFile, resultArr] of resultMap) {
- if (resultArr.length <= 0) continue;
- github.startGroup(resultFile);
- for (const result of resultArr) {
- total += 1;
- console.log(
- `::warning file=${resultFile},title=Invalid Link,line=${result.startLine ?? 0},endLine=${
- result.startLine ?? 0
- },col=${result.startColumn ?? 0},endColumn=${result.endColumn ?? result.startColumn ?? 0}::${
- result.title ?? "Invalid Link"
- }`,
- );
- }
- github.endGroup();
- }
- if (total > 0) {
- github.setFailed("One or more links are invalid!");
- }
-}
-
-function* concatIterables(...iterables: IterableIterator[]) {
- for (const iterable of iterables) {
- for (const value of iterable) {
- yield value;
- }
- }
-}
-
-const docFiles = importDirectory(path.join(cwd, "docs"), [".md", ".mdx"]);
-
-if (!docFiles) {
- console.error("No doc files found!");
- process.exit(1);
-}
-
-const validLinks = new Map([
- ["APPLICATIONS", []],
- ["SERVERS", []],
- ["TEAMS", []],
-]);
-
-// Gather valid links
-const changelogAnchors = [];
-for (const [name, raw] of docFiles) {
- const keyName = `/docs${name}`;
- if (!validLinks.has(keyName)) {
- validLinks.set(keyName, []);
- }
- const validAnchors = validLinks.get(keyName)!;
-
- // The changelog is unique in that each entry acts as it's own potential page,
- // and each entry can be represented in a single page under it's own H2.
- // This collects all potential change-log pages, and adds them to the list of
- // available anchors under `/change-log`.
- if (name.startsWith("/change-log/")) {
- const frontmatter = raw.split("---")[1];
- const parsedFrontmatter = yaml.load(frontmatter) as Frontmatter;
- const title = parsedFrontmatter?.title;
- if (title) {
- const anchor = title
- .replace(/[^ A-Z0-9]/gi, "")
- .trim()
- .replace(/ +/g, "-")
- .toLowerCase();
- changelogAnchors.push(anchor);
- }
- }
-
- let parentAnchor = "";
- let multilineCode = false;
- for (const line of raw.split("\n")) {
- if (line.trim().startsWith("```")) {
- multilineCode = !multilineCode;
- if (line.trim().length > 3 && line.trim().endsWith("```")) multilineCode = !multilineCode;
- }
- if (multilineCode || !line.startsWith("#")) continue;
- const anchor = line
- .split("%")[0]
- .replace(/[^ A-Z0-9]/gi, "")
- .trim()
- .replace(/ +/g, "-")
- .toLowerCase();
- if (/^#{1,5}(?!#)/.test(line.trim())) {
- parentAnchor = `${anchor}-`;
- validAnchors.push(anchor);
- continue;
- }
- validAnchors.push(`${parentAnchor}${anchor}`);
- }
-}
-
-// Add changelog anchors to the list of valid links
-validLinks.get("/docs/change-log")?.push(...changelogAnchors);
-
-const results = new Map();
-
-// Check Links
-for (const [name, raw] of docFiles) {
- const fileName = `docs${name}`;
- const file = raw.split("\n");
- if (!results.has(fileName)) {
- results.set(fileName, []);
- }
- const ownResults = results.get(fileName)!;
- let multilineCode = false;
- file.forEach((line, lineNum) => {
- if (line.trim().startsWith("```")) {
- multilineCode = !multilineCode;
- if (line.trim().length > 3 && line.trim().endsWith("```")) multilineCode = !multilineCode;
- }
- if (multilineCode) return;
- const markdownMatches = line.matchAll(/(?.+?)\)(?!`)/g);
- const componentMatches = line.matchAll(/(?:link|href)="(?!https?|mailto)(?.+?)"/g);
-
- for (const match of concatIterables(markdownMatches, componentMatches)) {
- if (!match.groups) continue;
- const [page, anchor] = match.groups?.link.split("#") ?? [];
- if (!validLinks.has(page)) {
- // Automatically ignore links with "image/" as the prefix, since the link checker is not designed to validate images.
- if (page.startsWith("images/")) continue;
-
- ownResults.push({
- title: `Base url ${chalk.blueBright(page)} does not exist`,
- startLine: lineNum + 1,
- startColumn: match.index,
- endColumn: (match.index ?? 0) + match[0].length,
- });
- continue;
- }
-
- if (!anchor) continue;
- if (!validLinks.get(page)!.includes(anchor)) {
- const suggestions = validLinks.get(page)!.filter((a) => a.includes(anchor));
- const suggestionText = suggestions.length > 0 ? ` Did you mean one of (${suggestions.join(", ")})?` : "";
- ownResults.push({
- title: `Anchor ${chalk.cyan(anchor)} does not exist on ${chalk.blueBright(page)}${suggestionText}`,
- startLine: lineNum + 1,
- startColumn: match.index,
- endColumn: (match.index ?? 0) + match[0].length,
- });
- }
- }
- });
-}
-
-if (results.size > 0) {
- if (process.env.GITHUB_ACTIONS) {
- annotateResults(results);
- } else {
- printResults(results);
- }
-}
diff --git a/tools/doxygen/decorate-social-sdk-references.js b/tools/doxygen/decorate-social-sdk-references.js
index 8b75ec2d4a..4214acc9f7 100644
--- a/tools/doxygen/decorate-social-sdk-references.js
+++ b/tools/doxygen/decorate-social-sdk-references.js
@@ -7,7 +7,7 @@ const __dirname = path.dirname(__filename);
// Configure paths
const REPO_ROOT = path.resolve(__dirname, "..", "..");
-const MARKDOWN_DIR = path.join(REPO_ROOT, "docs");
+const MARKDOWN_DIR = path.join(REPO_ROOT, "/discord/developers/docs");
const MAPPING_FILE = path.join(__dirname, "social-sdk-mappings.json");
// Helper function to ensure paths are resolved correctly
@@ -137,7 +137,7 @@ const processMarkdownFile = (filePath, mapping) => {
if (hasChanged) {
fs.writeFileSync(filePath, newContent, "utf-8");
- // eslint-disable-next-line no-undef
+
console.log(`Updated ${filePath} with ${referencesFound.size} references`);
}
@@ -151,7 +151,6 @@ const processMarkdownFile = (filePath, mapping) => {
const processMarkdownFiles = async () => {
const mapping = loadMapping();
if (!Object.keys(mapping).length) {
- // eslint-disable-next-line no-undef
console.error("Mapping is empty! Make sure the JSON is generated correctly.");
return;
}
@@ -174,12 +173,10 @@ const processMarkdownFiles = async () => {
}
if (filesUpdated > 0) {
- // eslint-disable-next-line no-undef
console.log(
`\nSDK reference links processed. Updated ${filesUpdated} files with ${totalReferences} total references.`,
);
} else {
- // eslint-disable-next-line no-undef
console.log("SDK reference links processed. No changes were made to any files.");
}
};
diff --git a/tools/doxygen/generate-social-sdk-mapping.js b/tools/doxygen/generate-social-sdk-mapping.js
index a957777f77..df055dd42d 100644
--- a/tools/doxygen/generate-social-sdk-mapping.js
+++ b/tools/doxygen/generate-social-sdk-mapping.js
@@ -92,10 +92,9 @@ const generateMapping = async () => {
const outputJsonPath = resolvePath(OUTPUT_JSON, true);
await fs.promises.writeFile(outputJsonPath, JSON.stringify(mapping, null, 2));
- // eslint-disable-next-line no-undef
console.log(`JSON mapping saved to ${outputJsonPath}`);
};
// Run the script
-// eslint-disable-next-line no-undef
+
generateMapping().catch(console.error);
diff --git a/eslint.config.js b/tools/eslint.config.js
similarity index 100%
rename from eslint.config.js
rename to tools/eslint.config.js
diff --git a/package-lock.json b/tools/package-lock.json
similarity index 99%
rename from package-lock.json
rename to tools/package-lock.json
index 50109a1c43..ded68f55f6 100644
--- a/package-lock.json
+++ b/tools/package-lock.json
@@ -1023,10 +1023,11 @@
}
},
"node_modules/@typescript-eslint/typescript-estree/node_modules/brace-expansion": {
- "version": "2.0.1",
- "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.1.tgz",
- "integrity": "sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==",
+ "version": "2.0.2",
+ "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz",
+ "integrity": "sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==",
"dev": true,
+ "license": "MIT",
"dependencies": {
"balanced-match": "^1.0.0"
}
@@ -1196,10 +1197,11 @@
"dev": true
},
"node_modules/brace-expansion": {
- "version": "1.1.11",
- "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
- "integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
+ "version": "1.1.12",
+ "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.12.tgz",
+ "integrity": "sha512-9T9UjW3r0UW5c1Q7GTwllptXwhvYmEzFhzMfZ9H7FQWt+uZePjZPjBP/W1ZEyZ1twGWom5/56TF4lPcqjnDHcg==",
"dev": true,
+ "license": "MIT",
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
@@ -1333,10 +1335,11 @@
"dev": true
},
"node_modules/cross-spawn": {
- "version": "7.0.3",
- "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz",
- "integrity": "sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==",
+ "version": "7.0.6",
+ "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.6.tgz",
+ "integrity": "sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==",
"dev": true,
+ "license": "MIT",
"dependencies": {
"path-key": "^3.1.0",
"shebang-command": "^2.0.0",
@@ -2542,10 +2545,11 @@
}
},
"node_modules/markdown-table-formatter/node_modules/brace-expansion": {
- "version": "2.0.1",
- "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.1.tgz",
- "integrity": "sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==",
+ "version": "2.0.2",
+ "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz",
+ "integrity": "sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==",
"dev": true,
+ "license": "MIT",
"dependencies": {
"balanced-match": "^1.0.0"
}
@@ -3377,12 +3381,13 @@
]
},
"node_modules/micromatch": {
- "version": "4.0.5",
- "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.5.tgz",
- "integrity": "sha512-DMy+ERcEW2q8Z2Po+WNXuw3c5YaUSFjAO5GsJqfEl7UjvtIuFKO6ZrKvcItdy98dwFI2N1tg3zNIdKaQT+aNdA==",
+ "version": "4.0.8",
+ "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.8.tgz",
+ "integrity": "sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==",
"dev": true,
+ "license": "MIT",
"dependencies": {
- "braces": "^3.0.2",
+ "braces": "^3.0.3",
"picomatch": "^2.3.1"
},
"engines": {
diff --git a/package.json b/tools/package.json
similarity index 68%
rename from package.json
rename to tools/package.json
index 0de41b6246..2e4aa1ae8d 100644
--- a/package.json
+++ b/tools/package.json
@@ -1,7 +1,7 @@
{
"name": "discord-api-docs",
"version": "1.1.1",
- "description": "Documentation for using Discord's API",
+ "description": "Documentation for using Discord's Developer Platform",
"main": "index.js",
"type": "module",
"directories": {
@@ -14,7 +14,7 @@
"type": "git",
"url": "git+https://github.com/discord/discord-api-docs.git"
},
- "author": "Discord Krew",
+ "author": "Discord for Developers",
"license": "MIT",
"bugs": {
"url": "https://github.com/discord/discord-api-docs/issues"
@@ -22,13 +22,12 @@
"homepage": "https://github.com/discord/discord-api-docs#readme",
"scripts": {
"build": "tsc",
- "lint": "eslint tools",
- "lint:fix": "eslint tools --fix",
- "test:links": "tsx tools/checkLinks.ts",
- "test:build": "tsx tools/checkBuild.ts",
- "test:tables": "npx markdown-table-formatter \"docs/**/*.{md,mdx}\" --check",
- "fix:tables": "npx markdown-table-formatter \"docs/**/*.{md,mdx}\"",
- "decorate:docs": "node tools/doxygen/generate-social-sdk-mapping.js && node tools/doxygen/decorate-social-sdk-references.js"
+ "lint": "eslint",
+ "lint:fix": "eslint --fix",
+ "test:build": "tsx checkBuild.ts",
+ "test:tables": "npx markdown-table-formatter \"../discord/developers/docs/**/*.{md,mdx}\" --check",
+ "fix:tables": "npx markdown-table-formatter \"../discord/developers/docs/**/*.{md,mdx}\"",
+ "decorate:docs": "node ./doxygen/generate-social-sdk-mapping.js && node ./doxygen/decorate-social-sdk-references.js"
},
"devDependencies": {
"@actions/core": "^1.10.1",
diff --git a/tools/parse-changelog.js b/tools/parse-changelog.js
index dc63539fed..b21e047416 100644
--- a/tools/parse-changelog.js
+++ b/tools/parse-changelog.js
@@ -65,7 +65,7 @@ breaking: ${file.breaking ? "true" : "false"}
.replace(/[ _:&,/*]/g, "-")
.replace(/---/g, "-")
.replace(/--/g, "-");
- // eslint-disable-next-line no-undef
+
console.log(slug);
await fs.writeFile(`./docs/change_log/${slug}.md`, content);
}
diff --git a/tsconfig.json b/tools/tsconfig.json
similarity index 100%
rename from tsconfig.json
rename to tools/tsconfig.json