User:Aprilbosworth

2008-10-16T03:12:00Z

Aprilbosworth:

By education, I am a technical writer. By employment a technical writer, instructional designer, and technology coordinator. I currently reside in North Carolina, USA and wrestle children full time. I am always looking for a way to clarify and condense the written word of technology.

User:Aprilbosworth

2008-10-16T03:10:46Z

Aprilbosworth: New page: By education, I am a technical writer. By employment a technical writer, instructional designer, and technology coordinator. I currently wrestle and chase children full time. I am always l...

By education, I am a technical writer. By employment a technical writer, instructional designer, and technology coordinator. I currently wrestle and chase children full time. I am always looking for a way to clarify and condense the written word of technology.

TechWiki talk:Guidelines

2008-10-16T03:02:25Z

Aprilbosworth: New page: <h3>Template:Need Input</h3> I just edited this explanation to eliminate the word "parameter" as it seems a little too much like jargon; however, now I'm thinking that the intent here is f...

<h3>Template:Need Input</h3> I just edited this explanation to eliminate the word "parameter" as it seems a little too much like jargon; however, now I'm thinking that the intent here is for programmers (developers? I'm not sure what the right term is) to be reading these guidelines, then perhaps "parameter" is a clear, meaningful word for them. If it is jargon, then the rest of the template section should be written to get rid of it too.

TechWiki:Guidelines

2008-10-16T02:53:05Z

Aprilbosworth: /* Template:Need Input */

{{Draft|Needs review and approval}}
These '''guidelines''' will create consistency for additions and corrections to the LDS Tech wiki.

== Creating New Articles ==
An '''article''' in this wiki should be similar to an encylopedia article. It should cover a single topic, and should stand on its own (although it may and generally should link to other articles). Topics may be very broad, or quite specific.

=== Article Title ===
The '''title''' of the article should be chosen carefully. It should describe the content well, and be a term that others would naturally apply to this content. A user of the wiki can type a title in the '''search box''' of the wiki and click '''Go''' (or press '''Enter''') and go directly to an article if an article with that title exists.

=== Before creating a page ===
Before you create a new page, make sure that
* The content is not already covered on another page
* The content is appropriate to the LDS Tech wiki
* You have chosen an appropriate title

== Editing Pages ==
The content of the wiki makes progress because many users make contributions, from making simple spelling corrections to adding new articles. Be bold so that you move the project forward, but don't be hasty -- sloppy edits will just create more work for others and lower the quality of the wiki.

=== Use Preview ===
Before you click '''Save page''' to save your changes, use the '''Show preview''' button to see how your changes will actually appear. This can help save you from posting content with obvious errors.

=== Make changes at one time ===
Use the preview button liberally as you are creating a page or making edits. Whenever possible, make all your changes to a page in a single session. If you save the page often, you will needlessly clutter the history of the page and fill up the '''recent changes''' log with many entries. This makes it more difficult for other users to discover what has actually changed.

=== Headings ===
The MediaWiki style guide suggests avoiding H1 level headings (i.e. <code>= This is an Incorrect Article Heading =</code>) in your articles, as those type of headings are used for the article titles. We prefer all article sub-headings to begin with H2 level headings (i.e. <code>== This is a Correct Article Heading ==</code>) and then go downwards from there.

=== Style Guide ===
For consistent usage and/or presentation of common words and concepts, a [[LDS Tech Style Guide|style guide]] will be written. Please refer to the style guide frequently when creating or editing a page. For more information on style guides, see [http://en.wikipedia.org/wiki/Style_guide Wikipedia's entry on style guides].

== Discussion Pages ==
Each article has a '''discussion page''' or '''talk page'''. These pages provide a forum for the community to come to a consensus as to the direction a particular article should take. If there is anything at all controversial about a change you have made or think ought to be made, start a discussion using the discussion pages.

You should '''never''' put discussion, questions, or comments in the body of articles. Discussion should be limited to the discussion page.

=== Topics ===
Discussion pages can be organized into topics. This is particularly helpful for articles that have multiple sections and thus may have ongoing discussion related to different sections.

If you are responding to a particular question, use one or more colons to indent your response so that it is clear what comment or question you are responding to.

=== Sign your name ===
You can easily sign your name by adding four tildes to the end of your comment. This will add your username and a time stamp. You can use three tildes for just your name or five tildes for just the timestamp, but the preferred signature uses four tildes to include both. The appearance of your username is determined by the preferences you have set. Comments in discussion pages should always be signed, but signatures should not be placed in articles.

== Use Templates to Flag questionable or incomplete content ==
If you come across an article that needs to be edited or should be deleted, you can flag the article by inserting a template. To do this, simply edit the article and insert the text '''<nowiki>{{Template_Name|Parameter}}</nowiki>'''. The parameters for a template are documented on the template page, which you can examine by going to the appropriate template page: '''<nowiki>Template:Template_Name</nowiki>'''.

=== Template:Edit ===
Use the {{tl|Edit}} template if you find a page that requires editing, but you don't have the time or skill to edit it. This template may be inserted at the top of the page if it applies to the entire page, or at the beginning of a section if it only applies to that section. It has a parameter that is a brief description of what needs to be corrected. For example, the annotation
<pre>{{Edit|Eliminate first person from this section}}</pre>
would result in a box appearing in the text as follows:
{{Edit|Eliminate first person from this section|category=}}

=== Template:Draft ===
Use the {{tl|Draft}} template for policy or guideline pages that are in a draft stage. This template should be inserted at the top of the page. It has a parameter that is a brief description of the reason for the draft status. For example, the annotation
<pre>{{Draft|Waiting for approval from Tom Welch}}</pre>
would result in a box appearing in the text as follows:
{{Draft|Waiting for approval from Tom Welch|category=}}

=== Template:Need Input ===
Use the {{tl|Need Input}} template when a particular issue in an article or discussion requires additional information, clarification, or collaboration. Indicate what is needed with a brief description of the issue or ask a question. For example, the annotation
<pre>{{Need Input|Should Bishops be able to assign responsibility for a household to a quorum?}}</pre>
would result in a box appearing in the text as follows:
{{Need Input|Should Bishops be able to assign responsibility for a household to a quorum?|category=}}

=== Template:Unresolved ===
Use the {{tl|Unresolved}} template for marking a question or concern as currently unresolved in discussions on Talk Pages. This template should be inserted at the top of an unresolved discussion. It has a parameter that is a brief description of the issue. For example, the annotation
<pre>{{Unresolved|This database architecture is too complicated}}</pre>
would result in a box appearing in the text as follows:
{{Unresolved|This database architecture is too complicated|category=}}

=== Template:Resolved ===
Use the {{tl|Resolved}} template for marking a question or concern as resolved in discussions on Talk Pages. This template should be inserted at the top of a resolved discussion. It has a parameter that is a brief summary of the resolution and resultant action. For example, the annotation
<pre>{{Resolved|Added to the Use Cases}}</pre>
would result in a box appearing in the text as follows:
{{Resolved|Added to the Use Cases|category=}}

=== Template:Stub ===
Use the {{tl|Stub}} template to indicate that an article is only a stub and needs to be fleshed out. This template takes no parameter, and appears as:
{{stub}}

=== Template:ToDo ===
Use the {{tl|ToDo}} template to indicate tasks that need to be performed on an article. It has a parameter that is a brief summary of the tasks requiring action. For example, the annotation
<pre>{{ToDo|Create a detailed instructions page to show how to configure this application}}</pre>
would result in a box appearing in the text as follows:
{{ToDo|Create a detailed instructions page to show how to configure this application|category=}}

== Add Sources ==
Although opinions and personal ideas can be helpful, statements purported to be official Church policy will be more effective if backed up by an [[Official Sources|official source]].

[[Category:Help]]

TechWiki - User contributions [en]

User:Aprilbosworth

User:Aprilbosworth

TechWiki talk:Guidelines

TechWiki:Guidelines