Awesome Ansible list: How to make it more presentable/attractive to contribute to?

Project Discussions
, , , , , , ,
1

Hi there,

On docs.ansible.com under the Ansible ecosystem page we refer to:

  • Ansible ecosystem page: lists key projects like ansible-core, collecitons, Navigator, AWX, etc.
  • Awesome Ansible list: A collaborative curated list of awesome Ansible resources, tools, roles, tutorials and other related content. Thanks to all the work the maintainers have done so far!

If you have a project that somehow relates to Ansible and you want it to be listed in some central place for community awareness, Awesome Ansible for the time being is the way to go: just open a PR against the README.

Yes, Awesome Ansible is just a README. Maybe I see READMEs too often, so it doesn’t look very impressive to me…

I’ve been wondering if we could make the list look more presentable for users and attractive to contribute to.

First, I was thinking about building a docsite from the README and publishing it on ReadTheDocs, see the example.
Then, not to increase fragmentation, @oranod suggested publishing it under docs.ansible.com/ecosystem, which sounds even better to me.

  • What the community think about this?
  • If it’s OK:
    • Should we build it from the README or instead move it to somewhere else and shut down the awesome-ansible repo entirely?
  • If it’s not OK, please suggest your options

Any other thoughts on the list will be much appreciated.
If you want to help with anything we’ll agree on during the discussion, just raise your hand.

Looking forward to your feedback,
Thanks!

1 Like
2

@Andersson007 Thanks for starting the discussion

And massive thanks to @KeyboardInterrupt who created the Awesome Ansible list to start with

@rndmh3ro I know you’ve helped with Awesome Ansible, so would welcome your ideas on this

1 Like
3

I personally have no preference whether it’s the README of a repository (like the existing one), or part of another repository (docsite, ansible-documentation, …); and whether you generally look at it by going to the repo, or going to some other website.

The fragmentation argument sounds good though, so if I’m currently forced to have a preference, I would go for https://docs.ansible.com/ecosystem.html :wink:

4

My preference:

Continue using a README in the “awesome-list” format, so:

  • it’s easy to edit for everyone
  • it still exists in the “awesome”-universe, thus having a wider reach
  • people who like the look of it, can continue ising the README

Then, publish it in the Ansible ecosystem page. This:

  • gives it additional reach
  • brings a nice-to-look-at overview
  • it is “official”, as it lives in the ansible-homepage
  • let’s all documentation be under one roof
1 Like
5

That’s a really good point ,thanks for highlighting that @rndmh3ro

1 Like
6

FYI, the awesome list is already the first link on the ecosystem page: Ansible Ecosystem | Ansible Documentation

image
image654Ă—461 31.9 KB

1 Like
7

Thanks for the feedback, folks! As there’s no strong support for building a separate docs.ansible.com page from the README, let’s keep it as-is.

1 Like