Style guide - Revision history

Bonsaibauer: Use the Guide:Wiki category for this style guide

2026-11-06T22:19:42Z

Use the Guide:Wiki category for this style guide

← Older revision		Revision as of 22:19, 6 November 2026
Line 37:		Line 37:

	<!--T:9-->		<!--T:9-->
	Put the article text that should be translated between <code><translate></code> and <code></translate></code>. Keep the metadata, image and category outside that block. ~~Add~~ <code><nowiki>[[Category:guide:Shroudforge]]</nowiki></code> ~~at the end of the page~~. Do not type translation markers such as <code><!--T:1--></code>. Translate creates those markers when the page is prepared.		Put the article text that should be translated between <code><translate></code> and <code></translate></code>. Keep the metadata, image and category outside that block. Use <code><nowiki>[[Category:guide:Shroudforge]]</nowiki></code> for general Modloader help, or a more specific guide category when one fits, such as <code><nowiki>[[Category:Guide:Wiki]]</nowiki></code> for wiki writing and translation guides. Do not type translation markers such as <code><!--T:1--></code>. Translate creates those markers when the page is prepared.

	== Add an illustration == <!--T:10-->		== Add an illustration == <!--T:10-->
Line 89:		Line 89:
	</translate>		</translate>

	[[Category:~~guide~~:~~Shroudforge~~]]		[[Category:Guide:Wiki]]

Bonsaibauer: Link the live article example and PO export page

2026-11-06T22:14:49Z

Link the live article example and PO export page

← Older revision		Revision as of 22:14, 6 November 2026
Line 23:		Line 23:

	<!--T:4-->		<!--T:4-->
	For a Modloader help article, use the same metadata and category conventions as the other guide pages. Add a picture when it helps explain the topic. A simple page can still use this consistent layout without being marked for translation.		For a Modloader help article, use the same metadata and category conventions as the other guide pages. Add a picture when it helps explain the topic. A simple page can still use this consistent layout without being marked for translation. Compare [[Dependencies\|Dependencies]] to see the layout in use. Open its source view to inspect the metadata and image markup.

	<!--T:5-->		<!--T:5-->
Line 67:		Line 67:

	<!--T:20-->		<!--T:20-->
	For offline work, export the article's message group as a Gettext PO file from [[Special:Translate\|Special:Translate]]. Keep its group name, language code and message contexts unchanged. Import that PO file through [[Special:ImportTranslations\|Special:ImportTranslations]], selecting the matching page group and language. Review the import preview before confirming it. PO imports require the <code>translate-import</code> right.		For offline work, export the article's message group as a Gettext PO file from [[Special:Translate\|Special:Translate]] or [[Special:ExportTranslations\|Special:ExportTranslations]]. Keep its group name, language code and message contexts unchanged. Import that PO file through [[Special:ImportTranslations\|Special:ImportTranslations]], selecting the matching page group and language. Review the import preview before confirming it. PO imports require the <code>translate-import</code> right.

	<!--T:21-->		<!--T:21-->

Bonsaibauer: Escape example file and category markup

2026-11-06T22:12:22Z

Escape example file and category markup

← Older revision		Revision as of 22:12, 6 November 2026
Line 37:		Line 37:

	<!--T:9-->		<!--T:9-->
	Put the article text that should be translated between <code><translate></code> and <code></translate></code>. Keep the metadata, image and category outside that block. Add <code>[[Category:guide:Shroudforge]]</code> at the end of the page. Do not type translation markers such as <code><!--T:1--></code>. Translate creates those markers when the page is prepared.		Put the article text that should be translated between <code><translate></code> and <code></translate></code>. Keep the metadata, image and category outside that block. Add <code><nowiki>[[Category:guide:Shroudforge]]</nowiki></code> at the end of the page. Do not type translation markers such as <code><!--T:1--></code>. Translate creates those markers when the page is prepared.

	== Add an illustration == <!--T:10-->		== Add an illustration == <!--T:10-->
Line 45:		Line 45:

	<!--T:12-->		<!--T:12-->
	Upload the image through [[Special:Upload\|Special:Upload]]. Check that the upload finishes and note the exact file name. In the article metadata, use that same name after <code>picture:</code>. Add the image with markup such as <code>[[File:ShroudForge-Wiki-article-id.svg\|thumb\|left\|600px]]</code>, then preview the page to check its size and placement.		Upload the image through [[Special:Upload\|Special:Upload]]. Check that the upload finishes and note the exact file name. In the article metadata, use that same name after <code>picture:</code>. Add the image with markup such as <code><nowiki>[[File:ShroudForge-Wiki-article-id.svg\|thumb\|left\|600px]]</nowiki></code>, then preview the page to check its size and placement.

	<!--T:13-->		<!--T:13-->

Bonsaibauer: Marked this version for translation

2026-11-06T22:11:22Z

Marked this version for translation

← Older revision		Revision as of 22:11, 6 November 2026
Line 14:		Line 14:
	<translate>		<translate>

			<!--T:1-->
	Learn how to write clear Modloader Wiki articles, add illustrations and prepare pages for translation.		Learn how to write clear Modloader Wiki articles, add illustrations and prepare pages for translation.

	== Choose the right kind of page ==		== Choose the right kind of page == <!--T:2-->

			<!--T:3-->
	Most wiki pages are ordinary articles. Give the page a clear title, start with a short explanation and write the content in normal wikitext. Use headings, short paragraphs, lists and code formatting where they help readers. You do not need Translate markup or a PO file for a page that will stay in one language.		Most wiki pages are ordinary articles. Give the page a clear title, start with a short explanation and write the content in normal wikitext. Use headings, short paragraphs, lists and code formatting where they help readers. You do not need Translate markup or a PO file for a page that will stay in one language.

			<!--T:4-->
	For a Modloader help article, use the same metadata and category conventions as the other guide pages. Add a picture when it helps explain the topic. A simple page can still use this consistent layout without being marked for translation.		For a Modloader help article, use the same metadata and category conventions as the other guide pages. Add a picture when it helps explain the topic. A simple page can still use this consistent layout without being marked for translation.

			<!--T:5-->
	Use Translate when the article should be maintained in several languages. Create one English source page at its normal title, such as <code>Style guide</code>. Do not create separate pages such as <code>Style guide/de</code>. Translate creates the language versions from the marked source page.		Use Translate when the article should be maintained in several languages. Create one English source page at its normal title, such as <code>Style guide</code>. Do not create separate pages such as <code>Style guide/de</code>. Translate creates the language versions from the marked source page.

	== Use the Modloader article layout ==		== Use the Modloader article layout == <!--T:6-->

			<!--T:7-->
	For a translated article, place <code><languages /></code> at the top. Add the ShroudForge metadata comment below it, then place the article image. Keep the short description in the metadata aligned with the first paragraph readers see.		For a translated article, place <code><languages /></code> at the top. Add the ShroudForge metadata comment below it, then place the article image. Keep the short description in the metadata aligned with the first paragraph readers see.

			<!--T:8-->
	The metadata fields are <code>title</code>, <code>description</code>, <code>language</code>, <code>picture</code> and <code>creator</code>. Use <code>en-GB</code> for an English source page. The value after <code>picture:</code> must exactly match the uploaded file name.		The metadata fields are <code>title</code>, <code>description</code>, <code>language</code>, <code>picture</code> and <code>creator</code>. Use <code>en-GB</code> for an English source page. The value after <code>picture:</code> must exactly match the uploaded file name.

			<!--T:9-->
	Put the article text that should be translated between <code><translate></code> and <code></translate></code>. Keep the metadata, image and category outside that block. Add <code>[[Category:guide:Shroudforge]]</code> at the end of the page. Do not type translation markers such as <code><!--T:1--></code>. Translate creates those markers when the page is prepared.		Put the article text that should be translated between <code><translate></code> and <code></translate></code>. Keep the metadata, image and category outside that block. Add <code>[[Category:guide:Shroudforge]]</code> at the end of the page. Do not type translation markers such as <code><!--T:1--></code>. Translate creates those markers when the page is prepared.

	== Add an illustration ==		== Add an illustration == <!--T:10-->

			<!--T:11-->
	Choose a clear image that supports the article. Use a stable name such as <code>ShroudForge-Wiki-article-id.svg</code>. SVG works well for diagrams and icons. PNG or JPG can be used for screenshots and photos. Use images that you have permission to publish.		Choose a clear image that supports the article. Use a stable name such as <code>ShroudForge-Wiki-article-id.svg</code>. SVG works well for diagrams and icons. PNG or JPG can be used for screenshots and photos. Use images that you have permission to publish.

			<!--T:12-->
	Upload the image through [[Special:Upload\|Special:Upload]]. Check that the upload finishes and note the exact file name. In the article metadata, use that same name after <code>picture:</code>. Add the image with markup such as <code>[[File:ShroudForge-Wiki-article-id.svg\|thumb\|left\|600px]]</code>, then preview the page to check its size and placement.		Upload the image through [[Special:Upload\|Special:Upload]]. Check that the upload finishes and note the exact file name. In the article metadata, use that same name after <code>picture:</code>. Add the image with markup such as <code>[[File:ShroudForge-Wiki-article-id.svg\|thumb\|left\|600px]]</code>, then preview the page to check its size and placement.

			<!--T:13-->
	Upload the image before saving the article so you can check the file name and thumbnail. If a file with that name already exists, choose a different name rather than replacing it unexpectedly.		Upload the image before saving the article so you can check the file name and thumbnail. If a file with that name already exists, choose a different name rather than replacing it unexpectedly.

	== Prepare a page for translation ==		== Prepare a page for translation == <!--T:14-->

			<!--T:15-->
	Write and review the English page first. Keep headings and paragraphs focused on one idea so each unit is easy to translate. Keep product names, file names, links and code exact. Put every heading, paragraph, list item and caption that needs translation inside the <code><translate></code> block.		Write and review the English page first. Keep headings and paragraphs focused on one idea so each unit is easy to translate. Keep product names, file names, links and code exact. Put every heading, paragraph, list item and caption that needs translation inside the <code><translate></code> block.

			<!--T:16-->
	After saving the source, a translation administrator can review and mark it through [[Special:PageTranslation\|Special:PageTranslation]]. The source language should be English (United Kingdom), shown as <code>en-GB</code>. Enable translation of the page title so each language can have a natural title.		After saving the source, a translation administrator can review and mark it through [[Special:PageTranslation\|Special:PageTranslation]]. The source language should be English (United Kingdom), shown as <code>en-GB</code>. Enable translation of the page title so each language can have a natural title.

			<!--T:17-->
	Once marked, the page appears as a message group in [[Special:Translate\|Special:Translate]]. Translate the article there, or export that specific group for offline translation. Do not make a hand-written German page. Do not copy message IDs from another article.		Once marked, the page appears as a message group in [[Special:Translate\|Special:Translate]]. Translate the article there, or export that specific group for offline translation. Do not make a hand-written German page. Do not copy message IDs from another article.

	== Translate online or with a PO file ==		== Translate online or with a PO file == <!--T:18-->

			<!--T:19-->
	For online translation, choose the article group in [[Special:Translate\|Special:Translate]] and enter the translations there.		For online translation, choose the article group in [[Special:Translate\|Special:Translate]] and enter the translations there.

			<!--T:20-->
	For offline work, export the article's message group as a Gettext PO file from [[Special:Translate\|Special:Translate]]. Keep its group name, language code and message contexts unchanged. Import that PO file through [[Special:ImportTranslations\|Special:ImportTranslations]], selecting the matching page group and language. Review the import preview before confirming it. PO imports require the <code>translate-import</code> right.		For offline work, export the article's message group as a Gettext PO file from [[Special:Translate\|Special:Translate]]. Keep its group name, language code and message contexts unchanged. Import that PO file through [[Special:ImportTranslations\|Special:ImportTranslations]], selecting the matching page group and language. Review the import preview before confirming it. PO imports require the <code>translate-import</code> right.

			<!--T:21-->
	Check translation progress on [[Special:MessageGroupStats\|Special:MessageGroupStats]]. The page list at [[Special:SpecialPages\|Special:SpecialPages]] shows the wiki tools available to your account.		Check translation progress on [[Special:MessageGroupStats\|Special:MessageGroupStats]]. The page list at [[Special:SpecialPages\|Special:SpecialPages]] shows the wiki tools available to your account.

	== Update an existing article ==		== Update an existing article == <!--T:22-->

			<!--T:23-->
	Edit the English source page when the instructions change. Keep its metadata, picture and category aligned with the article. After changing translatable text, ask a translation administrator to update the page's translation markers. Translate will show which existing translations need review.		Edit the English source page when the instructions change. Keep its metadata, picture and category aligned with the article. After changing translatable text, ask a translation administrator to update the page's translation markers. Translate will show which existing translations need review.

	== Quick checklist ==		== Quick checklist == <!--T:24-->

			<!--T:25-->
	* Use a clear title and explain the topic in the first paragraph.		* Use a clear title and explain the topic in the first paragraph.
	* Use the standard metadata and the <code>guide:Shroudforge</code> category for Modloader help articles.		* Use the standard metadata and the <code>guide:Shroudforge</code> category for Modloader help articles.

Bonsaibauer: Create the Modloader Wiki style guide

2026-11-06T22:11:12Z

Create the Modloader Wiki style guide

New page

<languages />



[[File:ShroudForge-Wiki-style-guide.svg|thumb|left|600px]]
<br style="clear:both;" />

<translate>

Learn how to write clear Modloader Wiki articles, add illustrations and prepare pages for translation.

== Choose the right kind of page ==

Most wiki pages are ordinary articles. Give the page a clear title, start with a short explanation and write the content in normal wikitext. Use headings, short paragraphs, lists and code formatting where they help readers. You do not need Translate markup or a PO file for a page that will stay in one language.

For a Modloader help article, use the same metadata and category conventions as the other guide pages. Add a picture when it helps explain the topic. A simple page can still use this consistent layout without being marked for translation.

Use Translate when the article should be maintained in several languages. Create one English source page at its normal title, such as <code>Style guide</code>. Do not create separate pages such as <code>Style guide/de</code>. Translate creates the language versions from the marked source page.

== Use the Modloader article layout ==

For a translated article, place <code><languages /></code> at the top. Add the ShroudForge metadata comment below it, then place the article image. Keep the short description in the metadata aligned with the first paragraph readers see.

The metadata fields are <code>title</code>, <code>description</code>, <code>language</code>, <code>picture</code> and <code>creator</code>. Use <code>en-GB</code> for an English source page. The value after <code>picture:</code> must exactly match the uploaded file name.

Put the article text that should be translated between <code><translate></code> and <code></translate></code>. Keep the metadata, image and category outside that block. Add <code>[[Category:guide:Shroudforge]]</code> at the end of the page. Do not type translation markers such as <code></code>. Translate creates those markers when the page is prepared.

== Add an illustration ==

Choose a clear image that supports the article. Use a stable name such as <code>ShroudForge-Wiki-article-id.svg</code>. SVG works well for diagrams and icons. PNG or JPG can be used for screenshots and photos. Use images that you have permission to publish.

Upload the image through [[Special:Upload|Special:Upload]]. Check that the upload finishes and note the exact file name. In the article metadata, use that same name after <code>picture:</code>. Add the image with markup such as <code>[[File:ShroudForge-Wiki-article-id.svg|thumb|left|600px]]</code>, then preview the page to check its size and placement.

Upload the image before saving the article so you can check the file name and thumbnail. If a file with that name already exists, choose a different name rather than replacing it unexpectedly.

== Prepare a page for translation ==

Write and review the English page first. Keep headings and paragraphs focused on one idea so each unit is easy to translate. Keep product names, file names, links and code exact. Put every heading, paragraph, list item and caption that needs translation inside the <code><translate></code> block.

After saving the source, a translation administrator can review and mark it through [[Special:PageTranslation|Special:PageTranslation]]. The source language should be English (United Kingdom), shown as <code>en-GB</code>. Enable translation of the page title so each language can have a natural title.

Once marked, the page appears as a message group in [[Special:Translate|Special:Translate]]. Translate the article there, or export that specific group for offline translation. Do not make a hand-written German page. Do not copy message IDs from another article.

== Translate online or with a PO file ==

For online translation, choose the article group in [[Special:Translate|Special:Translate]] and enter the translations there.

For offline work, export the article's message group as a Gettext PO file from [[Special:Translate|Special:Translate]]. Keep its group name, language code and message contexts unchanged. Import that PO file through [[Special:ImportTranslations|Special:ImportTranslations]], selecting the matching page group and language. Review the import preview before confirming it. PO imports require the <code>translate-import</code> right.

Check translation progress on [[Special:MessageGroupStats|Special:MessageGroupStats]]. The page list at [[Special:SpecialPages|Special:SpecialPages]] shows the wiki tools available to your account.

== Update an existing article ==

Edit the English source page when the instructions change. Keep its metadata, picture and category aligned with the article. After changing translatable text, ask a translation administrator to update the page's translation markers. Translate will show which existing translations need review.

== Quick checklist ==

* Use a clear title and explain the topic in the first paragraph.
* Use the standard metadata and the <code>guide:Shroudforge</code> category for Modloader help articles.
* Upload an illustration first and use the exact same filename in the metadata and image markup.
* Leave Translate markup out of simple pages that will not be translated.
* For multilingual pages, keep translatable text inside the Translate block and let the extension create message IDs.
* Use the correct page group and language when importing a PO file.

</translate>

[[Category:guide:Shroudforge]]