- Publishing in Apify Store |
- Another way to share your Actor with other users is to publish it in Apify Store. When publishing your Actor, you can make it a Paid Actor and get paid by the users benefiting from your tool. For more information, read the publishing and monetization section. |
+ Publishing in Apify Store |
+ Another way to share your Actor with other users is to publish it in Apify Store. When publishing your Actor, you can make it a Paid Actor and get paid by the users benefiting from your tool. For more information, read the publishing and monetization section. |
diff --git a/sources/platform/collaboration/list_of_permissions.md b/sources/platform/8-collaboration/list_of_permissions.md
similarity index 85%
rename from sources/platform/collaboration/list_of_permissions.md
rename to sources/platform/8-collaboration/list_of_permissions.md
index abd7e1cceb..9e05f051dd 100644
--- a/sources/platform/collaboration/list_of_permissions.md
+++ b/sources/platform/8-collaboration/list_of_permissions.md
@@ -13,7 +13,7 @@ This document contains all the access options that can be granted to resources o
## Actors
-To learn about Apify Actors, check out the [documentation](../actors/index.mdx).
+To learn about Apify Actors, check out the [documentation](/platform/using-actors).
### Actor
@@ -34,11 +34,11 @@ To learn about Apify Actors, check out the [documentation](../actors/index.mdx).
| View runs | View a list of Actor task runs and their details. |
| Manage access rights | Manage Actor task access rights. |
-To learn about Actor tasks, see the [documentation](../actors/running/tasks.md).
+To learn about Actor tasks, see the [documentation](///platform/using-actors/tasks).
## Storage
-For more information about Storage, see its [documentation](../storage/index.md).
+For more information about Storage, see its [documentation](/platform/core-concepts/storage).
### Dataset
@@ -48,7 +48,7 @@ For more information about Storage, see its [documentation](../storage/index.md)
| Write | Edit dataset settings, push data to it, and remove the dataset. |
| Manage access rights | Manage dataset access rights. |
-To learn about dataset storage, see its [documentation](../storage/dataset.md).
+To learn about dataset storage, see its [documentation](/platform/core-concepts/storage/dataset).
### Key-value-store
@@ -58,7 +58,7 @@ To learn about dataset storage, see its [documentation](../storage/dataset.md).
| Write | Edit key-value store settings, add, update or remove its records, and delete the key-value store. |
| Manage access rights | Manage key-value store access rights. |
-To learn about key-value stores, see the [documentation](../storage/key_value_store.md).
+To learn about key-value stores, see the [documentation](/platform/core-concepts/storage/key-value-store).
### Request queue
@@ -68,7 +68,7 @@ To learn about key-value stores, see the [documentation](../storage/key_value_st
| Write | Edit request queue settings, add, update, or remove its records, and delete the request queue. |
| Manage access rights | Manage request queue access rights. |
-To learn about request queue storage, see the [documentation](../storage/request_queue.md).
+To learn about request queue storage, see the [documentation](/platform/core-concepts/storage/request-queue).
## Proxy
@@ -76,11 +76,11 @@ To learn about request queue storage, see the [documentation](../storage/request
|------------|---------------------------|
| Proxy | Allow to use Apify Proxy. |
-To learn about Apify Proxy, see its [documentation](../proxy/index.md).
+To learn about Apify Proxy, see its [documentation](/platform/core-concepts/proxy).
## User permissions
-Permissions that can be granted to members of organizations. To learn about the organization account, see its [documentation](./organization_account/index.md).
+Permissions that can be granted to members of organizations. To learn about the organization account, see its [documentation](/platform/collaboration/organization-account).
| Permission | Description |
|---------------------|-----------------------------------------------------------------------|
diff --git a/sources/platform/collaboration/organization_account/how_to_use.md b/sources/platform/8-collaboration/organization_account/how_to_use.md
similarity index 92%
rename from sources/platform/collaboration/organization_account/how_to_use.md
rename to sources/platform/8-collaboration/organization_account/how_to_use.md
index ee54ae198b..495796afef 100644
--- a/sources/platform/collaboration/organization_account/how_to_use.md
+++ b/sources/platform/8-collaboration/organization_account/how_to_use.md
@@ -24,7 +24,7 @@ You can switch into **Organization account** view using the account button in th
In the menu, the account you are currently using is displayed at the top, with all the accounts you can switch to displayed below. When you need to get back to your personal account, you can just switch right back to it—no need to log in and out.
-The resources you can access and account details you can edit will depend on your [permissions](../list_of_permissions.md) in the organization.
+The resources you can access and account details you can edit will depend on your [permissions](/platform/collaboration/list-of-permissions) in the organization.
> When switching between accounts, beware which account you start an Actor run in. If you accidentally start an organization's Actor run in your personal account, the run will be billed to your account (and vice versa).
@@ -44,7 +44,7 @@ The organization, its Actors, and its integrations will keep running as they are
While you cannot manage an organization account's settings and members via API, you can access its Actor and task runs, webhooks, schedules, and storages just as you would with any other account.
-As a member of an organization, you are assigned an [API token](../../integrations/index.mdx) (under the **Integrations** tab) and proxy password (click the **Proxy** button in the left menu) for accessing the Apify platform via REST API.
+As a member of an organization, you are assigned an [API token](/platform/integrations) (under the **Integrations** tab) and proxy password (click the **Proxy** button in the left menu) for accessing the Apify platform via REST API.

diff --git a/sources/platform/collaboration/organization_account/index.md b/sources/platform/8-collaboration/organization_account/index.md
similarity index 77%
rename from sources/platform/collaboration/organization_account/index.md
rename to sources/platform/8-collaboration/organization_account/index.md
index 32842512ec..f915948dc4 100644
--- a/sources/platform/collaboration/organization_account/index.md
+++ b/sources/platform/8-collaboration/organization_account/index.md
@@ -9,14 +9,14 @@ slug: /collaboration/organization-account
---
-Organization accounts allow groups to collaborate on projects. It enables you to manage your team members' [permissions](../list_of_permissions.md) and to centralize your billing without having to share the credentials of a single personal account.
+Organization accounts allow groups to collaborate on projects. It enables you to manage your team members' [permissions](/platform/collaboration/list-of-permissions) and to centralize your billing without having to share the credentials of a single personal account.
-You can [switch](./how_to_use.md) between your personal and organization accounts in just two clicks: in [Apify Console](https://console.apify.com), click the account button in the top-left corner, then select the organization.
+You can [switch](/platform/collaboration/organization-account/how-to-use) between your personal and organization accounts in just two clicks: in [Apify Console](https://console.apify.com), click the account button in the top-left corner, then select the organization.
You can set up an organization in two ways.
* [Create a new organization](#create-a-new-organization). If you don't have integrations set up yet, or if they are easy to change, you can create a new organization, preserving your personal account.
-* [Convert an existing account](#convert-an-existing-account) into an organization. If your Actors and [integrations](../../integrations/index.mdx) are set up in a personal account, it is probably best to convert that account into an organization. This will preserve all your integrations but means you will have a new personal account created for you.
+* [Convert an existing account](#convert-an-existing-account) into an organization. If your Actors and [integrations](/platform/integrations) are set up in a personal account, it is probably best to convert that account into an organization. This will preserve all your integrations but means you will have a new personal account created for you.
> Prefer video to reading? [See our video tutorial](https://www.youtube.com/watch?v=BIL6HqtnvKk) for organization accounts.
@@ -38,7 +38,7 @@ You can create a new organization by clicking the **Create new organization** bu
>
> * **You will no longer be able to sign in to the converted user account.**
> * **An organization cannot be converted back to a personal account.**
-> * **During conversion, a new account (with the same login credentials) will be created for you. You can then use that account to [set up](./setup.md) the organization.**
+> * **During conversion, a new account (with the same login credentials) will be created for you. You can then use that account to [set up](/platform/collaboration/organization-account/setup) the organization.**
Before converting your personal account into an organization, make sure it has a **username**.
@@ -52,7 +52,7 @@ Next, set the organization's name and click **Convert**.
And that's it! Your personal account becomes the organization, and you will be logged out automatically. You can now log into your new personal account with the same credentials as you are currently logged in with. This applies to both **password** and **OAuth** methods.
-For information on [adding members and assigning roles](./setup.md), see the Setup page.
+For information on [adding members and assigning roles](/platform/collaboration/organization-account/setup), see the Setup page.
## Billing {#billing}
diff --git a/sources/platform/collaboration/organization_account/setup.md b/sources/platform/8-collaboration/organization_account/setup.md
similarity index 85%
rename from sources/platform/collaboration/organization_account/setup.md
rename to sources/platform/8-collaboration/organization_account/setup.md
index ab93a7b29e..88c043cc08 100644
--- a/sources/platform/collaboration/organization_account/setup.md
+++ b/sources/platform/8-collaboration/organization_account/setup.md
@@ -41,10 +41,10 @@ To edit the permissions for each role, click on the **Configure permissions** bu
> Each member can only have one role to avoid conflicting permissions.
-You can configure individual permissions for each resource type such as Actors, Actor tasks or storage. Bear in mind that if a user has the **read** permission for [storages](../../storage/index.md), you cannot prevent them from accessing a particular storage (e.g. a certain [dataset](../../storage/index.md)) - they will have access to all of the organization's storages.
+You can configure individual permissions for each resource type such as Actors, Actor tasks or storage. Bear in mind that if a user has the **read** permission for [storages](/platform/core-concepts/storage), you cannot prevent them from accessing a particular storage (e.g. a certain [dataset](/platform/core-concepts/storage)) - they will have access to all of the organization's storages.
**Some permissions have dependencies**. For example, if someone has the **Actor run** permission, it is likely they will also need the **storage write** permission, so they can store the results from their Actor runs.

-[See the full list of permissions](../list_of_permissions.md) that can be granted to Apify resources.
+[See the full list of permissions](/platform/collaboration/list-of-permissions) that can be granted to Apify resources.
diff --git a/sources/platform/9-monitoring/_category_.yml b/sources/platform/9-monitoring/_category_.yml
new file mode 100644
index 0000000000..7205da2906
--- /dev/null
+++ b/sources/platform/9-monitoring/_category_.yml
@@ -0,0 +1,2 @@
+label: 'Monitoring'
+position: 9
diff --git a/sources/platform/monitoring/images/alerts.png b/sources/platform/9-monitoring/images/alerts.png
similarity index 100%
rename from sources/platform/monitoring/images/alerts.png
rename to sources/platform/9-monitoring/images/alerts.png
diff --git a/sources/platform/monitoring/images/daily-run-statuses.png b/sources/platform/9-monitoring/images/daily-run-statuses.png
similarity index 100%
rename from sources/platform/monitoring/images/daily-run-statuses.png
rename to sources/platform/9-monitoring/images/daily-run-statuses.png
diff --git a/sources/platform/monitoring/images/email-notification.png b/sources/platform/9-monitoring/images/email-notification.png
similarity index 100%
rename from sources/platform/monitoring/images/email-notification.png
rename to sources/platform/9-monitoring/images/email-notification.png
diff --git a/sources/platform/monitoring/images/in-app-notification.png b/sources/platform/9-monitoring/images/in-app-notification.png
similarity index 100%
rename from sources/platform/monitoring/images/in-app-notification.png
rename to sources/platform/9-monitoring/images/in-app-notification.png
diff --git a/sources/platform/monitoring/images/metric-options.png b/sources/platform/9-monitoring/images/metric-options.png
similarity index 100%
rename from sources/platform/monitoring/images/metric-options.png
rename to sources/platform/9-monitoring/images/metric-options.png
diff --git a/sources/platform/monitoring/images/monitoring.png b/sources/platform/9-monitoring/images/monitoring.png
similarity index 100%
rename from sources/platform/monitoring/images/monitoring.png
rename to sources/platform/9-monitoring/images/monitoring.png
diff --git a/sources/platform/monitoring/images/notifications.png b/sources/platform/9-monitoring/images/notifications.png
similarity index 100%
rename from sources/platform/monitoring/images/notifications.png
rename to sources/platform/9-monitoring/images/notifications.png
diff --git a/sources/platform/monitoring/images/run-statistics-chart.png b/sources/platform/9-monitoring/images/run-statistics-chart.png
similarity index 100%
rename from sources/platform/monitoring/images/run-statistics-chart.png
rename to sources/platform/9-monitoring/images/run-statistics-chart.png
diff --git a/sources/platform/monitoring/index.md b/sources/platform/9-monitoring/index.md
similarity index 87%
rename from sources/platform/monitoring/index.md
rename to sources/platform/9-monitoring/index.md
index 4cb75ef4f0..369f6a6526 100644
--- a/sources/platform/monitoring/index.md
+++ b/sources/platform/9-monitoring/index.md
@@ -1,8 +1,7 @@
---
title: Monitoring
-description: Learn how to continuously make sure that your Actors and tasks perform as expected and retrieve correct results. Receive alerts when your jobs or their metrics are not as you expect.
-sidebar_position: 12
-category: guides
+description: "Learn how to continuously make sure that your Actors and tasks perform as expected and retrieve correct results. Receive alerts when your jobs or their metrics are not as you expect."
+sidebar_position: 1
slug: /monitoring
---
@@ -49,7 +48,7 @@ When you set up an alert, you have four choices for how you want the metrics to
3. **Alert, when run status is one of following** - This type of alert is checked only after the run finishes. It makes possible to track the status of your finished runs and send an alert if the run finishes in a state you do not expect. If your Actor runs very often and suddenly starts failing, you will receive a single alert after the first failed run in 1 minute, and then aggregated alert every 15 minutes.
-4. **Alert for dataset field statistics** - If you have a [dataset schema](../actors/development/actor_definition/dataset_schema/validation.md) set up, then you can use the field statistics to set up an alert. You can use field statistics for example to track if some field is filled in all records, if some numeric value is too low/high (for example when tracking the price of a product over multiple sources), if the number of items in an array is too low/high (for example alert on Instagram Actor if post has a lot of comments) and many other tasks like these.
+4. **Alert for dataset field statistics** - If you have a [dataset schema](//platform/building-actors/actor-definition/dataset-schema/validation) set up, then you can use the field statistics to set up an alert. You can use field statistics for example to track if some field is filled in all records, if some numeric value is too low/high (for example when tracking the price of a product over multiple sources), if the number of items in an array is too low/high (for example alert on Instagram Actor if post has a lot of comments) and many other tasks like these.
:::important
@@ -108,7 +107,7 @@ These are just a few examples of what you can monitor. It's always recommended t
### Alternative solutions
-For more complex monitoring, you can use the [monitoring suite](https://apify.com/apify/monitoring), which is a collection of [Apify Actors](../actors/index.mdx) that allows you to automate the monitoring of jobs you have running on the [Apify platform](https://apify.com). The monitoring suite offers some features that are not **currently** available in Apify Console, such as:
+For more complex monitoring, you can use the [monitoring suite](https://apify.com/apify/monitoring), which is a collection of Apify Actors that allows you to automate the monitoring of jobs you have running on the [Apify platform](https://apify.com). The monitoring suite offers some features that are not **currently** available in Apify Console, such as:
1. Schema validation of the output
2. Duplicate checks in the output
diff --git a/sources/platform/actors/development/index.md b/sources/platform/actors/development/index.md
deleted file mode 100644
index 3a97539d70..0000000000
--- a/sources/platform/actors/development/index.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Actor development
-desc: Read about the technical part of building Apify Actors. Learn to define Actor inputs, build new versions, persist Actor state, and choose base Docker images.
-sidebar_label: Development
-sidebar_position: 7.4
-slug: /actors/development
----
-
-**Read about the technical part of building Apify Actors. Learn to define Actor inputs, build new versions, persist Actor state, and choose base Docker images.**
-
----
-
-This section will guide you through the whole story of [Actor](../index.mdx) development.
-
-You can follow chapters sequentially from [Quick start](./quick_start/index.mdx), where you learn how to create your first Actor in just a few minutes, through the more technical sections describing the whole Actor model, up to the [Performance](/sources/platform/actors/development/performance.md) section, where you learn how to fine-tune your Actor to get the most out of the Apify platform.
-
-import Card from "@site/src/components/Card";
-import CardGrid from "@site/src/components/CardGrid";
-
-