Content for the context page in the workflow section

Author: Aviatorscode2

content/docs/platform/inbox/configuration/inbox-with-context.mdx

@@ -0,0 +1,6 @@
+---
+pageTitle: 'Using contexts for Inbox personalization'
+title: 'Inbox with context'
+description: 'Learn how to use the data object to extend in-app notifications with custom metadata.'
+icon: 'Table'
+---

content/docs/platform/inbox/configuration/meta.json

@@ -1,6 +1,6 @@
 {
   "title": "Customize and configure",
   "icon": "SlidersHorizontal",
-  "pages": ["styling", "icons", "tabs", "preferences", "data-object"],
+  "pages": ["styling", "icons", "tabs", "preferences", "data-object", "inbox-with-context"],
   "description": "Learn how to configure your inbox with styling, tabs, preferences, data objects, and snooze functionality"
 }

content/docs/platform/workflow/contexts.mdx

@@ -0,0 +1,79 @@
+---
+pageTitle: 'Personalize workflows and templates in Novu using context'
+title: 'Applying context'
+description: 'Learn how to use contexts in Novu to personalize notification templates, control workflow logic, and customize the Inbox. Understand supported data formats and how to debug context usage from the activity feed.'
+---
+
+Contexts let you personalize how notifications are rendered and delivered by making contextual data available inside template editors, step conditions, and the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> component.
+
+## How to use context
+
+Once a context is created either through the Novu dashboard or API, its data becomes available for use in your templates editors, step conditions, and for customizing the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> component.
+
+### Using context data in the template editor
+
+Use the `{{context}}` Handlebars helper to access context data in any template editor. The context key you provide while creating the context (for example, tenant, region) becomes the accessor.
+
+
+For example, if a context with this data is created:
+
+```json
+context: {
+  tenant: {
+    id: 'acme-corp',
+    data: {
+      name: 'Acme Corporation',
+      plan: 'enterprise'
+    }
+  }
+}
+```
+
+You can access the `name` and `plan` in your in-app, email, SMS, or push template like this:
+
+```html
+<p>Welcome, new user from {{context.tenant.data.name}}!</p>
+<p>Your account is on the {{context.tenant.data.plan}} plan.</p>
+```
+Or
+
+```text
+Welcome, new user from {{context.tenant.data.name}}!
+Your account is on the {{context.tenant.data.plan}} plan.
+```
+
+![Using context data in the template editor](/images/workflows/contexts/context.gif)
+
+<Callout>Refer to the Inbox documentation, to learn how to use context in the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> component. </Callout>
+
+### Using context in step conditions
+
+You can use context variables in the **Step conditions** tab of a workflow step to add conditional logic to your notifications. For example, only send a "Feature X is now enabled" email if `context.tenant.data.plan` is `enterprise`.
+![Context step conditions](/images/workflows/context-step-conditions.png)
+
+To learn how contexts are structured or how to define them, refer to the [Managing Contexts](/platform/workflow/contexts/manage-contexts) documentation.
+
+## Viewing and debugging contexts
+
+Once you start using contexts in your workflows, Novu provides full observability so you can monitor and debug your context usage after a workflow has been triggered.
+
+### Searching for workflow runs
+
+You can filter your workflow runs to find all executions associated with a specific context.
+
+1. Navigate to the **Activity Feed** in your Novu dashboard.
+2. Select the **Workflow Runs** tab.
+3. In the search bar, click **Context** and enter the context `type` and `id` using the format `type:id`.
+
+![Searching for workflow runs](/images/workflows/search-context-activityfeed.png)
+
+### Verifying the resolved context
+
+To confirm that Novu received and processed your context data correctly, you can inspect the API traces for a specific run.
+
+1. From the **Activity Feed**, select the relevant workflow run from the list in the **Requests** tab.
+2. In the workflow run details, go to the **API Traces** tab.
+
+Here, you will see the full context object that was resolved and attached to that specific workflow execution.
+
+![Verifying the resolved context](/images/workflows/resolved-context.png)