Misc Fixes

Add yarn.lock to .gitignore
Add images to guides
Add logo to navbar

.gitignore

@@ -10,3 +10,4 @@ dist
 .basement
 config.local.js
 basement_dist
+yarn.lock

src/.vuepress/config.js

@@ -58,6 +58,7 @@ module.exports = {
     editLinks: true,
     editLinkText: '',
     lastUpdated: true,
+    logo: '/logo.svg',
     nav: [
       {
         text: 'Guide',

src/guide/Example-AdobeReader.md

@@ -18,7 +18,7 @@ This example is provided as a script with the toolkit, in the “Examples” fol
 
 1.  Copy the application source files in to the “Files” directory, e.g.
 
-    ![](images/image20.png)
+    ![](./img/image20.png)
 
 2.  Customize the Deploy-Application.ps1 script using the example code below
 

src/guide/Example-AdobeReaderSCCM20072012.md

@@ -6,38 +6,38 @@
 
   - Create a new Package:
 
-![](images/image21.png)
+![](./img/image21.png)
 
   - Set the package source folder accordingly:
 
-![](images/image22.png)
+![](./img/image22.png)
 
   - Accept the defaults for the rest of the package (or modify according to your environment)
 
   - Distribute the content of the package to the relevant Distribution Points
 
   - Create a new Program for the package:
 
-![](images/image23.png)
+![](./img/image23.png)
 
   - Accept the defaults for the requirements of the program (or modify according to your environment)
 
   - On the Environment page, ensure you use a combination of settings that allows the user to interact with the application. Failure to do so will result in the application installing silently:
 
-![](images/image24.png)
+![](./img/image24.png)
 
   - Accept the defaults for the rest of the program (or modify according to your environment)
 
   - Create a new Advertisement for the Package and set your target collection accordingly:
 
-![](images/image25.png)
+![](./img/image25.png)
 
   - Set a recurring schedule for the Mandatory Assignment. This dictates how frequently the application should attempt to install. Additionally, ensure that “Rerun if failed previous attempt” is enabled. These settings are required when using the deferral system and ensure that if a user defers the install, the install will retry after the specified interval:
 
-![](images/image26.png)
+![](./img/image26.png)
 
   - When prompted with the following dialog box, select Yes:
 
-![](images/image27.png)
+![](./img/image27.png)
 
   - Accept the defaults for the rest of the advertisement (or modify according to your environment). The deployment should start on your target machines shortly.

src/guide/Example-AdobeReaderSCCM2012AppModel.md

@@ -6,33 +6,33 @@
 
   - Create a new Application and manually specify the application information:
 
-![](images/image28.png)
+![](./img/image28.png)
 
   - Populate the application details accordingly:
 
-![](images/image29.png)
+![](./img/image29.png)
 
   - Populate the application catalog details if required
 
   - Add a new Deployment Type and manually specify the deployment type information:
 
-![](images/image30.png)
+![](./img/image30.png)
 
   - Populate the deployment type details accordingly:
 
-![](images/image31.png)
+![](./img/image31.png)
 
   - Set the content location. Additionally, set the Install and Uninstall programs accordingly. They should be *Deploy-Application.exe -DeploymentType "Install"* and *Deploy-Application.exe -DeploymentType "Uninstall"* respectively:
 
-![](images/image32.png)
+![](./img/image32.png)
 
   - Create a new detection rule. Specify the base MSI product code and modify the Version to be the same as the final version after all patches are installed:
 
-![](images/image33.png)
+![](./img/image33.png)
 
   - On the User Experience page, ensure you use a combination of settings that allows the user to interact with the application. Failure to do so will result in the application installing silently:
 
-![](images/image34.png)
+![](./img/image34.png)
 
   - Leave the requirements page blank (or modify according to your environment)
 
@@ -42,28 +42,28 @@
 
   - Deploy the Application:
 
-![](images/image35.png)
+![](./img/image35.png)
 
   - Select the relevant Distribution Points:
 
-![](images/image36.png)
+![](./img/image36.png)
 
   - Configure deployment settings according to whether it should be a mandatory or app catalogue based deployment:
 
-![](images/image37.png)
+![](./img/image37.png)
 
   - Specify the deployment schedule:
 
-![](images/image38.png)
+![](./img/image38.png)
 
   - Specify User notification settings. In order to prevent excess noise, we recommend only showing notifications for computer restarts:
 
-![](images/image39.png)
+![](./img/image39.png)
 
   - Accept the defaults for the rest of the Deployment (or modify according to your environment)
 
 ### Important Note regarding deferrals
 
 The SCCM 2012 Application Model does not have the flexibility to schedule Mandatory Assignments on a recurring schedule like SCCM 2007 or SCCM 2012 packages do. Instead, this is determined by the frequency of Software Deployment evaluation cycle in the SCCM Agent Custom Settings. You can modify this to reduce the time from the default of once a day, however this may increase the load on your SCCM servers and clients, and is not configurable on a per application basis:
 
-![](images/image40.png)
+![](./img/image40.png)

src/guide/Toolkit-Components.md

@@ -11,42 +11,42 @@
 
 If the block execution option is enabled (see Show-InstallationWelcome function), the user will be prompted that they cannot launch the specified application(s) while the installation is in progress. The application will be unblocked again once the installation has completed.
 
-![](images/image10.png)
+![](./img/image10.png)
 
 ## Disk Space Requirements
 
 If the CheckDiskSpace parameter is used with the Show-InstallationWelcome function and the disk space requirements are not met, the following prompt will be displayed and the installation will not proceed.
 
-![](images/image11.png)
+![](./img/image11.png)
 
 ## Custom Installation Prompt
 
 A custom prompt with the toolkit branding can be used to display messages and interact with the user using the “Show-InstallationPrompt” function. The title and text is customizable and up to 3 customizable buttons can be included on the prompt as well as optional system icons, e.g.
 
-![](images/image12.png)
+![](./img/image12.png)
 
 Additionally, the prompt can be displayed asynchronously, e.g. to display a message at the end of the installation but allow the installation to return the exit code to the parent process without waiting for the user to respond to the message.
 
-![](images/image13.png)
+![](./img/image13.png)
 
 - [Installation Restart Prompt](installation-restart-prompt)
 ## Balloon tip notifications
 
 Balloon tip notifications are displayed in the system tray automatically at the beginning and end of the installation. These can be turned off in the XML configuration.
 
-![](images/image15.png)
+![](./img/image15.png)
 
-![](images/image16.png)
+![](./img/image16.png)
 
-![](images/image17.png)
+![](./img/image17.png)
 
 ## Custom Dialog box
 
 A generic dialog box to display custom messages to the user without the toolkit branding using the function “Show-DialogBox”. This can be customized with different system icons and buttons.
 
-![](images/image18.png)
+![](./img/image18.png)
 
-![](images/image19.png)
+![](./img/image19.png)
 
 ## Logging