Content modification to have an App instead a Connector

Author: arduibag

content/guides/ecommerce-connection/step4-define-your-first-scope.md

@@ -16,6 +16,10 @@ You have to choose these versions according to:
 * The number of potential users owning this version.
 * The lifetime of this version. It is useless to specifically develop a version compatible with a version of your eCommerce solution if this one won't exist anymore in a couple of months.
 
+## Follow the guide to build an App!
+
+We have a ["complete guide"](https://api.akeneo.com/apps/introduction.html) to understand how to build an App.
+
 ## What are Akeneo's recommendations to build the first iteration of an eCommerce App release?
 
 **Our recommendation: always listen to your customer's needs first!**

content/guides/erp-connection/introduction.md

@@ -42,5 +42,5 @@ Understand your target user: Who will install it? Who will set it up? Who will u
 Understand the product information that should flow between your ERP and the PIM.
 3. [Understand Akeneo PIM](step3-understand-akeneo-pim.html)
 Understand Akeneo PIM, its features, its data structure in order to be able to compare them with your ERP solution.
-4. [How to build your App?](step4-how-to-build-your-connector.html)
+4. [How to build your App?](step4-how-to-build-your-app.html)
 Ready to start? Some last recommendations on how to interact with our PIM...

content/guides/erp-connection/step4-how-to-build-your-app.md

@@ -23,9 +23,9 @@ All you need to know to interact with our PIM through our API can be found in ou
 
 **Our recommendation: always listen to your customer's needs first.**
 
-We are aware that it is quite difficult to develop a 100% complete connector that fits all your customer's needs immediately.
+We are aware that it is quite difficult to develop a 100% complete App that fits all your customer's needs immediately.
 
-Once you are comfortable with your customer's needs, our recommendation is to follow the steps we describe and to iterate in order not to miss any important feature. Building an ERP connector is a complex task that requires a dedicated focus every step of the way.  
+Once you are comfortable with your customer's needs, our recommendation is to follow the steps we describe and to iterate in order not to miss any important feature. Building an ERP App is a complex task that requires a dedicated focus every step of the way.  
 
 **To conclude: adopt an Agile approach**
 

content/guides/print-connection/introduction.md

@@ -2,7 +2,7 @@
 ![Asset family illustration](../../img/illustrations/illus--Assetfamily.svg)
 
 > Do you want to connect your PIM to your print solution?  
-> You want to implement an Akeneo PIM print connector and you don't know where to start?  
+> You want to implement an Akeneo PIM print App and you don't know where to start?  
 
 You landed in the right place!
 
@@ -23,4 +23,4 @@ Understand Akeneo PIM, its features, its data structure in order to be able to m
 4. [Reconcile PIM data with print capabilities](step3-reconcile-PIM-data-with-print-features.html)  
 Discover how you can use PIM data on paper products.
 5. [Starting your first version](step4-define-your-first-scope.html)  
-What are Akeneo's recommendations for starting the first version of a print connector?
+What are Akeneo's recommendations for starting the first version of a print App?

content/guides/print-connection/step2-understand-akeneo-pim.md

@@ -16,24 +16,24 @@ Then, in order to understand our different editions and their capabilities, you
 
 Play with our PIM!
 
-It is crucial to understand the PIM features and data model in order to create a great print connector.
+It is crucial to understand the PIM features and data model in order to create a great print App.
 
 The best way to become an expert at Akeneo PIM is to play with it!  
 Here, you can access our [Akeneo PIM Community Edition demo platform](http://demo.akeneo.com) (login/password: admin / admin).
 
 :::warning
-Please note that this Akeneo PIM CE demo instance is for exploratory purposes only and will only allow you to start getting familiar with Akeneo PIM. This instance is reset frequently and is therefore not intended to be used to build a connector.
+Please note that this Akeneo PIM CE demo instance is for exploratory purposes only and will only allow you to start getting familiar with Akeneo PIM. This instance is reset frequently and is therefore not intended to be used to build a App.
 :::
 
-If you need an Akeneo PIM **Enterprise Edition** instance to start developing your connector, please [contact us](https://www.akeneo.com/contact/).
+If you need an Akeneo PIM **Enterprise Edition** instance to start developing your App, please [contact us](https://www.akeneo.com/contact/).
 
 ## Acquire PIM knowledge
 
 We advise you to take a look at our [Helpcenter](https://help.akeneo.com/pim/index.html) where you'll find a lot of documentation about all our features.
 
 If you feel that a comprehensive training program would allow you to know everything about Akeneo PIM, we got you covered as well with our [training sessions](https://www.akeneo.com/training/). Don't hesitate to register!
 
-In the context of building a print connector, here is a selection of PIM concepts you'll need to master before developing anything:
+In the context of building a print App, here is a selection of PIM concepts you'll need to master before developing anything:
 - The [product](/concepts/products.html#product),
 - The [product model](/concepts/products.html#product-model),
 - The [family](/concepts/catalog-structure.html#family),

content/guides/print-connection/step3-reconcile-PIM-data-with-print-features.md

@@ -7,17 +7,17 @@ Congratulations! Now that you have a good overview of Akeneo PIM data, you need
 Next step, for each piece of PIM data, you need to ask yourself the following questions:
 
 1. What data does my print solution need from the PIM?
-2. How will the configuration UI of my connector fulfill all of my end users' needs?  
-3. How flexible does my connector need to be to adapt to any catalog structure created with the PIM?
+2. How will the configuration UI of my App fulfill all of my end users' needs?  
+3. How flexible does my App need to be to adapt to any catalog structure created with the PIM?
 4. Documentation: What do I need to document? (Data processing, feature limits, possible settings...)   
 
-In order to help you develop your connector features, here are some useful features you can use. 
+In order to help you develop your App features, here are some useful features you can use.
 
 ## API connection configuration
 
 **What is it?**
 
-In order for your connector to communicate with Akeneo PIM, you need to provide a setting to invite Julia to enter her PIM API credentials.
+In order for your App to communicate with Akeneo PIM, you need to provide a setting to invite Julia to enter her PIM API credentials.
 
 **What do you need to implement?**
 
@@ -44,7 +44,7 @@ Here are some examples of filters we believe are relevant:
 * Channel: Only import product data related to the selected channel (most of the time a "print" channel).
 * Locale: Only import product data related to the selected locale.
 * Completeness: A PIM product can be exported if it is complete in terms of data content, translation (localizable attribute), or information specific to the channels you are going to use (attribute with a value per channel).
-* Enabled/Disabled status: Each PIM product has an enable/disable status. You can set your connector to only export products that are `enabled`.
+* Enabled/Disabled status: Each PIM product has an enable/disable status. You can set your App to only export products that are `enabled`.
 
 And sometimes, your customers may also need to export a PIM product to the print solution based on the following parameters:
 
@@ -55,11 +55,11 @@ And sometimes, your customers may also need to export a PIM product to the print
 * A category tree or a subcategory tree
 * ...
 
-**Conclusion:** each customer project has its own requirements and it is important to offer enough flexibility in your connector settings to allow each customer to import only the product information they need according to their own criteria.
+**Conclusion:** each customer project has its own requirements and it is important to offer enough flexibility in your App settings to allow each customer to import only the product information they need according to their own criteria.
 
 **What do you need to implement?**
 
-In the features of your connector configuration page, in order to be able to cover all of your customers' needs, you can choose to have one of the two filter systems. Either a “simple” one for straightforward use cases or an “advanced” one for the most specific requirements. 
+In the features of your App configuration page, in order to be able to cover all of your customers' needs, you can choose to have one of the two filter systems. Either a “simple” one for straightforward use cases or an “advanced” one for the most specific requirements.
 
 ### Products with variants
 
@@ -109,7 +109,7 @@ Apart from taking into consideration all these PIM modeling capabilities, you al
 
 ::: warning
 The number of images that a catalog can contain can be quite large and we know that images dedicated to a print catalog can be very heavy (high definition).
-Make sure you have all the mechanisms in your connector to optimize the performance to manage image binaries.
+Make sure you have all the mechanisms in your App to optimize the performance to manage image binaries.
 :::
 
 
@@ -172,7 +172,7 @@ The introduction of [our documentation on Reference Entities](https://help.akene
 
 As you can see, Reference Entities can be used to enrich product information or to create dedicated pages with product relationships.
 
-Keep in mind that Julia can use "Reference Entities" for a wide variety of needs, you might have to adapt accordingly. 
+Keep in mind that Julia can use "Reference Entities" for a wide variety of needs, you might have to adapt accordingly.
 
 **What do you need to implement?**
 

content/guides/print-connection/step4-define-your-first-scope.md

@@ -1,33 +1,35 @@
 # Define the scope of your first version
 
-## A "Connection-compliant" connector
-
-The best way to interact with Julia's PIM is to develop a "[Connection-compliant](https://help.akeneo.com/pim/serenity/articles/what-is-a-connection.html)" connector (based on our API).
-
-:::tips
-Why?
-Please don't hesitate to read our ["4 reasons why you should use our API"](https://api.akeneo.com/documentation/why-the-api.html#4-reasons-why-you-should-use-our-api) page.
-:::
-
-## Follow the guide!
+## Find your PIM compatibility
 
 As [mentioned before](step2-understand-akeneo-pim.html), there are [several editions](https://www.akeneo.com/compare-editions/) and several supported versions of Akeneo PIM.
 
-Of course, the choice of the PIM version/edition depends on your business but we strongly encourage you to develop a connector that is fully compatible with our latest **SaaS edition**.
+Of course, the choice of the PIM version/edition depends on your business but we strongly encourage you to develop an App that is fully compatible with our latest **SaaS edition**.
 
 To know more about the different PIM versions, don't hesitate to consult our blog section on our [PIM release cycle](https://www.akeneo.com/blog/akeneo-introduces-a-simpler-product-release-cycle/).
 
 You can also consult our [release notes](https://www.akeneo.com/release-notes/) and our ["new key features released" page](https://help.akeneo.com/pim/serenity/whats-new.html) to understand more about the latest Akeneo supported **versions** and their brand new features.
 
-Well, now you can [start here](https://api.akeneo.com/getting-started/connect-the-pim-4x/welcome.html) to connect your print solution with our API! 🚀
+## Follow the guide to build an App!
+
+We have a ["complete guide"](https://api.akeneo.com/apps/introduction.html) to understand how to build an App.
+
+## Use our API
+
+:::tips
+Why?
+Please don't hesitate to read our ["4 reasons why you should use our API"](https://api.akeneo.com/documentation/why-the-api.html#4-reasons-why-you-should-use-our-api) page.
+:::
+
+Well, now you can [start here](https://api.akeneo.com/documentation/introduction.html) to connect your print solution with our API! 🚀
 
 ## Step by step
 
 **Our recommendation: always listen to your customer's needs first!**
 
-We are aware that it is difficult and expensive in terms of investment to achieve a 100% complete print connector that is flexible enough to adapt to any customer project.
+We are aware that it is difficult and expensive in terms of investment to achieve a 100% complete print App that is flexible enough to adapt to any customer project.
 
-Furthermore, to build such a complex connector as a print connector in a single iteration would undoubtedly be too complex to design from scratch.
+Furthermore, to build such a complex App as a print App in a single iteration would undoubtedly be too complex to design from scratch.
 
 **Our advice: adopt an Agile approach!**
 

content/guides/syndication-connection/step3-define-your-first-scope.md

@@ -1,15 +1,6 @@
 # Define the scope of your first version
 
-## A "Connection-compliant" App
-
-The best way to interact with Julia's PIM is to develop a "[Connection-compliant](https://help.akeneo.com/pim/serenity/articles/what-is-a-connection.html)" App (based on our API).
-
-:::tips
-Why?
-Please don't hesitate to read our ["4 reasons why you should use our API"](https://api.akeneo.com/documentation/why-the-api.html#4-reasons-why-you-should-use-our-api) page.
-:::
-
-## Follow the guide!
+## Find your PIM compatibility
 
 As [mentioned before](step2-understand-akeneo-pim.html), there are [several editions](https://www.akeneo.com/compare-editions/) and several supported version of Akeneo PIM.
 
@@ -19,7 +10,9 @@ To know more about the different PIM versions, don't hesitate to consult our blo
 
 You can also consult our [release notes](https://www.akeneo.com/release-notes/) and our ["new key features released" page](https://help.akeneo.com/pim/serenity/whats-new.html) to understand more about the latest Akeneo supported **versions** and their brand new features.
 
-Well, now you can [start here](https://api.akeneo.com/getting-started/connect-the-pim-4x/welcome.html) to connect your syndication solution with our API! 🚀
+## Follow the guide to build an App!
+
+We have a ["complete guide"](https://api.akeneo.com/apps/introduction.html) to understand how to build an App.
 
 ## Step by step
 

content/guides/translation-connection/introduction.md

@@ -14,11 +14,11 @@ We're here to help you find your way around, understand how Akeneo PIM will inte
 
 ## Follow the steps!
 
-1. [Who is your connector for?](step1-who-is-your-app-for.html)  
+1. [Who is your App for?](step1-who-is-your-app-for.html)  
 Understand your target user: Who will install it? Who will set it up? Who will use it? What are their needs?
 2. [Understand Akeneo PIM](step2-understand-akeneo-pim.html)
 Understand Akeneo PIM product structure and what data can be translated.
-3. [How to build your connector?](step3-how-to-build-your-connector.html)
+3. [How to build your App?](step3-how-to-build-your-app.html)
 Discover Akeneo PIM interaction capabilities to enable product data translation.
 4. [Known limits](step4-known-limits.html)
 Also understand the current limits of the suggested design...