Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
WIP: DOCS - shorten Scenario Guides, incorporate VMware Guide #53569
I really don't like the name "Integration Guides", it doesn't cover what it is about. We are not really integrating VMware with Infoblox (or Ansible with ACI), so I doubt people will understand what is behind this menu title. We don't integrate, we manage this infrastructure. To me "Integration Guides" sounds more like something developers would be looking at.
So I think "Scenario Guides" is a better fit, or maybe "Technology Guides". Puppet calls this Managed technology. SaltStack has its different guides structured per category in the main index (i.e. Cloud, Network Automation)
Scenario Guides, User Guides, Technology Guides doesn't set people on the wrong foot like Integration Guides does. I would think that section is about developing plugins/inventories/modules to integrate some technology into Ansible. And not about managing infrastructure.
Looking at the list, probably both VMware and Networking belong to these "Technology guides". Networking calls it the "Network Automation Guide" so why not call everything "Automation Guides" ? ACI Automation Guide, VMware Automation Guide, Infoblox Automation Guide, etc...