Added architectural layers diagram, placeholder for Summary section.

2 files changed, 7 insertions, 4 deletions

diff --git a/contributors/devel/arch-roadmap-1.png b/contributors/devel/arch-roadmap-1.png
new file mode 100644
index 00000000..660d8206
--- /dev/null
+++ b/contributors/devel/arch-roadmap-1.png
diff --git a/contributors/devel/architectural-roadmap.md b/contributors/devel/architectural-roadmap.md
index 5d50a2b9..51585bf3 100644
--- a/contributors/devel/architectural-roadmap.md
+++ b/contributors/devel/architectural-roadmap.md
@@ -10,13 +10,14 @@ Authors: Brian Grant, Tim Hockin, and Clayton Coleman
 
 Intended audience: Kubernetes contributors
 
-Let’s start as ordinary doc text and export to markdown later.
-
 * * *
 
-
 [[TOC]]
 
+## Summary/TL;DR
+
+TBD - for those who want an overview, but don't want to read a 20 page document.
+
 ## Background
 
 Kubernetes is a platform for deploying and managing containers. For
@@ -61,6 +62,8 @@ should be allowed and which should not.
 Kubernetes APIs, concepts, and functionality can be sorted into the
 following layers.
 
+![Architectural Layers](arch-roadmap-1.png)
+
 ### The Nucleus: API and Execution
 
 Essential API and execution machinery.
@@ -147,7 +150,7 @@ Kubernetes cannot function without this basic API machinery and semantics, inclu
         * [Lack of
           guarantees](https://github.com/kubernetes/kubernetes/issues/30698)
         * [Orchestration
-          support](https://github.com/kubernetes/kubernetes/issues/34363)\
+          support](https://github.com/kubernetes/kubernetes/issues/34363)
         * [Support for event-driven
           automation](https://github.com/kubernetes/kubernetes/issues/3692)
         * [Clean