# Ansible docsite personas
###### tags: `Documentation`

Personas represent various humans who are all on different automation journeys with Ansible. These docsite personas help put users in context to identify their technical content needs at each stage of their respective journeys.

We use personas to ensure Ansible community users can find help when and where they need it. If the right support is there, users are much more likely to succeed with their goals. This leads to higher levels of adoption and a more vibrant, stronger community.

See the [Ansible Community Personas](https://hackmd.io/KJInEFJmRfWsFGBGxEzviw?both) for a deeper dive into the high-level personas for the Ansible ecosystem.
##
### **Novice** || <img src="https://i.imgur.com/GMilRTB.png" alt="Person using a computer" width="150"/>

I'm a general technologist who has an idea about automation. I might already have a project or solution in mind and want to see if Ansible is the right tool for the job. I might just

**Needs:** A low barrier of entry to gain the fundamentals of Ansible automation.
**Attitude:** Wants to understand basic concepts quickly and can find small obstacles frustrating.
**Knowledge:** Undetermined. It is possible that I use Microsoft Windows as my primary operating system. I might even be completely new to open-source technology. I can be a Linux enthusiast doing home automation, a member of an IT team for a small business, or a solution architect for a Fortune 500 company.

##

### **User** || <img src="https://i.imgur.com/VrX4ygq.png" alt="Person using a computer" width="150"/>

I write automation content like playbooks and roles. When writing playbooks and roles I like to evaluate multiple options to find simple solutions to complex problems.

**Needs:** Needs best practice information that is up to date and complete.
**Attitude:** Does not like out of date, incomplete, or missing documentation.
**Knowledge:** Proficient. I am at home on the command line and enjoy technical challenges.

##

### **Operations** || <img src="https://i.imgur.com/0yGl5p2.png" alt="Person using a computer" width="150"/>

I'm all about the uptime. I provision and maintain AWX or Galaxy NG deployments that provide collections, roles, EEs, job templates, and so on across my organization. I also control which EEs to use with automation jobs, where they run, and who can execute them.

**Needs:** Planning and sizing requirements, installation, scaling physical and virtual infrastructure, upgrades, monitoring and troubleshooting.
**Attitude:** Wants to guarantee availability and identify and remediate issues as quickly as possible.
**Knowledge:** Expert knowledge of IT platforms, networking, and systems.

##

### **Developer** || <img src="https://i.imgur.com/QufXcjw.png" alt="Person using a computer" width="150"/>

I write Ansible plugins and modules in Python or other programming languages.

**Needs:** Understand programmatic options and their expected behaviour.
**Attitude:** Technically curious and prefers verbosity.
**Knowledge:** Basic to expert level programming ability.

##

### **Community maintainer** || <img src="https://i.imgur.com/GY18SFy.png" alt="Person using a computer" width="150"/>

I work with the community to maintain one or more collections as part of the Ansible package. I also work on community tooling such as Antsibull or other projects.

**Needs:** Clear path for getting collections included in the Ansible package. Guidance on lifecycles and maintenance guidelines.
**Attitude:** Often busy with another more primary role.
**Knowledge:** Proficient to expert IT skills with project management.

##

### **Community member/evangelist** || <img src="https://imgur.com/aseD8ux.png" alt="Kitten at a keyboard" width="130"/>

I participate in the Ansible ecosystem community to learn and share my Ansible knowledge.

**Needs:** Guidance on where and how I can contribute as a coder or non-coder for Ansible projects.
**Attitude:** Enthusiastic about Ansible.
**Knowledge:** Intermediate or above expertise in one or more parts of Ansible.