Repository: kedro-org/vscode-kedro
Pull request #175: Kedro VSCode extension walkthrough
Author: login: jitu5
Created: 2025-03-14T10:15:31Z | Merged: 2025-04-03T11:04:35Z

# Description: 

Resolves https://github.com/kedro-org/vscode-kedro/issues/151

This PR introduces a VSCode walkthrough for the Kedro extension, providing step-by-step guidance for users, from setting up virtual environments to visualizing pipelines using Kedro-Viz.

# Key changes:

### Documentation Enhancements:

* [`assets/markdown/install.md`](diffhunk://#diff-ae06e59f9765208f5b96b59d2a1e59fef5922ed6c9366ac0c450b8314907fdc8R1-R142): Added detailed instructions for setting up Kedro, including installation prerequisites, creating virtual environments using `venv` and `conda`, and verifying the installation.
* [`assets/markdown/new_project.md`](diffhunk://#diff-e88d67ecf67b2e2d0c5045ee035ac5fbdf0f1f0a1a84427c659fee9132c28746R1-R157): Provided a comprehensive guide on creating a new Kedro project, including using the `kedro new` command, selecting tools, and adding example pipelines.
* [`assets/markdown/set_project_path.md`](diffhunk://#diff-146edbc4eadda70423121c780ffe9f692733d9f02342984cfd136d1048b5b0d5R1-R28): Added instructions for setting a custom Kedro project path in VS Code using the command palette or settings.
* [`assets/markdown/learn_more.md`](diffhunk://#diff-71b12f6b725ce3ad72e70c666b3cedc5faa978a288082b91a185b312573e1c43R1-R5): Included links to additional Kedro documentation resources.

### Walkthrough and Configuration:

* [`package.json`](diffhunk://#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R144-R197): Introduced a new walkthrough for setting up and running a Kedro project in VS Code, including steps for installing Kedro, creating a project, selecting the Python interpreter, and running Kedro-Viz.

### Dependency Updates:

* [`src/test/python_tests/requirements.txt`](diffhunk://#diff-2ac3beb3ff8fab01882ffc641ea32638b24b3277ea4e45e2580b46fae732305eL2-L8): Updated the Python version used for generating the requirements file to Python 3.13 and adjusted dependencies accordingly. [[1]](diffhunk://#diff-2ac3beb3ff8fab01882ffc641ea32638b24b3277ea4e45e2580b46fae732305eL2-L8) [[2]](diffhunk://#diff-2ac3beb3ff8fab01882ffc641ea32638b24b3277ea4e45e2580b46fae732305eL17-L22)

# How to test:
- Checkout current branch
- Run `make build`, this will generate `.visx` file
- Install the generated `.visx` file
- After installing goto Help -> Welcome
- On Welcome page on the right side, check the Walkthroughs
- If you dont find Kedro walkthrough, please click on "more..."
- Search Kedro and select

# Gif:
![Kedro extension walkthrough](https://github.com/user-attachments/assets/dd02f6e4-7ad7-4991-bbda-134b19c4a318)




Diff:
diff --git a/assets/markdown/install.md b/assets/markdown/install.md
new file mode 100644
index 00000000..0620957f
--- /dev/null
+++ b/assets/markdown/install.md
@@ -0,0 +1,38 @@
+# Set up and run Kedro
+*P.S.: If you’re starting a new Kedro project, follow Steps 0. If you already have an existing Kedro project, you can skip to Step 1: “Select the correct Python interpreter.”*
+
+## 0.1 Create a directory for working with your project and navigate to it
+
+```bash
+mkdir your-kedro-project && cd your-kedro-project
+```
+
+## 0.2 Create a virtual environment for your Kedro project
+
+Choose a virtual environment tool: `venv`, `conda`, or `uv`. Or use any another environment managers you prefer.
+
+**P.S.:** `venv` is already built-in with Python 3. Install `conda` or `uv` when necessary.
+
+Refer to https://code.visualstudio.com/docs/python/environments
+
+## 0.3 Install Kedro
+
+`pip install kedro` (PyPI)
+
+`conda install -c conda-forge kedro` (conda)
+
+`uv pip install kedro` (uv)
+
+## 0.4 Create and run Kedro project
+
+To create a basic Kedro project with default setup, run this in your desired directory:
+```bash
+kedro new --name=spaceflights --example=y
+```
+
+To run your Kedro project:
+```bash
+kedro run
+```
+
+For more info, refer to our documentation: https://docs.kedro.org/en/stable/get_started/new_project.html
\ No newline at end of file
diff --git a/assets/markdown/learn_more.md b/assets/markdown/learn_more.md
new file mode 100644
index 00000000..591e601d
--- /dev/null
+++ b/assets/markdown/learn_more.md
@@ -0,0 +1,5 @@
+# For more information, please check out our documentation below:
+
+- [Kedro documentation](https://docs.kedro.org/en/stable)
+- [Kedro-Viz documentation](https://docs.kedro.org/projects/kedro-viz/en/stable)
+- [Kedro VSCode extension documentation](https://marketplace.visualstudio.com/items?itemName=kedro.Kedro)
\ No newline at end of file
diff --git a/assets/markdown/run_kedro-Viz.md b/assets/markdown/run_kedro-Viz.md
new file mode 100644
index 00000000..a9f05a0f
--- /dev/null
+++ b/assets/markdown/run_kedro-Viz.md
@@ -0,0 +1,13 @@
+# Install dependencies and run Kedro-Viz
+
+**Note:** For Kedro VS Code extension to work, please open a `.py` or `.yaml` file.
+
+### 5.1 Run Kedro Viz
+   - Press `Cmd` + `Shift` + `P` (on macOS) or `Ctrl` + `Shift` + `P` (on Windows/Linux)
+   - Type and select `Kedro: Run Kedro Viz`
+
+![Setting Kedro project path through Command Palette](../viz-vsc-run-kedro-viz-1.gif)
+
+#### P.S.: If you don't have Kedro-Viz 11.0.0 or later, you will be prompted to install or update it.
+
+![Setting Kedro project path through Command Palette](../viz-vsc-run-kedro-viz-2.gif)
\ No newline at end of file
diff --git a/assets/markdown/select_interpreter.md b/assets/markdown/select_interpreter.md
new file mode 100644
index 00000000..28fb6580
--- /dev/null
+++ b/assets/markdown/select_interpreter.md
@@ -0,0 +1,17 @@
+## 1.1 Select the correct Python interpreter
+
+#### 1.1.1 Select the interpreter that has Kedro and the necessary project dependencies installed. For more info, refer to: https://code.visualstudio.com/docs/python/environments#_working-with-python-interpreters
+
+#### 1.1.2 After selecting the interpreter, check for the orange warning icon below—if it appears, relaunch the terminal.
+
+![Verify the correct python interpreter](../vsc-orange-icon.gif)
+
+## 1.2 Set up or modify environment correctly
+
+To prevent conflicts between environments and ensure Kedro runs with the correct dependencies. Make sure you're using the correct virtual environment where Kedro is installed, and deactivate any others you don't need.
+
+Deactivate the unnecessary environment and ensure only the one with Kedro installed. E.g.
+
+`(.venv) (base) <your-computer-name> <your-kedro-project> % deactivate`
+
+`(.venv) <your-computer-name> <your-kedro-project> %`
\ No newline at end of file
diff --git a/assets/markdown/set_project_path.md b/assets/markdown/set_project_path.md
new file mode 100644
index 00000000..c0de9180
--- /dev/null
+++ b/assets/markdown/set_project_path.md
@@ -0,0 +1,14 @@
+# Set Custom Kedro Project Path
+
+### 2.1 Specify a custom path to your Kedro project root directory
+Please refer to “Set Custom Kedro Project Path” in https://marketplace.visualstudio.com/items?itemName=kedro.Kedro
+
+### 2.2 How to get the absolute path of your Kedro project
+
+   - Press `Cmd` + `Shift` + `E` (on macOS) or `Ctrl` + `Shift` + `E` (on Windows/Linux) to open VSCode explorer
+   - Locate your Kedro project folder
+   - Right click on it and select `Copy path`
+
+**Note:** This step is applicable to those who have their kedro project not at the root directory or they have multiple kedro projects.
+
+
diff --git a/assets/viz-vsc-run-kedro-viz-1.gif b/assets/viz-vsc-run-kedro-viz-1.gif
new file mode 100644
index 00000000..355aae12
Binary files /dev/null and b/assets/viz-vsc-run-kedro-viz-1.gif differ
diff --git a/assets/viz-vsc-run-kedro-viz-2.gif b/assets/viz-vsc-run-kedro-viz-2.gif
new file mode 100644
index 00000000..59ae52bd
Binary files /dev/null and b/assets/viz-vsc-run-kedro-viz-2.gif differ
diff --git a/assets/vsc-orange-icon.gif b/assets/vsc-orange-icon.gif
new file mode 100644
index 00000000..7ac0af97
Binary files /dev/null and b/assets/vsc-orange-icon.gif differ
diff --git a/package.json b/package.json
index 0ccddc52..5099c886 100644
--- a/package.json
+++ b/package.json
@@ -141,6 +141,48 @@
                 }
             }
         },
+        "walkthroughs": [
+            {
+              "id": "kedro-extension-setup",
+              "title": "Get Started with Kedro",
+              "description": "Learn how to set up and run a Kedro project, and visualize your pipeline in VS Code using the Kedro extension.",
+              "steps": [
+                {
+                  "id": "setup-kedro",
+                  "title": "Step 0: Set up and run Kedro",
+                  "description": "Learn how to install & run Kedro and set up a virtual environment.",
+                  "media": { "markdown": "assets/markdown/install.md" }
+                },
+                {
+                  "id": "select-python-interpreter",
+                  "title": "Step 1: Select the correct Python interpreter",
+                  "description": "Make sure you select the correct Python interpreter that has Kedro installed.\n\n[Select Interpreter](command:python.setInterpreter)",
+                  "media": { "markdown": "assets/markdown/select_interpreter.md" },
+                  "completionEvents": ["onCommand:python.setInterpreter"]
+                },
+                {
+                  "id": "configure-project-root",
+                  "title": "Step 2: Configure project's root (Optional)",
+                  "description": "You may need to set the project's root path for Kedro-related features.\n\n[Set Kedro Project Path](command:kedro.kedroProjectPath)",
+                  "media": { "markdown": "assets/markdown/set_project_path.md" },
+                  "completionEvents": ["onCommand:kedro.kedroProjectPath"]
+                },
+                {
+                  "id": "run-kedro-viz",
+                  "title": "Step 3:  Install dependencies and run Kedro Viz",
+                  "description": "Open the command palette and type\n\n ``Kedro: Run Kedro Viz`` \n\n[Open Command Palette](command:workbench.action.showCommands)",
+                  "media": { "markdown": "assets/markdown/run_kedro-Viz.md" },
+                  "completionEvents": ["onCommand:kedro.runKedroViz"]
+                },
+                {
+                  "id": "learn-more",
+                  "title": "Learn more",
+                  "description": "Great job! You've now completed Getting Started with Kedro. But don't stop here! Please checkout Kedro documentation for more information.",
+                  "media": { "markdown": "assets/markdown/learn_more.md" }
+                }
+              ]
+            }
+        ],
         "commands": [
             {
                 "title": "Restart Server",
diff --git a/requirements.txt b/requirements.txt
index 7e2775f1..4f6a30eb 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -8,7 +8,7 @@ attrs==25.3.0
     # via
     #   cattrs
     #   lsprotocol
-cattrs==24.1.2
+cattrs==24.1.3
     # via
     #   lsprotocol
     #   pygls
@@ -20,5 +20,5 @@ packaging==24.2
     # via -r ./requirements.in
 pygls==1.3.1
     # via -r ./requirements.in
-typing-extensions==4.12.2
+typing-extensions==4.13.0
     # via cattrs


Reviews:
user: login: noklam
body: The walkthrough seems very long to me. The last discussion that I recalled I thought we are going to focus on onboarding user with the extension only. The current walkthrough have a lot of documentation content inside, i.e. choosing tool, choosing a virtual environment, relaunch terminal, launching `kedro viz` command etc etc which is not related to the extension.


state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-01T13:24:10Z
user: login: astrojuanlu
body: Thanks a lot @jitu5 and @iamelijahko!

This walkthrough does a great job at describing every possible corner case, even with weirdly configured Python interpreters. It also suffers from having to explain to users that to run `kedro new` they first have to install Kedro etc etc, which is the "double venv" problem explained in https://github.com/kedro-org/kedro/issues/681

However, I think the cost of doing so is having too much text on the right hand side, which many users might consider overwhelming (I agree with @noklam on this one). I think there is a tradeoff here, in that adding very long explanations comes at a cost, and so we'd have to strike a balance.

I am making a series of suggestions to simplify the sequence of steps, offload some of the information to external, official sources, and shrink some of the explanations at the cost of potentially leaving some gaps.

I know we have validated the current text with users already though, which makes me feel bad about suggesting so many changes. So take these comments as you desire.

(Maybe going forward we could do 1 round of internal review first, then validate with users, then adjust?)

Two other high level comments:

- Some parts of the text are rendered strangely

<img width="619" alt="image" src="https://github.com/user-attachments/assets/682f1649-2af9-4023-b258-b9f30e71d9c2" />

- The walkthrough didn't open automatically after I installed the `.vsix` file
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-01T14:06:50Z
user: login: jitu5
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-01T18:13:31Z
user: login: astrojuanlu
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-02T07:30:21Z
user: login: jitu5
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-02T11:58:25Z
user: login: astrojuanlu
body: Let's ship this!
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-02T14:01:39Z
user: login: ravi-kumar-pilla
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-02T19:27:08Z
user: login: ravi-kumar-pilla
body: Left a minor comment. But looks good to me. Thank you @jitu5 and @iamelijahko
state: APPROVED
author_association: NONE
submitted_at: 2025-04-02T19:28:06Z
user: login: Huongg
body: the code looks good to me, thank you @jitu5. 

Lets 🚢  this 
state: APPROVED
author_association: NONE
submitted_at: 2025-04-03T09:35:16Z
user: login: rashidakanchwala
body: LGTM. had a call with Jitendra who gave me the walkthrough :) 

great work Elijah and Jitendra. I learnt a new term Protoduction --which is a combination of the words prototype + production and means a prototype that finally went into production. and this is an excellent example of it!
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T09:47:16Z
user: login: noklam
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T10:44:14Z

Review comments:
diff_hunk: @@ -0,0 +1,57 @@
+# Set up and install Kedro
+*P.S.: Steps 0 and 1 are for users who want to start a new Kedro project—if you already have an existing Kedro project, skip to Step 2: “Select the correct Python interpreter.”*
path: assets/markdown/install.md
user: login: astrojuanlu
body: "For users who want to start"

Better to always refer to users in second person
created_at: 2025-04-01T13:47:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,57 @@
+# Set up and install Kedro
+*P.S.: Steps 0 and 1 are for users who want to start a new Kedro project—if you already have an existing Kedro project, skip to Step 2: “Select the correct Python interpreter.”*
+
+## 0.1 Create a directory for working with your project and navigate to it
+
+```bash
+mkdir your-kedro-project && cd your-kedro-project
+```
+
+## 0.2 Create a virtual environment for your Kedro project
+
+Choose a virtual environment tool: `venv`, `conda`, or `uv`. Or use any another environment managers you prefer.
+
+**P.S.:** `venv` is already built-in with Python 3. Install `conda` or `uv` when necessary.
+
+## 0.3 Create a new virtual environment in your-kedro-project directory
+
+Using `venv`
+
+`python -m venv .venv`
+
+
+Using `conda`
+
+`conda create --name <your-environment-name> python=3.10 -y`
+
+(You can use any Python version ≥ 3.9 and ≤ 3.11 for your project)
+
+
+Using `uv`
+
+`uv init` (initialize project)
+
+`uv venv`
path: assets/markdown/install.md
user: login: astrojuanlu
body: Can we cross link other walkthroughs? Or otherwise, remove all this content and refer to https://code.visualstudio.com/docs/python/environments instead ?
created_at: 2025-04-01T13:51:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,70 @@
+# Create and run a Kedro project
+
+*P.S.: Steps 0 and 1 are for users who want to start a new Kedro project—if you already have an existing Kedro project, skip to Step 2: “Select the correct Python interpreter.”*
+
+## 1.1 Introducing `kedro new`
+
+To create a basic Kedro project with default setup, run this in your desired directory:
+
+```bash
+kedro new
+```
+
+### 1.1.1 Project tools
+
+Next, the CLI asks which tools you'd like to include in the project:
+
+```text
+Tools
+1) Lint: Basic linting with ruff
+2) Test: Basic testing with pytest
+3) Log: Additional, environment-specific logging options
+4) Docs: A Sphinx documentation setup
+5) Data Folder: A folder structure for data management
+6) PySpark: Configuration for working with PySpark
+7) Kedro-Viz: Kedro's native visualisation tool
+
+Which tools would you like to include in your project? [1-7/1,3/all/none]:
+ (none):
+```
+
+### 1.1.2 Quickstart example
+
+To create a spaceflights project called `spaceflights` with Kedro Viz features and example code:
+
+```text
+kedro new ⮐
+spaceflights ⮐
+7 ⮐
+yes ⮐
+```
+
+You can also enter this in a single line as follows:
+
+```bash
+kedro new --name=spaceflights --tools=viz --example=y
+```
+
+## 1.2 Run the new project
+
+After kedro new, run `cd <project-name>` and install dependencies with:
path: assets/markdown/new_project.md
user: login: astrojuanlu
body: By the time the user reaches this line they will face the "double venv" problem described in https://github.com/kedro-org/kedro/issues/681 

Can we simplify Steps 0 and 1 into "Do `uvx kedro new --name=spaceflights --example=y`, for more info check the docs"?
created_at: 2025-04-01T13:53:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,9 @@
+# Select the correct Python interpreter
path: assets/markdown/select_interpreter.md
user: login: astrojuanlu
body: Again, can we refer to the official Python on VS Code docs? https://code.visualstudio.com/docs/python/environments
created_at: 2025-04-01T13:55:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,9 @@
+# Select the correct Python interpreter
+
+### Select the interpreter that has Kedro and the necessary project dependencies installed.
+
+![select python interpreter](../select-python-interpreter.gif)
+
+### After selecting the interpreter, check for the orange warning icon below—if it appears, relaunch the terminal.
+
+![Verify the correct python interpreter](../vsc-orange-icon.gif)
path: assets/markdown/select_interpreter.md
user: login: astrojuanlu
body: What's the impact of not doing this? (Honest question)
created_at: 2025-04-01T13:55:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,16 @@
+# Set up or modify environment correctly
+
+To prevent conflicts between environments and ensure Kedro runs with the correct dependencies. Make sure you're using the correct virtual environment where Kedro is installed, and deactivate any others you don't need.
+
+
+E.g. Deactivate the `base` environment and ensure `.venv` is the one with Kedro installed.
+
+`(.venv) (base) <your-computer-name> <your-kedro-project> % conda deactivate`
+
+`(.venv) <your-computer-name> <your-kedro-project> %` 
+
+E.g. Deactivate the `base` environment and ensure `(your-kedro-environment)` is the one with Kedro installed.
+
+`(your-kedro-environment) (base) <your-computer-name> <your-kedro-project> % conda deactivate`
+
+`(your-kedro-environment) <your-computer-name> <your-kedro-project> %`
path: assets/markdown/verify_virtual_environment.md
user: login: astrojuanlu
body: If this is just for conda users that have an improperly configured environment... I would rather remove this section completely
created_at: 2025-04-01T13:55:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+# Set Custom Kedro Project Path
+
+### 4.1 Specify a custom path to your Kedro project root directory
+
+1. **Option 1: Using the Command Palette**:
+   - Press `Cmd` + `Shift` + `P` (on macOS) or `Ctrl` + `Shift` + `P` (on Windows/Linux)
+   - Type and select `Kedro: Set Project Path`
+   - Enter the absolute path to your Kedro project root directory
+   - The extension will validate if it's a valid Kedro project by checking for `pyproject.toml`
+
+2. **Option 2: Using Settings**:
+   - Open VS Code Settings (File > Preferences > Settings)
+   - Search for "Kedro Project Path"
+   - Enter the absolute path to your Kedro project root directory in the `kedro.kedroProjectPath` setting
+
+### 4.2 How to get the absolute path of your Kedro project
path: assets/markdown/set_project_path.md
user: login: astrojuanlu
body: This explanation is useful but also a bit verbose, I'm wondering if we could assume that users know this already and remove it
created_at: 2025-04-01T13:56:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,13 @@
+# Run Kedro-Viz and install dependencies
path: assets/markdown/run_kedro-Viz.md
user: login: astrojuanlu
body: Isn't it the other way around? (Install dependencies, then run Kedro Viz)
created_at: 2025-04-01T13:57:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,9 @@
+# Select the correct Python interpreter
+
+### Select the interpreter that has Kedro and the necessary project dependencies installed.
+
+![select python interpreter](../select-python-interpreter.gif)
+
+### After selecting the interpreter, check for the orange warning icon below—if it appears, relaunch the terminal.
+
+![Verify the correct python interpreter](../vsc-orange-icon.gif)
path: assets/markdown/select_interpreter.md
user: login: jitu5
body: @astrojuanlu After selecting the Python interpreter, if it is not applied correctly, VS Code will show a warning. Also, if you do not relaunch the terminal, the extension will not work properly.
created_at: 2025-04-01T18:13:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,38 @@
+# Set up and run Kedro
+*P.S.: If you’re starting a new Kedro project, follow Steps 0. If you already have an existing Kedro project, you can skip to Step 1: “Select the correct Python interpreter.”*
+
+## 0.1 Create a directory for working with your project and navigate to it
+
+```bash
+mkdir your-kedro-project && cd your-kedro-project
+```
+
+## 0.2 Create a virtual environment for your Kedro project
+
+Choose a virtual environment tool: `venv`, `conda`, or `uv`. Or use any another environment managers you prefer.
+
+**P.S.:** `venv` is already built-in with Python 3. Install `conda` or `uv` when necessary.
+
+Refer to https://code.visualstudio.com/docs/python/environments
+
+## 0.3 Install Kedro
+
+`pip install kedro` (PyPI)
+
+`conda install -c conda-forge kedro` (conda)
+
+`uv pip install kedro` (uv)
+
+## 0.4 Create and run Kedro project
+
+To create a basic Kedro project with default setup, run this in your desired directory:
+```bash
+uvx kedro new --name=spaceflights --example=y
path: assets/markdown/install.md
user: login: astrojuanlu
body: If the user has already done `pip/conda/uv pip install kedro`, they don't need `uvx kedro new`, right? Also, this will still create a second directory inside `your-kedro-project`
created_at: 2025-04-02T07:30:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,38 @@
+# Set up and run Kedro
+*P.S.: If you’re starting a new Kedro project, follow Steps 0. If you already have an existing Kedro project, you can skip to Step 1: “Select the correct Python interpreter.”*
+
+## 0.1 Create a directory for working with your project and navigate to it
+
+```bash
+mkdir your-kedro-project && cd your-kedro-project
+```
+
+## 0.2 Create a virtual environment for your Kedro project
+
+Choose a virtual environment tool: `venv`, `conda`, or `uv`. Or use any another environment managers you prefer.
+
+**P.S.:** `venv` is already built-in with Python 3. Install `conda` or `uv` when necessary.
+
+Refer to https://code.visualstudio.com/docs/python/environments
+
+## 0.3 Install Kedro
+
+`pip install kedro` (PyPI)
+
+`conda install -c conda-forge kedro` (conda)
+
+`uv pip install kedro` (uv)
+
+## 0.4 Create and run Kedro project
+
+To create a basic Kedro project with default setup, run this in your desired directory:
+```bash
+uvx kedro new --name=spaceflights --example=y
path: assets/markdown/install.md
user: login: jitu5
body: Thanks, I removed `uvx` and keeping consistency with the Kedro docs. 
created_at: 2025-04-02T11:58:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,5 @@
+# For more information, please check out our documentation below:
+
+- [Kedro documentation](https://docs.kedro.org/en/stable)
+- [Kedro-Viz documentation](https://docs.kedro.org/projects/kedro-viz/en/latest)
path: assets/markdown/learn_more.md
user: login: ravi-kumar-pilla
body: [Nit] Can we have this to /stable similar to kedro ? 
`https://docs.kedro.org/projects/kedro-viz/en/stable/`
created_at: 2025-04-02T19:27:08Z
author_association: NONE

PR comments:
user: login: jitu5
created_at: 2025-04-01T18:09:47Z
body:  @astrojuanlu 
> * Some parts of the text are rendered strangely

This part is removed all together 
> * The walkthrough didn't open automatically after I installed the `.vsix` file

If the extension is previously install then walkthrough will not open automatically even if yo uninstall and reinstall. I tired with other extension too. 
author_association: CONTRIBUTOR
user: login: jitu5
created_at: 2025-04-03T10:32:47Z
body: > The walkthrough seems very long to me. The last discussion that I recalled I thought we are going to focus on onboarding user with the extension only. The current walkthrough have a lot of documentation content inside, i.e. choosing tool, choosing a virtual environment, relaunch terminal, launching `kedro viz` command etc etc which is not related to the extension.

@noklam The scope of this walkthrough is primarily focused on getting started with Kedro and setting up the extension. Therefore, describing the extension's features is outside the scope of this guide. Initially, the steps and content were quite lengthy, but we have now reduced the number of steps from six to four and significantly streamlined the content.
author_association: CONTRIBUTOR
user: login: noklam
created_at: 2025-04-03T10:43:46Z
body: Thanks @jitu5, I like the simplified version better
author_association: CONTRIBUTOR