# Guía oficial de incorporación de moderadores de freeCodeCamp

Esta guía ayudará a los nuevos moderadores a ponerse en marcha con los procesos y procedimientos que siguen los moderadores experimentados en el foro de la comunidad freeCodeCamp y otras comunidades oficiales que fomentamos.

> [!NOTE] Si aún no ha leído el [Manual del moderador](https://contribute.freecodecamp.org/#/moderator-handbook), deberia empezar por ahí primero.

## Nuestro foro

### Primeros pasos

Lo primero que puede notar después de recibir el estado de moderador en el foro, es que su interfaz se verá algo diferente, con nuevas herramientas de administración para explorar y, acceder al subforo Mod-Team.

Algunas de las nuevas herramientas aparecerán dentro de un nuevo elemento de menú que parece una llave inglesa. Algunos aparecerán como nuevas pestañas o botones, o incluso nuevas opciones habilitadas dentro de los menús del foro.

Para familiarizarse con las nuevas herramientas y poderes, puede combinar uno o más de los siguientes métodos durante su primera semana con este rol elevado:

> [!TIP] Los dos primeros son los más importantes.

### Familiarícese con las herramientas de administración de discord

El foro freeCodeCamp es en realidad un foro de Discord y sigue muchas de las mismas pautas de otros foros creados en Discord. Para comenzar a familiarizarse con Discord y la función de moderación, comience leyendo la [nueva guía del usuario](https://meta.discourse.org/t/discourse-new-user-guide/96331) de Discord y la [nueva guía del moderador](https://meta.discourse.org/t/discourse-moderation-guide/63116) de Discord.

### Shadow a Mod

Todas las acciones del moderador se pueden seguir revisando los [registros de acciones](https://forum.freecodecamp.org/admin/logs/staff_action_logs). Las acciones realizadas por herramientas automatizadas como `akistmet` o `system` pueden ignorarse en su mayoría hasta que dan como resultado una publicación que debe revisarse. Posts to be reviewed will show up in the [Review](https://forum.freecodecamp.org/review) area of the forum.

For the first week or so you will want to pay attention to what is getting flagged and what is being reviewed, and compare that to the actions being taken upon the flagged posts. You may see the system account flag a post because the user created it too quickly. In many cases, the moderators will unflag the post by clicking on the "Approve Post" button or mark it as "Not Spam" (depending on the flag type).

Commonly, spam flags can also be raised by members or moderators. Common duplicitous behaviour would involve opening an account, making a post that seems harmless, then editing that post later on to add a link to an external site for the purpose of advertising it. In this case, usually the member account is fairly new and has only made this one post thus far, which indicates that the account was opened for the sole purpose of spamming the community. The decision should be made to delete the account after the first offence in this case. The same applies for accounts whose first post is deemed to be spam.

You may notice moderators performing a procedure called 'split topic'. This may be a case where a moderator has split a post that was made erroneously on an existing topic into a new topic, or a moderator merged duplicate topics that a single user has created for the same question. Watching this procedure will highlight different actions and their causes.

Another useful feature that becomes enabled for all moderators is the ability to post a "Canned Reply" which is a pre-written response that was worked out with the mod team in order to quickly respond to some well-known and repetitive scenarios. These include:

- Welcoming a new forum member who has posted code without a question -> "Welcome - remind question"
- Reminding members not to post code solutions but to provide hints and tips instead -> "Solutions Instead of Help"
- Responding to a situation where someone's code works for you but not for them -> "Browser Issues"
- Encouraging members to open GitHub issues when a possible bug is found -> "Bug Report"

There are more, which you can read through to become familiar with their respective uses. You can also find discussion around the templates in the mod-team subforum, and you are welcome to ask questions if you aren't sure how a template should be used.

### Read Mod-Team Subforum Posts

The Mod-Team subforum contains a number of posts from past and current moderators discussing the different requirements and/or challenges of moderating the forum.

Reading back through these posts can help to uncover some of the underlying goals and processes that concern forum moderators. Some of the threads may also shed some light on handling of spam and inappropriate content on the forum.

## Where to Ask for Help

To get help dealing with a situation that you are either uncomfortable with or unsure of how to handle, discuss with your fellow moderators on either the [Mod-Team Subforum](https://forum.freecodecamp.org/c/mod-team/4) or the [#mod-chat](https://discord.com/channels/692816967895220344/693157007418720277) on Discord.
