Merge branch 'main' into fix_327

3 files changed, 201 insertions, 0 deletions

diff --git a/pydis_site/apps/content/resources/server-info/_info.yml b/pydis_site/apps/content/resources/server-info/_info.yml
new file mode 100644
index 00000000..52df0f8d
--- /dev/null
+++ b/pydis_site/apps/content/resources/server-info/_info.yml
@@ -0,0 +1,3 @@
+title: Server Information
+description: Information on roles, tooling, and infrastructure at Python Discord.
+icon: fab fa-discord
diff --git a/pydis_site/apps/content/resources/server-info/roles.md b/pydis_site/apps/content/resources/server-info/roles.md
new file mode 100644
index 00000000..716f5b1e
--- /dev/null
+++ b/pydis_site/apps/content/resources/server-info/roles.md
@@ -0,0 +1,131 @@
+---
+title: Python Discord Server Roles
+description: Information on the various roles at Python Discord.
+icon: fab fa-discord
+---
+
+# Basic Roles
+
+### <span class="fas fa-circle" style="color:#6e6e6e"></span> Announcements
+**Description:** A role pinged by Admins when an announcement is made in the `#announcements` channel.
+
+**How to get it:** Run the command `!subscribe` in the `#bot-commands` channel.
+To unsubscribe, run `!unsubscribe` in the `#bot-commands` channel.
+
+
+### <span class="fas fa-circle" style="color:#6e6e6e"></span> Voice Verified
+**Description:** A role that lets people speak in voice channels.
+
+**How to get it:** Send `!voiceverify` in the `#voice-verification` channel.
+There are multiple requirements listed there for getting the role.
+
+---
+
+# Server Support Roles
+
+### <span class="fas fa-circle" style="color:#55cc6c"></span> Contributors
+**Description:** A role given by staff to people who make substantial contributions to any of the server's [open source repositories](https://github.com/python-discord/) (Sir Lancebot, Python, the site, the branding repo, etc..).<br>
+This includes writing pull requests for open issues, and also for reviewing open pull requests (**we really need reviewers!**)
+
+**How to get it:** Contribute to the projects!
+There is no minimum requirements, but the role is **not** assigned for every single contribution.
+Read more about this in the [Guidelines for the Contributors Role](/pages/contributing/#guidelines-for-the-contributors-role) on the Contributing page.
+
+---
+
+# Financial Support Roles
+
+### <span class="fas fa-circle" style="color:#46e6e8"></span> Nitro Boosters
+**Description:** A vanity role for people who boost the server with their nitro subscription.
+
+**How to get it:** Boost the server with a nitro subscription.
+
+
+### <span class="fas fa-circle" style="color:#46e6e8"></span> <span class="fas fa-circle" style="color:#3e7be9"></span> <span class="fas fa-circle" style="color:#2a82bd"></span> Patrons
+**Description:** A vanity role for Patreon patrons of the server.
+
+**How to get it:** [Become a patron here!](https://www.patreon.com/python_discord)
+
+---
+
+# Staff Roles
+#### Note regarding staff roles:
+##### Q: How do I apply for Helper/Moderator/Admin?
+There is no application, and there are no public nominations. Staff keep an eye out for potential candidates, and people nominated (by staff) are put in a pool for evaluation. After a period of time the candidate for a certain role is voted on by staff higher up the hierarchy.
+
+##### Q: How do I become Helper?
+See the description of a Helper. Being active in helping others, providing good help, contributing to our projects, and abiding by our rules go a long way towards catching staff attention, and make the server a better place for both beginners and advanced Python devs.
+
+##### Role Expectations
+In addition to the informal descriptions below, we've also written down a more formal list of expectations that come with each staff role. While this list is mostly for internal use, you can read it [here](/pages/server-info/staff-role-expectations/).
+
+### <span class="fas fa-circle" style="color:#f85950"></span> Owners
+**Description:** Owners of the server.
+
+### <span class="fas fa-circle" style="color:#ff784d"></span> Admins
+**Description:** Staff who administrate the server, its function, its staff, and are involved in deciding the direction of the server.
+
+### <span class="fas fa-circle" style="color:#1abc9c"></span> Domain Leads
+**Description:** Staff in charge of a certain domain such as moderation, events, and outreach. A lead will have a second role specifying their domain.
+
+### <span class="fas fa-circle" style="color:#8dc2ba"></span> Project Leads
+**Description:** Staff in charge of a certain project that require special attention, such as a YouTube video series or our new forms page.
+
+### <span class="fas fa-circle" style="color:#ff9f1b"></span> Moderators
+**Description:** Staff who moderate the server, enforce the rules, and coordinate with staff to support the server.
+
+### <span class="fas fa-circle" style="color:#a1d1ff"></span> PyDis Core Developers
+**Description:** A role for staff who are critical contributors to the server's core projects, like the [bot](https://github.com/python-discord/bot) and the [site](https://github.com/python-discord/site), and are in charge of managing the repositories.
+
+### <span class="fas fa-circle" style="color:#a1d1ff"></span> DevOps
+**Description:** A role for staff involved with the DevOps toolchain of our core projects.
+
+### <span class="fas fa-circle" style="color:#f8d188"></span> Project Teams
+**Description:** Staff can join teams which work on specific projects in the organisation, such as our code jams, media projects, and more.
+
+### <span class="fas fa-circle" style="color:#eecd36"></span> Helpers
+**Description:** This is the core staff role in our organization: All staff members have the Helpers role.
+
+In general, being a helper means that you provide substantial help for the server's function, and have a good understanding of the culture and rules of the server.
+
+Helpers assist in the help channels, demonstrate proficiency in the language, and have strong teaching and explanation skills.
+Otherwise they might assist in other areas of the organization, such as being a core developer, events team member, or moderator.
+
+Being a helper is also more than just quantity of messages, it's about quality. We watch and we pick these people out of the crowd, because we believe that they're a valuable asset to the community, and want our users to know that they're someone that can be relied on for answers and help.
+
+---
+
+# Code Jam Roles
+### <span class="fas fa-circle" style="color:#f87dc8"></span> Code Jam Champions
+**Description:** A vanity role for winners of past code jams.
+
+**How to get it:** Win a code jam!
+
+
+### <span class="fas fa-circle" style="color:#28866c"></span> Code Jam Leaders
+**Description:** A temporary role for the duration of a code jam given to team leaders.
+
+**How to get it:** Team leaders are picked from the participants by the Events Team, and assigned for the duration of a jam.
+
+
+### <span class="fas fa-circle" style="color:#229939"></span> Code Jam Participants
+**Description:** A temporary role for the duration of a code jam given to participants.
+
+**How to get it:** Qualify for and participate in a code jam.
+
+*Note: Similar roles may exist for a game jam.*
+
+
+---
+
+# Miscellaneous Roles
+
+### <span class="fas fa-circle" style="color:#9f3fee"></span> Partners
+**Description:** Representatives of communities we are partnered with. For a list of partnered communities, see the `#partners` channel.
+
+*Note: Not related to [Discord Partners](https://discordapp.com/partners), which our server is currently a part of.*
+
+### <span class="fas fa-circle" style="color:#c77cfa"></span> Python Community
+**Description:** Prominent people in the Python ecosystem.
+Typically this will be people who have written books, people who speak at PyCon, YouTube content creators, podcasters, or notable contributors to a Python runtime or a major Python module.
+These members will have a meta role attached to further explain why they have this role, for example `CPython: Core Developer`.
diff --git a/pydis_site/apps/content/resources/server-info/staff-role-expectations.md b/pydis_site/apps/content/resources/server-info/staff-role-expectations.md
new file mode 100644
index 00000000..286386d7
--- /dev/null
+++ b/pydis_site/apps/content/resources/server-info/staff-role-expectations.md
@@ -0,0 +1,67 @@
+---
+title: Staff Role Expectations
+description: List of expectations that come with being on the staff team at Python Discord.
+icon: fab fa-discord
+---
+
+This page has a list of expectations that come with having a certain staff role in our community.
+While the term "expectations" may sound a bit formal, it's important to keep in mind that everyone with a staff role is just a volunteer and that this list is a way of having a clear overview of what each role entails.
+
+This document is mostly meant for internal reference.
+If you want a more informal description of each staff role, take a look at our [roles page](/pages/server-info/roles/#staff-roles).
+
+## Expectations
+
+### <span class="fas fa-circle" style="color:#eecd36"></span> Helpers
+
+* In general, helpers participate in Python-related channels (e.g. Help Channels, Topical Channels) and help other members of our community.
+* Helpers may also help the community by taking up organizational tasks.
+* There are no real requirements for the level of activity a helper has to have, although we do expect their activity level to be more than "nothing".
+
+### <span class="fas fa-circle" style="color:#ff9f1b"></span> Moderators
+
+* Moderators moderate our community and participate in moderation discussions in our moderators channel.
+* While moderators don't need to have high levels of activity, we do expect some form of consistent activity.
+This means that consistently being active a few times a month is better than having one day with a lot of activity per year.
+Having some kind of consistent activity helps moderators bond with the rest of the moderation team and helps them to stay up to date with the moderation policy.
+* **Moderators are not required to fulfill the helper criteria in addition to this,** although it's is obviously appreciated if they do.
+
+### <span class="fas fa-circle" style="color:#ff784d"></span> Admins
+
+*  Admins are expected to work on tasks that directly improve the community on a regular basis.
+*  Examples of these tasks include:
+    * Doing pull request reviews;
+    * Being involved in events;
+    * Overseeing road map items;
+    * Solving critical issues;
+    * Handling raids;
+    * Joining our meetings (if in a compatible timezone);
+    * Actioning issues on the organisation repo;
+    * Improving our infrastructure;
+    * Writing documentation or guides;
+    * Recruiting and on-boarding new staff members;
+    * Calling staff votes for nominees;
+    * Having one-on-ones with moderators.
+* Admins are also expected to keep each other updated on the status of the tasks they are working on.
+
+### <span class="fas fa-circle" style="color:#f85950"></span> Owners
+
+**In addition to** the regular Admin criteria, Owners also have to:
+
+*  Join staff/admin meetings as often as possible and lead those meetings.
+*  Help identify the most critical tasks and try to distribute them among the Admins during the weekly Admin meeting.
+*  Make sure that no one is "blocked" in performing their tasks.
+*  Ensure that the community isn’t neglecting important responsibilities.
+*  Manage partnerships, sponsorships and speak on behalf of the community in public settings.
+
+---
+
+## Staff Management
+First of all, it's important to appreciate that everything staff members do in this community is voluntary and the expectations listed above are not meant to change that.
+**This means it's absolutely fine for all staff members to take breaks or vacations from their activities in the community when they need to.**
+We will never hold it against someone if they are temporarily away from their responsibilities.
+
+At the same time, it's only natural for a community like ours that there's some amount of staff turnover as personal interests and circumstances change.
+Going forward, we will periodically review the activity of individual staff members and open a dialogue with staff members who are currently not meeting the expectations to see what can be done.
+It might happen that we come to conclusion that it's better for a staff member to step down from their current position.
+Do note that there are no hard feelings involved if that happens; we just want to make sure that the current staffing reflects the people who are still interested in volunteering in this community.