Merge pull request #7565 from Luuk1983/feature/7490_context_api

Update to the Context API documentation

Author: eshanrnh

16/umbraco-cms/SUMMARY.md

@@ -204,6 +204,7 @@
   * [Umbraco Element](customizing/foundation/umbraco-element/README.md)
   * [Lit Element](customizing/foundation/lit-element.md)
   * [Context API](customizing/foundation/context-api/README.md)
+    * [Context API Fundamentals](customizing/foundation/context-api/context-api-fundamentals.md)
     * [Consume a Context](customizing/foundation/context-api/consume-a-context.md)
     * [Provide a Context](customizing/foundation/context-api/provide-a-context.md)
   * [Repositories](customizing/foundation/repositories.md)

16/umbraco-cms/customizing/foundation/context-api/README.md

@@ -1,9 +1,35 @@
 ---
-description: The Context API is your tool to integrate with the application
+description: >-
+  Learn about using the Context API for sharing data and functionality between
+  backoffice extensions through the component hierarchy.
 ---
 
 # Context API
 
-The Context API enables receiving APIs. Depending on where your code is executed from, it affects which and what instances of APIs can be received. The DOM structure defines the scope of who can gain access to what APIs. This is because the APIs are provided via an element and can then only be consumed by code running on itself or descendant elements.
+The Context API is a powerful communication system in Umbraco's backoffice. It enables extensions to share data and functionality through the component hierarchy without tight coupling. Think of it as a way for different parts of your UI to talk to each other and access shared services.
+
+Contexts are used throughout the Umbraco backoffice to provide access to workspace data, notifications, user information, and many other services. When building custom extensions, you will often need to consume existing contexts or create your own to share functionality between your components.
+
+## Key Concepts
+
+The Context API is built on a few core principles:
+
+* **Provider-Consumer Pattern**: Parent elements provide contexts that descendant elements can consume
+* **Loose Coupling**: Components don't need direct references to each other
+* **Hierarchical**: Contexts flow down through the DOM tree
+* **Type-Safe**: Context Tokens ensure you get the right context
+
+The Context API provides a structured way to access and share functionality when building property editors, workspace extensions, dashboards, or any other backoffice UI.
+
+## [Context API Fundamentals](context-api-fundamentals.md)
+
+Learn the core concepts, terminology, and flow mechanisms of the Context API. Understand how contexts are provided and consumed through the element hierarchy, and explore common context types used throughout Umbraco.
+
+## [Consume a Context](consume-a-context.md)
+
+Learn how to consume contexts in your extensions using one-time references or subscriptions. This guide covers consuming contexts in UI elements, services, and non-UI classes, with practical code examples for each scenario.
+
+## [Provide a Context](provide-a-context.md)
+
+Learn how to create and provide your own custom contexts. Make your data and functionality available to descendant elements in the component hierarchy.
 
-##