fix: links for not transfered repos

docs/guide/README.md

@@ -38,7 +38,7 @@ The API connector works in two phases:
 
 VueStorefront works seamlessly with your backend platform while two integration phases are managed as above.
 
-Some of the most popular backend platforms already have their integrations ([Magento 2](https://github.com/vuestorefront/mage2vuestorefront), [Magento 1](https://github.com/vuestorefront/magento1-vsbridge), [CoreShop](https://github.com/vuestorefront/coreshop-vsbridge), [BigCommerce](https://github.com/vuestorefront/bigcommerce2vuestorefront), [WooCommerce](https://github.com/vuestorefront/woocommerce2vuestorefront)), but you can easily make your own with the [integration boilerplate](https://github.com/vuestorefront/vue-storefront-integration-boilerplate).
+Some of the most popular backend platforms already have their integrations ([Magento 2](https://github.com/vuestorefront/mage2vuestorefront), [Magento 1](https://github.com/divanteLtd/magento1-vsbridge), [CoreShop](https://github.com/divanteLtd/coreshop-vsbridge), [BigCommerce](https://github.com/divanteLtd/bigcommerce2vuestorefront), [WooCommerce](https://github.com/divanteLtd/woocommerce2vuestorefront)), but you can easily make your own with the [integration boilerplate](https://github.com/divanteLtd/vue-storefront-integration-boilerplate).
 
 The blue parts on the diagram are responsible for offline cache and will be explained later in the article.
 

docs/guide/basics/ssr-cache.md

@@ -88,7 +88,7 @@ export VS_INVALIDATE_CACHE=1
 ```
 
 :::warning Caution !
-All the official Vue Storefront data indexers including [magento1-vsbridge-indexer](https://github.com/vuestorefront/magento1-vsbridge-indexer), [magento2-vsbridge-indexer](https://github.com/vuestorefront/magento2-vsbridge-indexer) and [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) support the cache invalidation. If the cache is enabled in both API and Vue Storefront frontend app, please make sure you are properly using the `config.server.invalidateCacheForwardUrl` config variable as the indexers can send the cache invalidate request only to one URL (frontend or backend) and it should be forwarded. Please check the default forwarding URLs in the `default.json` and adjust the `key` parameter to the value of `server.invalidateCacheKey`.
+All the official Vue Storefront data indexers including [magento1-vsbridge-indexer](https://github.com/divanteLtd/magento1-vsbridge-indexer), [magento2-vsbridge-indexer](https://github.com/vuestorefront/magento2-vsbridge-indexer) and [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) support the cache invalidation. If the cache is enabled in both API and Vue Storefront frontend app, please make sure you are properly using the `config.server.invalidateCacheForwardUrl` config variable as the indexers can send the cache invalidate request only to one URL (frontend or backend) and it should be forwarded. Please check the default forwarding URLs in the `default.json` and adjust the `key` parameter to the value of `server.invalidateCacheKey`.
 :::
 
 For `magento1-vsbridge-indexer` and `magento2-vsbridge-indexer` please do use the proper settings in the Magento admin panel.

docs/guide/cookbook/checklist.md

@@ -137,7 +137,7 @@ X-VS-Cache-Tags: P1852 P198 C20
 The tags can be used to invalidate the Varnish cache if you use it. [Read more on that](https://www.drupal.org/docs/8/api/cache-api/cache-tags-varnish).
 
 :::tip NOTE
- All the official Vue Storefront data indexers including [magento1-vsbridge-indexer](https://github.com/vuestorefront/magento1-vsbridge-indexer), [magento2-vsbridge-indexer](https://github.com/vuestorefront/magento2-vsbridge-indexer) and [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) support the cache invalidation. 
+ All the official Vue Storefront data indexers including [magento1-vsbridge-indexer](https://github.com/divanteLtd/magento1-vsbridge-indexer), [magento2-vsbridge-indexer](https://github.com/vuestorefront/magento2-vsbridge-indexer) and [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) support the cache invalidation. 
 
  If the cache is enabled in both API and Vue Storefront frontend app, please make sure you properly use the `config.server.invalidateCacheForwardUrl` config variable as the indexers can send the cache invalidate request only to one URL (either frontend or backend) and it **should be forwarded** to the other. Please check the default forwarding URLs in the `default.json` and adjust the `key` parameter to the value of `server.invalidateCacheKey`.
 :::
@@ -658,7 +658,7 @@ Although many Vue Storefornt projects are being developed using [mage2vuestorefr
 Because of this limitation we created a set of [native indexers](https://medium.com/the-vue-storefront-journal/native-magento-data-indexer-aec3c9ebfb).
 
 The indexers are available for:
-- [Magento 1](https://github.com/vuestorefront/magento1-vsbridge-indexer)
+- [Magento 1](https://github.com/divanteLtd/magento1-vsbridge-indexer)
 - [Magento 2](https://github.com/vuestorefront/magento2-vsbridge-indexer)
 
 The native indexer updates the Elasticsearch index in the very same format as the `mage2vuestorefront`. Our intention was to speed up the indexation process and make it more reliable. With native indexer, we were able to use the Magento 2 ORM and events to optimize the indexation process. Please do use this module instead of `mage2vuestorefront` if you experience any issue regarding indexing performance. Both projects are currently officially supported by the Vue Storefront Core team.
@@ -673,7 +673,7 @@ This URL requires you to pass the invalidation token set in the [config](https:/
 The tags can be used to invalidate the Varnish cache, if you're using it. [Read more on that](https://www.drupal.org/docs/8/api/cache-api/cache-tags-varnish).
 
 :::tip NOTE
-All the official Vue Storefront data indexers including [magento1-vsbridge-indexer](https://github.com/vuestorefront/magento1-vsbridge-indexer), [magento2-vsbridge-indexer](https://github.com/vuestorefront/magento2-vsbridge-indexer) and [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) support the cache invalidation. If the cache is enabled in both API and Vue Storefront frontend app, please make sure you are properly using the `config.server.invalidateCacheForwardUrl` config variable as the indexers can send the cache invalidate request only to one URL (either frontend or backend) and it **should be forwarded** to the other. Please check the default forwarding URLs in the `default.json` and adjust the `key` parameter to the value of `server.invalidateCacheKey`.
+All the official Vue Storefront data indexers including [magento1-vsbridge-indexer](https://github.com/divanteLtd/magento1-vsbridge-indexer), [magento2-vsbridge-indexer](https://github.com/vuestorefront/magento2-vsbridge-indexer) and [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) support the cache invalidation. If the cache is enabled in both API and Vue Storefront frontend app, please make sure you are properly using the `config.server.invalidateCacheForwardUrl` config variable as the indexers can send the cache invalidate request only to one URL (either frontend or backend) and it **should be forwarded** to the other. Please check the default forwarding URLs in the `default.json` and adjust the `key` parameter to the value of `server.invalidateCacheKey`.
 :::
 
 <br />

docs/guide/cookbook/data-import.md

@@ -463,7 +463,7 @@ In this recipe we will walk you with **Magento 2** example.
 <br />
 - You need an Elasticsearch instance [running](setup.html#_1-install-with-docker) with mapping is done as in [*Recipe 1 Data Mapping Migration for Elasticsearch*](#_1-data-mapping-migration-for-elasticsearch)
 <br />
-- You need [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) downloaded for data bridge. This instance is backend-dependant (in this case, Magento 2), you may replace it with other data bridges such as [coreshop-vsbridge](https://github.com/vuestorefront/coreshop-vsbridge), [shopware2vuestorefront](https://github.com/vuestorefront/shopware2vuestorefront) to your advantage. 
+- You need [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) downloaded for data bridge. This instance is backend-dependant (in this case, Magento 2), you may replace it with other data bridges such as [coreshop-vsbridge](https://github.com/divanteLtd/coreshop-vsbridge), [shopware2vuestorefront](https://github.com/divanteLtd/shopware2vuestorefront) to your advantage. 
 <br />
 - Finally, you need a Magento 2 instance as a data source to pump your data from. (For [Recipe B](#_2-2-recipe-b-using-on-premise) only)
 
@@ -473,7 +473,7 @@ We are going to import entities as follows :
 - Taxrules
 - Attributes
 - Product-to-categories
-- Reviews (require custom module [Divante/ReviewApi](https://github.com/vuestorefront/magento2-review-api))
+- Reviews (require custom module [Divante/ReviewApi](https://github.com/divanteLtd/magento2-review-api))
 - Cms Blocks & Pages (require custom module [SnowdogApps/magento2-cms-api](https://github.com/SnowdogApps/magento2-cms-api))
 
 ### 2-1. Recipe A (Using Demo)
@@ -713,7 +713,7 @@ node --harmony cli.js products --removeNonExistent=true --partitions=1
 
 6. In order to import `reviews` and `cms`, we need to install additional Magento 2 modules, so that we can expose required API. 
 
-Download and install [Review API module](https://github.com/vuestorefront/magento2-review-api) and run the following : 
+Download and install [Review API module](https://github.com/divanteLtd/magento2-review-api) and run the following : 
 ```bash
 node --harmony cli.js reviews
 ```

docs/guide/cookbook/elastic.md

@@ -428,7 +428,7 @@ node --harmony cli.js pages
 ```
 
 :::tip NOTE
-API endpoints for _reviews_, _blocks_ and _pages_ from Magento are not available out of the box. You should install additional modules for them on your own. [review](https://github.com/vuestorefront/magento2-review-api), [cms](https://github.com/SnowdogApps/magento2-cms-api)
+API endpoints for _reviews_, _blocks_ and _pages_ from Magento are not available out of the box. You should install additional modules for them on your own. [review](https://github.com/divanteLtd/magento2-review-api), [cms](https://github.com/SnowdogApps/magento2-cms-api)
 :::
 
 Now you are ready to launch your Vue Storefront shop powered by _Elasticsearch 7_. 

docs/guide/data/database-tool.md

@@ -4,7 +4,7 @@ Vue Storefront gets all of its data from [vue-storefront-api](https://github.com
 
 If you installed the project using `yarn installer`  command,  the database has been set up, data imported from demo-dump, and everything should be just fine.
 
-After more extensive data operations, like custom imports using [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) or [magento1-vsbridge](https://github.com/vuestorefront/magento1-vsbridge), there is a need to reindex the Elasticsearch and set up the proper metadata for fields.
+After more extensive data operations, like custom imports using [mage2vuestorefront](https://github.com/vuestorefront/mage2vuestorefront) or [magento1-vsbridge](https://github.com/divanteLtd/magento1-vsbridge), there is a need to reindex the Elasticsearch and set up the proper metadata for fields.
 
 
 The main reason you’ll know you must reindex the database is the following error you get from the `vue-storefront` console:

docs/guide/general/introduction.md

@@ -37,7 +37,7 @@ The API connector works in two phases:
 
 VueStorefront works seamlessly with your backend platform while two integration phases are managed as above.
 
-Some of the most popular backend platforms already have their integrations ([Magento 2](https://github.com/vuestorefront/mage2vuestorefront), [Magento 1](https://github.com/vuestorefront/magento1-vsbridge), [CoreShop](https://github.com/vuestorefront/coreshop-vsbridge), [BigCommerce](https://github.com/vuestorefront/bigcommerce2vuestorefront), [WooCommerce](https://github.com/vuestorefront/woocommerce2vuestorefront)), but you can easily make your own with the [integration boilerplate](https://github.com/vuestorefront/vue-storefront-integration-boilerplate).
+Some of the most popular backend platforms already have their integrations ([Magento 2](https://github.com/vuestorefront/mage2vuestorefront), [Magento 1](https://github.com/divanteLtd/magento1-vsbridge), [CoreShop](https://github.com/divanteLtd/coreshop-vsbridge), [BigCommerce](https://github.com/divanteLtd/bigcommerce2vuestorefront), [WooCommerce](https://github.com/divanteLtd/woocommerce2vuestorefront)), but you can easily make your own with the [integration boilerplate](https://github.com/divanteLtd/vue-storefront-integration-boilerplate).
 
 The blue parts on the diagram are responsible for offline cache and will be explained later in the article.
 

docs/guide/integrations/integrations.md

@@ -3,9 +3,9 @@
 Here is a short list of existing Vue Storefront integrations with links to their repositories.
 
 - [Vue Storefront + Magento](https://github.com/vuestorefront/mage2vuestorefront)
-- [Vue Storefront + Magento 1.9](https://github.com/vuestorefront/magento1-vsbridge)
-- [Vue Storefront + with Magento checkout](https://github.com/vuestorefront/magento2-external-checkout)
-- [Vue Storefront + Pimcore](https://github.com/vuestorefront/pimcore2vuestorefront)
+- [Vue Storefront + Magento 1.9](https://github.com/divanteLtd/magento1-vsbridge)
+- [Vue Storefront + with Magento checkout](https://github.com/divanteLtd/magento2-external-checkout)
+- [Vue Storefront + Pimcore](https://github.com/divanteLtd/pimcore2vuestorefront)
 - [Magento2 Product Reviews](https://github.com/vuestorefront/vue-storefront/blob/develop/doc/Reviews.md)
-- [Vue Storefront 3rd party platforms integration boilerplate](https://github.com/vuestorefront/vue-storefront-integration-boilerplate) - This is the API you should implement to integrate a third-party platform.
+- [Vue Storefront 3rd party platforms integration boilerplate](https://github.com/divanteLtd/vue-storefront-integration-boilerplate) - This is the API you should implement to integrate a third-party platform.
 - [Vue Storefront + Fresh Relevance](https://github.com/TriggeredMessaging/vsf-freshrelevance)

docs/guide/integrations/multistore.md

@@ -220,7 +220,7 @@ export default function(app, router, store) {
 Another option is to create a separate theme for a specific storeview. Runtime theme changes are not possible, as themes are compiled in the JS bundles by webpack during the page build process. In that case, you should run separate instances of `vue-storefront` having the proper theme set in the `config/local.json` file.
 
 ## Multi Source Inventory (MSI) support
-To support this custom feature you should take care of 2 things. At first please install [Magento2 VSBridge Indexer MSI Extension](https://github.com/vuestorefront/magento2-vsbridge-indexer-msi). Then in `config/local.json` of your VSF-API add part like:
+To support this custom feature you should take care of 2 things. At first please install [Magento2 VSBridge Indexer MSI Extension](https://github.com/divanteLtd/magento2-vsbridge-indexer-msi). Then in `config/local.json` of your VSF-API add part like:
 ```js
 "msi": {
   "enabled": true,

docs/guide/integrations/reviews.md

@@ -1,11 +1,11 @@
 # Product Reviews
 
-Starting with the 1.4.0 release, Vue Storefront is supporting Magento 2 product reviews. Unfortunately, the Magento 2 REST API doesn't contain any Reviews-related endpoints, so to make it work, you need to install an [additional Magento 2 module](https://github.com/vuestorefront/magento2-review-api).
+Starting with the 1.4.0 release, Vue Storefront is supporting Magento 2 product reviews. Unfortunately, the Magento 2 REST API doesn't contain any Reviews-related endpoints, so to make it work, you need to install an [additional Magento 2 module](https://github.com/divanteLtd/magento2-review-api).
 
 Installation steps (in your Magento 2 directory):
 
 ```bash
-composer config repositories.divante vcs https://github.com/vuestorefront/magento2-review-api.git
+composer config repositories.divante vcs https://github.com/divanteLtd/magento2-review-api.git
 composer require divante/magento2-review-api:dev-master
 php bin/magento setup:upgrade
 ```

docs/guide/upgrade-notes/README.md

@@ -409,7 +409,7 @@ This change does not involve any required actions to port the code, but please b
 
 #### Reviews
 
-We added Reviews support, however, Magento 2 is still lacking Reviews support in the REST API. To have reviews up and running, please add the https://github.com/vuestorefront/magento2-review-api to your Magento 2 instance.
+We added Reviews support, however, Magento 2 is still lacking Reviews support in the REST API. To have reviews up and running, please add the https://github.com/divanteLtd/magento2-review-api to your Magento 2 instance.
 
 #### Microcart