Style Guide - Revision history

Gwyneth Llewelyn: /* Videos */ Added a temporary warning that currently embedding video using Flash is not possible, because Flash is obsolete.

2022-09-14T16:45:06Z

Videos: Added a temporary warning that currently embedding video using Flash is not possible, because Flash is obsolete.

← Older revision		Revision as of 09:45, 14 September 2022
Line 519:		Line 519:

	We standardized on [http://vimeo.com/torley/videos Vimeo for Torley's official video tutorials which you can search through], or "vidtuts" for short. (We also have an alternative [http://www.mediawiki.org/wiki/Extension:Widgets Widgets] extension, but it conflicts with FlaggedRevs, so ''don't'' use it for videos on official Knowledge Base articles.)		We standardized on [http://vimeo.com/torley/videos Vimeo for Torley's official video tutorials which you can search through], or "vidtuts" for short. (We also have an alternative [http://www.mediawiki.org/wiki/Extension:Widgets Widgets] extension, but it conflicts with FlaggedRevs, so ''don't'' use it for videos on official Knowledge Base articles.)

			{{KBwarning\|Flash was discontinued in the 2020s, meaning that currently there is no easy way to embed videos on the SL Wiki. This has been reported to Linden Lab and we await a solution.}}

	=== Navigation Templates ===		=== Navigation Templates ===

Chaser Zaks: /* Files, paths, URLs, code, and other typed user input */

2017-06-27T15:47:22Z

Files, paths, URLs, code, and other typed user input

← Older revision	Revision as of 08:47, 27 June 2017
(No difference)

Chaser Zaks: /* Files, paths, URLs, code, and other typed user input */

2017-06-27T15:47:08Z

Files, paths, URLs, code, and other typed user input

← Older revision		Revision as of 08:47, 27 June 2017
Line 320:		Line 320:
	For multi-line code samples, use the [[Syntax Highlighting Examples\|syntax highlighting extension]]; for example:		For multi-line code samples, use the [[Syntax Highlighting Examples\|syntax highlighting extension]]; for example:

	<python> # Hello World in Python		<syntaxhighlight lang="python"> # Hello World in Python

	def main():		def main():
Line 326:		Line 326:

	if __name__ == '__main__':		if __name__ == '__main__':
	main()</~~python~~>		main()</syntaxhighlight>

	=== Tables ===		=== Tables ===

Lady Sumoku: Corrected typo in link description

2015-10-27T19:01:46Z

Corrected typo in link description

← Older revision		Revision as of 12:01, 27 October 2015
Line 1:		Line 1:
	{{KBtip\|While you aren't required to follow this Style Guide to make unofficial Wiki pages, it may help you be a more effective writer, so feel free to adopt these practices!}} {{TOCright}}{{otheruses4\|style used in English articles}}		{{KBtip\|While you aren't required to follow this Style Guide to make unofficial Wiki pages, it may help you be a more effective writer, so feel free to adopt these practices!}} {{TOCright}}{{otheruses4\|style used in English articles}}

	'''Interested in [[Extended Knowledge Base\|contributing to Extended ~~the~~ Knowledge Base]]? Please read this style guide to gain a better understanding of the framework we're using to craft beautiful documents which aren't just well-written, but easy-to-read.'''		'''Interested in [[Extended Knowledge Base\|contributing to the Extended Knowledge Base]]? Please read this style guide to gain a better understanding of the framework we're using to craft beautiful documents which aren't just well-written, but easy-to-read.'''

	Our style guide is inspired by successful common conventions such as [http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia]'s, blended with specifics about the Second Life® experience. This guide is open to evolving over time, yet aims to provide consistency you can refer to when in doubt.		Our style guide is inspired by successful common conventions such as [http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia]'s, blended with specifics about the Second Life® experience. This guide is open to evolving over time, yet aims to provide consistency you can refer to when in doubt.

Gianinni Babenco: + Extended

2011-11-11T16:31:48Z

+ Extended

← Older revision		Revision as of 09:31, 11 November 2011
Line 1:		Line 1:
	{{KBtip\|While you aren't required to follow this Style Guide to make unofficial Wiki pages, it may help you be a more effective writer, so feel free to adopt these practices!}} {{TOCright}}{{otheruses4\|style used in English articles}}		{{KBtip\|While you aren't required to follow this Style Guide to make unofficial Wiki pages, it may help you be a more effective writer, so feel free to adopt these practices!}} {{TOCright}}{{otheruses4\|style used in English articles}}

	'''Interested in [[Extended Knowledge Base\|contributing to the Knowledge Base]]? Please read this style guide to gain a better understanding of the framework we're using to craft beautiful documents which aren't just well-written, but easy-to-read.'''		'''Interested in [[Extended Knowledge Base\|contributing to Extended the Knowledge Base]]? Please read this style guide to gain a better understanding of the framework we're using to craft beautiful documents which aren't just well-written, but easy-to-read.'''

	Our style guide is inspired by successful common conventions such as [http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia]'s, blended with specifics about the Second Life® experience. This guide is open to evolving over time, yet aims to provide consistency you can refer to when in doubt.		Our style guide is inspired by successful common conventions such as [http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia]'s, blended with specifics about the Second Life® experience. This guide is open to evolving over time, yet aims to provide consistency you can refer to when in doubt.

Gianinni Babenco: Atualizando - Extended Knowledge Base

2011-11-10T23:11:42Z

Atualizando - Extended Knowledge Base

← Older revision		Revision as of 16:11, 10 November 2011
Line 1:		Line 1:
	{{KBtip\|While you aren't required to follow this Style Guide to make unofficial Wiki pages, it may help you be a more effective writer, so feel free to adopt these practices!}} {{TOCright}}{{otheruses4\|style used in English articles}}		{{KBtip\|While you aren't required to follow this Style Guide to make unofficial Wiki pages, it may help you be a more effective writer, so feel free to adopt these practices!}} {{TOCright}}{{otheruses4\|style used in English articles}}

	'''Interested in [[~~KB2Wiki~~\|contributing to the Knowledge Base]]? Please read this style guide to gain a better understanding of the framework we're using to craft beautiful documents which aren't just well-written, but easy-to-read.'''		'''Interested in [[Extended Knowledge Base\|contributing to the Knowledge Base]]? Please read this style guide to gain a better understanding of the framework we're using to craft beautiful documents which aren't just well-written, but easy-to-read.'''

	Our style guide is inspired by successful common conventions such as [http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia]'s, blended with specifics about the Second Life® experience. This guide is open to evolving over time, yet aims to provide consistency you can refer to when in doubt.		Our style guide is inspired by successful common conventions such as [http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia]'s, blended with specifics about the Second Life® experience. This guide is open to evolving over time, yet aims to provide consistency you can refer to when in doubt.

Gianinni Babenco: /* Warnings, notes, tips, and other templates */ Correção.

2011-08-21T22:27:10Z

Warnings, notes, tips, and other templates: Correção.

← Older revision		Revision as of 15:27, 21 August 2011
Line 394:		Line 394:
	\|-		\|-
	\| '''[[Template:KBwarning]]'''		\| '''[[Template:KBwarning]]'''
	\| <code><nowiki>{{~~KBWarning~~\|Foo}}</nowiki></code>		\| <code><nowiki>{{KBwarning\|Foo}}</nowiki></code>
	\| A strong notice of what NOT to do, and if applicable, the consequences, including something that can cause harm or damage.		\| A strong notice of what NOT to do, and if applicable, the consequences, including something that can cause harm or damage.
	\| {{KBwarning\|Foo}}		\| {{KBwarning\|Foo}}
Line 400:		Line 400:
	\|-		\|-
	\| '''[[Template:KBcaution]]'''		\| '''[[Template:KBcaution]]'''
	\| <code><nowiki>{{~~KBCaution~~\|Foo}}</nowiki></code>		\| <code><nowiki>{{KBcaution\|Foo}}</nowiki></code>
	\| An important notice of what NEEDS to or SHOULD be done — basically, the opposite of KBwarning.		\| An important notice of what NEEDS to or SHOULD be done — basically, the opposite of KBwarning.
	\| {{KBcaution\|Foo}}		\| {{KBcaution\|Foo}}

Boston Linden: /* Numbered lists */

2011-04-19T14:28:21Z

Numbered lists

← Older revision		Revision as of 07:28, 19 April 2011
Line 291:		Line 291:
	# Read the Messsage of the Day.		# Read the Messsage of the Day.
	# Smile!		# Smile!

			In general, each item or instruction in a numbered list should be a complete sentence and should be punctuated accordingly — that is, with a period, an exclamation point or (in rare cases) a question mark.

	==== Unordered lists ====		==== Unordered lists ====

Boston Linden: /* What to capitalize */

2011-04-18T18:43:16Z

What to capitalize

← Older revision		Revision as of 11:43, 18 April 2011
Line 179:		Line 179:
	* Linden Dollar		* Linden Dollar
	* Resident or Residents, when referring to the Second Life community members.		* Resident or Residents, when referring to the Second Life community members.
	* Region (when referring to a Second Life Region), Homestead Region, Openspace Region.		* Region (when referring to a Second Life Region), Private Region, Homestead Region, Openspace Region.

	* Second Life Region names, for example:		* Second Life Region names, for example:

Boston Linden: /* Style */

2011-04-15T17:35:10Z

Style

← Older revision		Revision as of 10:35, 15 April 2011
Line 541:		Line 541:

	* Article titles in a navigation template should always be presented as a '''bullet list'''.		* Article titles in a navigation template should always be presented as a '''bullet list'''.
	* Always use each article's '''full title'''. This is for the purpose of standardization and navigational clarity; an article's title is its unique identifier. We understand that some article titles are exceptionally long, and are currently considering options to universally shorten and standardize Knowledge Base article titles.		* Always use each article's '''full title'''. This is for the purpose of standardization and navigational clarity; an article's title is its unique identifier. We understand that some article titles are exceptionally long, and we are currently considering options to universally shorten and standardize Knowledge Base article titles.
	* Avoid unuseful font styles (bold, italic, etc) in article titles or the navbox title.		* Avoid unuseful font styles (bold, italic, etc) in article titles or the navbox title.