Jump to content

RLWiki:RLWiki NEO: Difference between revisions

From Rolling Lounge Wiki
First draft
 
m Added redundant templates/modules argument
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
Codenamed '''RLWiki NEO''', the Rolling Lounge Wiki is migrating from Miraheze to Rolling Lounge's own website.  
Codenamed '''RLWiki NEO''', the Rolling Lounge Wiki is migrating from Miraheze to Rolling Lounge's own website.  


== Reasons for the migration ==
== Reasons for the Migration ==
=== Bigger reasons ===
=== Bigger reasons ===
==== Slow performance ====
==== Slow performance ====
Miraheze is a large wikifarm that hosts over 8800 wikis<ref>https://miraheze.org/</ref> and understandably so, needs the adequate processing power. While it is a wonderful project and the ones powering deserve all the credit they get, it does load relatively slowly.  
Miraheze is a large wikifarm that hosts over 8800 wikis<ref>https://miraheze.org/</ref> and understandably so, needs the adequate processing power. While it is a wonderful project and the ones powering it deserve all the credit they get, it does load relatively slowly.  


Self-hosting the wiki allows for the server to concentrate on putting the appropriate processing power on the wiki, which has faster load times.
Self-hosting the wiki allows for the server to concentrate on putting the appropriate processing power on the wiki, which has faster load times.
==== Dormancy policy ====
==== Dormancy policy ====
Miraheze has a dormancy policy in which a wiki can get closed down or even deleted if it's inactive for too long.<ref>https://meta.miraheze.org/wiki/Dormancy_Policy#Process</ref> While this is an understandable process from Miraheze's sides, the RL Wiki is not guaranteed to have sufficient activity to avoid the process - in fact, the 60-day threshold has been reached multiple times already.  
Miraheze has a dormancy policy in which a wiki can get closed down or even deleted if it's inactive for too long.<ref>https://meta.miraheze.org/wiki/Dormancy_Policy#Process</ref> While this is an understandable process from Miraheze's side, the RL Wiki is not guaranteed to have sufficient activity to avoid the process - in fact, the 60-day threshold has been reached multiple times already.  


As there is no such policy when self-hosting the wiki, there is no need to worry about the data getting deleted due to inactivity.  
As there is no such policy when self-hosting the wiki, there is no need to worry about the data getting deleted due to inactivity.  
Line 14: Line 14:
=== Smaller reasons ===
=== Smaller reasons ===
==== Full autonomy ====
==== Full autonomy ====
While Miraheze does grant a lot of autonomy already, it's not complete.
While Miraheze does grant a lot of autonomy already, it's incomplete. For example, its extension list is a predefined set of extensions that are sufficient for most use cases, but adding any extension not included in the list would require requesting it.<ref>https://meta.miraheze.org/wiki/Extensions#Disclaimers</ref>


For example, its extension list is a predefined set of extensions which are sufficient for most usecases, but adding any extension not included in the list would require requesting it.<ref>https://meta.miraheze.org/wiki/Extensions#Disclaimers</ref>
Self-hosting gives us full autonomy over every single aspect of the wiki without being bound to anyone else.


Self-hosting gives us full autonomy of every single aspect over the wiki without being bound to anyone else.
=== More personalized domain ===
Since the rollinglounge.net domain is in our ownership, we're able to use a more personalized domain: '''wiki.rollinglounge.net'''.  


=== More personalized domain ===
== Additional improvements ==
Since the rollinglounge.net domain is in our ownership, we're able to use a more personalized domain: wiki.rollinglounge.net
Together with the migration, some improvements have been made to the wiki. While all these improvements could have already been done in the Miraheze wiki, the migration gave us a good opportunity to implement them.
=== Better infobox "backend code" ===
Most of the templates and modules in the RL Wiki are carbon copies from Wikipedia. The templates have only been adjusted as little as possible until they worked with our use cases with little knowledge on how these templates were made. This, however, had resulted in a lot of redundant and useless code left in these templates and the need to import more templates and modules from Wikipedia than needed.
 
Especially infoboxes - there was code left for handling IRL maps in the infoboxes for people.<ref name="infoboxrsplayer">https://rollinglounge.miraheze.org/wiki/Template:Infobox_RSplayer?action=edit</ref> This has been fixed in the new wiki, with infobox code only (for the most part) including necessary elements.
 
=== Better infobox naming ===
In Miraheze, the infoboxes often had some weird names. Most notably, "RSplayer," which was a generic infobox for Rolling Lounge members.<ref name="infoboxrsplayer"/> There were also unnecessary duplicates for templates that, in essence, had the same purpose.<ref>https://rollinglounge.miraheze.org/wiki/Template:Infobox_RSLevel</ref><ref>https://rollinglounge.miraheze.org/wiki/Template:Infobox_RJLevel?action=edit</ref>
 
=== New Discord Access System / WGASO ===
To prevent irrelevant discussions from the Discord channels (which cannot be moderated often), a manual approval system was put into place. Now it's possible to self-assign access to the Wiki by going to the [https://discord.gg/BuZ8XpTuzG RL | WGASO] server and entering the WGASO code "RLWIKINEO" (without the quotation marks) to gain access to the RL Wiki channels.


== References ==
== References ==
<references />

Latest revision as of 15:10, 2 October 2025

Codenamed RLWiki NEO, the Rolling Lounge Wiki is migrating from Miraheze to Rolling Lounge's own website.

Reasons for the Migration

Bigger reasons

Slow performance

Miraheze is a large wikifarm that hosts over 8800 wikis[1] and understandably so, needs the adequate processing power. While it is a wonderful project and the ones powering it deserve all the credit they get, it does load relatively slowly.

Self-hosting the wiki allows for the server to concentrate on putting the appropriate processing power on the wiki, which has faster load times.

Dormancy policy

Miraheze has a dormancy policy in which a wiki can get closed down or even deleted if it's inactive for too long.[2] While this is an understandable process from Miraheze's side, the RL Wiki is not guaranteed to have sufficient activity to avoid the process - in fact, the 60-day threshold has been reached multiple times already.

As there is no such policy when self-hosting the wiki, there is no need to worry about the data getting deleted due to inactivity.

Smaller reasons

Full autonomy

While Miraheze does grant a lot of autonomy already, it's incomplete. For example, its extension list is a predefined set of extensions that are sufficient for most use cases, but adding any extension not included in the list would require requesting it.[3]

Self-hosting gives us full autonomy over every single aspect of the wiki without being bound to anyone else.

More personalized domain

Since the rollinglounge.net domain is in our ownership, we're able to use a more personalized domain: wiki.rollinglounge.net.

Additional improvements

Together with the migration, some improvements have been made to the wiki. While all these improvements could have already been done in the Miraheze wiki, the migration gave us a good opportunity to implement them.

Better infobox "backend code"

Most of the templates and modules in the RL Wiki are carbon copies from Wikipedia. The templates have only been adjusted as little as possible until they worked with our use cases with little knowledge on how these templates were made. This, however, had resulted in a lot of redundant and useless code left in these templates and the need to import more templates and modules from Wikipedia than needed.

Especially infoboxes - there was code left for handling IRL maps in the infoboxes for people.[4] This has been fixed in the new wiki, with infobox code only (for the most part) including necessary elements.

Better infobox naming

In Miraheze, the infoboxes often had some weird names. Most notably, "RSplayer," which was a generic infobox for Rolling Lounge members.[4] There were also unnecessary duplicates for templates that, in essence, had the same purpose.[5][6]

New Discord Access System / WGASO

To prevent irrelevant discussions from the Discord channels (which cannot be moderated often), a manual approval system was put into place. Now it's possible to self-assign access to the Wiki by going to the RL | WGASO server and entering the WGASO code "RLWIKINEO" (without the quotation marks) to gain access to the RL Wiki channels.

References