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

[stichbury]

NOTE: Kedro datasets are moving from kedro.extras.datasets to a separate kedro-datasets package in
kedro-plugins repository. Any changes to the dataset implementations
should be done by opening a pull request in that repository.

Description

To address #3048 by updating the new project creation flow.

Ready for first review by @amandakys.

PREVIEW CODE IS BUILT HERE

Development notes

I have updated the new project text but have also:

• split the starters documentation into two sections for usage and starter creation, both are tidied up for language and content
• created a new folder for docs about starters and what I've currently titled "new project tools"
• revised text throughout the docs that refers to pandas-iris

Still to come

• Add basic summary of example options to new project doc page (once I've seen the options in Add tools documentation page #3331)
• Update for the specification of tools and example selections in config file in the new project doc page (unless I omit this option entirely - TBD in Add tools documentation page #3331)

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

• Read the contributing guidelines
• Signed off each commit with a Developer Certificate of Origin (DCO)
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added a description of this change in the RELEASE.md file
• Added tests to cover my changes
• Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

[stichbury]

Some notes on what we need to do to complete this PR:

• Update the get started section to introduce the new project creation flow that uses the different options / remove Iris starter etc. @stichbury to do this
• Add a page devoted to the different options for the new project creation flow. I've called it "Addons" right now but that needs to be changed (page name, titles etc). We seem to have settled on "Tools" although I'm not massively confident in how to use the terminology so hope @AhdraMeraliQB you can write the page and see how many adjustments are needed. It's coming in this PR Add tools documentation page #3331
• Revision to the page about Kedro starters (for usage) @AhdraMeraliQB can you take this too please?
• Introduction of a new page (in the "Extend Kedro" section) which takes the old content about how to create a starter and updates it as needed. @stichbury to do the first cut of this.
• Review the rest of the docs where kedro new is discussed and adjust (particularly to remove the Iris starter and add tools options). See Revise documentation that uses the iris starter #3160 for a list, which I've worked through except for one query about generators (requested input from @noklam and @merelcht)

[AhdraMeraliQB]

Add-ons are also configurable here - will double check what happens when they are omitted

Update: The process fails if they are omitted, consistent with the other attributes

[stichbury]

Thanks. I'll need some insight on how to include these so will await the changes on your branch for guidance.

[astrojuanlu]

I gave a look and looks okay! I see there are some parts yet to be written still

[stichbury]

This is ready for final review @astrojuanlu and @merelcht @amandakys

The sections marked as "to do" will be covered by @AhdraMeraliQB and @SajidAlamQB in a separate PR (branched from this branch) here #3331

[merelcht]

Looks great! I've left some minor comments.

[astrojuanlu]

Gave this a more thorough review. The content is fantastic - I have a few reservations about the overall structure of the starters folder. I made some specific suggestions in the comments and opened some questions.

[astrojuanlu]

It's weird that /starters/ is for "new project tools", /starters/starters.html is for "starters", and /starters/new_project_tools.html is for "configure a new project" (looking at the H1 of each page).

[astrojuanlu]

And speaking specifically about this title, "new project tools" could be read as "tools for new projects" or "new thing called project tools", which was confusing to me at first. I bet we don't want to use the second meaning, given that the "new" tools will stop being new at some point...

[stichbury]

I think we should fix the naming in the upcoming PR from @AhdraMeraliQB which explicitly writes the content. I can't really guess at what to call the page right now, so that's a placeholder.

You're correct about the /starters being an odd place for those tools but it's awkward to name the folder. Maybe "/project_creation. Again, I'm pushing that to #3331 rather than resolving here.

[amandakys]

I looked at the New Project Tools page and the Create a new Kedro project pages.

I like the way the two pages link together, the Create a New Kedro Project page is now much clearer and flows well.

On the New Project Tools page, would it be worth highlighting the kedro new --addons flag since we are listing out flags to use with the kedro new command? Or are we documenting that elsewhere?

On the Create a New Kedro Project. Would it worth having a section called Project Name? That way the in page navigation will reflect the structure of the CLI. Otherwise, we could signpost that there are 3 steps to the kedro new command at the top and list the steps before we go into more detail?