Gswiki:Style guide/Formatting special articles - Revision history

GS4-XERAPHINA: GS4-XERAPHINA moved page Help:Style/Formatting special articles to Gswiki:Style guide/Formatting special articles: Working through pages to separate style (specific to gswiki) vs help (editing help that could be used across various wikis)

2023-10-09T20:14:08Z

GS4-XERAPHINA moved page Help:Style/Formatting special articles to Gswiki:Style guide/Formatting special articles: Working through pages to separate style (specific to gswiki) vs help (editing help that could be used across various wikis)

← Older revision	Revision as of 15:14, 9 October 2023
(No difference)

GS4-XERAPHINA: /* Proposal Pages */

2023-09-16T18:36:08Z

Proposal Pages

← Older revision		Revision as of 13:36, 16 September 2023
Line 91:		Line 91:

	===Proposal Pages===		===Proposal Pages===
	Pages containing proposals of any form that players have created ~~can~~ ~~utiltize~~ ~~the~~ ~~Proposal~~ ~~name~~ ~~space,~~ ~~and~~ be ~~named~~ ~~"Proposal:{Proposal~~ ~~subject}"~~. ~~These~~ ~~pages~~ will ~~only~~ be ~~allowed~~ ~~in the [[:Category: Player proposals\|Player proposal category]]. Additionally,~~ these pages ~~are open to edits by any editor, but discussion is strongly advised to remain on the "Talk/Discussion" page before edits are made~~.		Pages containing proposals of any form that players have created should be set up as subpages to the contributor's USER page. Moderation will be light on these pages.

	Moderation will be light on these pages.

	===Other Help Pages===		===Other Help Pages===

MOD-GSMOTTE: Updated for consistency so that code blocks are around copy/paste information.

2023-06-18T18:52:55Z

Updated for consistency so that code blocks are around copy/paste information.

← Older revision		Revision as of 13:52, 18 June 2023
Line 5:		Line 5:
	===Redirects===		===Redirects===

	In some cases, an article may have more than one reasonable name, for instance, "CS" and "Casting strength". In this case, you can use redirect pages to make both names go to the same article. To do this, pick the most canonical name ("Casting strength") and create the article there. Then create an article under the other name(s) ("CS") with the only text being <nowiki>"#REDIRECT [[Real article name]]"</nowiki>. Then, if someone visits the other names, they'll automatically be sent to the canonical name.		In some cases, an article may have more than one reasonable name, for instance, "CS" and "Casting strength". In this case, you can use redirect pages to make both names go to the same article. To do this, pick the most canonical name ("Casting strength") and create the article there. Then create an article under the other name(s) ("CS") with the only text being <code><nowiki>"#REDIRECT [[Real article name]]"</nowiki></code>. Then, if someone visits the other names, they'll automatically be sent to the canonical name.

	Don't abuse this to make only vaguely related things go to the same article, though. Redirecting "Lock Mastery" to "Pick locks" or "Pickpocketing" to "Justice" would be a bad idea, but redirecting "Lockpicking" to "Pick locks" or "Combat maneuver list" to "Combat maneuvers" probably wouldn't be.		Don't abuse this to make only vaguely related things go to the same article, though. Redirecting "Lock Mastery" to "Pick locks" or "Pickpocketing" to "Justice" would be a bad idea, but redirecting "Lockpicking" to "Pick locks" or "Combat maneuver list" to "Combat maneuvers" probably wouldn't be.
Line 67:		Line 67:
	* All log pages should begin with: This log is from the {storyline/event (page linked if applicable)} on {date} from the viewpoint of {character}.		* All log pages should begin with: This log is from the {storyline/event (page linked if applicable)} on {date} from the viewpoint of {character}.
	* Log page content can use headers to break up the length, have summaries, note characters involved, and otherwise be formatted however the poster would like. They can use the following code for consistency and ease of reading:<nowiki> <pre{{log2\|border=none\|font=arial}}> PASTE LOG HERE </pre> </nowiki>.		* Log page content can use headers to break up the length, have summaries, note characters involved, and otherwise be formatted however the poster would like. They can use the following code for consistency and ease of reading:<nowiki> <pre{{log2\|border=none\|font=arial}}> PASTE LOG HERE </pre> </nowiki>.
	* All logs should be categorized in <nowiki>[[Category: Logs]]</nowiki>. <section end=storylines />		* All logs should be categorized in <code><nowiki>[[Category: Logs]]</nowiki></code>. <section end=storylines />

	There are currently three different categories of logs with special rules for mainspace/subpage placement, categories, and article titles for the purposes of documenting events on the wiki: storyline logs, OOC meeting logs, and other logs.		There are currently three different categories of logs with special rules for mainspace/subpage placement, categories, and article titles for the purposes of documenting events on the wiki: storyline logs, OOC meeting logs, and other logs.
Line 76:		Line 76:
	It is on the contributor uploading the log to ensure the log is linked on the storyline catalog article space, and if done so, it must be under the <code><nowiki>Logs</nowiki></code> subheader. The storyline's category, as well as the log category, should be added to the log.		It is on the contributor uploading the log to ensure the log is linked on the storyline catalog article space, and if done so, it must be under the <code><nowiki>Logs</nowiki></code> subheader. The storyline's category, as well as the log category, should be added to the log.

	Storyline logs should additionally be categorized within the category or categories created specifically for that storyline. Only the storyline category, not the log, should be categorized into its relevant town storylines category (i.e. Wehnimer's Landing storylines), its relevant year (i.e. 2016 Storylines), and the <nowiki>[[Category: {Storyline}]]</nowiki> category.<section end=storylines2 />		Storyline logs should additionally be categorized within the category or categories created specifically for that storyline. Only the storyline category, not the log, should be categorized into its relevant town storylines category (i.e. Wehnimer's Landing storylines), its relevant year (i.e. 2016 Storylines), and the <code><nowiki>[[Category: {Storyline}]]</nowiki></code> category.<section end=storylines2 />

	====OOC Meeting Logs====		====OOC Meeting Logs====
Line 82:		Line 82:

	====Other Logs====		====Other Logs====
	Other log page titles should be formatted like this: [Event Title, if applicable] - [Date] - [Title of Log, if applicable] (log). For example: Mist Harbor Library Lectures - 2022-01-30 - Ivas Provides (log)		Other log page titles should be formatted like this: <code><nowiki>[Event Title, if applicable] - [Date] - [Title of Log, if applicable] (log)</nowiki></code>. For example: Mist Harbor Library Lectures - 2022-01-30 - Ivas Provides (log)

	===Research Pages===		===Research Pages===

MOD-GSMOTTE: /* Storyline Logs */ updated formatting

2023-06-18T18:44:57Z

Storyline Logs: updated formatting

← Older revision		Revision as of 13:44, 18 June 2023
Line 72:		Line 72:

	====Storyline Logs====		====Storyline Logs====
	<section begin=storylines2 />Storyline logs should be tied to the storyline first by name, then by date. This mirrors standards in place for handling other logs, except that these should be set up as subpages to the storyline redirect page. Page naming standard should be as follows:		<section begin=storylines2 />Storyline logs should be tied to the storyline first by name, then by date. This mirrors standards in place for handling other logs, except that these should be set up as subpages to the storyline redirect page. Page naming standard should be as follows: <code><nowiki>Storyline redirect page name (storyline)/[Date] - [Title of Log, if applicable] (log)</nowiki></code>
	: <code><nowiki>Storyline redirect page name (storyline)/[Date] - [Title of Log, if applicable] (log)</nowiki></code>

	It is on the contributor uploading the log to ensure the log is linked on the storyline catalog article space, and if done so, it must be under the <code><nowiki>Logs</nowiki></code> subheader. The storyline's category, as well as the log category, should be added to the log.		It is on the contributor uploading the log to ensure the log is linked on the storyline catalog article space, and if done so, it must be under the <code><nowiki>Logs</nowiki></code> subheader. The storyline's category, as well as the log category, should be added to the log.

MOD-GSMOTTE: /* Storyline Logs */ updated LST for better formatting.

2023-06-18T18:44:36Z

Storyline Logs: updated LST for better formatting.

← Older revision		Revision as of 13:44, 18 June 2023
Line 72:		Line 72:

	====Storyline Logs====		====Storyline Logs====
	<section begin=~~storylines~~ />Storyline logs should be tied to the storyline first by name, then by date. This mirrors standards in place for handling other logs, except that these should be set up as subpages to the storyline redirect page. Page naming standard should be as follows:		<section begin=storylines2 />Storyline logs should be tied to the storyline first by name, then by date. This mirrors standards in place for handling other logs, except that these should be set up as subpages to the storyline redirect page. Page naming standard should be as follows:
	: <code><nowiki>Storyline redirect page name (storyline)/[Date] - [Title of Log, if applicable] (log)</nowiki></code>		: <code><nowiki>Storyline redirect page name (storyline)/[Date] - [Title of Log, if applicable] (log)</nowiki></code>

	It is on the contributor uploading the log to ensure the log is linked on the storyline catalog article space, and if done so, it must be under the <code><nowiki>Logs</nowiki></code> subheader. The storyline's category, as well as the log category, should be added to the log.		It is on the contributor uploading the log to ensure the log is linked on the storyline catalog article space, and if done so, it must be under the <code><nowiki>Logs</nowiki></code> subheader. The storyline's category, as well as the log category, should be added to the log.

	Storyline logs should additionally be categorized within the category or categories created specifically for that storyline. Only the storyline category, not the log, should be categorized into its relevant town storylines category (i.e. Wehnimer's Landing storylines), its relevant year (i.e. 2016 Storylines), and the <nowiki>[[Category: {Storyline}]]</nowiki> category.<section end=~~storylines~~ />		Storyline logs should additionally be categorized within the category or categories created specifically for that storyline. Only the storyline category, not the log, should be categorized into its relevant town storylines category (i.e. Wehnimer's Landing storylines), its relevant year (i.e. 2016 Storylines), and the <nowiki>[[Category: {Storyline}]]</nowiki> category.<section end=storylines2 />

	====OOC Meeting Logs====		====OOC Meeting Logs====

MOD-GSMOTTE: Updating the logs section of the style guide.

2023-06-18T17:08:46Z

Updating the logs section of the style guide.

← Older revision		Revision as of 12:08, 18 June 2023
Line 61:		Line 61:

	===Logs===		===Logs===
			<section begin=storylines />'''Logs''' is the shorthand term for files containing a record of in-game events seen through the viewpoint of characters.
	''Please see [[Help:Storyline guidelines#Logs\|Storyline Guidelines Logs]] for information on how to handle naming of log pages for storylines.''

		⚫	* All log page titles should use the real year, not the Elanthian year, to help reduce confusion for other players. The content of log pages can reference either the real year or the Elanthian year.
	Formatting for log pages:
			* All log page title dates should be in the format YYYY-MM-DD.
		⚫	* All log pages should begin with: This log is from the {storyline/event (page linked if applicable)} on {date} from the viewpoint of {character}.
		⚫	* Log page content can use headers to break up the length, have summaries, note characters involved, and otherwise be formatted however the poster would like. They can use the following code for consistency and ease of reading:<nowiki> <pre{{log2\|border=none\|font=arial}}> PASTE LOG HERE </pre> </nowiki>.
			* All logs should be categorized in <nowiki>[[Category: Logs]]</nowiki>. <section end=storylines />

			There are currently three different categories of logs with special rules for mainspace/subpage placement, categories, and article titles for the purposes of documenting events on the wiki: storyline logs, OOC meeting logs, and other logs.
⚫	~~<section~~ ~~begin=logs />Log~~ page titles should be formatted like this: [~~Storyline or~~ Event Title, if applicable] - [Date] - [Title of Log, if applicable] (log). For example: ~~Blood~~ ~~Son~~ - ~~2020~~-01-01 - ~~Excitement in Wehnimer's~~ ~~Landing~~ (log)

			====Storyline Logs====
⚫	~~Log~~ page titles should use the real year ~~and~~ not the Elanthian year to help reduce confusion for other players. The content of log pages can reference either the real year or the Elanthian year.
			<section begin=storylines />Storyline logs should be tied to the storyline first by name, then by date. This mirrors standards in place for handling other logs, except that these should be set up as subpages to the storyline redirect page. Page naming standard should be as follows:
			: <code><nowiki>Storyline redirect page name (storyline)/[Date] - [Title of Log, if applicable] (log)</nowiki></code>

			It is on the contributor uploading the log to ensure the log is linked on the storyline catalog article space, and if done so, it must be under the <code><nowiki>Logs</nowiki></code> subheader. The storyline's category, as well as the log category, should be added to the log.
⚫	~~Log~~ pages should begin with: This log is from the {storyline/event (page linked if applicable)} on {date} from the viewpoint of {character}.

		⚫	Storyline logs should additionally be categorized within the category or categories created specifically for that storyline. Only the storyline category, not the log, should be categorized into its relevant town storylines category (i.e. Wehnimer's Landing storylines), its relevant year (i.e. 2016 Storylines), and the <nowiki>[[Category: {Storyline}]]</nowiki> category.<section end=storylines />
⚫	Log content can use headers to break up the length, have summaries, note characters involved, and otherwise be formatted however the poster would like. They can use the following code for consistency and ease of reading:<nowiki> <pre{{log2\|border=none\|font=arial}}> PASTE LOG HERE </pre> </nowiki>

			====OOC Meeting Logs====
⚫	~~All logs should be categorized in <nowiki>[[Category: Logs]]</nowiki>.~~ Storyline logs should additionally be categorized within the category or categories created specifically for that storyline. ~~The~~ storyline category, ~~but~~ not the log, should be categorized into its relevant town storylines category (i.e. Wehnimer's Landing ~~Storylines~~), its relevant year (i.e. 2016 Storylines), and the <nowiki>[[Category: {Storyline}]]</nowiki> category.<section end=~~logs~~ />
			Page naming standard should be as follows:: <code><nowiki>[Date] - [Town Name or Subscription Type] - [Title of Log, if applicable] (log)</nowiki></code>

			====Other Logs====
		⚫	Other log page titles should be formatted like this: [Event Title, if applicable] - [Date] - [Title of Log, if applicable] (log). For example: Mist Harbor Library Lectures - 2022-01-30 - Ivas Provides (log)

	===Research Pages===		===Research Pages===

GS4-XERAPHINA at 20:31, 28 March 2023

2023-03-28T20:31:16Z

← Older revision		Revision as of 15:31, 28 March 2023
Line 61:		Line 61:

	===Logs===		===Logs===
			''Please see [[Help:Storyline guidelines#Logs\|Storyline Guidelines Logs]] for information on how to handle naming of log pages for storylines.''

	Formatting for log pages:		Formatting for log pages:

HOST-GSKEBECHET: /* Logs */ Updated section on log titles for clarity. Log titles should use the real year, not the Elanthian year, to reduce confusion for other players.

2022-08-12T14:45:47Z

Logs: Updated section on log titles for clarity. Log titles should use the real year, not the Elanthian year, to reduce confusion for other players.

← Older revision		Revision as of 09:45, 12 August 2022
Line 64:		Line 64:

	<section begin=logs />Log page titles should be formatted like this: [Storyline or Event Title, if applicable] - [Date] - [Title of Log, if applicable] (log). For example: Blood Son - 2020-01-01 - Excitement in Wehnimer's Landing (log)		<section begin=logs />Log page titles should be formatted like this: [Storyline or Event Title, if applicable] - [Date] - [Title of Log, if applicable] (log). For example: Blood Son - 2020-01-01 - Excitement in Wehnimer's Landing (log)

			Log page titles should use the real year and not the Elanthian year to help reduce confusion for other players. The content of log pages can reference either the real year or the Elanthian year.

	Log pages should begin with: This log is from the {storyline/event (page linked if applicable)} on {date} from the viewpoint of {character}.		Log pages should begin with: This log is from the {storyline/event (page linked if applicable)} on {date} from the viewpoint of {character}.

GS4-XERAPHINA: /* Concept Pages */

2022-07-24T02:19:09Z

Concept Pages

← Older revision		Revision as of 21:19, 23 July 2022
Line 77:		Line 77:
	Moderation will be light on these pages.		Moderation will be light on these pages.

	===~~Concept~~ Pages===		===Proposal Pages===
	Pages containing proposals of any form that players have created can utiltize the ~~Concept~~ name space, and be named "~~Concept~~:{Proposal subject}". These pages will only be allowed in the [[:Category: Player proposals\|Player proposal category]]. Additionally, these pages are open to edits by any editor, but discussion is strongly advised to remain on the "Talk/Discussion" page before edits are made.		Pages containing proposals of any form that players have created can utiltize the Proposal name space, and be named "Proposal:{Proposal subject}". These pages will only be allowed in the [[:Category: Player proposals\|Player proposal category]]. Additionally, these pages are open to edits by any editor, but discussion is strongly advised to remain on the "Talk/Discussion" page before edits are made.

	Moderation will be light on these pages.		Moderation will be light on these pages.

GS4-XERAPHINA: added in basic guidelines to concept pages for player proposals

2022-07-22T14:44:54Z

added in basic guidelines to concept pages for player proposals

← Older revision		Revision as of 09:44, 22 July 2022
Line 74:		Line 74:

	Pages containing mechanical research data that is unconfirmed by GMs can be put on pages named "Research:{Research subject}". These pages will only be allowed in the [[:Category: Player Research\|Player Research category]], but can be linked from the subject's article page(s) in the Resources section.		Pages containing mechanical research data that is unconfirmed by GMs can be put on pages named "Research:{Research subject}". These pages will only be allowed in the [[:Category: Player Research\|Player Research category]], but can be linked from the subject's article page(s) in the Resources section.

			Moderation will be light on these pages.

			===Concept Pages===
			Pages containing proposals of any form that players have created can utiltize the Concept name space, and be named "Concept:{Proposal subject}". These pages will only be allowed in the [[:Category: Player proposals\|Player proposal category]]. Additionally, these pages are open to edits by any editor, but discussion is strongly advised to remain on the "Talk/Discussion" page before edits are made.

	Moderation will be light on these pages.		Moderation will be light on these pages.