# Mkdocs for Docs

**URL:** <https://forum.ansible.com/t/mkdocs-for-docs/7283>\
**Category:** Get Help\
**Tags:** documentation\
**Created:** [July 15, 2024, 5:09pm UTC](https://forum.ansible.com/t/mkdocs-for-docs/7283 "2024-07-15T17:09:32Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [July 18, 2024, 4:24pm UTC](https://forum.ansible.com/t/mkdocs-for-docs/7283/18 "2024-07-18T16:24:19Z")

</div>

> [@samccann](#):
>
> My nickel is leave it to Galaxy if you do not have any extra guides (as in you have plugin docs and a readme). Galaxy will likely outperform your individual collection docsite on search results.

Right now be warned that Galaxy does not render role argument specs (not sure whether there’s an issue tracking that, since galaxy\_ng does not use GitHub for issues), and it does not render documentation of plugins that use docs fragments from other collections ([Galaxy importer: collection dependency handling](http://forum.ansible.com/t/3496), no idea whether there’s anything in galaxy\_ng’s issue tracker for that either).

---

_[View the full topic](https://forum.ansible.com/t/mkdocs-for-docs/7283)._