docs: added a page about CLI telemetry

[samalba]

Fixes #832

[netlify]

✅ Deploy Preview for devel-docs-dagger-io ready!

Name	Link
🔨 Latest commit	a27b7b2
🔍 Latest deploy log	https://app.netlify.com/sites/devel-docs-dagger-io/deploys/6243792e96ef4e000827fe19
😎 Deploy Preview	https://deploy-preview-1929--devel-docs-dagger-io.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[aluzzardi]

LGTM

For future reference, commits should say "add" rather than "added":

Use the imperative mood in the subject line: "If applied, this commit will [your subject line here]"

https://github.com/dagger/.github/blob/main/CONTRIBUTING.md#commit-messages

[shykes]

LGTM. Ideally we should move it outside of "core concepts", but there is no other good category at the moment, so we can worry about that later. Perhaps integrate it into a bigger FAQ?

[gerhard]

Do you think that this would fit under Advanced Concepts?

This is what I was imagining: #1804 (comment)

[shykes]

Do you think that this would fit under Advanced Concepts?

This is what I was imagining: #1804 (comment)

"advanced concepts" does't feel right in this case, it's not really something to learn and master, more like an (important) detail of Dagger's behavior, that is important to know as an admin / operator.

--> Typing this, I think it would fit great in a "operator's manual" category. We already have the "custom buildkit" article waiting to be moved to 0.2, so we would have:

• Operator's manual
  • Custom buildkit configuration
  • CLI telemetry

[samalba]

I agree it should move another category at some point. I just did not want to create a new one just for that.

[gerhard]

--> Typing this, I think it would fit great in a "operator's manual" category. We already have the "custom buildkit" article waiting to be moved to 0.2, so we would have:

• Operator's manual

  • Custom buildkit configuration
  • CLI telemetry

"Operator" introduces the dimension of personas and it doesn't fit with the existing categorisation.

The initial idea was:

1. Get started
2. Understand the core of Dagger
3. Learn from real-world use-cases

The next iteration on that would be:

1. Get started
2. Understand the core of Dagger
3. Dive into more advanced Dagger topics
4. Learn from real-world use-cases

Introducing operators, app devs and package devs sounds like something that we may want to do after the second iteration as it's a bigger step. It is a good idea and I know that this will become necessary as we add more content, but I want to keep it consistent and simple for now.

The other option for now might be to not put this page into a category, just like we do with the Migrate from Dagger 0.1 page. This page could fit after Use Cases and before Dagger 0.1, which will be last.

[shykes]

It's not about persona, but about having a reference manual. You need a place to reference various things to know, that don't fit into a neat linear narrative. There used to be a "knowledge base" category but that got removed. Call it whatever you want but that place needs to exist.