Patrice Chalin

FYI, from https://github.com/etcd-io/website/pull/490#pullrequestreview-761287141: > ... > The [Demo](https://etcd.io/docs/v3.5/demo/) page has a collection of little "how-to's", including one for [authentication](https://etcd.io/docs/v3.5/demo/#auth). > > Maybe what we need to do is to convert...

To be clear, I think that some of the entries don't qualify (have enough material) to warrant being referred to as a tutorial, though some might. On the other hand...

There's some prose from a Caution side-note that needs adjustment. It was introduced in #4246, but can be fixed in #4322. Here's the context: - [ ] https://github.com/open-telemetry/opentelemetry.io/pull/4246/files#r1592148676

@open-telemetry/docs-approvers @austinlparker - we run into the topic of visibility / discoverability. I'd love to see these forward-looking pages hosted on the website, possibly under https://opentelemetry.io/community: > 

~Oh wait, the `https` version of the link isn't working? I thought it was. Let me double check. Putting this in draft in the meantime.~ Fixed. Switched to using canonical...

Thanks for this PR @cjyabraham. FYI, this is still on the radar. I'll add it as a candidate to release 0.11.0 (#1944). Docsy 0.10.0 is just hot off the press!...

Escalated to upstream, since I'd like to see this behavior across CNCF websites: https://github.com/google/docsy/issues/780

Hi @leonardpahlke - no, this is far from complete. What has been accomplished is to [Reintroduce Docsy as a submodule #160](https://github.com/cncf/tag-env-sustainability/pull/160), which is an essential first step, but Docsy has...

Another thought: we could reuse the Vitess.io GA4 site tag, since the main website is being migrated: - https://github.com/vitessio/website/issues/1098 /cc @nate-double-u

The recommended GA4 account structure differs from that for UA. For Vitess, it would imply that we reuse the same web data stream. But no worries, I'll setup reports that...