Parameterized the files under content_bestpractices (#2521)

Replaced or reworked product names with either variables or generic content for best practices section

Co-authored-by: alexmolev <amolev@gmail.com>

Author: oloten

content/bestpractices/jenkins-plugin.md

@@ -1,6 +1,6 @@
 ---
 title: "Jenkins Plugin"
-description: "Introduction to Jenkins' Cloudify integration"
+description: "Introduction to Jenkins' integration"
 weight: 99
 alwaysopen: false
 ---
@@ -11,15 +11,15 @@ alwaysopen: false
 
 ![Jenkins Plugin]( /images/jenkins/jenkins-plugin.png )
 
-The Jenkins Plugin for Cloudify, provided with version 5.0.5 onward, allows Jenkins authors
-to embed Cloudify functions within jobs and pipelines.
+The Jenkins Plugin for {{< param product_name >}}, provided with version 5.0.5 onward, allows Jenkins authors
+to embed {{< param product_name >}} functions within jobs and pipelines.
 
 ### Plugin contents
 
 The plugin provides:
 
-* Discrete build steps for basic Cloudify functions (uploading / deleting blueprints, creating / deleting environments, workflow execution and so forth)
-* A standard Jenkins _Build Wrapper_, a convenient enclosure for other build steps that sets up a Cloudify environment before the main steps and deletes the environment afterwards
+* Discrete build steps for basic {{< param product_name >}} functions (uploading / deleting blueprints, creating / deleting environments, workflow execution and so forth)
+* A standard Jenkins _Build Wrapper_, a convenient enclosure for other build steps that sets up a {{< param product_name >}} environment before the main steps and deletes the environment afterwards
 * Build steps for integration with other provisioning tools:
     * Azure ARM
     * AWS CloudFormation

content/bestpractices/manager_of_managers/_index.md

@@ -7,22 +7,22 @@ abstract: Spire Manager
 weight: 102
 ---
 
-# Using Cloudify as a Manager of Managers  (a.k.a  MoM or Spire)
-![Using Cloudify as a Manager of Managers](/images/mom/spire.png "Using Cloudify as a Manager of Managers")  
-*Using Cloudify as a Manager of Managers*
+# Using {{< param product_name >}} as a Manager of Managers  (a.k.a  MoM or Spire)
+![Using {{< param product_name >}} as a Manager of Managers](/images/mom/spire.png "Using {{< param product_name >}} as a Manager of Managers")  
+*Using {{< param product_name >}} as a Manager of Managers*
 
 
-The Cloudify managers of managers (Spire) feature allows control of several managers (*local managers*) from one manager (*Spire*) via the deploy-on feature.
+The {{< param product_name >}} managers of managers (Spire) feature allows control of several managers (*local managers*) from one manager (*Spire*) via the deploy-on feature.
 The deploy-on feature allows users to deploy services on the discovered environments.
 The deploy-on feature also provides a means to deploy the same service on multiple environments using a single command. Users can group the environments based on location, tagging and filters.
 The following guide provides a step by step guide on how to install sub managers, add them to a central manager using a discovery mechanism, and deploy an application on multiple managers through a single command.
 
 
-## 1. Installation of Cloudify Spire Manager
+## 1. Installation of {{< param cfy_spire_name >}} Manager
 
-To install the ***MAIN Manager (Spire)***, please refer to the [Cloudify official documentation.](https://docs.cloudify.co/latest/install_maintain/installation/installing-manager/)
+To install the ***MAIN Manager (Spire)***, please refer to the [{{< param product_name >}} official documentation.](https://docs.cloudify.co/latest/install_maintain/installation/installing-manager/)
 
-You can also check [Cloudify EC2 Provisioning](https://github.com/cloudify-community/cloudify-catalog/tree/6.4.0-build/cloudify_manager/ec2). It is the package for installing the *Cloudify Manager* on an ec2 AWS instance.
+You can also check [{{< param product_name >}} EC2 Provisioning](https://github.com/cloudify-community/cloudify-catalog/tree/6.4.0-build/cloudify_manager/ec2). It is the package for installing the *{{< param cfy_manager_name >}}* on an ec2 AWS instance.
 
 ## 2. Installation of sub-managers
 
@@ -40,17 +40,17 @@ First step is to deploy [manager_discovery.yaml](https://github.com/cloudify-com
 - ***protocol*** - protocol used by sub manager
 - ***port*** - number of port which sub manager is exposed
 
-[Installation using the Cloudify Management Console]({{< relref "exposing_submanager/exposing_submanager_ui.md" >}})
+[Installation using the {{< param cfy_console_name >}}]({{< relref "exposing_submanager/exposing_submanager_ui.md" >}})
 
-[Installation using the Cloudify API]({{< relref "exposing_submanager/exposing_submanager_api.md" >}})
+[Installation using the {{< param cfy_api_name >}}]({{< relref "exposing_submanager/exposing_submanager_api.md" >}})
 
-[Installation using the Cloudify CLI]({{< relref "exposing_submanager/exposing_submanager_cli.md" >}})
+[Installation using the {{< param cfy_api_name >}}]({{< relref "exposing_submanager/exposing_submanager_cli.md" >}})
 
 
 ### Required secrets
 
 To perform correct management, you need to create also a proper [secret](https://docs.cloudify.co/latest/cli/orch_cli/secrets/) about your **all** sub managers in Spire central manager. There are two ways to connect Spire with sub managers:
-- _Token_ - contains the proper value of [Cloudify token](https://docs.cloudify.co/latest/cli/orch_cli/tokens/). The token can be created with command ***cfy token create***
+- _Token_ - contains the proper value of [{{< param product_name >}} token](https://docs.cloudify.co/latest/cli/orch_cli/tokens/). The token can be created with command ***cfy token create***
 - _User password_ and _username_- contains the value of password and name of the user
 ![Secrets]( /images/mom/secrets.png )
 

content/bestpractices/manager_of_managers/deploy_on_mechanism/_index.md

@@ -27,7 +27,7 @@ Inputs description:
     - *trust_all* - the value of ***CLOUDIFY_SSL_TRUST_ALL*** (true if the certificate is not valid or for testing purpose)
 - optional (depends on authentication type):
     - *cloudify_secret_token* - the name of the secret which contains token value
-    - *cloudify_password_secret_name* and *cloudify_user_secret_name*- the name of the secret which contains value of the password and the user name of Cloudify user. 
+    - *cloudify_password_secret_name* and *cloudify_user_secret_name*- the name of the secret which contains value of the password and the user name of {{< param product_name >}} user. 
 
 ## Verification “Deploy on” mechanism
 To check if deployments are deployed on local managers, follow the example below/

content/bestpractices/manager_of_managers/exposing_submanager/exposing_submanager_cli.md

@@ -5,7 +5,7 @@ weight: 105
 alwaysopen: false
 ---
 
-#### Installation via Cloudify CLI.
+#### Installation via {{< param cfy_cli_name >}}.
 
 To proceed with CLI installation, refer to [official documentation](https://docs.cloudify.co/latest/cli/orch_cli/).
 

content/bestpractices/plugin-development.md

@@ -1,5 +1,5 @@
 ---
-title: "Cloudify Plugin Development: Best Practices"
+title: "Plugin Development: Best Practices"
 description: "Tips and best practices for plugin development"
 weight: 98
 alwaysopen: false
@@ -159,7 +159,7 @@ finally:
 
 ### Using `causes` with `RecoverableError` / `NonRecoverableError`
 
-When raising one of Cloudify’s exceptions (`RecoverableError` or `NonRecoverableError`), as a result of an underlying exception, you should use the “causes” feature when creating the exception class. This ensures that important troubleshooting data is not lost.
+When raising one of {{< param product_name >}}’s exceptions (`RecoverableError` or `NonRecoverableError`), as a result of an underlying exception, you should use the “causes” feature when creating the exception class. This ensures that important troubleshooting data is not lost.
 
 For example:
 

content/bestpractices/vmware_docs.md

@@ -1,8 +1,8 @@
 ---
-title: Cloudify Solution for the VMware stack
+title: Solution for the VMware stack
 category: Manager Architecture
 draft: false
-abstract: Cloudify Solution for the VMware stack
+abstract: Solution for the VMware stack
 weight: 100
 aliases: /manager_architecture/create-deployment-flow/
 ---