Added initial content for hypershift

Author: day0hero

content/patterns/hypershift/_index.adoc

@@ -13,9 +13,8 @@ aliases: /hypershift/
 pattern_logo: medical-diagnosis.png
 links:
   install: getting-started
-  arch: https://www.redhat.com/architect/portfolio/architecturedetail?ppid=6
   help: https://groups.google.com/g/validatedpatterns
-  bugs: https://github.com/validatedpatterns/medical-diagnosis/issues
+  bugs: https://github.com/validatedpatterns-sandbox/hypershift/issues
 ci: hypershift
 ---
 
@@ -42,62 +41,34 @@ Workflow::
 * Create an S3 bucket to be used by HyperShift for OIDC
 * Create a buildconfig and imagestream that provide the HyperShift cli (`hypershift`) as an imagestream to be used in further automation if desired.
 
-This pipeline is showcased link:https://www.youtube.com/watch?v=zja83FVsm14[in this video].
+//This pipeline is showcased link:https://www.youtube.com/watch?v=zja83FVsm14[in this video].
 
-image::medical-edge/dashboard.png[link="/images/medical-edge/dashboard.png"]
+image::hypershift/hypershift-high-level-architecture.png[link="/images/hypershift/hypershift-high-level-architecture.png"]
 
 //[NOTE]
 //====
-//This pattern is still under development. If you have any questions or concerns contact mailto:jrickard@redhat.com[Jonny Rickard].
+//If you have any questions or concerns contact mailto:jrickard@redhat.com[Jonny Rickard].
 //====
 
-[id="about-solution-med"]
+[id="about-solution-hyp"]
 == About the solution elements
 
-The solution aids the understanding of the following:
+The solution enables the rapid provisioning of hosted controlplane clusters.
 
-* How to use a GitOps approach to keep in control of configuration and operations.
-* How to deploy AI/ML technologies for medical diagnosis using GitOps.
-
-The {med-pattern} uses the following products and technologies:
+The {hyp-pattern} uses the following products and technologies:
 
 * {rh-ocp} for container orchestration
 * {rh-gitops}, a GitOps continuous delivery (CD) solution
-* {rh-amq-first}, an event streaming platform based on the Apache Kafka
-* {rh-serverless-first} for event-driven applications
-* {rh-ocp-data-first} for cloud native storage capabilities
-* {grafana-op} to manage and share Grafana dashboards, data sources, and so on
+* {rh-mce}, the multicluster-engine provider
 * S3 storage
 
-[id="about-architecture-med"]
-== About the architecture
-
-[IMPORTANT]
-====
-Presently, the {med-pattern} does not have an edge component. Edge deployment capabilities are planned as part of the pattern architecture for a future release.
-====
-
-image::medical-edge/edge-medical-diagnosis-marketing-slide.png[link="/images/medical-edge/edge-medical-diagnosis-marketing-slide.png"]
-
-Components are running on OpenShift either at the data center, at the medical facility, or public cloud running OpenShift.
-
-[id="about-physical-schema-med"]
-=== About the physical schema
-
-The following diagram shows the components that are deployed with the various networks that connect them.
-
-image::medical-edge/physical-network.png[link="/images/medical-edge/physical-network.png"]
-
-The following diagram shows the components that are deployed with the the data flows and API calls between them.
-
-image::medical-edge/physical-dataflow.png[link="/images/medical-edge/physical-dataflow.png"]
-
-== Recorded demo
+// All commented out by jrickard
+//== Recorded demo
 
-link:/videos/xray-deployment.svg[image:/videos/xray-deployment.svg[Demo\]]
+//link:/videos/xray-deployment.svg[image:/videos/xray-deployment.svg[Demo\]]
 
-[id="next-steps_med-diag-index"]
-== Next steps
+//[id="next-steps_med-diag-index"]
+//== Next steps
 
-* Getting started link:getting-started[Deploy the Pattern]
+//* Getting started link:getting-started[Deploy the Pattern]
 //We have relevant links on the patterns page