Update Getting Started Docs: Calling Analyzers w/ FAKE

docs/content/Dual Analyzer.fsx

@@ -1,8 +1,8 @@
 (**
 ---
 category: end-users
-categoryindex: 1
-index: 3
+categoryindex: 2
+index: 2
 ---
 
 # Writing an analyzer for both console and editor

docs/content/Getting Started Writing.fsx

@@ -1,8 +1,8 @@
 (**
 ---
 category: end-users
-categoryindex: 1
-index: 2
+categoryindex: 2
+index: 1
 ---
 
 # Getting started writing an analyzer

docs/content/Programmatic access.fsx

@@ -1,8 +1,8 @@
 (**
 ---
 category: end-users
-categoryindex: 1
-index: 4
+categoryindex: 2
+index: 3
 ---
 
 # Programmatically running an analyzer

docs/content/Running during CI.md

@@ -1,7 +1,7 @@
 ---
 category: end-users
-categoryindex: 1
-index: 6
+categoryindex: 2
+index: 5
 ---
 
 # Running analyzers during continuous integration

docs/content/Unit Testing.fsx

@@ -1,8 +1,8 @@
 (**
 ---
 category: end-users
-categoryindex: 1
-index: 5
+categoryindex: 2
+index: 4
 ---
 
 # Unit testing an analyzer

docs/content/getting-started/CLI.md

@@ -0,0 +1,33 @@
+---
+category: getting-started
+categoryindex: 1
+index: 3
+---
+
+# Command Line Arguments
+
+## Example Command
+
+When running the CLI tool from the command line, the bare minimum you need to provide is the path to the project file(s) you want to analyze.
+
+```shell
+dotnet fsharp-analyzers --project ./YourProject.fsproj
+```
+
+An optional argument you may need to provide is `--analyzers-path`. This is the path to the directory containing the analyzer DLLs. 
+
+```shell
+dotnet fsharp-analyzers --project ./YourProject.fsproj --analyzers-path ./path/to/analyzers/directory
+```
+
+⚠️ If you don't provide this argument, it will default to `packages/analyzers`.
+
+## Viewing Additional Commands
+
+You can view the full list of commands available by running:
+
+```shell
+dotnet fsharp-analyzers --help
+```
+
+[Next]({{fsdocs-next-page-link}})

docs/content/getting-started/Configuring for IDE.md

@@ -0,0 +1,26 @@
+---
+category: getting-started
+categoryindex: 1
+index: 2
+---
+
+# Configuring for the IDE
+
+## Visual Studio Code
+
+In order to configure analyzers for VSCode, you will need to update your project's `.vscode/settings.json` file or your user settings. You should only need the following settings:
+
+```json
+{
+  "FSharp.enableAnalyzers": true,
+  "FSharp.analyzersPath": ["packages/analyzers"]
+}
+```
+
+📓 Note: The path in `FSharp.analyzersPath` above is currently pointing to the path we set up in the Paket example on the [installation page]({{fsdocs-previous-page-link}}).
+
+After saving your new settings, make sure to restart VSCode. Once VSCode restarts, you should be able to test and see if the analyzers are working by opening a F# file in your workspace and entering the following code
+
+![Analyzers Inline Warning](../../images/analyzers-inline-warning.png)
+
+[Next]({{fsdocs-next-page-link}})

docs/content/getting-started/Installing Analyzers.md

@@ -0,0 +1,50 @@
+---
+category: getting-started
+categoryindex: 1
+index: 1
+---
+# Installation
+
+## Installing the Tool
+
+A dotnet CLI tool, called [fsharp-analyzers](https://github.com/ionide/FSharp.Analyzers.SDK/), is used to run analyzers outside the context of an IDE. Add it to your tool-manifest with:
+
+```shell
+dotnet tool install fsharp-analyzers
+```
+
+## Installing Analyzers
+
+### Suggested Packages
+
+1. [Ionide Analyzers](https://github.com/ionide/FSharp.Analyzers.SDK/)
+2. [G-Research Analyzers](https://github.com/G-Research/fsharp-analyzers/)
+
+### Nuget
+
+If you are using Nuget as your package manager, add the `PackageReference` pointing to your favorite analyzers to the `.fsproj` file of the project you want to analyze.
+
+```xml
+<PackageReference Include="G-Research.FSharp.Analyzers" Version="0.12.1">
+    <PrivateAssets>all</PrivateAssets>
+    <IncludeAssets>analyzers</IncludeAssets>
+</PackageReference>
+<PackageReference Include="Ionide.Analyzers" Version="0.28.0">
+    <PrivateAssets>all</PrivateAssets>
+    <IncludeAssets>analyzers</IncludeAssets>
+</PackageReference>
+```
+
+### Paket
+
+If you are using Paket as your package manager, add the package to your `paket.dependencies` file. The example below uses a paket group, but it is not required.
+
+```paket
+group analyzers
+    source https://api.nuget.org/v3/index.json
+
+    nuget Ionide.Analyzers
+    nuget G-Research.FSharp.Analyzers
+```
+
+[Next]({{fsdocs-next-page-link}})