Overview
The Maintenance Team is responsible for ensuring that the site navigation and its components function properly for our users. Among its responsibilities are managing tags, updating components, and improving the structure of the site.
As a maintenance member, you can use the maintenance list on the main wiki to track work.
Tasks
Regular duties
When you see a submission page on the maintenance list:
- Check that the page has been cleared or greenlit by checking the greenlights channel on discord
- If it was greenlit or cleared, move the page by going into "rename", then renaming the page to the page link
- Before moving, use GPTZero or Copyleaks to check if the page is was written by AI
- If not done already, edit the main list (if applicable, for example levels or entities) to add the page name there, and tag the page with _cc and _licensebox
Note that not all devlogs will be mirrored on the site! Things such as polls, events exclusive to Discord, and things that are not easily mirrored onto the site do not need a devlog. However, things like rewrite acceptances, new Staffers/GLMP members, application updates, etc. should get a mirrored devlog/news announcement!
More specific list to come.
- Announce it in the respective channel on the Discord server
- Make a new page under the news: or devlog: category
- Title the page and write a short, one-sentence blurb about the topic. Make sure to include a page link if needed!
- Edit the Attribution Metadata to remove the page from your CROM Profile. Please assign the page to “Staff”.
- Check the Announcements module on the homepage to make sure it’s up!
The GLMP votes on rewrites, but if you see an app pending without a vote ongoing, you can start if yourself on the GLMP server by starting a thread from the rewrite bot message.
Once a rewrite has been accepted:
Remember, self-rewrites are automatically accepted, so there is just the need to log!
- DM the author looking to rewrite and tell them it has been accepted, then give them a due date if necessary (3 months from the day of acceptance)
- Add the rewrite + due date to the rewrite list on oversight (self-rewrite of deleted pages go in "self-rewrites" tab) in http://backrooms-oversight.wikidot.com/rewrite-list
- - Delete the original application off of the google form (the link is available on both the staff and GLMP discord server)
- Tag the original page with "in-rewrite" and add a disclaimer next to it on the page its listed on
"##orange|✱##" (unless the page isn't on site anymore)
- Make a small annoucement in #devlogs, and notify branches on the INT server in the #rewrite-notificaton channel
Once a rewrite has been denied:
- An explanation should be written and agreed upon by other members of the GL team. This is then DMed to the applicant.
- Delete the original application off of the google form (the link is available on both the staff and GLMP discord server)
Legacy Authors are people who have their work protected against deletion through a rewrite if they retire, due to their services to the site. They are voted on by both staff and the GLMP.
If an application is accepted:
- Tag all the relevant pages with the legacy page tag.
- Add the author and the relevant pages onto the Legacy Authors List.
- Delete the original application off of the google form (the link is available on both the staff and GLMP discord server).
- Contact the applicant to notify them of the acceptance.
If an application is denied:
- Delete the original application off of the google form (the link is available on both the staff and GLMP discord server).
- Contact the applicant to notify them of the denial, providing them with the reasoning.
Greenlight Exemption is something voted on by the GLMP to allow veteran authors to bypass the Greenlighting system and post pages freely.
If an application is accepted:
- Add the author to the Greenlight Exemption List.
- Delete the original application off of the google form (the link is available on both the staff and GLMP discord server).
- Contact the applicant to notify them of the acceptance.
- Devlog the acceptance in the discord.
If an application is denied:
- Delete the original application off of the google form (the link is available on both the staff and GLMP discord server).
- Contact the applicant to notify them of the denial, providing them with the reasoning.
Use the maintenance site page to track articles in the deletion threshold
- Pages falls into the deletion threshold if they have:
- A rating <0 and posted before June 1st of 2024 (date of the change of the deletion system)
- A rating <10 with 3 downvotes or more, posted after June 1st of 2024 (keep in mind there's a 4 day grace period where the page will not be deleted)
- If a page is within the deletion threshold
- Tag it with in-deletion for maintenance ease
- Make a devlog on discord saying it will be deleted in 24h if it remains below the threshold number
- If the page doesn't come back above the deletion threshold, you can log it and delete it using the course of action below.
Warning: Legacy pages are NOT deleted when they get rewritten (but can be deleted normally through the deletion threshold). You can recognize them by their legacy tag, or find a list in the Legacy Authors List. If one gets rewritten:
- Move it to the following adress:
https://backrooms-wiki.wikidot.com/authorname-pagename- Add the alternate tag to the page (but do NOT remove the legacy tag). This will automatically adds it to the Alternative Pages List
Deleting a page
- To keep record of article deletions, post an update in this thread to record the deletion! The format for posting in the thread can be found below:
**URL:**
**Reason:**
**Author:**
**Date:**
**First Revision Date:**
**Tags:**
**Rating:** total; upvotes/downvotes
[[collapsible show="Show Article Source" hide="Hide Article Source"]]
[[code]]
[[/code]]
[[/collapsible]]- After logging the code and information, you can delete the page:
- Step 1) Click "Delete"
- Step 2) Click "Just Rename"
- Step 3) Click "Rename/Move"
- Step 4) Click "Delete" again
- Step 5) Click "Delete Completely"
- Step 6) Click "Delete"
This is done so that if it breaks on deletion (which is something that happens where the page link becomes unusable because of some wikidot bug), the "deleted:example" URL will break, not the real one.
- If applicable, remove the name from the list (for example levels, entities…)
- If the deletion has been demanded by the author, you can tell them it has been deleted successfully.
- If the deletion was the result of the threshold, you can modify the following message and send it to them:
Hi [[*user Username]]!
Your article, [Article Name], has reached the deletion threshold, and has kept it for more than 24 hours without leaving it. As such, the article has unfortunately been deleted.
You are still free to rewrite this article in the future, which is why we have included the source code for your deleted article below.
-----
[[collapsible show="Open code" hide="Close code"]]
[[code]]
[[/code]]
[[/collapsible]]
To rewrite the page, please fill [https://forms.gle/ATXHVk1wenvDwtkR8 the rewrite form] to allow us to log your rewrite request.
-----
Thanks.
[Staff Nickname], on behalf of the Backrooms Wiki staff.- If the deletion was the result of a coldpost, you can modify the following message and send it to them:
Hello!
We appreciate that you are interested in writing for the Backrooms Wiki. However, we have a very important [http://backrooms-wiki.wikidot.com/greenlight-policy Greenlight Policy] that must be followed before you post anything. This just means that any article you write must get approval and some constructive criticism from a greenlighter before you post it. Please read over our page on the site's Greenlight Policy, linked above. Because of this policy, your article will be deleted until you get a greenlight. It is highly suggested that you join the Backrooms Wiki's official [https://discord.com/invite/2fXuFbB Discord server] if you haven't already; or, if Discord isn't your thing, you can also use the [http://backrooms-wiki.wikidot.com/forum:start forums] to get constructive criticism and a greenlight. This isn't a slight against you by any means, or even a statement on the quality of your article. Below, I have included the source code for your article in case you don't have it backed up anywhere.
[[collapsible show="+ Show article text" hide="- Hide article text"]]
[[code]]
(paste the article code here)
[[/code]]
[[/collapsible]]
@@@@
~UsernameIn order to vote for the creation of a new tag you must either:
- Propose a new tag yourself.
- Check the Tag Suggestion Thread for user suggestions.
Remember to check if the tag proposal fits the requirements described in the Tag Guide.
Once a new tag is approved:
- Add the tag to all the relevant pages.
- Update the Tag Guide to include the new tag.
- Update the Crom Tags page so that the Crom bot recognizes the new tag.
- Make the tag metadata (basically, showing the tag definition on the individual tag list
- go to /tag-metadata:tagnamehere
- create the page with the description for the tag as the content. try to keep it the same as in http://backrooms-wiki.wikidot.com/tag-guide if possible
- tag the newly created page with the tag in question
- check that it works by pressing on the name of the tag and seeing if the description shows up on the invididual tag page
- Make a devlog to announce the addition
Applying tags:
- The application of tags is normally relegated to the authors themselves, but in the event that none are applied, it is the of the maintenance team to add the basic navigation tags.
- The featured tag must be applied to the 4 new featured articles of each month.
- The team may be currently applying other tags. Check the Projects section for more information.
Staff promotion/demotion
dots means the seletected role the person is promoted to; or demoted from; is to check
● — Helpers (currently unused)
⎊ — Jstaff
⮿ — Moderator
⊚ — Admin
Step 1 - Discord updating
- Invite or kick the member from
-
- Staffrooms ●; ⎊; ⮿; ⊚
- GLMP ●; ⎊; ⮿; ⊚
- INT ⎊; ⮿; ⊚
- Appeals ⎊; ⮿; ⊚
- Archived staffrooms if needed ⎊; ⮿; ⊚
-
- Update the staff roles on the servers above + TS ●; ⎊; ⮿; ⊚
Step 2 - Site perms
- Add, promote or remove the member from
- The Backrooms wiki ● sometimes; ⎊ sometimes; ⮿; ⊚
- Backrooms Oversight ⎊; ⮿; ⊚
- Backrooms GLMP if needed ⊚ sometimes
- Backrooms sandbox 1,2 and 3 if needed ⊚ sometimes
- Backrooms INT if needed ⊚ sometimes
Some admins own some servers and/or wikis. The list can be found here.
Step 3 - Update the site
- Update the following pages by adding, moving or deleting the member
- User flairs ⎊; ⮿; ⊚
- Staff Info ⎊; ⮿; ⊚
Step 4 - Other
- Tell the new staff to make a presentation in the meet-the-staff discord server, or delete the one from the removed staff member
For Greenlighters:
- Edit the metadata list and metadata profile for their respective roles on http://glmp.wikidot.com/ (either GLT, GFT or GL)
- Edit the user flairs
- Edit their roles on the discord and GLMP (might need to invite or kick them from staffrooms and GLMP depending on whether they have the roles to stay or not
Regularly update the page Attribution Metadata so that the Crom bot recognizes the actual attribution information of the articles.
Check for:
- Co-authored pages.
- Rewrites in which the original article was not deleted.
- Staff owned pages.
- Translations.
Check the: Metatag Guide.
Can only be done by admins
The requirements to put an int site on the translation hub are:
- At least 10 pages, whether they are translations or original articles.
- If the site has any NSFW content it has to be behind adult content warnings so our <18 members cannot access it if they visit your wiki. The age limit of the site needs to reflect this as well.
- The wiki must not be broken in some way e.g. a broken home page, and having a base theme that is compatible with the one used on this wiki for translation convenience.
- The wiki must have existed continuously for at least 3 months.
The person requesting the language will also have to give staff:
- Names for the language custodians
- "Language code", for the tag and (for ULI) category name (example: FR for france, CN for chinese…)
- A logo for the translation hub block. It can be the branch logo of a country if they don't have a branch logo
Hub page creation
If the conditions are met, you can create their language hub (for example ES is Spanish Hub)
There are two different courses of action depending on whether the language is:
- This will be the only site for this language (mockup example - http://praetor.wikidot.com/french-hub). Create a new hub for this
- The language already has at least one other site (mockup example - http://praetor.wikidot.com/french-hub-2). Edit the current hub into the mockup linked here.
Add the language on the translation hub:
[[include :praetor:component:group-grid-item
|group-name=French Branch (FR)
|group-hub-url=french-hub
|preview-text=This is the hub for all English translations of levels, entities, and other articles from the French Language Wiki.
|tag=fr
|white= 225, 225, 225
|black= 0, 0, 0
|gray= 1, 38, 83
|accent= 206, 17, 39
|heading= 255, 255, 255
|logoImage= http://reyday.wikidot.com/local--files/code-test/French
]]
Variable explanations:
- white: header text color
- black: body text color
- gray: background header color
- accent: body link color
- heading: body background color
/!\ The language blocks are in alphabetical order!
Other
- Create a tag by adding it to the tag guide (in the case of ULI, the tag should be the same as the language category: for example fr: category has the fr tag). You can follow the process of tag creation that is explained earlier in the maintenance page.
- Add the language custodians of this language into the user flairs
- Add the lanuage custodians onto the INT discord server (link on the staff discord server) by sending them a discord invite
Below is a list of elements on the wiki and the discord that can be anonymized. This is by no mean a step-by-step guide, as different people might have different needs when it comes to be anonymized on the wiki:
- User posting metadata (metadata page)
- User author page
- User announcements
- User mentions in the following discord channels: #page-announcements, #announcement (such as monthly features), #devlogs (such as rewrite notifications), #info (such as critic profiles). Keep in mind to check discord @mentions AND their username separately, as they may be different
- [[*user]] mentions on the site, but also Oversight and the GLMP wiki.
- Translated pages on other sites (see with sister branches)
Projects
See "to implement" thread in staffrooms "to-do" channel