New kb

.gitignore

@@ -7,9 +7,9 @@
 # Generated files
 .docusaurus
 .cache-loader
-/docs/SDK-API/*.mdx
+/docs/APIs-and-SDKs/SDK-API*.mdx
 /docs/Web-Console-API/*.mdx
-/docs/SDK-API/*.js
+/docs/APIs-and-SDKs/SDK-API*.js
 /docs/Web-Console-API/*.js
 
 # Misc

docs/SDK-Documentation/Advanced/code-as-a-variant-variable.mdx → docs/APIs-and-SDKs/SDK-Documentation/Advanced/code-as-a-variant-variable.mdx

@@ -2,7 +2,7 @@ import Image from "@theme/IdealImage";
 
 # Code as a Variant Variable
 
-[Variant Variables](/docs/SDK-Documentation/basic-usage#treatment-variables) 
+[Variant Variables](/docs/APIs-and-SDKs/SDK-Documentation/basic-usage#treatment-variables) 
 are incredibly useful for setting particular values in your experiments, but 
 sometimes it can be useful to run code as a variable instead. This section 
 will show you a few examples of how this can be implemented; connecting your 

docs/SDK-Documentation/Advanced/context-attributes/setting-context-attributes/_setting-context-attributes.mdx → docs/APIs-and-SDKs/SDK-Documentation/Advanced/context-attributes/setting-context-attributes/_setting-context-attributes.mdx

@@ -34,7 +34,7 @@ context is ready.
 One of the most useful and commonly used attributes, is the `user_agent` attribute
 which, when passed to the SDK, will be split up into multiple attributes that
 can be used to target specific browsers or devices in the Web Console. You can read
-more about how this works in [the Segments section of the Dashboard Settings docs](/docs/web-console-docs/settings#segments).
+more about how this works in [the Segments section of the Dashboard Settings docs](/docs/web-console-docs/configuration/settings#segments).
 
 <Tabs groupId="language">
 

docs/SDK-Documentation/Advanced/custom-assignments/_custom-assignments.mdx → docs/APIs-and-SDKs/SDK-Documentation/Advanced/custom-assignments/_custom-assignments.mdx

@@ -40,7 +40,7 @@ Events with custom assignments are **counted as eligible events** by the ABsmart
 statistics engines. If you are using these methods for development purposes
 (to force a particular variant for yourself or somebody else on the team) it is
 likely that you need the 
-[`context.override` methods](/docs/SDK-Documentation/basic-usage#overriding-treatment-variants) 
+[`context.override` methods](/docs/APIs-and-SDKs/SDK-Documentation/basic-usage#overriding-treatment-variants) 
 instead.
 :::
 

docs/SDK-Documentation/Advanced/using-custom-fields-in-your-code.mdx → docs/APIs-and-SDKs/SDK-Documentation/Advanced/using-custom-fields-in-your-code.mdx

@@ -1,6 +1,6 @@
 # Custom Fields in Code
 
-In the [Platform Settings on the Web Console](/docs/web-console-docs/settings#platform-settings), you can create
+In the [Platform Settings on the Web Console](/docs/web-console-docs/configuration/settings#platform-settings), you can create
 custom fields that are available to the SDKs. These custom fields can be used to add additional logic to your
 A/B experiments.
 
@@ -18,7 +18,7 @@ Let's say you wish to override an experiment's allocation to a specific variant
 
 ### Creating a Custom Field
 
-Checkout the [docs on creating a custom field](/docs/web-console-docs/settings#custom-fields) for more information on
+Checkout the [docs on creating a custom field](/docs/web-console-docs/configuration/settings#custom-fields) for more information on
 adding a field to your experiment creation form, but for this example, we'll create a field with
 the following properties:
 - **Name**: `Developers' variant`
@@ -31,7 +31,7 @@ the following properties:
 - **Section**: `Description`
 
 :::note
-You may wish to [create a custom section](/docs/web-console-docs/settings#custom-fields) for this field.
+You may wish to [create a custom section](/docs/web-console-docs/configuration/settings#custom-fields) for this field.
 :::
 
 ### Using the Custom Field
@@ -64,7 +64,7 @@ edited on the Web Console to change the variant that developers see.
 
 :::caution
 Overriding an experiment allocation will not count the user towards the experiment data.
-To learn more about overrides, have a look at the [overrides SDK documentation](/docs/SDK-Documentation/basic-usage#overriding-treatment-variants).
+To learn more about overrides, have a look at the [overrides SDK documentation](/docs/APIs-and-SDKs/SDK-Documentation/basic-usage#overriding-treatment-variants).
 :::
 
 ## Conclusion

docs/SDK-Documentation/basic-usage/overriding/_overriding.mdx → docs/APIs-and-SDKs/SDK-Documentation/basic-usage/overriding/_overriding.mdx

@@ -28,7 +28,7 @@ import FlutterOverriding from "!!raw-loader!./flutter/override.dart";
 :::warning Warning
 Overriden events are typed as ineligible and are **ignored** by the ABsmartly statistics engines. 
 If you want to force a particular experiment's variant and have the event be counted, you
-can use the [`customAssignment` methods](/docs/SDK-Documentation/Advanced/custom-assignments)
+can use the [`customAssignment` methods](/docs/APIs-and-SDKs/SDK-Documentation/Advanced/custom-assignments)
 instead, although this **is not recommended**.
 :::
 

docs/SDK-Documentation/getting-started/import-and-initialize/_import-and-initialize.mdx → docs/APIs-and-SDKs/SDK-Documentation/getting-started/import-and-initialize/_import-and-initialize.mdx

@@ -34,9 +34,9 @@ import FlutterImport from "!!raw-loader!./flutter/import.dart";
 Once the SDK is installed, it can be initialized in your project.
 
 :::info
-The following examples assume that an [Api Key with SDK permissions](/docs/web-console-docs/settings#api-keys),
-an [Application](/docs/web-console-docs/tutorial#2-setting-your-applications), and an
-[Environment](/docs/web-console-docs/settings#environments) have been created in the ABsmartly Web Console.
+The following examples assume that an [Api Key with SDK permissions](/docs/web-console-docs/configuration/settings#api-keys),
+an [Application](/docs/web-console-docs/Configuration/Applications), and an
+[Environment](/docs/web-console-docs/configuration/settings#environments) have been created in the ABsmartly Web Console.
 :::
 
 <Tabs groupId="language">

docs/Examples/Slack-Integration/index.mdx → docs/APIs-and-SDKs/Web-Console-API/Examples/Slack-Integration/index.mdx

@@ -191,17 +191,17 @@ We are going to make sure our webhook is `Enabled` and `Ordered`; we will give i
 and we will choose to send events whenever any experiment event occurs.
 
 This includes:
-- [ExperimentCreated](/docs/web-console-docs/settings#experiment-created)
-- [ExperimentDevelopment](/docs/web-console-docs/settings#experiment-started-in-development)
-- [ExperimentStarted](/docs/web-console-docs/settings#experiment-started)
-- [ExperimentStopped](/docs/web-console-docs/settings#experiment-stopped)
-- [ExperimentRestarted](/docs/web-console-docs/settings#experiment-restarted)
-- [ExperimentFullOn](/docs/web-console-docs/settings#experiment-put-full-on)
-- [ExperimentEdited](/docs/web-console-docs/settings#experiment-edited)
-- [ExperimentCommented](/docs/web-console-docs/settings#experiment-commented-on)
-- [ExperimentArchived](/docs/web-console-docs/settings#experiment-archived)
-- [ExperimentUnarchived](/docs/web-console-docs/settings#experiment-unarchived)
-- [ExperimentAlertCreated](/docs/web-console-docs/settings#experiment-alert-created)
+- [ExperimentCreated](/docs/web-console-docs/configuration/settings#experiment-created)
+- [ExperimentDevelopment](/docs/web-console-docs/configuration/settings#experiment-started-in-development)
+- [ExperimentStarted](/docs/web-console-docs/configuration/settings#experiment-started)
+- [ExperimentStopped](/docs/web-console-docs/configuration/settings#experiment-stopped)
+- [ExperimentRestarted](/docs/web-console-docs/configuration/settings#experiment-restarted)
+- [ExperimentFullOn](/docs/web-console-docs/configuration/settings#experiment-put-full-on)
+- [ExperimentEdited](/docs/web-console-docs/configuration/settings#experiment-edited)
+- [ExperimentCommented](/docs/web-console-docs/configuration/settings#experiment-commented-on)
+- [ExperimentArchived](/docs/web-console-docs/configuration/settings#experiment-archived)
+- [ExperimentUnarchived](/docs/web-console-docs/configuration/settings#experiment-unarchived)
+- [ExperimentAlertCreated](/docs/web-console-docs/configuration/settings#experiment-alert-created)
 
 Click `Create Webhook` and we should start receiving events in our express app!
 
@@ -246,7 +246,7 @@ app.listen(PORT, () => {
 
 Now, whenever an experiment is changed or has an alert created, that event will be sent as a message to your Slack channel!
 
-For further formatting of the messages, checkout the [various Webhook Payloads](/docs/web-console-docs/settings#payloads) that ABsmartly can send, and
+For further formatting of the messages, checkout the [various Webhook Payloads](/docs/web-console-docs/configuration/settings#payloads) that ABsmartly can send, and
 have a look at Slack's [Message Formatting](https://api.slack.com/messaging/composing) documentation.
 
 Our final `index.ts` file should look like this:

docs/APIs-and-SDKs/Web-Console-API/Examples/_category_ copy.json

@@ -0,0 +1,6 @@
+{
+  "position": 50,
+  "collapsible": true,
+  "collapsed": true,
+  "label": "Custom Integration Examples"
+}

docs/Web-Console-API/_category_.json → docs/APIs-and-SDKs/Web-Console-API/_category_.json

@@ -2,5 +2,5 @@
   "position": 4,
   "collapsed": true,
   "collapsible": true,
-  "label": "Web Console API"
+  "label": "Platform API"
 }

docs/APIs-and-SDKs/_category_.json

@@ -0,0 +1,6 @@
+{
+  "position": 2,
+  "collapsible": true,
+  "collapsed": true,
+  "label": "APIs & SDKs"
+}

docs/APIs-and-SDKs/overview.mdx

@@ -0,0 +1,18 @@
+---
+sidebar_position: 0
+---
+
+# Overview
+
+The APIs & SDKs section provides everything you need to integrate ABsmartly into your product.  
+This is the technical foundation that powers experiment assignment, event tracking, feature flags and consistent user experiences across all platforms.
+
+Here you will find:
+- SDK documentation for client side, server side and mobile environments  
+- API references for the ABsmartly platform and the SDKs  
+- implementation guides, examples and best practices  
+- details on exposure handling, goal tracking and variant assignment  
+
+If you are an engineer integrating ABsmartly or maintaining experiment infrastructure, this section is for you.  
+It explains how the SDKs work, how to use the API programmatically and how to build a reliable experimentation setup that fits your architecture.
+

docs/Onboarding/Azure SAML Setup.mdx → docs/Third-party-integrations/SSO/Azure SAML Setup.mdx

@@ -1,4 +1,4 @@
-import Image from '../../src/components/Image';
+import Image from '../../../src/components/Image';
 
 # SAML SSO - Azure
 

docs/Onboarding/Google SAML Setup.mdx → docs/Third-party-integrations/SSO/Google SAML Setup.mdx

@@ -1,4 +1,4 @@
-import Image from '../../src/components/Image';
+import Image from '../../../src/components/Image';
 
 # SAML SSO - Google Workspace
 

docs/Onboarding/Okta SAML Setup.mdx → docs/Third-party-integrations/SSO/Okta SAML Setup.mdx

@@ -1,4 +1,4 @@
-import Image from '../../src/components/Image';
+import Image from '../../../src/components/Image';
 
 # SAML SSO - Okta
 

docs/Third-party-integrations/SSO/_category_.json

@@ -0,0 +1,6 @@
+{
+  "position": 200,
+  "collapsed": true,
+  "collapsible": true,
+  "label": "SSO"
+}

docs/Third-party-integrations/Segment-Integration/index.mdx

@@ -104,7 +104,7 @@ It can be useful to send experiment exposures to Segment for visibility from oth
 By default, the _Track Calls_ mapping will filter and not send any events with the name `Experiment Viewed` to ABsmartly.
 :::
 
-You can [install a custom event logger](/docs/SDK-Documentation/getting-started#using-a-custom-event-logger) in ABsmartly and send exposures directly to Segment.
+You can [install a custom event logger](/docs/APIs-and-SDKs/SDK-Documentation/getting-started#using-a-custom-event-logger) in ABsmartly and send exposures directly to Segment.
 
 <CodeBlock language="javascript">{JsSendingExposuresToSegment}</CodeBlock>
 
@@ -256,7 +256,7 @@ To migrate from the classic ABsmartly destination to ABsmartly (Actions), discon
     for this purpose.
 
     In the ABsmartly context, we can
-    [install a custom event logger](https://docs.absmartly.com/docs/sdk-documentation/getting-started/#using-a-custom-event-logger)
+    [install a custom event logger](https://docs.absmartly.com/docs/APIs-and-SDKs/SDK-Documentation/getting-started/#using-a-custom-event-logger)
     and send exposures directly to Segment.
 
     <CodeBlock language="javascript">{JsSendingExposuresToSegment}</CodeBlock>

docs/Third-party-integrations/Zuko-Integration.mdx

@@ -1,3 +1,7 @@
+---
+sidebar_position: 3
+---
+
 import Image from "../../src/components/Image";
 
 # Zuko Integration
@@ -15,7 +19,7 @@ Zuko to gain deeper insights into how your experiments affect your forms.
 ## Prerequisites
 
 1. **ABsmartly Implementation:** Ensure ABsmartly is correctly implemented on your page. Refer 
-    to the [SDK documentation](/docs/SDK-Documentation/getting-started) for more information.
+    to the [SDK documentation](/docs/APIs-and-SDKs/SDK-Documentation/getting-started) for more information.
 2. **Zuko Account and Tracking:** [Create a Zuko account](https://app.zuko.io/signup) (if 
     you don't have one) and ensure that the tracking is successfully added to your form. Refer to 
     the [Zuko Installation Guides](https://www.zuko.io/guides) for more information.
@@ -61,7 +65,7 @@ attributes into `window.zuko.attributes`. See [Zuko's documentation on setting c
 1. **Run your experiment:** Make sure your experiment is running on ABsmartly and users are being assigned to 
     different variants.
 2. **Submit test forms:** Fill out the forms on your page while participating in the test. You can do this for
-    different variants using the ABsmartly SDKs' [override functionalities](/docs/SDK-Documentation/basic-usage#overriding-treatment-variants).
+    different variants using the ABsmartly SDKs' [override functionalities](/docs/APIs-and-SDKs/SDK-Documentation/basic-usage#overriding-treatment-variants).
 3. **Check Zuko:** Go to your Zuko dashboard and look for the custom attributes you configured in the 
     filters dropdown. You should see attributes like `exp_YourExperimentName` with values corresponding 
     to the assigned variant for each form submission. It might take a few minutes for the data to appear in Zuko.

docs/Third-party-integrations/_category_.json

@@ -1,7 +1,7 @@
 {
-    "position": 6,
+    "position": 3,
     "collapsible": true,
     "collapsed": true,
-    "label": "Third-party integrations"
+    "label": "Integrations"
   }
 

docs/get-started.mdx

@@ -0,0 +1,72 @@
+---
+sidebar_position: 0
+---
+
+# Get Started
+
+Welcome to the ABsmartly Documentation.
+
+ABsmartly is an advanced experimentation and feature flagging platform designed to help teams validate ideas quickly, measure impact reliably and roll out changes safely. The platform provides everything you need to design experiments, expose users consistently, 
+measure impact with robust metrics and make evidence based product decisions.
+
+This documentation will guide you through how to use the platform, integrate it into your product and understand the core concepts behind trustworthy experimentation.
+
+---
+
+## Documentation structure
+
+The documentation is divided into a few main sections to help you find what you need easily.
+
+### Product Documentation
+This [section](./web-console-docs/overview) explains how to use the ABsmartly Web Console to run experiment and feature flags.
+
+You will find guides on:
+- [creating](./web-console-docs/experiments/creating-an-experiment) and managing experiments  
+- defining [goals](./web-console-docs/goals-and-metrics/goals/overview) and [metrics](./web-console-docs/goals-and-metrics/metrics/overview)
+- using [feature flags](./web-console-docs/feature-flags/creating-a-feature)
+- tracking [events](./web-console-docs/events/the-events-page)  
+- managing [users, teams and permissions](./web-console-docs/users-teams-permissions/teams)  
+- configuring workspaces and settings  
+- using the [LaunchPad browser extension](./web-console-docs/launchpad-browser-extension/getting-started)
+
+If you use ABsmartly day to day to run experiments or feature flags, this is where you will spend most of your time.
+
+---
+
+### APIs & SDKs
+
+This [section](./APIs-and-SDKs/overview) contains all technical resources for implementing ABsmartly in your product.
+
+You will find:
+- [SDK documentation](./APIs-and-SDKs/sdk-documentation/) for client side, server side and mobile  
+- [SDK API](./APIs-and-SDKs/SDK-API/absmartly-collector-api) references and examples  
+- The full platform [API reference](./APIs-and-SDKs/SDK-API/absmartly-collector-api) for programmatic access  
+
+Developers and engineers will spend most of their time here.
+
+---
+
+### Integrations
+Using the platform API, ABsmartly can integrate with any tools you already use for analytics, communication and authentication.
+
+This section includes from sample integration:
+- [Slack integration](./Third-party-integrations/Slack-Integration)
+- [Segment integration](./Third-party-integrations/Segment-Integration/) 
+- [Zuko integration](./Third-party-integrations/Zuko-Integration)  
+- [SSO setup](./Third-party-integrations/SSO/Azure%20SAML%20Setup) 
+
+Each guide explains how to connect ABsmartly with your existing systems.
+
+---
+
+
+## What to do next
+
+If you are new to ABsmartly, we recommend starting with:
+1. **Product Documentation → Getting Started**  
+2. **APIs & SDKs** (choose the SDK you need to integrate first)  
+3. **Experiments** to learn how to create, run and analyse your first test  
+
+You can explore the rest of the documentation as you become more familiar with the platform.
+
+Welcome to ABsmartly.