Updated documentation

Author: PowerCommands

Docs/Job.md

@@ -0,0 +1,25 @@
+# Run your command as a job
+A PowerCommands application can be started with arguments from the commandline which is usefull when you want to use your PowerCommands implementation to perform something as a automated job.
+
+The code below shos a dummie example of how you design your Command to run as an automatated task, notice the **return Quit()** at the end of the Run() method, that will trigger the program to quit the application. 
+
+![Alt text](images/job.png?raw=true "job")
+
+You just startup your PowerCommands application from with the parameter "job", like this:
+```
+"powercommands.exe job"
+```
+Your PowerCommands application may of course have so other name and your command could have Input parameters that will be passed on from the command line like this:
+```
+"powercommands.exe job argument1"
+```
+
+Read more about:
+
+[Design your Command](Design_command.md)
+
+[Options](Options.md)
+
+[PowerCommands Attribute](PowerCommandAttribute.md)
+
+[Back to start](https://github.com/PowerCommands/PowerCommands2022/blob/main/Docs/README.md)

Docs/PowerCommandDesignAttribute.md

@@ -46,7 +46,7 @@ Describe your quotes, separate them with | use // to display a commented line ov
 Suggestion will be added to the autocomplete functionallity so the user could use tab to cycle trough the commands and commands with a suggested argument.
 ### Options
 Describe your options, separate them with | use // to display a commented line over the actual option, all options that are described will also be used by the autocomplete functionallity to help the user find the right option.
-Read more about [options](options.md).
+Read more about [options](Options.md).
 ### secrets
 Describe your secrets that the commands needs, you probably want to declare a secret as required with **!** character, in the sample above secret **cnDatabase** is marked as required.
 ```

Docs/Secrets.md

@@ -3,7 +3,7 @@
 ## Configure your environment to use Encryption/Decryption and Secrets functionallity
 ## Good to know
 Secret is initialized the fist time you startup a new power command project on your machine, the same keys for encryption/decryption is used by all your PowerCommands based applications on the same machine.
-If you setup PowerCommands on a diffrent machine, a new key for encryption/decryption will be used, meaning you have to create the secrets again on that machine. But you can move the keys manually, but I do not think that you should do that.
+If you setup PowerCommands on a diffrent machine, a new key for encryption/decryption will be created for that machine. It is possible to manually move both the key and the encrypted secrets from one machine to another, but it is not recommended and therefore not documented.
 ## Use the secrets built in functionallity 
 Create secret with built in commands named secret, like this:
 ```

Docs/images/job.png

@@ -4,23 +4,18 @@ You could se PowerCommands as an easy Create your CLI applikation starter kit. I
 [Follow progress on twitter](https://twitter.com/PowerCommands) <img src="https://github.com/PowerCommands/PowerCommands2022/blob/main/Docs/images/Twitter.png?raw=true" alt="drawing" width="20"/>
 
  ### The core components offering this to your custom PowerCommands
- - Logging (using Microsoft.Extensions.Logging.ILogger)
- - Process log (using the standard logger with tags to track a process)
+ - Command completion, with history, suggestions, options and support for Path/File navigation and color highlightning when typing a valid command
+ - Secret handling to protect sensitive information like password or authentication tokens in the configuration file. 
  - Configuration with YAML (built to be very easy to extend)
- - Display your POCO:s easy with a nice Console Table display output
- - Simple to write test rules with attribute
+ - Logging (using Microsoft.Extensions.Logging.ILogger)
+ - Built in help system with the use of attributes
+ - Run as job
  - Validation rules with attribute
- - Diagnostic 
- - Secret handling to protect sensitive information like password or authentication tokens in the configuration file.
- - Command completion, with history, suggestions, options and support for Path/File navigation and color highlightning when typing a valid command
+ - Diagnostic  
  - Progressbar
- - Download files
- - Password prompt
- - Run as job
- - Zip with attributes like checksum, filecount and file size
- - Describe your commands with code examples using attributes. 
+ - Dialog service (with password prompting) 
 
- ![Alt text](Docs/images/startup.png?raw=true "Test result")
+ ![Alt text](Docs/images/startup.png?raw=true "Startup")
 
  ## Start your journey
 [Create a new VS Solution](Docs/Create_new_%20project.md)
@@ -42,6 +37,9 @@ You could se PowerCommands as an easy Create your CLI applikation starter kit. I
 
 [Output to the Console guidline](Docs/ConsoleOutput.md)
 
+## Automation
+[Run your command as job](Docs/Job.md)
+
 ## Core framework
 [PowerCommandsRuntime](Docs/PowerCommandsRuntime.md)