# Ansible documentation goals for rest of 2023

**URL:** <https://forum.ansible.com/t/ansible-documentation-goals-for-rest-of-2023/1575>\
**Category:** Project Discussions\
**Tags:** documentation\
**Created:** [October 9, 2023, 7:11pm UTC](https://forum.ansible.com/t/ansible-documentation-goals-for-rest-of-2023/1575 "2023-10-09T19:11:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [October 9, 2023, 7:11pm UTC](https://forum.ansible.com/t/ansible-documentation-goals-for-rest-of-2023/1575/1 "2023-10-09T19:11:57Z")

</div>

Since we have a bit more than two months left, I thought it would be a good time to see what the community thinks are priorities are for wrapping up this calendar year with regard to Ansible documentation.

As a reminder, we have a few big things we’re planning on completing:

- Read the Docs as the main platform for ecosystem project docs (core is the final one in the works)
- Ecosystem cross-project docs repo (to hold things like the EE getting started that crosses more than one project)
- [tackling the docs issue backlog](https://github.com/ansible/ansible-documentation/issues)
- modernizing the docs build (aka nox vs makefile)
- ensure all rst files are part of CI tests, not just the core subset for example (rstcheck likely does but not docs-build)

Is there something else y’all have in mind that we should focus on in the next couple of months?