Auto-update Tech namespace pages 2024-09-16 17:57:18.606391

content/tech-docs/Tech:MediaWiki-Compatibility.md

@@ -4,19 +4,24 @@ title: Tech:MediaWiki/Compatibility
 
  `{{ {{MediaWiki navigation|compatibility|header=MediaWiki compatibility|description=Miraheze supports a variety of browsers which meet the latest web standards. Their support is fully dependent on upstream support by MediaWiki. Learn more on Miraheze Meta.|keywords=miraheze mediawiki compatibility}} }}` `{{ {{Shortcut|Old}} }}`
 <!--T:3-->
+
 Miraheze supports all browsers which are supported by the version of MediaWiki which Miraheze runs (currently, MediaWiki `{{ {{CURRENTVERSION}} }}`).
 
 <!--T:4-->
+
 MediaWiki divides all web browsers into 3 categories: **Grade A** (modern browsers, full support), **Grade C** (basic support), and **Grade X** (unknown):
 
 <!--T:5-->
+
 * **Grade A** browsers have MediaWiki's full support and are tested as being able to support all of MediaWiki's core features.
 * **Grade C** browsers are those that do not support some web standards, such as older browsers. MediaWiki attempts to disable some features in an effort to ensure readability of content, but their full support is not guaranteed.
 * **Grade X** browsers are all those browsers that are either no longer supported or have a user base that is too small to focus on. Grade X browsers are treated like Grade A browsers, meaning that MediaWiki does not fall back and disable features like it does for Grade C browsers. This is done deliberately to allow users of modern web browsers without a big user base to experience MediaWiki to the fullest.
 
 <!--T:6-->
+
 Below is a table from [MediaWiki.org](https://meta.miraheze.org/wiki/mw:) which explains which browsers fall under what category. `{{ {{mw:Compatibility browser}} }}`
 <!--T:7-->
+
 ## Further reading 
 
 * [[mw:Compatibility#Browsers|Browser compatibility]] on MediaWiki.org.

content/tech-docs/Tech:Noticeboard-Archives.md

@@ -2,9 +2,12 @@
 title: Tech:Noticeboard/Archives
 ---
 
-<!--<includeonly>--> `{{ {{Collapse top|Archives of [[Tech:Noticeboard|Technology noticeboard]]&nbsp;[{{Editlink|Tech:Noticeboard/Archives}}]&nbsp;&nbsp;&nbsp; }} }}`<!--</includeonly>-->
+<!--<includeonly>--> `{{ {{Collapse top|Archives of [[Tech:Noticeboard|Technology noticeboard]]&nbsp;[{{Editlink|Tech:Noticeboard/Archives}}]&nbsp;&nbsp;&nbsp; }} }}`
+<!--</includeonly>-->
+
 * **[Archive 1](/tech-docs/technoticeboard-archive_1)** – current
-<!--<includeonly>--> `{{ {{Collapse bottom}} }}`<!--</includeonly>--> [Category:Archives of Technology noticeboard](https://meta.miraheze.org/wiki/Category:Archives_of_Technology_noticeboard)
+<!--<includeonly>--> `{{ {{Collapse bottom}} }}`
+<!--</includeonly>--> [Category:Archives of Technology noticeboard](https://meta.miraheze.org/wiki/Category:Archives_of_Technology_noticeboard)
 
 ----
 **Source**: [https://meta.miraheze.org/wiki/Tech:Noticeboard/Archives](https://meta.miraheze.org/wiki/Tech:Noticeboard/Archives)

content/tech-docs/Tech:Noticeboard.md

@@ -4,6 +4,7 @@ title: Tech:Noticeboard
 
 `{{ {{/header}} }}`
 <!-- DO NOT MODIFY THIS AUTOARCHIVE VALUE UNLESS YOU KNOW WHAT YOU ARE DOING -->
+
 ```
 {{ {{Autoarchive/config
 |archive = Tech:Noticeboard/Archive %(counter)d

content/tech-docs/Tech:Projects.md

@@ -4,36 +4,43 @@ title: Tech:Projects
 
  `{{ {{SRE navigation|projects|header=SRE Projects|description=<translate><!--T:9--> Miraheze's system administrators are always planning out things. Learn more about our current projects on Miraheze Meta.</translate>|keywords=sre projects, miraheze sre projects}} }}`
 <!--T:10-->
+
 Miraheze continually strives to provide a strong, community centred service; along with that comes community scrutiny and community involvement over projects that are planned to take up considerable resources in terms of development, reviewing efforts, deployment, or long-standing maintenance.
 
 <!--T:2-->
+
 Below is a list of large projects that SRE has in mind, the idea of this page is to:
 * Have a centralised place for active community discussion over merits, design specs, etc.
 * Store all information about a project in a central place, not in [Phorge](https://meta.miraheze.org/wiki/Phorge).
 * Be planned and thoroughly thought through before being formally proposed as a project eligible for a goal.
 
 <!--T:3-->
+
 A proposal template is available [here](https://meta.miraheze.org/wiki//Template) and should be put in a subpage.
 
 <!--T:4-->
+
 Anyone may:
 * Propose a new project (see [here](https://meta.miraheze.org/wiki//Template)).
 * Comment on a proposal (use the talk page of the relevant proposal).
 * Work on a proposal (see [Contributing](https://meta.miraheze.org/wiki/Contributing) and *starting points* in a proposal for guidance).
 
 <!--T:11-->
+
 ## Current proposals 
 
 * [Automation of SSL requests](https://meta.miraheze.org/wiki//Automation_of_SSL_requests) — Implement a system where on request, users are able to generate a Lets Encrypt certificate which is then deployed to GitHub and to MediaWiki via $wgServer (after being approved by an SRE member) (~175 hours).
 * [CreateWiki AI improvement](https://meta.miraheze.org/wiki//CreateWiki_AI_improvement) — Improve the current AI system for CreateWiki to allow for different factors to be taken into account when assessing how 'good' a request is (~175 hours).
 * [Proper CI for Miraheze extensions](https://meta.miraheze.org/wiki//Proper_CI_for_Miraheze_extensions) — Implement proper continuous integration for extensions maintained by Miraheze (~175 hours).
 
 <!--T:6-->
+
 ## In progress 
 
 * None yet.
 
 <!--T:7-->
+
 ## Completed 
 
 * [List of Miraheze wikis](https://meta.miraheze.org/wiki//Miraheze_Wiki_List) — A page where all wikis are listed off and can be ranked/categorised and viewed by all users.

content/tech-docs/Tech:Puppet.md

@@ -50,6 +50,7 @@ puppet node find <node>
 Here are the steps you should follow when adding a new puppet agent (server) to the Puppetserver:
 
 <!-- TODO: Make this a script rather than a paste -->
+
 * Step 1: Run [https://issue-tracker.miraheze.org/P220](https://issue-tracker.miraheze.org/P220) (you will have to do it a few times as at the apt-install step, it forgets the commands to run after). If you cannot just copy-paste, use a URL to download the script:
 * `wget -O puppet.sh https://phorge-static.wikitide.net/file/data/wmmm75y6r7nls47h6rtf/PHID-FILE-viitpgh7mzarscwsnszy/puppet_install_script`
 * Step 2: (On the **puppetserver**) `cd /etc/puppetlabs/puppet/git && git pull`

content/tech-docs/Tech:Translating_Miraheze_extensions.md

@@ -5,21 +5,28 @@ title: Tech:Translating Miraheze extensions
 
 <translate>
 <!--T:1-->
+
 Miraheze develops and maintains a few extensions, for example [[<tvar|cw>github:miraheze/CreateWiki</>|CreateWiki]] and [[<tvar|mw>github:miraheze/ManageWiki</>|ManageWiki]]. As Miraheze has users with no or limited knowledge of English, internationalization is important for such users.
 
 <!--T:2-->
+
 Currently, Miraheze uses [[<tvar|twn>translatewiki:</>|translatewiki.net]] for CreateWiki and ManageWiki translations.
 
 ## TranslateWiki process 
 
 <!--T:3-->
 
 </translate>
-* <!--T:7--> Add strings on en.json.
-* <!--T:9--> Translatewiki.net bot will pull the code when they import the strings, and it will be shown to translators to translate.
-* <!--T:10--> Translators in Translatewiki.net translate the texts.
-* <!--T:11--> Translatewiki.net bot will push the $lang.json when the export bot is run.
+* <!--T:7-->
+Add strings on en.json.
+* <!--T:9-->
+Translatewiki.net bot will pull the code when they import the strings, and it will be shown to translators to translate.
+* <!--T:10-->
+Translators in Translatewiki.net translate the texts.
+* <!--T:11-->
+Translatewiki.net bot will push the $lang.json when the export bot is run.
 * <!--T:14-->
+
 They are then deployed to the Miraheze cluster (the submodule must be updated).
 [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 

content/tech-docs/Tech:Volunteers.md

@@ -4,24 +4,36 @@ title: Tech:Volunteers
 
  `{{ {{SRE navigation|members|header=<translate><!--T:14--> Technology team members</translate>|description=Miraheze's Technology team is composed of various members who work together to ensure the stability of the infrastructure behind Miraheze. Learn more on Miraheze Meta.|keywords=miraheze tech, miraheze system administrators, miraheze sysadmins}} }}`
 <!--T:1-->
+
 **Technology team members**, formerly known as Site Reliability Engineering, are responsible for the technical operation and stability of the infrastructure behind Miraheze. Team members are often referred to as **system administrators** (or **sysadmins**).
 
 <!--T:15-->
+
 The team includes volunteers in technical and less-technical roles, including project management and community liaising. You can contact the team at tech `{{ {{@}} }}`miraheze.org.
 <div style="width: 100%; overflow: auto;>
 {| class="wikitable center"
 |-
 ! class="unsortable"| [ `{{ {{fullurl:Tech:Volunteers/List|action=edit}} }}` +/-]
-! <!--T:3--> Name & Role
-! <!--T:4--> Libera Chat nickname <br /> on [[Special:MyLanguage/IRC|IRC]]
-! <!--T:5--> E-mail
-! <!--T:6--> Shell
-! <!--T:7--> GitHub
-! <!--T:8--> Phorge (admin)
-! <!--T:9--> Service Providers
-! <!--T:16--> Cloudflare
-! <!--T:10--> Domain Registrar
-! <!--T:11--> Grafana (Admin)
+! <!--T:3-->
+Name & Role
+! <!--T:4-->
+Libera Chat nickname <br /> on [[Special:MyLanguage/IRC|IRC]]
+! <!--T:5-->
+E-mail
+! <!--T:6-->
+Shell
+! <!--T:7-->
+GitHub
+! <!--T:8-->
+Phorge (admin)
+! <!--T:9-->
+Service Providers
+! <!--T:16-->
+Cloudflare
+! <!--T:10-->
+Domain Registrar
+! <!--T:11-->
+Grafana (Admin)
 |- `{{ {{Tech:{{BASEPAGENAME}}/List}} }}`
 
 ## See also