Jorge P

It's a pretty long conversation in that link. I think we want readable and actionable docs issues for planning, etc. Imagine someone (maybe even yourself) opens this in a year...

Out of curiosity, what makes this p1? Perhaps there are there lots of support cases that could be avoided by or redirected to this? Thanks

Would this be an update to the [Get Started](https://cml.dev/doc/start), or are we thinking about another longer tutorial? And in the latter case, should it be blog posts instead?

Or I guess it could be 2 top-level docs i.e. an update to [CML with DVC](https://cml.dev/doc/start) and a new [CML with Tensorboard] one.

> ... already auto-suffixed to all pages Just keep in mind that in terms of SEO, Google sometimes decides to make up it's own page title e.g. > When they're...

> I'd call this a `p1` instead of an `epic`, at least from the description and within my understanding of what those labels mean.

Where are you seeing that figure, @jendefig ? `checkout` only moves you to some branch, so to speak, to act on it. It doesn't cause any change to the graph.

Ah right (weird, the hashes seemed to change, anyhow...). It's just how this particular graph is rendered (corresponds to the 2nd merge). There are no commits in that line i.e....

Just a couple relatively off-topic notes wrt terminology (sorry, it may be annoying but I think we also want to make sure we're talking the same language): - I call...

> high-level: scenarios/problems That's what I mean by use case. Happy to change our official terminology if we can get more people to agree. > mid-level: use cases There's a...