Stuffed in initial terms and homepage updates

Signed-off-by: cjyabraham <cjyabraham@gmail.com>
todogroup · Jun 5, 2023 · 6101678 · 6101678
1 parent 84430c9
commit 6101678
Show file tree

Hide file tree

Showing 94 changed files with 67 additions and 2,329 deletions.
diff --git a/content/en/_TEMPLATE.md b/content/en/_TEMPLATE.md
diff --git a/content/en/_index.md b/content/en/_index.md
@@ -5,44 +5,17 @@ status: Completed
 
 # OSPO Glossary
 
-The Cloud Native Glossary aims to make the cloud native space — which is notorious for its complexity — simpler for people by making it easier to understand, 
-not only for technologists but also for people on the business side. 
-To achieve that, we focus on simplicity (e.g., simple language free from buzzwords, examples anyone using technology can relate to, leaving unnecessary details out). 
-The Glossary is a project led by the CNCF Business Value Subcommittee (BVS). 
-
-<p><img class="mt-3" src="/images/homepage/kubecon.jpg" alt="People watching a Kubecon presentation"></p>
-
-## Contributing
-
-Everybody is invited to suggest changes, additions, and improvements to the Cloud Native Glossary. 
-We employ a community-driven process governed by the CNCF to develop and improve upon this shared lexicon. 
-This Glossary provides a vendor-neutral platform to organize a shared vocabulary around cloud native technologies. 
-Contributions are welcome from all participants who abide by the project's purpose and charter.
-
-Anyone who wishes to make a contribution may submit a GitHub issue or create a pull request. 
-Please ensure you follow the [Style Guide](/style-guide/), read the [How To Contribute](/contribute/) doc, and join the [#glossary](https://cloud-native.slack.com/archives/C02TX20MQBB) channel on the CNCF Slack.
-There is also a [#glossary-localizations](https://cloud-native.slack.com/archives/C02N2RGFXDF) channel for those who want to help translate the glossary into their native language.
-
-## Acknowledgements
-
-The Cloud Native Glossary was initiated by the CNCF Marketing Committee (Business Value Subcommittee) and includes contributions from 
-[Catherine Paganini](https://www.linkedin.com/in/catherinepaganini/en/), 
-[Chris Aniszczyk](https://www.linkedin.com/in/caniszczyk/), 
-[Daniel Jones](https://www.linkedin.com/in/danieljoneseb/?originalSubdomain=uk), 
-[Jason Morgan](https://www.linkedin.com/in/jasonmorgan2/), 
-[Katelin Ramer](https://www.linkedin.com/in/katelinramer/), 
-[Mike Foster](https://www.linkedin.com/in/mfosterche/?originalSubdomain=ca), 
-and many more contributors. 
-For a complete contributor list, please refer to [this GitHub page](https://github.com/cncf/glossary/graphs/contributors).
-
-The Glossary is maintained by 
-[Catherine Paganini](https://www.linkedin.com/in/catherinepaganini/en/), 
-[Jason Morgan](https://www.linkedin.com/in/jasonmorgan2/), 
-[Jihoon Seo](https://www.linkedin.com/in/jihoon-seo/), 
-[Noah Ispas](https://www.linkedin.com/in/noah-ispas-0665b42a/), 
-and [Seokho Son](https://www.linkedin.com/in/seokho-son/).
+Welcome to the glossary for the Open Source Program Offices (OSPOs) Book. As you may know, the world of open source is vast and complex, with many different terms and concepts that can be difficult to navigate. Our aim with this glossary is not to provide a definitive or general definition of these terms, but to clarify what we mean specifically under the context of this book.
+
+We believe that it is important to be concise and clear in our definitions, and to reference existing descriptions and resources whenever possible. This will help us avoid creating a glossary that is overly complex or difficult to understand, and will ensure that our readers have access to the best information and resources available.
+
+<p><img class="mt-3" src="/images/homepage/group.jpg" alt="Group of people talking"></p>
+
+As you explore the terms and concepts in this glossary, we encourage you to use the descriptions and links provided. And if you have any suggestions for additional terms or resources that we should include, please don't hesitate to open an Issue or include new terms by opening a PR!
 
 ## License
 
 All code contributions are under the Apache 2.0 license. 
 Documentation is distributed under CC BY 4.0.
+
+<p><img class="mt-3" src="/images/homepage/writing.jpg" alt="Woman writing on a pad of paper"></p>
diff --git a/content/en/abstraction.md b/content/en/abstraction.md
diff --git a/content/en/agile-software-development.md b/content/en/agile-software-development.md
diff --git a/content/en/api-gateway.md b/content/en/api-gateway.md
diff --git a/content/en/application-programming-interface.md b/content/en/application-programming-interface.md
diff --git a/content/en/auto-scaling.md b/content/en/auto-scaling.md
diff --git a/content/en/bare-metal-machine.md b/content/en/bare-metal-machine.md
diff --git a/content/en/blue-green-deployment.md b/content/en/blue-green-deployment.md
diff --git a/content/en/canary-deployment.md b/content/en/canary-deployment.md
diff --git a/content/en/chaos-engineering.md b/content/en/chaos-engineering.md