With some 80% of the CLI being deprecated, is the basic idea that those departing functions will be replaced by plugins?? I realize this feedback is probably too late, but frankly a big part of the utility of kedro is to provide "training wheels" to data scientists in the form of a well documented CLI. Just to throw an idea out there: maybe instead of a hard deprecation, those commands could remain as placeholders to be explicitly overridden by plugins. In other words they could define the common entry points for most plugins instead of each plugin providing its own.

So when we investigated via telemetry this we found that a very small subset of users were actually using the features directly You can read up on this in issues like this - the short answer is that we want to replace much of this with documentation and be a little less restrictive with the ‘right’ way of doing things. A good example of this is that Sphinx was the best option for docs 7 years ago when we started this journey - but today we’d back a newer horse like Mkdocs or Jupyterbook The idea about keeping these as installable CLI plugins is a good idea though - @Yetunde what are your thoughts here?

I tend to agree with this @Andrew Stewart - see my suggestion here for something very much along the lines you’re suggesting: https://github.com/kedro-org/kedro/issues/1622. Please do feel free to add any comments there also 🙂

Link to my thoughts, fairly aligned with @Andrew Stewart: https://github.com/kedro-org/kedro/issues/1293#issuecomment-1156339787 So far, I think we've said that we maintain a template that follows the same linting rules, etc. as before (and enforce that via CI), but we don't provide the commands--maybe a community-driven plugin takes it's place.