Merge pull request #11 from Exlint/EXL-37

docs: 📘 Updated docs for go command

Author: tal-rofe

docs/setup/cli-argument/index.mdx

@@ -11,12 +11,24 @@ import styles from './styles.module.css';
 
 Exlint's command-line interface (CLI) allows you to run Exlint on your codebase from the command line. The following arguments are available:
 
+#### Usage commands:
+
 `auth`: This argument is used to authenticate your Exlint account. You will be prompted to enter your API key.
 
 `use`: This argument is used to specify the group you want to run Exlint on using its unique ID. The group ID can be found on the Exlint dashboard.
 
 `run`: This argument is used to run Exlint on your codebase. The `--fix` or `-f` flag can be used to automatically fix any issues found by Exlint.
 
+#### Base commands
+
+`-v`, `--version`: This argument is used to check your Exlint CLI version.
+
+`--env-info`: This argument is used to print system and project information.
+
+#### Debugging
+
+Usage commands can be debugged using the `--debug` flag.
+
 #### Examples:
 
 To authenticate your Exlint account, you can use the following command:

docs/setup/cli-output/index.mdx

@@ -17,16 +17,15 @@ The output of the command will display the results of each policy in the group,
 For example, when using the run command with a Group that includes the `Prettier` and `ESLint` policies, the output will show the results for each policy in the group.
 Here is an example of what the output may look like:
 
-```bash title="Exlint File list"
---- Prettier output ---
+```bash title="Terminal"
+──────────────────────────── Prettier output ────────────────────────────
 
 Checking formatting...
-[warn] .vscode/settings.json
 [warn] index.js
-[warn] Code style issues found in 2 files. Forgot to run Prettier?
+[warn] Code style issues found in 1 files. Forgot to run Prettier?
 
 
---- ESLint output ---
+──────────────────────────── ESLint output ────────────────────────────
 
 /Users/talrofe/Desktop/Exlint/index.js
 4:1  error  File has too many lines (4). Maximum allowed is 3  max-lines

docs/setup/policies/index.mdx

@@ -10,13 +10,15 @@ import styles from './styles.module.css';
 A Policy is a way to apply a set of rules and configurations to your code using a specific library.
 This document will guide you through the process of creating and using a Policy in Exlint.
 
+<!---
 ## Policy in a nutshell
 
 1. In the [Exlint Dashboard](https://app.exlint.io), select the `Group` you want to add a new Policy to.
 2. When creating a new Policy, select the open-source library you want to use for your Policy.
 3. Apply the appropriate `configurations` for your Policy, following the library guidelines.
 4. If the library has `rules` that can be applied, configure them as needed.
 5. Run the Policy's Group to get results! ([Running a Group](/setup/groups#running-a-group))
+-->
 
 ## Configuring a Policy
 
@@ -35,6 +37,9 @@ For example, Prettier has no `Rules`, and all configuration is `Global`.
 ### Global Policy configurations
 
 When configuring a global configuration, you have two options:
+:::tip
+Both options will produce the same result, it's just a matter of preference and ease of use.
+:::
 
 1.  `Code-based configuration`: This option allows you to input configuration using code, like you would on your IDE.
     You can set the configurations using the library's specific syntax and guidelines.
@@ -50,10 +55,6 @@ When configuring a global configuration, you have two options:
     This feature is currently under maintanance and not available.
     :::
 
-:::tip
-Both options will produce the same result, it's just a matter of preference and ease of use.
-:::
-
 ### File list
 
 The `File list` section allows you to specify which files the policy should run on.

docs/welcome/getting-started/index.mdx

@@ -29,18 +29,9 @@ Exlint does not require access to code, Git provider, or any other sensitive inf
 
 ---
 
-## Using Exlint
-
-### 1. Centralize your compliance in Exlint
-
-Get started by creating an account at [app.exlint.io](https://app.exlint.io).
-
-Create your first Exlint Group, where can organize and manage different policies, and then run them as a group.
-These policies are used to check your code for compliance with industry standards and best practices.
+## Quickstart
 
-Read more about configuring groups [here](setup/groups).
-
-### 2. Install the Exlint CLI
+### 1. Install the Exlint CLI
 
 To install the Exlint CLI with `npm`, run one of the following commands:
 
@@ -57,27 +48,50 @@ To install the Exlint CLI with `npm`, run one of the following commands:
   </TabItem>
 </Tabs>
 
-### 3. Connect your CLI to your Exlint Dashboard
+### 2. 🚀 Run your first compliance run
+
+Use the `go` command to quickly setup a recommended compliance and customize it in our Dashboard.
+
+```bash
+exlint go
+```
+
+Exlint will ask you for you project languages, and create a recommended compliance based on how we code at Exlint.
+
+:::tip
+Use the go command to easily get started enforcing best practices with Exlint.
+You can adjust and customize the compliance for your needs, or create a new one from scratch!
+:::
+
+## Using Exlint
+
+### 1. Connect your CLI to your Exlint Dashboard
 
 Use the following command to authenticate with your Exlint account:
 
-    exlint auth
+```bash
+exlint auth
+```
 
-### 4. Run an Exlint Group scan on your repository
+### 2. Run an Exlint Group scan on your repository
 
 To use a group, copy its identifier and use it with the `use` command in the Exlint CLI.
 This will adjust your IDE and install necessary extensions and libraries.
 
-    exlint use <group_id>
+```bash
+exlint use <group_id>
+```
 
 Run a group scan against your code using the `run` command:
 
-    exlint run [options]
+```bash
+exlint run [options]
+```
 
 You can also run the command with `--fix` or `-f` option.
 Providing this option will make Exlint try to automatically fix code issues.
 
-### 5. Integrate Exlint into your CI
+### 3. Integrate Exlint into your CI
 
 Keep your CI aligned with your stardartized Exlint compliance using our [GitHub Action](/ci/github-action).
 Check out our [roadmap](https://github.com/orgs/Exlint/projects/3) to see which other integrations we're planning to support (or tell us if we're missing the one you like!)