It's worth taking into account that Gerrit itself has fairly thorough documentation (e.g., see https://gerrit-review.googlesource.com/Documentation/index.html).

For example, https://gerrit-review.googlesource.com/Documentation/user-attention-set.html explains the "Attention Set" feature in depth, and https://gerrit-review.googlesource.com/Documentation/user-review-ui.html goes over all the UI elements that can be useful during code review.

The https://go.dev/doc/contribute#sending_a_change_gerrit section currently explains step by step what it takes to send a change via Gerrit, but it can't cover everything Gerrit offers without also becoming as large as the links I shared above. Gerrit itself is improving and sometimes gets new features (e.g., Attention Set was only added in recent years).

The point I want to make with this is that it could work well to take advantage of Gerrit's own existing documentation in some helpful way, and avoid trying to replace it.

As an easy first step, we could probably just add those links to the page.