Add blog to docs (#484)

* Adding social card infrastructure
* Upgrades doc project to .NET 6
* Adds Playwright
* Changes the console to a web project for Playwright
* Adds social card template
* Added blog content
* Parallelized social image processing
* Updating CI to use .NET 6 for docs build

docs/input/cli/commandApp.md

@@ -1,5 +1,6 @@
 Title: CommandApp
 Order: 2
+Description: "**CommandApp** is the entry point for a *Spectre.Console.Cli* command line application. It is used to configure the settings and commands used for execution of the application."
 ---
 
 `CommandApp` is the entry point for a `Spectre.Console.Cli` command line application. It is used to configure the settings and commands used for execution of the application. Most `Spectre.Console.Cli` applications will need to specify a custom configuration using the `Configure` method.

docs/input/cli/commands.md

@@ -1,5 +1,6 @@
 Title: Creating Commands
 Order: 6
+Description: "How to create commands for *Spectre.Console.Cli*"
 ---
 
 Commands in `Spectre.Console.Cli` are defined by creating a class that inherits from either `Spectre.Console.Cli.Command<TSettings>` or `Spectre.Console.Cli.AsyncCommand<TSettings>`. `Command<TSettings>` must implement an `Execute` method that returns an int where as `AsyncCommand<TSettings>` must implement `ExecuteAsync`  returning `Task<int>`.

docs/input/cli/composing.md

@@ -1,6 +1,8 @@
 Title: Composing Commands
 RedirectFrom: introduction
 Order: 8
+Description: "The underlying philosophy behind *Spectre.Console.Cli* is to rely on the .NET type system to
+declare the commands, but tie everything together via composition."
 ---
 
 The underlying philosophy behind `Spectre.Console.Cli` is to rely on the .NET type system to

docs/input/cli/getting-started.md

@@ -1,5 +1,6 @@
 Title: Getting Started
 Order: 1
+Description: "How to get started using *Spectre.Console.Cli* to write a modern console application that follows industry conventions for command line parsing."
 ---
 
 `Spectre.Console.Cli` is a modern library for parsing command line arguments. While it's extremely

docs/input/cli/index.cshtml

@@ -1,5 +1,6 @@
 Title: Spectre.Console.Cli
-Order: 10
+Order: 80
+Description: "The command line interface for the *Spectre.Console* project."
 ---
 
 <p>Spectre.Console.Cli is a modern library for parsing command line arguments. While it's extremely opinionated in what it does, it tries to follow established industry conventions, and draws its inspiration from applications you use everyday.</p>

docs/input/cli/introduction.md

@@ -1,5 +1,8 @@
 Title: Introduction
 Order: 1
+Description: "*Spectre.Console.Cli* is a modern library for parsing command line arguments. While it's extremely
+opinionated in what it does, it tries to follow established industry conventions, and draws
+its inspiration from applications you use everyday."
 ---
 
 `Spectre.Console.Cli` is a modern library for parsing command line arguments. While it's extremely

docs/input/cli/migration.md

@@ -1,5 +1,6 @@
 Title: Migrate from Spectre.Cli
 Order: 10
+Description: "Migrating from *Specte.Cli* to *Spectre.Console.Cli*"
 ---
 
 The functionality in `Spectre.Cli` has been moved into the `Spectre.Console`

docs/input/cli/settings.md

@@ -1,5 +1,6 @@
 Title: Specifying Settings
 Order: 5
+Description: "How to define command line argument settings for your *Spectre.Console.Cli* Commands"
 ---
 
 Settings for `Spectre.Console.Cli` commands are defined via classes that inherit from `CommandSettings`. Attributes are used to indicate how the parser interprets the command line arguments and create a runtime instance of the settings to be used.