diff --git a/astro.sidebar.mjs b/astro.sidebar.mjs
index 9ddc3ceb3..a3ef3da06 100644
--- a/astro.sidebar.mjs
+++ b/astro.sidebar.mjs
@@ -29,11 +29,16 @@ export function generateSidebar() {
             { label: 'Backend options', link: '/get-started/backends/' },
             { label: 'Luma Bridge', link: '/setup/discovery/luma-bridge/' },
             { label: 'Create a storefront', link: '/get-started/create-storefront/' },
-            { label: 'Plan your storefront project', link: '/setup/' },
             {
-              label: 'Licensing',
+              label: 'AI tools',
               collapsed: true,
-              autogenerate: { directory: '/licensing/' },
+              items: [
+                { label: 'Install the AI tools', link: '/ai/' },
+                { label: 'Boilerplate skills', link: '/ai/boilerplate-skills/' },
+                { label: 'Dropins AI tools', link: '/ai/dropins-ai-tools/' },
+                { label: 'Wayfinder', link: '/ai/wayfinder/' },
+                { label: 'LLM files', link: '/ai/static-text-files/' },
+              ],
             },
             {
               label: 'Boilerplate',
@@ -45,15 +50,9 @@ export function generateSidebar() {
               ],
             },
             {
-              label: 'AI tools',
+              label: 'Licensing',
               collapsed: true,
-              items: [
-                { label: 'Install the integrations', link: '/ai/' },
-                { label: 'Boilerplate skills', link: '/ai/boilerplate-skills/' },
-                { label: 'Dropins AI tools', link: '/ai/dropins-ai-tools/' },
-                { label: 'Wayfinder', link: '/ai/wayfinder/' },
-                { label: 'Fallback docs', link: '/ai/static-text-files/' },
-              ],
+              autogenerate: { directory: '/licensing/' },
             },
           ],
         },
diff --git a/src/components/HomeHero.astro b/src/components/HomeHero.astro
index e5a91ed45..8a9e997c5 100644
--- a/src/components/HomeHero.astro
+++ b/src/components/HomeHero.astro
@@ -12,19 +12,22 @@ const menuIcons = Object.fromEntries(
 const directories = [
   {
     label: 'For developers',
+    link: '/get-started/',
     aria: 'Developer documentation',
     categories: [
       {
         title: 'Getting started',
+        link: '/get-started/',
         links: [
           { title: 'Prerequisites', link: '/get-started/before-you-start/' },
           { title: 'Backend options', link: '/get-started/backends/' },
-          { title: 'Plan your storefront project', link: '/setup/' },
+          { title: 'Install the AI tools', link: '/ai/' },
           { title: 'Create a storefront', link: '/get-started/create-storefront/' },
         ],
       },
       {
         title: 'Architecture',
+        link: '/get-started/architecture/',
         links: [
           { title: 'How a page loads', link: '/get-started/architecture/how-a-page-loads/' },
           {
@@ -43,15 +46,17 @@ const directories = [
       },
       {
         title: 'Blocks',
+        link: '/blocks/',
         links: [
           { title: 'Blocks and drop-ins', link: '/blocks/blocks-and-dropins/' },
           { title: 'Customize blocks', link: '/blocks/customize-blocks/' },
-          { title: 'Arrange block layouts', link: '/blocks/arrange-block-layouts/' },
           { title: 'Create commerce blocks', link: '/blocks/create-commerce-blocks/' },
+          { title: 'Build commerce features', link: '/blocks/build-custom-features/' },
         ],
       },
       {
         title: 'Drop-ins',
+        link: '/dropins/all/introduction/',
         links: [
           { title: 'Drop-in containers', link: '/dropins/all/containers/' },
           { title: 'Container slots', link: '/dropins/all/slots/' },
@@ -61,6 +66,7 @@ const directories = [
       },
       {
         title: 'Configuration',
+        link: '/setup/configuration/',
         links: [
           {
             title: 'Storefront configuration',
@@ -76,6 +82,7 @@ const directories = [
       },
       {
         title: 'Production',
+        link: '/setup/launch/',
         links: [
           { title: 'Launch checklist', link: '/setup/launch/launch-checklist/' },
           { title: 'Performance best practices', link: '/get-started/performance/' },
@@ -87,10 +94,12 @@ const directories = [
   },
   {
     label: 'For authors',
+    link: '/merchants/quick-start/',
     aria: 'Content author documentation',
     categories: [
       {
         title: 'Getting started',
+        link: '/merchants/quick-start/',
         links: [
           { title: 'What is a storefront?', link: '/merchants/quick-start/create-content/' },
           { title: 'How a page comes together', link: '/merchants/quick-start/content-model/' },
@@ -100,6 +109,7 @@ const directories = [
       },
       {
         title: 'Authoring',
+        link: '/merchants/authoring/',
         links: [
           { title: 'Add a block to a page', link: '/how-tos/add-block-to-page/' },
           { title: 'Block table structure', link: '/merchants/blocks/block-tables/' },
@@ -112,6 +122,7 @@ const directories = [
       },
       {
         title: 'B2C blocks',
+        link: '/merchants/blocks/b2c/',
         links: [
           { title: 'Product Details', link: '/merchants/blocks/product-details/' },
           { title: 'Product List Page', link: '/merchants/blocks/product-list-page/' },
@@ -121,6 +132,7 @@ const directories = [
       },
       {
         title: 'B2B blocks',
+        link: '/merchants/blocks/b2b/',
         links: [
           { title: 'Company Profile', link: '/merchants/blocks/commerce-company-profile/' },
           {
@@ -133,6 +145,7 @@ const directories = [
       },
       {
         title: 'Customization',
+        link: '/merchants/content-customizations/',
         links: [
           { title: 'Show enrichment content', link: '/how-tos/show-enrichment-content/' },
           { title: 'Create a page experiment', link: '/how-tos/create-page-experiment/' },
@@ -142,6 +155,7 @@ const directories = [
       },
       {
         title: 'Publishing',
+        link: '/merchants/edge-delivery-services/',
         links: [
           { title: 'Scheduling options', link: '/merchants/edge-delivery-services/scheduling/' },
           { title: 'Translate content', link: '/how-tos/translate-storefront-content/' },
@@ -213,13 +227,17 @@ const sharedPaths = [
       directories.map((dir, i) => (
         <section class='home-hero__audience' aria-labelledby={`home-hero-audience-${i}`}>
           <h2 class='home-hero__audience-title' id={`home-hero-audience-${i}`}>
-            {dir.label}
+            <a class='home-hero__heading-link' href={setBasePath(dir.link)}>
+              {dir.label}
+            </a>
           </h2>
           <nav class='home-hero__categories' aria-label={dir.aria}>
             {dir.categories.map((category, j) => (
               <section class='home-hero__category' aria-labelledby={`home-hero-category-${i}-${j}`}>
                 <h3 class='home-hero__category-title' id={`home-hero-category-${i}-${j}`}>
-                  {category.title}
+                  <a class='home-hero__heading-link' href={setBasePath(category.link)}>
+                    {category.title}
+                  </a>
                 </h3>
                 <ul class='home-hero__link-list'>
                   {category.links.map((item) => (
@@ -237,23 +255,6 @@ const sharedPaths = [
       ))
     }
   </div>
-
-  <nav class='home-hero__reference' aria-label='Shared reference documentation'>
-    <ul class='home-hero__reference-list'>
-      {
-        sharedPaths.map((path) => (
-          <li>
-            <a class='home-hero__link' href={setBasePath(path.link)}>
-              <span>{path.title}</span>
-              <span class='home-hero__link-icon' aria-hidden='true'>
-                <Icon name='right-arrow' size='1rem' />
-              </span>
-            </a>
-          </li>
-        ))
-      }
-    </ul>
-  </nav>
 </section>
 
 <style>
@@ -424,7 +425,7 @@ const sharedPaths = [
     padding: 0.6rem 1.25rem;
     border-radius: 0.5rem;
     font-size: 1rem;
-    font-weight: 600;
+    font-weight: 400;
     text-decoration: none;
     background: #06c;
     color: #fff;
@@ -496,7 +497,7 @@ const sharedPaths = [
     padding: 0;
     color: var(--sl-color-white);
     font-family: var(--sl-font);
-    font-size: 1.25rem;
+    font-size: 1.1rem;
     font-weight: 700;
     line-height: 1.5;
     letter-spacing: 0;
@@ -583,6 +584,18 @@ const sharedPaths = [
     color: var(--sl-color-text-accent);
   }
 
+  .home-hero .home-hero__heading-link {
+    color: inherit;
+    text-decoration: inherit;
+  }
+
+  .home-hero .home-hero__heading-link:hover {
+    color: var(--sl-color-text-accent);
+    text-decoration: underline;
+    text-underline-offset: 4px;
+  }
+
+  .home-hero__heading-link:focus-visible,
   .home-hero__link:focus-visible,
   .home-hero__category-link:focus-visible {
     outline: 2px solid var(--sl-color-text-accent);
diff --git a/src/content/docs/ai/index.mdx b/src/content/docs/ai/index.mdx
index ae4ae3327..8901d9b71 100644
--- a/src/content/docs/ai/index.mdx
+++ b/src/content/docs/ai/index.mdx
@@ -1,8 +1,8 @@
 ---
-title: Install the integrations
+title: Install the AI tools
 description: Give your AI editor or coding agent current Adobe Commerce storefront documentation, drop-in APIs, and project conventions.
 sidebar:
-  label: Install the integrations
+  label: Install the AI tools
   order: 1
 ---
 
@@ -20,6 +20,7 @@ If your project is based on the Adobe Commerce boilerplate, set up all three int
 | [Boilerplate skills](/ai/boilerplate-skills/) | Storefront planning, coding, customization, and testing conventions |
 | [Dropins AI tools](/ai/dropins-ai-tools/) | Accurate drop-in slots, events, API functions, and design tokens validated against source |
 | [Wayfinder](/ai/wayfinder/) | Routing to the correct Adobe Commerce documentation source |
+| [LLM files](/ai/static-text-files/) | AI tools use these static, regenerated llms.txt files as context for the storefront documentation. |
 
 
 </TableWrapper>
@@ -76,16 +77,16 @@ Follow these steps in order.
 
 </Steps>
 
-## Use fallback documentation files
+## Use LLM documentation files
 
-If your AI editor or coding agent doesn't support tool servers or agent skills, add the following URL to your project instructions, or paste it into a chat instead:
+If your AI editor or coding agent doesn't support tool servers or agent skills, add the following LLM documentation URL to your project instructions, or paste it into a chat instead:
 
 ```text
 https://experienceleague.adobe.com/en/tools/commerce-storefront/llms.txt
 ```
 
-For editor-specific setup instructions and a verification prompt, see [Fallback documentation files](/ai/static-text-files/).
+For editor-specific setup instructions and a verification prompt, see [LLM files](/ai/static-text-files/).
 
 <Aside type="note">
-The `llms.txt` file offers guidance similar to the integrations above, but it isn't validated against your project's source, so it can become outdated. If you completed the installation steps, your agent already has more reliable, source-backed information — use `llms.txt` only as a fallback.
+The `llms.txt` file offers guidance similar to the integrations above, but it isn't validated against your project's source, so it can become outdated. If you completed the installation steps, your agent already has more reliable, source-backed information, use `llms.txt` only as a fallback.
 </Aside>
diff --git a/src/content/docs/ai/static-text-files.mdx b/src/content/docs/ai/static-text-files.mdx
index 9cb8ec0d1..97f9f4c02 100644
--- a/src/content/docs/ai/static-text-files.mdx
+++ b/src/content/docs/ai/static-text-files.mdx
@@ -1,5 +1,5 @@
 ---
-title: Fallback documentation files
+title: LLM files
 description: Use fallback llms.txt and topic files, regenerated at each publish, to give AI editors and coding agents current Adobe Commerce storefront documentation.
 tableOfContents:
   maxHeadingLevel: 2
@@ -9,10 +9,10 @@ import TableWrapper from '@components/TableWrapper.astro';
 import Link from '@components/Link.astro';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 
-If your AI editor cannot use MCP servers or agent skills, use these static documentation files as context for storefront APIs, drop-ins, and Edge Delivery Services.
+Static llms.txt files are regenerated on every build to give AI editors and coding agents current Adobe Commerce storefront documentation.
 
 <Aside type="note" title="Already using the boilerplate with a capable agent?">
-If your AI editor or coding agent supports MCP servers and agent skills, use [Install the integrations](/ai/#installation-steps) instead. That setup provides source-backed drop-in information, documentation routing, and storefront development conventions. Adding this page's `llms.txt` link is unnecessary.
+If your AI editor or coding agent supports MCP servers and agent skills, use [Install the AI tools](/ai/#installation-steps) instead. That setup provides source-backed drop-in information, documentation routing, and storefront development conventions. Adding this page's `llms.txt` link is unnecessary.
 </Aside>
 
 ## Available files
diff --git a/src/content/docs/get-started/index.mdx b/src/content/docs/get-started/index.mdx
index 3c0f6f275..2483bfb13 100644
--- a/src/content/docs/get-started/index.mdx
+++ b/src/content/docs/get-started/index.mdx
@@ -17,10 +17,6 @@ Within that setup, your job is to connect Commerce data to the page. You start f
 Drop-in components are included with an Adobe Commerce as a Cloud Service or Adobe Commerce Optimizer license. If you use Adobe Commerce on Cloud, you need a separate Adobe Commerce Optimizer license to use drop-ins. Read [Backend options](/get-started/backends/) to see which prerequisites apply to your backend, and [Licensing requirements](/licensing/) to confirm what your license covers.
 </Aside>
 
-## Plan your project
-
-Start with [Plan your storefront project](/setup/) to define your scope and migration strategy. If your team already has a plan, continue with the preview steps below.
-
 ## Get your first preview running
 
 You can start with [Create a storefront](/get-started/create-storefront/) if your team already has accounts and a chosen backend. If not, this path takes you from zero to a working local preview:
diff --git a/src/content/docs/setup/index.mdx b/src/content/docs/setup/index.mdx
deleted file mode 100644
index c81561fd6..000000000
--- a/src/content/docs/setup/index.mdx
+++ /dev/null
@@ -1,211 +0,0 @@
----
-title: Plan your storefront project
-description: Learn about Adobe Commerce on Edge Delivery Services project requirements, drop-in components, and storefront migration strategy.
----
-import Link from '@components/Link.astro';
-
-
-import Callouts from '@components/Callouts.astro';
-import Diagram from '@components/Diagram.astro';
-import Task from '@components/Task.astro';
-import Tasks from '@components/Tasks.astro';
-
-Before starting any Adobe Commerce on Edge Delivery Services project, you must conduct a setup phase to scope the project and ensure that there are no major roadblocks or risks.
-
-## Big picture
-
-In the [create your storefront](/get-started/) how-to, you learned how to quickly create a new project based on the <Link href={"https://github.com/hlxsites/aem-boilerplate-commerce"} text={"Commerce boilerplate template"} />. The boilerplate provides a starter storefront that uses a pre-configured Adobe Commerce environment.
-
-The next step is to plan, build, optimize, and launch a production-ready storefront connected to your own Adobe Commerce instance and storefront services. Here's an overview of the process:
-
-<Diagram caption="Storefront project planning and delivery process.">
-  ![Storefront project planning and delivery
-  process.](@images/implementation/implementation-overview-v2.svg)
-</Diagram>
-
-<Callouts>
-
-1. **Discovery**: Understand the requirements and goals of the project.
-1. **Setup**: Configure the project environment and tools.
-1. **Analytics**: Instrument the storefront to collect user interaction events.
-1. **SEO**: Optimize the storefront for search engines and marketing campaigns.
-1. **Drop-in components**: Develop and integrate drop-in components to enhance the storefront experience.
-1. **Launch**: Deploy the storefront to a production environment.
-
-</Callouts>
-
-## Project scope
-
-The discovery phase is important because Adobe Commerce is a highly customizable platform with a large third-party extension ecosystem. Migrating an Adobe Commerce storefront to Edge Delivery Services is similar to migrating to a headless storefront (like <Link href={"https://developer.adobe.com/commerce/pwa-studio"} text={"PWA Studio"} />).
-
-:::note[Important]
-The key requirement for a headless storefront implementation is that all required data is provided by APIs.
-:::
-
-Successfully building a storefront requires a well-defined plan and a phased approach. Here are some key steps to consider:
-
-<Tasks>
-
-<Task>
-
-### Phased launch
-
-Fast return on investment (ROI) and learnings:
-
-- Break down project scope into small milestones
-- Small milestones result in faster time-to-value (TTV), learnings, and higher quality
-- Define a rollout _and_ rollback strategy for each milestone (for example, split traffic)
-
-Adobe recommends the following launch phases:
-
-- Homepage and content pages with high-acquisition traffic that benefit from SEO improvement
-- Catalog pages (PDP and PLP) with high-conversion traffic that benefit from performance improvements
-- Checkout and account pages with high-retention traffic that benefit from personalization
-
-:::tip
-Instead of launching all features at once, start with a fresh Commerce project, launch with the minimum viable feature set, and add additional features as needed.
-
-Avoid introducing any potentially breaking changes to the existing project. For example, if you uninstall an extension required for an existing storefront when migrating to Edge Delivery Services, this could be a breaking change that prevents you from rolling back to the existing storefront if necessary.
-:::
-
-</Task>
-
-<Task>
-
-### Metrics
-
-Define what success should look like in each phase:
-
-- Define measurable business and technical metrics that are impacted by launch
-- Establish a baseline for each metric before launch
-- Create a realistic forecast of what to expect over time
-
-</Task>
-
-<Task>
-
-### Validation
-
-Validate the impact of changes:
-
-- Validate launch impact using your baseline and forecast
-- Prioritize fixing issues you and your team can resolve quickly
-- Rollback if issues are unclear or if a fix will take too long
-- Improve and test code before the next launch
-
-</Task>
-
-</Tasks>
-
-An iterative approach to launching your storefront will help you quickly identify and resolve issues, and improve the overall quality of your project. The following diagram illustrates the iterative approach:
-
-<Diagram caption="Iterative rollout process.">
-  ![Iterative rollout process.](@images/implementation/iterative-rollout-v1.svg)
-</Diagram>
-
-### Use cases and requirements
-
-Document your use cases and requirements and create a plan for how you will implement them. Adobe offers pre-built components that accelerate development (drop-in components).
-
-Drop-in components are reusable components that define the storefront shopping experience. They are framework agnostic and can be used in any context (Edge Delivery Services, AEM, Luma). However, this documentation focuses on the use of drop-in components in Edge Delivery Services projects using the <Link href={"https://github.com/hlxsites/aem-boilerplate-commerce"} text={"boilerplate template"} />. The drop-in component development roadmap is synchronized with Adobe Commerce APIs, so new API features become available in drop-in components as Adobe ships them. See [Boilerplate updates](/boilerplate/updates/) for how to pull new drop-in versions into your project.
-
-:::note
-See the [drop-in components overview](/dropins/all/introduction/) for a list of all available drop-in components.
-:::
-
-If you see gaps in what the drop-in components support, Adobe can help with a plan to achieve your scenarios. For example:
-
-- Identify if drop-in components can solve your use cases and requirements
-- Identify what use cases are already supported, what is a gap, and what needs to be implemented differently from what is available out-of-the-box
-- Reach out to the Adobe team early to share your use cases and get recommendations on how to fulfill them: <Link href={"mailto:commerce-storefront-compatibility@adobe.com"} text={"commerce-storefront-compatibility@adobe.com"} />
-
-The Product Discovery drop-in component covers both the quick search popover and the product listing page (PLP). It installs like any other drop-in component, using scoped [`SearchResults`](/dropins/product-discovery/containers/search-results/) containers: one scoped to a popover for quick search, and one for the full PLP. Because you own the containers directly, you have full control over styling, layout, and behavior for both experiences.
-
-See the [Product Discovery drop-in](/dropins/product-discovery/) for its containers, functions, and events.
-
-### Extensions
-
-Before starting the project, use the following list to create an inventory of the Adobe Commerce extensions that are actively being used. This will help you understand which extensions can be replaced by out-of-the-box Adobe Commerce functionality.
-
-- What extensions are currently in use?
-
-- What type of data do the extensions provide (for example, reviews)?
-
-- Is the data required on the frontend?
-- How do the extensions expose the data (for example, GraphQL, REST API)?
-
-- Do the extensions expose an API to access data (for example, a product labels module from <Link href={"https://commercemarketplace.adobe.com/"} text={"Adobe Commerce Marketplace"} />)? If not, create an action item to expose the required data through an API. Options include:
-
-  - Customize the Adobe Commerce Catalog Service exporter to export additional custom data to Catalog Service
-  - Create a custom Adobe Commerce GraphQL query
-  - Use <Link href={"https://developer.adobe.com/graphql-mesh-gateway/"} text={"API Mesh for Adobe Developer App Builder"} />
-
-- Are any of the extensions for delivery options (for example, shipping/BOPIS), payments, or tax providers? If you use third-party solutions, clarify if they expose APIs on the frontend and if they provide their own set of drop-in components for the frontend integration.
-
-## Existing storefronts
-
-There are a couple of options for modernizing your existing storefront with Edge Delivery Services:
-
-- **Progressive implementation**: Rebuild selected parts of the commerce funnel on Edge Delivery Services and reuse the rest from your existing storefront.
-- **Full implementation**: Rebuild your entire storefront on Edge Delivery Services and retire your existing storefront.
-
-A progressive implementation enables you to unlock business value with Edge Delivery Services sooner, minimizing the risks associated with migration. You can start by implementing the home page only and reusing the rest of your existing storefront. The next step could be implementing catalog with product listing, search, and product details and reusing cart, checkout, and account from your existing storefront.
-
-This approach comes with the cost of maintaining two storefronts in parallel, so before you choose, assess which approach is right for you. These are the key factors to consider:
-
-- **Business metrics to improve**:
-
-  - What areas of your existing storefront drive business performance?
-  - What are the challenges based on the site analytics that you see?
-
-- **Level of storefront customization**:
-
-  - How many experiences are built with custom code on your storefront?
-  - Do these experiences rely on custom business logic?
-
-- **Third-party extensions**:
-
-  - How many third-party extensions are you using on your existing storefront?
-  - Do you need to connect to third-party services?
-
-- **B2B**:
-  - Are there any Adobe Commerce B2B modules enabled on your existing storefront?
-
-Adobe recommends the progressive implementation if any of the following are true:
-
-- The main business metrics are brand visibility in search engines, customer acquisition cost, and customer engagement.
-- The existing storefront is heavily customized in the areas of checkout and user account.
-- There are many third-party integrations in the existing storefront that affect transactional flow.
-- The existing storefront supports B2B use cases with Adobe Commerce modules.
-
-The full implementation is a better option if any of the following are true:
-
-- Your business objectives include improving customer conversion and re-engagement.
-- The current checkout flow only relies on a few third-party integrations (for example, payments, shipping, taxes).
-- No Adobe Commerce B2B modules are enabled on the existing storefront.
-
-| Criteria                        | Progressive Implementation                                                                                                | Full Implementation                                                                                |
-| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
-| **Description**                 | Rebuild selected parts of the commerce funnel on Edge Delivery Services and reuse the rest from your existing storefront. | Rebuild your entire storefront on Edge Delivery Services and retire your existing storefront.      |
-| **Business Metrics to Improve** | Brand visibility in search engines, customer acquisition cost, customer engagement.                                       | Customer conversion, customer re-engagement.                                                       |
-| **Level of Customization**      | Heavily customized in areas like checkout and user account.                                                               | Minimal customization, relies on a few third-party integrations (e.g., payments, shipping, taxes). |
-| **Third-Party Integrations**    | Many third-party integrations affecting transactional flow.                                                               | Few third-party integrations.                                                                      |
-| **B2B Modules**                 | Supports B2B use cases with Adobe Commerce modules.                                                                       | No Adobe Commerce B2B modules enabled.                                                             |
-| **Project Scope**               | Identify use cases for new and existing storefronts (e.g., catalog, product detail, cart, checkout, customer account).    | Verify use cases are available through Adobe Commerce GraphQL APIs.                                |
-| **Third-Party Extensions**      | Identify necessary extensions and their reliance on third-party services.                                                 | Identify necessary extensions and their reliance on third-party services.                          |
-| **Storefront Bridge Options**   | Plan to connect existing storefront with the new one (e.g., using [Luma Bridge](/setup/discovery/luma-bridge/)).          | Not applicable.                                                                                    |
-
-### Progressive implementation
-
-For the progressive implementation, you'll need to look into the following:
-
-- **Project scope**: Identify which use cases the new storefront will handle and which ones the existing storefront will continue to manage, such as catalog, product detail, cart, checkout, and customer account.
-- **Third-party extensions**: Identify the list of extensions you will need on your new storefront and determine if they rely on integrating third-party services.
-- **Storefront bridge options**: Plan to connect the existing storefront with the new one. If you are using Adobe Commerce native storefront with Luma, you can use the [Luma Bridge](/setup/discovery/luma-bridge/).
-
-### Full implementation
-
-For the full implementation, the list of considerations is similar to the progressive implementation:
-
-- **Project scope**: Identify which use cases the new storefront will handle and verify that they are available through Adobe Commerce GraphQL APIs.
-- **Third-party extensions**: Identify the list of extensions you will need on your new storefront and determine if they rely on integrating third-party services.