docs update

6-ide-integrations/integration-via-marketplace/vscode/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+ and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+ overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+ advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+ address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+nathanw9722@gmail.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

6-ide-integrations/integration-via-marketplace/vscode/README.md

@@ -8,13 +8,19 @@ This extension enables key features from BMC Software's Control-M product that w
 
 > Tip: No prior experience with Control-M is required to write jobs.
 
+<br/>
+<br/>
+
 ## Supported file types or languages
 | language | extension | description |
 | ----------- | ------------------------ | --------------------------- |
 | JSON | .json | job-as-code script files |
 | Python | .py | job-as-code python files |
 
 
+<br/>
+<br/>
+
 ## Features
 - Use pre-built code snippets while writing and debugging your Control-M Workflow Job-As-Code scripts. 
 - **build**, **run** and **deploy** the Job-As-Code scripts direclty out of ***Visual Studio Code*** or ***Visual Studio Code Server*** 
@@ -24,6 +30,9 @@ This extension enables key features from BMC Software's Control-M product that w
 
 
 
+<br/>
+<br/>
+
 ## Install the Control-M Visual Studio Code extension
 The Control-M extension can be found in the Visual Studio Code Extension Marketplace. More information on adding extensions to Visual Studio Code can be found [here](https://code.visualstudio.com/docs/introvideos/extend).
 
@@ -36,6 +45,9 @@ As in any Visual Studio Code Extension you have several options to install:
 code --install-extension job-as-code-*.vsix
 ```
 
+<br/>
+<br/>
+
 ## Getting Started & Installing the Control-M Automation CLI
 Control-M Automation API is a set of programmatic interfaces that give developers and DevOps engineers access to the capabilities of Control-M within the modern application release process. Job flows and related configuration objects are built in JSON and managed together with other application artifacts in any source code management solution, such as GIT. This approach enables capabilities such as sophisticated scheduling, flow control, and SLA management to be built in right from inception and used during the running of batch applications as they are automatically deployed in dev, test, and production environments. Click on the image to watch the introduction video:
 
@@ -59,18 +71,26 @@ In general these are the two steps: ***download*** **ctm-cli.tgz**, then run ***
 npm -g install ctm-cli.tgz
 
 
+<br/>
+<br/>
+
 ## Platform Support
 
 The extension _should_ work anywhere VS Code itself is [supported]. 
 
 Read the [Start using a Jobs-as-Code approach to build workflows with Control-M](https://controlm.github.io/)
 to get more details on how to use the extension on these platforms.
 
-https://docs.bmc.com/docs/automation-api/monthly/tutorials-1064010699.html
+
+<br/>
+<br/>
+
 ## API Support
 
 Control-M Automation API [Swagger](http://aapi-swagger-doc.s3-website-us-west-2.amazonaws.com/swagger.json) builds the basis of the job-as-code integration and code snippets.
 
+<br/>
+<br/>
 
 ### Control-M objects in JSON code
 
@@ -81,6 +101,8 @@ Control-M Automation API enables you to manage jobs through JSON code. See [Code
 
 The Control-M Automation API allows you to automate and work interactively with Control-M. Services are groups of API commands available via either a CLI (Command Line Interface) or as REST API commands. Using the services, you can build job definitions to test whether they are valid, test-run a job to debug job definitions , combine multiple definition files into a package, deploy job definitions and packages to Control-M, provision a Control-M/Agent, manage environments, and more. Click on the link below for more information. 
 
+<br/>
+<br/>
 
 | Name | description | 
 | ----------- | ------------------------ |
@@ -98,7 +120,8 @@ The Control-M Automation API allows you to automate and work interactively with
 | [session]() | The Session service allows you to log in and log out of Control-M and receive a token that can be reused in subsequent requests. | 
 | usage | Run the usage service in order to get a usage report. Supported only in Control-M SaaS | 
 
-
+<br/>
+<br/>
 
 ## Usage / Tutorials
 
@@ -107,10 +130,16 @@ To get you started, BMC provides you with a group of tutorials to introduce you
 Create a new *.json or *.py file. Enter "jac." to utilize provided code snippets.
 **Right-Mouse-Click* to invoke the Visual Studio Code conext menus to activate the Control-M AAPI commands.
 
+<br/>
+<br/>
+
 ## License
 
 Please see the [BMC License](https://github.com/controlm/automation-api-community-solutions/license.html) file for details on the project.
 
+<br/>
+<br/>
+
 ## Release Notes
 
 ### 0.1.*