Onboarding improvement suggestions

Proposed changes / additions

Sharing a few thoughts on how we could improve our onboarding process.

Expand GDK Geo setup tips

We could maybe enhance the GDK setup by adding tips related to Geo:

• Link to GDK Geo troubleshooting tips.
• After setup, run gitlab-rake geo:status locally to verify your Geo GDK is working correctly
• Review common Geo troubleshooting docs: Common Geo Troubleshooting.

Add an overview video / short explanation

Our current content consists of long-form deep dives. We could maybe:

• Create or find a concise (< 20 min) "What is Geo and why does it matter?" overview video/doc for new team members.

This would cover: architecture at a high level, primary/secondary topology, what gets replicated, how DR works, and how Cells/Org Migration relates to Geo — without going deep into any one area.

We could also link @nsilva5's video generated by AI showing a good overview of Geo.

Add workflow / process explanation

Could be nice to have a general explanation of the team's workflows, labels, issues, and processes:

• Document or link to an explanation of the Geo team workflow: how issues flow from backlog → refinement → scheduling → development → review → release.
• Explain the key labels used: group::geo, Category:Geo, Geo::Replication, Geo::Disaster Recovery, workflow labels, priority/severity, weight, etc.
• Explain the milestone/planning cadence and how new team members can participate.