Community Team Hub

Community Team Hub

Overview

---

The community team is centered around all sorts of interactions with the community. The work of the team therefore aims at listening to the community (site and discord), as well as communicating all sorts of information to them.

Tasks

---

Monitoring the discord suggestion and community feedback threads

Show course of action

• When a suggestion thread is created, make sure it has been tagged with the right suggestion tags to sort them (especially contest ideas).
• Monitor the discussion to ensure it remains civil and efficient.
• Tagging the thread with
  • "In development" if you or another staff member brought the subject to the rest of staff on Staffrooms (discord staff server) for a more in-depth discussion
  • "Denied" if the topic or suggestion won't get implemented
  • "Resolved" if the topic or suggestion has been implemented or the issue has been solved
• As said above, bring the topic/suggestion on Staffrooms and ping the "Suggestion soldier" staff role to notify them and start a staff discussion.
• Once the topic is settled (whether it has been resolved or denied), close the suggestion or comfeed thread to prevent further discussion.

Managing events (contests or other)

Show course of action

• When choosing a contest theme with the rest of the team, list the community theme suggestions by checking the "contest idea" tagged threads on the suggestion forum.
• Once the theme has been chosen, define:
  • The rules (use previous contests as examples and operate tweaks if needed)
  • The dates (using the staff calendar present in "staff-links" in Staffrooms). If possible, contests should ideally be separated by ~ 2 months from each other, and not occur at the same time as another event.
• Create the contest hub page (see older contest hubs as example, but try using different themes or formats if needed).
• When the contest starts:
  • Post the hub. (And add its link to the hubs hub, link in the http://backrooms-wiki.wikidot.com/contest-archive and the contest tag to the tag list)
  • Announce it on discord (@everyone ping).
  • Put the link on the annoucement blocks on the site front page (here).
• During the contest:
  • Answer the potential questions.
  • Check for eventual rulebreaks/cheats.
  • Announce each new phase (posting period, then voting period) both on discord (@secondary-ping) and the wiki by editing the newsblock to mention the current phase.
• When the contest ends:
  • Announce the winners on discord with an @everyone.
  • Edit the newsblock to say the contest has concluded.
  • Ask the 3 winners + the 4^th place for a page to feature for the month coming.

Managing the monthly writing features

Show course of action

• Check if a GLMP member started the vote on the first day of each month. If not, you can start it yourself.
• Ping the GLMP each day, once for the initial annoucement and then once per day during the two following days to make sure as many people vote.
• After the three days of voting, close the votes and gather a quote for each of the 4 selected entries (DM the author for a quote, and if they don't answer in two days, take one yourself from the page).
• Tag the four entries with the "featured" tag.
• Edit the featured part of the front page to showcase for each entry the name, an image of the page, the author name(s), and the selected quote.
• Once done, make an announcement on discord, listing the featured pages and the names of the authors.

Managing the monthly art features

Show course of action

• Look through ⁠the backrooms art channel on Discord and find 6 art pieces you think are deserving of being featured. Try to pick pieces from artists who haven't been featured in the month before or aren't often featured, and avoid picking the same artist twice.
• When 6 potential features have been chosen, send a link to each in ⁠the community team channel of the Staffrooms server for approbation by other staff members. Then, DM each artist informing them that their art has been chosen as a potential art feature. Ask if they're okay with this and make sure they know that this means licensing their art as CC BY-SA 3.0 (usually, their art is already this license since it showcases a wiki concept, and is therefore a derivative, but the question should still be asked).
  • A message you can use:

Hey. Staff on TS are choosing art from the server to feature on the website. We were wondering if we could use [link to post]⁠ as one of the features? This would include the art being licensed under CC BY-SA 3.0.

• If someone says no to their art being used as a feature, find another art piece to use instead and repeat the same steps.
• Upload all images to the files on http://backrooms-wiki.wikidot.com/featured-art-archive. Name them "AAAMMauthorname" in order to sort them more easily, for example "202409reyday".
• Go to the artblock section of the front page. This is the block responsible for showcasing featured art on the front page. Click to view the page source before editing to get an idea of the template. The only two sections you will be editing are the links on the numbered list and the featured artist's names.
  • For the numbered list, paste the link to each featured art piece for that month.
  • For the artist's names, type their Wikidot username if they have one. If not, use their Discord account username or their Discord showcased username.
• On the featured art archive, copy and paste the previous month's code. Only replace the month name, link, and artist's name.
• Make an announcement on Discord to notify of the new featured arts of the month.

Managing the Pages of the Week

Show course of action

• Each sunday, use the "random page" wiki feature to find a page to feature.
• Make a small analysis to post on discord devlogs and onto the PotW (Page of the Week) as well.
• Edit the PotW archive on the PotW hub to include the new page + edit the total number.
• Edit the PotW block on the http://backrooms-wiki.wikidot.com/front-page:announcements to include the new name, link, author name, and a small catchy sentence to make people click.

Managing the Monthly Site News

Show course of action

• Throughout the month, take notes of all events, changes (like policy changes), site additions (like PotW) and small imformation (like new tags), basically everything that happened about the site this month.
• In the site news, make the following blocks and write a small presentation of them (feel free to copy the code from previous news pages to keep things like header or author names)
  • a block for each of these points
  • a block for every small stuff at once
  • a block for monthly featured articles and art features
  • a block for staff and GLMP updates
• Publish the news on the site (link "news-YYYY-MM", for example "news-2024-08"), with the page title being "Month YYYY Backrooms report" (for example "August 2024 Backrooms Report")
• Go on Oversight and create a "news:N" page for the information to appear on oversight hub. For example "news:5" if it's the fifth news page created (you can check the news archive if you're unsure)
  • Then write a small catchy introductory sentence to introduce the news on said page, and put the link of the site news page there as well.
• Edit the announcements on the wiki hub page to include the site news link and a catchy introduction text.
• Announce the site news on Discord pinging @secondary-ping

Managing the Social Accounts

Show course of action

Twitter/Bluesky

The main thing that I(ReyDay) keep in mind when it comes to running the Twitter account is that Twitter is meant to be silly. Shitposts gain the most traction, so have fun with it! Of course, try not to get too carried away, but there should be a general sense of silliness and friendliness among people. Also keep in mind that posts should stay related to the Backrooms or our community. Though, don’t be afraid to retweet or engane with stuff from SCP or adjacent communities too.

I personally try to answer as many of the replies as I can in a timely manner, but ALWAYS make sure to check the person’s profile first before you interact. Make sure you keep yourself and the other members of the community safe!

You should also try to avoid shilling pages. The only time you should post a link to a written article is for monthly features or when a large rewrite happens. People are a lot more receptive to art pages being shilled, so try to go for that instead.

Keep in mind that you represent the community and our site goals when you post, we don’t want to give folks the wrong idea about ourselves, yk?

But that’s all, really! Happy posting!

P.S. Include the mascot in as many posts as you can >:3

Tumblr

• 1. Follow various Backrooms tags so it shows up on the dash
• 2. Reblog and add to the queue projects and various images that fit the vibe of the site.
  • 2a. If the project is not related to the Backrooms at all, but still has good vibes, tag the post with "what is this a crossover episode"
  • 2b. If the project is Backrooms themed, but not related to the wiki but still really cool, tag it with "other Backrooms projects"
• 3. If someone mentions us in a positive way, reblog and queue a silly response to them
• 4. Use the tags to show personality a bit
• 5. Admins can only answer asks, but all asks that aren't offensive or rude will be answered. If a link to the wiki is applicable, link it.
• 6. Queue up various pages from the wiki.
  • 6a. Ask members on the Discord, use featured pages, use Page of the Week, or hit a random page to figure out what to post.
  • 6b. Copy the image that represents the page best and put that first
  • 6c. Write a little blurb about the page that's not the metadata or grab the opening lines.
  • 6d. Post the link to the page
  • 6e. Tag the post and add it to the queue

Managing Annual Features and Annual satisfation poll

Show course of action

Annual features:

The 2023 poll can be found in staffrooms in the staff-links channel, and can be used as an example

• The votes for each month are for pages that got featured in said month (so 4 options per month + an "other" option where people can submit another page of the month
• Multiple choices possible
• Start the vote preferably at the start of January of the next year

• Once the vote is closed, go to http://backrooms-wiki.wikidot.com/yearly-features-hub and move the previous year into a collapsible, then copy the block code to add the 12 winners.
• Tag the entries with "annual-feature"
• Make an announcement on Discord, then on the front hub

Community poll

The structure can be found in staffrooms in the staff-links channel.

Other Community Interactions

• Regulerly start VCs to chill and make members join and discuss

Projects

See "to implement" thread in staffrooms "to-do" channel