👋 Hey everyone! We’d love your help validating a new guide on node grouping methods in Kedro: pipelines, tags, and namespaces. 🔍 What we’re asking: Please read through the node grouping guide, then share your feedback on: • What’s clear vs. confusing? • Any pain points or inconsistencies? • How easy is it to understand the differences between pipelines, tags, and namespaces? 🧪 Think of it like a quick "bash test" — try out each method and let us know where things don’t make sense. 💬 This is a self-serve task — no supervision needed. Just reply directly in this thread with your thoughts and findings! If you're interested in a follow-up session to test out namespace-based grouping, give this message a 👍 and we’ll reach out soon. Thanks in advance for your insights — they’re super valuable in shaping the Kedro experience!

Not to use when

• The tagged nodes have strong dependencies, which might cause execution failures.

I think this is saying "The tagged nodes have `MemoryDataset`s as inputs. These inputs will not be created when running only the tagged nodes."

• Tags are not hierarchical, so tracking groups of nodes can become difficult.

Is this saying "Tags do not necessarily compose a DAG"?

Hey @Chris Schopp, thanks for sharing your feedback! > I think this is saying "The tagged nodes have `MemoryDataset`s as inputs. These inputs will not be created when running only the tagged nodes. You're right—that's one example of what could happen. > Tags are not hierarchical, so tracking groups of nodes can become difficult. I think the key point here is not about the DAG itself, but rather how tags are used to group nodes. Two main challenges we’ve identified are: • Tags are not inherently hierarchical like pipelines or namespaces. If multiple developers assign tags arbitrarily, it can be difficult to track which nodes belong together. • *Tags do not enforce structure*—they are just labels. A new developer joining the project might not immediately understand which nodes are critical for different deployments. If we explain a bit more about these two points as above, would it make more sense in the guide to you?

I think that would help. I've always worked solo on Kedro projects, so the "If multiple developers..." part was eye-opening. The second point is clear, too.

We'll make sure to incorporate your feedback in our second iteration @Chris Schopp thanks for taking the time to review this version