Improve Geo subcategories in documentation
Geo supports two functional categories:
- Replication: https://docs.gitlab.com/ee/administration/geo/replication/index.html
- Disaster Recovery: https://docs.gitlab.com/ee/administration/geo/disaster_recovery/index.html
In the documentation, one first needs to assume the role of "administrator" by going to https://docs.gitlab.com/ee/administration/.
One is then presented with:
- "Geo", for replication.
- "Disaster Recovery" for disaster recovery.
Anecdotally, when one thinks "Geo", one probably does think replication. However, Geo is fundamental to both.
Question: Do we want to position Geo as the name for the provider of replication, disaster recovery, and future functional subcategories? Or, do we want to downplay the Geo name, and treat it merely as the means to those ends.
Put another way, if I'm using the GitLab Docs to discover features supported by Geo, do I either:
- Find all the Geo-supported functionality in a "Geo Docs"-type area, called out as such in bright lights.
- Find GitLab features separately, and note that as I read about them, they mention as minor detail that Geo is required for them.
In the short term, it becomes important for how we expect folks to find Replication and Disaster Recovery in our Global Navigation. Which of the following paths through the menus is most appropriate:
Path A, strong Geo branding:
- Administrator > Geo > Replication
- Administrator > Geo > Disaster Recovery
- Administrator > Geo > Future features
Path B, weak Geo branding:
- Administrator > Replication
- Administrator > Disaster Recovery
- Administrator > Future features
In the longer term, it affects how we treat the term "Geo". Right now:
- We call the replication feature "Geo Replication" and call "Geo" that which is replication in GitLab.
- In disaster recovery, we make the assumption that you are using Geo for replication, and give steps on how to use it for disaster recovery.
Do we plan for Geo Replication to always take top billing, and for it to unlock other features? Or perhaps disaster recovery could sit alongside replication as equal features that happen to share technology called Geo?