7 files changed, 5 insertions(+), 6 deletions(-)

M README.md
D badge/project_status.svg
R example_package/example.ps1 => contrib/examplepackage/example.ps1
R example_package/package.xml => contrib/examplepackage/package.xml
R example_package/powerpkg.ps1 => contrib/examplepackage/powerpkg.ps1
R readme/example_verifyinstall_program.gif => img/example_verifyinstall_program.gif
R readme/header.gif => img/header.gif

@@ 1,6 1,6 @@
 # powerpkg
 
-![](/readme/header.gif)
+![](/img/header.gif)
 
 `powerpkg` is a Windows-exclusive software deployment facilitator for enterprise environments, serving as an installation (or uninstallation) script for individual software packages; with optional actions, conditions and exceptions as core features. It is deliberately designed to use a [configuration file](#package-file-packagexml) model, ensuring a low learning curve, code standardization among every instance, and easy software updates (when available).
 


@@ 41,7 41,7 @@ To begin testing powerpkg:
 
 **(2)**: Invoke `powerpkg.ps1`:
 ```shell
-powershell.exe -NoProfile -ExecutionPolicy Unrestricted -File "example_package\powerpkg.ps1"
+powershell.exe -NoProfile -ExecutionPolicy Unrestricted -File "contrib\examplepackage\powerpkg.ps1"
 ```
 
 **(3)**: *And that's it!*


@@ 210,7 210,7 @@ Which, with a bit of customization, can become the following example:
 </Package>
 ```
 
-To further familiarize yourself with powerpkg (and especially the above examples), continue reading the [Script Configuration](#script-configuration-configuration) and [Task Entry](#task-entry-taskentry) segments of this README. Examining the contents of the `\example_package` directory is also encouraged.
+To further familiarize yourself with powerpkg (and especially the above examples), continue reading the [Script Configuration](#script-configuration-configuration) and [Task Entry](#task-entry-taskentry) segments of this README. Examining the contents of the `\contrib\examplepackage` directory is also encouraged.
 
 ### Script Configuration (`<Configuration>`)
 


@@ 508,7 508,7 @@ To utilize the **`[Program]`** subparameter, you can verify the existence of a:
 
   - Open the `Programs and Features` applet of the Windows Control Panel, and retrieve the name of the installed program you wish to verify the existence of:
 
-    ![Programs and Features](/readme/example_verifyinstall_program.gif)
+    ![Programs and Features](/img/example_verifyinstall_program.gif)
 
   - Within PowerShell, enter the following command:
 


@@ 546,7 546,7 @@ To utilize the **`[Program]`** subparameter, you can verify the existence of a:
 
   - Open the `Programs and Features` applet of the Windows Control Panel, and retrieve the name of the installed program you wish to verify the existence of:
 
-    ![Programs and Features](/readme/example_verifyinstall_program.gif)
+    ![Programs and Features](/img/example_verifyinstall_program.gif)
 
   - Then, specify a program name in this fashion:
 

@@ 1,1 0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="134" height="20"><linearGradient id="b" x2="0" y2="100%"><stop offset="0" stop-color="#bbb" stop-opacity=".1"/><stop offset="1" stop-opacity=".1"/></linearGradient><clipPath id="a"><rect width="134" height="20" rx="3" fill="#fff"/></clipPath><g clip-path="url(#a)"><path fill="#555" d="M0 0h87v20H0z"/><path fill="#e05d44" d="M87 0h47v20H87z"/><path fill="url(#b)" d="M0 0h134v20H0z"/></g><g fill="#fff" text-anchor="middle" font-family="DejaVu Sans,Verdana,Geneva,sans-serif" font-size="110"> <text x="445" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="770">project status</text><text x="445" y="140" transform="scale(.1)" textLength="770">project status</text><text x="1095" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="370">retired</text><text x="1095" y="140" transform="scale(.1)" textLength="370">retired</text></g> </svg>>
\ No newline at end of file