TechWiki - User contributions [en]

User:Mkmurray

2012-10-31T19:45:18Z

Mkmurray: Mike Murray profile edit

==Mike Murray==
[[image:mkmurray.jpg | right | border]]
'''Community Administrator'''<br>
LDS Tech Forums<br>
<br>
{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Email || [mailto:charliebrown928@hotmail.com charliebrown928@hotmail.com]
|-
| AIM || miguelito928
|-
| Google Talk || charliebrown928@gmail.com
|-
| MSN || charliebrown928@hotmail.com
|-
| Skype || miguelito928
|}
<br>
'''Location:'''<br>
Utah<br>
'''Interests:'''<br>
Microsoft development environments and technologies; software development best practices and methodologies<br>
'''Occupation:'''<br>
Software Engineer<br>
'''Blog:'''<br>
[http://mkmurray.com/ http://mkmurray.com/]<br>
'''Twitter:'''<br>
[http://twitter.com/mkmurray mkmurray]<br>
'''LDSTech Forums Profile:'''<br>
[http://tech.lds.org/forum/member.php?u=219 mkmurray]

User:Mkmurray

2012-04-28T06:24:31Z

Mkmurray:

==Mike Murray==
[[image:mkmurray.jpg | right | border]]
'''Community Administrator'''<br>
LDS Tech Forums<br>
<br>
{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Email || [mailto:charliebrown928@hotmail.com charliebrown928@hotmail.com]
|-
| AIM || miguelito928
|-
| Google Talk || charliebrown928@gmail.com
|-
| MSN || charliebrown928@hotmail.com
|-
| Skype || miguelito928
|}
<br>
'''Location:'''<br>
Utah<br>
'''Interests:'''<br>
Microsoft development environments and technologies; software development best practices and methodologies<br>
'''Occupation:'''<br>
Software Engineer<br>
'''Blog:'''<br>
[http://MurrayOn.NET/ http://MurrayOn.NET/]<br>
[http://mkmurray.com/ http://mkmurray.com/]<br>
'''Twitter:'''<br>
[http://twitter.com/mkmurray mkmurray]<br>
'''LDSTech Forums Profile:'''<br>
[http://tech.lds.org/forum/member.php?u=219 mkmurray]

File:Mkmurray.jpg

2012-04-28T06:24:07Z

Mkmurray: Image for mkmurray's profile

Image for mkmurray's profile

User:Mkmurray

2012-04-28T06:06:52Z

Mkmurray:

==Mike Murray==
[[image:mkmurray.png | right | border]]
'''Community Administrator'''<br>
LDS Tech Forums<br>
<br>
{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Email || [mailto:charliebrown928@hotmail.com charliebrown928@hotmail.com]
|-
| AIM || miguelito928
|-
| Google Talk || charliebrown928@gmail.com
|-
| MSN || charliebrown928@hotmail.com
|-
| Skype || miguelito928
|}
<br>
'''Location:'''<br>
Utah<br>
'''Interests:'''<br>
Microsoft development environments and technologies; software development best practices and methodologies<br>
'''Occupation:'''<br>
Software Engineer<br>
'''Blog:'''<br>
[http://MurrayOn.NET/ http://MurrayOn.NET/]<br>
[http://mkmurray.com/ http://mkmurray.com/]<br>
'''Twitter:'''<br>
[http://twitter.com/mkmurray mkmurray]<br>
'''LDSTech Forums Profile:'''<br>
[http://tech.lds.org/forum/member.php?u=219 mkmurray]

User:Mkmurray

2010-02-23T05:09:41Z

Mkmurray:

==Mike Murray==
[[image:mkmurray.png | right | border]]
'''Community Administrator'''<br>
LDS Tech Forums<br>
<br>
{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Email || [mailto:charliebrown928@hotmail.com charliebrown928@hotmail.com]
|-
| AIM || miguelito928
|-
| Google Talk || charliebrown928@gmail.com
|-
| MSN || charliebrown928@hotmail.com
|-
| Skype || miguelito928
|}
<br>
'''Location:'''<br>
Utah<br>
'''Interests:'''<br>
Microsoft development environments and technologies; software development best practices and methodologies<br>
'''Occupation:'''<br>
Software Engineer<br>
'''Blog:'''<br>
[http://MurrayOn.NET/ http://MurrayOn.NET/]<br>
'''Twitter:'''<br>
[http://twitter.com/murrayondotnet murrayondotnet]<br>
'''LDSTech Forums Profile:'''<br>
[http://tech.lds.org/forum/member.php?u=219 mkmurray]

User:Mkmurray

2010-02-23T05:09:16Z

Mkmurray:

==Mike Murray==
[[image:mkmurray.png | right | border]]
'''Community Administrator'''<br>
LDS Tech Forums<br>
<br>
{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Email || [mailto:charliebrown928@hotmail.com charliebrown928@hotmail.com]
|-
| AIM || miguelito928
|-
| Google Talk || charliebrown928@gmail.com
|-
| MSN || charliebrown928@hotmail.com
|-
| Skype || miguelito928
|}
<br>
'''Location:'''<br>
Pleasant Grove, UT<br>
'''Interests:'''<br>
Microsoft development environments and technologies; software development best practices and methodologies<br>
'''Occupation:'''<br>
Software Engineer<br>
'''Blog:'''<br>
[http://MurrayOn.NET/ http://MurrayOn.NET/]<br>
'''Twitter:'''<br>
[http://twitter.com/murrayondotnet murrayondotnet]<br>
'''LDSTech Forums Profile:'''<br>
[http://tech.lds.org/forum/member.php?u=219 mkmurray]

User:Mkmurray

2010-02-23T05:07:14Z

Mkmurray: update some profile links and contact info

==Mike Murray==
[[image:mkmurray.png | right | border]]
'''Community Administrator'''<br>
LDS Tech Forums<br>
<br>
{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Email || [mailto:charliebrown928@hotmail.com charliebrown928@hotmail.com]
|-
| AIM || miguelito928
|-
| Google Talk || charliebrown928@gmail.com
|-
| MSN || charliebrown928@hotmail.com
|-
| Skype || miguelito928
|}
<br>
'''Location:'''<br>
Pleasant Grove, UT<br>
'''Interests:'''<br>
Microsoft development environments and technologies<br>
'''Occupation:'''<br>
Software Engineer for consulting firm Knowlysis, LLC<br>
'''Blog:'''<br>
[http://MurrayOn.NET/ http://MurrayOn.NET/]<br>
'''Twitter:'''<br>
[http://twitter.com/murrayondotnet murrayondotnet]<br>
'''LDSTech Forums Profile:'''<br>
[http://tech.lds.org/forum/member.php?u=219 mkmurray]

Main Page

2010-01-19T19:35:06Z

Mkmurray:

<div style="margin: 10px 0px 0px 0px;">
<div style="background-color: #f2f3e5; text-align: center;">
==Welcome to the LDSTech Wiki==
</div>
The purpose of this wiki is for the Church and community members to collaborate on various documents and technology projects sponsored by the Church. We invite all to participate. '''New users''', please review the [[Requirements for Participation]] and [[Guidelines|Wiki Guidelines]] pages.
<table width="100%" cellspacing="10" cellpadding="0">
<tr valign="top">
<td width="50%">
<div style="margin: 0px 5px 0px 0px; border: 1px solid #afa3bf;">
<div style="background-color: #ddcef2; text-align: center;">

=== Project Wiki Menu ===
</div> 
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #ddcef2; padding-left: 10px; ">

=====Announcements=====
</div>
* [[file:New.gif]][[Subversion Change to Dev | Subversion has changed locations]]
* [[General_Announcements#Moving_to_HTTPS_for_key_tools | Change in our URLs]]
* [[General_Announcements#First_Java_Stack_Documentation | LDS Java Stack Documentation]]
* [[General_Announcements#Where_is_Subversion | Subversion URL]]
* [[General_Announcements#Syntax_Highlighting | Syntax Code Highlighting in Wiki]]
</td>

<td><div style="background-color: #ddcef2; padding-left: 10px; ">

=====Participation & Current Needs=====
</div>
* [[LDSTech:About | New to the LDSTech Wiki?]]
* [[Requirements for Participation | Requirements for Participation]]
* [http://www.mediawiki.org/wiki/Help:Formatting Help with Formatting Documents]
* [[Current Needs]]
* [[Getting Involved with Projects | How to get involved]]
* [[Community Development Best Practices | Dev Best Practices]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #ddcef2; padding-left: 10px; ">

===== Current Projects =====
</div>
* [[Home Teaching / Visiting Teaching Application | Home Teaching / Visiting Teaching Application]]
* [[Local Unit Website Project | Local Unit Website Project]]
* [[Mormon Channel | Mormon Channel Mobile Applications]]
* [[:Category:Scriptures Application|Mobile Scriptures Applications]]
* [[:Category:Projects|more...]]
</td>
<td><div style="background-color: #ddcef2; padding-left: 10px; ">

===== Feedback & Suggestions =====
</div>
* [[MLS:_Feedback_and_Suggestions | MLS (Member and Leader Services)]]
* [[LUWS:_Feedback_and_Suggestions | LUWS (Local Unit Web Sites)]]
* [[Online_Scriptures:_Feedback_and_Suggestions | Online Scriptures]]
</td>
</tr>

<tr>
<td><div style="background-color: #ddcef2; padding-left: 10px; ">
===== Internet & Family Safety =====
</div>
* [[Internet (Family Safety) | Internet Safety]]
* [[Cell Phones (Family_Safety) | Cell Phone Safety]]
* [[Family Safety | more...]]
</td>
</tr>

</table>
</div> 
</td>
<td>
<div style="margin: 0px 0px 0px 10px; border: 1px solid #a3b0bf;">
<div style="background-color: #cedff2; text-align: center;">

=== Clerk Wiki Menu ===
</div>
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #cedff2; padding-left: 10px; ">
=====General=====
</div>
* [[Clerks Overview|Overview]]
* [[Stake Clerk]] / [[Ward Clerk]]
* [[MLS]]
* [[Letters and policies archive]]
* [[Glossary]]
* '''[[Tip of the Week]]!'''
</td>
<td><div style="background-color: #cedff2; padding-left: 10px; ">
=====Financial=====
</div>
* [[Financial Clerk]]
* [[Financial Audit]]
* [[Reconciliation]]
* [[:Category:Finance|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #cedff2; padding-left: 10px; ">
===== Membership =====
</div>
* [[Membership Clerk]]
* [[Membership Records]]
* [[Recording Ordinances]]
* [[Membership Audit]]
* [[:Category:Membership|more...]]
</td>
<td><div style="background-color: #cedff2; padding-left: 10px; ">
===== Statistical =====
</div>
* [[Statistical Clerk]]
* [[Statistical Reporting]]
* [[Quarterly Report]]
* [[Annual History]]
* [[:Category:Statistical|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #cedff2; padding-left: 10px; ">
===== Technology =====
</div>
* [[Stake Technology Specialist]]
* [[Meetinghouse Internet]]
* [[Meetinghouse Webcast]]
* [[Satellite Broadcasts]]
* [[Local Unit Website]]
* [[:Category:Technology|more...]]
</td>
<td><div style="background-color: #cedff2; padding-left: 10px; ">
=====Unit Administration=====
</div>
* [[:Category:Roles|Roles]]
* [[CDOL]]
* [[Maps and Boundaries]]
* [[Meetinghouse Locator]]
* [[Training]]
* [[:Category:Unit Administration|more...]]
</td>
</tr>
<tr>
<td colspan="2">
{{Box
| title=Acknowledgement
| color=blue
| content=For many years [[User:Kslarsena|Kent S. Larsen]] of New York, New York, has personally funded and maintained a mailing list, discussion forum, and (more recently) a wiki for [[LDSClerks|LDS clerks]]. The administrators of the LDSTech wiki wish to thank this pioneer of clerk training and the other long-time contributors to his site for generously donating all of the contents of their wiki (more than 100 pages of information) to the new LDSTech wiki. This contribution is a great blessing to clerks around the world, allowing the new site to “go live” overnight.
}}
</td>
</tr>
</table>
</div>
</td>
</tr>
</table>
__NOTOC__
__NOEDITSECTION__

Template:TechForum

2009-12-01T19:52:17Z

Mkmurray: add the word "the" to template in several branches

<includeonly>{{#if: {{{post|}}} | [http://tech.lds.org/forum/showthread.php?p={{{post}}}#post{{{post}}} {{#if: {{{title|}}} | ''{{{title}}}'' |}} Post] on the | {{#if: {{{spost|}}} | [http://tech.lds.org/forum/showpost.php?p={{{spost}}} {{#if: {{{title|}}} | ''{{{title}}}'' |}} Post] on the | {{#if: {{{thread|}}} | [http://tech.lds.org/forum/showthread.php?t={{{thread}}} {{#if: {{{title|}}} | ''{{{title}}}'' |}} Thread] on the | {{#if: {{{forum|}}} | [http://tech.lds.org/forum/forumdisplay.php?f={{{forum}}} {{#switch: {{{forum}}}
| 3 = ''What's New''
| 4 = ''Announcements & Policies''
| 13 = ''Community Discussions''
| 14 = ''General Discussions''
| 15 = ''Ideas & Suggestions''
| 16 = ''Links & Resources''
| 17 = ''In The News''
| 18 = ''Current and Future Church Technologies''
| 21 = ''MLS Support, Help, and Feedback ''
| 22 = ''Help & Feedback''
| 23 = ''Getting Help''
| 24 = ''Feedback''
| 27 = ''Building-to-Building Communications''
| 34 = ''LDSTech Featured Article Discussions''
| 36 = ''Development Help Wanted''
| 38 = ''Technical Recruiting''
| 42 = ''Clerks and Technology Support''
| 43 = ''Getting Started for New Clerks''
| 45 = ''Reports and Forms''
| 46 = ''Local Unit Finance''
| 47 = ''Membership Help''
| 48 = ''Computers, Printers, Networking, and Electronics''
| 49 = ''Other Technologies''
| 50 = ''General Clerks Discussion''
| 51 = ''Meetinghouse Internet''
| 86 = ''FAQs for Local Unit Copier Program''
| 87 = ''Local Unit Copiers & MFPs''
| #default =
}} Forum] on the }} }} }} }} [http://tech.lds.org LDSTech] [http://tech.lds.org/forum Discussion Forum]</includeonly><noinclude>
== Purpose ==
This template is used to easily reference items on the [http://tech.lds.org LDS Technology Web Site] forums.

== Usage ==
This template can take one of four optional parameters (or no parameter) for creating a reference link to an item in the forums:
* '''forum''': the ID of a forum
* '''thread''': the ID of a thread
* '''post''': the ID of a post within a thread
* '''spost''': the ID of a post in single post view

This template can also take another optional parameter that allows you to add a title to the generated link:
* '''title''': the title of the post or thread

=== Examples ===
{| border="1" cellpadding="3" cellspacing="0"
!style="width:50px;" | Type
!style="width:80px;" | Usage
!style="width:200px;" | Result
|-
| forum
| <pre>{{LDSTech|forum=50}}</pre>
| {{LDSTech|forum=50}}
|-
| thread
| <pre>{{LDSTech|thread=1438}}</pre>
| {{LDSTech
|thread=1438
}}
|-
| post
| <pre>{{LDSTech
|post=13222
|title=Wiki LDSClerks.com Status 18 June 2008
}}</pre>
| {{LDSTech
|post=13222
|title=Wiki LDSClerks.com Status 18 June 2008
}}
|-
| spost
| <pre>{{LDSTech
|spost=13222
|title=Wiki LDSClerks.com Status 18 June 2008
}}</pre>
| {{LDSTech
|spost=13222
|title=Wiki LDSClerks.com Status 18 June 2008
}}
|-
| (none)
| <pre>{{LDSTech}}</pre>
| {{LDSTech}}
|}

[[Category:Templates|LDSTech]]
</noinclude>

TechWiki:New wiki content requests

2009-09-19T17:23:01Z

Mkmurray: /* New clerk content */

Anyone can add to this page any '''requests for new content''' on the LDSTech wiki. This wiki is always a work in progress. Sometimes contributors will notice that something is missing, or think of a new topic that would be very helpful. This page provides a place to quickly capture those ideas, especially when the person with the idea can't make the changes personally for any reason.

People who have time and expertise to contribute content are welcome to come here and help fulfill some of these requests. Once a topic has been added to the wiki, it should be removed from this page.

Feel free to discuss the merits of any of these suggestions on the [[LDSTech_talk:New Content Requests|discussion page]].

== New clerk content ==
Add bullet points below regarding new topics that should be added to the wiki.

* [[Home Teaching]] and [[Visiting Teaching]] articles (perhaps combine both into one article).
* [[Language]] issues in MLS: [[Changing the Language Setting in MLS]] explains how to run MLS in a different language, but we should also explain how to print forms and certificates in a different language (without changing the MLS language). This could go in that same article (but broaden the title), or in a separate article.
* [[Local Unit Website]]: Break this article into a user-oriented page and an administrator page. The administration page could then spawn additional detailed articles. For example, resource scheduling could be its own topic, as well as [http://tech.lds.org/forum/showthread.php?t=3105 How to get members to use LUWS].
* [[Stake President]] and [[Bishop]] currently redirect to [[Leaders' responsibilities for record keeping]]. But there have been discussions on LDSTech forums such as [http://tech.lds.org/forum/showthread.php?t=1244 New Stake Presidency] about what clerks need to do, especially in the technology realm, to help get new stake presidencies and bishops acquainted with Church systems and get the proper access. This would apply to new clerks as well. It would be helpful to capture this "getting started" information.
* [[Members without callings]]: This MLS report has several options, and how to use it is not clear to all clerks. See {{LDSTech|thread=3690|title=Members Without Callings List}}.
* [[Escheating checks]]: This existing article should explain what happens after a check has been submitted on the Outstanding Checks form -- how long does it take to process, what will show up on a CUFS, what the clerk does in MLS to clear it out. See {{LDSTech|thread=3749|title=Old Uncleared checks}}.
* [[Custom Reports]]: Now that the wiki allows upload of the ''.mls'' file type, create and upload some helpful custom reports definition files that clerks can download and import into their unit's MLS.

== New projects ==
* [[iPhone App]] for Ward Directory and Calendar.

== New wiki features ==
Add bullet points below regarding changes to the structure of the wiki, or guidelines or procedures, such as templates or categories.

* Add template for references to the CHI

== Other ==
Add bullet points below for any other suggestions that do not fit the above topics.

[[Category:LDSTech Administration|New Content Requests]]

TechWiki:New wiki content requests

2009-09-19T17:22:32Z

Mkmurray: /* New clerk content */ Add suggestion

Anyone can add to this page any '''requests for new content''' on the LDSTech wiki. This wiki is always a work in progress. Sometimes contributors will notice that something is missing, or think of a new topic that would be very helpful. This page provides a place to quickly capture those ideas, especially when the person with the idea can't make the changes personally for any reason.

People who have time and expertise to contribute content are welcome to come here and help fulfill some of these requests. Once a topic has been added to the wiki, it should be removed from this page.

Feel free to discuss the merits of any of these suggestions on the [[LDSTech_talk:New Content Requests|discussion page]].

== New clerk content ==
Add bullet points below regarding new topics that should be added to the wiki.

* [[Home Teaching]] and [[Visiting Teaching]] articles (perhaps combine both into one article).
* [[Language]] issues in MLS: [[Changing the Language Setting in MLS]] explains how to run MLS in a different language, but we should also explain how to print forms and certificates in a different language (without changing the MLS language). This could go in that same article (but broaden the title), or in a separate article.
* [[Local Unit Website]]: Break this article into a user-oriented page and an administrator page. The administration page could then spawn additional detailed articles. For example, resource scheduling could be its own topic, as well as [http://tech.lds.org/forum/showthread.php?t=3105 How to get members to use LUWS].
* [[Stake President]] and [[Bishop]] currently redirect to [[Leaders' responsibilities for record keeping]]. But there have been discussions on LDSTech forums such as [http://tech.lds.org/forum/showthread.php?t=1244 New Stake Presidency] about what clerks need to do, especially in the technology realm, to help get new stake presidencies and bishops acquainted with Church systems and get the proper access. This would apply to new clerks as well. It would be helpful to capture this "getting started" information.
* [[Members without callings]]: This MLS report has several options, and how to use it is not clear to all clerks. See {{LDSTech|thread=3690|title=Members Without Callings List}}.
* [[Escheating checks]]: This existing article should explain what happens after a check has been submitted on the Outstanding Checks form -- how long does it take to process, what will show up on a CUFS, what the clerk does in MLS to clear it out. See {{LDSTech|thread=3749|title=Old Uncleared checks}}.
* [[Custom Reports]]: Now that the wiki allows upload of the .mls file type, create and upload some helpful custom reports definition files that clerks can download and import into their unit's MLS.

== New projects ==
* [[iPhone App]] for Ward Directory and Calendar.

== New wiki features ==
Add bullet points below regarding changes to the structure of the wiki, or guidelines or procedures, such as templates or categories.

* Add template for references to the CHI

== Other ==
Add bullet points below for any other suggestions that do not fit the above topics.

[[Category:LDSTech Administration|New Content Requests]]

Church Directory of Organizations and Leaders

2009-09-03T17:22:25Z

Mkmurray: Add reference

The online '''Church Directory of Organizations and Leaders (CDOL)''' provides the same information as the old CD-ROM based Church Organization Information (COI), but it is always up to date with the latest information.

== Capabilities ==
CDOL allows leaders to:
* Look up leaders of other units, including contact information
* See the organizational structure of units. For example, a stake would have links to the wards and branches within the stake and any family history centers in the stake, as well as larger entities that include the stake, such as areas, welfare regions, temple districts, etc.
* Access a Unit Locator to find what ward and stake contains a given street address
* Find how to contact any Church department

== New CDOL Version (cdol.lds.org)==
A new version of CDOL was announced in a letter dated 18 December 2008. This new version uses [[LDS Account]] credentials and is located at https://cdol.lds.org. '''The previous CDOL website used different login credentials.''' If you do not have an LDS Account, you will need to [[LDS_Account#Create_an_account|create]] one the first time you visit the website. This can be done by clicking the link "Register for an LDS Account."

The new version adds the following features:
* Option to create a customized directory
* Ability to perform searches for organizations or leaders using multiple search criteria
* Option to save searches
* A listing of the current local time for units
* Ability to see all Standard Positions for units in the user's ward and stake

== Old CDOL Version (col.ldschurch.org)==
As of 31 December 2008 the old site is no longer promoted. Although the information is still current, no permission keys are being issued for the old CDOL (col.ldschurch.org). New users should use the new CDOL (cdol.lds.org).

== Directory CDs ==
The old CDOL (directory) CDs are no longer being created and sent to local units. They have been discontinued and replaced by the CDOL (cdol.lds.org) online.

== Access ==
The following positions have been approved for access:
* Bishops
* Branch Presidents
* Stake Presidents
* Stake Presidency Counselors
* [[Stake Clerk|Stake Clerks]]
* [[Executive Secretary|Stake Executive Secretary]] (if added by the stake president)
* [[Assistant stake clerk]]s (if properly specified in MLS using standardized callings)
* District President and Counselors
* District Clerk and Assistant Clerks
* District Executive Secretary

To have access, they must be listed in the correct position in CDOL and have an LDS Account. People with these [[callings]] will be listed in CDOL if they have been added using the appropriate [[Leader and Unit Change Request]] form or are properly listed in MLS using the standardized callings.

=== Alternative for those without access ===
Some clerks and leaders (such as bishopric counselors, ward clerks, and assistant stake clerks) might need to look up bishops of other wards (e.g., to communicate regarding a member who has moved to a new ward in a different stake, or to move records when a member moves). Although access to CDOL would be helpful, it is not permitted under current policy.

One way to look up a bishop is to use the [[Meetinghouse Locator]]. Entering a member's new address will display the assigned congregation. Clicking on that congregation's link will display a popup over the map that includes the bishop's last name and a phone number.

For moving membership records, it is helpful to have the ward and stake unit numbers and names for the member's new address<ref>{{LDSTech|title=Alternative for getting unit numbers without access to CDOL|post=18744}}</ref>. The popup from maps.lds.org described above will have a link labeled "Go to Website" (assuming the new stake participates in the [[Local Unit Website]] program, which most do). Following that link will take you to the ward's home page. If you look closely at the URL for that page, it will end in "-nnnnnn,00.html"; the "nnnnnn" is the unit number for the ward. Similarly, if you then follow the "Stake Home" link from the ward's home page, you will be taken to the stake's home page, where you can examine the URL to obtain the stake's unit number.

== Supported Languages ==
The Church Directory of Organizations and Leaders will be translated into a total of 41 languages. Currently about half are translated.

=== Released Languages ===
The new version of CDOL is currently available in the following languages. ''Please note that languages are viewed based on the user's browser setting. If the user's browser is set to Spanish (es) then the user will see CDOL screen text in Spanish.''

{| {{table}} border="1" cellspacing="0" cellpadding="5"
| align="center" style="background:#f0f0f0;"|'''Language'''
| align="center" style="background:#f0f0f0;"|'''Language Code'''
|-
| Chinese - Traditional||zh
|-
| Czech||cs
|-
| Danish||da
|-
| Dutch||nl
|-
| English||en
|-
| Finnish||fi
|-
| French||fr
|-
| German||de
|-
| Hungarian||hu
|-
| Italian||it
|-
| Japanese||ja
|-
| Korean||ko
|-
| Norwegian||no
|-
| Portuguese||pt-BR
|-
| Samoan||sm
|-
| Spanish||es
|-
| Swedish||sv
|-
| Ukrainian||uk
|-
|}

=== Pending Translation ===
CDOL is still being translated into the following languages.

{| {{table}} border="1" cellspacing="0" cellpadding="5"
| align="center" style="background:#f0f0f0;"|'''Language'''
| align="center" style="background:#f0f0f0;"|'''Language Code'''
|-
| Albanian||sq
|-
| Armenian||hy
|-
| Bulgarian||bg
|-
| Cambodian||km
|-
| Croatian||hr
|-
| Estonian||et
|-
| Fijian||fj
|-
| Greek||el
|-
| Icelandic||is
|-
| Indonesian||id
|-
| Laotian||lo
|-
| Latvian||lv
|-
| Lithuanian||lt
|-
| Mongolian||mn
|-
| Polish||pl
|-
| Romanian||ro
|-
| Russian||ru
|-
| Serbian (Cyrillic)||sr
|-
| Slovak||sk
|-
| Slovenian||sl
|-
| Thai||th
|-
| Tongan||to
|-
| Vietnamese||vi
|-
|}

== References ==
<references />

[[Category:Websites]]

Talk:Church Directory of Organizations and Leaders

2009-07-29T20:10:42Z

Mkmurray: /* Assistant Stake Clerk access to CDOL */

== Why was the correct information about the old site deleted? ==

The original version of this page had the correct information about the old site:

'''Although the 18 December 2008 letter said that the old site was to be discontinued 31 December 2008, the site continues to function. It is located at http://col.ldschurch.org and uses the [[Login Credentials#NetID|NetID]] credentials.'''

Why was this changed? Did someone simply trust the letter, without actually attempting to verify if the old site was still active? Because it most definitely is still active. I see no reason to put a false statement on the page, which is its current state. I imagine the Church would prefer to have people move to the new site, but if some authorized user doesn't yet have an LDS Account and wants to access the old site, I see no reason why they shouldn't do so.

If the intent is to encourage people to use the new site, then let's put a true statement to that effect. -- [[User:Aebrown|Aebrown]] 04:38, 28 March 2009 (UTC)

:The ''old'' information was taken out because the Church wants to direct priesthood leaders to the new CDOL. Although the old CDOL (col.ldschurch.org) is still being updated, the Church is no longer issuing permission keys and are in the process of removing some of the users so they will be directed to the new CDOL (cdol.lds.org). It is in transition. New users should be directed to the new website. The complete discontinuation of the old CDOL is targeted for the end of April 2009.

::(Please remember to sign all posts to a Talk page by using four tildes).

::Thanks for the clarification. I surmised all this. I don't see any reason why we shouldn't be up front about this. We can indicate that no new permission keys are being issued and that any new users should use the new site. -- [[User:Aebrown|Aebrown]] 15:50, 30 March 2009 (UTC)

== Assistant Stake Clerk access to CDOL ==

I'm surprised by the removal of Alan's very recent addition to the list of leaders that have access to CDOL. I believe he's correct that Assistant Stake Clerks now indeed do have access. -- [[User:Mkmurray|Mike Murray]] 19:16, 29 July 2009 (UTC)

:It's been confirmed that Assistant Stake Clerks do not have access to CDOL. --[[User:Calebpusey|Caleb]] 19:56, 29 July 2009 (UTC)

::I suppose not unless special allowance is made at the request of the Stake President? Thanks for your response. -- [[User:Mkmurray|Mike Murray]] 20:10, 29 July 2009 (UTC)

Talk:Church Directory of Organizations and Leaders

2009-07-29T19:16:07Z

Mkmurray: /* Assistant Stake Clerk access to CDOL */ new section

Tech Project FAQs

2009-07-28T20:00:28Z

Mkmurray: /* FAQs */ fix typo

An exciting new direction that the Church is taking is to involve the community in the design and development of various projects. Some of these projects include:

* [[Local_Unit_Website_Project | Local Unit Website Project]].
* [[Home Teaching / Visiting Teaching Application | Home and Visiting Teaching Project]]
* [[Mormon Channel | Mormon Channel Mobile Applications Project]]
* [[IPhone Scriptures Application | iPhone Scriptures Project]]
* [[:Category:Projects|more...]]

We encourage anyone to get involved. Read the FAQs below to learn how you can get involved in helping the Church build great applications.

===FAQs===
Here are answers to some of the most frequently asked questions.

; How do I get involved?
# You need to follow all of the steps found on the [[Requirements for Participation]] page.
# Find a project that is interesting to you. It does not matter if you are a programmer, QA engineer, security expert, technical writer, or UI designer, we need all skill sets and talents.
# Visit the project page on the wiki for the project you are interested in. Most are listed above.
# Each project will have specific needs and many have a step by step process for checking out code, building, with links to our Bug Tracking system so that you can see what needs to be done and volunteer.

; Where can I find out the most urgent projects to help with?
: Check out our [[Current Needs]] wiki page.

; How do I check out code?
: We use subversion as our code management system. Each project has it's own subversion repository. Before you can check out any code, however, you must have an LDSAccount username (see [[Requirements for Participation]] for information about how to get an LDSAccount username). Visit the project page for details on where to find the subversion repository for the project.

; How do I check in code?
: This depends upon the project. Some projects you can request to have commit rights to subversion. Other projects require that you submit code patches to be reviewed before they are applied. See the project wiki page for specifics. If you have any questions, please contact [[User:welchtc | Tom Welch]].

; Is there a testing environment for the various projects?
: Most projects have a test environment that you can utilize. For example, you can see the latest build of the Local Unit Directory application by visiting http://tech.lds.org/luc. Most projects will automatically look for subversion commits and generate builds to the test environment. See the individual project pages for more information about their test environments.

; Are there any coding or other community standards that must be followed?
: Each project may have their own standards but overall, you can read the currently defined [[Community Development Best Practices | best practices]].

; I'm not a programmer. How can I contribute?
: We always have need for UI designers, QA engineers and testers, technical writers, translators, security experts, project managers, etc. Contact [[User:welchtc | Tom Welch]] with your skills and we will put you on a team best fitting to your skills.

; What do I do if I have a great idea for a new application?
: We love to hear your ideas or even see projects you have created. Please send an email to [[User:welchtc | Tom Welch]] with your idea or project.

; Who do I contact for more information?
: You can contact [[User:welchtc | Tom Welch]] with any questions that you have.

Main Page

2009-07-09T21:17:06Z

Mkmurray: change link for Mormon Channel projects to the newly created home page for all mobile apps

<div style="margin: 10px 0px 0px 0px;">
<div style="background-color: #f2f3e5; text-align: center;">
==Welcome to the LDSTech Wiki==
</div>
The purpose of this wiki is for the Church and community members to collaborate on various documents and technology projects sponsored by the Church. We invite all to participate. '''New users''', please review the [[Requirements for Participation]] and [[Guidelines|Wiki Guidelines]] pages.
<table width="100%" cellspacing="10" cellpadding="0">
<tr valign="top">
<td width="50%">
<div style="margin: 0px 5px 0px 0px; border: 1px solid #d8d7c5;">
<div style="background-color: #f2f3e5; text-align: center;">
=== Projects ===
</div> 
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Announcements=====
</div>
* [[General_Announcements#Moving_to_HTTPS_for_key_tools | Change in our URLs]]
* [[General_Announcements#First_Java_Stack_Documentation | LDS Java Stack Documentation]]
* [[General_Announcements#Where_is_Subversion | Subversion URL]]
* [[General_Announcements#Syntax_Highlighting | Syntax Code Highlighting in Wiki]]
</td>

<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

=====Participation & Current Needs=====
</div>
* [[LDSTech:About | New to the LDSTech Wiki?]]
* [[Requirements for Participation | Requirements for Participation]]
* [http://www.mediawiki.org/wiki/Help:Formatting Help with Formatting Documents]
* [[Current Needs]]
* [[Community Development Best Practices | Getting Started/Best Practices]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

===== Current Projects =====
</div>
* [[Home Teaching / Visiting Teaching Application | Home Teaching / Visiting Teaching Application]]
* [[Local Unit Website Project | Local Unit Website Project]]
* [[Mormon Channel | Mormon Channel Mobile Applications]]
* [[IPhone Scriptures Application | iPhone Scriptures Application]]
* [[:Category:Projects|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

===== Feedback & Suggestions =====
</div>
* [[MLS:_Feedback_and_Suggestions | MLS (Member and Leader Services)]]
* [[LUWS:_Feedback_and_Suggestions | LUWS (Local Unit Web Sites)]]
* [[Online_Scriptures:_Feedback_and_Suggestions | Online Scriptures]]
</td>
</tr>

<tr>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Internet & Family Safety =====
</div>
* [[Internet (Family Safety) | Internet Safety]]
* [[Cell Phones (Family_Safety) | Cell Phone Safety]]
* [[Family Safety | more...]]
</td>
</tr>

</table>
</div> 
</td>
<td>
<div style="margin: 0px 0px 0px 10px; border: 1px solid #d8d7c5;">
<div style="background-color: #f2f3e5; text-align: center;">

=== Clerks ===
</div>
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====General=====
</div>
* [[Clerks Overview|Overview]]
* [[Stake Clerk]] / [[Ward Clerk]]
* [[MLS]]
* [[Glossary]]
* '''[[Tip of the Week]]!'''
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Financial=====
</div>
* [[Financial Clerk]]
* [[Financial Audit]]
* [[Reconciliation]]
* [[:Category:Finance|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Membership =====
</div>
* [[Membership Clerk]]
* [[Membership Records]]
* [[Recording Ordinances]]
* [[Membership Audit]]
* [[:Category:Membership|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Statistical =====
</div>
* [[Statistical Clerk]]
* [[Statistical Reporting]]
* [[Quarterly Report]]
* [[Annual History]]
* [[:Category:Statistical|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Technology =====
</div>
* [[Stake Technology Specialist]]
* [[Meetinghouse Internet]]
* [[Meetinghouse Webcast]]
* [[Satellite Broadcasts]]
* [[Local Unit Website]]
* [[:Category:Technology|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Unit Administration=====
</div>
* [[:Category:Roles|Roles]]
* [[CDOL]]
* [[Maps and Boundaries]]
* [[Meetinghouse Locator]]
* [[Training]]
* [[:Category:Unit Administration|more...]]
</td>
</tr>
<tr>
<td colspan="2">
{{Box
| title=Acknowledgement
| color=yellow
| content=For many years [[User:Kslarsena|Kent S. Larsen]] of New York, New York, has personally funded and maintained a mailing list, discussion forum, and (more recently) a wiki for LDS clerks. The administrators of the LDSTech wiki wish to thank this pioneer of clerk training and the other long-time contributors to his site for generously donating all of the contents of their wiki (more than 100 pages of information) to the new LDSTech wiki. This contribution is a great blessing to clerks around the world, allowing the new site to “go live” overnight.
}}
</td>
</tr>
</table>
</div>
</td>
</tr>
</table>
__NOTOC__
__NOEDITSECTION__

TechWiki talk:Guidelines

2009-06-17T15:17:35Z

Mkmurray: /* How to help people with guidelines */ I was guilty of the "no preview" issue :\

== Template:Need Input==
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. [[User:Aprilbosworth|Aprilbosworth]] 03:02, 16 October 2008 (UTC)

:I agree the word "parameter" is pretty technical. I'm not quite sure how else to describe it, since I've dealt with this jargon for quite a few years. I guess it's time to pull out the Thesaraus.

:P.S. Don't forget to sign your name using 4 tildes '~'; I have added your signature to your last post. Thanks. -- [[User:Mkmurray|Mike Murray]] 15:52, 16 October 2008 (UTC)

:Although many participants on the wiki will be developers, we need the involvement of others as well. So reducing jargon is a good idea (except for certain pages involving technical design such as [[Home Teaching / Visiting Teaching Detailed Design]]). I think your rewrite is good and could be extended to the other templates. I don't think we need a term to replace parameter as long as there is an example. --[[User:Eblood66|Eric Blood]] 18:18, 16 October 2008 (UTC)

== Guidelines vs. Manual of Style ==
I propose that this article (or portions of it) should be merged with the [[LDS_Tech:Manual of Style|Manual of Style]] or at least be moved to the LDS_Tech namespace. --[[User:Cottrells|Steve]] 20:28, 16 April 2009 (UTC)

: I certainly agree that the Guidelines should be in the LDS Tech namespace. But I don't like the idea of merging the content with the Manual of Style. As I see it, there is a pretty clear distinction between the articles. The MoS covers specific wording choices, and the Guidelines covers procedures and wiki elements. Articles should cover a specific topic and not be too long. The current organization meets these goals, and merging would violate both principles, in my opinion. -- [[User:Aebrown|Aebrown]] 03:05, 17 April 2009 (UTC)

::I think I was being a little hasty. After further review, I can see the benefit of having these two separate articles. On reflection I think this article would be better placed in the ''Help'' namespace. --[[User:Cottrells|Steve]] 12:26, 17 April 2009 (UTC)

== How to help people with guidelines ==

{{unresolved}}
There are many contributors who are clearly new to wikis, or at least are not familiar with the standard practices. We've tried to collect some helpful guidelines in this article, but clearly some people have never seen these guidelines, or forget what they are, or disagree with them and ignore them. I tend to think most people who don't follow the guidelines are in the first group.

The errors I see most commonly are:
* There are a few users who are extremely quick to click the Save Page button when they are editing. They might make 15 changes in the space of 10 minutes that really clutter up the change log, and some are obvious errors that show that they never used preview to see if it was a good change before saving.
* Mislabeling of changes as a "minor edit." This is to be used only for completely non-controversial changes such as punctuation, formatting, etc. If you are actually adding content, it is not a minor change, even if you are only adding one sentence. I see many "minor edits" that introduce many lines of new content.
* Using title case, contrary to the new capitalization guidelines for titles and section headings.

Given that we value the contributions of all contributors, and we work under the assumption that they want to "do it right" but are just not aware, my questions are:
# How do we help people know about the guidelines? They are mentioned on the Main Page, and on the Help page, but it's easy to miss those places. Is there some other way to make these guidelines visible? If we had a "Wiki Tip of the Week", is there a way we could make that sufficiently prominent to get people's attention?
# When a particular individual is repeatedly doing things outside the guidelines, how can we help the individual? I have tried to e-mail some of these people, but none of them can be e-mailed through the wiki, either because they did not specify an e-mail address in their profile, or they have requested no e-mail. I really doubt that they monitor their User Talk pages, so that's probably not effective, either. Am I missing some way to communicate with them?

I'd appreciate any feedback on this topic. -- [[User:Aebrown|Aebrown]] 15:06, 17 June 2009 (UTC)

:I have been frustrated with the inability to email members in the past as well. Though this is a side issue to the problem at hand, I think it would help enormously to be able to contact every wiki member offline from the wiki via email. Might I suggest we make email addresses and receiving emails mandatory? Is this possible with the software? -- [[User:Mkmurray|Mike Murray]] 15:16, 17 June 2009 (UTC)

TechWiki talk:Guidelines

2009-06-17T15:16:51Z

Mkmurray: RE: /* How to help people with guidelines */

== Template:Need Input==
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. [[User:Aprilbosworth|Aprilbosworth]] 03:02, 16 October 2008 (UTC)

:I agree the word "parameter" is pretty technical. I'm not quite sure how else to describe it, since I've dealt with this jargon for quite a few years. I guess it's time to pull out the Thesaraus.

:P.S. Don't forget to sign your name using 4 tildes '~'; I have added your signature to your last post. Thanks. -- [[User:Mkmurray|Mike Murray]] 15:52, 16 October 2008 (UTC)

:Although many participants on the wiki will be developers, we need the involvement of others as well. So reducing jargon is a good idea (except for certain pages involving technical design such as [[Home Teaching / Visiting Teaching Detailed Design]]). I think your rewrite is good and could be extended to the other templates. I don't think we need a term to replace parameter as long as there is an example. --[[User:Eblood66|Eric Blood]] 18:18, 16 October 2008 (UTC)

== Guidelines vs. Manual of Style ==
I propose that this article (or portions of it) should be merged with the [[LDS_Tech:Manual of Style|Manual of Style]] or at least be moved to the LDS_Tech namespace. --[[User:Cottrells|Steve]] 20:28, 16 April 2009 (UTC)

: I certainly agree that the Guidelines should be in the LDS Tech namespace. But I don't like the idea of merging the content with the Manual of Style. As I see it, there is a pretty clear distinction between the articles. The MoS covers specific wording choices, and the Guidelines covers procedures and wiki elements. Articles should cover a specific topic and not be too long. The current organization meets these goals, and merging would violate both principles, in my opinion. -- [[User:Aebrown|Aebrown]] 03:05, 17 April 2009 (UTC)

::I think I was being a little hasty. After further review, I can see the benefit of having these two separate articles. On reflection I think this article would be better placed in the ''Help'' namespace. --[[User:Cottrells|Steve]] 12:26, 17 April 2009 (UTC)

== How to help people with guidelines ==

{{unresolved}}
There are many contributors who are clearly new to wikis, or at least are not familiar with the standard practices. We've tried to collect some helpful guidelines in this article, but clearly some people have never seen these guidelines, or forget what they are, or disagree with them and ignore them. I tend to think most people who don't follow the guidelines are in the first group.

The errors I see most commonly are:
* There are a few users who are extremely quick to click the Save Page button when they are editing. They might make 15 changes in the space of 10 minutes that really clutter up the change log, and some are obvious errors that show that they never used preview to see if it was a good change before saving.
* Mislabeling of changes as a "minor edit." This is to be used only for completely non-controversial changes such as punctuation, formatting, etc. If you are actually adding content, it is not a minor change, even if you are only adding one sentence. I see many "minor edits" that introduce many lines of new content.
* Using title case, contrary to the new capitalization guidelines for titles and section headings.

Given that we value the contributions of all contributors, and we work under the assumption that they want to "do it right" but are just not aware, my questions are:
# How do we help people know about the guidelines? They are mentioned on the Main Page, and on the Help page, but it's easy to miss those places. Is there some other way to make these guidelines visible? If we had a "Wiki Tip of the Week", is there a way we could make that sufficiently prominent to get people's attention?
# When a particular individual is repeatedly doing things outside the guidelines, how can we help the individual? I have tried to e-mail some of these people, but none of them can be e-mailed through the wiki, either because they did not specify an e-mail address in their profile, or they have requested no e-mail. I really doubt that they monitor their User Talk pages, so that's probably not effective, either. Am I missing some way to communicate with them?

:I have been frustrated with the inability to email members in the past as well. Though this is a side issue to the problem at hand, I think it would help enormously to be able to contact every wiki member offline from the wiki via email. Might I suggest we make email addresses and receiving emails mandatory? Is this possible with the software? -- [[User:Mkmurray|Mike Murray]] 15:16, 17 June 2009 (UTC)
I'd appreciate any feedback on this topic. -- [[User:Aebrown|Aebrown]] 15:06, 17 June 2009 (UTC)

Main Page

2009-05-22T16:15:25Z

Mkmurray: Fix user link

<div style="margin: 10px 0px 0px 0px;">
<div style="background-color: #f2f3e5; text-align: center;">
==Welcome to the LDSTech Wiki==
</div>
The purpose of this wiki is for the Church and community members to collaborate on various documents and technology projects sponsored by the Church. We invite all to participate. '''New users''', please review the [[Requirements for Participation]] and [[Guidelines|Wiki Guidelines]] pages.
<table width="100%" cellspacing="10" cellpadding="0">
<tr valign="top">
<td width="50%">
<div style="margin: 0px 5px 0px 0px; border: 1px solid #d8d7c5;">
<div style="background-color: #f2f3e5; text-align: center;">
=== Projects ===
</div> 
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Announcements=====
</div>
* [[General_Announcements#Moving_to_HTTPS_for_key_tools | Change in our URLs]]
* [[General_Announcements#First_Java_Stack_Documentation | LDS Java Stack Documentation]]
* [[General_Announcements#Where_is_Subversion | Subversion URL]]
* [[General_Announcements#Syntax_Highlighting | Syntax Code Highlighting in Wiki]]
</td>

<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

=====Participation & Current Needs=====
</div>
* [[LDSTech:About | New to the LDSTech Wiki?]]
* [[Requirements for Participation | Requirements for Participation]]
* [http://www.mediawiki.org/wiki/Help:Formatting Help with Formatting Documents]
* [[Current Needs]]
* [[Community Development Best Practices | Getting Started/Best Practices]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

===== Current Projects =====
</div>
* [[Home Teaching / Visiting Teaching Application | Home Teaching / Visiting Teaching Application]]
* [[Local Unit Website Project | Local Unit Website Project]]
* [[IPhone Scriptures Application | iPhone Scriptures Application]]
* [[:Category:Projects|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

===== Feedback & Suggestions =====
</div>
* [[MLS:_Feedback_and_Suggestions | MLS (Member and Leader Services)]]
* [[LUWS:_Feedback_and_Suggestions | LUWS (Local Unit Web Sites)]]
* [[Online_Scriptures:_Feedback_and_Suggestions | Online Scriptures]]
</td>
</tr>

<tr>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Internet & Family Safety =====
</div>
* [[Internet (Family Safety) | Internet Safety]]
* [[Cell Phones (Family_Safety) | Cell Phone Safety]]
* [[Family Safety | more...]]
</td>
</tr>

</table>
</div> 
</td>
<td>
<div style="margin: 0px 0px 0px 10px; border: 1px solid #d8d7c5;">
<div style="background-color: #f2f3e5; text-align: center;">

=== Clerks ===
</div>
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====General=====
</div>
* [[Clerks Overview|Overview]]
* [[Stake Clerk]] / [[Ward Clerk]]
* [[MLS]]
* [[Glossary]]
* [[Humor]]
* '''[[Tip of the Week]]!'''
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Financial=====
</div>
* [[Financial Clerk]]
* [[Financial Audit]]
* [[Reconciliation]]
* [[:Category:Finance|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Membership =====
</div>
* [[Membership Clerk]]
* [[Membership Records]]
* [[Recording Ordinances]]
* [[Membership Audit]]
* [[:Category:Membership|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Statistical =====
</div>
* [[Statistical Clerk]]
* [[Statistical Reporting]]
* [[Quarterly Report]]
* [[Annual History]]
* [[:Category:Statistical|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Technology =====
</div>
* [[Stake Technology Specialist]]
* [[Meetinghouse Internet]]
* [[Meetinghouse Webcast]]
* [[Satellite Broadcasts]]
* [[Local Unit Website]]
* [[:Category:Technology|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Unit Administration=====
</div>
* [[:Category:Roles|Roles]]
* [[CDOL]]
* [[Maps and Boundaries]]
* [[Meetinghouse Locator]]
* [[Training]]
* [[:Category:Unit Administration|more...]]
</td>
</tr>
<tr>
<td colspan="2">
{{Box
| title=Acknowledgement
| color=yellow
| content=For many years [[User:Kslarsena|Kent S. Larsen]] of New York, New York, has personally funded and maintained a mailing list, discussion forum, and (more recently) a wiki for LDS clerks. The administrators of the LDSTech wiki wish to thank this pioneer of clerk training and the other long-time contributors to his site for generously donating all of the contents of their wiki (more than 100 pages of information) to the new LDSTech wiki. This contribution is a great blessing to clerks around the world, allowing the new site to “go live” overnight.
}}
</td>
</tr>
</table>
</div>
</td>
</tr>
</table>
__NOTOC__
__NOEDITSECTION__

Login credentials

2009-05-06T05:15:33Z

Mkmurray: /* LDS Account */ correct a few links and better describe LDS Account credential system

'''Login credentials''' are required for accessing many Church systems. Several different credential systems exist, although some are shared among multiple systems.

== LDS Account ==
The LDS Account is the new, unified online LDS credential and login system. It is described in an [http://tech.lds.org/index.php?option=com_content&view=article&id=4:lds-account&catid=1:miscellanous article on the main page of LDSTech]. Newer web sites use this system, while many existing LDS sites are being migrated to this platform.
* [http://ldsaccount.lds.org LDS Account]: Sign up for an LDS Account
* [[Temple Recommends#Temple Entry System|Temple Entry System]] (online temple recommend renewals)
* [[Missionary Recommendation System]]
* New [[Online Directory of Leaders]]
* [https://tech.lds.org/wiki LDSTech Wiki]
* New [https://www.ldsces.org/emplogin/loginldsaccount.aspx Church Educational System] employee site
* [http://www.lds.org/churchhistory/museum/competition LDS International Art Competition]
* [[Local Unit Website|Local Unit Websites (LUWS)]]: Formerly used NetID, but now use LDS Account. [https://secure.lds.org/units/login Login Page]

== NetID ==
The LDS NetID is a user name that at one time was used for several systems, including the local unit web site (LUWS). However, it is gradually being replaced by LDS Account. Only a few sites remain that use it, including:
* Old [[Online Directory of Leaders]]
* Old [https://www.ldsces.org/emplogin/loginldsaccount.aspx Church Educational System] (moving to LDS Account)
* [https://secure.lds.org/scs/ersdb Employment Resource Database]
* [http://www.lds.org/pef Perpetual Education Fund]

Most of these sites provide a means for updating the NetID account information, but it can also be updated directly at: [https://secure.lds.org/gso/edit_account Update NetID Profile]

== Stake Unit ==
Each stake president can use the stake unit number to access e-mail and the archive of official letters:
* [http://ldsmail.net LDSMail.net]. The password can be changed using the Options page as follows:
:''If you know the current password:''
# Log in to [http://ldsmail.net LDSMail.net]
# At the top of the main window next to the date, click the middle '''Options''' icon.
# In the '''Options - General Settings''' window, enter the old password once and the new password twice, and then click '''Save'''.
:''If you do not know the current password:''
:Contact your stake technology specialist, who will contact the Global Service Desk.
* [http://apps.lds.org/letters Official Communication Library] (OCL). There is no option for changing the password; change it using LDSMail.net and it will affect the OCL as well.

== Miscellaneous ==
A variety of other systems have their own login credentials:
* [[MLS Users|Member and Leader Services (MLS)]]
* [http://tech.lds.org/forum LDS Tech Forum]
* [http://www.familysearch.org FamilySearch]
* [http://www.ldscatalog.com LDS Catalog] (Online Distribution Services unit login)

[[Category:Websites]]

Main Page

2009-04-27T14:44:42Z

Mkmurray: standardize "more..." links

<div style="margin: 10px 0px 0px 0px;">
<div style="background-color: #f2f3e5; text-align: center;">
==Welcome to the LDSTech Wiki==
</div>
The purpose of this wiki is for the Church and community members to collaborate on various documents and technology projects sponsored by the Church. We invite all to participate. '''New users''', please review the [[Requirements for Participation]] and [[Guidelines|Wiki Guidelines]] pages.
<table width="100%" cellspacing="10" cellpadding="0">
<tr valign="top">
<td width="50%">
<div style="margin: 0px 5px 0px 0px; border: 1px solid #d8d7c5;">
<div style="background-color: #f2f3e5; text-align: center;">
=== Projects ===
</div> 
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Announcements=====
</div>
* [[General_Announcements#Moving_to_HTTPS_for_key_tools | Change in our URLs]]
* [[General_Announcements#First_Java_Stack_Documentation | LDS Java Stack Documentation]]
* [[General_Announcements#Where_is_Subversion | Subversion URL]]
* [[General_Announcements#Syntax_Highlighting | Syntax Code Highlighting in Wiki]]
</td>

<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

=====Participation & Current Needs=====
</div>
* [[LDSTech:About | New to the LDSTech Wiki?]]
* [[Requirements for Participation | Requirements for Participation]]
* [http://www.mediawiki.org/wiki/Help:Formatting Help with Formatting Documents]
* [[Current Needs | Current Needs ]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

===== Current Projects =====
</div>
* [[Home Teaching / Visiting Teaching Application | Home Teaching / Visiting Teaching Application]]
* [[Local Unit Website Project | Local Unit Website Project]]
* [[IPhone Scriptures Application | iPhone Scriptures Application]]
* [[:Category:Projects|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

===== Feedback & Suggestions =====
</div>
* [[MLS:_Feedback_and_Suggestions | MLS (Member and Leader Services)]]
* [[LUWS:_Feedback_and_Suggestions | LUWS (Local Unit Web Sites)]]
* [[Online_Scriptures:_Feedback_and_Suggestions | Online Scriptures]]
</td>
</tr>

<tr>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Internet & Family Safety =====
</div>
* [[Internet (Family Safety) | Internet Safety]]
* [[Cell Phones (Family_Safety) | Cell Phone Safety]]
* [[Family Safety | more...]]
</td>
</tr>

</table>
</div> 
</td>
<td>
<div style="margin: 0px 0px 0px 10px; border: 1px solid #d8d7c5;">
<div style="background-color: #f2f3e5; text-align: center;">

=== Clerks ===
</div>
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====General=====
</div>
* [[Clerks Overview|Overview]]
* [[Stake Clerk]] / [[Ward Clerk]]
* [[MLS]]
* [[Glossary]]
* '''[[Tip of the Week]]!'''
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Financial=====
</div>
* [[Financial Clerk]]
* [[Financial Audit]]
* [[Reconciliation]]
* [[:Category:Finance|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Membership =====
</div>
* [[Membership Clerk]]
* [[Membership Records]]
* [[Recording Ordinances]]
* [[Membership Audit]]
* [[:Category:Membership|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Statistical =====
</div>
* [[Statistical Clerk]]
* [[Statistical Reporting]]
* [[Quarterly Report]]
* [[Annual History]]
* [[:Category:Statistical|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Technology =====
</div>
* [[Stake Technology Specialist]]
* [[Meetinghouse Internet]]
* [[Meetinghouse Webcast]]
* [[Satellite Broadcasts]]
* [[Local Unit Website]]
* [[:Category:Technology|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Unit Administration=====
</div>
* [[:Category:Roles|Roles]]
* [[CDOL]]
* [[Maps and Boundaries]]
* [[Meetinghouse Locator]]
* [[Training]]
* [[:Category:Unit Administration|more...]]
</td>
</tr>
<tr>
<td colspan="2">
{{Box
| title=Acknowledgement
| color=yellow
| content=For many years Kent S. Larsen of New York City, New York, has personally funded and maintained a mailing list, discussion forum, and (more recently) a wiki for LDS clerks. The administrators of the LDSTech wiki wish to thank this pioneer of clerk training and the other long-time contributors to his site for generously donating all of the contents of their wiki (more than 100 pages of information) to the new LDSTech wiki. This contribution is a great blessing to clerks around the world, allowing the new site to “go live” overnight.
}}
</td>
</tr>
</table>
</div>
</td>
</tr>
</table>
__NOTOC__
__NOEDITSECTION__

Main Page

2009-04-27T14:42:27Z

Mkmurray: update Current Projects section

<div style="margin: 10px 0px 0px 0px;">
<div style="background-color: #f2f3e5; text-align: center;">
==Welcome to the LDSTech Wiki==
</div>
The purpose of this wiki is for the Church and community members to collaborate on various documents and technology projects sponsored by the Church. We invite all to participate. '''New users''', please review the [[Requirements for Participation]] and [[Guidelines|Wiki Guidelines]] pages.
<table width="100%" cellspacing="10" cellpadding="0">
<tr valign="top">
<td width="50%">
<div style="margin: 0px 5px 0px 0px; border: 1px solid #d8d7c5;">
<div style="background-color: #f2f3e5; text-align: center;">
=== Projects ===
</div> 
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Announcements=====
</div>
* [[General_Announcements#Moving_to_HTTPS_for_key_tools | Change in our URLs]]
* [[General_Announcements#First_Java_Stack_Documentation | LDS Java Stack Documentation]]
* [[General_Announcements#Where_is_Subversion | Subversion URL]]
* [[General_Announcements#Syntax_Highlighting | Syntax Code Highlighting in Wiki]]
</td>

<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

=====Participation & Current Needs=====
</div>
* [[LDSTech:About | New to the LDSTech Wiki?]]
* [[Requirements for Participation | Requirements for Participation]]
* [http://www.mediawiki.org/wiki/Help:Formatting Help with Formatting Documents]
* [[Current Needs | Current Needs ]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

===== Current Projects =====
</div>
* [[Home Teaching / Visiting Teaching Application | Home Teaching / Visiting Teaching Application]]
* [[Local Unit Website Project | Local Unit Website Project]]
* [[IPhone Scriptures Application | iPhone Scriptures Application]]
* [[:Category:Projects|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">

===== Feedback & Suggestions =====
</div>
* [[MLS:_Feedback_and_Suggestions | MLS (Member and Leader Services)]]
* [[LUWS:_Feedback_and_Suggestions | LUWS (Local Unit Web Sites)]]
* [[Online_Scriptures:_Feedback_and_Suggestions | Online Scriptures]]
</td>
</tr>

<tr>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Internet & Family Safety =====
</div>
* [[Internet (Family Safety) | Internet Safety]]
* [[Cell Phones (Family_Safety) | Cell Phone Safety]]
* [[Family Safety | More]]
</td>
</tr>

</table>
</div> 
</td>
<td>
<div style="margin: 0px 0px 0px 10px; border: 1px solid #d8d7c5;">
<div style="background-color: #f2f3e5; text-align: center;">

=== Clerks ===
</div>
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====General=====
</div>
* [[Clerks Overview|Overview]]
* [[Stake Clerk]] / [[Ward Clerk]]
* [[MLS]]
* [[Glossary]]
* '''[[Tip of the Week]]!'''
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Financial=====
</div>
* [[Financial Clerk]]
* [[Financial Audit]]
* [[Reconciliation]]
* [[:Category:Finance|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Membership =====
</div>
* [[Membership Clerk]]
* [[Membership Records]]
* [[Recording Ordinances]]
* [[Membership Audit]]
* [[:Category:Membership|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Statistical =====
</div>
* [[Statistical Clerk]]
* [[Statistical Reporting]]
* [[Quarterly Report]]
* [[Annual History]]
* [[:Category:Statistical|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
===== Technology =====
</div>
* [[Stake Technology Specialist]]
* [[Meetinghouse Internet]]
* [[Meetinghouse Webcast]]
* [[Satellite Broadcasts]]
* [[Local Unit Website]]
* [[:Category:Technology|more...]]
</td>
<td><div style="background-color: #f2f3e5; padding-left: 10px; ">
=====Unit Administration=====
</div>
* [[:Category:Roles|Roles]]
* [[CDOL]]
* [[Maps and Boundaries]]
* [[Meetinghouse Locator]]
* [[Training]]
* [[:Category:Unit Administration|more...]]
</td>
</tr>
<tr>
<td colspan="2">
{{Box
| title=Acknowledgement
| color=yellow
| content=For many years Kent S. Larsen of New York City, New York, has personally funded and maintained a mailing list, discussion forum, and (more recently) a wiki for LDS clerks. The administrators of the LDSTech wiki wish to thank this pioneer of clerk training and the other long-time contributors to his site for generously donating all of the contents of their wiki (more than 100 pages of information) to the new LDSTech wiki. This contribution is a great blessing to clerks around the world, allowing the new site to “go live” overnight.
}}
</td>
</tr>
</table>
</div>
</td>
</tr>
</table>
__NOTOC__
__NOEDITSECTION__

Template:Merge

2009-04-17T19:34:43Z

Mkmurray: correct "LDS Tech" phrase to be "LDSTech"

{| style="margin: 0 10%; border-collapse: collapse; background: #FBFBFB; border: 1px solid #aaa; border-left: 10px solid #ff00ff;"
|-
|
| style="padding: 0.25em 0.5em; width: 100%;" | This page <b>may need to be merged</b> for quality to meet the LDSTech [[guidelines]].<br/>{{{1|}}}
|}

<includeonly>{{{category|[[Category:Pages to be merged]]}}}</includeonly><noinclude>
== Documentation ==
This template is to be applied to a page that need to be merged with another page, because it contains duplicate information. Once the content has been merged with the main article on the topic, the duplicate page should be changed to redirect to the main article.

=== Categorization ===
Pages that include this template will be automatically included in the [[:Category:Pages to be merged]] (unless you supply the "category=" parameter, as described below).

=== Usage ===
Simply insert the template near the top of the article by typing '''<nowiki>{{Merge}}</nowiki>'''. You should always supply the target page, and generally also the reason the merge is needed, e.g., '''<nowiki>{{Merge|This topic is covered under [[Membership Records]]}}</nowiki>'''. If you are using the template only for documentation purposes (such as on the [[Guidelines]] page), you can suppress the "Pages to be deleted"" category by adding a blank "category" parameter, e.g., '''<nowiki>{{Merge|This topic is covered under [[Membership Records]]|category=}}</nowiki>'''.

[[Category:Templates|Merge]]
</noinclude>

TechWiki talk:Manual of Style

2009-04-17T14:14:34Z

Mkmurray: /* LDSTech or LDS Tech? */ Reference Tom's response; "LDSTech" with no space wins

'''<span style='font-size:16px;'>Please leave any suggestions or questions below...</span>'''<br />



== We need a LDS Tech style guide ==

The Wikipedia manual of style is fine as far as it goes, but of course it does not address a single issue unique to the LDS Church. If we want to have usage that is both internally consistent and matches Church-mandated styles where they exist, we need to address many issues directly.

The [http://www.ldsclerks.com/index.php?title=Style_guide LDSClerks style guide] was a pretty good start at this, although it is clearly only a start. An example of an issue that is missing from that style guide is references to the ''Church Handbook of Instructions''. The Church has a specific style for such references. But how are wiki users to know what that style is? The obvious answer is that we describe it in a style guide.

It appears that the intent of this [[LDS_Tech:Manual of Style|Manual of Style]] article is that we would extend the article to include new specifics under the heading '''Exceptions'''. What we need is really not an exception, but rather details on a variety of topics that the Wikipedia MoS is silent on.

I would propose that we change the heading to "Additions," move the LDSClerks style guide content to this page, and then add a topic for CHI references. -- [[User:Aebrown|Aebrown]] 16:38, 26 March 2009 (UTC)

: Since there were no responses to my proposal, I went ahead and drafted style guidelines, based on the LDSClerks style guide but significantly revised and extended to match my understanding of the style guidelines used in the LDS Tech wiki. Please feel free to discuss questions on this Talk page or to make needed adjustments to the text. -- [[User:Aebrown|Aebrown]] 06:01, 7 April 2009 (UTC)

:: Looks great to me! Thanks for all of your hard work on this Wiki, Alan. This is becoming an amazing resource! -- [[User:Mkmurray|Mike Murray]] 14:43, 7 April 2009 (UTC)

== LDSTech or LDS Tech? ==
Maybe this is a very minor point, but I like consistency. The Manual of Style currently says ''The Church's technology website should be referenced as LDS Tech, or by its full name, "LDS Technology Web Site"'', however [https://tech.lds.org/wiki/index.php?title=Category:Projects&diff=prev&oldid=3476 a recent edit] by [[User:Welchtc|Tom]] was to change "LDS Tech" to "LDSTech". Some clarification would be appreciated, thanks. --[[User:Cottrells|Steve]] 10:24, 16 April 2009 (UTC)

: It's certainly an appropriate question, particularly in the Manual of Style. When I wrote this point in the MoS, I relied on a forum post by TomW at {{LDSTech|thread=1398}} in choosing to include a space. But the recent edit you mentioned, as well as several others on the wiki main page seem to indicate that Tom no longer prefers a space. Yet even the home page of http://tech.lds.org is quite inconsistent in its usage.

: I guess we'll wait for guidance from Tom, since there are many instances of both usages. The "LDS Tech" usage is a bit more readable, so I lean towards that, but "LDSTech" is more clearly a unique reference to this particular site, so I can see its virtues as well. Let's decide on the correct style and then work towards using that style '''everywhere'''. -- [[User:Aebrown|Aebrown]] 11:09, 16 April 2009 (UTC)

::The answer according to [[User_talk:Welchtc#LDSTech_or_LDS_Tech.3F|Tom Welch's user talk page]] is "LDSTech" with no space. I will try to help in editing when I see it. -- [[User:Mkmurray|Mike Murray]] 14:14, 17 April 2009 (UTC)

Template talk:TechForum

2009-04-14T17:23:57Z

Mkmurray: RE: /* Adding a Title Parameter */

==Adding a Title Parameter==

I'm unsure of how to do this in the wiki syntax, but would it be helpful to have another optional parameter that is the title of the post, thread, or forum, and then have that title included as part of the link that goes to the specific post, thread, or forum. For instance, the result could be "[http://tech.lds.org/forum/forumdisplay.php?f=50 General Clerks Discussion Forum] on {{LDSTech}}" instead of a forum link without a title like "[http://tech.lds.org/forum/forumdisplay.php?f=50 Forum] on {{LDSTech}}". -- [[User:Mkmurray|Mike Murray]] 15:42, 12 April 2009 (UTC)

:I have altered the template to include a solution that will insert the forum name based on the forum parameter. It does mean that your example above may no longer make sense. --[[User:Cottrells|Steve]] 22:09, 12 April 2009 (UTC)

::This isn't exactly what I had in mind, but it certainly is a creative solution. However, it would only work for forums, and not for threads or posts. It may also be somewhat of a pain to maintain that enumeration. I was actually looking just for an optional parameter called Title or something, that would just put a string of text before all of the other stuff. I figured the user could choose if they wanted to take the time to put in the title of the forum, thread, or post themself, or just go with the default wording that [[User:Aebrown|Aebrown]] set up. -- [[User:Mkmurray|Mike Murray]] 00:30, 13 April 2009 (UTC)

:::Oh, and yes you are right. My example above is no longer as I first typed it. I've now fixed the example. Thanks. -- [[User:Mkmurray|Mike Murray]] 00:39, 13 April 2009 (UTC)

::::I have added in an optional title parameter that will name posts or threads. I do not think the solution for naming forums is too hard to maintain. --[[User:Cottrells|Steve]] 08:29, 13 April 2009 (UTC)

:::::Just one comment about your change of the post link to showpost.php instead of showthread.php...I actually prefer the showthread.php method, because I like to see the post in context. My personal preference is to never use the showpost.php method of linking. I'm not necessarily asking you to change it back, but just wanted to get your comments and opinions on it.

:::::Also, I just attempted to fix the template when you don't provide a title parameter, but was unsuccessful. It is pasting <nowiki>{{{title}}}</nowiki> into the link. I added an if statement that I thought would work, but I guess I still don't know what I'm doing. :) Can someone "in the know" fix the bug for me? Thanks. -- [[User:Mkmurray|Mike Murray]] 15:53, 13 April 2009 (UTC)

::::::I've fixed the #if statements for the title parameter so that if it is not used it will return nothing. I think you make a fair comment about showpost.php, but maybe sometimes just highlighting the specific post would be more appropriate. Maybe both ways of linking should be an option? --[[User:Cottrells|Steve]] 17:48, 13 April 2009 (UTC)

:::::::Thanks, I think that looks terrific. Great work! -- [[User:Mkmurray|Mike Murray]] 17:23, 14 April 2009 (UTC)

Template talk:TechForum

2009-04-13T15:53:46Z

Mkmurray: RE: /* Adding a Title Parameter */

Template:TechForum

2009-04-13T15:47:11Z

Mkmurray: Reword parameter list and show example without the use of the Title parameter

<includeonly>{{#if: {{{post|}}} | [http://tech.lds.org/forum/showpost.php?p={{{post}}} {{#if: {{{title|}}} | ''{{{title}}}'' }} Post] on | {{#if: {{{thread|}}} | [http://tech.lds.org/forum/showthread.php?t={{{thread}}} {{#if: {{{title|}}} | ''{{{title}}}'' }} Thread] on | {{#if: {{{forum|}}} | [http://tech.lds.org/forum/forumdisplay.php?f={{{forum}}} {{#switch: {{{forum}}}
| 3 = ''What's New''
| 4 = ''Announcements & Policies''
| 13 = ''Community Discussions''
| 14 = ''General Discussions''
| 15 = ''Ideas & Suggestions''
| 16 = ''Links & Resources''
| 17 = ''In The News''
| 18 = ''Current and Future Church Technologies''
| 21 = ''MLS Support, Help, and Feedback ''
| 22 = ''Help & Feedback''
| 23 = ''Getting Help''
| 24 = ''Feedback''
| 27 = ''Building-to-Building Communications''
| 34 = ''LDS Tech Featured Article Discussions''
| 36 = ''Development Help Wanted''
| 38 = ''Technical Recruiting''
| 42 = ''Clerks and Technology Support''
| 43 = ''Getting Started for New Clerks''
| 45 = ''Reports and Forms''
| 46 = ''Local Unit Finance''
| 47 = ''Membership Help''
| 48 = ''Computers, Printers, Networking, and Electronics''
| 49 = ''Other Technologies''
| 50 = ''General Clerks Discussion''
| 51 = ''Meetinghouse Internet''
| 86 = ''FAQs for Local Unit Copier Program''
| 87 = ''Local Unit Copiers & MFPs''
| #default =
}} Forum] on }} }} }} [http://tech.lds.org LDS Tech] [http://tech.lds.org/forum Discussion Forum]</includeonly><noinclude>
== Purpose ==
This template is used to easily reference items on the [http://tech.lds.org LDS Technology Web Site] forums.

== Usage ==
This template can take one of three optional parameters (or no parameter) for creating a reference link to an item in the forums:
* '''forum''': the ID of a forum
* '''thread''': the ID of a thread
* '''post''': the ID of a post

This template can also take another optional parameter that allows you to add a title to the generated link:
* '''title''': the title of the post or thread

=== Examples ===
{| border="1" cellpadding="3" cellspacing="0"
!style="width:50px;" | Type
!style="width:80px;" | Usage
!style="width:200px;" | Result
|-
| forum
| <pre>{{LDSTech|forum=50}}</pre>
| {{LDSTech|forum=50}}
|-
| thread
| <pre>{{LDSTech
|thread=1438
}}</pre>
| {{LDSTech
|thread=1438
}}
|-
| post
| <pre>{{LDSTech
|post=13222
|title=Wiki LDSClerks.com Status 18 June 2008
}}</pre>
| {{LDSTech
|post=13222
|title=Wiki LDSClerks.com Status 18 June 2008
}}
|-
| (none)
| <pre>{{LDSTech}}</pre>
| {{LDSTech}}
|}

[[Category:Templates|LDSTech]]
</noinclude>

Template talk:TechForum

2009-04-13T00:40:00Z

Mkmurray: typo

Template talk:TechForum

2009-04-13T00:39:44Z

Mkmurray: RE: /* Adding a Title Parameter */

Template talk:TechForum

2009-04-13T00:30:50Z

Mkmurray: /* Adding a Title Parameter */ typo

Template talk:TechForum

2009-04-13T00:30:11Z

Mkmurray: RE: /* Adding a Title Parameter */

Template talk:TechForum

2009-04-12T15:42:33Z

Mkmurray: Add a Title Parameter?

Template:TechForum

2009-04-12T15:34:35Z

Mkmurray:

<includeonly>{{#if: {{{post|}}} | [http://tech.lds.org/forum/showthread.php?p={{{post}}}#post{{{post}}} Post] on | {{#if: {{{thread|}}} | [http://tech.lds.org/forum/showthread.php?t={{{thread}}} Thread] on | {{#if: {{{forum|}}} | [http://tech.lds.org/forum/forumdisplay.php?f={{{forum}}} Forum] on }} }} }} [http://tech.lds.org LDS Tech] [http://tech.lds.org/forum Discussion Forum]</includeonly><noinclude>
== Purpose ==
This template is used to easily reference items on the [http://tech.lds.org LDS Technology Web Site] forums.

== Usage ==
This template takes one of three optional parameters (or no parameter):
* '''post''': the ID of a post
* '''thread''': the ID of a thread
* '''forum''': the ID of a forum

=== Examples ===
{| border="1" cellpadding="3" cellspacing="0"
!style="width:50px;" | Type
!style="width:80px;" | Usage
!style="width:200px;" | Result
|-
| forum
| <pre>{{LDSTech|forum=50}}</pre>
| ''General Clerks Discussion'' {{LDSTech|forum=50}}
|-
| thread
| <pre>{{LDSTech|thread=1438}}</pre>
| ''Wiki LDSClerks.com Status'' {{LDSTech|thread=1438}}
|-
| post
| <pre>{{LDSTech|post=13222}}</pre>
| ''Wiki LDSClerks.com Status 18 June 2008'' {{LDSTech|post=13222}}
|-
| (none)
| <pre>{{LDSTech}}</pre>
| {{LDSTech}}
|}

[[Category:Templates|LDSTech]]
</noinclude>

TechWiki talk:Manual of Style

2009-04-07T14:43:55Z

Mkmurray: RE: /* We need a LDS Tech style guide */

Main Page

2009-02-18T17:48:08Z

Mkmurray: /* Current Projects */

__NOTOC__
==Welcome to the LDSTech Wiki==

The purpose of this wiki is for the Church and community members to collaborate on various technology projects sponsored by the Church. We invite all to participate in these projects.

<table width="100%" cellspacing="0" cellpadding="0">
<tr valign="top">
<td width="50%">




<div style="margin: 0px 5px 10px 0px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">
===Announcements===
</div>
<div style="padding: 0px 5px 0px 5px;">
* '''Notice:''' Subversion, the Java repositories, Jira, and this whole Wiki are now accessed via HTTPS instead of HTTP. Please make sure you updated your links to represent this change.
* We have posted the first bit of documentation on the [[LDS Java Stack]]. More to come!
* Many people ask where Subversion is? The Subversion URL is https://tech.lds.org/svn. We have two projects posted there (HT/VT and Timeline).
* We have added Syntax Highlighting to the wiki so that if you paste source code snippits, they will show up with highlights. Read more about the syntax on how to add your source code and get the highlighting working [[metawikipedia:Extension:SyntaxHighlight_GeSHi|here]].
</div>
</div>





<div style="margin: 10px 5px 0px 0px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Current Projects===
</div>
<div style="padding: 0px 5px 0px 5px;">
Currently the Church is asking for help in collaborating on the following projects.

* [[Home Teaching / Visiting Teaching Application]]
* [[Church Historical Timeline Application]]
* [[IPhone Scriptures Application]]

Should you have any questions or suggestions please contact [[User:Welchtc | Tom Welch]]
</div>
</div>


</td>

<td>




<div style="margin: 0px 0px 10px 5px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Requirements for Participation===
</div>
<div style="padding: 0px 5px 0px 5px;">
In order to participate and contribute to any projects that the Church sponsors, each individual must:
# Agree to and fill out the [http://tech.lds.org/index.php?option=com_content&task=view&id=140&Itemid=61 Individual Contributors License Agreement].
# Have an [http://ldsaccount.lds.org LDS Account]. To do so you must know your membership number and confirmation date. '''Note:''' Having an LDS Account is not the same as having a login to the Local Unit Web Sites. Please follow the [http://ldsaccount.lds.org LDS Account link] to get your account. LDS Account is the new unified authentication being deployed to all applications at the Church.
</div>
</div>





<div style="margin: 10px 0px 0px 5px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Current Volunteer Needs===
</div>
<div style="padding: 0px 5px 0px 5px;">
* '''UI and Web designers''' for the [[Home_Teaching_/_Visiting_Teaching_Application#Current_Needs | Home Teaching / Visiting Teaching project]].
* '''QA Engineers''' for the [[Home_Teaching_/_Visiting_Teaching_Application#Current_Needs | Home Teaching / Visiting Teaching project]].

Our new [[LDSTech:Community_Portal|Community Portal]] is the central place for coordinating volunteer efforts. Go there to find ways you can contribute.
</div>
</div>

</td>

</tr>
</table>

==New to LDSTech Wiki?==
LDSTech Wiki uses [[wikipedia:MediaWiki|MediaWiki]], a web-based [[wikipedia:wiki|wiki]] software popularly known for its use in [[wikipedia:Main_Page|Wikipedia]]. Consult the [[metawikipedia:Help:Contents|User's Guide]] for information on using wiki software. Here are some quick tips to help you get going.

* '''Searching for Articles''': To search for an article or some content within the wiki, type in your search phrase in the search box (where it says "wiki search..."). Then you can either press the '''Go''' or '''Search''' button to perform your search. The '''Go''' button will first search for an article with the exact name as you typed in. Then it will find all articles with the words you typed in. The '''Search''' button searches all articles for any of the words you typed in.
* '''Creating Articles''': To create an article, simple type in the search box the name of the article and press the '''Go''' button. A search will be performed with the exact article name as the one you typed in. If an article with the exact name is not found, there will be a link on the search results page that will allow you to create the article.
* '''Editing Articles''': To edit an article, simply press the '''Edit''' tab at the top of the article. You edit articles using "[[wikipedia:Wikitext|wikitext]]". [[metawikipedia:Help:Formatting|Here]] is a quick reference of formatting commands for your convenience.
* '''Discussing Articles''': If you want to discuss an article,click the '''Discussions''' tab at the top of an article and type in your comments.
* '''Red vs Blue Hyperlinks''': Red links are links to articles within the wiki that have not been created yet. Simply click on the link and you can then create the article. Blue links are links to wiki articles already created or links to external sites.

Main Page

2009-01-26T21:35:11Z

Mkmurray: /* Announcements */

__NOTOC__
==Welcome to the LDSTech Wiki==

The purpose of this wiki is for the Church and community members to collaborate on various technology projects sponsored by the Church. We invite all to participate in these projects.

<table width="100%" cellspacing="0" cellpadding="0">
<tr valign="top">
<td width="50%">




<div style="margin: 0px 5px 10px 0px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">
===Announcements===
</div>
<div style="padding: 0px 5px 0px 5px;">
* '''Notice:''' Subversion, the Java repositories, Jira, and this whole Wiki are now accessed via HTTPS instead of HTTP. Please make sure you updated your links to represent this change.
* We have posted the first bit of documentation on the [[LDS Java Stack]]. More to come!
* Many people ask where Subversion is? The Subversion URL is https://tech.lds.org/svn. We have two projects posted there (HT/VT and Timeline). [[User:Rhusted|Rhusted]] 14:59, 15 October 2008 (UTC)
* We have added Syntax Highlighting to the wiki so that if you paste source code snippits, they will show up with highlights. To read more about the syntax on how to add your source code and get the highlighting working, visit [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi this] link.
</div>
</div>





<div style="margin: 10px 5px 0px 0px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Current Projects===
</div>
<div style="padding: 0px 5px 0px 5px;">
Currently the Church is asking for help in collaborating on the following projects.

* [[Home Teaching / Visiting Teaching Application]]
* [[Church Historical Timeline Application]]

Should you have any questions or suggestions please contact [[User:Welchtc | Tom Welch]]
</div>
</div>


</td>

<td>




<div style="margin: 0px 0px 10px 5px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Requirements for Participation===
</div>
<div style="padding: 0px 5px 0px 5px;">
In order to participate and contribute to any projects that the Church sponsors, each individual must:
# Agree to and fill out the [http://tech.lds.org/index.php?option=com_content&task=view&id=140&Itemid=61 Individual Contributors License Agreement].
# Have an [http://ldsaccount.lds.org LDS Account]. To do so you must know your membership number and confirmation date. '''Note:''' Having an LDS Account is not the same as having a login to the Local Unit Web Sites. Please follow the [http://ldsaccount.lds.org LDS Account link] to get your account. LDS Account is the new unified authentication being deployed to all applications at the Church.
</div>
</div>





<div style="margin: 10px 0px 0px 5px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Current Volunteer Needs===
</div>
<div style="padding: 0px 5px 0px 5px;">
* '''UI and Web designers''' for the [[Home_Teaching_/_Visiting_Teaching_Application#Current_Needs | Home Teaching / Visiting Teaching project]].
* '''QA Engineers''' for the [[Home_Teaching_/_Visiting_Teaching_Application#Current_Needs | Home Teaching / Visiting Teaching project]].

Our new [[LDSTech:Community_Portal|Community Portal]] is the central place for coordinating volunteer efforts. Go there to find ways you can contribute.
</div>
</div>

</td>

</tr>
</table>

==New to LDSTech Wiki?==
LDSTech Wiki is built upon MediaWiki, which is the same wiki software that runs [http://www.wikipedia.org wikipedia]. Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using this wiki software. Here are some quick tips to help you get going.

* '''Searching for Articles''': To search for an article or some content within the wiki, type in your search phrase in the search box (where it says "wiki search..."). Then you can either press the '''Go''' or '''Search''' button to perform your search. The '''Go''' button will first search for an article with the exact name as you typed in. Then it will find all articles with the words you typed in. The '''Search''' button searches all articles for any of the words you typed in.
* '''Creating Articles''': To create an article, simple type in the search box the name of the article and press the '''Go''' button. A search will be performed with the exact article name as the one you typed in. If an article with the exact name is not found, there will be a link on the search results page that will allow you to create the article.
* '''Editing Articles''': To edit an article, simply press the '''Edit''' tab at the top of the article. You edit articles using "wikitext". [http://www.mediawiki.org/wiki/Help:Formatting Here] is a quick reference of formatting commands for your convenience.
* '''Discussing Articles''': If you want to discuss an article,click the '''Discussions''' tab at the top of an article and type in your comments.
* '''Red vs Blue Hyperlinks''': Red links are links to articles within the wiki that have not been created yet. Simply click on the link and you can then create the article. Blue links are links to wiki articles already created or links to external sites.

User talk:Techgeek775

2009-01-12T05:41:34Z

Mkmurray: Response to Techgeek775's User Talk Page

I'm fairly new to programming (a little over a year of hobbiest coding, self taught) but consider myself proficient with the Java language and Swing libraries, as well as many of the other common packages. I'm quickly picking up C# at the moment, and eventually plan on learning C++.

I'm entirely new to this website, but am interested in helping with a project. If someone could give me a pointer (no pun intended) to where I could join a project or where I'm supposed to put info about myselft, it would be much appreciated and dereferenced. --[[User:Techgeek775|Techgeek775]] 02:22, 12 January 2009 (UTC)

:Hello and welcome! The best area to put your profile information would be on your [http://tech.lds.org/wiki/index.php?title=User:Techgeek775&action=edit User Page]. This page is the "Talk Page" or discussion page about your User Page. Every page on a wiki has an accompanying discussion page where questions and comments can go back and forth between community members about the information on the wiki page.

:Here is a great page to start reading about the Community and wiki guidelines we are trying to follow: [http://tech.lds.org/wiki/index.php/LDSTech:Community_Portal Community Portal]. The two most active (well, relatively active) projects are listed in the [http://tech.lds.org/wiki/index.php/Main_Page#Current_Projects Current Projects section of the wiki's Main Page]. Also, the [http://tech.lds.org/wiki/index.php/LDS_Java_Stack LDS Java Stack] is the Church's own stack of technologies that many Community projects will likely be based on, so this is also an informative read. Hope this info helps you get started, and good luck and have fun! --[[User:Mkmurray|Mike Murray]] 05:41, 12 January 2009 (UTC)

User:Spotmax

2008-11-13T18:31:08Z

Mkmurray: /* Wolfgang Schmullius */

== Wolfgang Schmullius ==

Chiemseestr. 88, 83233 Bernau am Chiemsee, Germany

I'm working on the [[Church Historical Timeline]] filling the Germany niche.

If you want to help me, please mail to wolfgang@spotmax.net

Talk:Ward & Stake Directory Application

2008-10-24T16:25:27Z

Mkmurray: /* Reasoning for this Community Project? */

== Reasoning for this Community Project? ==

Not to be rude, but I don't understand the purpose of this project. I do understand the helpfulness in getting quality membership directories and the like, but I don't understand why the Community would work on this. I would have thought these proposed enhancements would be going into LUWS 2.0 where they would belong. Again, no disrespect intended; just confused and concerned. Thanks. -- [[User:Mkmurray|Mike Murray]] 16:25, 24 October 2008 (UTC)

TechWiki talk:Guidelines

2008-10-16T15:52:42Z

Mkmurray: RE: /* Template:Need Input */

TechWiki:Guidelines

2008-10-03T22:44:13Z

Mkmurray: /* Headings */

{{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 is in need of input or discussion. It has a parameter that is a brief description of the issue or 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:Guidelines

2008-10-03T22:40:57Z

Mkmurray: /* Editing Pages */ - Please don't use H1 headings in articles!

{{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 guid 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 is in need of input or discussion. It has a parameter that is a brief description of the issue or 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:Guidelines

2008-10-03T21:53:37Z

Mkmurray: /* 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.

=== 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 is in need of input or discussion. It has a parameter that is a brief description of the issue or 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:Community portal

2008-10-03T21:52:41Z

Mkmurray: /* Help Out */

The '''Community Portal''' is the central place to find out what's happening on the [[Main_Page | LDS Tech Wiki]] (see the [http://en.wikipedia.org/wiki/Wikipedia:Community_portal Community Portal] on [http://en.wikipedia.org/wiki/ Wikipedia] for a model). Learn what tasks need to be done, or get or post news about recent events or current activities. If you think something should be done, add it to the lists here, even if you don't have the time or expertise to create the content yourself.

== Community Bulletin Board ==

=== News ===
* There is now a [[Guidelines]] page. Please review it as it gives helpful guidance on how pages should be created and edited on this wiki.
* There is also a draft of the [[Development Project Guidelines]] page, which describes the process for creating a project, as well as the recommended structure for its wiki pages.

== Help Out ==
The [[Guidelines]] and [[Development Project Guidelines]] pages are currently in a draft stage. We welcome discussion and refinement of these guidelines.

=== Tasks ===
Here are some tasks you can do:

* '''Wikify''': Follow the [[guidelines|Guidelines]] to make articles use links, headings, sources, templates, and categories in a standard way.
* '''Annotate''': Use templates to flag articles that need attention if you are unable to make the necessary changes.
** {{tl|Stub}} flags articles or sections that are incomplete and need to be expanded
** {{tl|Draft}} flags articles that are in a Draft stage and not approved as authoritative yet
** {{tl|Edit}} flags articles or sections that need to be rewritten
** {{tl|ToDo}} flags articles or sections that have tasks that need to be accomplished
** {{tl|Need Input}} flags articles or sections that are in need of input
** {{tl|Unresolved}} flags Talk Page discussions that are currently unresolved
** {{tl|Resolved}} flags Talk Page discussions that have been resolved
* '''Create''': If there is a topic you think needs to be addressed, create a new article. If your page is related to a project, please follow the [[Development Project Guidelines]]. Also, a red link anywhere on this wiki indicates that someone thought an article ''should'' exist, but they didn't have the time or expertise to write it themselves. If you can, get that topic started by writing the first draft yourself. You can see the entire list of such articles at [[Special:Wantedpages]].
* '''Expand''': Some articles may be incomplete stubs which should be improved by fleshing out the content. You can see the entire list of such articles at [[:Category:Stubs]].
* '''Resource''': Add attachments or links to sample documents, spreadsheets, or templates that will add breadth and depth to the articles.
* '''Copyedit''': Fix grammar, punctuation, style to be more accurate, and in accordance with the [[LDS Tech Style Guide]].
* '''Source''': 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]].
* '''See Also''': Adding "See Also" sections to the end of articles can improve navigation
* '''[[LDSTech:Copyrights]]''': Write/Edit this page, which is linked to from the Editing page that appears whenever you edit a page; this should briefly explain Public Domain, Fair Use, and improper use of copyrighted materials.
* '''User Page''': Add your own user page to give people some idea of your background and experience.

=== Needs Attention or Action ===
For a list of pages needing discussion, input, or specific actions, review the following category pages:

:[[:Category:Need Input]]
:[[:Category:ToDo]]

=== Cleanup ===
For a list of pages needing cleanup, review the following category pages:

:[[:Category:Stubs]]
:[[:Category:Pages to be edited]]
:[[:Category:Drafts]]
:[[:Category:Unresolved]]

== Guidelines, Help, and Resources ==
=== Guidelines ===
* Consult the [[Guidelines]] page so that the content you create can be consistent across the wiki.
* For new projects, consult the [[Development Project Guidelines]] page.

=== Help ===
[[Help:Contents]]: Flesh out this page which is linked to from the main navigation panel displayed to the left of every page, as well as from the Search Results page.

[[Category:LDS Tech Administration|Community Portal]]

Category:Need Input

2008-10-03T21:51:26Z

Mkmurray:

This category is applied to articles or sections that are in need of input or discussion. Generally the category is applied by using the {{tl|Need Input}} template.

[[Category:LDS Tech Administration]]

TechWiki:Guidelines

2008-10-03T21:44:01Z

Mkmurray: /* Template:ToDo */

{{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.

=== 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 is in need of authoritative input. It has a parameter that is a brief description of the issue or 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:Guidelines

2008-10-03T21:43:38Z

Mkmurray: Added ToDo template to Guidelines

{{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.

=== 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 is in need of authoritative input. It has a parameter that is a brief description of the issue or 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 teh {{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]]

Category:ToDo

2008-10-03T21:38:30Z

Mkmurray: New page: This category is applied to articles that have tasks that need to be carried out. Generally the category is applied by using the {{tl|ToDo}} template. Category:LDS Tech Administration

This category is applied to articles that have tasks that need to be carried out. Generally the category is applied by using the {{tl|ToDo}} template.

[[Category:LDS Tech Administration]]

Template:ToDo

2008-10-03T21:36:37Z

Mkmurray:

{| style="margin: 0 10%; border-collapse: collapse; background: #FBFBFB; border: 1px solid #aaa; border-left: 10px solid #006600;"
|-
|
| style="padding: 0.25em 0.5em; width: 100%;" | '''To Do:''' {{{1|}}}
|}
<includeonly>{{{category|[[Category:ToDo]]}}}</includeonly><noinclude>
== Documentation ==
This template can be added to any article as a reminder of items still to do on the article to complete it. Many times an author may be able to contribute only portions of the article. Applying this template will allow others to add the missing necessary content.

=== Categorization ===
Pages that include this template will be automatically included in the [[:Category:ToDo]] (unless you supply the "category=" parameter, as described below).

=== Usage ===
Simply insert the template near the top of the article by typing '''<nowiki>{{ToDo|your To Do comments here}}</nowiki>'''. In general you should supply the tasks that need to be done, e.g., '''<nowiki>{{ToDo|Create a detailed instructions page on how to configure this application.}}</nowiki>'''. If you are using the template only for documentation purposes (such as on the [[Guidelines]] page), you can suppress the "To Do" category by adding a blank "category" parameter, e.g., '''<nowiki>{{ToDo|An item that needs to be done.|category=}}</nowiki>'''.

[[Category:Templates|ToDo]]
</noinclude>

Template:Edit

2008-10-03T21:36:28Z

Mkmurray:

{| style="margin: 0 10%; border-collapse: collapse; background: #FBFBFB; border: 1px solid #aaa; border-left: 10px solid #ff7700;"
|-
|
| style="padding: 0.25em 0.5em; width: 100%;" | This page <b>may need to be edited</b> for quality to meet the LDS Tech [[guidelines]].<br/>{{{1|}}}
|}

<includeonly>{{{category|[[Category:Pages to be edited]]}}}</includeonly><noinclude>
== Documentation ==
This template is to be applied to pages that need to be edited. If, however, you have the capability to clean up the page yourself, please consider cleaning up the page directly, without applying the template and hoping someone will clean it up later.

=== Categorization ===
Pages that include this template will be automatically included in the [[:Category:Pages to be edited]] (unless you supply the "category=" parameter, as described below).

=== Usage ===
Simply insert the template near the top of the article by typing '''<nowiki>{{Edit}}</nowiki>'''. In general you should supply the reason the cleanup is needed, e.g., '''<nowiki>{{Edit|Remove first person}}</nowiki>'''. If you are using the template only for documentation purposes (such as on the [[Guidelines]] page), you can suppress the "Pages to be edited" category by adding a blank "category" parameter, e.g., '''<nowiki>{{Edit|Remove first person|category=}}</nowiki>'''.

[[Category:Templates|Edit]]
</noinclude>