[Ready] Docs changes to remove pandas-iris and update kedro new flow in onboarding docs

docs/source/deployment/airflow_astronomer.md

@@ -15,7 +15,7 @@ The following tutorial uses a different approach and shows how to deploy a Kedro
 
 [Astronomer](https://docs.astronomer.io/astro/install-cli) is a managed Airflow platform which allows users to spin up and run an Airflow cluster easily in production. Additionally, it also provides a set of tools to help users get started with Airflow locally in the easiest way possible.
 
-The tutorial discusses how to run the [example Iris classification pipeline](../get_started/new_project.md#create-a-new-project-containing-example-code) on a local Airflow cluster with Astronomer. You may also consider using our [`astro-airflow-iris` starter](https://github.com/kedro-org/kedro-starters/tree/main/astro-airflow-iris) which provides a template containing the boilerplate code that the tutorial describes:
+The tutorial discusses how to run the example Iris classification pipeline on a local Airflow cluster with Astronomer. You may also consider using our [`astro-airflow-iris` starter](https://github.com/kedro-org/kedro-starters/tree/main/astro-airflow-iris) which provides a template containing the boilerplate code that the tutorial describes:
 
 ```shell
 kedro new --starter=astro-airflow-iris
@@ -44,10 +44,10 @@ To follow this tutorial, ensure you have the following:
     astro dev init
     ```
 
-2. Create a new Kedro project using the `pandas-iris` starter. You can use the default value in the project creation process:
+2. Create a new Kedro project using the `astro-airflow-iris` starter. You can use the default value in the project creation process:
 
     ```shell
-    kedro new --starter=pandas-iris
+    kedro new --starter=astro-airflow-iris
     ```
 
 3. Copy all files and directories under `new-kedro-project`, which was the default project name created in step 2, to the root directory so Kedro and Astro CLI share the same project root:

docs/source/deployment/distributed.md

@@ -40,4 +40,4 @@
 
 ## 4. (Optional) Create starters
 
-This is an optional step, but it may speed up your work in the long term. If you find yourself having to deploy in a similar environment or to a similar platform fairly often, you may want to [build your own Kedro starter](../kedro_project_setup/starters.md). That way you will be able to re-use any deployment scripts written as part of step 2.
+You may opt to [build your own Kedro starter](../starters/starters.md) if you regularly have to deploy in a similar environment or to a similar platform. The starter enables you to re-use any deployment scripts written as part of step 2.

docs/source/extend_kedro/architecture_overview.md

@@ -37,7 +37,7 @@ Kedro framework serves as the interface between a Kedro project and Kedro librar
 
 ## Kedro starter
 
-You can use a [Kedro starter](../kedro_project_setup/starters.md) to generate a Kedro project that contains boilerplate code. We maintain a set of [official starters](https://github.com/kedro-org/kedro-starters/) but you can also use a custom starter of your choice.
+You can use a [Kedro starter](../starters/starters.md) to generate a Kedro project that contains boilerplate code. We maintain a set of [official starters](https://github.com/kedro-org/kedro-starters/) but you can also use a custom starter of your choice.
 
 ## Kedro library
 

docs/source/extend_kedro/common_use_cases.md

@@ -39,4 +39,4 @@ Your plugin's implementation can take advantage of other extension mechanisms su
 
 ## Use Case 4: How to customise the initial boilerplate of your project
 
-Sometimes you might want to tailor the starting boilerplate of a Kedro project to your specific needs. For example, your organisation might have a standard CI script that you want to include in every new Kedro project. To this end, see the [guide for creating Kedro starters](../kedro_project_setup/starters.md#how-to-create-a-kedro-starter).
+Sometimes you might want to tailor the starting boilerplate of a Kedro project to your specific needs. For example, your organisation might have a standard CI script that you want to include in every new Kedro project. To this end, see the [guide for creating Kedro starters](../starters/create_a_starter.md).

docs/source/extend_kedro/index.md

@@ -6,4 +6,5 @@
 common_use_cases
 plugins
 architecture_overview
+../starters/create_a_starter
 ```

docs/source/extend_kedro/plugins.md

@@ -42,49 +42,6 @@ Once the plugin is installed, you can run it as follows:
 kedro to_json
 ```
 
-## Extend starter aliases
-It is possible to extend the list of starter aliases built into Kedro. This means that a [custom Kedro starter](../kedro_project_setup/starters.md#how-to-create-a-kedro-starter) can be used directly through the `starter` argument in `kedro new` rather than needing to explicitly provide the `template` and `directory` arguments. A custom starter alias behaves in the same way as an official Kedro starter alias and is also picked up by `kedro starter list`.
-
-You need to extend the starters by providing a list of  `KedroStarterSpec`, in this example it is defined in a file called `plugin.py`.
-
-Example for a non-git repository starter:
-```python
-# plugin.py
-starters = [
-    KedroStarterSpec(
-        alias="test_plugin_starter",
-        template_path="your_local_directory/starter_folder",
-    )
-]
-```
-
-Example for a git repository starter:
-```python
-# plugin.py
-starters = [
-    KedroStarterSpec(
-        alias="test_plugin_starter",
-        template_path="https://github.com/kedro-org/kedro-starters/",
-        directory="spaceflights-pandas",
-    )
-]
-```
-
-The `directory` argument is optional and should be used when you have multiple templates in one repository as for the [official kedro-starters](https://github.com/kedro-org/kedro-starters). If you only have one template, your top-level directory will be treated as the template. For an example, see the [spaceflights-pandas starter](https://github.com/kedro-org/kedro-starters/tree/main/spaceflights-pandas).
-
-In your `pyproject.toml`, you need to register the specifications to `kedro.starters`:
-
-```toml
-[project.entry-points."kedro.starters"]
-starter = "plugin:starters"
-```
-
-After that you can use this starter with `kedro new --starter=test_plugin_starter`.
-
-```{note}
-If your starter lives on a git repository, by default Kedro attempts to use a tag or branch labelled with your version of Kedro, e.g. `0.18.12`. This means that you can host different versions of your starter template on the same repository, and the correct one will automatically be used. If you do not wish to follow this structure, you should override it with the `checkout` flag, e.g. `kedro new --starter=test_plugin_starter --checkout=main`.
-```
-
 ## Working with `click`
 
 Commands must be provided as [`click` `Groups`](https://click.palletsprojects.com/en/7.x/api/#click.Group)

docs/source/faq/faq.md

@@ -13,7 +13,7 @@
 
 ## Kedro project development
 
-* [How do I write my own Kedro starter projects](../kedro_project_setup/starters.md#how-to-create-a-kedro-starter)?
+* [How do I write my own Kedro starter projects](../starters/create_a_starter.md)?
 
 ## Configuration
 
@@ -67,3 +67,30 @@
 | Models         | Stored, serialised pre-trained machine learning models                                                                                                                                                                                                                                                                                                            |
 | Model output   | Analytics specific data model(s) containing the results generated by the model based on the `model input` data                                                                                                                                                                                                                                                    |
 | Reporting      | Reporting data model(s) that are used to combine a set of `primary`, `feature`, `model input` and `model output` data used to drive the dashboard and the views constructed. It encapsulates and removes the need to define any blending or joining of data, improve performance and replacement of presentation layer without having to redefine the data models |
+
+## How can I check the version of Kedro installed?
+To check the version installed, type `kedro -V` in your terminal window.
+
+
+## How do I install a development version of Kedro?
+
+This section explains how to try out a development version of Kedro direct from the [Kedro GitHub repository](https://github.com/kedro-org/kedro).
+
+```{important}
+The development version of Kedro is not guaranteed to be bug-free and/or compatible with any of the [stable versions](https://pypi.org/project/kedro/#history). We do not recommend that you use a development version of Kedro in any production systems. Please install and use with caution.
+```
+
+To try out latest, unreleased functionality from the `develop` branch of the Kedro GitHub repository, run the following installation command:
+
+```bash
+pip install git+https://github.com/kedro-org/kedro.git@develop
+```
+
+This will install Kedro from the `develop` branch of the GitHub repository, which is always the most up to date. This command will install Kedro from source, unlike `pip install kedro` which installs Kedro from PyPI.
+
+If you want to roll back to a stable version of Kedro, execute the following in your environment:
+
+```bash
+pip uninstall kedro -y
+pip install kedro
+```

docs/source/get_started/install.md

@@ -162,28 +162,6 @@ When migrating an existing project to a newer Kedro version, make sure you also
 * For projects generated with versions of Kedro > 0.17.0, you'll do this in the `pyproject.toml` file from the project root directory.
 * If your project was generated with a version of Kedro <0.17.0, you will instead need to update the `ProjectContext`, which is found in `src/<package_name>/run.py`.
 
-## How to install a development version of Kedro
-
-This section explains how to try out a development version of Kedro direct from the [Kedro GitHub repository](https://github.com/kedro-org/kedro).
-
-```{important}
-The development version of Kedro is not guaranteed to be bug-free and/or compatible with any of the [stable versions](https://pypi.org/project/kedro/#history). We do not recommend that you use a development version of Kedro in any production systems. Please install and use with caution.
-```
-
-To try out latest, unreleased functionality from the `develop` branch of the Kedro GitHub repository, run the following installation command:
-
-```bash
-pip install git+https://github.com/kedro-org/kedro.git@develop
-```
-
-This will install Kedro from the `develop` branch of the GitHub repository, which is always the most up to date. This command will install Kedro from source, unlike `pip install kedro` which installs Kedro from PyPI.
-
-If you want to roll back to a stable version of Kedro, execute the following in your environment:
-
-```bash
-pip uninstall kedro -y
-pip install kedro
-```
 
 ## Summary