# The Ansible ecosystem docsite is here **URL:** \ **Category:** News & Announcements\ **Tags:** ecosystem, ansible-navigator, documentation\ **Created:** [October 19, 2023, 10:52am UTC](https://forum.ansible.com/t/the-ansible-ecosystem-docsite-is-here/1799 "2023-10-19T10:52:06Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![oranod](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oranod/32/1434_2.png) [@oranod](https://forum.ansible.com/u/oranod)\ **Post date:** [October 25, 2023, 2:27pm UTC](https://forum.ansible.com/t/the-ansible-ecosystem-docsite-is-here/1799/8 "2023-10-25T14:27:28Z")
@rfc2549 I hear you. We (community team) talked about this a few days ago. It’s still a little strange because I feel like this is something that really _should_ be simple. What are those criteria for projects need to meet - or as @gwmngilfen says - what are the table stakes? It’s probably going to take a lot of discussion and some tricky navigation to get us there but - rest assured - there is no gatekeeping of the ecosystem by Red Hat. And I think there are a lot of lessons learned from things like collection inclusion guidelines that we can reference for the ecosystem. Another thing we can draw from is what @samccann captured for the Awesome Ansible list: [Setting guidelines for awesome ansible's curated list of interesting tools · Issue #242 · ansible-community/community-topics · GitHub](https://github.com/ansible-community/community-topics/issues/242) That’s a pretty sweet list of guidelines already imho --- _[View the full topic](https://forum.ansible.com/t/the-ansible-ecosystem-docsite-is-here/1799)._