Update content

- added slides and content for introduction section
- updated navigation to make more sense
- removed silly attribute causing rendering issue

Author: day0hero

documentation/modules/ROOT/assets/images/Linux-Penguin-Evolution-1.png

@@ -2,6 +2,8 @@
 ** xref:getting-started.adoc#prereqs[Pre-Requisites]
 
 * xref:patterns.adoc[2. Introduction]
+** xref:patterns.adoc#objectives[Topic Objectives]
+** xref:patterns.adoc#goals[Validated Patterns Business Goals]
 ** xref:patterns.adoc#benefits[Benefits of Validated Patterns]
 ** xref:patterns.adoc#batteries[Batteries Included]
 ** xref:patterns.adoc#whotheyfor[Who are the Patterns for]
@@ -30,4 +32,4 @@
 
 * xref:helm.adoc[11. Helm for Fun and Profit]
 
-* xref:additionalTopics.adoc[12. Additional Resources]
+* xref:additionalTopics.adoc[12. Additional Resources]

documentation/modules/ROOT/assets/images/introduction-batteriesIncluded.png

@@ -1,4 +1,3 @@
-::moduledir: ..
 :cli: oc
 :branch: main
 :vp-gh-repo: https://github.com/validatedpatterns

documentation/modules/ROOT/assets/images/introduction-goals.png

@@ -1,7 +1,72 @@
+== Topic Objectives
 include::_attributes.adoc[]
 
+[#objectives]
+
+In this topic  we will discuss:
+
+* What is a GitOps Pattern?
+** Explain high level benefits provided by GitOps Patterns
+** Discuss what is included in the patterns initiative
+** Detail the difference between a community and validated patterns
+* Who are GitOps Patterns for?
+** Explain the high level benefit for each persona
+** Clarify the requirements to become validated
+* Where can you keep up to date or point people to find more information?
+
+[#what]
+
+== What are Validated Patterns?
+
+Validated Patterns are an evolution of reference architectures. Each pattern is given a lifecycle when it is added to Red Hat's continuous integration (CI) system because we're testing against the latest version of operators, OpenShift releases and across multiple public cloud environments.
+
+image::Linux-Penguin-Evolution-1.png[evolution]
+
+[#goals]
+
+== Business Goals
+
+Every organization is facing the need to transform itself into a digital business. It's part of an evolution to help **accelerate innovation** by making application development faster - fueled with data insights, and enabled through technologies like containers, kubernetes and artifical intelligence/machine learning.
+
+In order to be successful, they know they must also look at how to be more **operationally agile** and **efficient** in order to quickly meet business needs. Hybrid-Cloud computing coupled with these new technologies is helping create new opportunities to achieve these goals.
+
+Validated Patterns are focused on customer solutions and Proof-Of-Concepts (POC's).
+
+image::introduction-goals.png[]
+
 [#benefits]
 
+== Benefits
+
+Red Hat’s validated patterns are a collection of repositories that show a customers use case in the form of Kubernetes Resources (helm charts, kustomize, primitive objects) that describe an hybrid cloud stack declaratively and comprehensively; from its services down to the supporting infrastructure. Validated Patterns facilitate complex, highly reproducible deployments and are ideal for operating these deployments at scale using GitOps operational practices.
+
+image::introduction-pattern-benefits.png[]
+
+* Use a GitOps model to deliver the use case as code
+* Use as a POC, modified to fit a particular need that you can evolve into a real deployment.
+* Highly reproducible - great for operating at scale
+* Open for collaboration, so anyone can suggest improvements, contribute to them or use them as the Git Repositories are all upstream
+* Can be modified for customers needs.  If you would like to swap out a component, use Ceph Storage instead of S3, it is as easy as commenting out sections and including other repos.
+* Tested.  Once made a validated pattern, the use case is included into Red Hat’s CI and continues to be tested across product versions while the pattern remains active.
+
 [#batteries]
 
+== Batteries Included 
+
+Validated Patterns are a "batteries included" solution. This means that wherever you start with the patterns framework a core and configurable set of components are delivered out of the box. Reusability is a major theme that will be seen throughout this workshop. 
+
+image::introduction-batteriesIncluded.png[]
+
 [#whotheyfor]
+
+== Who are patterns for?
+
+Value provided by Validated Patterns is unique to each individual or organization. Generally speaking Patterns provide value to our:
+
+image::introduction-pattern-values.png[]
+
+* Customers - get going faster, reduce risk, time to value
+* Sales - don't spend time architecting, they have a tested use ccase for a base deployment. Though messaged for a specific vertical in some cases, they can be used across other verticals. 
+* Partners - free use of a defined architecutre that you can build a solution on top of. All the value to accelerate sales/deployments.
+** Can also be used as a way to promote your product (HashiCorp)
+* GSIs or Consulting Services - predefined architectures, ready to deploy with minimal modifications. They can trust in the use-case as it is maintained across production version updates.