IBX-8674: Improve product completeness and attribute definitions (#2617)

* Make product completeness and attribute definitions more precise
---------

Co-authored-by: Adrien Dupuis <[email protected]>

Author: dabrt

Diff for: docs/pim/pim_guide.md

@@ -36,10 +36,13 @@ Product specifications rely on product attributes. Available attributes are defi
 Each product has its own, specific attributes. You can describe a product in technical terms, define its physical characteristics such as size, color, or shape, or functional characteristics (for example, for a laptop it could be the operating system, amount of memory, or available ports).
 
 Product attributes can belong to one of existing types (for example, numbers, selection, or checkout), but you can also [add custom attribute types](create_custom_attribute_type.md).
-You can configure selected product attributes to be used as a basis for variants.
+Attributes are used as criteria for filtering and searching for products.
+You can also configure selected product attributes to be used as a basis for variants.
 
 ![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/)
+
 ### Product variants
 
 One product can have multiple versions, for example, there can be a t-shirt in different colors.
@@ -108,6 +111,10 @@ You can check how complete the configuration is in the product’s view.
 
 When you create or edit a product, under the product name, you can see visual indication of what part of product information (tasks) you have completed, and what part is still missing.
 
+Product completeness doesn't impact product availability or visibility on the storefront.
+It is intended to help you ensure that product data is properly populated.
+As long as your product meets [basic requirements](enable_purchasing_products.md), it can be published and made available for purchase regardless of its completeness score.
+
 ### Catalogs
 
 With catalogs you can create product lists for special purposes, for example, for B2B and B2C uses, for retailers and distributors, or for different regions.

Diff for: docs/pim/products.md

@@ -47,6 +47,13 @@ An example of an attribute group can be dimensions (length, width, height).
 
 You can assign both whole attribute groups or individual attributes to a product type.
 
+!!! note "Attribute translations"
+
+    Product attributes are not translatable.
+    Unlike content fields, product attribute values cannot differ between languages.
+
+    For the information that is intended to be displayed, consider using [TextLine](textlinefield.md) fields for short text, [RichText](richtextfield.md) fields for longer text that may require formatting, and product attributes for precise product properties or specifications.
+
 ## Product variants
 
 Product variants represent different versions of a product, for example, clothes in different colors, or laptops with different amounts of RAM.
@@ -87,4 +94,3 @@ The stock can also be set to infinite (for example, in case of digital products)
     A product can be available, but have zero stock.
 
     A product can only be ordered when it has either positive stock, or stock set to infinite.
-

Diff for: docs/release_notes/ibexa_dxp_v4.2.md

@@ -84,6 +84,12 @@ You can use it to get a quick overview of missing parts in the product configura
 
 ![Product completeness tab](4.2_product_completeness.png)
 
+!!! note "No impact on availability"
+
+    Product completeness helps ensure that product data is complete.
+    It does not impact product availability or visibility on the storefront.
+    As long as a product meets availability and stock requirements, it can be published and made available for purchase regardless of its completeness score.
+
 ### Product categories
 
 With product categories, you can organize products that populate the Product Catalog.