Merge pull request #3 from docusign/DEVDOCS-14961

naming changes

Author: paigesrossi

.env.example

@@ -4,11 +4,11 @@ NODE_ENV=development # Set to "production" so server serves static assets
 
 ### Client Variables
 FRONTEND_DEV_HOST=http://localhost:3000
-FRONTEND_PROD_HOST=https://mymaestro.azurewebsites.net
+FRONTEND_PROD_HOST={PROD_HOST}
 
 ### Server Variables
 BACKEND_DEV_HOST=http://localhost:4000/api
-BACKEND_PROD_HOST=https://mymaestro.azurewebsites.net/api
+BACKEND_PROD_HOST={PROD_HOST}/api
 JWT_REDIRECT_URI=https://developers.docusign.com/platform/auth/consent # Where the user will be redirected after providing consent for JWT.
 DS_OAUTH_SERVER=https://account-d.docusign.com # The Docusign authentication server, used for JWT.
 USER_ID={YOUR_USER_ID} # A GUID unique to each user's Docusign Account, located on the Apps and Keys page.

README.md

@@ -1,8 +1,8 @@
-# Node.js and React: MyMaestro Sample App
+# Node.js and React: Maestro Sample App
 
 ## Introduction
 
-Welcome to the MyMaestro sample app! MyMaestro is written using Node.js and React. Docusign Maestro lets you easily build and deploy customized workflows that automate and accelerate your agreement processes without writing any code. Maestro connects all the tools and activities in your workflow so that agreement processes are more efficient, more uniform, and have better visibility.
+Welcome to the Maestro Sample App! The app is written using Node.js and React. Docusign Maestro lets you easily build and deploy customized workflows that automate and accelerate your agreement processes without writing any code. Maestro connects all the tools and activities in your workflow so that agreement processes are more efficient, more uniform, and have better visibility.
 
 With Docusign Maestro, you can combine Docusign features such as ID Verification, Web Forms, and eSignature with third-party extensions to automate your workflows from end to end.
 
@@ -20,7 +20,6 @@ Before you can run this sample app on your local machine, you must first create
       - Save the **integration key** and **private RSA key pair** somewhere safe as you will need these later.
 5. Add redirect URIs for your app. There are several variables from the **.env** file that are used in the code and configured for redirect urls. Find variables below in the **.env** file and add the values of these variables in the Docusign account settings in the appropriate **Redirect URIs** section:
     - FRONTEND_DEV_HOST (http://localhost:3000)
-    - FRONTEND_PROD_HOST (https://mymaestro.azurewebsites.net)
     - JWT_REDIRECT_URI (https://developers.docusign.com/platform/auth/consent)
 
 If you run this project in Docker using the **docker-compose.local.yml** file, the variable FRONTEND_DEV_HOST there changes to the value **http://localhost:80**. Keep in mind that in this case this value will also have to be added to the **Redirect URIs** section.
@@ -35,8 +34,8 @@ If you run this project in Docker using the **docker-compose.local.yml** file, t
 
 ### Install dependencies locally
 
-1. Download or clone this repository to your workstation in a new folder named **sample-app-mymaestro-node**.
-2. Navigate to that folder: **`cd sample-app-mymaestro-node`**
+1. Download or clone this repository to your workstation in a new folder named **sample-app-maestro-node**.
+2. Navigate to that folder: **`cd sample-app-maestro-node`**
 3. Navigate to the **client** folder: **`cd client`**
 4. Install dependencies using the [npm](https://www.npmjs.com/) package manager: **`npm install`**
 5. Navigate to the **server** folder: **`cd ../server`**
@@ -45,20 +44,20 @@ If you run this project in Docker using the **docker-compose.local.yml** file, t
   > **Note:** Protect your integration key and client secret. You should make sure that the **.env** file will not be stored in your source code repository.
 8. Rename the **example_private.key** file to **private.key**, and paste your complete private RSA key into this file (including the header and footer of the key). This should be the private RSA you should have gotten when you created your Docusign account.
 
-## Running MyMaestro in development mode
+## Running the Maestro Sample App in development mode
 
-1. Navigate to the application folder: **`cd sample-app-mymaestro-node`**
+1. Navigate to the application folder: **`cd sample-app-maestro-node`**
 2. To start the server and client at the same time: **`npm run concurrently:dev`**
 3. **Or,** to run the server and client separately:
     - In one terminal, run **`npm run client:dev`**
     - In a separate terminal, run **`npm run server:dev`**
 4. Open a browser to **http://localhost:3000**
 
-## Running MyMaestro in Docker
+## Running the Maestro Sample App in Docker
 
 You can run the application in Docker locally in production mode:
 
-1. Navigate to the application folder: **`cd sample-app-mymaestro-node`**
+1. Navigate to the application folder: **`cd sample-app-maestro-node`**
 2. Make sure that you configured **.env** file and saved your **private.key** in the root of the folder. Make sure that you have Docker installed.
 3. Run **`docker-compose -f docker-compose.local.yaml up -d`**
 4. To stop containers, run **`docker compose -f docker-compose.local.yaml down`**

client/README.md

@@ -1,12 +1,12 @@
-# MyMaestro Frontend
+# Maestro Sample App Frontend
 
 ![React + Vite](./src/assets/img/favicon.png) ![React + Vite](./src/assets/img/logo.svg)
 
 Created with React + Vite! This setup provides a minimal yet powerful environment to develop React applications with Vite. It includes Hot Module Replacement (HMR) and some ESLint rules to ensure code quality.
 
 ## Table of Contents
 
-- [MyMaestro Frontend](#mymaestro-frontend)
+- [Maestro Sample App Frontend](#maestro-frontend)
   - [Table of Contents](#table-of-contents)
   - [Available Scripts](#available-scripts)
     - [`npm run dev`](#npm-run-dev)

client/index.html

@@ -3,10 +3,10 @@
 <head>
   <meta charset="UTF-8" />
   <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-  <meta property="og:title" content="MyMaestro Sample App" />
-  <meta property="og:description" content="Leverage the power of Docusign workflows with Maestro. MyMaestro showcases how the Maestro API (beta) can be used to create workflow definitions and trigger, cancel, and get status updates for workflow instances." />
+  <meta property="og:title" content="Maestro Sample App" />
+  <meta property="og:description" content="Leverage the power of Docusign workflows with Maestro. The Maestro Sample App showcases how the Maestro API (beta) can be used to create workflow definitions and trigger, cancel, and get status updates for workflow instances." />
   <meta property="og:image" content="/og-image.jpg" />
-  <title>MyMaestro</title>
+  <title>Maestro Sample App</title>
   <link rel="icon" type="image/x-icon" href="./src/assets/img/favicon.png">
 </head>
 <body>