From 54b2d6a239a7b15ee98bc59d36092ec4c8394147 Mon Sep 17 00:00:00 2001
From: Todd Baert <todd.baert@dynatrace.com>
Date: Fri, 22 Sep 2023 10:25:07 -0400
Subject: [PATCH] review feedback

Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
---
 web-docs/deployment.md | 9 +++++++++
 web-docs/intro.md      | 3 +--
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/web-docs/deployment.md b/web-docs/deployment.md
index e69de29bb..24988d17f 100644
--- a/web-docs/deployment.md
+++ b/web-docs/deployment.md
@@ -0,0 +1,9 @@
+# Docker
+
+## Kubernetes
+
+# Binary
+
+## systemd
+
+# In-Process
diff --git a/web-docs/intro.md b/web-docs/intro.md
index 87184f6fe..73cc95318 100644
--- a/web-docs/intro.md
+++ b/web-docs/intro.md
@@ -28,8 +28,7 @@ No matter how you run flagd, you will need to supply it with feature flags.
 The flag definitions supplied to flagd (*sources*) are monitored for changes which will be immediately reflected in flagd's evaluations.
 Currently supported sources include files, HTTP endpoints, Kubernetes custom resources, and proto-compliant gRPC services.
 
-<!-- Should we add some simple diagrams here to illustrate the deployment options and sources? -->
-<!-- Do we want to add links here? or is there value in keeping this entirely self-contained to keep things focused? -->
+<!-- TODO: Link to various deployment sections with grid: https://squidfunk.github.io/mkdocs-material/reference/grids -->
 
 # How to I use flagd?