Справка:Style guide - История изменений

>La Villa Strangiato: quick grammar error edit

2024-02-11T01:03:32Z

quick grammar error edit

← Предыдущая версия		Версия от 04:03, 11 февраля 2024
Строка 21:		Строка 21:
	As stated on the [[Wiki Staff Guidelines]] page, it is required that work-in-progress pages be avoided. In practice, what this means is that a wiki page should have each section filled out and ready to present before being pushed to the wiki. There should be no "finish later" or "WIP" text under a section. However, elements of the section can be expanded upon after their release.		As stated on the [[Wiki Staff Guidelines]] page, it is required that work-in-progress pages be avoided. In practice, what this means is that a wiki page should have each section filled out and ready to present before being pushed to the wiki. There should be no "finish later" or "WIP" text under a section. However, elements of the section can be expanded upon after their release.

	~~Ideally, lore~~ pages should be proofread by ~~not just~~ the lore team they apply to to ensure no continuity errors, spelling mistakes, or grammatical errors (or at least as few as possible) make it to the live page. The Lore Team Administration can also be consulted for large, wide-ranging changes, but this is not strictly necessary. Sections in a lore page should strive to stay at or below four paragraphs. If they extend over four paragraphs, the section in question should be trimmed, moved to its own page (if a faction page or capital planet), or sectioned under a collapsible box.		Lore pages should be proofread by the lore team they apply to to ensure no continuity errors, spelling mistakes, or grammatical errors (or at least as few as possible) make it to the live page. The Lore Team Administration can also be consulted for large, wide-ranging changes, but this is not strictly necessary. Sections in a lore page should strive to stay at or below four paragraphs. If they extend over four paragraphs, the section in question should be trimmed, moved to its own page (if a faction page or capital planet), or sectioned under a collapsible box.

	Writers should strive to avoid hard numbers on population. Percentages are generally acceptable when describing a demographic.		Writers should strive to avoid hard numbers on population. Percentages are generally acceptable when describing a demographic.

>La Villa Strangiato в 03:38, 7 января 2024

2024-01-07T03:38:24Z

@@ Строка 19: / Строка 19: @@
 == Writing Lore Pages ==
-# Each lore page should generally begin with a brief introductory paragraph on that subject.
+As stated on the [[Wiki Staff Guidelines]] page, it is required that work-in-progress pages be avoided. In practice, what this means is that a wiki page should have each section filled out and ready to present before being pushed to the wiki. There should be no "finish later" or "WIP" text under a section. However, elements of the section can be expanded upon after their release.
-# A page on a person, place, or thing should have the subject name bolded in its introductory paragraph.
-## '''Bold''' should be used sparingly, if at all, within the confines of a lore page. To emphasize matters, use ''italics'' instead.
+Ideally, lore pages should be proofread by not just the lore team they apply to to ensure no continuity errors, spelling mistakes, or grammatical errors (or at least as few as possible) make it to the live page. The Lore Team Administration can also be consulted for large, wide-ranging changes, but this is not strictly necessary. Sections in a lore page should strive to stay at or below four paragraphs. If they extend over four paragraphs, the section in question should be trimmed, moved to its own page (if a faction page or capital planet), or sectioned under a collapsible box.
-# Ensure that the subsections within the page are consistent with other pages in the same area of knowledge. For example, if you are writing a page about a planet within the [[Empire of Dominia]], ensure that each subsection on their history, environment, culture, and demographics are structured generally the same as other pages in the Empire of Dominia category.

>La Villa Strangiato: fixes heading 1 and 2 rules

2024-01-05T03:35:38Z

fixes heading 1 and 2 rules

← Предыдущая версия		Версия от 06:35, 5 января 2024
Строка 6:		Строка 6:
	# Keep a consistent narrative tone throughout an article. An article on game mechanics should be inclined to be informative, but not especially formal; lore pages are far more formal and definitive. Try to keep your words relatively simple, and don’t use language that is too technical prior to explaining it. You can use contractions, the general “you”, and include brief jokes in the text so long as they do not overshadow or break the flow of the guide.		# Keep a consistent narrative tone throughout an article. An article on game mechanics should be inclined to be informative, but not especially formal; lore pages are far more formal and definitive. Try to keep your words relatively simple, and don’t use language that is too technical prior to explaining it. You can use contractions, the general “you”, and include brief jokes in the text so long as they do not overshadow or break the flow of the guide.
	# Remember header etiquette. Use Heading 2 (<code>==Insert Text Here==</code>) to separate sections from each other. To create sub-sections within a section, use <code>===Heading 3===</code>. Heading 1 should be used when a page has multiple topics of equal importance, such as the [[Tajaran Educational Institutions]] page. When creating a wiki page, do not create a title header using Heading 1 in the article itself; that duty will be fulfilled by the built-in page title that matches a link.		# Remember header etiquette. Use Heading 2 (<code>==Insert Text Here==</code>) to separate sections from each other. To create sub-sections within a section, use <code>===Heading 3===</code>. Heading 1 should be used when a page has multiple topics of equal importance, such as the [[Tajaran Educational Institutions]] page. When creating a wiki page, do not create a title header using Heading 1 in the article itself; that duty will be fulfilled by the built-in page title that matches a link.
	# If a subsection extends over four paragraphs, it is advised ~~but not strictly necessary~~ to place it in a drop-down menu. The page's accessibility and reading comfort should always be considered when writing extensively.		# If a subsection extends over four paragraphs, it is advised to place it in a drop-down menu. The page's accessibility and reading comfort should always be considered when writing extensively.
	# When moving on to a new subject matter within a topic, use a paragraph break. This prevents walls of text from overwhelming the reader.		# When moving on to a new subject matter within a topic, use a paragraph break. This prevents walls of text from overwhelming the reader.
	# When using Heading 1 and Heading 2, <code>Capitalize ~~The First Letter Of Every Word~~</code>. When using other headings, <code>Capitalize the first letter of the sentence</code>.		# When using Heading 1 and Heading 2, <code>Capitalize All Major Words in the Title</code>. When using other headings, <code>Capitalize the first letter of the sentence</code>.

	== Writing Gameplay Guides ==		== Writing Gameplay Guides ==

>La Villa Strangiato в 20:30, 5 октября 2023

2023-10-05T20:30:06Z

← Предыдущая версия		Версия от 23:30, 5 октября 2023
Строка 3:		Строка 3:
	== General Guidelines ==		== General Guidelines ==

	# ~~Use American~~ English~~. Color over~~ colour, ~~behavior over behaviour~~, etc~~. When in doubt, use a spelling checker or Google Docs to proof-read any spelling mistakes~~.		# Forms of English are not strictly enforced, but there is a loose policy in place to use British English (colour, neighbour, etc) over American English.
	# Keep a consistent narrative tone throughout an article. An article on game mechanics should be inclined to be informative, but not especially formal; lore pages are far more formal and definitive. Try to keep your words relatively simple, and don’t use language that is too technical prior to explaining it. You can use contractions, the general “you”, and include brief jokes in the text so long as they do not overshadow or break the flow of the guide.		# Keep a consistent narrative tone throughout an article. An article on game mechanics should be inclined to be informative, but not especially formal; lore pages are far more formal and definitive. Try to keep your words relatively simple, and don’t use language that is too technical prior to explaining it. You can use contractions, the general “you”, and include brief jokes in the text so long as they do not overshadow or break the flow of the guide.
	# Remember header etiquette. Use Heading 2 (<code>==Insert Text Here==</code>) to separate sections from each other. To create sub-sections within a section, use <code>===Heading 3===</code>. Heading 1 should be used when a page has multiple topics of equal importance, such as the [[Tajaran Educational Institutions]] page. When creating a wiki page, do not create a title header using Heading 1 in the article itself; that duty will be fulfilled by the built-in page title that matches a link.		# Remember header etiquette. Use Heading 2 (<code>==Insert Text Here==</code>) to separate sections from each other. To create sub-sections within a section, use <code>===Heading 3===</code>. Heading 1 should be used when a page has multiple topics of equal importance, such as the [[Tajaran Educational Institutions]] page. When creating a wiki page, do not create a title header using Heading 1 in the article itself; that duty will be fulfilled by the built-in page title that matches a link.

>La Villa Strangiato в 05:57, 3 октября 2023

2023-10-03T05:57:54Z

← Предыдущая версия		Версия от 08:57, 3 октября 2023
Строка 23:		Строка 23:
	## '''Bold''' should be used sparingly, if at all, within the confines of a lore page. To emphasize matters, use ''italics'' instead.		## '''Bold''' should be used sparingly, if at all, within the confines of a lore page. To emphasize matters, use ''italics'' instead.
	# Ensure that the subsections within the page are consistent with other pages in the same area of knowledge. For example, if you are writing a page about a planet within the [[Empire of Dominia]], ensure that each subsection on their history, environment, culture, and demographics are structured generally the same as other pages in the Empire of Dominia category.		# Ensure that the subsections within the page are consistent with other pages in the same area of knowledge. For example, if you are writing a page about a planet within the [[Empire of Dominia]], ensure that each subsection on their history, environment, culture, and demographics are structured generally the same as other pages in the Empire of Dominia category.

	~~{{Guides}}~~

>La Villa Strangiato: Created page with "This guide explains the style of writing one should use in most pages. They are relatively loose and informal, and as such have only a few basic guidelines. Nevertheless, following these guidelines helps create a more cohesive, readable experience when it comes to writing a lore page, a guide, or making edits to a page. == General Guidelines == # Use American English. Color over colour, behavior over behaviour, etc. When in doubt, use a spelling checker or Google Docs..."

2023-10-03T05:57:38Z

Created page with "This guide explains the style of writing one should use in most pages. They are relatively loose and informal, and as such have only a few basic guidelines. Nevertheless, following these guidelines helps create a more cohesive, readable experience when it comes to writing a lore page, a guide, or making edits to a page. == General Guidelines == # Use American English. Color over colour, behavior over behaviour, etc. When in doubt, use a spelling checker or Google Docs..."

Новая страница

This guide explains the style of writing one should use in most pages. They are relatively loose and informal, and as such have only a few basic guidelines. Nevertheless, following these guidelines helps create a more cohesive, readable experience when it comes to writing a lore page, a guide, or making edits to a page.

== General Guidelines ==

# Use American English. Color over colour, behavior over behaviour, etc. When in doubt, use a spelling checker or Google Docs to proof-read any spelling mistakes.
# Keep a consistent narrative tone throughout an article. An article on game mechanics should be inclined to be informative, but not especially formal; lore pages are far more formal and definitive. Try to keep your words relatively simple, and don’t use language that is too technical prior to explaining it. You can use contractions, the general “you”, and include brief jokes in the text so long as they do not overshadow or break the flow of the guide.
# Remember header etiquette. Use Heading 2 (<code>==Insert Text Here==</code>) to separate sections from each other. To create sub-sections within a section, use <code>===Heading 3===</code>. Heading 1 should be used when a page has multiple topics of equal importance, such as the [[Tajaran Educational Institutions]] page. When creating a wiki page, do not create a title header using Heading 1 in the article itself; that duty will be fulfilled by the built-in page title that matches a link.
# If a subsection extends over four paragraphs, it is advised but not strictly necessary to place it in a drop-down menu. The page's accessibility and reading comfort should always be considered when writing extensively.
# When moving on to a new subject matter within a topic, use a paragraph break. This prevents walls of text from overwhelming the reader.
# When using Heading 1 and Heading 2, <code>Capitalize The First Letter Of Every Word</code>. When using other headings, <code>Capitalize the first letter of the sentence</code>.

== Writing Gameplay Guides ==

# Consult an expert on the gameplay. Even if you consider yourself an especially good player, errors can still surface. Ensure you have someone to proof-read your article who is aware of the mechanics behind it.
# Keep your explanations as succinct as possible. Use short, simple sentences and clear language. Ensure your guide is free of grammatical errors, run-on sentences, and other information-obscuring errata.
# Do not include bugs, exploits, or other unintended behavior in the guide.
# Use bold to emphasize '''lifesaving information'''. Use italics to put ''stress'' on a word, or differentiate it from a proceeding or succeeding statement.

== Writing Lore Pages ==

# Each lore page should generally begin with a brief introductory paragraph on that subject.
# A page on a person, place, or thing should have the subject name bolded in its introductory paragraph.
## '''Bold''' should be used sparingly, if at all, within the confines of a lore page. To emphasize matters, use ''italics'' instead.
# Ensure that the subsections within the page are consistent with other pages in the same area of knowledge. For example, if you are writing a page about a planet within the [[Empire of Dominia]], ensure that each subsection on their history, environment, culture, and demographics are structured generally the same as other pages in the Empire of Dominia category.

{{Guides}}