WikiAdmin: Add structured forms and visual template editing

2026-09-15T07:04:25Z

Add structured forms and visual template editing

← Older revision		Revision as of 07:04, 15 September 2026
Line 2:		Line 2:
	<p>Create useful pages with a few supported fields. The wiki builds its indexes from those fields.</p></div>		<p>Create useful pages with a few supported fields. The wiki builds its indexes from those fields.</p></div>
	== Create a reference page ==		== Create a reference page ==
	~~Search~~ for the subject first. If there is no existing article, ~~create a page using~~ its ~~documented in-game name. For ambiguous names, add a short qualifier, such as a place or entity type, only when needed.~~		[[Special:UserLogin\|Log in]] with an editor account, then search for the subject first. If there is no existing article, choose its form:

	~~Copy~~ the appropriate blank ~~template~~ below to the beginning of ~~the~~ article~~. Fill~~ only supported values, then add ~~readable~~ prose ~~under the template~~. The template categorizes the page and ~~sends~~ its nonempty fields ~~to the database~~. ~~Do not place a~~ template on ~~an index or help~~ page.		{\| class="wikitable fw-data-table"
			! Reference type !! Create or edit
			\|-
			\| Item \|\| [[Form:Item\|Open the item form]]
			\|-
			\| Quest \|\| [[Form:Quest\|Open the quest form]]
			\|-
			\| Zone \|\| [[Form:Zone\|Open the zone form]]
			\|-
			\| NPC \|\| [[Form:NPC\|Open the NPC form]]
			\|-
			\| Dungeon \|\| [[Form:Dungeon\|Open the dungeon form]]
			\|}

			# Enter the documented in-game name. For ambiguous names, add a short qualifier, such as a place or entity type, only when needed.
			# Fill only fields supported by evidence. Leave unknown values blank. Suggested page names help connect related articles; you can enter a documented name even if its page does not exist yet.
			# Add a source link, the applicable version when known, and a review status when recorded. Use the '''Article text''' box for the introduction, details, and additional sources.
			# Preview the page, check the information box and links, write an edit summary, and save.

			The form adds the appropriate reference template and category automatically. Use these forms for real subject pages.

			== Edit an existing reference page ==
			Open the article and choose '''Edit with form''' to update its reference fields and article text together. Existing prose and other content appear in the '''Article text''' box; preserve them when changing a field. A new page may need a moment before its category makes the form tab available. You can also open the relevant form above and enter the existing page name.

			Choose '''Edit''' to use the visual editor for prose, links, and citations. Select an information box to see its template parameters and descriptions. Choose '''Edit source''' when you want to work directly with wiki markup. Check the preview after editing an information box.

			== Edit source ==
			The blank templates below are available for source editing. Copy the appropriate pattern to the beginning of a subject article, fill only supported values, then add prose below it. The template categorizes the page and records its nonempty fields. Keep just one primary reference template on each subject page.

	Use plain page names in relationship fields such as <code>zone</code>, <code>starts_at</code>, and <code>ends_at</code>; the template creates the links. Use plain numbers in numeric fields. Do not add commas, units, or level-range punctuation to a single numeric field.		Use plain page names in relationship fields such as <code>zone</code>, <code>starts_at</code>, and <code>ends_at</code>; the template creates the links. Use plain numbers in numeric fields. Do not add commas, units, or level-range punctuation to a single numeric field.
Line 70:		Line 97:
	}}		}}
	</nowiki></pre>		</nowiki></pre>
	=== Add the article text ===		== Add the article text ==
	Use a short introduction, relevant sections, and a Sources section. Explain claims in prose so the article is useful beyond its information box. Keep each source near the claim it supports when the connection would otherwise be unclear.		Use a short introduction, relevant sections, and a Sources section. Explain claims in prose so the article is useful beyond its information box. Keep each source near the claim it supports when the connection would otherwise be unclear.

	To link another article~~, write~~ <code><nowiki>[[Page title]]</nowiki></code>. ~~To cite~~ a ~~web page without a citation extension, use an external link:~~ <code><nowiki>[https://example.org/source Descriptive source title]</nowiki></code>. The example address is a formatting placeholder, not a game source.		In the visual editor, use the link and citation tools. In the forms' article text box or the source editor, link another article with <code><nowiki>[[Page title]]</nowiki></code>. Cite a source next to the claim with <code><nowiki><ref>[https://example.org/source Descriptive source title]</ref></nowiki></code>, then place <code><nowiki><references /></nowiki></code> under a Sources heading. The example address is a formatting placeholder, not a game source.

	Use <code>verification_status</code> only with one of these values: <code>Unverified</code>, <code>Source checked</code>, <code>In-game checked</code>, or <code>Needs review</code>. Leave the field blank when no status has been recorded. See [[Project:Data policy]] for the definitions.		Use <code>verification_status</code> only with one of these values: <code>Unverified</code>, <code>Source checked</code>, <code>In-game checked</code>, or <code>Needs review</code>. Leave the field blank when no status has been recorded. See [[Project:Data policy]] for the definitions.

Maintenance script: Create Forever Wiki starter page

2026-09-15T03:44:53Z

Create Forever Wiki starter page

New page

<div class="fw-hub-intro"><span class="fw-eyebrow">CONTRIBUTOR GUIDE</span>
<p>Create useful pages with a few supported fields. The wiki builds its indexes from those fields.</p></div>
== Create a reference page ==
Search for the subject first. If there is no existing article, create a page using its documented in-game name. For ambiguous names, add a short qualifier, such as a place or entity type, only when needed.

Copy the appropriate blank template below to the beginning of the article. Fill only supported values, then add readable prose under the template. The template categorizes the page and sends its nonempty fields to the database. Do not place a template on an index or help page.

Use plain page names in relationship fields such as <code>zone</code>, <code>starts_at</code>, and <code>ends_at</code>; the template creates the links. Use plain numbers in numeric fields. Do not add commas, units, or level-range punctuation to a single numeric field.

=== Item ===
<pre><nowiki>
{{Item
|type=
|slot=
|quality=
|item_level=
|required_level=
|zone=
|source_url=
|game_version=
|verification_status=
}}
</nowiki></pre>
=== Quest ===
<pre><nowiki>
{{Quest
|quest_level=
|zone=
|starts_at=
|ends_at=
|source_url=
|game_version=
|verification_status=
}}
</nowiki></pre>
=== Zone ===
<pre><nowiki>
{{Zone
|type=
|region=
|min_level=
|max_level=
|source_url=
|game_version=
|verification_status=
}}
</nowiki></pre>
=== NPC ===
<pre><nowiki>
{{NPC
|type=
|zone=
|faction=
|level=
|source_url=
|game_version=
|verification_status=
}}
</nowiki></pre>
=== Dungeon ===
<pre><nowiki>
{{Dungeon
|zone=
|min_level=
|max_level=
|party_size=
|source_url=
|game_version=
|verification_status=
}}
</nowiki></pre>
=== Add the article text ===
Use a short introduction, relevant sections, and a Sources section. Explain claims in prose so the article is useful beyond its information box. Keep each source near the claim it supports when the connection would otherwise be unclear.

To link another article, write <code><nowiki>[[Page title]]</nowiki></code>. To cite a web page without a citation extension, use an external link: <code><nowiki>[https://example.org/source Descriptive source title]</nowiki></code>. The example address is a formatting placeholder, not a game source.

Use <code>verification_status</code> only with one of these values: <code>Unverified</code>, <code>Source checked</code>, <code>In-game checked</code>, or <code>Needs review</code>. Leave the field blank when no status has been recorded. See [[Project:Data policy]] for the definitions.

== Create a guide ==
Class and profession guides can use the shared metadata template at the top of the article. Add the appropriate category at the end. The following is a blank pattern; replace or remove the category as appropriate.
<pre><nowiki>
{{Page metadata
|source_url=
|game_version=
|verification_status=
}}

== Overview ==

== Sources ==

[[Category:Classes]]
</nowiki></pre>
For a profession guide, use <code><nowiki>[[Category:Professions]]</nowiki></code> instead. Add categories only to real subject pages, not to copied template examples.

== How the database works ==
A reference template records each filled field as a typed property. For example, <code>required_level</code> uses [[Property:Required level]], which accepts a number. Relationship fields use page names; <code>zone</code> uses [[Property:Located in]]. The [[Items]], [[Quests]], [[Zones]], [[NPCs]], and [[Dungeons]] indexes query the categories and properties added by their templates.

Keep the information box's structured values in agreement with the article text. When a record is missing from an index, check that its template is spelled correctly and preview the page for errors. Updates may appear after the site's background jobs finish.

== Before you save ==
* Confirm that the article describes Forever and records the applicable version when known.
* Leave unsupported values blank, and use specific source links.
* Check page links and the information box in the preview.
* Write a short edit summary describing your change.

[[Project:Data policy|Sources, review statuses, and unknown values]]

Help:Editing - Revision history

WikiAdmin: Add structured forms and visual template editing

Maintenance script: Create Forever Wiki starter page