updates to layout

Bob Wall · Bob Wall · commit d4e76ae304f3 · 2023-01-22T18:39:16.000-05:00
diff --git a/docs/index.md b/docs/index.md
@@ -0,0 +1,10 @@
+# Overview
+
+Commandeer is a desktop IDE used to manage AWS, LocalStack, and Docker. It gives you to work in a clean UI to manage many cloud services. Commandeer is a bottom up solution, meaning you can go down to the granular level for everything. For example, you can search for a file in S3, look up a record in DynamoDB, PostgreSQL, or Athena, or see CloudWatch Logs for a Lambda Invocation that you just invoked.
+
+While other tools take a top down approach where you can see high level pieces of information, but once you actually try to manage your system, you quickly realize it is not for you. What differentiates other IDE's from Commandeer is that we provide a true interface into your services. Most IDE's have extensions that you can supposedly see things like Lambda with, but once you start to work with them, you will notice that they don't have all the complex interconnections between services that are crucial to managing your system.
+
+Visualize your lambda connections and the interactions between them. Advanced event runners for SQS, SNS, API Gateway, DynamoDB Streams, S3 files and more, let you actually run the event, and view the triggered Lambda's invocation logs. If you are connected to LocalStack you can also view the Docker Containers logs. You can also invoke a Lambda directly to test your code. This is one of the most important aspects of Commandeer. Rather than having to deal with running these things on the Web or in the CLI, you can now easily do them in an IDE.
+
+
+
diff --git a/docs/localstack/index.md b/docs/localstack/index.md
@@ -1 +1,23 @@
-# LocalStack with Commandeer
+# LocalStack
+
+LocalStack is one of our favorite tools for simulating the AWS environment. It is a mock environment that mimics many of the most popular AWS services. You are able to stand up many different services, such as S3 or Dynamo, and have complete access to the files or NoSQL data exactly is it would appear on AWS.
+
+Why does this matter? Because running things locally is great for many reasons. It is much faster and it saves CPU costs on AWS for starters. We feel it also allows you to get a better feel for how your system is actually operating. You can also test outages of certain services much easier than trying to do it directly on AWS.
+
+## Commandeer Key Features
+
+- Get LocalStack running instantly. Simply download Commandeer, open up the LocalStack dashboard, and hit the start button, and it is running.
+- Start/Stop all or individual LocalStack services.
+- See what LocalStack ports are running (DynamoDB, IAM, Lambda, S3, SNS, SQS, and more).
+- View your local S3 data.
+- View your local DynamoDB data.
+- View your local Lambdas.
+- See and manage all your local AWS infrastructure for supported AWS services like (SNS, SQS, CloudWatch Logs, CloudWatch Rules, CloudFormation, IAM, ApiGateway, and more).
+- Update the URLs for your services.
+- Manage the LocalStack resources on a remote LocalStack server.
+- Customize LocalStack using the environment variables.
+
+## Helpful Links
+
+- [LocalStack Github Page](https://github.com/localstack/localstack "LocalStack 💻 is a cloud service emulator that runs in a single container on your laptop or in your CI environment.").
+- [LocalStack Home Page](https://localstack.cloud/ "A fully functional local cloud stack. Develop and test your cloud and serverless apps offline!").
diff --git a/docs/localstack/setting-up-localstack.md b/docs/localstack/setting-up-localstack.md
@@ -0,0 +1 @@
+# Setting up Localstack
