---
# System prepended metadata

title: docs.ansible.com
tags: [Documentation]

---

# docs.ansible.com

###### tags: `Documentation`

## past and present: Oct 4, 2022

Context: community of communities, Ansible ecosystem, solid community contributors

Sandra: ansible/ansible then added collections. what should we do? 

bring everything back so docsite is the same
guides in one spot, collections in another -> means users can't search

other problem is that things in docsite doesn't need to be versioned
developer guide is tied to core
always develop in devel
devel is just a test site

CI testing is in ansible/ansible and does call some delays
docs can't change requirements without Matt Clay changing test containers - slight misalignment

hard dependencies on teams or people? current jenkins build called by core

make content external minus core and collections - gain is less frustration for the core folks, complicates their CI stuff
when the PRs roll in, they fall into core triage

if we do move docs to another repo, need to keep: CI tests, automatic updates to devel, edit on github

who are the stakeholders? ansible core, community team, community members

do community members have a psychological preference for ansible/ansible or no opinion? two categories: edit on github / really engaged folks
really engaged people probably don't care but will have opinions on how we do things
random contributors, as long as there is a breadcrumb for their contribution, it doesn't matter 

Sandra: would like to see the top-down, who are the readers, what kind of strategy?

Different persona have different perspectives, use persona to drive the user experience, broad persona have other needs

if we make significant change to docs.ansible.com/community
