It is all very well stating that Ansible playbooks should be cloned from a version control system and cloned to the systems from which they are to be run (be that from the command line or AWX), but how do you actually organize these effectively so that you can find your code when you need it?
A clue comes to us from the user interface of the AWX tool, which refers to each version control repository you might reference as Project. As you build up your automation processes and solution, you could end up with many playbooks, possibly into the hundreds, depending on the size of your enterprise.
You can, of course, store all of these within the same repository. The ansible-examples repository ...
