Creating a separate Ansible Collections Documentation site(samccann, 15:35:11)
the current proposal -
https://hackmd.io/TQmzyhCUSSKa22iFR_079A?both(samccann,
15:36:12)
a hack of what this might look like -
http://docs.testing.ansible.com/ansible/devel/(samccann,
15:36:27)
TL;DR; of the idea is to create a separate
'Ansible Collections Documentation' and move all scenario etc guides
over there, plus the collection index. And leave all the 'what is
ansible, how to use ansible, etc on the existing site and call it
Ansible Core Documentation(samccann,
15:36:59)
this is in 'interim' solution as there is more
work/discussions on creating an improved docs.ansible.com overall.
But that is too far out to solve our immediate problem(samccann,
15:39:52)
if we split the docs - core vs Collections - we
also impact search. Today it would be two independent
searches(samccann,
15:59:38)
ACTION: samccann
acozine - review old old DaWGs meeting minutes and other docs that
described decisions when we created the docs pipeline but decided
NOT to create a /collections/ url on the docsite(samccann,
16:03:43)
we have to decide if we duplicate
ansible.builtin to Ansible Collections and rebuild for every
ansible-base release, how do we handl the folks who upgrade only
based on Ansible releases? They won't get the updated ansible-base
until the next Ansible release, but the docs will already be on that
future ansible-base release(samccann,
16:14:16)
ACTION: - open a docs
PR to explain how to determine ansible-base version vs Ansible
package version...`ansible --version` is base, `pip show ansible` is
Ansible version(samccann,
16:23:23)
samccann acozine - review old old DaWGs meeting minutes and other docs that described decisions when we created the docs pipeline but decided NOT to create a /collections/ url on the docsite
- open a docs PR to explain how to determine ansible-base version vs Ansible package version...`ansible --version` is base, `pip show ansible` is Ansible version
samccann to create pro/con list for the different way forward and/or an outline of which content goes where
Action items, by person
acozine
samccann acozine - review old old DaWGs meeting minutes and other docs that described decisions when we created the docs pipeline but decided NOT to create a /collections/ url on the docsite
samccann
samccann acozine - review old old DaWGs meeting minutes and other docs that described decisions when we created the docs pipeline but decided NOT to create a /collections/ url on the docsite
samccann to create pro/con list for the different way forward and/or an outline of which content goes where