diff --git a/docs/content_management/taxonomy/taxonomy.md b/docs/content_management/taxonomy/taxonomy.md index afee28e616..f01ddb75df 100644 --- a/docs/content_management/taxonomy/taxonomy.md +++ b/docs/content_management/taxonomy/taxonomy.md @@ -116,7 +116,7 @@ php bin/console ibexa:taxonomy:remove-orphaned-content tags --force ## Taxonomy suggestions -Once the feature is [enabled](#enable-taxonomy-suggestions), with taxonomy suggestions, editors can pick from suggestions generated by an AI service based on selected fields like the product's or content item's name and description instead of having to manually browse through taxonomy trees and selecting [product categories]([[= user_doc =]]/pim/work_with_product_categories/#assign-product-categories-by-editing-product-details) or [tags]([[= user_doc =]]/content_management/create_edit_content_items/#add-taxonomy-entries). +Once the feature is [enabled](#enable-taxonomy-suggestions), with taxonomy suggestions, editors can pick from suggestions generated by an AI service based on selected fields like the product's or content item's name and description instead of having to manually browse through taxonomy trees and selecting [product categories]([[= user_doc =]]/product_catalog/work_with_product_categories/#assign-product-categories-by-editing-product-details) or [tags]([[= user_doc =]]/content_management/create_edit_content_items/#add-taxonomy-entries). Taxonomy suggestions build on existing [AI Actions](ai_actions_guide.md) functionality. The [`TaxonomyEmbeddingFieldProviderInterface`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Taxonomy-Embedding-TaxonomyEmbeddingFieldProviderInterface.html) diff --git a/docs/discounts/discounts_api.md b/docs/discounts/discounts_api.md index 80cdacf1b9..743737b70c 100644 --- a/docs/discounts/discounts_api.md +++ b/docs/discounts/discounts_api.md @@ -70,7 +70,7 @@ With conditions you can narrow down the scenarios in which the discount applies. | Condition
(identifier) | Applies to | Description | Required expression values | |---|---|---|---| -| `IsInCategory`
(`is_in_category`) | Cart, Catalog | Checks if the product belongs to specified [product categories]([[= user_doc =]]/pim/work_with_product_categories/) | `categories` | +| `IsInCategory`
(`is_in_category`) | Cart, Catalog | Checks if the product belongs to specified [product categories]([[= user_doc =]]/product_catalog/work_with_product_categories/) | `categories` | | `IsInCurrency`
(`is_in_currency`) | Cart, Catalog | Checks if the product has price in the specified currency | `currency_code` | | `IsInRegions`
(`is_in_regions`) | Cart, Catalog | Checks if the customer is making the purchase in one of the specified regions | `regions` | | `IsProductInArray`
(`is_product_in_array`) | Cart, Catalog | Checks if the product belongs to the group of selected products | `product_codes` | diff --git a/docs/product_catalog/enable_purchasing_products.md b/docs/product_catalog/enable_purchasing_products.md index e5f96c712a..ed73b78faf 100644 --- a/docs/product_catalog/enable_purchasing_products.md +++ b/docs/product_catalog/enable_purchasing_products.md @@ -13,9 +13,9 @@ To enable adding product to cart and purchasing from the catalog, the following !!! note "Configuring products in the UI" - After you configure the region, currency and VAT rates for regions in settings, the store manager must set up the remaining parameters in the UI, such as, [VAT rates per product type]([[= user_doc =]]/pim/create_product_types/#vat), descriptions, attributes, assets, [prices]([[= user_doc =]]/pim/manage_prices/), and [availability]([[= user_doc =]]/pim/manage_availability_and_stock/) per product. + After you configure the region, currency and VAT rates for regions in settings, the store manager must set up the remaining parameters in the UI, such as, [VAT rates per product type]([[= user_doc =]]/product_catalog/create_product_types/#vat), descriptions, attributes, assets, [prices]([[= user_doc =]]/product_catalog/manage_prices/), and [availability]([[= user_doc =]]/product_catalog/manage_availability_and_stock/) per product. - For more information, see [User Documentation]([[= user_doc =]]/pim/products/#product-completeness). + For more information, see [User Documentation]([[= user_doc =]]/product_catalog/products/#product-completeness). ## Region and currency @@ -110,6 +110,6 @@ ibexa: ``` You can then assign VAT rates that apply to every product type in each of the supported regions. -To do it, in the back office, [open the product type for editing]([[= user_doc =]]/pim/create_product_types/#vat), and navigate to the **VAT rates** area. +To do it, in the back office, [open the product type for editing]([[= user_doc =]]/product_catalog/create_product_types/#vat), and navigate to the **VAT rates** area. -![Assigning VAT rates to a product type](catalog_vat_rates.png "Assigning VAT rates to a product type") \ No newline at end of file +![Assigning VAT rates to a product type](catalog_vat_rates.png "Assigning VAT rates to a product type") diff --git a/docs/product_catalog/product_catalog_guide.md b/docs/product_catalog/product_catalog_guide.md index 0fa004ab75..7c33fe0014 100644 --- a/docs/product_catalog/product_catalog_guide.md +++ b/docs/product_catalog/product_catalog_guide.md @@ -43,7 +43,7 @@ You can also configure selected product attributes to be used as a basis for var ![Product attributes](img/product_attributes.png) -For more information, see [Product attributes](products.md#product-attributes) and [Work with product attributes]([[= user_doc =]]/pim/work_with_product_attributes/) +For more information, see [Product attributes](products.md#product-attributes) and [Work with product attributes]([[= user_doc =]]/product_catalog/work_with_product_attributes/) ### Product variants @@ -64,7 +64,7 @@ Created collection is automatically assigned to the variant or variants that hav ### Availability Product availability defines whether a product is available in the catalog. -For each product you can [set availability]([[= user_doc =]]/pim/manage_availability_and_stock/) per variant or per base product. +For each product you can [set availability]([[= user_doc =]]/product_catalog/manage_availability_and_stock/) per variant or per base product. When a product is available, it can have numerical stock defined, that you can set. The stock can also be set to infinite, for example, for digital, downloadable products. A product can only be ordered when it has either positive stock, or stock set to infinite. @@ -76,7 +76,7 @@ Each product can belong to multiple categories of, depending on user’s choice, Category can also be assigned to multiple products. One of the reasons for applying product categories is assisting users in searching for products. -Before you can assign categories to products, you need to [enable product categories]([[= user_doc =]]/pim/work_with_product_categories/#enable-product-categories). +Before you can assign categories to products, you need to [enable product categories]([[= user_doc =]]/product_catalog/work_with_product_categories/#enable-product-categories). ![Product categories](img/product_categories.png) @@ -89,7 +89,7 @@ Product types in [[= product_name =]] can be either virtual or physical: This product type property can affect the checkout process. A cart of only virtual products skips the [shipping step](shipping_management.md) during checkout. -To learn more about working with virtual products, see [Virtual products]([[= user_doc =]]/pim/create_virtual_product/) in the User Documentation. +To learn more about working with virtual products, see [Virtual products]([[= user_doc =]]/product_catalog/create_virtual_product/) in the User Documentation. ### Currencies @@ -183,7 +183,7 @@ This versatility allows for a consistent and user-friendly purchasing workflow r ##### Pricing, stock and availability -A product can only be ordered when it has defined [availability]([[= user_doc =]]/pim/manage_availability_and_stock/), stock and [pricing information]([[= user_doc =]]/pim/manage_prices/). +A product can only be ordered when it has defined [availability]([[= user_doc =]]/product_catalog/manage_availability_and_stock/), stock and [pricing information]([[= user_doc =]]/product_catalog/manage_prices/). By default, such information is held in the [[= product_name =]]'s local database. In your specific scenario, you can implement the support for availability and pricing information coming from an external source as well, by using a price/availability matching strategy that is an extension point exposed in the Product catalog module. diff --git a/docs/templating/twig_function_reference/product_twig_functions.md b/docs/templating/twig_function_reference/product_twig_functions.md index ffaca5e59e..69b7fb9873 100644 --- a/docs/templating/twig_function_reference/product_twig_functions.md +++ b/docs/templating/twig_function_reference/product_twig_functions.md @@ -137,7 +137,7 @@ The `ibexa_is_pim_local` is a helper Twig function that enables changing the beh ### `ibexa_product_catalog_group_attributes` -The `ibexa_product_catalog_group_attributes` filter groups product attributes based on the [attribute group]([[= user_doc =]]/pim/work_with_product_attributes/#create-attribute-groups) they belong to. +The `ibexa_product_catalog_group_attributes` filter groups product attributes based on the [attribute group]([[= user_doc =]]/product_catalog/work_with_product_attributes/#create-attribute-groups) they belong to. #### Example