WIP: Rework navigation to make sense

src/content/docs/dropins/cart/slots.mdx

@@ -8,7 +8,7 @@ tableOfContents:
 
 Learn about the slots provided in the Cart drop-in component.
 
-[Extending drop-in components](/dropins/all/extending/) describes default properties available to all slots.
+[Extending drop-in components](/dropins/extending/) describes default properties available to all slots.
 
 ## CartSummaryList slots
 

src/content/docs/dropins/checkout/slots.mdx

@@ -10,7 +10,7 @@ import Aside from '@components/Aside.astro';
 
 Learn about the slots provided in the checkout drop-in component.
 
-[Extending drop-in components](/dropins/all/extending/) describes the default properties available to all slots.
+[Extending drop-in components](/dropins/extending/) describes the default properties available to all slots.
 
 ## PaymentMethods slots
 

src/content/docs/dropins/all/introduction.mdx → src/content/docs/dropins/introduction.mdx

@@ -66,16 +66,16 @@ All drop-in components can be customized in five ways: design tokens, CSS classe
 
 ### Design tokens
 
-[Design tokens](/dropins/all/branding/) are the quickest way to customize your storefront. By changing the default token values with your own brand colors, typography, spacing, and shapes, you can make quick, global brand changes to your entire storefront.
+[Design tokens](/dropins/branding/) are the quickest way to customize your storefront. By changing the default token values with your own brand colors, typography, spacing, and shapes, you can make quick, global brand changes to your entire storefront.
 
 ### CSS classes
 
-[CSS classes](/dropins/all/styling/) provide deeper style changes for drop-in components than design tokens. Overriding or adding new CSS classes allows you to restyle specific areas of the drop-in component. You'll find best practices for styling here.
+[CSS classes](/dropins/styling/) provide deeper style changes for drop-in components than design tokens. Overriding or adding new CSS classes allows you to restyle specific areas of the drop-in component. You'll find best practices for styling here.
 
 ### Slots
 
-[Slots](/dropins/all/extending/) provide the deepest level of customization. Slots are built-in extension points in the drop-in component to add your own UI components and functions. You'll learn how powerful slots can be.
+[Slots](/dropins/extending/) provide the deepest level of customization. Slots are built-in extension points in the drop-in component to add your own UI components and functions. You'll learn how powerful slots can be.
 
 ### Localization
 
-[Localization](/dropins/all/labeling/) is one of the easiest ways to customize drop-in components for a region. This topic shows you how to add and use a second language file in your drop-in components.
+[Localization](/dropins/labeling/) is one of the easiest ways to customize drop-in components for a region. This topic shows you how to add and use a second language file in your drop-in components.

src/content/docs/dropins/all/labeling.mdx → src/content/docs/dropins/labeling.mdx

@@ -1,5 +1,5 @@
 ---
-title: Labeling and localizing drop-in components
+title: Localizing drop-in components
 description: How to localize your drop-in components.
 sidebar:
   label: Labeling
@@ -26,7 +26,7 @@ In this topic, you will learn how to update drop-in component labels by using th
 
 ### Placeholders file
 
-A `placeholders` content sheet where you can manage labels for your storefront, which includes localization. See the [Placeholders file](/resources/placeholders/) for more information.
+A `placeholders` content sheet where you can manage labels for your storefront, which includes localization. See the [Placeholders file](https://www.aem.live/docs/placeholders) for more information.
 
 ### Language objects
 

src/content/docs/dropins/order/slots.mdx

@@ -5,7 +5,7 @@ description: Learn about the slots provided in the order drop-in component.
 
 This topic describes the slots that are provided in the order drop-in component.
 
-[Extending drop-in components](/dropins/all/extending/) describes the default properties available to all slots.
+[Extending drop-in components](/dropins/extending/) describes the default properties available to all slots.
 
 ## CreateReturn slots
 

src/content/docs/dropins/product-details/index.mdx

@@ -59,4 +59,4 @@ The PDP component supports rendering different product types configured in your
 
 Generating product metadata is crucial for optimizing search engine visibility, enhancing user experience, integrating with social media, supporting ecommerce functionality, ensuring compliance, and enabling data-driven decision-making.
 
-The Commerce boilerplate provides a [metadata generation script](/setup/seo/metadata/#generate-metadata) that fetches product data from the Catalog Service GraphQL API and generates meta tags and structured data in JSON-LD format. The script writes the metadata to an Excel file, which you can upload to Edge Delivery Services.
+The Commerce boilerplate provides a [metadata generation script](/setup/metadata/#generate-metadata) that fetches product data from the Catalog Service GraphQL API and generates meta tags and structured data in JSON-LD format. The script writes the metadata to an Excel file, which you can upload to Edge Delivery Services.

src/content/docs/dropins/product-details/slots.mdx

@@ -39,7 +39,7 @@ The following slots are not currently in use within the default PDP drop-in:
 
 ## PDP SlotProps
 
-The slots for product details are defined in the `ProductDetailsProps` interface. Each slot comes with a set of [primitive functions](/dropins/all/extending/) and may be extended with custom functions, such as `appendButton`.
+The slots for product details are defined in the `ProductDetailsProps` interface. Each slot comes with a set of [primitive functions](/dropins/extending/) and may be extended with custom functions, such as `appendButton`.
 
 ```typescript
 slots?: {

src/content/docs/dropins/user-auth/slots.mdx

@@ -9,7 +9,7 @@ import OptionsTable from '@components/OptionsTable.astro';
 
 The UserAuth drop-in component provides several slots that can be used to customize the presentation of its containers.
 
-[Extending drop-in components](/dropins/all/extending/) describes default properties available to all slots.
+[Extending drop-in components](/dropins/extending/) describes default properties available to all slots.
 
 ## PrivacyPolicyConsent slot
 

src/content/docs/get-started/boilerplate-project.mdx

@@ -109,11 +109,11 @@ The file structure of the storefront boilerplate is shown here. Detailed descrip
 
 ### Commerce drop-in components
 
-Full-featured shopping components that turn websites into storefronts. [Drop-in components](/setup/discovery/architecture/#drop-in-components-and-widgets) are not primitive components, like Carousels and Galleries. They provide the entire storefront shopping experience for a website using pages and other commerce features.
+Full-featured shopping components that turn websites into storefronts. [Drop-in components](/setup/architecture/#drop-in-components-and-widgets) are not primitive components, like Carousels and Galleries. They provide the entire storefront shopping experience for a website using pages and other commerce features.
 
 ### Commerce blocks
 
-The integration of Commerce drop-in components into the Edge Delivery Services architecture of JavaScript blocks and document-based authoring. [Commerce blocks](/setup/discovery/architecture/#commerce-blocks) are the components that provide the content and layout for commerce pages in the storefront.
+The integration of Commerce drop-in components into the Edge Delivery Services architecture of JavaScript blocks and document-based authoring. [Commerce blocks](/setup/architecture/#commerce-blocks) are the components that provide the content and layout for commerce pages in the storefront.
 
 ### Content blocks
 

src/content/docs/merchants/get-started/experiments.mdx

@@ -46,7 +46,7 @@ To install and configure the plugin, follow the instructions in the [AEM Experim
 
 ### Placeholders file
 
-A `placeholders` sheet in your content folder where you change and maintain your storefront's labels, which includes localization. See the [Placeholders file](/resources/placeholders/) for more information.
+A `placeholders` sheet in your content folder where you change and maintain your storefront's labels, which includes localization.
 
 </Vocabulary>
 

src/content/docs/merchants/get-started/multistore.mdx

@@ -17,7 +17,7 @@ To maintain storefronts that implement Edge Delivery Services, you must be famil
 * [Authoring and Publishing Content](https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/document-authoring/authoring)
 * [Placeholders](https://www.aem.live/docs/placeholders)
 * [Adobe Commerce Configuration Scope](https://experienceleague.adobe.com/en/docs/commerce-admin/config/scope-change)
-* [Storefront Configuration](/setup/configuration/commerce-configuration/)
+* [Storefront Configuration](/setup/commerce-configuration/)
 * [Folder Mapping](https://www.aem.live/developer/folder-mapping)
 
 ## Big Picture
@@ -120,9 +120,9 @@ To learn more about the Config Service, please see [aem.live's documentation](ht
 
 ### Site Config
 
-You must update your [storefront config](/setup/configuration/commerce-configuration/) to include configuration overrides for the new store view. In this file, you'll define store-view specific settings, such as service headers and analytics values. The `key` of each overridden object must match the root folder path of the corresponding store view. These values will be merged into the default configuration.
+You must update your [storefront config](/setup/commerce-configuration/) to include configuration overrides for the new store view. In this file, you'll define store-view specific settings, such as service headers and analytics values. The `key` of each overridden object must match the root folder path of the corresponding store view. These values will be merged into the default configuration.
 
-The `analytics` section contains the Adobe Commerce environment variables for the store view. These variables are used by the Analytics API. For more details, see [Analytics](/setup/analytics/instrumentation).
+The `analytics` section contains the Adobe Commerce environment variables for the store view. These variables are used by the Analytics API. For more details, see [Analytics](/setup/instrumentation).
 
 ```json
 {

src/content/docs/releases/index.mdx

@@ -49,12 +49,12 @@ Slots are built-in extension points in the drop-in components to add your own UI
 | Type | Description |
 |---|---|
 | Default properties available to all slots: | Function signatures of the following functions:<br/>`prependSibling`<br/>`prependChild`<br/>`replaceWith`<br/>`appendChild`<br/>`appendSibling`<br/>`getSlotElement`<br/>`onChange` |
-| | Structure of the [`dictionary`](/dropins/all/labeling/#drop-in-component-dictionaries) object |
+| | Structure of the [`dictionary`](/dropins/labeling/#drop-in-component-dictionaries) object |
 | Individual drop-in slots | Function signatures as defined elsewhere on this site (for example, [cart slots](https://experienceleague.adobe.com/developer/commerce/storefront/dropins/cart/slots/)) |
 
 #### Drop-in design tokens
 
-Drop-in [design tokens](/dropins/all/branding/#design-tokens) are defined in the drop-in SDK and are used by the drop-in components to style the storefront application.
+Drop-in [design tokens](/dropins/branding/#design-tokens) are defined in the drop-in SDK and are used by the drop-in components to style the storefront application.
 
 ## Drop-in components