Fix relative links in documentation for improved navigation #141

ziagham · ziagham · commit ccf863e8e276 · 2025-12-23T20:47:23.000+01:00
diff --git a/docs/getting-started/quickstarts/build-your-first-workflow.mdx b/docs/getting-started/quickstarts/build-your-first-workflow.mdx
@@ -160,7 +160,7 @@ curl -X POST http://localhost:6262/workflows -H "Content-Type: application/json"
 - Dependencies must reference other task names exactly.
 - Cyclic graphs (A → B → A) are rejected during validation.
 - Tasks without dependencies are considered root nodes and are scheduled immediately.
-- Outputs are available via `"$[Outputs('<taskName>').<property>]"` placeholders. For more information [**Expressions**](/docs/reference/flowsynx/expressions)
+- Outputs are available via `"$[Outputs('<taskName>').<property>]"` placeholders. For more information [**Expressions**](./../../reference/flowsynx/expressions)
 
 ## Step 4: Add Error Handling (Retry Policy) (≈5 min)
 
diff --git a/docs/getting-started/quickstarts/flowsynx-in-5-minutes.mdx b/docs/getting-started/quickstarts/flowsynx-in-5-minutes.mdx
@@ -100,7 +100,7 @@ flowctl workflows executions execute -f ./hello-world.json
 Execution begins immediately.  
 
 :::info Flowctl
-If flowctl is not installed, please refer to [**Install flowctl**](/docs/getting-started/flowctl-based-installation) guide to help you install it.
+If flowctl is not installed, please refer to [**Install flowctl**](./../../getting-started/flowctl-based-installation) guide to help you install it.
 :::
 
 #### Option B — Run via REST API
@@ -141,11 +141,11 @@ This confirms that your FlowSynx environment and workflow engine are working cor
 
 Now that FlowSynx is installed and your first workflow is running, explore the following:
 
-#### ▶ [**Learn the Workflow Model**](/docs/concepts)
+#### ▶ [**Learn the Workflow Model**](./../../concepts)
 Understand DAGs, tasks, dependencies, and error handling.
 
-#### ▶ [**Use the FlowCtl CLI**](/docs/reference/cli/overview)
+#### ▶ [**Use the FlowCtl CLI**](./../../reference/cli/overview)
 Discover advanced CLI commands for managing workflows, executions, logs, and diagnostics.
 
-#### ▶ [**Integrate with the API**](/docs/reference/flowsynx/api)
+#### ▶ [**Integrate with the API**](./../../reference/flowsynx/api)
 Use FlowSynx programmatically from your applications and automation systems.
diff --git a/docs/overview.mdx b/docs/overview.mdx
@@ -6,7 +6,7 @@ sidebar_position: 1
 
 <div class="cardsGrid">
 
-  <a class="overview-card" href="/docs/getting-started">
+  <a class="overview-card" href="./getting-started">
     <h3 class="overview-card-title">Getting started</h3>
     <p class="overview-card-description">Read the comprehensive documentation to start building workflows.</p>
   </a>
diff --git a/docs/reference/flowsynx/configuration.mdx b/docs/reference/flowsynx/configuration.mdx
@@ -248,7 +248,7 @@ This is essential for automated scaling, rolling updates, and alerting in contai
 | `Enabled` | boolean | Enables or disables health check endpoints for monitoring.   |
 
 For comprehensive guidance on configuration options, response formats, and integration examples,
-see the full [Health API documentation](/docs/reference/flowsynx/api/health).
+see the full [Health API documentation](./../../reference/flowsynx/api/health).
 It provides in-depth details on endpoint behavior and sample outputs for health checks.
 
 
diff --git a/versioned_docs/version-1.2.x/getting-started/quickstarts/build-your-first-workflow.mdx b/versioned_docs/version-1.2.x/getting-started/quickstarts/build-your-first-workflow.mdx
@@ -160,7 +160,7 @@ curl -X POST http://localhost:6262/workflows -H "Content-Type: application/json"
 - Dependencies must reference other task names exactly.
 - Cyclic graphs (A → B → A) are rejected during validation.
 - Tasks without dependencies are considered root nodes and are scheduled immediately.
-- Outputs are available via `"$[Outputs('<taskName>').<property>]"` placeholders. For more information [**Expressions**](/docs/reference/flowsynx/expressions)
+- Outputs are available via `"$[Outputs('<taskName>').<property>]"` placeholders. For more information [**Expressions**](./../../reference/flowsynx/expressions)
 
 ## Step 4: Add Error Handling (Retry Policy) (≈5 min)
 
diff --git a/versioned_docs/version-1.2.x/getting-started/quickstarts/flowsynx-in-5-minutes.mdx b/versioned_docs/version-1.2.x/getting-started/quickstarts/flowsynx-in-5-minutes.mdx
@@ -100,7 +100,7 @@ flowctl workflows executions execute -f ./hello-world.json
 Execution begins immediately.  
 
 :::info Flowctl
-If flowctl is not installed, please refer to [**Install flowctl**](/docs/getting-started/flowctl-based-installation) guide to help you install it.
+If flowctl is not installed, please refer to [**Install flowctl**](./getting-started/flowctl-based-installation) guide to help you install it.
 :::
 
 #### Option B — Run via REST API
@@ -141,11 +141,11 @@ This confirms that your FlowSynx environment and workflow engine are working cor
 
 Now that FlowSynx is installed and your first workflow is running, explore the following:
 
-#### ▶ [**Learn the Workflow Model**](/docs/concepts)
+#### ▶ [**Learn the Workflow Model**](./../../concepts)
 Understand DAGs, tasks, dependencies, and error handling.
 
-#### ▶ [**Use the FlowCtl CLI**](/docs/reference/cli/overview)
+#### ▶ [**Use the FlowCtl CLI**](./../../reference/cli/overview)
 Discover advanced CLI commands for managing workflows, executions, logs, and diagnostics.
 
-#### ▶ [**Integrate with the API**](/docs/reference/flowsynx/api)
+#### ▶ [**Integrate with the API**](./../../reference/flowsynx/api)
 Use FlowSynx programmatically from your applications and automation systems.
diff --git a/versioned_docs/version-1.2.x/overview.mdx b/versioned_docs/version-1.2.x/overview.mdx
@@ -6,7 +6,7 @@ sidebar_position: 1
 
 <div class="cardsGrid">
 
-  <a class="overview-card" href="/docs/getting-started">
+  <a class="overview-card" href="./getting-started">
     <h3 class="overview-card-title">Getting started</h3>
     <p class="overview-card-description">Read the comprehensive documentation to start building workflows.</p>
   </a>
@@ -34,9 +34,9 @@ workflows in a simple, consistent, and maintainable way.
 With its modular plugin architecture and native C# SDK, FlowSynx supports seamless integration with 
 external systems, custom business logic, cloud storage providers, databases, APIs, and more—allowing 
 users to extend functionality without modifying the core engine. Workflows are represented as 
-JSON-based [DAGs (Directed Acyclic Graphs)](/docs/concepts#directed-acyclic-graphs-dags), enabling 
-precise control over [execution order, dependencies](/docs/concepts#task-dependencies--execution-order), 
-[retries & error handling](/docs/concepts#retry-policies--error-handling), and conditional logic.
+JSON-based [DAGs (Directed Acyclic Graphs)](./concepts#directed-acyclic-graphs-dags), enabling 
+precise control over [execution order, dependencies](./concepts#task-dependencies--execution-order), 
+[retries & error handling](./concepts#retry-policies--error-handling), and conditional logic.
 
 ### FlowSynx features:
 - **Plugin-Based Extensibility** — Add, upgrade, or remove capabilities dynamically and version-controlled  
diff --git a/versioned_docs/version-1.2.x/reference/flowsynx/configuration.mdx b/versioned_docs/version-1.2.x/reference/flowsynx/configuration.mdx
@@ -248,7 +248,7 @@ This is essential for automated scaling, rolling updates, and alerting in contai
 | `Enabled` | boolean | Enables or disables health check endpoints for monitoring.   |
 
 For comprehensive guidance on configuration options, response formats, and integration examples,
-see the full [Health API documentation](/docs/reference/flowsynx/api/health).
+see the full [Health API documentation](./../../reference/flowsynx/api/health).
 It provides in-depth details on endpoint behavior and sample outputs for health checks.
 
 
