fix(docs): extract Medusa integration section and update UI paths in 1.6.0 release notes

Made-with: Cursor

Author: tomaszpacior

apps/docs/blog/releases/o2s/1.6.0.md

@@ -27,12 +27,32 @@ What's included:
 - New blocks covering the full purchase journey: from cart management through checkout steps to order confirmation.
 - "Add to Cart" buttons across product blocks (Product List, Product Details, Recommended Products) with promo code support.
 - Multi-step checkout with address, company data, and payment forms — including validation and error handling.
-- [Medusa.js integration](../../../docs/integrations/commerce/medusa-js/overview) for carts, checkout, customers, and payments — so you can connect to a real commerce backend out of the box.
 
 :::tip
 For setup instructions and data model details, see the new documentation for [Carts](../../../docs/main-components/harmonization-app/normalized-data-model/core-model-carts), [Checkout](../../../docs/main-components/harmonization-app/normalized-data-model/core-model-checkout), and [Payments](../../../docs/main-components/harmonization-app/normalized-data-model/core-model-payments).
 :::
 
+### Medusa.js commerce integration
+
+To power the cart and checkout features above, we've added a full [Medusa.js integration](../../../docs/integrations/commerce/medusa-js/overview) — the first commerce backend supported in O2S. This means you can connect to a real store out of the box, without building your own API layer.
+
+The integration covers six O2S modules:
+
+| Module    | What it enables |
+| --------- | --------------- |
+| Carts     | Cart creation, line items, addresses, shipping methods, promo codes |
+| Checkout  | Multi-step checkout flow with order placement |
+| Customers | Saved address management for authenticated users |
+| Orders    | Order history and details |
+| Payments  | Payment session creation and provider selection |
+| Products  | Product catalog browsing with variants and pricing |
+
+It supports both guest and authenticated checkout, multi-currency pricing, and uses Medusa's Store API with SSO-based authentication. For extended use cases like asset tracking and service subscriptions, there's also an optional [Medusa plugin](https://github.com/o2sdev/medusa-plugin-assets-services) that adds custom entities.
+
+:::tip
+See the full [Medusa.js integration docs](../../../docs/integrations/commerce/medusa-js/overview) for setup instructions, and the [Cart & Checkout guide](../../../docs/integrations/commerce/medusa-js/cart-checkout) for details on the checkout flow.
+:::
+
 ### Interactive CLI wizard
 
 Setting up a new O2S project is now much easier. Instead of cloning a repository and manually configuring packages, you can use the new interactive wizard that walks you through the entire process:
@@ -55,17 +75,17 @@ For all available CLI options and usage examples, see the [Installation guide](.
 
 ### Domain-based block and UI organization
 
-Blocks and UI components are now organized by business domain. For example, billing-related blocks live under `packages/blocks/billing/`, support blocks under `packages/blocks/support/`, and checkout blocks under `packages/blocks/checkout/`. The same applies to UI components, which are now grouped into categories like `Cart`, `Checkout`, `cards`, `data`, `forms`, and others.
+Blocks and UI components are now organized by business domain. For example, billing-related blocks live under `packages/blocks/billing/`, support blocks under `packages/blocks/support/`, and checkout blocks under `packages/blocks/checkout/`. The same applies to UI components, which are now grouped into categories like `Cart`, `Checkout`, `Cards`, `Data`, `Forms`, `Products`, and others.
 
 This makes it easier to find what you're looking for when working with the codebase, and scales better as the number of blocks grows.
 
 :::info
 **Breaking change**: UI import paths have changed. The new format is `@o2s/ui/components/<group>/<Component>` — for example:
 
 ```typescript
-import { ProductCard } from '@o2s/ui/components/cards/ProductCard';
-import { DataGrid } from '@o2s/ui/components/data/DataGrid';
-import { Carousel } from '@o2s/ui/components/media/Carousel';
+import { ProductCard } from '@o2s/ui/components/Cards/ProductCard';
+import { DataGrid } from '@o2s/ui/components/Data/DataGrid';
+import { Carousel } from '@o2s/ui/components/Media/Carousel';
 ```
 :::
 
@@ -137,9 +157,9 @@ Several improvements make day-to-day work with O2S smoother:
 A set of new UI components was added to support the cart and checkout flows:
 
 - [`StepIndicator`](https://storybook-o2s.openselfservice.com/?path=/docs/components-checkout-stepindicator--docs) — visual step progress for multi-step checkout.
-- [`RadioTile`](https://storybook-o2s.openselfservice.com/?path=/docs/components-radiotilegroup--docs) — selectable option tiles (e.g., for shipping or payment methods).
+- [`RadioTile`](https://storybook-o2s.openselfservice.com/?path=/docs/components-forms-radiotilegroup--docs) — selectable option tiles (e.g., for shipping or payment methods).
 - [`CartItem`](https://storybook-o2s.openselfservice.com/?path=/docs/components-cart-cartitem--docs), [`CartSummary`](https://storybook-o2s.openselfservice.com/?path=/docs/components-cart-cartsummary--docs), [`CartPromoCode`](https://storybook-o2s.openselfservice.com/?path=/docs/components-cart-cartpromocode--docs) — cart display and promo code input.
-- [`AddressFields`](https://storybook-o2s.openselfservice.com/?path=/docs/components-checkout-addressfields--docs), [`QuantityInput`](https://storybook-o2s.openselfservice.com/?path=/docs/components-quantityinput--docs) — form building blocks for checkout pages.
+- [`AddressFields`](https://storybook-o2s.openselfservice.com/?path=/docs/components-checkout-addressfields--docs), [`QuantityInput`](https://storybook-o2s.openselfservice.com/?path=/docs/components-forms-quantityinput--docs) — form building blocks for checkout pages.
 
 ### Storybook and documentation