Open stichbury opened 11 months ago
*
imports..run
them, how to define their inputs and so on. Most Kedro users will never do this, and only interact with the Framework way of doing things. I think we should consider whether we want to split the page somehow: Framework usage on top, Python API at the bottom. This applies to many other parts of our docs.pipeline
convenience function is imported from.pipeline
) are with respect to the corresponding class initialiser (uppercase Pipeline
) would be nice.I think this may be a comment to https://github.com/kedro-org/kedro/issues/3200 rather than here?
Child of https://github.com/kedro-org/kedro/issues/2799 This is a parent itself and will cover all the changes necessary to popular pages in the "Extend Kedro" section (namely plugins). Won't be addressed until 0.19.0 and is relatively low priority compared to https://github.com/kedro-org/kedro/issues/3200 but higher than #3201.
Parent ticket because there are already a bunch existing for plugins docs improvements, so this is the umbrella to make sure they're all addressed as part of the improvement.