Removing dist/images folder, renaming image paths (#446)

Signed-off-by: Sarah Ishida <[email protected]>

docs/_documentations/eclipse-codechange.md

@@ -17,20 +17,20 @@ To see this feature in action, make a change to the getting started example.
 
 1\. Edit the `index.html` file.
 
-![](dist/images/eclipsechangeproject1.png){:width="800px"}
+![](images/eclipsechangeproject1.png){:width="800px"}
 
 2\. In the file, find the `Congratulations!` line.
 
-![](dist/images/eclipsechangeproject2.png)
+![](images/eclipsechangeproject2.png)
 
 3\. Change the heading from `Congratulations` to `I did this` and save the file.
 
-![](dist/images/eclipsechangeproject3.png)
+![](images/eclipsechangeproject3.png)
 
 4\. Click the **Open Application**
-![](dist/images/eclipseopenprojecticon.png)
+![](images/eclipseopenprojecticon.png)
 icon to show your code change running.
 
-![](dist/images/eclipsechangeproject4.png){:width="800px"}
+![](images/eclipsechangeproject4.png){:width="800px"}
 
 Next step: [Buiding and deploying in a cloud environment](remote-overview.html)

docs/_documentations/eclipse-firstproject.md

@@ -14,32 +14,32 @@ To create your first project:
 
 1\. Right-click the **Local [Running]** item and select **Create New Project...**.
 
-![](dist/images/eclipsecreateproject1.png){:width="800px"}
+![](images/eclipsecreateproject1.png){:width="800px"}
 
 2\. Creating a new project displays the project creation screen.
 
-![](dist/images/eclipsecreateproject2.png){:width="800px"}
+![](images/eclipsecreateproject2.png){:width="800px"}
 
 3\. Enter a name for the project and change the location if you want. Scroll through the list of templates until you see **Node.js Express**. 
 
-![](dist/images/eclipsecreateproject3.png){:width="800px"}
+![](images/eclipsecreateproject3.png){:width="800px"}
 
 4\. Select this template and click **Finish**. You now see the project overview screen.
 
-![](dist/images/eclipsecreateproject4.png){:width="800px"}
+![](images/eclipsecreateproject4.png){:width="800px"}
 
 5\. Codewind now starts to build and run your very first project. This process initially takes several minutes, depending on the speed of your network and the selected project.
 
 Once complete, the following screen shows your application is built and running. 
 
-![](dist/images/eclipsecreateproject5.png){:width="800px"}
+![](images/eclipsecreateproject5.png){:width="800px"}
 
 6\. To view your running application, select it in the Codewind Explorer view and click the **Open Application** icon.
-![](dist/images/eclipseopenprojecticon.png)
+![](images/eclipseopenprojecticon.png)
 
 This icon launches your web browser and displays your application.
 
-![](dist/images/eclipsefirstprojectrunning.png){:width="800px"}
+![](images/eclipsefirstprojectrunning.png){:width="800px"}
 
 Congratulations, you have created your first application on Codewind.
 

docs/_documentations/eclipse-getting-started.md

@@ -32,10 +32,10 @@ To install Codewind for Eclipse, complete the following steps:
     - Navigate to **Window**>**Show View**>**Other...**>**Codewind**>**Codewind Explorer**
 5. Codewind requires the installation of additional Docker images to run.  Double-click the **Codewind** item in the Codewind Explorer view to complete the installation. The installation might take a few minutes to complete.
 
-![image of Codewind once installed](dist/images/eclipseinstall1.png){:width="800px"}
+![image of Codewind once installed](images/eclipseinstall1.png){:width="800px"}
 
 6\. Once complete, you have a **Codewind** section in the IDE. 
 
-![image of Codewind once installed](dist/images/eclipseinstall2.png){:width="800px"}
+![image of Codewind once installed](images/eclipseinstall2.png){:width="800px"}
 
 Next step: [Create your first project](eclipse-firstproject.html)

docs/_documentations/metrics-dashboard.md

@@ -67,7 +67,7 @@ View a summary of the information from the performance metrics graphs that you s
 
 * **Resource Usage:** This table shows the **Average Process CPU**, which shows what the application is using, and the **Average System CPU**, which shows what the environment as a whole is using. This information can help determine whether application issues are caused by something else in the environment that is external to the application.
 
-![Resource Usage](dist/images/performanceguide/viewing_metrics.png)
+![Resource Usage](images/performanceguide/viewing_metrics.png)
 
 ## Viewing the graph in the **Profiling** tab
 
@@ -100,7 +100,7 @@ If profiling markers do not appear, check to see if your project and load run co
 
 After you start the load test and the test completes, view the source code. Theia displays an annotation tooltip with a specified message in a similar format to the following example:
 
-![image of Theia annotation tooltip](dist/images/theia-annotation-tooltip.png)
+![image of Theia annotation tooltip](images/theia-annotation-tooltip.png)
 
 - The bullet points indicate the parent callers of the function. The percentages equal the number of times that a parent caller called a function. In this example, `<anonymous function>` probably made 2 calls to the `app.get()` function, and the `handle()` function probably made 1 call.
 - The numbers in the parenthesis indicate the position of the parent function in the file, such as the line and character number. This position information is ambiguous for anonymous functions, but the message includes the information regardless.

docs/_documentations/performance.md

@@ -28,7 +28,7 @@ You will learn how to add and enable monitoring to your application. Then, you c
 1. From your IDE, go to the Codewind plug-in and right-click on a project.
 2. Then, select **Performance Dashboard**. A window appears that displays the Performance Dashboard.<br>
 
-![performance dashboard](dist/images/performanceguide/performancedash_window.png){:height="375px" width="800px"}<br>
+![performance dashboard](images/performanceguide/performancedash_window.png){:height="375px" width="800px"}<br>
 
 ## Running a load test
 

docs/_documentations/troubleshooting.md

@@ -113,7 +113,7 @@ Issue link: https://github.com/eclipse/codewind/issues/2239
 ## Cannot find Codewind in Marketplace when attempting to install in IntelliJ
 When attempting to install Codewind in IntelliJ, you cannot locate the Codewind plug-in in Marketplace, and if you verify the custom plug-in repository link, you get a `Connection failed` error message:
 
-![intellij install error](dist/images/intellij/custom-plugin-repo-connection-failed-error.png)
+![intellij install error](images/intellij/custom-plugin-repo-connection-failed-error.png)
 
 This error occurs because the custom plug-in repository link contains an additional space.
 

docs/_documentations/vsc-codechange.md

@@ -16,27 +16,27 @@ To see this feature in action, make a change to the getting started example.
 
 1\. Edit the `index.html` file:
 
-![](dist/images/vsc-codechange.png){:width="800px"}
+![](images/vsc-codechange.png){:width="800px"}
 
 2\. In the file, find the `Congratulations!` line.
 
-![](dist/images/vsc-codeline.png)
+![](images/vsc-codeline.png)
 
 3\. Change the heading from `Congratulations` to `I did this`:
 
-![](dist/images/vsc-ididthis.png)
+![](images/vsc-ididthis.png)
 
 The status of the project changes to **Stopped** while the project is rebuilt and deployed:
 
-![](dist/images/vsc-buildstopped.png)
+![](images/vsc-buildstopped.png)
 
 After a few moments, the status changes back to **Running**:
 
-![](dist/images/vsc-buildrunning.png)
+![](images/vsc-buildrunning.png)
 
 4\. Click the **Open Application** icon to show your code change running:
-![](dist/images/launchicon.png)
+![](images/launchicon.png)
 
-![](dist/images/vsc-screenchanged.png)
+![](images/vsc-screenchanged.png)
 
 Next step: [Buiding and deploying in a cloud environment](remote-overview.html)

docs/_documentations/vsc-firstproject.md

@@ -14,38 +14,38 @@ To create your first project:
 
 1\. Click on the prompt in the **Codewind** window.
 
-![](dist/images/createproject.png)
+![](images/createproject.png)
 
 2\. This prompt displays a list of project types for you to select. 
 
-![](dist/images/listtemplates.png)
+![](images/listtemplates.png)
 
 3\. Scroll through the list until you see **Node.js Express (Default templates)**.
 
-![](dist/images/nodetemplate.png)
+![](images/nodetemplate.png)
 
 4\. Selecting this template prompts you to enter a name for your project.
 
-![](dist/images/projectname.png)
+![](images/projectname.png)
 
 5\. Enter a name and then choose where to create this on disk. For example, `myFirstNodeProject`.
 
-![](dist/images/projloc.png)
+![](images/projloc.png)
 
 6\. Codewind now starts to build and run your very first project. Once complete,the following screen shows your application is built and running.
 
-![](dist/images/allbuilt.png)
+![](images/allbuilt.png)
 
 7\. To view your running application, click on the project name in the **Codewind** window. 
 
-![](dist/images/launch.png)
+![](images/launch.png)
 
 8\. Then click the **Open Application** icon.
-![](dist/images/launchicon.png)
+![](images/launchicon.png)
 
 This icon launches your web browser and displays your application.
 
-![](dist/images/runningapp.png)
+![](images/runningapp.png)
 
 Congratulations, you have created your first application on Codewind.
 

docs/_documentations/vsc-getting-started.md

@@ -24,6 +24,6 @@ order: 1
 5. Codewind requires the installation of additional Docker images to run. Choose **Install** when prompted to complete the installation. The installation might take a few minutes to complete.
 6. Once complete, you have a **Codewind** section in the IDE. 
 
-![image of Codewind once installed](dist/images/installed.png){:width="800px"}
+![image of Codewind once installed](images/installed.png){:width="800px"}
 
 Next step: [Create your first project](vsc-firstproject.html)

docs/_documentations/vsc-installinfo.md

@@ -16,7 +16,7 @@ The Codewind installation includes two parts:
 1. The VS Code extension installs when you install Codewind from the VS Code Marketplace or when you install by searching in the **VS Code Extensions** view.
 2. The Codewind back end containers install after you click **Install** when you are prompted. After you click **Install**, the necessary images are downloaded from the internet. The download is approximately 1 GB.
 
-![Switch start or stop Codewind](dist/images/cdt-vsc/on-off-switch.png)<br>
+![Switch start or stop Codewind](images/cdt-vsc/on-off-switch.png)<br>
 
 The following images are pulled. These images together form the Codewind back end:
 - `eclipse/codewind-initialize-amd64`

docs/_documentations/vsc-tutorial.md

@@ -40,12 +40,12 @@ For more detail on any of the commands, see the [commands overview](vsc-commands
         - In the Codewind tree, the application stops and starts again as the application server restarts.
         - You can also see **nodemon** restart the project in the application logs.
     - At this point, your VS Code should look similar to the following example:
-    <br>![Editing nodeproject](dist/images/cdt-vsc/tutorial-1.png)
+    <br>![Editing nodeproject](images/cdt-vsc/tutorial-1.png)
 7. To make sure your code change was picked up, test your new endpoint.
     - Right-click the project and select [Open App](vsc-commands-project.html#open-app). The project root endpoint opens in the browser, and the **IBM Cloud Starter** page appears.
     - Navigate to the new endpoint. If you copied the previous snippet, add `/health/test/` to the URL.
     - See the new response:<br>
-    <br>![New endpoint response](dist/images/cdt-vsc/tutorial-2.png)
+    <br>![New endpoint response](images/cdt-vsc/tutorial-2.png)
 8. You can debug your application within the container. To debug a containerized project, restart it in **Debug** mode.
     - Right-click the project and select [Restart in Debug Mode](vsc-commands-restart-and-debug.html#restart).
     - The project restarts into the **Debugging** state.
@@ -56,4 +56,4 @@ For more detail on any of the commands, see the [commands overview](vsc-commands
     - If your code matches the screenshot, set a breakpoint at line 13 in `health.js`.
     - Refresh the new endpoint page that you opened in step 7 so that a new request is made, and the breakpoint gets hit.
     - VS Code suspends your application at the breakpoint. Here you can step through the code, inspect variables, see the call stack, and evaluate expressions in the **Debug Console**.
-    ![Debugging](dist/images/cdt-vsc/tutorial-3.png)
+    ![Debugging](images/cdt-vsc/tutorial-3.png)

docs/_news/news06.md

@@ -42,4 +42,4 @@ The information in the **VS Code** section also applies to Eclipse but with thes
 #### VS Code output view
 - New to VS Code is the Codewind output stream, which logs `cwctl` commands and their output. In addition to providing status on all of your `cwctl` commands, it also helps you to debug unusual problems, especially when you start Codewind. For more information, see [Troubleshooting](troubleshooting.html).<br>
 
-![Image of VS Code output](dist/images/cdt-vsc/output_view.png)<br>
+![Image of VS Code output](images/cdt-vsc/output_view.png)<br>