docs updated

Author: yaroslavGoncharuk

README.md

@@ -8,9 +8,9 @@ This repository is responsible for Catalog Storefront Application
 - store data in an efficient way in own database(s)
 
 ### Service repository Dependencies 
-- https://github.com/magento/saas-export/ (Provides API to Export entities from Magento to any subscribed consumer)
+- https://github.com/magento/commerce-data-export (Provides API to Export entities from Magento to any subscribed consumer)
 
-### 3rd-party dependecnies (composer packages)
+### 3rd-party dependencies (composer packages)
 - google/protobuf
 - grpc/grpc
 - spiral/php-grpc
@@ -26,7 +26,7 @@ This project is licensed under the OSL-3.0 License. See [LICENSE](./LICENSE.md)
 * [Project Overview:](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/home/Home.md)
   * [Scopes (Milestones)](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/home/Milestones.md)
 * [Onboarding:](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/onboarding/Project-Onboarding.md)
-   * [Repositories](https://github.com/magento/storefront-cloud-project/blob/develop/production/.magento.env.yaml)
+   * [Repositories](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/onboarding/Repositories.md)
    * [Services Responsibilities](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/onboarding/Services-responsibilities.md)
    * [Time Off Tracking List](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/onboarding/Time-Off-Tracking.md)
 * Development:
@@ -42,14 +42,13 @@ This project is licensed under the OSL-3.0 License. See [LICENSE](./LICENSE.md)
    * [Catalog Storefront Service Overview](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/designDocuments/Catalog-Storefront-Service.md)
    * [Plan to Introduce Back Office APIs](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/designDocuments/Plan-to-introduce-back-office-APIs.md)
    * [Product Variants and Type Specific Options](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/designDocuments/Product-variants-and-type-specific-options.md)
-   * [Catalog Media Tech Vision](https://github.com/magento/architecture/blob/develop/master/design-documents/media/catalog-images.md)
-   * [Configuration Propagation](https://github.com/magento/architecture/blob/develop/master/design-documents/storefront/configuraiton-propagation.md)
+   * [Catalog Media Tech Vision](https://github.com/magento/architecture/blob/master/design-documents/media/catalog-images.md)
+   * [Configuration Propagation](https://github.com/magento/architecture/blob/master/design-documents/storefront/configuraiton-propagation.md)
    * [Configurable Product Variants](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/designDocuments/Configurable-products-option-variants.md)
    * [Product Variants Services](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/designDocuments/Product-Variants-services.md)
 * QA:
    * [Storefront Testing](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/qa/Storefront-Testing.md)
 * Demo:
    * [How To Demo "Add Product with Options to Cart"](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/demo/How-To-Demo-"Add-Product-with-Options-to-Cart".md)
 * Contacts:
-   * [Slack](https://magentocommeng.slack.com/archives/G0157R0PF3J)
-
+   * [Slack](https://magentocommeng.slack.com/archives/G0157R0PF3J)

dev/docs/contribution/How-To-Contribute-To-Project.md

@@ -2,21 +2,21 @@ Two main points that is underlie the following instruction:
 1) magento org is a read-only replica of new primary fork visible only to internal teams
 2) sync from that invisible primary fork to magento org happens in eventually consistent way
 
-The example would be given for complex task that has a code changes for catalog-storefront and saas-export repos but whatever repo of Storefront project you need to contribute the flow will look same. 
+The example would be given for complex task that has a code changes for catalog-storefront and commerce-data-export repos but whatever repo of Storefront project you need to contribute the flow will look same. 
 
 ## Step #1
-Make a fork of catalog-storefront and saas-export repos from magento org to your own organisation. 
+Make a fork of catalog-storefront and commerce-data-export repos from magento org to your own organisation. 
 ## Step #2 [optional]
 If you are working together with someone else in a team, please create your story-branch from magento/catalog-storefront/develop branch and push it to your fork.
 For example, you need auto-generated files from proto-scheme, then someone from internal magento team would be able to create a PR to your story-branch.
 ## Step #3
-When you ready, create a PR from your fork to magento/catalog-storefront and magento/saas-export repos
+When you ready, create a PR from your fork to magento/catalog-storefront and magento/commerce-data-export repos
 
 *Note:* don't forget to link the PRs by providing this information under the _Related Pull Requests_ section
 *Examples:*
 ```
 ### Related Pull Requests
-https://github.com/magento/saas-export/pull/9999999
+https://github.com/magento/commerce-data-export/pull/9999999
 <!-- related pull request placeholder -->
 ```
 ## Step #4

dev/docs/designDocuments/Configurable-products-option-variants.md

@@ -24,7 +24,7 @@ System has 3 simple products which reflects 3 combinations of those options (blu
 2. simple "Red XL"  {id: 2, storeViewId: ["default", "storeview2"], color: "red",   size: "xl"}
 3. simple "Red L"   {id: 3, storeViewId: ["default", "storeview2"], color: "red",   size: "l"}
 
-## Saas-export part
+## Commerce Data Export
 in `et_schema.xml` there's the following structure for ProductVariant:
 ```
     <record name="ProductVariant">

dev/docs/home/Home.md

@@ -72,7 +72,7 @@ The next data should be exposed in Magento:
 * Category system attributes.
 * Product attributes metadata.
 
-[Optional] By introducing extractor API for Magento we have enough control to deduplicate messages even before they were emitted. And do not emit messages if Magento did not really change the data. (Example1: the product has been saved but no properties were changed, such an event should be ignored; Example 2: Magento should not issue a new event if the product changed inventory records only.). This option is available for the Magento data exporter only. See implementation example https://github.com/magento/saas-export/
+[Optional] By introducing extractor API for Magento we have enough control to deduplicate messages even before they were emitted. And do not emit messages if Magento did not really change the data. (Example1: the product has been saved but no properties were changed, such an event should be ignored; Example 2: Magento should not issue a new event if the product changed inventory records only.). This option is available for the Magento data exporter only. See implementation example https://github.com/magento/commerce-data-export
 
 In the general case, the messages filtration should happen at the import step. 
 

dev/docs/home/Milestones.md

@@ -0,0 +1,10 @@
+## Project Repositories 
+ 
+### Magento Community Edition with Storefront APP
+APP | Repo Name | Repo URL | Repo Branch |
+| -------- |------------ | ------------- | ------------- |
+| Storefront | Catalog Storefront | https://github.com/magento/catalog-storefront | develop
+| Storefront | Commerce Data Export  | https://github.com/magento/commerce-data-export | main
+| Storefront | Storefront Message Broker | https://github.com/magento/storefront-message-broker | main
+|  |  |  | 
+| Magento | Magento CE | https://github.com/magento/magento2 | develop-storefront

dev/docs/onboarding/Repositories.md

@@ -22,7 +22,7 @@ This simplified diagram highlights the main "parts" of Storefront Application (G
 
 ## Responsibilities
 ### Export API. 
-Source: https://github.com/magento/saas-export/tree/develop-storefront   
+Source: https://github.com/magento/commerce-data-export/tree/main   
 **Provide API to Export entities from Magento to any subscribed consumer**   
 Implement 2 different strategies:   
 - Push strategy (used by PRex): push changes to remote end-point called Injection Service
@@ -31,7 +31,7 @@ Implement 2 different strategies:
 By fact contract of Export API is described in et_schema.xml
 
 ### Message Broker. 
-Source: https://github.com/magento/catalog-storefront/tree/develop/app/code/Magento/CatalogMessageBroker   
+Source: https://github.com/magento/storefront-message-broker   
 **Connect Backoffice and Storefront application.**   
 
 Responsibilities:
@@ -47,24 +47,6 @@ Responsibilities:
 - provide Read API for specific attributes, scope
 - store data in an efficient way in own databases
 
-## Modules that will be eliminated (transition period)
-
-### Extension for Backoffice dependent on saas-export repo
-Source: [CatalogExport](https://github.com/magento/catalog-storefront/tree/develop/app/code/Magento/CatalogExport), [CatalogExportAPI](https://github.com/magento/catalog-storefront/tree/develop/app/code/Magento/CatalogExportAPI)   
-Will be eliminated in https://github.com/magento/catalog-storefront/issues/185
-
-
-
-### Old Export API
-Source: [CatalogExtractor](https://github.com/magento/catalog-storefront/tree/develop/app/code/Magento/CatalogExtractor), any "*Extractor" module   
-**The previous implementation of Export API. Will be migrated to new Export API**   
-Will be eliminated after migration all existing Data Providers to Export API
-
-### Connector 
-Source: https://github.com/magento/catalog-storefront/tree/develop/app/code/Magento/CatalogStorefrontConnector   
-Responsibilities:
-- expose events "storefront.catalog.category.update", "storefront.catalog.product.update" which publish product ids on different events: product saved, category assigned to product, store created...
-
 ## Legacy approach (historical notes)
 
 ### GQL Extension for Backoffice 

dev/docs/onboarding/Services-responsibilities.md

@@ -14,12 +14,12 @@ Here is a “Code Review checklist" for the Storefront Application project that
  - Export API (et_schema.xml) and SF API schemas (proto schema) are reflected in the codebase
   - prerequisite: story branch created with all needed generated classes according to proposes schema-changes
   - DTO classes does not contain any manual changes (Magento\CatalogExportApi\*, Magento\CatalogStorefrontApi\*)
-- Class usage: magento/catalog-storefront repo don't use directly classes from magento/saas-export repo and vise-verse
+- Class usage: magento/catalog-storefront repo don't use directly classes from magento/commerce-data-export repo and vise-verse
   - Check composer.json dependencies
   - note: Can be automated by static test
 - Legacy code is deleted
   - Any Data Providers present in Connector part  (Magento\CatalogStorefrontConnector, Magento\*Extractor modules)
-  - And Data Providers from Export API (magento/saas-export repo) that is not relevant anymore
+  - And Data Providers from Export API (magento/commerce-data-export repo) that is not relevant anymore
   - Any DTO for Export API/SF API which does not reflect current schema: et_schema, proto schema
   - Any “mapper” on Message Broker (between Export API and SF API)
     - if mapper still needed, verify fields used in mapping, remove not relevant fields

dev/docs/projectAgreements/Code-Review-checklist.md

@@ -4,7 +4,7 @@ To run tests for the Storefront Application project we use [GitHub App](https://
 
 #### Flow:
 - add a comment in PR, e.g. `@magento run all tests` (see [full list](https://github.com/magento/catalog-storefront/blob/develop/dev/docs/development/Running-tests-on-PR.md))
- - Currently, it's configured only for next repos: https://github.com/magento/catalog-storefront, https://github.com/magento/saas-export
+ - Currently, it's configured only for next repos: https://github.com/magento/catalog-storefront, https://github.com/magento/commerce-data-export
 GitHub App will ask “Magento Test API” to run tests in PR with [configuration](https://github.com/magento-commerce/engcom-githubapp-pr-mts-builds/blob/master/app/repo-config.js#L652) for SF project
 - Test results will be provided in PR