Move "dlt in notebooks"

docs/website/docs/general-usage/dataset-access/streamlit.md

@@ -31,6 +31,18 @@ dlt pipeline {pipeline_name} show
 
 Use the pipeline name you defined in your Python code with the `pipeline_name` argument. If you are unsure, you can use the `dlt pipeline --list` command to list all pipelines.
 
+## Credentials
+
+`dlt` will look for `secrets.toml` and `config.toml` in the `.dlt` folder.
+
+If `secrets.toml` are not found, it will use
+`secrets.toml` from `.streamlit` folder.
+
+If you run locally, maintain your usual `.dlt` folder.
+
+When running on streamlit cloud, paste the content of `dlt`
+`secrets.toml` into the `streamlit` secrets.
+
 ## Inspecting your data
 
 You can now inspect the schema and your data. Use the left sidebar to switch between:

docs/website/docs/walkthroughs/run-a-pipeline.md

@@ -140,7 +140,24 @@ destination, etc. Please refer to
 [Running in production](../running-in-production/running.md#inspect-and-save-the-load-info-and-trace)
 for more details.
 
-## 5. Detect and handle problems
+## Run dlt in Notebooks
+
+### Colab
+You'll need to install `dlt` like any other dependency:
+```sh
+!pip install dlt
+```
+
+You can configure secrets using **Secrets** sidebar. Just create a variable with the name `secrets.toml` and paste
+the content of the **toml** file from your `.dlt` folder into it. We support `config.toml` variable as well.
+
+:::note
+`dlt` will not reload the secrets automatically. Please restart your interpreter in Colab options when you add/change
+content of the variables above.
+:::
+
+
+## Troubleshooting
 
 What happens if something goes wrong? In most cases, the `dlt` `run` command raises exceptions. We put a
 lot of effort into making the exception messages easy to understand. Reading them is the first step

docs/website/sidebars.js

@@ -271,7 +271,6 @@ const sidebars = {
             'general-usage/full-loading',
           ]
         },
-        'dlt-ecosystem/notebooks'
       ]
     },
     {