User:Kermit-old/Style Guide - Revision history

Kermit: SadKermit moved page User:Kermit/Style Guide to User:Kermit-old/Style Guide: Automatically moved page while renaming the user "Kermit" to "Kermit-old"

2025-08-26T12:59:31Z

SadKermit moved page User:Kermit/Style Guide to User:Kermit-old/Style Guide: Automatically moved page while renaming the user "Kermit" to "Kermit-old"

← Older revision	Revision as of 12:59, 26 August 2025
(No difference)

Kermit-old at 15:29, 20 July 2025

2025-07-20T15:29:30Z

← Older revision		Revision as of 15:29, 20 July 2025
Line 34:		Line 34:
	# '''Do not use ‘purple prose’/‘flowery speech’.''' Wiki writing is for the reader’s comprehension, not a literature exam. Overly embellished/adjectivised writing, metaphorical speech, conjecture, rhetorical questions, and similar prose derails a reader’s train of thought and thus their comprehension.		# '''Do not use ‘purple prose’/‘flowery speech’.''' Wiki writing is for the reader’s comprehension, not a literature exam. Overly embellished/adjectivised writing, metaphorical speech, conjecture, rhetorical questions, and similar prose derails a reader’s train of thought and thus their comprehension.
	# '''Be concise.''' Avoid filler words, redundancies, and abstract language. Your first draft can always be slimmed down.		# '''Be concise.''' Avoid filler words, redundancies, and abstract language. Your first draft can always be slimmed down.

			Pages that markedly fall behind style guidelines may have the <nowiki>{{Template:Substandard}}</nowiki> banner applied to them.

	== Mechanics Page Guidelines ==		== Mechanics Page Guidelines ==

Kermit-old at 14:27, 20 July 2025

2025-07-20T14:27:50Z

← Older revision		Revision as of 14:27, 20 July 2025
Line 77:		Line 77:
	*'''Military''', in which the planet/faction's military and armed forces are described. This includes branches, general actions, and structure. If the planet is part of a larger faction, this section is not required.		*'''Military''', in which the planet/faction's military and armed forces are described. This includes branches, general actions, and structure. If the planet is part of a larger faction, this section is not required.
	*'''Technology''', in which the planet/faction's notable technological advances or specializations are expanded on. If the planet is part of a larger faction, this section is not required.		*'''Technology''', in which the planet/faction's notable technological advances or specializations are expanded on. If the planet is part of a larger faction, this section is not required.
			*'''Phoron Scarcity''', in which choice aspects of the faction/planet's technology/economy/culture/other have their phoron scarcity impacts detailed.
	*If the page is a planet, '''Major Cities/Population Centres''', where a number of major population centres can be described in brief. This should range from one to two paragraphs. Not applicable to faction pages.		*If the page is a planet, '''Major Cities/Population Centres''', where a number of major population centres can be described in brief. This should range from one to two paragraphs. Not applicable to faction pages.
	</div></div>		</div></div>

Kermit-old at 14:22, 20 July 2025

2025-07-20T14:22:36Z

← Older revision		Revision as of 14:22, 20 July 2025
Line 16:		Line 16:
	# '''Hyperlinks are the most important wiki tool,''' use them as often as you can. They are the through-thread between related pages and prevent re-explanation of already explored topics.		# '''Hyperlinks are the most important wiki tool,''' use them as often as you can. They are the through-thread between related pages and prevent re-explanation of already explored topics.
	# '''When referencing a topic already explored elsewhere, hyperlink to it.''' "See Also: Link"s and "Main Article: Link"s are ''strongly'' encouraged. The hyperlinked topic then needs not be re-explained, derailing the current topic and impacting brevity. EG: The NanoTrasen page should not re-explain the discovery of phoron, and instead present a <2 clause summary before hyperlinking to the relevant page.		# '''When referencing a topic already explored elsewhere, hyperlink to it.''' "See Also: Link"s and "Main Article: Link"s are ''strongly'' encouraged. The hyperlinked topic then needs not be re-explained, derailing the current topic and impacting brevity. EG: The NanoTrasen page should not re-explain the discovery of phoron, and instead present a <2 clause summary before hyperlinking to the relevant page.
	# '''The first mention of a name, ~~organisation~~, ~~place~~, etc. per section must be hyperlinked.''' You don't need to hyperlink something that has already been hyperlinked earlier ''in the same section''.		# '''The first mention of a name, location, event, etc. per section must be hyperlinked.''' You don't need to hyperlink something that has already been hyperlinked earlier ''in the same section''.

	=== Form & Structure ===		=== Form & Structure ===

Kermit-old at 14:21, 20 July 2025

2025-07-20T14:21:41Z

← Older revision		Revision as of 14:21, 20 July 2025
Line 43:		Line 43:

	== Lore Page Guidelines ==		== Lore Page Guidelines ==
	# ''All of the General Guidelines.''		# '''All of the General Guidelines.'''
	# '''Always have another member of the lore team — preferably from your own species team — proofread your page.''' No one is immune to making mistakes. The Lore Team Administration can be asked to proofread wide-ranging changes.		# '''Always have another member of the lore team — preferably from your own species team — proofread your page.''' No one is immune to making mistakes. The Lore Team Administration can be asked to proofread wide-ranging changes.
	# '''Do not use hard numbers anywhere''', especially for populations. Ranges, averages, or percentages are preferred.		# '''Do not use hard numbers anywhere''', especially for populations. Ranges, averages, or percentages are preferred.

Kermit-old at 14:21, 20 July 2025

2025-07-20T14:21:28Z

← Older revision		Revision as of 14:21, 20 July 2025
Line 43:		Line 43:

	== Lore Page Guidelines ==		== Lore Page Guidelines ==
	0. All of the General Guidelines.		# ''All of the General Guidelines.''
	# '''Always have another member of the lore team — preferably from your own species team — proofread your page.''' No one is immune to making mistakes. The Lore Team Administration can be asked to proofread wide-ranging changes.		# '''Always have another member of the lore team — preferably from your own species team — proofread your page.''' No one is immune to making mistakes. The Lore Team Administration can be asked to proofread wide-ranging changes.
	# '''Do not use hard numbers anywhere''', especially for populations. Ranges, averages, or percentages are preferred.		# '''Do not use hard numbers anywhere''', especially for populations. Ranges, averages, or percentages are preferred.

Kermit-old at 14:20, 20 July 2025

2025-07-20T14:20:44Z

← Older revision		Revision as of 14:20, 20 July 2025
Line 43:		Line 43:

	== Lore Page Guidelines ==		== Lore Page Guidelines ==
			0. All of the General Guidelines.
	# '''Always have another member of the lore team — preferably from your own species team — proofread your page.''' No one is immune to making mistakes. The Lore Team Administration can be asked to proofread wide-ranging changes.		# '''Always have another member of the lore team — preferably from your own species team — proofread your page.''' No one is immune to making mistakes. The Lore Team Administration can be asked to proofread wide-ranging changes.
	# '''Do not use hard numbers anywhere''', especially for populations. Ranges, averages, or percentages are preferred.		# '''Do not use hard numbers anywhere''', especially for populations. Ranges, averages, or percentages are preferred.

Kermit-old at 14:20, 20 July 2025

2025-07-20T14:20:21Z

← Older revision		Revision as of 14:20, 20 July 2025
Line 26:		Line 26:
	# '''Dropdowns should not contain novel or important information.''' The Ctrl+F and Wiki Searchbar searching does not scan dropdowns. Dropdowns should be reserved for non-critical information and similar. Create a new page if you’re using dropdowns to conceal large amounts of information.		# '''Dropdowns should not contain novel or important information.''' The Ctrl+F and Wiki Searchbar searching does not scan dropdowns. Dropdowns should be reserved for non-critical information and similar. Create a new page if you’re using dropdowns to conceal large amounts of information.
	# '''Be mindful of paragraph and sentence length.''' Know when to start a new paragraph; a paragraph begins when there is a change in topic or idea. Be wary of running on sentences that go on for >4 clauses, and avoid using parentheses or semi-colons to jam more clauses into a sentence when a new sentence is better for reader comprehension.		# '''Be mindful of paragraph and sentence length.''' Know when to start a new paragraph; a paragraph begins when there is a change in topic or idea. Be wary of running on sentences that go on for >4 clauses, and avoid using parentheses or semi-colons to jam more clauses into a sentence when a new sentence is better for reader comprehension.
	# '''Create a [https://www.mediawiki.org/wiki/Help:Subpages subpage] if you are condensing too much information in one place.''' ~~A page should not take more than 30 minutes for the average person to read.~~		# '''Create a [https://www.mediawiki.org/wiki/Help:Subpages subpage] if you are condensing too much information in one place.'''
	# '''Do not repeat ideas or topics''', and stay on topic.		# '''Do not repeat ideas or topics''', and stay on topic.

Line 45:		Line 45:
	# '''Always have another member of the lore team — preferably from your own species team — proofread your page.''' No one is immune to making mistakes. The Lore Team Administration can be asked to proofread wide-ranging changes.		# '''Always have another member of the lore team — preferably from your own species team — proofread your page.''' No one is immune to making mistakes. The Lore Team Administration can be asked to proofread wide-ranging changes.
	# '''Do not use hard numbers anywhere''', especially for populations. Ranges, averages, or percentages are preferred.		# '''Do not use hard numbers anywhere''', especially for populations. Ranges, averages, or percentages are preferred.
	# '''Sections in a lore page should strive to stay at or below four paragraphs.''' If a section extends over four paragraphs, the section should be heavily trimmed or move onto its own subpage (eg. Biesel/Culture). ''Do not use dropdowns to hide large sections''.		# '''Sections in a lore page should strive to stay at or below four paragraphs.''' If a section extends over four paragraphs, the section should be heavily trimmed or move onto its own subpage (eg. Biesel/Culture). ''Do not use dropdowns to hide large sections''. A page should not take more than 30 minutes for the average person to read.

	<div class="toccolours mw-collapsible mw-collapsed">		<div class="toccolours mw-collapsible mw-collapsed">

Kermit-old at 14:16, 20 July 2025

2025-07-20T14:16:33Z

← Older revision		Revision as of 14:16, 20 July 2025
Line 32:		Line 32:
	# '''Wiki spelling is based on British English.''' No one enforces this, but it helps players using search functions, so it ''ought'' to be used.		# '''Wiki spelling is based on British English.''' No one enforces this, but it helps players using search functions, so it ''ought'' to be used.
	# '''Use dispassionate, objective language.''' Detailings of events should not be opinionated, so as to allow the reader to come to their own conclusion and so characters cannot point to the ‘correct’ opinion. Ambiguity describing in-universe events is acceptable and encouraged.		# '''Use dispassionate, objective language.''' Detailings of events should not be opinionated, so as to allow the reader to come to their own conclusion and so characters cannot point to the ‘correct’ opinion. Ambiguity describing in-universe events is acceptable and encouraged.
	# '''Do not use ‘purple prose’.''' Wiki writing is for the reader’s comprehension, not a literature exam. Overly embellished/adjectivised writing, metaphorical speech, conjecture, rhetorical questions, and similar prose derails a reader’s train of thought and thus their comprehension.		# '''Do not use ‘purple prose’/‘flowery speech’.''' Wiki writing is for the reader’s comprehension, not a literature exam. Overly embellished/adjectivised writing, metaphorical speech, conjecture, rhetorical questions, and similar prose derails a reader’s train of thought and thus their comprehension.
	# '''Be concise.''' Avoid filler words, redundancies, and abstract language. Your first draft can always be slimmed down.		# '''Be concise.''' Avoid filler words, redundancies, and abstract language. Your first draft can always be slimmed down.

Kermit-old at 14:15, 20 July 2025

2025-07-20T14:15:46Z

← Older revision		Revision as of 14:15, 20 July 2025
Line 15:		Line 15:
	==== Hyperlinks ====		==== Hyperlinks ====
	# '''Hyperlinks are the most important wiki tool,''' use them as often as you can. They are the through-thread between related pages and prevent re-explanation of already explored topics.		# '''Hyperlinks are the most important wiki tool,''' use them as often as you can. They are the through-thread between related pages and prevent re-explanation of already explored topics.
	# '''When referencing a topic already explored elsewhere, hyperlink to it.''' "See Also: Link"s and "Main Article: Link"s are ''strongly'' encouraged. The hyperlinked topic then needs not be re-explained, derailing the current topic and impacting brevity. EG: The NanoTrasen page should not re-explain the discovery of phoron, and instead present a 1 clause summary before hyperlinking to the relevant page.		# '''When referencing a topic already explored elsewhere, hyperlink to it.''' "See Also: Link"s and "Main Article: Link"s are ''strongly'' encouraged. The hyperlinked topic then needs not be re-explained, derailing the current topic and impacting brevity. EG: The NanoTrasen page should not re-explain the discovery of phoron, and instead present a <2 clause summary before hyperlinking to the relevant page.
	# '''The first mention of a name, organisation, place, etc. per section must be hyperlinked.''' You don't need to hyperlink something that has already been hyperlinked earlier ''in the same section''.		# '''The first mention of a name, organisation, place, etc. per section must be hyperlinked.''' You don't need to hyperlink something that has already been hyperlinked earlier ''in the same section''.