Added Components v2

Author: anthonydiscord

docs/change-log/2017-07-24-new-feature-audit-logs.md

@@ -3,4 +3,4 @@ title: "New Feature: Audit Logs"
 date: "2017-07-24"
 ---
 
-Audit logs are here! Well, they've been here all along, but now we've got [documentation](/docs/resources/audit-log#) about them. Check it out, but remember: with great power comes great responsibility.
+Audit logs are here! Well, they've been here all along, but now we've got [documentation](/docs/resources/audit-log) about them. Check it out, but remember: with great power comes great responsibility.

docs/change-log/2018-01-23-deprecation-accept-invite-endpoint.md

@@ -3,4 +3,4 @@ title: "Deprecation: Accept Invite Endpoint"
 date: "2018-01-23"
 ---
 
-The [Accept Invite](/docs/resources/invite#) endpoint is deprecated starting today, and will be discontinued on March 23, 2018. The [Add Guild Member](/docs/resources/guild#add-guild-member) endpoint should be used in its place.
+The [Accept Invite](/docs/resources/invite) endpoint is deprecated starting today, and will be discontinued on March 23, 2018. The [Add Guild Member](/docs/resources/guild#add-guild-member) endpoint should be used in its place.

docs/change-log/2019-08-12-more-precise-rate-limits.md

@@ -3,4 +3,4 @@ title: "More Precise Rate Limits"
 date: "2019-08-12"
 ---
 
-You can now get more precise rate limit reset times, via a new request header. Check out the [rate limits](/docs/topics/rate-limits#) documentation for more information.
+You can now get more precise rate limit reset times, via a new request header. Check out the [rate limits](/docs/topics/rate-limits) documentation for more information.

docs/change-log/2020-12-15-slash-commands-and-interactions.md

@@ -3,7 +3,7 @@ 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 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:
 

docs/change-log/2021-05-26-buttons-and-message-components.md

@@ -5,7 +5,7 @@ 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/interactions/message-components#).
+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:
 

docs/change-log/2021-06-30-select-menu-components.md

@@ -5,4 +5,4 @@ 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/interactions/message-components#). Learn all the specifics in the [documentation](/docs/interactions/message-components#select-menus).
+Select menus can be used like other [message components](/docs/components/overview). Learn all the specifics in the [documentation](/docs/components/reference#string-select).

docs/change-log/2022-10-13-new-select-menu-components.md

@@ -3,13 +3,13 @@ title: "New Select Menu Components"
 date: "2022-10-13"
 ---
 
-Four new select menu [component types](/docs/interactions/message-components#component-object-component-types) have been added to make it easier to populate selects with common resources in Discord:
+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/interactions/message-components#select-menu-object-select-menu-interaction) apps receive also contain a [`resolved` field](/docs/interactions/message-components#select-menu-object-select-menu-resolved-object) for the new components.
+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#string-select-string-select-interaction) apps receive also contain a [`resolved` field](/docs/components/reference#string-select-select-menu-resolved-object) for the new components.
 
-More details can be found in the updated [select menu documentation](/docs/interactions/message-components#select-menus).
+More details can be found in the updated [select menu documentation](/docs/components/reference#component-object-component-types).

docs/change-log/2023-09-22-default-value-in-auto-populated-select-menus.md

@@ -3,4 +3,4 @@ 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/interactions/message-components#select-menus). `default_values` is a list of [default value objects](/docs/interactions/message-components#select-menu-object-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"`).
+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"`).

docs/change-log/2023-09-26-premium-app-subscriptions-available-in-the-us.md

@@ -17,6 +17,6 @@ Starting today, eligible US-based developers can monetize their verified apps wi
   * [Delete Test Entitlement](/docs/resources/entitlement#delete-test-entitlement)  `DELETE /applications/<application.id>/entitlements/<entitlement.id>`
 * [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)
+* 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).

docs/change-log/2024-06-17-premium-apps-new-premium-button-style-deep-linking-url-schemes.md

@@ -5,15 +5,15 @@ date: "2024-06-17"
 
 **New Premium Button Style**
 
-Introduces a new `premium` [button style](/docs/interactions/message-components#button-object-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.
+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/interactions/message-components#buttons).
+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/interactions/message-components#button-object-button-styles).
+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).
 

docs/change-log/2025-04-22-components-v2.md

@@ -0,0 +1,61 @@
+---
+title: "Introducing New Components for Messages!"
+date: "2025-04-22"
+topics:
+- "User Apps"
+- "HTTP API"
+- "Interactions"
+---
+
+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!

docs/components/overview.mdx

@@ -0,0 +1,44 @@
+---
+sidebar_label: Overview
+showTOC: false
+---
+
+# Components Overview
+
+Components allow you to add interactive elements to modals and the messages your app sends. They're accessible, customizable, and easy to use.
+
+![](images/components/hero.png)
+
+Discord apps support three types of message components: layout components, content components, and interactive components. Each type of component has its own purpose and use cases.
+
+- **Layout Components**: These components are used to organize and structure the content of your message. They help create a visually appealing and user-friendly layout.
+- **Content Components**: These components are used to display information and content in your message. They can include text, images, and other media.
+- **Interactive Components**: These components allow users to interact with your message. They can include buttons, select menus, and other interactive elements.
+
+All components are customizable and can be organized using layout components to create rich, interactive message experiences.
+
+To use components, messages must be sent with the `IS_COMPONENTS_V2` flag (`1<<15`). Note that using this flag disables traditional content and embeds - all content must be sent as components instead.
+
+:::info
+[Legacy message component behavior](/docs/components/reference#legacy-message-component-behavior) will **not** be deprecated and will continue to be available to your apps on a message-by-message basis. However, we recommend using the new components for new projects and features.
+:::
+
+<Container>
+  <Card title="Using Message Components" link="/docs/components/using-message-components" icon="ChatDotsIcon">
+    A guide on sending Message Components with examples.
+  </Card>
+   <Card title="Using Modal Components" link="/docs/components/using-modal-components" icon="CompassIcon">
+    A guide on sending Modal Components with examples.
+  </Card>
+  <Card title="Component Reference" link="/docs/components/reference" icon="BrowserIcon">
+    Explore the Components reference documentation.
+  </Card>
+</Container>
+
+---
+
+## Get Help & Join the Community
+
+Do you have a question or want to connect with other app developers? 
+
+- Join our [DDevs Discord Server](https://discord.gg/discord-developers) and get help from the community, share best practices, and discover new ways to enhance your apps.