Added Components v2 (#7487)

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