diff --git a/.github/workflows/docs.yaml b/.github/workflows/docs.yaml
index ae2a53c0a..4811102d2 100644
--- a/.github/workflows/docs.yaml
+++ b/.github/workflows/docs.yaml
@@ -41,6 +41,8 @@ jobs:
               run: |
                   # install project deps
                   yarn
+                  # update next docs reference
+                  yarn update-docs
                   # go to website dir
                   cd website
                   # install website deps
diff --git a/docs/reference.md b/docs/reference.md
index 1268815ac..d736e4196 100644
--- a/docs/reference.md
+++ b/docs/reference.md
@@ -12,13 +12,40 @@ This section contains printouts of `apify help` for all commands.
 * [`apify actor push-data [ITEM]`](#apify-actor-push-data-item)
 * [`apify actor set-value KEY [VALUE]`](#apify-actor-set-value-key-value)
 * [`apify actors`](#apify-actors)
+* [`apify actors build [ACTORID]`](#apify-actors-build-actorid)
+* [`apify actors call [ACTORID]`](#apify-actors-call-actorid)
+* [`apify actors ls`](#apify-actors-ls)
+* [`apify actors pull [ACTORID]`](#apify-actors-pull-actorid)
+* [`apify actors push [ACTORID]`](#apify-actors-push-actorid)
+* [`apify actors rm ACTORID`](#apify-actors-rm-actorid)
+* [`apify actors start [ACTORID]`](#apify-actors-start-actorid)
+* [`apify builds`](#apify-builds)
+* [`apify builds create [ACTORID]`](#apify-builds-create-actorid)
+* [`apify builds info BUILDID`](#apify-builds-info-buildid)
+* [`apify builds log BUILDID`](#apify-builds-log-buildid)
+* [`apify builds ls [ACTORID]`](#apify-builds-ls-actorid)
+* [`apify builds rm BUILDID`](#apify-builds-rm-buildid)
 * [`apify call [ACTORID]`](#apify-call-actorid)
 * [`apify create [ACTORNAME]`](#apify-create-actorname)
 * [`apify datasets`](#apify-datasets)
+* [`apify datasets create [DATASETNAME]`](#apify-datasets-create-datasetname)
+* [`apify datasets get-items DATASETID`](#apify-datasets-get-items-datasetid)
+* [`apify datasets ls`](#apify-datasets-ls)
+* [`apify datasets push-items NAMEORID ITEM`](#apify-datasets-push-items-nameorid-item)
+* [`apify datasets rename NAMEORID [NEWNAME]`](#apify-datasets-rename-nameorid-newname)
+* [`apify datasets rm DATASETNAMEORID`](#apify-datasets-rm-datasetnameorid)
 * [`apify help [COMMAND]`](#apify-help-command)
 * [`apify info`](#apify-info)
 * [`apify init [ACTORNAME]`](#apify-init-actorname)
 * [`apify key-value-stores`](#apify-key-value-stores)
+* [`apify key-value-stores create [KEYVALUESTORENAME]`](#apify-key-value-stores-create-keyvaluestorename)
+* [`apify key-value-stores delete-value STOREID ITEMKEY`](#apify-key-value-stores-delete-value-storeid-itemkey)
+* [`apify key-value-stores get-value KEYVALUESTOREID ITEMKEY`](#apify-key-value-stores-get-value-keyvaluestoreid-itemkey)
+* [`apify key-value-stores keys STOREID`](#apify-key-value-stores-keys-storeid)
+* [`apify key-value-stores ls`](#apify-key-value-stores-ls)
+* [`apify key-value-stores rename KEYVALUESTORENAMEORID [NEWNAME]`](#apify-key-value-stores-rename-keyvaluestorenameorid-newname)
+* [`apify key-value-stores rm KEYVALUESTORENAMEORID`](#apify-key-value-stores-rm-keyvaluestorenameorid)
+* [`apify key-value-stores set-value STOREID ITEMKEY [VALUE]`](#apify-key-value-stores-set-value-storeid-itemkey-value)
 * [`apify login`](#apify-login)
 * [`apify logout`](#apify-logout)
 * [`apify pull [ACTORID]`](#apify-pull-actorid)
@@ -26,6 +53,12 @@ This section contains printouts of `apify help` for all commands.
 * [`apify request-queues`](#apify-request-queues)
 * [`apify run`](#apify-run)
 * [`apify runs`](#apify-runs)
+* [`apify runs abort RUNID`](#apify-runs-abort-runid)
+* [`apify runs info RUNID`](#apify-runs-info-runid)
+* [`apify runs log RUNID`](#apify-runs-log-runid)
+* [`apify runs ls [ACTORID]`](#apify-runs-ls-actorid)
+* [`apify runs resurrect RUNID`](#apify-runs-resurrect-runid)
+* [`apify runs rm RUNID`](#apify-runs-rm-runid)
 * [`apify secrets`](#apify-secrets)
 * [`apify secrets add NAME VALUE`](#apify-secrets-add-name-value)
 * [`apify secrets rm NAME`](#apify-secrets-rm-name)
@@ -45,7 +78,7 @@ DESCRIPTION
   Commands are designed to be used in Actor runs. All commands are in PoC state, do not use in production environments.
 ```
 
-_See code: [src/commands/actor/index.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/actor/index.ts)_
+_See code: [src/commands/actor/index.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actor/index.ts)_
 
 ## `apify actor get-input`
 
@@ -59,7 +92,7 @@ DESCRIPTION
   Gets the Actor input value from the default key-value store associated with the Actor run.
 ```
 
-_See code: [src/commands/actor/get-input.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/actor/get-input.ts)_
+_See code: [src/commands/actor/get-input.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actor/get-input.ts)_
 
 ## `apify actor get-value KEY`
 
@@ -76,7 +109,7 @@ DESCRIPTION
   Gets a value from the default key-value store associated with the Actor run.
 ```
 
-_See code: [src/commands/actor/get-value.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/actor/get-value.ts)_
+_See code: [src/commands/actor/get-value.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actor/get-value.ts)_
 
 ## `apify actor push-data [ITEM]`
 
@@ -98,7 +131,7 @@ DESCRIPTION
   $ cat ./test.json | apify actor push-data
 ```
 
-_See code: [src/commands/actor/push-data.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/actor/push-data.ts)_
+_See code: [src/commands/actor/push-data.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actor/push-data.ts)_
 
 ## `apify actor set-value KEY [VALUE]`
 
@@ -127,7 +160,7 @@ DESCRIPTION
   $ cat ./my-text-file.txt | apify actor set-value KEY --contentType text/plain
 ```
 
-_See code: [src/commands/actor/set-value.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/actor/set-value.ts)_
+_See code: [src/commands/actor/set-value.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actor/set-value.ts)_
 
 ## `apify actors`
 
@@ -141,7 +174,320 @@ DESCRIPTION
   Commands are designed to be used with Actors.
 ```
 
-_See code: [src/commands/actors/index.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/actors/index.ts)_
+_See code: [src/commands/actors/index.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actors/index.ts)_
+
+## `apify actors build [ACTORID]`
+
+Creates a new build of the Actor.
+
+```
+USAGE
+  $ apify actors build [ACTORID] [--json] [--tag <value>] [--version <value>] [--log]
+
+ARGUMENTS
+  ACTORID  Optional Actor ID or Name to trigger a build for. By default, it will use the Actor from the current
+           directory.
+
+FLAGS
+  --log              Whether to print out the build log after the build is triggered.
+  --tag=<value>      Build tag to be applied to the successful Actor build. By default, this is "latest".
+  --version=<value>  Optional Actor Version to build. By default, this will be inferred from the tag, but this flag is
+                     required when multiple versions have the same tag.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Creates a new build of the Actor.
+```
+
+_See code: [src/commands/actors/build.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actors/build.ts)_
+
+## `apify actors call [ACTORID]`
+
+Runs a specific Actor remotely on the Apify cloud platform.
+
+```
+USAGE
+  $ apify actors call [ACTORID] [--json] [-b <value>] [-t <value>] [-m <value>] [-i <value> | --input-file
+    <value>] [-s] [-o]
+
+ARGUMENTS
+  ACTORID  Name or ID of the Actor to run (e.g. "my-actor", "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not
+           provided, the command runs the remote Actor specified in the ".actor/actor.json" file.
+
+FLAGS
+  -b, --build=<value>       Tag or number of the build to run (e.g. "latest" or "1.2.34").
+  -i, --input=<value>       Optional JSON input to be given to the Actor.
+  -m, --memory=<value>      Amount of memory allocated for the Actor run, in megabytes.
+  -o, --output-dataset      Prints out the entire default dataset on successful run of the Actor.
+  -s, --silent              Prevents printing the logs of the Actor run to the console.
+  -t, --timeout=<value>     Timeout for the Actor run in seconds. Zero value means there is no timeout.
+      --input-file=<value>  Optional path to a file with JSON input to be given to the Actor. The file must be a valid
+                            JSON file. You can also specify `-` to read from standard input.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Runs a specific Actor remotely on the Apify cloud platform.
+  The Actor is run under your current Apify account. Therefore you need to be logged in by calling "apify login". It
+  takes input for the Actor from the default local key-value store by default.
+```
+
+_See code: [src/commands/actors/call.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actors/call.ts)_
+
+## `apify actors ls`
+
+Lists all recently ran Actors or your own Actors.
+
+```
+USAGE
+  $ apify actors ls [--json] [--my] [--offset <value>] [--limit <value>] [--desc]
+
+FLAGS
+  --desc            Sort Actors in descending order.
+  --limit=<value>   [default: 20] Number of Actors that will be listed.
+  --my              Whether to list Actors made by the logged in user.
+  --offset=<value>  Number of Actors that will be skipped.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Lists all recently ran Actors or your own Actors.
+```
+
+_See code: [src/commands/actors/ls.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actors/ls.ts)_
+
+## `apify actors pull [ACTORID]`
+
+Pulls an Actor from the Apify platform to the current directory. If it is defined as Git repository, it will be cloned. If it is defined as Web IDE, it will fetch the files.
+
+```
+USAGE
+  $ apify actors pull [ACTORID] [-v <value>] [--dir <value>]
+
+ARGUMENTS
+  ACTORID  Name or ID of the Actor to run (e.g. "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not provided, the
+           command will update the Actor in the current directory based on its name in ".actor/actor.json" file.
+
+FLAGS
+  -v, --version=<value>  Actor version number which will be pulled, e.g. 1.2. Default: the highest version
+      --dir=<value>      Directory where the Actor should be pulled to
+
+DESCRIPTION
+  Pulls an Actor from the Apify platform to the current directory. If it is defined as Git repository, it will be
+  cloned. If it is defined as Web IDE, it will fetch the files.
+```
+
+_See code: [src/commands/actors/pull.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actors/pull.ts)_
+
+## `apify actors push [ACTORID]`
+
+Uploads the Actor to the Apify platform and builds it there.
+
+```
+USAGE
+  $ apify actors push [ACTORID] [-v <value>] [-b <value>] [-w <value>] [--no-prompt] [--force] [--dir <value>]
+
+ARGUMENTS
+  ACTORID  Name or ID of the Actor to push (e.g. "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not provided, the
+           command will create or modify the Actor with the name specified in ".actor/actor.json" file.
+
+FLAGS
+  -b, --build-tag=<value>        Build tag to be applied to the successful Actor build. By default, it is taken from the
+                                 ".actor/actor.json" file
+  -v, --version=<value>          Actor version number to which the files should be pushed. By default, it is taken from
+                                 the ".actor/actor.json" file.
+  -w, --wait-for-finish=<value>  Seconds for waiting to build to finish, if no value passed, it waits forever.
+      --dir=<value>              Directory where the Actor is located
+      --force                    Push an Actor even when the local files are older than the Actor on the platform.
+      --no-prompt                Do not prompt for opening the Actor details in a browser. This will also not open the
+                                 browser automatically.
+
+DESCRIPTION
+  Uploads the Actor to the Apify platform and builds it there.
+  The Actor settings are read from the ".actor/actor.json" file in the current directory, but they can be overridden
+  using command-line options.
+  NOTE: If the source files are smaller than 3 MB then they are uploaded as
+  "Multiple source files", otherwise they are uploaded as "Zip file".
+
+  When there's an attempt to push files that are older than the Actor on the platform, the command will fail. Can be
+  overwritten with --force flag.
+```
+
+_See code: [src/commands/actors/push.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actors/push.ts)_
+
+## `apify actors rm ACTORID`
+
+Deletes an Actor.
+
+```
+USAGE
+  $ apify actors rm ACTORID
+
+ARGUMENTS
+  ACTORID  The Actor ID to delete.
+
+DESCRIPTION
+  Deletes an Actor.
+```
+
+_See code: [src/commands/actors/rm.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actors/rm.ts)_
+
+## `apify actors start [ACTORID]`
+
+Runs a specific Actor remotely on the Apify cloud platform and immediately returns information about the run.
+
+```
+USAGE
+  $ apify actors start [ACTORID] [--json] [-b <value>] [-t <value>] [-m <value>] [-i <value> | --input-file
+    <value>]
+
+ARGUMENTS
+  ACTORID  Name or ID of the Actor to run (e.g. "my-actor", "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not
+           provided, the command runs the remote Actor specified in the ".actor/actor.json" file.
+
+FLAGS
+  -b, --build=<value>       Tag or number of the build to run (e.g. "latest" or "1.2.34").
+  -i, --input=<value>       Optional JSON input to be given to the Actor.
+  -m, --memory=<value>      Amount of memory allocated for the Actor run, in megabytes.
+  -t, --timeout=<value>     Timeout for the Actor run in seconds. Zero value means there is no timeout.
+      --input-file=<value>  Optional path to a file with JSON input to be given to the Actor. The file must be a valid
+                            JSON file. You can also specify `-` to read from standard input.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Runs a specific Actor remotely on the Apify cloud platform and immediately returns information about the run.
+  The Actor is run under your current Apify account. Therefore you need to be logged in by calling "apify login". It
+  takes input for the Actor from the default local key-value store by default.
+```
+
+_See code: [src/commands/actors/start.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/actors/start.ts)_
+
+## `apify builds`
+
+Commands are designed to be used with Actor Builds.
+
+```
+USAGE
+  $ apify builds
+
+DESCRIPTION
+  Commands are designed to be used with Actor Builds.
+```
+
+_See code: [src/commands/builds/index.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/builds/index.ts)_
+
+## `apify builds create [ACTORID]`
+
+Creates a new build of the Actor.
+
+```
+USAGE
+  $ apify builds create [ACTORID] [--json] [--tag <value>] [--version <value>] [--log]
+
+ARGUMENTS
+  ACTORID  Optional Actor ID or Name to trigger a build for. By default, it will use the Actor from the current
+           directory.
+
+FLAGS
+  --log              Whether to print out the build log after the build is triggered.
+  --tag=<value>      Build tag to be applied to the successful Actor build. By default, this is "latest".
+  --version=<value>  Optional Actor Version to build. By default, this will be inferred from the tag, but this flag is
+                     required when multiple versions have the same tag.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Creates a new build of the Actor.
+```
+
+_See code: [src/commands/builds/create.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/builds/create.ts)_
+
+## `apify builds info BUILDID`
+
+Prints information about a specific build.
+
+```
+USAGE
+  $ apify builds info BUILDID [--json]
+
+ARGUMENTS
+  BUILDID  The build ID to get information about.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Prints information about a specific build.
+```
+
+_See code: [src/commands/builds/info.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/builds/info.ts)_
+
+## `apify builds log BUILDID`
+
+Prints the log of a specific build.
+
+```
+USAGE
+  $ apify builds log BUILDID
+
+ARGUMENTS
+  BUILDID  The build ID to get the log from.
+
+DESCRIPTION
+  Prints the log of a specific build.
+```
+
+_See code: [src/commands/builds/log.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/builds/log.ts)_
+
+## `apify builds ls [ACTORID]`
+
+Lists all builds of the Actor.
+
+```
+USAGE
+  $ apify builds ls [ACTORID] [--json] [--offset <value>] [--limit <value>] [--desc] [-c]
+
+ARGUMENTS
+  ACTORID  Optional Actor ID or Name to list runs for. By default, it will use the Actor from the current directory.
+
+FLAGS
+  -c, --compact         Display a compact table.
+      --desc            Sort builds in descending order.
+      --limit=<value>   [default: 10] Number of builds that will be listed.
+      --offset=<value>  Number of builds that will be skipped.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Lists all builds of the Actor.
+```
+
+_See code: [src/commands/builds/ls.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/builds/ls.ts)_
+
+## `apify builds rm BUILDID`
+
+Deletes an Actor Build.
+
+```
+USAGE
+  $ apify builds rm BUILDID
+
+ARGUMENTS
+  BUILDID  The build ID to delete.
+
+DESCRIPTION
+  Deletes an Actor Build.
+```
+
+_See code: [src/commands/builds/rm.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/builds/rm.ts)_
 
 ## `apify call [ACTORID]`
 
@@ -149,7 +495,7 @@ Runs a specific Actor remotely on the Apify cloud platform.
 
 ```
 USAGE
-  $ apify call [ACTORID] [-b <value>] [-t <value>] [-m <value>] [-w <value>] [-i <value> | --input-file
+  $ apify call [ACTORID] [--json] [-b <value>] [-t <value>] [-m <value>] [-i <value> | --input-file
     <value>] [-s] [-o]
 
 ARGUMENTS
@@ -157,15 +503,17 @@ ARGUMENTS
            provided, the command runs the remote Actor specified in the ".actor/actor.json" file.
 
 FLAGS
-  -b, --build=<value>            Tag or number of the build to run (e.g. "latest" or "1.2.34").
-  -i, --input=<value>            Optional JSON input to be given to the Actor.
-  -m, --memory=<value>           Amount of memory allocated for the Actor run, in megabytes.
-  -o, --output-dataset           Prints out the entire default dataset on successful run of the Actor.
-  -s, --silent                   Prevents printing the logs of the Actor run to the console.
-  -t, --timeout=<value>          Timeout for the Actor run in seconds. Zero value means there is no timeout.
-  -w, --wait-for-finish=<value>  Seconds for waiting to run to finish, if no value passed, it waits forever.
-      --input-file=<value>       Optional path to a file with JSON input to be given to the Actor. The file must be a
-                                 valid JSON file. You can also specify `-` to read from standard input.
+  -b, --build=<value>       Tag or number of the build to run (e.g. "latest" or "1.2.34").
+  -i, --input=<value>       Optional JSON input to be given to the Actor.
+  -m, --memory=<value>      Amount of memory allocated for the Actor run, in megabytes.
+  -o, --output-dataset      Prints out the entire default dataset on successful run of the Actor.
+  -s, --silent              Prevents printing the logs of the Actor run to the console.
+  -t, --timeout=<value>     Timeout for the Actor run in seconds. Zero value means there is no timeout.
+      --input-file=<value>  Optional path to a file with JSON input to be given to the Actor. The file must be a valid
+                            JSON file. You can also specify `-` to read from standard input.
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
   Runs a specific Actor remotely on the Apify cloud platform.
@@ -173,7 +521,7 @@ DESCRIPTION
   takes input for the Actor from the default local key-value store by default.
 ```
 
-_See code: [src/commands/call.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/call.ts)_
+_See code: [src/commands/call.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/call.ts)_
 
 ## `apify create [ACTORNAME]`
 
@@ -198,7 +546,7 @@ DESCRIPTION
   Creates a new Actor project directory from a selected boilerplate template.
 ```
 
-_See code: [src/commands/create.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/create.ts)_
+_See code: [src/commands/create.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/create.ts)_
 
 ## `apify datasets`
 
@@ -212,7 +560,129 @@ DESCRIPTION
   Commands are designed to be used with Datasets.
 ```
 
-_See code: [src/commands/datasets/index.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/datasets/index.ts)_
+_See code: [src/commands/datasets/index.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/datasets/index.ts)_
+
+## `apify datasets create [DATASETNAME]`
+
+Creates a new Dataset on your account
+
+```
+USAGE
+  $ apify datasets create [DATASETNAME] [--json]
+
+ARGUMENTS
+  DATASETNAME  Optional name for the Dataset
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Creates a new Dataset on your account
+```
+
+_See code: [src/commands/datasets/create.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/datasets/create.ts)_
+
+## `apify datasets get-items DATASETID`
+
+Exports the items present in a Dataset.
+
+```
+USAGE
+  $ apify datasets get-items DATASETID [--limit <value>] [--offset <value>] [--format json|jsonl|csv|html|rss|xml|xlsx]
+
+ARGUMENTS
+  DATASETID  The ID of the Dataset to export the items for
+
+FLAGS
+  --format=<option>  [default: json] The format of the returned output. By default, it is set to 'json'
+                     <options: json|jsonl|csv|html|rss|xml|xlsx>
+  --limit=<value>    The amount of elements to get from the dataset. By default, it will return all available items.
+  --offset=<value>   The offset in the dataset where to start getting items.
+
+DESCRIPTION
+  Exports the items present in a Dataset.
+```
+
+_See code: [src/commands/datasets/get-items.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/datasets/get-items.ts)_
+
+## `apify datasets ls`
+
+Lists all Datasets on your account.
+
+```
+USAGE
+  $ apify datasets ls [--json] [--offset <value>] [--limit <value>] [--desc] [--unnamed]
+
+FLAGS
+  --desc            Sorts Datasets in descending order.
+  --limit=<value>   [default: 20] Number of Datasets that will be listed.
+  --offset=<value>  Number of Datasets that will be skipped.
+  --unnamed         Lists Datasets that don't have a name set.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Lists all Datasets on your account.
+```
+
+_See code: [src/commands/datasets/ls.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/datasets/ls.ts)_
+
+## `apify datasets push-items NAMEORID ITEM`
+
+Pushes an object or an array of objects to the provided Dataset.
+
+```
+USAGE
+  $ apify datasets push-items NAMEORID ITEM
+
+ARGUMENTS
+  NAMEORID  The Dataset ID or name to push the objects to
+  ITEM      The object or array of objects to be pushed.
+
+DESCRIPTION
+  Pushes an object or an array of objects to the provided Dataset.
+```
+
+_See code: [src/commands/datasets/push-items.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/datasets/push-items.ts)_
+
+## `apify datasets rename NAMEORID [NEWNAME]`
+
+Renames a Dataset, or removes its unique name
+
+```
+USAGE
+  $ apify datasets rename NAMEORID [NEWNAME] [--unname]
+
+ARGUMENTS
+  NAMEORID  The Dataset ID or name to delete
+  NEWNAME   The new name for the Dataset
+
+FLAGS
+  --unname  Removes the unique name of the Dataset
+
+DESCRIPTION
+  Renames a Dataset, or removes its unique name
+```
+
+_See code: [src/commands/datasets/rename.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/datasets/rename.ts)_
+
+## `apify datasets rm DATASETNAMEORID`
+
+Deletes a Dataset
+
+```
+USAGE
+  $ apify datasets rm DATASETNAMEORID
+
+ARGUMENTS
+  DATASETNAMEORID  The Dataset ID or name to delete
+
+DESCRIPTION
+  Deletes a Dataset
+```
+
+_See code: [src/commands/datasets/rm.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/datasets/rm.ts)_
 
 ## `apify help [COMMAND]`
 
@@ -232,7 +702,7 @@ DESCRIPTION
   Display help for apify.
 ```
 
-_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v6.2.10/src/commands/help.ts)_
+_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v6.2.16/src/commands/help.ts)_
 
 ## `apify info`
 
@@ -247,7 +717,7 @@ DESCRIPTION
   The information is printed to the console.
 ```
 
-_See code: [src/commands/info.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/info.ts)_
+_See code: [src/commands/info.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/info.ts)_
 
 ## `apify init [ACTORNAME]`
 
@@ -275,7 +745,7 @@ DESCRIPTION
   WARNING: The directory at "storage" will be overwritten if it already exists.
 ```
 
-_See code: [src/commands/init.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/init.ts)_
+_See code: [src/commands/init.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/init.ts)_
 
 ## `apify key-value-stores`
 
@@ -287,9 +757,178 @@ USAGE
 
 DESCRIPTION
   Commands are designed to be used with Key Value Stores.
+
+  Aliases: kvs
+```
+
+_See code: [src/commands/key-value-stores/index.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/key-value-stores/index.ts)_
+
+## `apify key-value-stores create [KEYVALUESTORENAME]`
+
+Creates a new Key-value store on your account
+
+```
+USAGE
+  $ apify key-value-stores create [KEYVALUESTORENAME] [--json]
+
+ARGUMENTS
+  KEYVALUESTORENAME  Optional name for the Key-value store
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Creates a new Key-value store on your account
+```
+
+_See code: [src/commands/key-value-stores/create.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/key-value-stores/create.ts)_
+
+## `apify key-value-stores delete-value STOREID ITEMKEY`
+
+Delete a value from a key-value store.
+
+```
+USAGE
+  $ apify key-value-stores delete-value STOREID ITEMKEY
+
+ARGUMENTS
+  STOREID  The key-value store ID to delete the value from.
+  ITEMKEY  The key of the item in the key-value store.
+
+DESCRIPTION
+  Delete a value from a key-value store.
+```
+
+_See code: [src/commands/key-value-stores/delete-value.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/key-value-stores/delete-value.ts)_
+
+## `apify key-value-stores get-value KEYVALUESTOREID ITEMKEY`
+
+Gets a value by key in the given key-value store.
+
+```
+USAGE
+  $ apify key-value-stores get-value KEYVALUESTOREID ITEMKEY [--only-content-type]
+
+ARGUMENTS
+  KEYVALUESTOREID  The key-value store ID to get the value from.
+  ITEMKEY          The key of the item in the key-value store.
+
+FLAGS
+  --only-content-type  Only return the content type of the specified key
+
+DESCRIPTION
+  Gets a value by key in the given key-value store.
+```
+
+_See code: [src/commands/key-value-stores/get-value.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/key-value-stores/get-value.ts)_
+
+## `apify key-value-stores keys STOREID`
+
+Lists all keys in a key-value store.
+
+```
+USAGE
+  $ apify key-value-stores keys STOREID [--json] [--limit <value>] [--exclusive-start-key <value>]
+
+ARGUMENTS
+  STOREID  The key-value store ID to list keys for.
+
+FLAGS
+  --exclusive-start-key=<value>  The key to start the list from.
+  --limit=<value>                [default: 20] The maximum number of keys to return.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Lists all keys in a key-value store.
+```
+
+_See code: [src/commands/key-value-stores/keys.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/key-value-stores/keys.ts)_
+
+## `apify key-value-stores ls`
+
+Lists all Key-value stores on your account.
+
+```
+USAGE
+  $ apify key-value-stores ls [--json] [--offset <value>] [--limit <value>] [--desc] [--unnamed]
+
+FLAGS
+  --desc            Sorts Key-value stores in descending order.
+  --limit=<value>   [default: 20] Number of Key-value stores that will be listed.
+  --offset=<value>  Number of Key-value stores that will be skipped.
+  --unnamed         Lists Key-value stores that don't have a name set.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Lists all Key-value stores on your account.
+```
+
+_See code: [src/commands/key-value-stores/ls.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/key-value-stores/ls.ts)_
+
+## `apify key-value-stores rename KEYVALUESTORENAMEORID [NEWNAME]`
+
+Renames a Key-value store, or removes its unique name
+
+```
+USAGE
+  $ apify key-value-stores rename KEYVALUESTORENAMEORID [NEWNAME] [--unname]
+
+ARGUMENTS
+  KEYVALUESTORENAMEORID  The Key-value store ID or name to delete
+  NEWNAME                The new name for the Key-value store
+
+FLAGS
+  --unname  Removes the unique name of the Key-value store
+
+DESCRIPTION
+  Renames a Key-value store, or removes its unique name
+```
+
+_See code: [src/commands/key-value-stores/rename.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/key-value-stores/rename.ts)_
+
+## `apify key-value-stores rm KEYVALUESTORENAMEORID`
+
+Deletes a Key-value store
+
+```
+USAGE
+  $ apify key-value-stores rm KEYVALUESTORENAMEORID
+
+ARGUMENTS
+  KEYVALUESTORENAMEORID  The Key-value store ID or name to delete
+
+DESCRIPTION
+  Deletes a Key-value store
+```
+
+_See code: [src/commands/key-value-stores/rm.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/key-value-stores/rm.ts)_
+
+## `apify key-value-stores set-value STOREID ITEMKEY [VALUE]`
+
+Sets a value in a key-value store.
+
+```
+USAGE
+  $ apify key-value-stores set-value STOREID ITEMKEY [VALUE] [--content-type <value>]
+
+ARGUMENTS
+  STOREID  The key-value store ID to set the value in.
+  ITEMKEY  The key of the item in the key-value store.
+  VALUE    The value to set.
+
+FLAGS
+  --content-type=<value>  [default: application/json] The MIME content type of the value. By default, "application/json"
+                          is assumed.
+
+DESCRIPTION
+  Sets a value in a key-value store.
 ```
 
-_See code: [src/commands/key-value-stores/index.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/key-value-stores/index.ts)_
+_See code: [src/commands/key-value-stores/set-value.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/key-value-stores/set-value.ts)_
 
 ## `apify login`
 
@@ -310,7 +949,7 @@ DESCRIPTION
   "apify" commands. To log out, call "apify logout".
 ```
 
-_See code: [src/commands/login.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/login.ts)_
+_See code: [src/commands/login.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/login.ts)_
 
 ## `apify logout`
 
@@ -326,7 +965,7 @@ DESCRIPTION
   call "apify login".
 ```
 
-_See code: [src/commands/logout.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/logout.ts)_
+_See code: [src/commands/logout.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/logout.ts)_
 
 ## `apify pull [ACTORID]`
 
@@ -334,7 +973,7 @@ Pulls an Actor from the Apify platform to the current directory. If it is define
 
 ```
 USAGE
-  $ apify pull [ACTORID] [-v <value>]
+  $ apify pull [ACTORID] [-v <value>] [--dir <value>]
 
 ARGUMENTS
   ACTORID  Name or ID of the Actor to run (e.g. "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not provided, the
@@ -342,13 +981,14 @@ ARGUMENTS
 
 FLAGS
   -v, --version=<value>  Actor version number which will be pulled, e.g. 1.2. Default: the highest version
+      --dir=<value>      Directory where the Actor should be pulled to
 
 DESCRIPTION
   Pulls an Actor from the Apify platform to the current directory. If it is defined as Git repository, it will be
   cloned. If it is defined as Web IDE, it will fetch the files.
 ```
 
-_See code: [src/commands/pull.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/pull.ts)_
+_See code: [src/commands/pull.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/pull.ts)_
 
 ## `apify push [ACTORID]`
 
@@ -356,8 +996,7 @@ Uploads the Actor to the Apify platform and builds it there.
 
 ```
 USAGE
-  $ apify push [ACTORID] [--version-number <value>] [-v <value>] [-b <value>] [-w <value>] [--no-prompt]
-    [--force]
+  $ apify push [ACTORID] [-v <value>] [-b <value>] [-w <value>] [--no-prompt] [--force] [--dir <value>]
 
 ARGUMENTS
   ACTORID  Name or ID of the Actor to push (e.g. "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not provided, the
@@ -369,11 +1008,10 @@ FLAGS
   -v, --version=<value>          Actor version number to which the files should be pushed. By default, it is taken from
                                  the ".actor/actor.json" file.
   -w, --wait-for-finish=<value>  Seconds for waiting to build to finish, if no value passed, it waits forever.
+      --dir=<value>              Directory where the Actor is located
       --force                    Push an Actor even when the local files are older than the Actor on the platform.
       --no-prompt                Do not prompt for opening the Actor details in a browser. This will also not open the
                                  browser automatically.
-      --version-number=<value>   DEPRECATED: Use flag version instead. Actor version number to which the files should be
-                                 pushed. By default, it is taken from the ".actor/actor.json" file.
 
 DESCRIPTION
   Uploads the Actor to the Apify platform and builds it there.
@@ -386,7 +1024,7 @@ DESCRIPTION
   overwritten with --force flag.
 ```
 
-_See code: [src/commands/push.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/push.ts)_
+_See code: [src/commands/push.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/push.ts)_
 
 ## `apify request-queues`
 
@@ -400,7 +1038,7 @@ DESCRIPTION
   Commands are designed to be used with Request Queues.
 ```
 
-_See code: [src/commands/request-queues/index.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/request-queues/index.ts)_
+_See code: [src/commands/request-queues/index.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/request-queues/index.ts)_
 
 ## `apify run`
 
@@ -436,7 +1074,7 @@ DESCRIPTION
   package.json file. You can set up your own main file or environment variables by changing it.
 ```
 
-_See code: [src/commands/run.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/run.ts)_
+_See code: [src/commands/run.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/run.ts)_
 
 ## `apify runs`
 
@@ -450,7 +1088,133 @@ DESCRIPTION
   Commands are designed to be used with Actor Runs.
 ```
 
-_See code: [src/commands/runs/index.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/runs/index.ts)_
+_See code: [src/commands/runs/index.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/runs/index.ts)_
+
+## `apify runs abort RUNID`
+
+Aborts an Actor Run.
+
+```
+USAGE
+  $ apify runs abort RUNID [--json] [-f]
+
+ARGUMENTS
+  RUNID  The run ID to abort.
+
+FLAGS
+  -f, --force  Whether to force the run to abort immediately, instead of gracefully.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Aborts an Actor Run.
+```
+
+_See code: [src/commands/runs/abort.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/runs/abort.ts)_
+
+## `apify runs info RUNID`
+
+Prints information about an Actor Run.
+
+```
+USAGE
+  $ apify runs info RUNID [--json] [-v]
+
+ARGUMENTS
+  RUNID  The run ID to print information about.
+
+FLAGS
+  -v, --verbose  Prints more in-depth information about the Actor Run.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Prints information about an Actor Run.
+```
+
+_See code: [src/commands/runs/info.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/runs/info.ts)_
+
+## `apify runs log RUNID`
+
+Prints the log of a specific run.
+
+```
+USAGE
+  $ apify runs log RUNID
+
+ARGUMENTS
+  RUNID  The run ID to get the log from.
+
+DESCRIPTION
+  Prints the log of a specific run.
+```
+
+_See code: [src/commands/runs/log.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/runs/log.ts)_
+
+## `apify runs ls [ACTORID]`
+
+Lists all runs of the Actor.
+
+```
+USAGE
+  $ apify runs ls [ACTORID] [--json] [--offset <value>] [--limit <value>] [--desc] [-c]
+
+ARGUMENTS
+  ACTORID  Optional Actor ID or Name to list runs for. By default, it will use the Actor from the current directory.
+
+FLAGS
+  -c, --compact         Display a compact table.
+      --desc            Sort runs in descending order.
+      --limit=<value>   [default: 10] Number of runs that will be listed.
+      --offset=<value>  Number of runs that will be skipped.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Lists all runs of the Actor.
+```
+
+_See code: [src/commands/runs/ls.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/runs/ls.ts)_
+
+## `apify runs resurrect RUNID`
+
+Resurrects an aborted or finished Actor Run.
+
+```
+USAGE
+  $ apify runs resurrect RUNID [--json]
+
+ARGUMENTS
+  RUNID  The run ID to resurrect.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Resurrects an aborted or finished Actor Run.
+```
+
+_See code: [src/commands/runs/resurrect.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/runs/resurrect.ts)_
+
+## `apify runs rm RUNID`
+
+Deletes an Actor Run.
+
+```
+USAGE
+  $ apify runs rm RUNID
+
+ARGUMENTS
+  RUNID  The run ID to delete.
+
+DESCRIPTION
+  Deletes an Actor Run.
+```
+
+_See code: [src/commands/runs/rm.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/runs/rm.ts)_
 
 ## `apify secrets`
 
@@ -480,7 +1244,7 @@ DESCRIPTION
   of the Actor.
 ```
 
-_See code: [src/commands/secrets/index.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/secrets/index.ts)_
+_See code: [src/commands/secrets/index.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/secrets/index.ts)_
 
 ## `apify secrets add NAME VALUE`
 
@@ -499,7 +1263,7 @@ DESCRIPTION
   The secrets are stored to a file at ~/.apify
 ```
 
-_See code: [src/commands/secrets/add.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/secrets/add.ts)_
+_See code: [src/commands/secrets/add.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/secrets/add.ts)_
 
 ## `apify secrets rm NAME`
 
@@ -516,7 +1280,7 @@ DESCRIPTION
   Removes the secret.
 ```
 
-_See code: [src/commands/secrets/rm.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/secrets/rm.ts)_
+_See code: [src/commands/secrets/rm.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/secrets/rm.ts)_
 
 ## `apify task`
 
@@ -530,7 +1294,7 @@ DESCRIPTION
   Commands are designed to be used to interact with Tasks.
 ```
 
-_See code: [src/commands/task/index.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/task/index.ts)_
+_See code: [src/commands/task/index.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/task/index.ts)_
 
 ## `apify task run TASKID`
 
@@ -538,16 +1302,15 @@ Runs a specific Actor remotely on the Apify cloud platform.
 
 ```
 USAGE
-  $ apify task run TASKID [-b <value>] [-t <value>] [-m <value>] [-w <value>]
+  $ apify task run TASKID [-b <value>] [-t <value>] [-m <value>]
 
 ARGUMENTS
   TASKID  Name or ID of the Task to run (e.g. "my-task" or "E2jjCZBezvAZnX8Rb").
 
 FLAGS
-  -b, --build=<value>            Tag or number of the build to run (e.g. "latest" or "1.2.34").
-  -m, --memory=<value>           Amount of memory allocated for the Task run, in megabytes.
-  -t, --timeout=<value>          Timeout for the Task run in seconds. Zero value means there is no timeout.
-  -w, --wait-for-finish=<value>  Seconds for waiting to run to finish, if no value passed, it waits forever.
+  -b, --build=<value>    Tag or number of the build to run (e.g. "latest" or "1.2.34").
+  -m, --memory=<value>   Amount of memory allocated for the Task run, in megabytes.
+  -t, --timeout=<value>  Timeout for the Task run in seconds. Zero value means there is no timeout.
 
 DESCRIPTION
   Runs a specific Actor remotely on the Apify cloud platform.
@@ -555,7 +1318,7 @@ DESCRIPTION
   takes input for the Actor from the default local key-value store by default.
 ```
 
-_See code: [src/commands/task/run.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/task/run.ts)_
+_See code: [src/commands/task/run.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/task/run.ts)_
 
 ## `apify validate-schema [PATH]`
 
@@ -580,6 +1343,6 @@ DESCRIPTION
   You can also pass any custom path to your input schema to have it validated instead.
 ```
 
-_See code: [src/commands/validate-schema.ts](https://github.com/apify/apify-cli/blob/v0.20.7/src/commands/validate-schema.ts)_
+_See code: [src/commands/validate-schema.ts](https://github.com/apify/apify-cli/blob/v0.21.0/src/commands/validate-schema.ts)_
 <!-- commandsstop -->
 <!-- prettier-ignore-end -->
diff --git a/package.json b/package.json
index 62c7ee523..4c42f5c32 100644
--- a/package.json
+++ b/package.json
@@ -17,7 +17,8 @@
         "clean": "rimraf dist",
         "build": "yarn clean && tsc && tsc -p tsconfig.typechecking.json",
         "postpack": "rimraf oclif.manifest.json",
-        "prepack": "yarn build && oclif manifest && oclif readme && oclif readme --readme-path=docs/reference.md",
+        "prepack": "yarn build && oclif manifest && oclif readme && yarn update-docs",
+        "update-docs": "oclif readme --readme-path=docs/reference.md",
         "postinstallDev": "yarn build && node ./bin/run.js check-version && node ./dist/lib/community.js"
     },
     "files": [
diff --git a/website/docusaurus.config.js b/website/docusaurus.config.js
index 807df86ea..884356563 100644
--- a/website/docusaurus.config.js
+++ b/website/docusaurus.config.js
@@ -1,5 +1,7 @@
 const { config } = require('@apify/docs-theme');
+
 const { externalLinkProcessor } = require('./tools/utils/externalLink');
+const versions = require('./versions.json');
 
 const { absoluteUrl } = config;
 /** @type {Partial<import('@docusaurus/types').DocusaurusConfig>} */
@@ -23,35 +25,38 @@ module.exports = {
                     title: 'Apify CLI',
                     items: [
                         {
-                            to: 'docs',
+                            type: 'doc',
+                            docId: 'index',
                             label: 'Docs',
                             position: 'left',
                             activeBaseRegex: 'docs(?!/changelog|/reference)',
                         },
                         {
-                            to: 'docs/reference',
+                            type: 'doc',
+                            docId: 'reference',
                             label: 'Reference',
                             position: 'left',
-                            activeBaseRegex: 'docs/reference',
+                            activeBaseRegex: 'reference',
                         },
                         {
-                            to: 'docs/changelog',
+                            type: 'doc',
+                            docId: 'changelog',
                             label: 'Changelog',
                             position: 'left',
-                            activeBaseRegex: 'docs/changelog',
+                            activeBaseRegex: 'changelog',
                         },
                         {
                             href: 'https://github.com/apify/apify-cli',
                             label: 'GitHub',
                             position: 'left',
                         },
-                        // {
-                        //     type: 'docsVersionDropdown',
-                        //     position: 'left',
-                        //     className: 'navbar__item', // fixes margin around dropdown - hackish, should be fixed in theme
-                        //     dropdownItemsBefore: [],
-                        //     dropdownItemsAfter: [],
-                        // },
+                        {
+                            type: 'docsVersionDropdown',
+                            position: 'left',
+                            className: 'navbar__item', // fixes margin around dropdown - hackish, should be fixed in theme
+                            dropdownItemsBefore: [],
+                            dropdownItemsAfter: [],
+                        },
                     ],
                 },
             },
@@ -78,6 +83,6 @@ module.exports = {
     plugins: [
         ...config.plugins,
     ],
-    themeConfig: config.themeConfig,
+    themeConfig: { ...config.themeConfig, versions },
     staticDirectories: ['node_modules/@apify/docs-theme/static', 'static'],
 };
diff --git a/website/versioned_docs/version-0.20/changelog.md b/website/versioned_docs/version-0.20/changelog.md
new file mode 100644
index 000000000..e4aceddb1
--- /dev/null
+++ b/website/versioned_docs/version-0.20/changelog.md
@@ -0,0 +1,318 @@
+---
+title: Changelog
+sidebar_label: Changelog
+toc_max_heading_level: 2
+---
+
+## [v0.20.11](https://github.com/apify/apify-cli/releases/tag/v0.20.11)
+
+#### What's Changed
+
+- fix: scrapy wrapping being broken due to ESM migration ([#686](https://github.com/apify/apify-cli/pull/686)) by [@vladfrangu](https://github.com/vladfrangu)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.10...v0.20.11
+
+## [v0.20.10](https://github.com/apify/apify-cli/releases/tag/v0.20.10)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.9...v0.20.10
+
+## [v0.20.9](https://github.com/apify/apify-cli/releases/tag/v0.20.9)
+
+#### What's Changed
+
+- fix: emit warning if input.json is modified during run and prefilled with defaults ([#672](https://github.com/apify/apify-cli/pull/672)) by [@vladfrangu](https://github.com/vladfrangu)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.8...v0.20.9
+
+## [v0.20.8](https://github.com/apify/apify-cli/releases/tag/v0.20.8)
+
+#### What's Changed
+
+- Reverted the empty namespaces that were added in the previous release
+- fix: look for lowercase input schema in default paths ([#647](https://github.com/apify/apify-cli/pull/647)) by [@mvolfik](https://github.com/mvolfik)
+- Increase the minimum Python version to 3.9, in line with Apify SDK
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.7...v0.20.8
+
+## [v0.20.7](https://github.com/apify/apify-cli/releases/tag/v0.20.7)
+
+#### What's Changed
+
+- fix: auto-set `apify run` `INPUT.json` only with values that have defaults by [@vladfrangu](https://github.com/vladfrangu) in [#641](https://github.com/apify/apify-cli/pull/641)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.6...v0.20.7
+
+## [v0.20.6](https://github.com/apify/apify-cli/releases/tag/v0.20.6)
+
+#### What's Changed
+
+- fix: ensure input kvs path exists when calling `apify run` by [@vladfrangu](https://github.com/vladfrangu) in [#625](https://github.com/apify/apify-cli/pull/625)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.5...v0.20.6
+
+## [v0.20.5](https://github.com/apify/apify-cli/releases/tag/v0.20.5)
+
+#### What's Changed
+
+- fix: print path to invalid `actor.json` when an invalid file is found by [@vladfrangu](https://github.com/vladfrangu) in [#618](https://github.com/apify/apify-cli/pull/618)
+- fix: passing the item via stdin to `actor push-data` works again by [@vladfrangu](https://github.com/vladfrangu) in [#617](https://github.com/apify/apify-cli/pull/617)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.4...v0.20.5
+
+## [v0.20.4](https://github.com/apify/apify-cli/releases/tag/v0.20.4)
+
+#### What's Changed
+
+- feat: printing dataset result for `call` command by [@vladfrangu](https://github.com/vladfrangu) in [#614](https://github.com/apify/apify-cli/pull/614)
+
+#### New Contributors
+
+- @netmilk made their first contribution in [#609](https://github.com/apify/apify-cli/pull/609)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.3...v0.20.4
+
+## [v0.20.3](https://github.com/apify/apify-cli/releases/tag/v0.20.3)
+
+#### What's Changed
+
+- fix(call): support calling with bare ids by [@vladfrangu](https://github.com/vladfrangu) in [#613](https://github.com/apify/apify-cli/pull/613)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.2...v0.20.3
+
+## [v0.20.2](https://github.com/apify/apify-cli/releases/tag/v0.20.2)
+
+#### What's Changed
+
+- fix: run scripts not printing unsupported node versions rightly by [@vladfrangu](https://github.com/vladfrangu) in [#589](https://github.com/apify/apify-cli/pull/589)
+- fix: run command validating inputs caused inputs to not work in crawlee projects by [@vladfrangu](https://github.com/vladfrangu) in [#591](https://github.com/apify/apify-cli/pull/591)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.20.0...v0.20.2
+
+## [](https://github.com/apify/apify-cli/releases/tag/v0.20.0)
+
+#### What's Changed
+
+- feat: add a troubleshooting section to the root help screen by [@tobice](https://github.com/tobice) in [#491](https://github.com/apify/apify-cli/pull/491)
+- feat: Better copy and docs by [@jancurn](https://github.com/jancurn) in [#494](https://github.com/apify/apify-cli/pull/494)
+- fix: prompt for new folder name when existing folder is used with `apify create` by [@vladfrangu](https://github.com/vladfrangu) in [#504](https://github.com/apify/apify-cli/pull/504)
+- feat: Warn user there's newer Actor version on the platform by [@HonzaTuron](https://github.com/HonzaTuron) in [#506](https://github.com/apify/apify-cli/pull/506)
+- feat: use login-new as default login method by [@HonzaTuron](https://github.com/HonzaTuron) in [#508](https://github.com/apify/apify-cli/pull/508)
+- feat: support spaces and `:` for subcommands by [@vladfrangu](https://github.com/vladfrangu) in [#521](https://github.com/apify/apify-cli/pull/521)
+- feat: prevent old node from running CLI by [@vladfrangu](https://github.com/vladfrangu) in [#522](https://github.com/apify/apify-cli/pull/522)
+- feat: different exit codes for different errors by [@vladfrangu](https://github.com/vladfrangu) in [#520](https://github.com/apify/apify-cli/pull/520)
+- feat: --no-optional for create command by [@vladfrangu](https://github.com/vladfrangu) in [#524](https://github.com/apify/apify-cli/pull/524)
+- feat: support calling actors with bare names by [@vladfrangu](https://github.com/vladfrangu) in [#538](https://github.com/apify/apify-cli/pull/538)
+- feat: support running other entrypoints with injected Apify environment variables by [@vladfrangu](https://github.com/vladfrangu) in [#539](https://github.com/apify/apify-cli/pull/539)
+- fix: always enable crawlee storage purging when `--purge` is provided, even in non-crawlee-detected envs by [@vladfrangu](https://github.com/vladfrangu) in [#543](https://github.com/apify/apify-cli/pull/543)
+- feat: Setup Smartlook for CLI docs by [@HonzaTuron](https://github.com/HonzaTuron) in [#544](https://github.com/apify/apify-cli/pull/544)
+- fix: prevent running `apify push` from non-actor-looking folders by [@vladfrangu](https://github.com/vladfrangu) in [#537](https://github.com/apify/apify-cli/pull/537)
+- fix: purge working in python again by [@vladfrangu](https://github.com/vladfrangu) in [#548](https://github.com/apify/apify-cli/pull/548)
+- fix: deprecate `vis` command in favor of `validate-schema` by [@vladfrangu](https://github.com/vladfrangu) in [#556](https://github.com/apify/apify-cli/pull/556)
+- fix: always try to get a remote storage if IS_AT_HOME is true by [@vladfrangu](https://github.com/vladfrangu) in [#557](https://github.com/apify/apify-cli/pull/557)
+- feat: task run, actor call, deprecate top level call by [@vladfrangu](https://github.com/vladfrangu) in [#558](https://github.com/apify/apify-cli/pull/558)
+- fix: print most information to stderr in preparation of future integrations by [@vladfrangu](https://github.com/vladfrangu) in [#570](https://github.com/apify/apify-cli/pull/570)
+- feat: Update api token links by [@valekjo](https://github.com/valekjo) in [#578](https://github.com/apify/apify-cli/pull/578)
+- feat: validate input on run by [@vladfrangu](https://github.com/vladfrangu) in [#560](https://github.com/apify/apify-cli/pull/560)
+- feat: call with inputs by [@vladfrangu](https://github.com/vladfrangu) in [#577](https://github.com/apify/apify-cli/pull/577)
+- chore: migrate to TypeScript and Oclif 3 by [@vladfrangu](https://github.com/vladfrangu) in [#477](https://github.com/apify/apify-cli/pull/477)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.19.5...v0.20.0
+
+## [v0.19.5](https://github.com/apify/apify-cli/releases/tag/v0.19.5)
+
+#### What's Changed
+
+- fix: CLI on Windows throwing EINVAL errors with latest node 18/20/22 by [@vladfrangu](https://github.com/vladfrangu)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.19.4...v0.19.5
+
+## [v0.19.4](https://github.com/apify/apify-cli/releases/tag/v0.19.4)
+
+#### What's Changed
+
+- fix: make `run --purge` work again for Python projects by [@vladfrangu](https://github.com/vladfrangu)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.19.3...v0.19.4
+
+## [](https://github.com/apify/apify-cli/releases/tag/v0.19.3)
+
+#### What's Changed
+
+- fix: always enable crawlee storage purging when `--purge` is provided even in non-crawlee-detected envs by [@vladfrangu](https://github.com/vladfrangu)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.19.2...v0.19.3
+
+## [v0.19.2](https://github.com/apify/apify-cli/releases/tag/v0.19.2)
+
+#### What's Changed
+
+- feat: validate the Actor name during init by [@barjin](https://github.com/barjin) in [#450](https://github.com/apify/apify-cli/pull/450)
+- feat: extend success command on create by [@HonzaTuron](https://github.com/HonzaTuron) in [#466](https://github.com/apify/apify-cli/pull/466)
+- fix: axios v1 and new client breaking cli by [@vladfrangu](https://github.com/vladfrangu) in [#481](https://github.com/apify/apify-cli/pull/481)
+
+#### New Contributors
+
+- @vdusek made their first contribution in [#439](https://github.com/apify/apify-cli/pull/439)
+- @TC-MO made their first contribution in [#468](https://github.com/apify/apify-cli/pull/468)
+- @honzajavorek made their first contribution in [#472](https://github.com/apify/apify-cli/pull/472)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.19.1...v0.19.2
+
+## [v0.19.1](https://github.com/apify/apify-cli/releases/tag/v0.19.1)
+
+#### What's Changed
+
+- fix: restore fallback behaviour for `apify run` in Scrapy projects by [@barjin](https://github.com/barjin) in [#437](https://github.com/apify/apify-cli/pull/437)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.19.0...v0.19.1
+
+## [v0.19.0](https://github.com/apify/apify-cli/releases/tag/v0.19.0)
+
+#### What's Changed
+
+- feat: Auto-update `apify-cli` Homebrew formula in `homebrew-core` by [@fnesveda](https://github.com/fnesveda) in [#387](https://github.com/apify/apify-cli/pull/387)
+- fix: spelling in helpers by [@barjin](https://github.com/barjin) in [#389](https://github.com/apify/apify-cli/pull/389)
+- feat: `apify init` wraps Scrapy projects with Apify middleware by [@barjin](https://github.com/barjin) in [#393](https://github.com/apify/apify-cli/pull/393)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.18.1...v0.19.0
+
+## [v0.18.1](https://github.com/apify/apify-cli/releases/tag/v0.18.1)
+
+#### What's Changed
+
+##### Fixes
+
+- Fixed `actor:push-data` and `actor:set-value` commands by [@drobnikj](https://github.com/drobnikj) in [#386](https://github.com/apify/apify-cli/pull/386)
+
+##### Documentation changes
+
+- Updated Homebrew installation instructions by [@fnesveda](https://github.com/fnesveda) in [#385](https://github.com/apify/apify-cli/pull/385)
+- Minor rewording by [@jancurn](https://github.com/jancurn) in [#383](https://github.com/apify/apify-cli/pull/383)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.18.0...v0.18.1
+
+## [v0.18.0](https://github.com/apify/apify-cli/releases/tag/v0.18.0)
+
+#### What's Changed
+
+- feat(create, init): create INPUT.json from input_schema prefills by [@nguyeda1](https://github.com/nguyeda1) in [#379](https://github.com/apify/apify-cli/pull/379)
+- feat: Use actor/apify env vars instead of old `ENV_VARS` by [@jirimoravcik](https://github.com/jirimoravcik) in [#381](https://github.com/apify/apify-cli/pull/381)
+- chore: Bump version to 0.18.0 by [@jirimoravcik](https://github.com/jirimoravcik) in [#382](https://github.com/apify/apify-cli/pull/382)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.17.0...v0.18.0
+
+## [v0.17.0](https://github.com/apify/apify-cli/releases/tag/v0.17.0)
+
+#### What's Changed
+
+- BREAKING CHANGE: Telemetry data collection by [@drobnikj](https://github.com/drobnikj) in [#362](https://github.com/apify/apify-cli/pull/362)
+- chore: Fix docs reference by [@drobnikj](https://github.com/drobnikj) in [#375](https://github.com/apify/apify-cli/pull/375)
+- fix: Folder path creation by [@HonzaTuron](https://github.com/HonzaTuron) in [#376](https://github.com/apify/apify-cli/pull/376)
+- feat(create): Merge local development instructions into README by [@nguyeda1](https://github.com/nguyeda1) in [#372](https://github.com/apify/apify-cli/pull/372)
+
+#### New Contributors
+
+- @nguyeda1 made their first contribution in [#372](https://github.com/apify/apify-cli/pull/372)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.16.2...v0.17.0
+
+## [v0.16.2](https://github.com/apify/apify-cli/releases/tag/v0.16.2)
+
+#### What's Changed
+
+- chore: Use new workflow secrets by [@fnesveda](https://github.com/fnesveda) in [#361](https://github.com/apify/apify-cli/pull/361)
+- feat: Add community message by [@HonzaTuron](https://github.com/HonzaTuron) in [#363](https://github.com/apify/apify-cli/pull/363)
+- fix: Use the right exit code on error by [@fnesveda](https://github.com/fnesveda) in [#364](https://github.com/apify/apify-cli/pull/364)
+- feat(push): Allow disabling of the prompt mechanism via flag/CI by [@vladfrangu](https://github.com/vladfrangu) in [#365](https://github.com/apify/apify-cli/pull/365)
+- fix(push): Correctly check if in CI env to skip prompt by [@vladfrangu](https://github.com/vladfrangu) in [#366](https://github.com/apify/apify-cli/pull/366)
+- fix: Fix unit tests by [@fnesveda](https://github.com/fnesveda) in [#371](https://github.com/apify/apify-cli/pull/371)
+- feat(app): Add apify pull by [@HonzaTuron](https://github.com/HonzaTuron) in [#360](https://github.com/apify/apify-cli/pull/360)
+
+#### New Contributors
+
+- @vladfrangu made their first contribution in [#365](https://github.com/apify/apify-cli/pull/365)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.16.1...v0.16.2
+
+## [v0.16.1](https://github.com/apify/apify-cli/releases/tag/v0.16.1)
+
+#### What's Changed
+
+- Fix `apify create` on Node 19+, add Node 20 to CI test roster by [@fnesveda](https://github.com/fnesveda) in [#359](https://github.com/apify/apify-cli/pull/359)
+
+## [v0.16.0](https://github.com/apify/apify-cli/releases/tag/v0.16.0)
+
+#### What's Changed
+
+##### New features
+
+- Added option to open actor detail in Apify Console after successful `apify push` by [@HonzaTuron](https://github.com/HonzaTuron) in [#353](https://github.com/apify/apify-cli/pull/353)
+
+##### Fixes
+
+- Stopped adding `apify_storage` to .gitignore if it already is there by [@fnesveda](https://github.com/fnesveda) in [#355](https://github.com/apify/apify-cli/pull/355)
+- Fixed extracting some template archives by [@mvolfik](https://github.com/mvolfik) in [#358](https://github.com/apify/apify-cli/pull/358)
+- Improved log messages for different build statuses by [@fnesveda](https://github.com/fnesveda) in [#350](https://github.com/apify/apify-cli/pull/350)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.15.1...v0.16.0
+
+## [v0.15.1](https://github.com/apify/apify-cli/releases/tag/v0.15.1)
+
+#### What's Changed
+
+- Added a post-create message to Python actors by [@fnesveda](https://github.com/fnesveda) in [#349](https://github.com/apify/apify-cli/pull/349)
+- Updated the `apify run` help to not be so Node-specific by [@fnesveda](https://github.com/fnesveda) in [#347](https://github.com/apify/apify-cli/pull/347)
+- Started using correct "omit optional dependencies" argument based on NPM version by [@fnesveda](https://github.com/fnesveda) in [#346](https://github.com/apify/apify-cli/pull/346)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.15.0...v0.15.1
+
+## [v0.15.0](https://github.com/apify/apify-cli/releases/tag/v0.15.0)
+
+#### New features
+
+- Apify Console login integration in `apify login-new` by [@fnesveda](https://github.com/fnesveda) in [#302](https://github.com/apify/apify-cli/pull/302)
+- Preparations for release on Homebrew by [@fnesveda](https://github.com/fnesveda) in [#341](https://github.com/apify/apify-cli/pull/341), [#342](https://github.com/apify/apify-cli/pull/342), [#343](https://github.com/apify/apify-cli/pull/343) and [#345](https://github.com/apify/apify-cli/pull/345)
+- Better template language selection in `apify create` by [@mnmkng](https://github.com/mnmkng) in [#338](https://github.com/apify/apify-cli/pull/338)
+- New documentation portal by [@barjin](https://github.com/barjin) in [#331](https://github.com/apify/apify-cli/pull/331)
+
+#### Internal changes
+
+- Added automated tests for Python support by [@fnesveda](https://github.com/fnesveda) in [#344](https://github.com/apify/apify-cli/pull/344)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.14.1...v0.15.0
+
+## [v0.14.1](https://github.com/apify/apify-cli/releases/tag/v0.14.1)
+
+#### What's Changed
+
+- chore: Disable actor template prompt looping around by [@fnesveda](https://github.com/fnesveda) in [#318](https://github.com/apify/apify-cli/pull/318)
+- feat: Support for running Python actors by [@fnesveda](https://github.com/fnesveda) in [#316](https://github.com/apify/apify-cli/pull/316)
+- fix: Removing unneeded dependencies by [@mtrunkat](https://github.com/mtrunkat) in [#322](https://github.com/apify/apify-cli/pull/322)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.13.0...v0.14.1
+
+## [v0.13.0](https://github.com/apify/apify-cli/releases/tag/v0.13.0)
+
+#### What's Changed
+
+- feat: Making outdated version warning more visible by [@mtrunkat](https://github.com/mtrunkat) in [#301](https://github.com/apify/apify-cli/pull/301)
+- fix: fix headings in readme by [@mhamas](https://github.com/mhamas) in [#308](https://github.com/apify/apify-cli/pull/308)
+- fix: Update node version by [@novotnyj](https://github.com/novotnyj) in [#314](https://github.com/apify/apify-cli/pull/314)
+- fix: missing latest tag on first push by [@mnmkng](https://github.com/mnmkng) in [#312](https://github.com/apify/apify-cli/pull/312)
+
+**Full Changelog**: https://github.com/apify/apify-cli/compare/v0.12.0...v0.13.0
+
+## [v0.12.0](https://github.com/apify/apify-cli/releases/tag/v0.12.0)
+
+- add the `X-Apify-Request-Origin: CLI` header to the API calls done by CLI
+
+## [v0.11.1](https://github.com/apify/apify-cli/releases/tag/v0.11.1)
+
+- Fix `create` command which rewrites `.actor/actor.json` from template with default file
+
+## [v0.11.0](https://github.com/apify/apify-cli/releases/tag/v0.11.0)
+
+- modify commands to work with actor config stored in `.actor/actor.json` instead of the deprecated `apify.json`
+- add migration from the deprecated config to the new one
+- modify `vis` and `edit-input-schema` commands to find the input schema at the correct location, where it would be loaded from on the platform
+- update README and commands' help texts to cover these changes
diff --git a/website/versioned_docs/version-0.20/index.md b/website/versioned_docs/version-0.20/index.md
new file mode 100644
index 000000000..c7a113828
--- /dev/null
+++ b/website/versioned_docs/version-0.20/index.md
@@ -0,0 +1,22 @@
+---
+title: Apify CLI
+---
+
+<a href="https://www.npmjs.com/package/apify-cli"><img src="https://badge.fury.io/js/apify-cli.svg" alt="npm version" loading="lazy" /></a>
+<a href="https://travis-ci.com/apify/apify-cli?branch=master"><img src="https://travis-ci.com/apify/apify-cli.svg?branch=master" loading="lazy" alt="Build Status" /></a>
+
+Apify command-line interface (Apify CLI) helps you create, develop, build and run
+[Apify Actors](https://apify.com/actors),
+and manage the Apify cloud platform from any computer.
+
+Apify Actors are cloud programs that can perform arbitrary web scraping, automation or data processing job.
+They accept input, perform their job and generate output.
+While you can develop Actors in an online IDE directly in the [Apify web application](https://console.apify.com/),
+for complex projects it is more convenient to develop Actors locally on your computer
+using <a href="https://github.com/apify/apify-sdk-js">Apify SDK</a>
+and only push the Actors to the Apify cloud during deployment.
+This is where the Apify CLI comes in.
+
+Note that Actors running on the Apify platform are executed in Docker containers, so with an appropriate `Dockerfile`
+you can build your Actors in any programming language.
+However, we recommend using JavaScript / Node.js, for which we provide most libraries and support.
diff --git a/website/versioned_docs/version-0.20/installation.md b/website/versioned_docs/version-0.20/installation.md
new file mode 100644
index 000000000..dc78dd526
--- /dev/null
+++ b/website/versioned_docs/version-0.20/installation.md
@@ -0,0 +1,189 @@
+---
+title: Installation
+description: Learn how to install Apify CLI, and how to create, run, and manage Actors through it.
+sidebar_label: Installation
+---
+
+## Installation
+
+You can install Apify CLI either using [Homebrew package manager](https://brew.sh) on macOS or Linux or using NPM on all platforms including Windows.
+
+### Via Homebrew
+
+Run the following command:
+
+```bash showLineNumbers
+brew install apify-cli
+```
+
+### Via NPM
+
+First, make sure you have [Node.js](https://nodejs.org) version 18 or higher with NPM installed on your computer:
+
+```bash showLineNumbers
+node --version
+npm --version
+```
+
+Install or upgrade Apify CLI by running:
+
+```bash showLineNumbers
+npm -g install apify-cli
+```
+
+If you receive a permission error, read npm's [official guide](https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally) on installing packages globally.
+
+Alternatively, you can use [Node Version Manager (nvm)](https://github.com/nvm-sh/nvm) and install Apify CLI only into a selected user-level Node version without requiring root privileges:
+
+```bash showLineNumbers
+nvm install 18
+nvm use 18
+npm -g install apify-cli
+```
+
+After using either of these methods , verify that Apify CLI was installed correctly by running:
+
+```bash showLineNumbers
+apify --version
+```
+
+which should print something like:
+
+```bash showLineNumbers
+apify-cli/0.19.1 linux-x64 node-v18.17.0
+```
+
+## Basic Usage
+
+The following examples demonstrate the basic usage of Apify CLI.
+
+### Create a New Actor from Scratch
+
+```bash showLineNumbers
+apify create my-hello-world
+```
+
+First, you will be prompted to select a template with the boilerplate for the Actor, to help you get started quickly.
+The command will create a directory called `my-hello-world` that contains a Node.js project
+for the Actor and a few configuration files.
+
+### Create a New Actor from Existing Project
+
+:::tip Automatic Actor directory initialization
+When you create an Actor using the `apify create` command, the directory will already be initialized.
+:::
+
+```bash showLineNumbers
+cd ./my/awesome/project
+apify init
+```
+
+This command will only set up local Actor development environment in an existing directory,
+i.e. it will create the `.actor/actor.json` file and `apify_storage` directory.
+
+Before you can run your project locally using `apify run`, you have to set up the right start command in `package.json` under scripts.start. For example:
+
+```json showLineNumbers
+{
+    ...
+    "scripts": {
+        "start": "node your_main_file.js",
+    },
+    ...
+}
+```
+
+You can find more information about by running `apify help run`.
+
+### Run the Actor Locally
+
+```bash showLineNumbers
+cd my-hello-world
+apify run
+```
+
+This command runs the Actor on your local machine.
+Now's your chance to develop the logic - or magic :smirk:
+
+### Login with your Apify account
+
+```bash showLineNumbers
+apify login
+```
+
+Before you can interact with the Apify cloud, you need to [create an Apify account](https://console.apify.com/)
+and log in to it using the above command. You will be prompted for
+your [Apify API token](https://console.apify.com/settings/integrations).
+
+:::note API token save directory
+The command will store the API token and other sensitive information to `~/.apify`.
+:::
+
+### Push the Actor to the Apify Cloud
+
+```bash showLineNumbers
+apify push
+```
+
+This command uploads your project to the Apify cloud and builds an Actor from it. On the platform, Actor needs to be built before it can be run.
+
+### Run an Actor on the Apify Cloud
+
+```bash showLineNumbers
+apify call
+```
+
+Runs the Actor corresponding to the current directory on the Apify Platform.
+
+This command can also be used to run other Actors, for example:
+
+```bash showLineNumbers
+apify call apify/hello-world
+```
+
+### So what's in this `.actor/actor.json` File?
+
+This file associates your local development project with an Actor on the Apify Platform.
+It contains information such as Actor name, version, build tag and environment variables.
+Make sure you commit this file to the Git repository.
+
+For example, `.actor/actor.json` file can look as follows:
+
+```json showLineNumbers
+{
+  "actorSpecification": 1,
+  "name": "name-of-my-scraper",
+  "version": "0.0",
+  "buildTag": "latest",
+  "environmentVariables": {
+    "MYSQL_USER": "my_username",
+    "MYSQL_PASSWORD": "@mySecretPassword"
+  },
+  "dockerfile": "./Dockerfile",
+  "readme": "./ACTOR.md",
+  "input": "./input_schema.json",
+  "storages": {
+    "dataset": "./dataset_schema.json"
+  }
+}
+```
+
+**`Dockerfile` field**
+
+If you specify the path to your Docker file under the `dockerfile` field, this file will be used for Actor builds on the platform. If not specified, the system will look for Docker files at `.actor/Dockerfile` and `Dockerfile` in this order of preference.
+
+**`Readme` field**
+
+If you specify the path to your readme file under the `readme` field, the readme at this path will be used on the platform. If not specified, readme at `.actor/README.md` and `README.md` will be used in this order of preference.
+
+**`Input` field**
+
+You can embed your [input schema](https://docs.apify.com/actors/development/input-schema#specification-version-1) object directly in `actor.json` under `input` field. Alternatively, you can provide a path to a custom input schema. If not provided, the input schema at `.actor/INPUT_SCHEMA.json` and `INPUT_SCHEMA.json` is used in this order of preference.
+
+**`Storages.dataset` field**
+
+You can define the schema of the items in your dataset under the `storages.dataset` field. This can be either an embedded object or a path to a JSON schema file. You can read more about the schema of your Actor output [here](https://docs.apify.com/actors/development/output-schema#specification-version-1).
+
+:::note Migration from deprecated config "apify.json"
+Note that previously, Actor config was stored in the `apify.json` file that has been deprecated. You can find the (very slight) differences and migration info in [migration guidelines](https://github.com/apify/apify-cli/blob/master/MIGRATIONS.md).
+:::
diff --git a/website/versioned_docs/version-0.20/integrating-scrapy.md b/website/versioned_docs/version-0.20/integrating-scrapy.md
new file mode 100644
index 000000000..37a862007
--- /dev/null
+++ b/website/versioned_docs/version-0.20/integrating-scrapy.md
@@ -0,0 +1,203 @@
+---
+title: Integrating Scrapy projects
+description: Learn how to run Scrapy projects as Apify Actors and deploy them on the Apify platform.
+sidebar_label: Integrating Scrapy projects
+---
+
+[Scrapy](https://scrapy.org/) is a widely used open-source web scraping framework for Python. Scrapy projects can now be executed on the Apify platform using our dedicated wrapping tool. This tool allows users to transform their Scrapy projects into [Apify Actors](https://docs.apify.com/platform/actors) with just a few simple commands.
+
+## Getting started
+
+### Install Apify CLI
+
+To run the migration tool, you need to have the Apify CLI installed. You can install it using Homebrew with the following command:
+
+```bash showLineNumbers
+brew install apify-cli
+```
+
+Alternatively, you can install it using NPM with the following command:
+
+```bash showLineNumbers
+npm i -g apify-cli
+```
+
+In case of any issues, please refer to the [installation guide](./installation.md).
+
+## Actorization of your existing Scrapy spider
+
+Assuming your Scrapy project is set up, navigate to the project root where the `scrapy.cfg` file is located.
+
+```bash showLineNumbers
+cd your_scraper
+```
+
+Verify the directory contents to ensure the correct location.
+
+```bash showLineNumbers
+$ ls -R
+.:
+your_scraper  README.md  requirements.txt  scrapy.cfg
+
+./your_scraper:
+__init__.py  items.py  __main__.py  main.py  pipelines.py  settings.py  spiders
+
+./your_scraper/spiders:
+your_spider.py  __init__.py
+```
+
+To convert your Scrapy project into an Apify Actor, initiate the wrapping process by executing the following command:
+
+```bash showLineNumbers
+apify init
+```
+
+The script will prompt you with a series of questions. Upon completion, the output might resemble the following:
+
+```bash showLineNumbers
+Info: The current directory looks like a Scrapy project. Using automatic project wrapping.
+? Enter the Scrapy BOT_NAME (see settings.py): books_scraper
+? What folder are the Scrapy spider modules stored in? (see SPIDER_MODULES in settings.py): books_scraper.spiders
+? Pick the Scrapy spider you want to wrap: BookSpider (/home/path/to/actor-scrapy-books-example/books_scraper/spiders/book.py)
+Info: Downloading the latest Scrapy wrapper template...
+Info: Wrapping the Scrapy project...
+Success: The Scrapy project has been wrapped successfully.
+```
+
+For example, here is a [source code](https://github.com/apify/actor-scrapy-books-example) of an actorized Scrapy project, and [here](https://apify.com/vdusek/scrapy-books-example) the corresponding Actor in Apify Store.
+
+### Run the Actor locally
+
+Create a Python virtual environment by running:
+
+```bash showLineNumbers
+python -m virtualenv .venv
+```
+
+Activate the virtual environment:
+
+```bash showLineNumbers
+source .venv/bin/activate
+```
+
+Install Python dependencies using the provided requirements file named `requirements_apify.txt`. Ensure these requirements are installed before executing your project as an Apify Actor locally. You can put your own dependencies there as well.
+
+```bash showLineNumbers
+pip install -r requirements-apify.txt [-r requirements.txt]
+```
+
+Finally execute the Apify Actor.
+
+```bash showLineNumbers
+apify run [--purge]
+```
+
+If [ActorDatasetPushPipeline](https://github.com/apify/apify-sdk-python/blob/master/src/apify/scrapy/pipelines.py) is configured, the Actor's output will be stored in the `storage/datasets/default/` directory.
+
+### Run the scraper as Scrapy project
+
+The project remains executable as a Scrapy project.
+
+```bash showLineNumbers
+scrapy crawl your_spider -o books.json
+```
+
+## Deploy on Apify
+
+### Log in to Apify
+
+You will need to provide your [Apify API Token](https://console.apify.com/settings/integrations) to complete this action.
+
+```bash showLineNumbers
+apify login
+```
+
+### Deploy your Actor
+
+This command will deploy and build the Actor on the Apify platform. You can find your newly created Actor under [Actors -> My Actors](https://console.apify.com/actors?tab=my).
+
+```bash showLineNumbers
+apify push
+```
+
+## What the wrapping process does
+
+The initialization command enhances your project by adding necessary files and updating some of them while preserving its functionality as a typical Scrapy project. The additional requirements file, named `requirements_apify.txt`, includes the Apify Python SDK and other essential requirements. The `.actor/` directory contains basic configuration of your Actor. We provide two new Python files [main.py](https://github.com/apify/actor-templates/blob/master/templates/python-scrapy/src/main.py) and [\_\_main\_\_.py](https://github.com/apify/actor-templates/blob/master/templates/python-scrapy/src/__main__.py), where we encapsulate the Scrapy project within an Actor. We also import and use there a few Scrapy components from our [Python SDK](https://github.com/apify/apify-sdk-python/tree/master/src/apify/scrapy). These components facilitate the integration of the Scrapy projects with the Apify platform. Further details about these components are provided in the following subsections.
+
+### Scheduler
+
+The [scheduler](https://docs.scrapy.org/en/latest/topics/scheduler.html) is a core component of Scrapy responsible for receiving and providing requests to be processed. To leverage the [Apify request queue](https://docs.apify.com/platform/storage/request-queue) for storing requests, a custom scheduler becomes necessary. Fortunately, Scrapy is a modular framework, allowing the creation of custom components. As a result, we have implemented the [ApifyScheduler](https://github.com/apify/apify-sdk-python/blob/master/src/apify/scrapy/scheduler.py). When using the Apify CLI wrapping tool, the scheduler is configured in the [src/main.py](https://github.com/apify/actor-templates/blob/master/templates/python-scrapy/src/main.py) file of your Actor.
+
+### Dataset push pipeline
+
+[Item pipelines](https://docs.scrapy.org/en/latest/topics/item-pipeline.html) are used for the processing of the results produced by your spiders. To handle the transmission of result data to the [Apify dataset](https://docs.apify.com/platform/storage/dataset), we have implemented the [ActorDatasetPushPipeline](https://github.com/apify/apify-sdk-python/blob/master/src/apify/scrapy/pipelines.py). When using the Apify CLI wrapping tool, the pipeline is configured in the [src/main.py](https://github.com/apify/actor-templates/blob/master/templates/python-scrapy/src/main.py) file of your Actor. It is assigned the highest integer value (1000), ensuring its execution as the final step in the pipeline sequence.
+
+### Retry middleware
+
+[Downloader middlewares](https://docs.scrapy.org/en/latest/topics/downloader-middleware.html) are a way how to hook into Scrapy's request/response processing. Scrapy comes with various default middlewares, including the [RetryMiddleware](https://docs.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.retry), designed to handle retries for requests that may have failed due to temporary issues. When integrating with the [Apify request queue](https://docs.apify.com/platform/storage/request-queue), it becomes necessary to enhance this middleware to facilitate communication with the request queue marking the requests either as handled or ready for a retry. When using the Apify CLI wrapping tool, the default `RetryMiddleware` is disabled, and [ApifyRetryMiddleware](https://github.com/apify/apify-sdk-python/blob/master/src/apify/scrapy/middlewares/apify_retry.py) takes its place. Configuration for the middlewares is established in the [src/main.py](https://github.com/apify/actor-templates/blob/master/templates/python-scrapy/src/main.py) file of your Actor.
+
+### HTTP proxy middleware
+
+Another default Scrapy [downloader middleware](https://docs.scrapy.org/en/latest/topics/downloader-middleware.html) that requires replacement is [HttpProxyMiddleware](https://docs.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpproxy). To utilize the use of proxies managed through the Apify [ProxyConfiguration](https://github.com/apify/apify-sdk-python/blob/master/src/apify/proxy_configuration.py), we provide [ApifyHttpProxyMiddleware](https://github.com/apify/apify-sdk-python/blob/master/src/apify/scrapy/middlewares/apify_proxy.py). When using the Apify CLI wrapping tool, the default `HttpProxyMiddleware` is disabled, and [ApifyHttpProxyMiddleware](https://github.com/apify/apify-sdk-python/blob/master/src/apify/scrapy/middlewares/apify_proxy.py) takes its place. Additionally, inspect the [.actor/input_schema.json](https://github.com/apify/actor-templates/blob/master/templates/python-scrapy/.actor/input_schema.json) file, where proxy configuration is specified as an input property for your Actor. The processing of this input is carried out together with the middleware configuration in [src/main.py](https://github.com/apify/actor-templates/blob/master/templates/python-scrapy/src/main.py).
+
+## Known limitations
+
+There are some known limitations of running the Scrapy projects on Apify platform we are aware of.
+
+### Asynchronous code in spiders and other components
+
+Scrapy asynchronous execution is based on the [Twisted](https://twisted.org/) library, not the
+[AsyncIO](https://docs.python.org/3/library/asyncio.html), which brings some complications on the table.
+
+Due to the asynchronous nature of the Actors, all of their code is executed as a coroutine inside the `asyncio.run`.
+In order to execute Scrapy code inside an Actor, following the section
+[Run Scrapy from a script](https://docs.scrapy.org/en/latest/topics/practices.html?highlight=CrawlerProcess#run-scrapy-from-a-script)
+from the official Scrapy documentation, we need to invoke a
+[`CrawlProcess.start`](https://github.com/scrapy/scrapy/blob/2.11.0/scrapy/crawler.py#L393:L427)
+method. This method triggers Twisted's event loop, also known as a reactor.
+Consequently, Twisted's event loop is executed within AsyncIO's event loop.
+On top of that, when employing AsyncIO code in spiders or other components, it necessitates the creation of a new
+AsyncIO event loop, within which the coroutines from these components are executed. This means there is
+an execution of the AsyncIO event loop inside the Twisted event loop inside the AsyncIO event loop.
+
+We have resolved this issue by leveraging the [nest-asyncio](https://pypi.org/project/nest-asyncio/) library,
+enabling the execution of nested AsyncIO event loops. For executing a coroutine within a spider or other component,
+it is recommended to use Apify's instance of the nested event loop. Refer to the code example below or derive
+inspiration from Apify's Scrapy components, such as the
+[ApifyScheduler](https://github.com/apify/apify-sdk-python/blob/v1.5.0/src/apify/scrapy/scheduler.py#L114).
+
+```python showLineNumbers
+from apify.scrapy.utils import nested_event_loop
+
+...
+
+# Coroutine execution inside a spider
+nested_event_loop.run_until_complete(my_coroutine())
+```
+
+### More spiders per Actor
+
+It is recommended to execute only one Scrapy spider per Apify Actor.
+
+Mapping more Scrapy spiders to a single Apify Actor does not make much sense. We would have to create a separate
+instace of the [request queue](https://docs.apify.com/platform/storage/request-queue) for every spider.
+Also, every spider can produce a different output resulting in a mess in an output
+[dataset](https://docs.apify.com/platform/storage/dataset). A solution for this could be to store an output
+of every spider to a different [key-value store](https://docs.apify.com/platform/storage/key-value-store). However,
+a much more simple solution to this problem would be to just have a single spider per Actor.
+
+If you want to share common Scrapy components (middlewares, item pipelines, ...) among more spiders (Actors), you
+can use a dedicated Python package containing your components and install it to your Actors environment. The
+other solution to this problem could be to have more spiders per Actor, but keep only one spider run per Actor.
+What spider is going to be executed in an Actor run can be specified in the
+[input schema](https://docs.apify.com/academy/deploying-your-code/input-schema).
+
+## Additional links
+
+- [Scrapy Books Example Actor](https://apify.com/vdusek/scrapy-books-example)
+- [Python Actor Scrapy template](https://apify.com/templates/python-scrapy)
+- [Apify SDK for Python](https://docs.apify.com/sdk/python)
+- [Apify platform](https://docs.apify.com/platform)
+- [Join our developer community on Discord](https://discord.com/invite/jyEM2PRvMU)
+
+> We welcome any feedback! Please feel free to contact us at [python@apify.com](mailto:python@apify.com). Thank you for your valuable input.
diff --git a/website/versioned_docs/version-0.20/reference.md b/website/versioned_docs/version-0.20/reference.md
new file mode 100644
index 000000000..7463b5e32
--- /dev/null
+++ b/website/versioned_docs/version-0.20/reference.md
@@ -0,0 +1,510 @@
+---
+title: Command reference
+---
+
+This section contains printouts of `apify help` for all commands.
+
+<!-- prettier-ignore-start -->
+<!-- commands -->
+* [`apify actor`](#apify-actor)
+* [`apify actor get-input`](#apify-actor-get-input)
+* [`apify actor get-value KEY`](#apify-actor-get-value-key)
+* [`apify actor push-data [ITEM]`](#apify-actor-push-data-item)
+* [`apify actor set-value KEY [VALUE]`](#apify-actor-set-value-key-value)
+* [`apify call [ACTORID]`](#apify-call-actorid)
+* [`apify create [ACTORNAME]`](#apify-create-actorname)
+* [`apify help [COMMAND]`](#apify-help-command)
+* [`apify info`](#apify-info)
+* [`apify init [ACTORNAME]`](#apify-init-actorname)
+* [`apify login`](#apify-login)
+* [`apify logout`](#apify-logout)
+* [`apify pull [ACTORID]`](#apify-pull-actorid)
+* [`apify push [ACTORID]`](#apify-push-actorid)
+* [`apify run`](#apify-run)
+* [`apify secrets`](#apify-secrets)
+* [`apify secrets add NAME VALUE`](#apify-secrets-add-name-value)
+* [`apify secrets rm NAME`](#apify-secrets-rm-name)
+* [`apify task`](#apify-task)
+* [`apify task run TASKID`](#apify-task-run-taskid)
+* [`apify validate-schema [PATH]`](#apify-validate-schema-path)
+
+## `apify actor`
+
+Commands are designed to be used in Actor runs. All commands are in PoC state, do not use in production environments.
+
+```
+USAGE
+  $ apify actor
+
+DESCRIPTION
+  Commands are designed to be used in Actor runs. All commands are in PoC state, do not use in production environments.
+```
+
+_See code: [src/commands/actor/index.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/actor/index.ts)_
+
+## `apify actor get-input`
+
+Gets the Actor input value from the default key-value store associated with the Actor run.
+
+```
+USAGE
+  $ apify actor get-input
+
+DESCRIPTION
+  Gets the Actor input value from the default key-value store associated with the Actor run.
+```
+
+_See code: [src/commands/actor/get-input.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/actor/get-input.ts)_
+
+## `apify actor get-value KEY`
+
+Gets a value from the default key-value store associated with the Actor run.
+
+```
+USAGE
+  $ apify actor get-value KEY
+
+ARGUMENTS
+  KEY  Key of the record in key-value store
+
+DESCRIPTION
+  Gets a value from the default key-value store associated with the Actor run.
+```
+
+_See code: [src/commands/actor/get-value.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/actor/get-value.ts)_
+
+## `apify actor push-data [ITEM]`
+
+Stores an object or an array of objects to the default dataset of the Actor run.
+
+```
+USAGE
+  $ apify actor push-data [ITEM]
+
+ARGUMENTS
+  ITEM  JSON string with one object or array of objects containing data to be stored in the default dataset.
+
+DESCRIPTION
+  Stores an object or an array of objects to the default dataset of the Actor run.
+  It is possible to pass data using item argument or stdin.
+  Passing data using argument:
+  $ apify actor push-data {"foo": "bar"}
+  Passing data using stdin with pipe:
+  $ cat ./test.json | apify actor push-data
+```
+
+_See code: [src/commands/actor/push-data.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/actor/push-data.ts)_
+
+## `apify actor set-value KEY [VALUE]`
+
+Sets or removes record into the default KeyValueStore associated with the Actor run.
+
+```
+USAGE
+  $ apify actor set-value KEY [VALUE] [-c <value>]
+
+ARGUMENTS
+  KEY    Key of the record in key-value store.
+  VALUE  Record data, which can be one of the following values:
+         - If empty, the record in the key-value store is deleted.
+         - If no `contentType` flag is specified, value is expected to be any JSON string value.
+         - If options.contentType is set, value is taken as is.
+
+FLAGS
+  -c, --contentType=<value>  Specifies a custom MIME content type of the record. By default "application/json" is used.
+
+DESCRIPTION
+  Sets or removes record into the default KeyValueStore associated with the Actor run.
+  It is possible to pass data using argument or stdin.
+  Passing data using argument:
+  $ apify actor set-value KEY my-value
+  Passing data using stdin with pipe:
+  $ cat ./my-text-file.txt | apify actor set-value KEY --contentType text/plain
+```
+
+_See code: [src/commands/actor/set-value.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/actor/set-value.ts)_
+
+## `apify call [ACTORID]`
+
+Runs a specific Actor remotely on the Apify cloud platform.
+
+```
+USAGE
+  $ apify call [ACTORID] [-b <value>] [-t <value>] [-m <value>] [-w <value>] [-i <value> | --input-file
+    <value>] [-s] [-o]
+
+ARGUMENTS
+  ACTORID  Name or ID of the Actor to run (e.g. "my-actor", "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not
+           provided, the command runs the remote Actor specified in the ".actor/actor.json" file.
+
+FLAGS
+  -b, --build=<value>            Tag or number of the build to run (e.g. "latest" or "1.2.34").
+  -i, --input=<value>            Optional JSON input to be given to the Actor.
+  -m, --memory=<value>           Amount of memory allocated for the Actor run, in megabytes.
+  -o, --output-dataset           Prints out the entire default dataset on successful run of the Actor.
+  -s, --silent                   Prevents printing the logs of the Actor run to the console.
+  -t, --timeout=<value>          Timeout for the Actor run in seconds. Zero value means there is no timeout.
+  -w, --wait-for-finish=<value>  Seconds for waiting to run to finish, if no value passed, it waits forever.
+      --input-file=<value>       Optional path to a file with JSON input to be given to the Actor. The file must be a
+                                 valid JSON file. You can also specify `-` to read from standard input.
+
+DESCRIPTION
+  Runs a specific Actor remotely on the Apify cloud platform.
+  The Actor is run under your current Apify account. Therefore you need to be logged in by calling "apify login". It
+  takes input for the Actor from the default local key-value store by default.
+```
+
+_See code: [src/commands/call.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/call.ts)_
+
+## `apify create [ACTORNAME]`
+
+Creates a new Actor project directory from a selected boilerplate template.
+
+```
+USAGE
+  $ apify create [ACTORNAME] [-t <value>] [--skip-dependency-install] [--omit-optional-deps]
+
+ARGUMENTS
+  ACTORNAME  Name of the Actor and its directory
+
+FLAGS
+  -t, --template=<value>         Template for the Actor. If not provided, the command will prompt for it.
+                                 Visit
+                                 https://raw.githubusercontent.com/apify/actor-templates/master/templates/manifest.json
+                                 to find available template names.
+      --omit-optional-deps       Skip installing optional dependencies.
+      --skip-dependency-install  Skip installing Actor dependencies.
+
+DESCRIPTION
+  Creates a new Actor project directory from a selected boilerplate template.
+```
+
+_See code: [src/commands/create.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/create.ts)_
+
+## `apify help [COMMAND]`
+
+Display help for apify.
+
+```
+USAGE
+  $ apify help [COMMAND...] [-n]
+
+ARGUMENTS
+  COMMAND...  Command to show help for.
+
+FLAGS
+  -n, --nested-commands  Include all nested commands in the output.
+
+DESCRIPTION
+  Display help for apify.
+```
+
+_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v6.2.10/src/commands/help.ts)_
+
+## `apify info`
+
+Displays information about the currently active Apify account.
+
+```
+USAGE
+  $ apify info
+
+DESCRIPTION
+  Displays information about the currently active Apify account.
+  The information is printed to the console.
+```
+
+_See code: [src/commands/info.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/info.ts)_
+
+## `apify init [ACTORNAME]`
+
+Initializes a new Actor project in an existing directory.
+
+```
+USAGE
+  $ apify init [ACTORNAME] [-y]
+
+ARGUMENTS
+  ACTORNAME  Name of the Actor. If not provided, you will be prompted for it.
+
+FLAGS
+  -y, --yes  Automatic yes to prompts; assume "yes" as answer to all prompts. Note that in some cases, the command may
+             still ask for confirmation.
+
+DESCRIPTION
+  Initializes a new Actor project in an existing directory.
+  If the directory contains a Scrapy project in Python, the command automatically creates wrappers so that you can run
+  your scrapers without changes.
+
+  The command creates the ".actor/actor.json" file and the "storage" directory in the current directory, but does not
+  touch any other existing files or directories.
+
+  WARNING: The directory at "storage" will be overwritten if it already exists.
+```
+
+_See code: [src/commands/init.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/init.ts)_
+
+## `apify login`
+
+Logs in to your Apify account.
+
+```
+USAGE
+  $ apify login [-t <value>] [-m console|manual]
+
+FLAGS
+  -m, --method=<option>  [Optional] Method of logging in to Apify
+                         <options: console|manual>
+  -t, --token=<value>    [Optional] Apify API token
+
+DESCRIPTION
+  Logs in to your Apify account.
+  The API token and other account information is stored in the ~/.apify directory, from where it is read by all other
+  "apify" commands. To log out, call "apify logout".
+```
+
+_See code: [src/commands/login.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/login.ts)_
+
+## `apify logout`
+
+Logs out of your Apify account.
+
+```
+USAGE
+  $ apify logout
+
+DESCRIPTION
+  Logs out of your Apify account.
+  The command deletes the API token and all other account information stored in the ~/.apify directory. To log in again,
+  call "apify login".
+```
+
+_See code: [src/commands/logout.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/logout.ts)_
+
+## `apify pull [ACTORID]`
+
+Pulls an Actor from the Apify platform to the current directory. If it is defined as Git repository, it will be cloned. If it is defined as Web IDE, it will fetch the files.
+
+```
+USAGE
+  $ apify pull [ACTORID] [-v <value>]
+
+ARGUMENTS
+  ACTORID  Name or ID of the Actor to run (e.g. "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not provided, the
+           command will update the Actor in the current directory based on its name in ".actor/actor.json" file.
+
+FLAGS
+  -v, --version=<value>  Actor version number which will be pulled, e.g. 1.2. Default: the highest version
+
+DESCRIPTION
+  Pulls an Actor from the Apify platform to the current directory. If it is defined as Git repository, it will be
+  cloned. If it is defined as Web IDE, it will fetch the files.
+```
+
+_See code: [src/commands/pull.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/pull.ts)_
+
+## `apify push [ACTORID]`
+
+Uploads the Actor to the Apify platform and builds it there.
+
+```
+USAGE
+  $ apify push [ACTORID] [--version-number <value>] [-v <value>] [-b <value>] [-w <value>] [--no-prompt]
+    [--force]
+
+ARGUMENTS
+  ACTORID  Name or ID of the Actor to push (e.g. "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not provided, the
+           command will create or modify the Actor with the name specified in ".actor/actor.json" file.
+
+FLAGS
+  -b, --build-tag=<value>        Build tag to be applied to the successful Actor build. By default, it is taken from the
+                                 ".actor/actor.json" file
+  -v, --version=<value>          Actor version number to which the files should be pushed. By default, it is taken from
+                                 the ".actor/actor.json" file.
+  -w, --wait-for-finish=<value>  Seconds for waiting to build to finish, if no value passed, it waits forever.
+      --force                    Push an Actor even when the local files are older than the Actor on the platform.
+      --no-prompt                Do not prompt for opening the Actor details in a browser. This will also not open the
+                                 browser automatically.
+      --version-number=<value>   DEPRECATED: Use flag version instead. Actor version number to which the files should be
+                                 pushed. By default, it is taken from the ".actor/actor.json" file.
+
+DESCRIPTION
+  Uploads the Actor to the Apify platform and builds it there.
+  The Actor settings are read from the ".actor/actor.json" file in the current directory, but they can be overridden
+  using command-line options.
+  NOTE: If the source files are smaller than 3 MB then they are uploaded as
+  "Multiple source files", otherwise they are uploaded as "Zip file".
+
+  When there's an attempt to push files that are older than the Actor on the platform, the command will fail. Can be
+  overwritten with --force flag.
+```
+
+_See code: [src/commands/push.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/push.ts)_
+
+## `apify run`
+
+Runs the Actor locally in the current directory.
+
+```
+USAGE
+  $ apify run [-p] [--purge-queue] [--purge-dataset] [--purge-key-value-store] [--entrypoint <value>] [-i
+    <value> | --input-file <value>]
+
+FLAGS
+  -i, --input=<value>          Optional JSON input to be given to the Actor.
+  -p, --purge                  Shortcut that combines the --purge-queue, --purge-dataset and --purge-key-value-store
+                               options.
+      --entrypoint=<value>     Optional entrypoint for running with injected environment variables.
+                               For Python, it is the module name, or a path to a file.
+                               For node.js, it is the npm script name, or a path to a JS/MJS file. You can also pass in
+                               a directory name, provided that directory contains an "index.js" file.
+      --input-file=<value>     Optional path to a file with JSON input to be given to the Actor. The file must be a
+                               valid JSON file. You can also specify `-` to read from standard input.
+      --purge-dataset          Deletes the local directory containing the default dataset before the run starts.
+      --purge-key-value-store  Deletes all records from the default key-value store in the local directory before the
+                               run starts, except for the "INPUT" key.
+      --purge-queue            Deletes the local directory containing the default request queue before the run starts.
+
+DESCRIPTION
+  Runs the Actor locally in the current directory.
+  It sets various APIFY_XYZ environment variables in order to provide a working execution environment for the Actor. For
+  example, this causes the Actor input, as well as all other data in key-value stores, datasets or request queues to be
+  stored in the "storage" directory, rather than on the Apify platform.
+
+  NOTE: You can override the command's default behavior for Node.js Actors by overriding the "start" script in the
+  package.json file. You can set up your own main file or environment variables by changing it.
+```
+
+_See code: [src/commands/run.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/run.ts)_
+
+## `apify secrets`
+
+Manages secret values for Actor environment variables.
+
+```
+USAGE
+  $ apify secrets
+
+DESCRIPTION
+  Manages secret values for Actor environment variables.
+
+  Example:
+  $ apify secrets add mySecret TopSecretValue123
+
+  Now the "mySecret" value can be used in an environment variable defined in ".actor/actor.json" file by adding the "@"
+  prefix:
+
+  {
+  "actorSpecification": 1,
+  "name": "my_actor",
+  "environmentVariables": { "SECRET_ENV_VAR": "@mySecret" },
+  "version": "0.1
+  }
+
+  When the Actor is pushed to Apify cloud, the "SECRET_ENV_VAR" and its value is stored as a secret environment variable
+  of the Actor.
+```
+
+_See code: [src/commands/secrets/index.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/secrets/index.ts)_
+
+## `apify secrets add NAME VALUE`
+
+Adds a new secret value.
+
+```
+USAGE
+  $ apify secrets add NAME VALUE
+
+ARGUMENTS
+  NAME   Name of the secret
+  VALUE  Value of the secret
+
+DESCRIPTION
+  Adds a new secret value.
+  The secrets are stored to a file at ~/.apify
+```
+
+_See code: [src/commands/secrets/add.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/secrets/add.ts)_
+
+## `apify secrets rm NAME`
+
+Removes the secret.
+
+```
+USAGE
+  $ apify secrets rm NAME
+
+ARGUMENTS
+  NAME  Name of the secret
+
+DESCRIPTION
+  Removes the secret.
+```
+
+_See code: [src/commands/secrets/rm.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/secrets/rm.ts)_
+
+## `apify task`
+
+Commands are designed to be used to interact with Tasks.
+
+```
+USAGE
+  $ apify task
+
+DESCRIPTION
+  Commands are designed to be used to interact with Tasks.
+```
+
+_See code: [src/commands/task/index.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/task/index.ts)_
+
+## `apify task run TASKID`
+
+Runs a specific Actor remotely on the Apify cloud platform.
+
+```
+USAGE
+  $ apify task run TASKID [-b <value>] [-t <value>] [-m <value>] [-w <value>]
+
+ARGUMENTS
+  TASKID  Name or ID of the Task to run (e.g. "my-task" or "E2jjCZBezvAZnX8Rb").
+
+FLAGS
+  -b, --build=<value>            Tag or number of the build to run (e.g. "latest" or "1.2.34").
+  -m, --memory=<value>           Amount of memory allocated for the Task run, in megabytes.
+  -t, --timeout=<value>          Timeout for the Task run in seconds. Zero value means there is no timeout.
+  -w, --wait-for-finish=<value>  Seconds for waiting to run to finish, if no value passed, it waits forever.
+
+DESCRIPTION
+  Runs a specific Actor remotely on the Apify cloud platform.
+  The Actor is run under your current Apify account. Therefore you need to be logged in by calling "apify login". It
+  takes input for the Actor from the default local key-value store by default.
+```
+
+_See code: [src/commands/task/run.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/task/run.ts)_
+
+## `apify validate-schema [PATH]`
+
+Validates input schema and prints errors found.
+
+```
+USAGE
+  $ apify validate-schema [PATH]
+
+ARGUMENTS
+  PATH  Optional path to your INPUT_SCHEMA.json file. If not provided ./INPUT_SCHEMA.json is used.
+
+DESCRIPTION
+  Validates input schema and prints errors found.
+  The input schema for the Actor is used from these locations in order of preference.
+  The first one found is validated as it would be the one used on the Apify platform.
+  1. Directly embedded object in ".actor/actor.json" under 'input' key
+  2. Path to JSON file referenced in ".actor/actor.json" under 'input' key
+  3. JSON file at .actor/INPUT_SCHEMA.json
+  4. JSON file at INPUT_SCHEMA.json
+
+  You can also pass any custom path to your input schema to have it validated instead.
+```
+
+_See code: [src/commands/validate-schema.ts](https://github.com/apify/apify-cli/blob/v0.20.10/src/commands/validate-schema.ts)_
+<!-- commandsstop -->
+<!-- prettier-ignore-end -->
diff --git a/website/versioned_docs/version-0.20/telemetry.md b/website/versioned_docs/version-0.20/telemetry.md
new file mode 100644
index 000000000..360c813bd
--- /dev/null
+++ b/website/versioned_docs/version-0.20/telemetry.md
@@ -0,0 +1,24 @@
+---
+sidebar_label: Telemetry
+title: Telemetry
+---
+
+Apify collects telemetry data about the general usage of the CLI to help us improve the product. Participation in this program is optional and you may opt out if you prefer not to share any information.
+
+## Data Collection
+
+All telemetry data is collected and stored securely on [Mixpanel](https://mixpanel.com/). We do not collect any sensitive information such as your API token or personal information.
+
+### Metrics Collected
+
+Before a user connects to the Apify platform, we collect anonymous information about CLI usage including:
+
+- Usage of all commands
+- Internal attributes of the local environment (OS, shell, Node.js version, Python version, Apify CLI version)
+- For the `actor create` command, we identify which template was used to create the Actor (language, template name, template ID)
+
+After a user connects to the Apify platform (successful `apify login`), we collect the same information about CLI usage along with the ID of the connected user. You can read more about how we protect personal information in our [Privacy Policy](https://apify.com/privacy-policy).
+
+## How to opt out
+
+You can disable telemetry by setting the "APIFY_CLI_DISABLE_TELEMETRY" environment variable to "1". After setting this variable, the CLI will not send any telemetry data whether you are connected with Apify or not.
diff --git a/website/versioned_docs/version-0.20/troubleshooting.md b/website/versioned_docs/version-0.20/troubleshooting.md
new file mode 100644
index 000000000..3ae6d5282
--- /dev/null
+++ b/website/versioned_docs/version-0.20/troubleshooting.md
@@ -0,0 +1,8 @@
+---
+sidebar_label: Troubleshooting
+title: Troubleshooting
+---
+
+For general support, reach out to us at [apify.com/contact](https://apify.com/contact).
+
+If you believe you are encountering a bug, file it on [GitHub](https://github.com/apify/apify-cli/issues/new).
diff --git a/website/versioned_docs/version-0.20/vars.md b/website/versioned_docs/version-0.20/vars.md
new file mode 100644
index 000000000..ba0e60709
--- /dev/null
+++ b/website/versioned_docs/version-0.20/vars.md
@@ -0,0 +1,77 @@
+---
+sidebar_label: Environment variables
+title: Environment variables
+---
+
+There are two options how you can set up environment variables for Actors.
+
+### Set up environment variables in `.actor/actor.json`
+
+All keys from `env` will be set as environment variables into Apify platform after you push Actor to Apify. Current values on Apify will be overridden.
+
+```json
+{
+  "actorSpecification": 1,
+  "name": "dataset-to-mysql",
+  "version": "0.1",
+  "buildTag": "latest",
+  "environmentVariables": {
+    "MYSQL_USER": "my_username",
+    "MYSQL_PASSWORD": "@mySecretPassword"
+  }
+}
+```
+
+### Set up environment variables in Apify Console
+
+In [Apify Console](https://console.apify.com/actors) select your Actor, you can set up variables into Source tab.
+After setting up variables in the app, remove the `environmentVariables` from `.actor/actor.json`. Otherwise, variables from `.actor/actor.json` will override variables in the app.
+
+```json
+{
+  "actorSpecification": 1,
+  "name": "dataset-to-mysql",
+  "version": "0.1",
+  "buildTag": "latest"
+}
+```
+
+#### How to set secret environment variables in `.actor/actor.json`
+
+CLI provides commands to manage secrets environment variables. Secrets are stored to the `~/.apify` directory.
+You can add a new secret using the command:
+
+```bash
+apify secrets add mySecretPassword pwd1234
+```
+
+After adding a new secret you can use the secret in `.actor/actor.json`.
+
+```text
+{
+    "actorSpecification": 1,
+    "name": "dataset-to-mysql",
+    ...
+    "environmentVariables": {
+      "MYSQL_PASSWORD": "@mySecretPassword"
+    },
+    ...
+}
+```
+
+### Need help?
+
+To see all CLI commands simply run:
+
+```bash
+apify help
+```
+
+To get information about a specific command run:
+
+```bash
+apify help COMMAND
+```
+
+Still haven't found what you were looking for? Please go to [Apify Help center](https://www.apify.com/help)
+or [contact us](https://www.apify.com/contact).
diff --git a/website/versioned_sidebars/version-0.20-sidebars.json b/website/versioned_sidebars/version-0.20-sidebars.json
new file mode 100644
index 000000000..8c1531bf3
--- /dev/null
+++ b/website/versioned_sidebars/version-0.20-sidebars.json
@@ -0,0 +1,39 @@
+[
+  [
+    {
+      "type": "doc",
+      "id": "index",
+      "label": "Apify CLI"
+    },
+    {
+      "type": "doc",
+      "id": "installation",
+      "label": "Installation"
+    },
+    {
+      "type": "doc",
+      "id": "vars",
+      "label": "Environment variables"
+    },
+    {
+      "type": "doc",
+      "id": "reference",
+      "label": "Command reference"
+    },
+    {
+      "type": "doc",
+      "id": "integrating-scrapy",
+      "label": "Integrating Scrapy"
+    },
+    {
+      "type": "doc",
+      "id": "troubleshooting",
+      "label": "Troubleshooting"
+    },
+    {
+      "type": "doc",
+      "id": "changelog",
+      "label": "Changelog"
+    }
+  ]
+]
diff --git a/website/versions.json b/website/versions.json
index 0d4f101c7..e264dc292 100644
--- a/website/versions.json
+++ b/website/versions.json
@@ -1,2 +1,3 @@
 [
+  "0.20"
 ]