Fix/quickstart (#476)

* docs: inserting cloudpods sample link
* docs: added link to relevant quickstart sample
* dev: added devcontainer setup for VSCode and workspace extensions

Author: SimonWallner

.devcontainer/devcontainer.json

@@ -0,0 +1,34 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
+{
+	"name": "Debian",
+	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
+	"image": "mcr.microsoft.com/devcontainers/base:bullseye",
+	"features": {
+		"ghcr.io/devcontainers/features/go:1": {},
+		"ghcr.io/devcontainers/features/hugo:1": {
+			"extended": true
+		}
+	},
+	"customizations": {
+		"vscode": {
+			"extensions": [
+				"budparr.language-hugo-vscode",
+				"rusnasonov.vscode-hugo",
+				"streetsidesoftware.code-spell-checker"
+			]
+		}
+	}
+
+	// Features to add to the dev container. More info: https://containers.dev/features.
+	// "features": {},
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Configure tool-specific properties.
+	// "customizations": {},
+
+	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
+	// "remoteUser": "root"
+}

.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+	"recommendations": [
+		"budparr.language-hugo-vscode",
+		"rusnasonov.vscode-hugo",
+		"streetsidesoftware.code-spell-checker"
+	]
+}

.vscode/settings.json

@@ -0,0 +1,6 @@
+{
+	"cSpell.words": [
+		"awslocal",
+		"quickstart"
+	]
+}

content/en/getting-started/quickstart.md

@@ -12,14 +12,16 @@ This quickstart guide will walk you through starting LocalStack on your local ma
 
 {{< alert title="Note" >}}
 The quickest way to experiment with LocalStack is to use one of our [LocalStack quickstart samples](https://app.localstack.cloud/quickstart) to deploy a thumbnail creator, request worker application, or an asynchronous microservice with tracing/debugging. The quickstart samples will automatically connect to your running LocalStack container on your local machine and run the applications.
+
+To quickly see the outcome of this quickstart guide, try deploying the [Request Worker](https://app.localstack.cloud/quickstart-cloudformation) sample from our website.
 {{< /alert >}}
 
 ## Start your LocalStack container
 
 After installing LocalStack and configuring your API key, let us start LocalStack. To run our sample AWS application, we will start LocalStack using the `localstack` CLI.
 
 {{< command >}}
-$ localstack start 
+$ localstack start
 {{< / command >}}
 
 You can optionally run your LocalStack container in background mode by adding the `-d` flag to the `localstack start` command.

content/en/user-guide/tools/cloud-pods/_index.md

@@ -9,14 +9,18 @@ aliases:
 ---
 
 {{< alert title="Note">}}
-Please note that cloud pods may not be compatibile across different versions of LocalStack.
+Please note that cloud pods may not be compatible across different versions of LocalStack.
 We are actively working on addressing this limitation in the upcoming releases.
 {{< /alert >}}
 
 Cloud Pods are a mechanism that allows you to take a snapshot of the state in your current LocalStack instance, persist it to a storage backend, and easily share it with your team members.
 
 ![Persistence versus Cloud Pods](pods-persistence.png)
 
+{{< alert title="Demo">}}
+To quickly see cloud pods in action, we prepared a small sample application that uses cloud pods to inject its state into a running LocalStack container. [Cloud Pod Thumbnail Sample App](https://app.localstack.cloud/quickstart/demo4)
+{{< /alert >}}
+
 While the [Persistence]({{< ref "persistence-mechanism" >}}) feature ensures that the service state survives container restarts, Cloud Pods go beyond and allow more fine-grained control over your state.
 
 Instead of simply restoring a state when restarting LocalStack, Cloud Pods allow you to take snapshots of your local instance (with the `save` command) and inject such snapshots into a running instance (with the `load` command) without requiring a restart.