docs: add developer and api reference tabs (#190)

* docs: add developer and api reference tabs

* fix: remove duplicate image

docs/voice-agent/editing-a-workflow.mdx

@@ -29,7 +29,7 @@ Contains instructions applicable across the entire call:
 ## Node-Level Toggles
 
 ### Add Global Prompt
-- Recommended to inject Global Node instructions into most nodes
+- Recommended to inject [Global Node](/voice-agent/global) instructions into most nodes
 
 ### Allow Interruption
 - **Default "On"**: Bot stops and responds to user interruption
@@ -46,7 +46,7 @@ Supported in Agent and End Call Nodes:
 - Define name, type, and description
 - Examples: customer name, budget, interest
 
-## Webhook Node
+## [Webhook Node](/voice-agent/webhook)
 
 - Executed at call end
 - Sends payload to specific endpoint
@@ -63,5 +63,5 @@ Supported in Agent and End Call Nodes:
 ## Pathways and Tool Calls
 
 - Define agent node movement
-- Use tool calls to transition between nodes
+- Use [tool calls](/voice-agent/tools/http-api) to transition between nodes
 - **"tool"** is a reserved keyword for function calls and actions

docs/voice-agent/template-variables.mdx

@@ -4,7 +4,7 @@ description: "You can use Template Variables in your prompts for your Agent node
 ---
 
 ### Template Rendering
-You can reference template variables which is passed as `initial_context` either using the API Trigger or when uploading a Sheet for a campaign. You can also use any extracted variable as `gathered_context`
+You can reference template variables which is passed as [`initial_context`](/core-concepts/context-and-variables#initial_context) either using the [API Trigger](/voice-agent/api-trigger) or when uploading a Sheet for a [campaign](/core-concepts/campaigns). You can also use any extracted variable as [`gathered_context`](/core-concepts/context-and-variables#gathered_context)
 
 The template rendering can take nested values. 
 
@@ -25,4 +25,4 @@ You can write your prompt to access the user's name as below
 Prompt: `You are Alice, who is talking to {{initial_context.user.name}}.`
 
 ### Nodes
-Dograh Voice Agents are composed of various nodes. These nodes can provide instructions to the voice agent, help you setup a trigger where you can trigger the voice agent to call someone, or help you setup a webhook, where you can update the results of the call in your CRM or trigger a downstream workflow in n8n. In the next steps, we will be documenting the nodes that you can use in building the voice agent.
+Dograh Voice Agents are composed of various nodes. These nodes can provide instructions to the voice agent, help you setup a [trigger](/voice-agent/api-trigger) where you can trigger the voice agent to call someone, or help you setup a [webhook](/voice-agent/webhook), where you can update the results of the call in your CRM or trigger a downstream workflow in n8n. In the next steps, we will be documenting the nodes that you can use in building the voice agent.

docs/voice-agent/webhook.mdx

@@ -26,8 +26,8 @@ The payload can contain a valid JSON, and you can reference variables while cons
 - `{{workflow_run_id}}` Unique ID of the Agent run
 - `{{workflow_id}}` ID of the Agent
 - `{{workflow_name}}` Name of the workflow
-- `{{initial_context.*}}` Initial context variables
-- `{{gathered_context.*}}` Extracted variables
+- `{{initial_context.*}}` [Initial context variables](/core-concepts/context-and-variables#initial_context)
+- `{{gathered_context.*}}` [Extracted variables](/core-concepts/context-and-variables#gathered_context)
 - `{{cost_info.call_duration_seconds}}` Call duration
 - `{{recording_url}}` Call recording URL
 - `{{transcript_url}}` Transcript URL