docs: reorganize integrations sidebar (#1042)

add new sub categories
- Programming
- Actor-to-Actor
- Workflows & notifications
- Data storage
- AI

add _category_.yml to each new folder to control sidebar label and
position
fix all the md links to account for new structure

Author: TC-MO

sources/platform/actors/development/actor_definition/index.md

@@ -23,8 +23,8 @@ Actors have the following elements:
 
 The documentation and the input/output schemas make it possible for people to easily understand what the Actor does, enter the required inputs both in the user interface or API, and integrate the Actor's results with their other workflows. Actors can easily call and interact with each other, enabling building more complex systems on top of simple ones.
 
-The Apify platform provides an open [API](/api/v2), cron-style [scheduler](../../schedules), [webhooks](../../../integrations/webhooks/index.md), and [integrations](../../integrations) to services such as Zapier or Make, which make it easy for users to integrate Actors with their existing workflows. Anyone is welcome to [publish Actors](/platform/actors/publishing) in [Apify Store](https://apify.com/store), and you can even [monetize your Actors](/platform/actors/publishing/monetize).
+The Apify platform provides an open [API](/api/v2), cron-style [scheduler](../../schedules), [webhooks](../../../integrations/programming/webhooks/index.md), and [integrations](../../integrations) to services such as Zapier or Make, which make it easy for users to integrate Actors with their existing workflows. Anyone is welcome to [publish Actors](/platform/actors/publishing) in [Apify Store](https://apify.com/store), and you can even [monetize your Actors](/platform/actors/publishing/monetize).
 
-Actors can be developed and run locally and then easily deployed to the Apify platform using the [Apify CLI](/cli) or a [GitHub integration](../../../integrations/github.md). For more details, see the [Deployment](../deployment/index.md) section.
+Actors can be developed and run locally and then easily deployed to the Apify platform using the [Apify CLI](/cli) or a [GitHub integration](../../../integrations/programming/github.md). For more details, see the [Deployment](../deployment/index.md) section.
 
 > **To get a better idea of what Apify Actors are, visit [Apify Store](https://apify.com/store), and try out some of them!**

sources/platform/actors/development/deployment/source_types.md

@@ -34,7 +34,7 @@ To specify a Git branch or tag to check out, add a URL fragment to the URL. For
 
 Optionally, the second part of the fragment in the Git URL (separated by a colon) specifies the directory from which the Actor will be built (and where the `.actor`) folder is located. For example, `https://github.com/jancurn/some-actor.git#develop:some/dir` will check out the **develop** branch and set **some/dir** as the root directory of the Actor.
 
-Note that you can easily set up an integration where the Actor is automatically rebuilt on every commit to the Git repository. For more details, see [GitHub integration](../../../integrations/github.md).
+Note that you can easily set up an integration where the Actor is automatically rebuilt on every commit to the Git repository. For more details, see [GitHub integration](../../../integrations/programming/github.md).
 
 ### [](#private-repositories)Private repositories
 

sources/platform/integrations/actors/_category_.yml

@@ -0,0 +1 @@
+position: 3

sources/platform/integrations/actors/index.md

@@ -1,7 +1,7 @@
 ---
-title: Actors
+title: Actor-to-Actor
 description: Learn how to integrate with other Actors and tasks.
-sidebar_position: 11.10
+sidebar_label: Actor-to-Actor
 slug: /integrations/actors
 ---
 

sources/platform/integrations/actors/integration_ready_actors.md

@@ -1,5 +1,5 @@
 ---
-title: Integration-ready Actors
+title: Creating integration Actors
 description: Learn how to create Actors that are ready to be integrated with other Actors and tasks.
 sidebar_position: 1
 slug: /integrations/actors/integration-ready-actors

sources/platform/integrations/ai/_category_.yml

@@ -0,0 +1,2 @@
+label: 'AI'
+position: 6

sources/platform/integrations/flowise.md renamed to sources/platform/integrations/ai/flowise.md

@@ -1,7 +1,8 @@
 ---
-title: Flowise
+title: Flowise integration
 description: Learn how to integrate Apify with Flowise.
-sidebar_position: 11.20
+sidebar_label: Flowise
+sidebar_position: 3
 slug: /integrations/flowise
 ---
 
@@ -43,23 +44,23 @@ The first step is to create a new flow in the web UI.
 
 In the left menu, you need to find Apify Website Content Crawler under Document Loaders.
 
-![Flowise add Apify Crawler](./images/flowise-apify.png)
+![Flowise add Apify Crawler](../images/flowise-apify.png)
 
 Now you need to configure the crawler. You can find more information about the crawler [here](https://apify.com/apify/website-content-crawler).
 
-![Flowise and Apify](images/flowise.png)
+![Flowise and Apify](../images/flowise.png)
 
 In the configuration, provide your Apify API token, which you can find in your [Apify account](https://my.apify.com/account#/integrations).
 
-![Apify API token screen](./images/flowise-apify-api.png)
+![Apify API token screen].(./images/flowise-apify-api.png)
 
 You can add more loaders, or you can add some processors to process the data.
 In our case, we create the flow that loads data from the Apify docs using Website Content Crawler and save them into the in-memory vector database.
 Connect the ChatOpenAI and the OpenAI embeddings and QA retrieval into the chatbot.
 
 The final flow can answer questions about Apify docs.
 
-![Flowise and Apify](images/flowise-2.png)
+![Flowise and Apify](../images/flowise-2.png)
 
 For more information visit the Flowise [documentation](https://flowiseai.com/).
 

sources/platform/integrations/langchain.md renamed to sources/platform/integrations/ai/langchain.md

@@ -1,8 +1,8 @@
 ---
-title: 🦜🔗 LangChain
+title: 🦜🔗 LangChain integration
 sidebar_label: LangChain
 description: Learn how to integrate Apify with 🦜🔗 LangChain, in order to feed vector databases and LLMs with data crawled from the web.
-sidebar_position: 11.19
+sidebar_position: 1
 slug: /integrations/langchain
 ---
 

sources/platform/integrations/llama.md renamed to sources/platform/integrations/ai/llama.md

@@ -1,7 +1,8 @@
 ---
-title: LlamaIndex
+title: LlamaIndex integration
 description: Learn how to integrate Apify with LlamaIndex in order to feed vector databases and LLMs with data crawled from the web.
-sidebar_position: 11.21
+sidebar_label: Llamaindex
+sidebar_position: 2
 slug: /integrations/llama
 ---
 

sources/platform/integrations/pinecone.md renamed to sources/platform/integrations/ai/pinecone.md

@@ -1,7 +1,8 @@
 ---
-title: Pinecone
+title: Pinecone integration
 description: Learn how to integrate Apify with Pinecone to feed data crawled from the web into the Pinecone vector database.
-sidebar_position: 11.22
+sidebar_label: Pinecone
+sidebar_position: 4
 slug: /integrations/pinecone
 toc_min_heading_level: 2
 toc_max_heading_level: 4
@@ -41,11 +42,11 @@ The examples utilize the Website Content Crawler Actor, which deeply crawls webs
 
 1. Once you have the crawler ready, navigate to the integration section and add Apify’s Pinecone integration.
 
-    ![Website Content Crawler with Pinecone integration](./images/pinecone-wcc-integration.png)
+    ![Website Content Crawler with Pinecone integration](../images/pinecone-wcc-integration.png)
 
 1. Select when to trigger this integration (typically when a run succeeds) and fill in all the required fields for the Pinecone integration. You can learn more about the input parameters at the [Pinecone integration input schema](https://apify.com/jan.turon/pinecone-integration/input-schema).
 
-   ![Pinecone integration configuration](./images/pinecone-integration-setup.png)
+   ![Pinecone integration configuration](../images/pinecone-integration-setup.png)
 
 1. For a comprehensive explanation on how to combine Actors to accomplish more complex tasks, refer to the guide on [Actor-to-Actor](https://blog.apify.com/connecting-scrapers-apify-integration/) integrations.