Revise documentation table of contents

[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

I created this PR because I realised that the "Kedro projects" section of the ToC has been massively improved (still got nodes & pipelines to do, but the data/config sections have had substantial revision). The only section that hasn't been touched, and is a bit of an anomaly in that section, is the "Kedro project setup" and it's a bit of a mixed bag of content on starters, dependencies, settings and lifecycle management.

Note: I don't actually think that many people use the ToC. We do because we're very familiar with the contents of the docs so we use it to navigate around. I suspect most people look at Get Started or they use search to find what they're looking for. So although this may seem like a seismic shift in terms of layout (for us) it won't be a big deal to most. If I understood how to use Heap I'd get some data to justify this.

Development notes

I've moved the "Kedro project setup" into the "Advanced" section and retitled it as just "Project setup".

You can see the built docs here

The content is still on the list for revision but it doesn't receive significant user attention so isn't the highest priority right now and Nodes & Pipelines will be fixed up first.

The move does NOT impact any links because it's not moved in URL terms, just where it's located in the documentation set (it's shifted down a bit).

ORIGINAL TOC

NEW TOC

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

[merelcht]

That makes a lot of sense! 👍

[astrojuanlu]

One step towards perfection 👍🏽 I agree the "Project setup" page is a bit of a mixed bag, time will come to improve it