Manual:How to make a MediaWiki skin/ko

스킨을 만드는 겄은 미디어 위키의 기여에 익숙해지는 방법입니다! 그러고MediaWiki와 Wikimedia 운동에 대한 여러분의 기여를 시작합니다! 의 프런트 엔드 기술에 대해 잘 알고 있다면 MediaWiki와 Wikimedia 운동에 대한 여러분의 기여를 시작합니다!

꼭 필요한 건 아니지만 그겄은 당신이 [$url Mustache templates] 및 그러고 LESS CSS.에 익숙하게 해줍니다!^^ 본 자습서에서는 [Special:MyLanguage/Manual:Installation guide| MediaWiki]의 작동 버전이 설치되어 있고 '[Special:MyLanguage/Download#Development_releases|현재 개발 릴리스]',를 실행하고 있다고 가정합니다. 그렇지 않은 경우 먼저 설치하는 것이 좋습니다.

If you having an existing skin using the PHP BaseTemplate, this guide is not for you. Please see Manual:How to make a MediaWiki skin/Migrating SkinTemplate based skins to SkinMustache instead.

Preparation
Skin development will be a lot easier with a familiarity with Mustache templates.

At minimum, you should know be familiar with the following Mustache basics described in the example below: A skin is responsible for the rendering of user-visible content - the HTML inside the BODY tag. It is restricted from editing anything inside the HEAD. Code will be automatically generated for the skin, so that the skin can focus on presentation. If you need to modify the HEAD this is considered outside the scope of the skin, please use Hooks, extensions or configuration to do that see the FAQ for best practices on how to do that.

시작해 봅시다!
당신의 첯번째 스킨을 두 가지 옵션을 권장합니다.

옵션 1 - 포크 스킨 예제
예시 스킨은 https://github.com/wikimedia/mediawiki-skins-Example 스킨의 맨뼈 구현을 제공합니다. 스킨 폴더의 리포지토리를 복제하여 폴더가 "Example"인지 확인한 후 LocalSettings.php에 다음을 추가하십시오.

만약에 당신의 위키에당신의 스킨을 계획하기 위해 당신의 위키의 Special:Preferences 페이지에서 사용할 수 있게 되었습니다.

옵션 2 스킨 랩을 사용하기
The skins lab tool allows you to setup a skin with basic CSS and templates. 마음이 편안해지면 'ZIP으로 다운로드'를 클릭하면 스킨에 필요한 보일러 플레이트가 정리됩니다. 결과 리포지토리가 탐색하기 쉽기를 바랍니다. 당신이 ZIP place 를 다운로드하면 MediaWiki 스킨 폴더에서 LocalSettings.php을 업데이트하십시오.

만약에 당신의 위키에 당신의 스킨을 계획하기 위해 당신의 위키의 Special:Preferences 페이지에서 사용할 수 있게 되었습니다.

사람들에게 알려줍니다!
스킨을 만드는겄은 다른 사람들과 함께 하는 것이 더 재미있을 것이고 훨씬 더 쉬워질 것입니다! 사용 가능한 항목이 있으면 GitHub 또는 에 게시하는 것을 고려하십시오. Once the code is publicly available, you should [ create a skin page] (make sure you change the title!) to let people know you are open for collaboration!

Setting up a wiki page has many other benefits. You'll be able to handle bug reports in Phabricator or GitHub issues and receive patches from other volunteers in the MediaWiki community. Somebody should also be able to help you setup translation.

Mustache
In 1.35 we added support for Mustache in skins. We found using Mustache to be very helpful in the development of the Skin:Minerva and Skin:Vector skins as it allows you to separate data from presentation. Mustache partials can be used to reuse templates. To use a partial Partial.mustache in MediaWiki, simply add them to the folder you are working in and reference them using in the master template `skin.mustache`.

The data sent to Mustache templates is relatively flexible. If something is missing, you can use PHP to add data by extending the SkinMustache::getTemplateData function.

The SkinJson skin can be added to a MediaWiki development instance, to inspect the data available to skins. Note that arrays are prefixed "array-", booleans are prefixed with "is-" and objects are prefixed "data-" to help you conceptualize the data you are working with.

The data available, and in which MediaWiki versions it is available is documented on Manual:SkinMustache.php.

스킨 번역 가능(i18n)
In skin.json under ValidSkinNames, you can use the `messages` option to define translateable message keys. These keys should correspond to entries inside the i18n/en.json folder. Once registered for the skin, these will be available in your template with a prefix "msg-".

For example in the example below, the message "sitetitle" can be rendered in a Mustache template using

See Localisation for more information on why this is important.

Rendering template partials
Template partials can be used to render different parts of the skin and to avoid the problem with having a large unmaintainable skin.mustache file. In the following example, the skin renders the contents of the templates in the 3 files with the filenames Logo.mustache, Content.mustache and Footer.mustache. These files must exist in the same folder as the skin.mustache file or a subfolder of the directory containing skin.mustache.

Template partials are a great way to break up your skin to make it more readable. No template partials are predefined and available by default, however you can look at existing skins using SkinMustache for inspiration.

Read more about Mustache template partials.

Logo.mustache
Following code block is being used to show the site logo in the Example skin and you will also see the same if you create the skin from the SkinLabs.

From the code block mentioned above, the following line is responsible to show the logo `icon`:

This line assumes that, there is a key  in the array $wgLogos. So in your LocalSettings.php file, if there is a line similar as, then the logo/ icon image will be displayed. The default MediaWiki  exports a   key in the   array.

So to show the logo you need to update the LocalSettings.php and add a key.

기본값
스킨에는 최소한 단일 스타일 리소스 로더 모듈이 필요합니다. 이렇게 보일 것입니다.: 기능 키를 사용하면 i18n을 비롯한 다양한 작업에 유용한 보일러 플레이트 기본값을 사용할 수 있으며 MediaWiki core php 설명서에 나와 있는 표준화를 수행할 수 있습니다. 기능은 키 목록(opt-in 정책)이거나 1.36의 개체(opt-out 정책)일 수 있습니다. 잘 모를 경우 기능 키를 생략하여 권장 기본값을 사용하십시오. A skin at minimum requires a single style ResourceLoader module. It will look a bit like this:

The features key allows you to use useful boiler plate defaults for a variety of things including i18n and normalize which are documented in the MediaWiki core php documentation. Features can be a list of keys (opt-in policy) or in 1.36 an object (opt-out policy). If you are not sure, please omit the features key to use the recommended defaults.

CSS / LESS
The skin.json is a manifest of all the assets your skin uses. Under the `ResourceModules` key you should find the style module for your skin listed under `skins.example`. Here, under the "styles" key you can add LESS or CSS files. They will be loaded in the order they are listed. With LESS you can use @import statements in the same folder. More information about what's possible can be found in ResourceLoader/Developing_with_ResourceLoader.

When using images you should be able to use relative URIs to access the image assets.

Responsive skins / adding a meta viewport
If you are building a responsive skin, make sure to use the responsive skin option when declaring your skin in skin.json.

Images
You can extend Manual:$wgLogos with any data you choose to. This will allow site admins to configure images as they choose, but you must always conditionally render them.

In cases where images must be hardcoded for some reason., and cannot use a CSS background-image, or wgLogos for any reason you will need to extend the data sent to the template

JavaScript
JavaScript code in skins, runs in an environment where you can rely on the `mw` and `jQuery` objects having been loaded. We recommend using ResourceLoader/Package_files which will allow you to require file assets.

For information on the available API and libraries see core JS documentation.

보다 발전된
스킨에는 최소한 단일 스타일 리소스 로더 모듈이 필요합니다. 이렇게 보일 것입니다. More advanced information will provided on an as requested basis. Please ask a question on the talk page to accelerate the addition of documentation!

i18n
Messages defined in i18n/en.json can be passed directly to your Mustache template by inclusion in skin.json. Note, that you can use any messages defined inside MediaWiki core.

Extending data
The data available is documented on Manual:SkinMustache.php.

If you need to add additional data for rendering inside your skin's template that cannot be served by messages (as in the i18n section) e.g. raw HTML or complex data structures you must use a dedicated PHP class and extend the SkinMustache::getTemplateData method.

ResourceLoaderSkinModule 클래스를 통한 기본 스타일링
All skins should define a single style module with the class ResourceLoaderSkinModule. The module defines various default styles to take care of MediaWiki internals. If you want, you can disable these features and provide your own styles. Define features as an empty object to tie yourself into the recommended MediaWiki defaults. A list of support features is provided in our docs.

Example ResourceLoaderSkinModule that disables the logo feature but enables several others:

다른 확장과 통합
요청하신 대로 고급 정보가 제공됩니다. 설명서의 추가를 가속화하려면 토크 페이지에 질문을 하십시오!

i18n입니다. i18n/en.json에 정의된 메시지는 skin.json에 포함시켜 콧수염 템플릿으로 직접 전달할 수 있습니다. MediaWiki 코어에 정의된 모든 메시지를 사용할 수 있습니다. Extensions should integrate with you, not the other way round! Try to forget about extensions when writing your skin. User:Jdlrobson/Skins for extension developers is provided for extension developers to ensure they get the best compatibility. The starter templates in Manual:How_to_make_a_MediaWiki_skin will render all possible UI elements. If you omit certain pieces of data you may break support with extensions.

For certain extensions you may want to tweak the styles of the default UI elements, notably Extension:Echo. To do this you will need to read Manual:$wgResourceModuleSkinStyles.

체인징 메뉴 컨탠츠
후크를 사용하여 메뉴 구성을 변경할 수 있습니다. 예를 들어, 벡터에서는 SkinTemplateNavigation 후크를 사용하여 시계 모양 아이콘을 재배치합니다. 이렇게 할 때, 다른 스킨에 부작용이 생기지 않도록 수술 중인 피부를 확인하는 것을 잊지 마세요. The composition of menus can be changed by using hooks. For example in Vector, the SkinTemplateNavigation hook is used to relocate the watch star icon. When doing this, remember to check the skin being operated on, to avoid side effects in other skins.

I want to change elements in the head of the HTML page
Skin developers should not concern themselves with modifying anything in the HEAD of a document. Modifications of the HEAD are better served via extensions and configuration inside LocalSettings.php. For any questions please use the

The following links may be helpful:


 * Manual:$wgAppleTouchIcon
 * Manual:$wgFavicon
 * Manual:Hooks/OutputPageBodyAttributes
 * Manual:$wgSkinMetaTags

I am writing an extension that needs to style itself differently depending on the skin
Extensions can make use of skin styles to ship skin-specific styles using the skinStyles key. See Manual:$wgResourceModuleSkinStyles.

Building skins for 1.35
In 1.35 support for building skins was not as straightforward as in 1.36. If you wish to build a skin for 1.35, using template data provided in 1.36, you will need to extend the SkinMustache  PHP class. A polyfill for the Example skin is provided.

당신의 피드백은 중요합니다
쉽지 않은 점이 있다면 좀 더 쉽게 해드리고 싶기 때문에 여러분의 피드백이 중요합니다. 문제가 발생하면 Phabricator의 미디어위키 코어 스킨 아키텍처 프로젝트에 버그 보고서를 제출해 주십시오. 그러면 멋진 솔루션을 찾아보겠습니다.

토크 페이지에 자유롭게 질문해 주세요. 바보 같은 질문은 없습니다. If something is not easy, we'd like to make it easier, so your feedback is important. If you run into problems, then please file a bug report in the mediawiki core skin architecture project in Phabricator, and we'll try and find an elegant solution.

Please feel free to ask a question on the talk page. There is no such thing as a stupid question.