Manual:How to make a MediaWiki skin/Migrating SkinTemplate based skins to SkinMustache/ja

2020年の MediaWiki 1.35 リリースの一部として、SkinMustache クラスが MediaWiki コアに追加されました. この開発により、Mustache テンプレートを使用して外装を作成できるようになりました. PHP を使用したくない、または PHP への依存度を下げたいと考えている外装開発者には魅力的なはずです. このチュートリアルは、PHP ベースの SkinTemplate 外装を SkinMustache に変換するために必要と思われる手順を示すことを目的としています.

手順 1: 外装登録の使用
以前は、外装は SkinTemplate を継承する Skin PHP クラスを宣言する必要がありました. It would need to define several properties that were used to define the skins internal key and the associated PHP template.

Since 1.35, this information can be defined at time of skin registration.

Historically, skins have required the creation of 2 PHP classes. With the new registration process, you need at most 1 PHP class.

When declaring a skin, it's possible you can set the class value to "SkinTemplate" to use the default core interface:

If your Skin contains hooks, we recommend pulling those out into a separate file.

Here is an example for Monobook: https://gerrit.wikimedia.org/r/c/mediawiki/skins/MonoBook/+/701142

Step 2: Unlock the power of templating
To follow this next step, it's assumed that a little knowledge of the Mustache template language has been acquired. At minimum, you should know the following Mustache basics described in the example below:

Hello World
Create a Mustache file with the relative path templates/skin.mustache

To use the SkinMustache class, declare the class property as SkinMustache.

Load the skin in your browser and you should see the contents of your Mustache file.

Note: In MediaWiki versions prior to 1.37 you should also define templateDirectory and template:

Using a custom class
To aid migration, you'll want to use your own custom class that extends SkinMustache, at least as an interim step and start redirecting the code from your skin template into templates.

Create a new skin class that extends SkinMustache, for example for the MonoBook skin this might be named SkinMonoBook.

When using a PHP based template e.g. MonoBookTemplate, the skin developer is expected to implement an execute function that echo's HTML. in SkinMustache, the approach is different. We provide an associative array of template data that is passed to a Mustache template.

In the example that follows, we set new data to pass to the Mustache template With this change we can make the following change to our template to output the data. Using this technique we can bridge our old skin with SkinMustache.

First we may need to refactor our execute method to separate out a function that returns a string which represents the body of the skin. It's important to note in SkinMustache, you are restricted to templating the content of the body tag.

Step 3: Embrace data.
At this point you should have a skin implementing SkinMustache which is leveraging BaseTemplate to generate HTML. The PHP inside your PHP template that implements BaseTemplate should be possible with Mustache.

SkinMustache skins are data driven, which we believe gives better flexibility in how you want to render the data. The data is informed by skins in the wild. This data is documented elsewhere at Manual:SkinMustache.php.

There is little guidance on this step, other than explore how you can generate HTML code identical to your code in BaseTemplate using only the data and templates. Challenges you face while doing this should be raised on the talk page to help others.

Step 4: Fill out the missing data
During step 3 you may find HTML you are trying to generate cannot be rendered using the data inside SkinMustache. Hopefully from step 2 however you've realized you are not limited to the data you pass to your template.

However, it's useful for us to know about data that was missing, as it's likely your skin is doing something unique that may benefit other skins.

Simply by your code existing, you've communicated bits of data that would be helpful but you are invited to explicitly file Phabricator ticket requesting the data you need.