---
# System prepended metadata

title: 'Proposal: docs.ansible.com/community (new docsite)'
tags: [Documentation]

---

# Proposal: docs.ansible.com/community (new docsite)
###### tags: `Documentation` 

This document is meant to allow discussion around moving the community documentation to a new dedicated docsite (docs.ansible.com/community)

## Current status of community docs

As of 2020, the Community docs are split across the following
* d.a.c/ansible/community
* gh/a-c/overview
  * README
  * Checklist
  * ...

## Objective


See also [Splitting Ansible 3.0.0 from Ansible Core Docs](https://hackmd.io/TQmzyhCUSSKa22iFR_079A?view) proposal

All community, including: 
* Projects
    * AWX
    * ansible-core
    * ansible-lint
    * collections
    * molecule
* Events
    * Meetups
    * 
* Training & Other resources
    * Other books
    * Katacoda

## Steps

1. Agree we want to do this
2. Define the structure (top level index) - something like https://hackmd.io/uKhHRhFUStG_bVNhY10cLQ#New-Index-structure
3. Create new repo, initially with just `index.rst` with top level titles (no actually links)
4. Jenkins job to build
5. Individual PRs that add specific bits of content (ie PR to detail how to use GitHub Actions for CI) - Smallest PRs possible, ie update index + add new page. Anything larger is just painful
6. Maybe add some back links from existing d.a.c/ansible/community to $newplace
7. Future: Migrate content from d.a.c/ansible/community to $newplace as you mentioned 

### Structure

### Infrastructure

### Initial content

### Links and redirects

### Migrating other content


# Worked examples

## Example 1
Something with Galaxy, still links to /ansible and /galaxy

## Example 2

Developing plugins
* Link to Galaxy structure
* Link to dev_guide

## Example 3
AWX

## Questions

1. Do we need a testing site
2. Will this be confusing for users, how can we reduce confusion?
  * No duplicated content, items will be moved over one-by-one
  * Ensure we have server side redirects


# Notes
#info We know there are various gaps in the community documentation, especially around how to look after (maintain, own, manage) Collection & Collection repos. We have a lot of brand new docs to write. Currently we've been using https://github.com/ansible-collections/overview to host some RST. Though this was always viewed as a short term solution
16:19 #info I wonder if we could start a new top level docsite for these brand new docs (docs.ansible.com/community)
16:19 #info Example index page https://hackmd.io/uKhHRhFUStG_bVNhY10cLQ#New-Index-structure