Feat: Improve ADaaS documentation

fern/docs/pages/airdrop/connecting-to-the-external-system.mdx

@@ -0,0 +1,18 @@
+TODO: Keyring explanation and guide setting up.
+
+## Keyrings
+
+_Keyrings_ are a DevRev-specific mechanism for managing authentication to external systems.
+They are called **Connections** in the DevRev app.
+
+Keyrings provide a secure way to store and manage credentials within your DevRev snap-in.
+This eliminates the need to expose sensitive information like passwords or access tokens directly
+within your code or configuration files, enhancing overall security.
+They also provide a valid token by abstracting OAuth token renewal from the end user.
+
+A keyring is used by a worker to authenticate to the external system in API calls.
+They include the key (for example, a PAT or API key), its type, the organization ID for which a
+key is valid, and in some cases the organization name.
+
+Configure a keyring for the external system in the `manifest.yaml`.
+Refer to [Keyrings](/snapin-development/references/manifest#developer-keyrings) for instructions.

fern/docs/pages/airdrop/development-guide.mdx

@@ -0,0 +1,7 @@
+## Extracting data from external system
+
+TODO: Explain the order of development steps.
+
+## Loading data to DevRev
+
+TODO: Explain the order of development steps.

fern/docs/pages/airdrop/getting-started.mdx

@@ -1,35 +1,54 @@
-## Before you begin
-
-- If you have not created a development organization on DevRev before, create a dedicated
-[DevRev organization for development purposes](https://app.devrev.ai/) where you are
-publishing your Airdrop snap-in.
-- Install required tools and packages:
-  - [devrev-cli](https://developer.devrev.ai/snapin-development/references/cli-install) (version 4.7 or higher)
-  - [jq](https://stedolan.github.io/jq)
-  - [golang](https://go.dev/doc/install)
-  - [nodejs](https://nodejs.org/en/download/package-manager) (version 18.x.x+ or higher)
-
-## Setting up the snap-in
-
-1. Create a new repo from the [Airdrop template repo](https://github.com/devrev/adaas-template).
-Select _Use this template_ and then _Create a new repository_.
-1. Copy `.env.example` to `.env` and fill in the required variables.
-1. Configure a keyring for the external system in the `manifest.yaml`.
-   Refer to [Keyrings](/snapin-development/references/manifest#developer-keyrings) for instructions.
-1. Deploy a draft version of your snap-in to your dev org using `make deploy`.
-1. Install the snap-in in your DevRev at **Settings** > **Snap-ins** > **Install snap-in**.
-1. Define the connection at **Settings** > **Imports** > **Connections**.
-1. Create an import at **Settings** > **Imports** > **Import**.
-
-## Observability
-
-- To observe logs from your snap-in in your development environment:
-   ```
-   devrev snap_in_package logs | jq
-   ```
-- To open logs in your favorite editor:
-  ```
-  devrev snap_in_package logs | code -
-  ```
+## Before You Begin
+
+If this is your first time setting up an organization within DevRev, you'll need to create a dedicated DevRev organization for developing your new Airdrop snap-in:
+
+1. Click on your profile picture in the top left corner.
+2. Navigate to the **Orgs** section and click on **+**.
+3. Fill in the necessary details and click **Create**.
+
+You will now find your newly created organization under **Orgs**.
+
+Install required tools and packages:
+
+- [devrev-cli](https://developer.devrev.ai/snapin-development/references/cli-install) (version 4.7 or higher)
+- [jq](https://stedolan.github.io/jq)
+- [golang](https://go.dev/doc/install)
+- [nodejs](https://nodejs.org/en/download/package-manager) (version 18.x.x+ or higher)
+
+## Setting Up the Snap-in
+
+### Starter Template
+
+DevRev provides a starter template for Airdrop snap-in development.
+
+1. Create a new repository from [Airdrop template repository](https://github.com/devrev/adaas-template) by selecting _Use this template_ and then _Create a new repository_.
+1. Copy `.env.example` to a new file named `.env` and fill in the required variables.
+
+### Local Development
+
+For ease of development, you can run your snap-in locally and receive logs directly in your console. Follow the guide [here](/snapin-development/locally-testing-snap-ins).
+
+### Publishing the snap-in
+
+Once you're ready to launch your snap-in in a production environment, follow these steps:
+
+1. Deploy a draft version of your snap-in to your organization by using `make deploy`.
+1. Install the snap-in in your DevRev by going to **Settings** > **Snap-ins** > **Install snap-in**.
+1. Set up the connection under **Settings** > **Airdrops** > **Connections**.
+1. Create an import at **Settings** > **Airdrops** > **Airdrop**.
+
+#### Observability
+
+To observe logs from your snap-in in your development environment:
+
+```
+devrev snap_in_package logs | jq
+```
+
+To open logs in your favorite editor:
+
+```
+devrev snap_in_package logs | code -
+```
 
 For more information, refer to [Debugging](/snapin-development/debugging).

fern/docs/pages/airdrop/how-does-it-work.mdx

@@ -0,0 +1,5 @@
+TODO: Explain how ADaaS code works by using the template
+
+TODO: Explain the role of manifest.yaml and where is what
+
+TODO: Explain how the communication between snap-in and DevRev works (through emitting events).

fern/docs/pages/airdrop/overview.mdx

@@ -8,9 +8,6 @@ DevRev’s Airdrop functionality.
 It enables developers to create external workers (extractors and loaders) to bring data from various
 external systems.
 
-<Tip>DevRev offers a repository template to help you create Airdrop snap-ins.
-Refer to [Getting started](getting-started) for instructions.</Tip>
-
 ```mermaid
 flowchart TD
 %%{init: {
@@ -57,18 +54,4 @@ An extractor function in the snap-in is responsible for extracting data from the
 A _reverse sync_ is a sync run from DevRev to an external system.
 It uses a loader function, to create or update data in the external system.
 
-## Keyrings
-
-_Keyrings_ are a DevRev-specific mechanism for managing authentication to external systems.
-They are called **Connections** in the DevRev app.
-
-Keyrings provide a secure way to store and manage credentials within your DevRev snap-in.
-This eliminates the need to expose sensitive information like passwords or access tokens directly
-within your code or configuration files, enhancing overall security.
-They also provide a valid token by abstracting OAuth token renewal from the end user.
-
-A keyring is used by a worker to authenticate to the external system in API calls.
-They include the key (for example, a PAT or API key), its type, the organization ID for which a
-key is valid, and in some cases the organization name.
-
-Refer to [Keyrings](/snapin-development/references/keyrings) for more information.
+TODO: 1-way sync, 2-way sync, incremental sync, ...

fern/docs/pages/airdrop/publish-to-marketplace.mdx

@@ -0,0 +1,3 @@
+When you feel like your snap-in is ready to be used by different organizations, you can publish it to the DevRev marketplace.
+
+Follow this [guide](/snapin-development/marketplace-listings).

fern/docs/pages/airdrop/snap-in-examples.mdx

@@ -0,0 +1,5 @@
+You can find snap-in examples for various external systems [here](https://github.com/devrev/adaas-connector-examples).
+
+Examples include:
+
+- Asana

fern/versions/public.yml

@@ -145,6 +145,24 @@ navigation:
           - page: "Getting started"
             slug: getting-started
             path: ../docs/pages/airdrop/getting-started.mdx
+          - page: "How does it work"
+            slug: how-does-it-work
+            path: ../docs/pages/airdrop/how-does-it-work.mdx
+          - page: "Snap-in examples"
+            slug: snap-in-examples
+            path: ../docs/pages/airdrop/snap-in-examples.mdx
+          - page: "Connecting to the external system"
+            slug: connecting-to-the-external-system
+            path: ../docs/pages/airdrop/connecting-to-the-external-system.mdx
+          - section: "Development guide"
+            slug: development-guide
+            contents:
+              - page: "Extracting data from external system"
+                slug: extracting-data
+                path: ../docs/pages/airdrop/development-guide/extracting-data.mdx
+              - page: "Loading data to DevRev"
+                slug: loading-data
+                path: ../docs/pages/airdrop/development-guide/loading-data.mdx
           - page: "Extraction phases"
             slug: extraction-phases
             path: ../docs/pages/airdrop/extraction-phases.mdx
@@ -154,24 +172,27 @@ navigation:
             path: ../docs/pages/airdrop/loading-phases.mdx
           - page: "External sync units extraction"
             slug: external-sync-units-extraction
-            hidden: false
+            hidden: true
             path: ../docs/pages/airdrop/external-sync-units-extraction.mdx
           - page: "Metadata extraction"
-            hidden: false
+            hidden: true
             slug: metadata-extraction
             path: ../docs/pages/airdrop/metadata-extraction.mdx
           - page: "Data extraction"
-            hidden: false
+            hidden: true
             slug: data-extraction
             path: ../docs/pages/airdrop/data-extraction.mdx
           - page: "Attachments extraction"
-            hidden: false
+            hidden: true
             slug: extract-attachments
             path: ../docs/pages/airdrop/attachments-extraction.mdx
           - page: "Data and attachments deletion"
             slug: data-attachments-deletion
-            hidden: false
+            hidden: true
             path: ../docs/pages/airdrop/data-attachments-deletion.mdx
+          - page: "Publish to the marketplace"
+            slug: publish-to-marketplace
+            path: ../docs/pages/airdrop/publish-to-marketplace.mdx
           - page: "Common issues - FAQ"
             slug: faq
             path: ../docs/pages/airdrop/faq.mdx