TechWiki - User contributions [en]

Tech Broadcasts

2012-02-01T17:21:08Z

Cottrells: move </div> tag so table uses full width

[[File:Broadcast-wiki-banner-sm.png|278px|right]]

We will have an LDSTech Broadcast on the first Friday of each month (except in April). The annual [[LDSTech Conference]] is also broadcast (typically the week before April general conference). The locations are listed below, but anyone can join remote.

{{NextEvent|Next Broadcast: 3 FEB 2012 @ 12:00pm MST "Leader and Clerk Resources Now Available on LDS.org"}}

[https://webchat.freenode.net/?channels=%23ldstech Click here to join the live chat via IRC]

__TOC__

<div id="indent140">
[[file:learn.png|left]]

== When do I show up? ==

You can show up at 12pm to watch the Broadcast. Dress code for on-site participants at the ROB is business casual to casual.

== Where are we broadcasting from? ==
In the Zion Room at the ROB (Riverton Office Building). You are welcome to join us live. It is located at 3740 West Market Centre Drive, Riverton, Utah 84065. You can [http://maps.google.com/maps?hl=en&sugexp=ldymls&xhr=t&q=3740+west+market+center+drive&cp=0&qe=Mzc0MCB3&qesig=vQt4vNoIngfE9W5VTvtXXQ&pkc=AFgZ2tmwGiZnPMTPAIey56vk_z_c9Ytejibup3Pi6KpD_qi1nkTXFp9pcwyVhp6RtNd5ITnMZBitqFmNQ_ERJBbsos0cfj_ZNA&nord=1&bav=on.2,or.r_gc.r_pw.&ion=1&um=1&ie=UTF-8&hq=&hnear=3740+S+Market+Centre+Dr,+Riverton,+UT+84065&gl=us&ei=cZ7BTcb8K4bk0QGDs6C4Cg&sa=X&oi=geocode_result&ct=title&resnum=1&sqi=2&ved=0CBYQ8gEwAA see a map here.] The [http://www.rideuta.com/ridinguta/routes/routefinder.aspx?r=f518 F518 bus] runs to this location, or you may provide your own transportation to and from the building. All Service Day activities will be held on the first floor, with signs to guide you. We are toying with the idea of broadcasting from other LDSTech Chapter Locations, but for now we are only doing it from the ROB.

<hr>

[[File:contribute.png|left]]
== 2011-12 LDSTech monthly broadcast calendar ==

We will have a 1 hour broadcast that will cover both projects and introduce products and technologies to the community. [[Media:LDSTech_Broadcast.ics|Add this event to your calendar]].
</div>

{|class="ldstechtable sortable"
!Date
!Time
!Stream
!Presenter
|-
| 2012-12-07
| 12:00pm - 1:00pm MST
| TBD
| TBD
|-
| 2012-11-02
| 12:00pm - 1:00pm MST
| TBD
| TBD
|-
| 2012-10-05
| 12:00pm - 1:00pm MST
| TBD
| TBD
|-
| 2012-09-07
| 12:00pm - 1:00pm MST
| TBD
| TBD
|-
| 2012-08-03
| 12:00pm - 1:00pm MST
| TBD
| TBD
|-
| 2012-07-06
| 12:00pm - 1:00pm MST
| TBD
| TBD
|-
| 2012-06-01
| 12:00pm - 1:00pm MST
| TBD
| TBD
|-
| 2012-05-04
| 12:00pm - 1:00pm MST
| TBD
| TBD
|-
| 2012-03-29
| All-Day 29-30
| TBD
| Annual [[LDSTech Conference]]
|-
|2012-03-02
|12:00pm - 1:00pm MST
|TBD
|Meetinghouse Internet Upgrade
|-
| {{NextEvent|2012-02-03}}
| {{NextEvent|12:00pm - 1:00pm MST}}
| TBD
| TBD
|-
| 2012-01-06
| 9:00am - 10:00am MST
| [http://tech.lds.org/pics/misc/LDSTech_6JAN2011.mp4 Watch it now]
| Stephan Heilner - iOS Developer, Bible Videos / iPad
|-
| 2011-12-02
| 9:00am - 10:00am MST
| [http://broadcast.lds.org/ics/techtalk/2011-12-02.html Watch it now]
| Mike Jones - Android Developer, LDS Gospel Library
|-
| 2011-11-04
| 9:00am - 9:00pm MST
| [http://tech.lds.org/pics/misc/November2011TechDayConference.mpg Watch it now]
| Lee Gibbons - Director lds.org, http://lds.org
|-
| 2011-10-07
| 9:00am - 9:00pm MST
| [http://tech.lds.org/pics/misc/October2011TechDayConference.mp4 Watch it now]
| Hal Rushton - Blackberry & Feature Phone Developer, Gospel Library
|-
| 2011-09-02
| 9:00am - 9:00pm MST
| [https://tech.lds.org/pics/misc/2Sep11_201108.mp4 Watch it now]
| Steve Knudsen - Manager Field Relationships, http://camping.lds.org
|-
| 2011-08-05
| 9:00am - 9:00pm MST
| [https://tech.lds.org/pics/misc/5Aug11_201108-201108.mp4 Watch it now]
| Kathryn Grant - Developer, Bishops Storehouse
|-
| 2011-07-01
| 9:00am - 9:00pm MST
| [https://tech.lds.org/pics/misc/1July11_201107-201107.avi Watch it now]
| Tim Riker - LDSTech Guru, Bishop's Storehouse
|-
| 2011-06-03
| 9:00am - 9:00pm MST
| [https://tech.lds.org/pics/misc/3June11_201106-201106.asf Watch it now]
| Howard Olson, Engineer, GreenHopper for Jira (Agile Project Management)
|-
| 2011-05-06
| 9:00am - 9:00pm MST
| [https://tech.lds.org/pics/misc/6May11_201105-201105.asf Watch it now]
| Tom Welch - John R. Moyle Award Recipient
|-
| 2011-03-31
| All day Mar 31 - Apr 1
| no stream
| [[LDSTech 2011]]
|}

Note: On a PC, the stream will play through Windows Media Player. If you're using a Mac to view the stream, make sure you use Quicktime with the Flip4Mac plugin installed. If you experience audio issues, make sure your volume is turned up. If you are still having trouble connecting, you may want to join us on [[IRC]] or email [[User:TimRiker]]

[[Category:LDSTech Service Days]]

TechWiki talk:Guidelines

2012-01-17T17:34:40Z

Cottrells: /* Appropriate content section */ new section

== 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 think with emailing interface that we could in fact make a specific web address in terms of like someone.lds.org on the end of the email to signify that it is pertaining to the church. I can make all these if needed so that emails do get answered and not lost. It would in essence design our own email system that would be in specific to the church.

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)

:: It's certainly possible, but enforcing those e-mail requirements would require customizations that only Tom (as far as I know) could do. Only Tom could tell if people have not supplied e-mail addresses, but have simply chosen not to receive e-mail. Any changes we would make to these settings would not affect current users, but if they supplied e-mail addresses, then at least Tom could e-mail them and request that they start accepting e-mails. -- [[User:Aebrown|Aebrown]] 18:33, 17 June 2009 (UTC)

:::I think a polite notice on a users talk page, directing them to this article could help. When the user next logs into the site a notice that a message has been left, will be displayed at the top of each page they view. --[[User:Cottrells|Steve]] 19:35, 17 June 2009 (UTC)

:I wonder if it might be possible to change the default skin to provide a short note next to the minor edit checkbox and near the Save Page and Show Preview buttons advising about their use and a pointer to the guidelines page. Of course, that's something only Tom could do as well. -- [[User:Eblood66|Eric Blood]] 20:56, 17 June 2009 (UTC)

== Appropriate content section ==

I feel that the new section on [[LDSTech:Guidelines#Appropriate content|Appropriate content]] is well written and is a timely addition to this article. [[User:Cottrells|Steve]] 17:34, 17 January 2012 (UTC)

Tech.churchofjesuschrist.org

2011-06-13T16:53:51Z

Cottrells: add cat

The current state and future of tech.lds.org

==Purposes of tech.lds.org==
Many people know of the resources for ward clerks and technology specialists on tech.lds.org. The forum and wiki contain myriad conversations and a knowledge base for technology related ward and stake issues that cannot be found anywhere else. Tech.lds.org is an indispensable resource to those seeking technology support in their demanding and difficult callings.

Tech.lds.org also serves as an avenue to facilitate community participation in development of Church technology projects. The Church has many technology [[Community_Projects|projects]] to complete to meet the needs of an ever-growing, world-wide church. The Church seeks the help of the tech.lds.org community with this tremendous undertaking.

==Project Objectives==
The purpose of this project is to continue to improve the '''self-support''' services provided through tech.lds.org. It is also to expand the ability to '''partner''' with the tech.lds.org community on Church technology projects.

===Self-Support===
The '''forum and wiki''' are the tools for '''self-support''' on the site. The wiki provides a codified knowledge base for officially approved uses and scenarios for Church related technology. In the forum, users can post questions and get answers from other forum users. They can also search previous remarks from users. Problems that aren't answered in the wiki can be researched in the forum.

===Community Involvement===
The Church invites participants to review the list of [[Community_Projects|projects]] and '''volunteer''' where they have time and inclination.

==Community Collaboration==
Tech.lds.org provides a collection of tools, held together by glue and sawdust, to enable community collaboration.

===Issue Tracking===
'''JIRA''' is used to track issues on community projects. After joining a project users will have access to that project in JIRA.

===Source Control===
Tech.lds.org currently has source control available with Subversion ('''SVN'''). Git support may be added in the near future. Users have access to the source through the project page. Users do not automatically receive commit access to Subversion, but should contact a project manager to obtain access. Users can create JIRA issues and attach patches to those JIRA tickets.

===Skills Profile===
Users of tech.lds.org can identify which technologies they are comfortable with or interested in learning. This aids project managers in identifying people who will be able to contribute to their project. It is '''not necessary to fill out the skills profile''' to join projects.

===Projects===
The list of available community projects is visible to those who sign the '''contributor agreement'''. Projects are created by sponsors internal to The Church. Community members can join projects they are interested in and participate at a level they are comfortable with. After joining a project, users will be able to comment on and add JIRA tickets related to that project. They'll also be able to submit patches to the project through JIRA. Volunteers can leave a project at any time.

====Contributor Agreement====
Those willing to contribute to Church technology projects must sign the '''contributor license agreement''' before they will be able to start.

===Content Management===
'''Joomla''' is used to manage and maintain the site, the users and the projects.

==Key Information==
===Communication===

====Weekly Meeting====
An open meeting is held '''weekly on Fridays, 10:30-11:30am Mountain Time'''.

'''How to join the meeting''':

When: Occurs every Friday effective 5/20/2011 until 12/16/2011 from 10:30 AM to 11:30 AM (UTC-07:00) Mountain Time (US & Canada).
Where: CR-ROB-3244-TeamRoom

Note: The GMT offset above does not reflect daylight saving time adjustments.

Meeting URL: http://meetingplace.ldschurch.org/a/b7b27674a89f687bd589288936befc10
Dial in Numbers: 801-240-2663 (Local/International) or 877-453-7266 (US Toll-free)

Join the meeting:

# Go to http://meetingplace.ldschurch.org/a/b7b27674a89f687bd589288936befc10 or http://meetingplace.ldschurch.org and enter your Meeting ID 1773 and click the "Attend Meeting" button
# If requested, Sign in with your LDS Account or as a Guest
# Select the desired "Connect Me" options and enter the phone number that you want MeetingPlace to call you at
# Click the Connect button

To Attend the Conference Without Using your Computer:

# Dial into 801-240-2663 (Local/International) or 877-453-7266 (US Toll-free)
# Follow the prompts to enter the Meeting ID 1773 and join the meeting

Additional Help:

* Frequently Asked Questions at http://meetingplace.ldschurch.org/FAQ/
* Online Training at http://meetingplace.ldschurch.org/training/training.htm

'''First-time users''' should run the http://meetingplace.ldschurch.org/test/ to verify they can participate in a web meeting.

====IRC====
The preferred method of communication regarding all LDSTech projects is in #ldstech channel on irc.freenode.net. [http://colloquy.info/ Colloquy] is a good IRC client for Mac and [http://www.trillian.im/ Trillian] is a good one for PC. See [[IRC]] for more details.

====Google Group====
We are working on getting our own Church hosted Google Group. Until then we have one hosted with Google:

https://groups.google.com/forum/#!forum/ldstech-development-and-design

===Source code===
The code for tech.lds.org is available:<br>
https://code.lds.org/svn/ldstech/trunk.

===Issue tracking===
Issues, tasks, and bugs can be found in the LDSTech instance:<br>
https://tech.lds.org/jira/browse/LDSTECH

===Test system===
The dev site: https://tech.lds.org/ldstech/joomla/

===Internal Team Members===
* [[user:smootar|Alan Smoot]]
* [[user:timriker|Tim Riker]]
* [[user:tdeforest|Tom DeForest]]
* Elder Aaron Monson
* [[user:joshrees|Josh Rees]]
* Nathaniel Gustafson

==Requirements==
* XAMPP - PHP/MySQL Development - http://www.apachefriends.org/en/xampp.html

[[Category:Websites]]

Facebook

2011-06-13T16:48:10Z

Cottrells: edit cat

With over 500 million active users and half of those logging in at least once daily, Facebook is an excellent tool for sharing the Gospel. With over 70 languages and 70% of Facebook being outside the United States, Facebook can let you share with friends wherever they are.

* [[Understanding Facebook]]
* [[Helpful Facebook Stats]]
* [[How to set up a Facebook page]]
* [[Moderating Facebook comments]]
* [[Formulating a successful posting strategy]]
* [[Understanding and using Facebook insights]]
* [[Building a Facebook ad strategy]]
* [[Using Facebook places and deals]]
* [[Understanding Facebook Credits]]
* [[Facebook Programming]]

[[Category:Facebook]]

Category:Social networking

2011-06-13T16:47:28Z

Cottrells: add cat

{{catmain|Sharing the Gospel online}}

[[Category:Family safety]]

Basic blog features

2011-06-13T16:37:50Z

Cottrells: add cat

The most important features/functions of a blog include the following:

- Create post option - allows you to begin and publish a new post. Be sure to pick a descriptive title. (Note: You can publish immediately or schedule a time in the future for the post to be published.)

- Insert link function: If you use your mouse to highlight text, you can then click on the link button and paste a link URL to which you want that text to be able to point. (Sometimes you have the option to have the link open in a new window. Keep an eye open for that.)

- Insert photo and/or video option: Wherever you put your cursor, the video or photo will be inserted. You can upload a photo from your computer or put a link to an image. If you have an original video, you can upload from your computer. If you only want to link to a video (such as on YouTube), simply insert a link as described above.

However, if you want to have a video from YouTube or another site embedded into your blog post, you'll need to get what is called the embed code. Look for the embed code on the video source page. You can also look for the symbol <>. Copy and paste the code into your blog post. Note: You need to be in the editing mode where you can see the HTML code. Usually, you can choose between editing in "visual" or "compose" mode, or in code or HTML mode.

- Comment options: There are various ways to handle comments. They can be completely turned off. They can be moderated (you can get email notifications when someone makes a comment). You can require that commenters do some sort of identity validation to avoid spam. Look at your comment options in your tool to see what you can do. If you don't moderate or have some sort of validation process, be sure to watch comments closely.

A few other features include the following:

- The "more" function: a marker in the post that tells the blog to only display the content before the marker on your blog. Think of it as a "teaser" for your post. This comes in handy if you want people to quickly see several posts on your blog's home page. If you don't use this feature, the entire post will be displayed on your blog.

[[Category:Social networking]]

Inner City Project

2011-06-13T16:36:44Z

Cottrells: add cat

The Salt Lake Inner City Project was organized and functions for the purpose of assisting the poor and needy under the direction of bishops and branch presidents by teaching principles of temporal self-reliance that leads to temporal and spiritual well-being, and in bringing souls unto Christ. Approximately 600 Church-service missionaries are currently serving in the greater Salt Lake City area to assist bishops and branch presidents of 26 stakes to achieve its purpose of assisting the poor and needy.

Currently, the Inner City Project serves the leaders and members in the greater Salt Lake City area. But, the new website is intended to be a foundation to serve other potential inner city projects throughout the world.

== Features of the Inner City Website ==
=== Administration ===
*Who are the missionaries serving in the inner city project
*Where are the missionaries serving from (i.e. home ward and stake, and who are their bishops and stake presidents)
*What ward or branch is the missionary assigned to serve in
*Reports for monitoring missionary services

=== Resources for Missionaries ===
*Storehouse of Specialist (what services are available for the missionaries to use to assist the needy)
*Guidelines on using the Storehouse of Specialist
*Links to Church resources (i.e. Provident Living)
*Links to community resources (i.e. 211 directory, State of Utah Community Services, Utah Jo Services, etc...)

=== Missionary Reporting ===
*Online form for missionaries to submit their monthly reports

== Skills Needed for Project ==
=== mySQL database designer/engineer ===
=== php developer ===
*the UI framework will be using ICS's IxF framework
=== Authentication and Authorization ===
*the project will use LDS Accounts and WAM for its authentication and authorization
=== WordPress Guru ===
*embedding Wordpress into the php website for a manual and for a blog
=== Google Calendar Expert ===
*embedding calendar
*programmatically logging in as one of three users: admin, stake lead or missionary

[[Category:Projects]]

Helpful articles and tutorials for sharing the gospel online

2011-06-13T16:35:41Z

Cottrells: add cat

These are great third party resources for learning about sharing the Gospel online with your friends and family:

* [http://wellbehavedmormonwoman.blogspot.com/2011/06/mormons-and-social-media-getting.html Well Behaved Mormon Woman - "Mormons and Social Media - Getting Started"]

[[Category:Social networking]]

Talking about online missionary work at church

2011-06-13T16:35:36Z

Cottrells: add cat

These tips can help you with fifth Sunday lessons, Relief Society meetings, youth activities, ward missionary firesides or other Church related presentations

* [[General Principles/Applicable Quotes]]

* [[Tips for teaching members who are new to online tools and resources (e.g., members without an LDS Account, etc.)]]

* [[Tips for teaching members familiar with LDS.org]]

* [[Tips for helping members get started with Social Media]]

* [[Tips for helping members already familiar with Social Media understand what the Church has to offer and how they can use social media to further the work]]

* [[Online behavior guidelines (valuable for all members)]]

<blockquote>

</blockquote>

[[Category:Social networking]]

Helpful quotes related to social media

2011-06-13T16:35:30Z

Cottrells: add cat

Of course, social media is not for everyone. But if you are in the group of people that can use it (eg your Bishop hasn't told you not to, or your employment doesn't prohibit your using it) these quotes might be helpful.
<blockquote>
President Joseph F. Smith counseled, “Let every man’s life be so that his character will bear the closest inspection, and that it may be seen as an open book, so that he will have nothing to shrink from or be ashamed of” (''Gospel Doctrine'' 5th ed. [1939], 252).
<br>
[https://lds.org/manual/gospel-principles/chapter-31-honesty Gospel Principles - Chapter 31: Honesty]
</blockquote>
Brethren, the Lord has inspired men to invent these great tools. Now if we don’t use them to teach his gospel, Satan will use them to lead the people astray (Elder LeGrand Richards)


[[Category:Social networking]]

Blogging

2011-06-13T16:35:24Z

Cottrells: add cat

* [[Free blogging tool options]]
* [[Basic blog features]]
* [[Basic posting tips]]
* [[Tips and tricks for helping people find your blog]]

[[Category:Social networking]]

Foreign language blogging

2011-06-13T16:35:19Z

Cottrells: add cat

When doing foreign language blogging, or rather writing a blog in a foreign language, there are a few different things that you may need to be aware of when setting up a blo in a foreign language. The main one is that you should be reasonably proficient in the lagnuage, and have the tools on your computer (such as knowledge of how to generate special characters that are different than what would be in a standard English character set, or use a non-Romanic character set like that used for Russian, Chinese, Arabic, etc.

Some blogging software will accomodate foreign languages better than others, so before you download or in some cases purchase software, be sure it will actually work properly and show things the way they should in your chosen language.

[[Category:Social networking]]

Youtube

2011-06-13T16:35:13Z

Cottrells: add cat

Youtube is a very large video sharing service owned presently by Google, which bought it from the creators in 2007. The Google purchase of the site resulted in the site being what it is today, a large repository of video content from top level pro
video producers to the amateur with a cellphone.

Over two billion videos are viewed each day, and some content has tens of m illions of hits while many videos may have hardly any. However, Youtube has also made it possible for people to create content and share material on almost any subject, and the Church is no exception, having begun to place material on Youtube beginning in early 2008.

=== Using Youtube - The Basics ===

You simply shoot a video clip or produce video content and place it online, that is the simple part. However, there are some constraints to consider when preparing a video clip. First off, the video file uploaded must not be more than two gigabytes in size. Some say that can result in a 13-minute clip depending on the video quality. Video quality also is a consideration, as you can shoot in any format up to 1080p, which is a very common standard. A lot of amateurs use 720p or even 480p (similar to analog NTSC or PAL video broadcasting), so with the boom in HD programming, many people are going to want to view your video in the highest resolution possible, as 1080p or at least 720p is what many HD Televisions are capable of displaying.

The second thing to consider is production values. For most people, just getting a good video for general use is good enough, being sure there are no lighting issues, overexposed shots and underexposures, camera shake, and other problems that can crop up can torpedo even the best everyday video shots. Most modern-day digital cameras have ways of avoiding all of this although to minimize camera shake a tripod should be used. Most editing software is good for everyday use as well and some have ways of correcting bad shots or other problems with the picture, or cutting out things after the fact.

For best results, if one can afford it, use a digital single lens reflex camera, or DSLR, to get hte best results. For best results on editing the final video use a program that may be a little more expensive but which should have more options in cleaning up the footage and fixing other problems such as with sound, etc. Sound is one thing many people forget about, so find the best available microphones, as trying to capture sound through hte camera is a hit and miss proposition. You can use sound from the camera to sync what you get from a microphone with the action, but otherwise it generally is not recommended.

=== Uploading Your Finished Video ===

After you finish producing your video, there are a number of things to consider when readying for and placing the video on Youtube. The first thing is properly titling it. Avoid titles like 'Me in a Tuxedo' or anything similar. Use a descriptive tiIttle that looks like it could be the title of a book, song, or something like that. Then you need to write a description. Make it as professional and be as articulate as possible in describing your video and do it in such a way it will reach its target audience, as the description shows up in the search results in both Google and Youtube itself.

The next thing is tags. Tag it with descriptive terms and words that best describe the video. Using very generic terms causes the video to get lost whether the terms are used in descriptions or tags, so be sure that you use terms that most accurately describe your video to the audience you are seeking.

=== Copyright Issues ===

Given the no-holds-barred and open nature of Youtube, sometimes things happen or are done that are not always done properly. One of them is using copyrighted material without proper permissions. The best way to avoid issues is to use only material that has been placed in the public domain, either through Creative Commons licensing, or that has simply fallen out of copyright and thus become a public domain item. For music clips, one should look not only for Creative Commons licensing that allows you to use music in video clips, but also 'podsafe' music, which can be used in materials that can be downloaded or otherwise placed online.

=== Making Others Aware of Your Video ===

Some things useful in promoting your video need to be done at the time you post your video to Youtube. Others can be done at or after that time. When uploading a video, at times you may find that it is a response to another video, so you can say that it is a response to that video, and it will show on that video's page as a response to it. A popular way to share your video once it is actually on Youtube is to post it to your Facebook wall, tweet about it on Twitter, or add to a social bookmarking site. There are a large number of social bookmarking sites, the best known are Digg, Del.icio.us ('Delicious'), and a few others. However, there are over 340 known social bookmarking sites, and if you have Firefox as one of your browsers, add the 'AddThis Toolbar' to it, and you can select
from any of these, new ones are added as they find them.

[[Category:Social networking]]

Facebook

2011-06-13T16:34:54Z

Cottrells: add cat

Flickr

2011-06-13T16:33:18Z

Cottrells: edit cat

Flickr is a large repository of photos taken by a large number of users, like Youtube, anyone
can load up any photos they have taken, caption them, and make them available for others to view, or if they choose, to allow someone to use themselves.

== Uploading Photos ==

Uploading photos themselves is not as hard to do as uploading to Youtube, as the photo file size is mmuch smaller. However, you may still find you have to deal with issues that you find only after you have taken the shot, so a basic photo editing software package such as the free 'Gimp' software, is a must for anyone taking photos and preparing them for uploading to Flickr. The best known of the paid software programs is Adobe Photoshop, which Gimp emulates to a degree.

== Useful LDS-Related Flickr Groups ==

[[Category:Social networking]]

Flickr

2011-06-13T16:31:10Z

Cottrells: add cat

Talk:Leader Resources and Clerk Resources

2011-05-16T21:32:44Z

Cottrells: /* Membership menu */ new section

== Ward Assistant Executive Secretaries ==

Unless something has changed very recently there isn't a standard position for a ward assistant executive secretary (although I think many wards have them--mine does). As such ward assistant executive secretaries do not have access to the leader portal but the wording on this page implies that they do which may be confusing. I think it should probably be reworded to clarify. In fact it would probably be better to list the exact standardized callings that have access (probably in a bullet list). I'd be willing to take a shot at it but since this page was written by a church employee I thought I'd get feedback first and see if the author would prefer to make the changes. -- [[User:Eblood66|Eric Blood]] 05:12, 5 December 2010 (UTC)

==Stake Patriarch's getting enhanced lds.org leadership access?==

I am working on LDS Tools for Android and got an inquiry from a clerk who was asked by a Stake Patriarch what information he would have available to him online. He seems to find on a regular basis that he gets recommends for blessing without a MRN number on it. He was hoping that he would have some kind of access that he could look up that MRN with the new tools online.

I haven't been able to find anybody to talk to or ask about the request and the percieved need for Patriarchs to have some kind of enhanced access to meet their needs in their calling.

Any ideas if this is something that would be even considered? We kind of overlook our Patriarchs sometimes.

[[user:jasonhyer|Jason Hyer]] December 27, 2010

== Membership menu ==

Currently the article does not describe the options available from the ''Membership'' menu. In fact the screen shots used do not even feature this menu. --[[User:Cottrells|Steve]] 21:32, 16 May 2011 (UTC)

Community Development Security Essentials

2011-04-01T16:21:39Z

Cottrells: add cat

==Secure Development Activities==
===Risk Analysis===
[[Church_Security_Risk_Assessment_Process|Church Security Risk Assessment Process]]

===Automated Source Code Analysis===
[[Church_Application_Security_Requirements#Automated_Code_Analysis|Automated Source Code Analysis Guidelines]]

==Secure Development Guidelines==
===Application Security Guidelines===
[[Church_Application_Security_Requirements|Church Application Security Guidelines]]
===Critical Web Application Vulnerability Prevention Techniques===
====SQL Injection Prevention====
[[Church_Application_Security_Requirements#Parameterized_Queries|SQL Injection Prevention]]
====Cross-Site Scripting Prevention====
[[Church_Application_Security_Requirements#Output_Encoding|Cross-Site Scripting Prevention]]
====Cross-Site Request Forgery Prevention====
[[Church_Application_Security_Requirements#Cross-site Request Forgery|Cross-Site Request Forgery Prevention]]
===Mobile Application Security===
[http://www.veracode.com/blog/2010/12/mobile-app-top-10-list Mobile App Top 10 List]

[[Category:Development]]

Template:MobileGospelLibraryIndex

2011-04-01T15:51:54Z

Cottrells: remove link to Gospel Library for Android Wish List - now included on {{Template:GospelLibraryAndroidIndex}}

{| style="float: right; margin-left: 10px; background: #F2F3E5; border: 1px solid #aaa; width: 300px;"
|-
| style="padding: 0.25em 0.5em; width: 100%;" colspan="2" align="center" | '''''Mobile Gospel Library Project Index''''' <sup>[[Template:MobileGospelLibraryIndex | edit]]</sup>
|- valign="top"
|
* [[Mobile Gospel Library Project | Home]]
* [[Gospel Library for Android | Android Project]]
* [[Gospel Library for BlackBerry | BlackBerry Project]]
** [[Gospel Library for BlackBerry screenshots | Screenshots]]
** [[Gospel Library for BlackBerry getting started | Getting started]]
* [[Gospel Library for eBooks|eBooks (iPad iBook, Amazon Kindle, B&N Nook, Sony Reader)]]
* [[Gospel Library for iPhone | iPhone / iPod Touch Project]]
** [[Gospel Library for iPhone functional specifications | Functional specifications]]
** [[Gospel Library for iPhone wish lists | Wish lists]]
** [[Gospel Library for iPhone development info | Development Info]]
* [[Gospel Library for Amazon Kindle | Amazon Kindle Project]]
* [[Gospel Library for Palm Pre | WebOS (Palm Pre, Palm Pixi) Project]]
* [[Gospel Library for Windows Mobile | Windows Mobile Project]]
* [[Gospel Library for Windows Phone | Windows Phone Project]]
* [[Gospel Library for JavaME | JavaME Project]]
* [[Gospel Library Web Service]]
* [[Gospel Library Catalog Web Service]]
|}

<includeonly>{{{category|[[Category:Mobile Gospel Library]]}}}</includeonly><noinclude>
== Documentation ==
{{tempmain|Mobile Gospel Library Project}}
Use this template to include the an index of the major Mobile Gospel Library project articles within the wiki. The index will appear at the top right corner of the article page.

=== Categorization ===
Pages that include this template will be automatically included in the [[:Category:Mobile Gospel Library]] (unless you supply the "category=" parameter).

=== Usage ===
Simply insert the template at the top of the article by typing '''<nowiki>{{MobileGospelLibraryIndex}}</nowiki>'''.
[[Category:Index box templates|MobileGospelLibraryIndex]]
</noinclude>

User talk:Emerylynn

2011-03-22T12:44:04Z

Cottrells: /* Understanding page move */

== Understanding page move ==
Hi, I'm not sure why you moved [[Recording ordinances]] to [[My documents]]? This appears to have been a mistake. I would be interested to hear your explanation. --[[User:Cottrells|Steve]] 12:44, 22 March 2011 (UTC)

Category:Gospel Library for Android

2010-12-22T11:53:41Z

Cottrells: add/change cat

{{catmain|Gospel Library for Android}}

[[Category:Mobile Gospel Library]]
[[Category:Android applications]]

Category:IOS applications

2010-12-22T11:51:51Z

Cottrells: Created page with '{{lowercase title}} This category is used for all articles dealing with the usage or development of applications for iOS. Category:Software by operating system'

{{lowercase title}}
This category is used for all articles dealing with the usage or development of applications for iOS.

[[Category:Software by operating system]]

Category:Gospel Library for iOS

2010-12-22T11:51:26Z

Cottrells: add cat

{{catmain|Gospel Library for iOS}}

This will replace [[:Category:Gospel Library for iPhone]] since iPhone is no longer the top-level for this platform.

[[Category:iOS applications]]
[[Category:Mobile Gospel Library]]

Category:Projects

2010-12-22T11:43:50Z

Cottrells: format link

This is the main category for all community development projects on the '''[[LDSTech]]''' wiki.

In general, if a project has only one page, it should be in the Projects category. If more than one page is involved, then a category should be created for the project, and that category would be a subcategory of the Projects category.

[[Category:Contents]]

Tech Projects

2010-12-22T11:42:54Z

Cottrells: add cat

<div style="margin: 10px 0px 0px 0px;">
<div style="text-align: center;">
==Welcome to the LDSTech Projects Wiki==
</div>
<div style="font-size: 1.15em;">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.</div>
<br />
<br />
<table width="100%" cellspacing="10" cellpadding="0">
<tr valign="top">
<td width="50%">
<div style="margin: 0px 5px 0px 0px; border: 1px solid #656550;">
<div style="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: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
=====Announcements=====
</div>
* [[file:new.gif]][[LDS Tools for Android#Project status|LDS Tools for Android version 1.0.2]] has now been released to the Android market.
* [[file:New.gif]][http://new.lds.org/pages/mobile-apps/mobile-blackberry.xqy Beta version of Gospel Library for BlackBerry now available]
* [[file:New.gif]][[Mormon_Channel_BlackBerry_Application#Version_1.0 | Mormon Channel for BlackBerry version 1.0 is released]]
* [[Subversion Change to Dev | Subversion has changed locations]]
* [[LDS_Java_Stack | 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: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
=====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: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
===== Current Projects =====
</div>
* [[Community Projects | A listing of all of our community projects]]
* [[LDS_Tools_application | LDS Tools - Mobile Membership]]
* [[Local Unit Website Project | Local Unit Website Project]]
* [[Mormon Channel | Mormon Channel Mobile Applications]]
* [[Mobile Gospel Library Project | Mobile Gospel Library Applications]]
* [[Social Prototyping]]
</td>
<td><div style="background-color: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
===== 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: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
===== Internet & Family Safety =====
</div>
* [[Internet (Family Safety) | Internet Safety]]
* [[Cell Phones (Family_Safety) | Cell Phone Safety]]
* [[Family Safety | more...]]
</td>

<td><div style="background-color: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
===== Services Deployed to Community =====
</div>

* [[Community_Services_Service_Access | Accessing Services]]
* [[Community_Services_List_of_Services | List of Services]]
* [[Community_Services_version_2_Overview | more...]]
</td>
</tr>

</table>
</div> 
</td>

</tr>
</table>
__NOTOC__
__NOEDITSECTION__

[[Category:Projects| ]]

Gospel Library for iOS user interface examples on iPad

2010-12-22T11:32:46Z

Cottrells: add cat

Return to [[Gospel_Library_for_iOS_design|iOS Design]] page.

==Examples of reader application UIs on iPad==

===[http://itunes.apple.com/us/app/ibooks/id364709193?mt=8| iBooks]===

* Multi-colored hi-lighting
* Standard text-selection controls
* Hi-lighting, color selection and text management built into OS-standard text popup controls
* Navigation bar at top
* Navigation hides/shows with single touch anywhere on screen
* Notes display inline in page gutter, created through same text selection popup controls
* Popover search
* Popover dictionary definitions (compare with what can be done on cross-references, footnotes, etc)
* Pagination information at the bottom is a nice touch that converts the "digital" into a "physical" feel
** Potentially very valuable to display physical page numbers in Gospel Library to correlate location between digital and physical world for settings such as Sunday School where an instructor says "now turn to page xxx" or "let's read the first paragraph of page yy"
* Overall a clean design though the "book" feel of the pages in the background is obviously unnecessary
* Synchronizes annotations (hi-lights, bookmarks, notes) and reading location automatically between devices (iPhone and iPad for example)

[[File:IBooks-1.png|400px]]
[[File:IBooks-2.png|400px]]
[[File:IBooks-3.png|400px]]
[[File:IBooks-4.png|400px]]
[[File:IBooks-5.png|400px]]
[[File:IBooks-6.png|400px]]
[[File:IBooks-7.png|400px]]
[[File:IBooks-8.png|400px]]
[[File:IBooks-9.png|400px]]

===[http://itunes.apple.com/us/app/articles-for-ipad/id364881979?mt=8| Articles for iPad]===

* Beautiful layout and design including typography
* Images are styled nicely to fit the design
* Every article has a 'globe' at the top allowing access to languages the article is in
** This could be very powerful in the Gospel Library so that on any scripture, talk, video or other document it can immediately be accessed in any language.
* Popovers are effectively used for quick navigation within an article or for changing settings
* Navigation bar at top

[[File:Articles-1.png|400px]]
[[File:Articles-2.png|400px]]
[[File:Articles-3.png|400px]]
[[File:Articles-4.png|400px]]

===[http://itunes.apple.com/us/app/inkling/id379351586?mt=8| Inkling]===

* Excellent navigation system for dealing with very large textbooks
** Uses both the top and side bar for navigation
** Sidebar works very well on an iPad with the extra screen real-estate and typical two-handed use of the device
* Sidebar shows context of the current chapter for location in the document and sections
** The sidebar could be potentially useful in the Gospel Library for similar reasons
* Popovers provide rapid access to settings and navigation
* Graphical representation of books and chapters instead of just text
** Could be very powerful in Gospel Library to use iconography instead of just text lists to provide richer visual differentiation of the many types of content
* Annotations (hi-lights and notes) are easy to use and discoverable without documentation since they use OS-standard text selection controls

[[File:Inkling-1.png|400px]]
[[File:Inkling-2.png|400px]]
[[File:Inkling-3.png|400px]]
[[File:Inkling-4.png|400px]]

===[http://itunes.apple.com/us/app/instapaper/id288545208?mt=8| Instapaper]===

* Minimal and highly functional UI
* Navigation bar at top
** Originally had bar at bottom when it migrated from iPhone but moved to top after some user experience demonstrated that on an iPad the top bar is better suited to where hands are held.
* Fast and easy to switch between Light and Dark modes for day/night use.
* The entire UI including navigation lists use the Light/Dark modes, not just the reading view
* OS-standard text selection controls are used to integrate application specific sharing features
* Synchronizes automatically
** Content between devices and web
** Reading location within articles

[[File:Instapaper-1.png|400px]]
[[File:Instapaper-2.png|400px]]
[[File:Instapaper-3.png|400px]]

===[http://itunes.apple.com/us/app/reeder-for-ipad/id375661689?mt=8| Reeder]===

* Uses sidebar navigation effectively so that holding the iPad with two-hands allow effective controls with the thumb.
* Popovers and top navigation are also used similar to the other apps.

[[File:Reeder-1.png|400px]]
[[File:Reeder-2.png|400px]]

===[http://itunes.apple.com/us/app/simplenote/id289429962?mt=8| Simplenote]===

* Top navigation bar and popovers
* Tags are effectively used for allowing articles in multiple "categories" for searching, filtering and navigating
** Could be very effective with Gospel Library for tagging hi-lights, notes etc

[[File:Simplenote-1.png|400px]]
[[File:Simplenote-2.png|400px]]

===[http://itunes.apple.com/us/app/wikipanion-for-ipad/id364195592?mt=8| Wikipanion]===

* Top navigation bar and popovers

[[File:Wikipanion-1.png|400px]]

[[Category:Gospel Library for iOS|user interface examples on iPad]]

Main Page

2010-12-10T16:36:33Z

Cottrells: update status LDS Tools for Android

<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]][[LDS Tools for Android#Project status|LDS Tools for Android version 1.0.1]] has now been released to the Android market.
* [[file:New.gif]][http://new.lds.org/pages/mobile-apps/mobile-blackberry.xqy Beta version of Gospel Library for BlackBerry now available]
* [[file:New.gif]][[Mormon_Channel_BlackBerry_Application#Version_1.0 | Mormon Channel for BlackBerry version 1.0 is released]]
* [[Subversion Change to Dev | Subversion has changed locations]]
* [[LDS_Java_Stack | 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>
* [[Community Projects | A listing of all of our community projects]]
* [[LDS_Tools_application | LDS Tools - Mobile Membership]]
* [[Local Unit Website Project | Local Unit Website Project]]
* [[Mormon Channel | Mormon Channel Mobile Applications]]
* [[Mobile Gospel Library Project | Mobile Gospel Library Applications]]
* [[Social Prototyping]]
</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>

<td><div style="background-color: #ddcef2; padding-left: 10px; ">
===== Services Deployed to Community =====
</div>

* [[Community_Services_Service_Access | Accessing Services]]
* [[Community_Services_List_of_Services | List of Services]]
* [[Community_Services_version_2_Overview | 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]]
* [[file:New.gif]][[CUBS]]
* [[: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/Historical =====
</div>
* [[Statistical clerk]]
* [[Statistical records and reporting|Statistical reporting]]
* [[Quarterly report]]
* [[Annual history]]
* [[Record retention]]
* [[: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 broadcast]]s
* [[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]]
* [[LDS Maps]]
* [[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 LDSTech wiki. This contribution has been a great blessing to clerks around the world.
}}
</td>
</tr>
</table>
</div>
</td>
</tr>
</table>
__NOTOC__
__NOEDITSECTION__

User talk:Pliniovolponi

2010-11-12T16:31:27Z

Cottrells: reply with help

Hello, I noticed that you added some translated content to the wiki. I think you may have gone to the [[Meetinghouse technology‎]] page and clicked on the [edit] link at the end of the '''In other languages:''' line. This took you to the template that creates the link to the translated pages. I have therefore moved the content that you added to [[Meetinghouse technology‎/pt]] which is where the Portuguese content should be added. Thank you for helping out. --[[User:Cottrells|Steve]] 16:23, 12 November 2010 (UTC)

YEAP! How can I fix it by myself?

:When you would like to create or edit the pages with the translated content, select the name of the language from the '''In other languages:''' line. rather than the [edit] link. The edit away on that page. If that still does not make sense, let me know. --[[User:Cottrells|Steve]] 16:31, 12 November 2010 (UTC)

User talk:Pliniovolponi

2010-11-12T16:23:25Z

Cottrells: explaination about moving user edits/translated content

Main Page

2010-11-09T10:42:06Z

Cottrells: change external link to internal 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 #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]][[LDS Tools for Android#Project status|LDS Tools for Android version 1.0]] will be released to the Android market November 11
* [[file:New.gif]][http://new.lds.org/pages/mobile-apps/mobile-blackberry.xqy Beta version of Gospel Library for BlackBerry now available]
* [[file:New.gif]][[Mormon_Channel_BlackBerry_Application#Version_1.0 | Mormon Channel for BlackBerry version 1.0 is released]]
* [[Subversion Change to Dev | Subversion has changed locations]]
* [[LDS_Java_Stack | 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>
* [[Community Projects | A listing of all of our community projects]]
* [[LDS_Tools_application | LDS Tools - Mobile Membership]]
* [[Local Unit Website Project | Local Unit Website Project]]
* [[Mormon Channel | Mormon Channel Mobile Applications]]
* [[Mobile Gospel Library Project | Mobile Gospel Library Applications]]
* [[Social Prototyping]]
</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>

<td><div style="background-color: #ddcef2; padding-left: 10px; ">
===== Services Deployed to Community =====
</div>

* [[Community_Services_Service_Access | Accessing Services]]
* [[Community_Services_List_of_Services | List of Services]]
* [[Community_Services_version_2_Overview | 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]]
* [[file:New.gif]][[CUBS]]
* [[: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/Historical =====
</div>
* [[Statistical clerk]]
* [[Statistical records and reporting|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 broadcast]]s
* [[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]]
* [[LDS Maps]]
* [[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__

Global Service Center

2010-10-11T17:34:10Z

Cottrells: update urls/links

The '''Global Service Center''' provides support and answers questions about product ordering and distribution. Please contact them if there are any problems with the arrival or contents of your order from Distribution Services or http://store.lds.org.

== Contacting the Global Service Center ==
You may contact the [http://store.lds.org/webapp/wcs/stores/servlet/GlobalServiceCenterView?catalogId=10551&langId=-1&storeId=10704 Global Service Center]:
* by phone at 1-800-537-5971 (toll free in the US and Canada)
* by phone at 1-801-240-3800 (in the Salt Lake City area, or outside the US and Canada)
* by email at [mailto:help@store.lds.org help@store.lds.org].

{{Note| The Global Service Center is different from the [[Global Service Desk|Global Service Desk]] which provides technical support for [[Meetinghouse technology|meetinghouse technologies]].}}

[[Category:Help]]

Template:Namespace detect

2010-09-24T20:34:22Z

Cottrells: add cat sort

{{#switch:
{{lc: 

{{#if:{{{demospace|}}}
| {{{demospace}}}
| {{#ifeq:{{NAMESPACE}}|{{ns:0}}
| main
| {{#ifeq:{{NAMESPACE}}|{{TALKSPACE}}
| talk
| {{NAMESPACE}}
}}
}}
}}
}}


| main = {{{main| {{{other|}}} }}}
| talk = {{{talk| {{{other|}}} }}}
| user = {{{user| {{{other|}}} }}}
| wikipedia = {{{wikipedia| {{{other|}}} }}}
| file
| image = {{{file| {{{image| {{{other|}}} }}} }}}
| mediawiki = {{{mediawiki| {{{other|}}} }}}
| template = {{{template| {{{other|}}} }}}
| help = {{{help| {{{other|}}} }}}
| category = {{{category| {{{other|}}} }}}
| portal = {{{portal| {{{other|}}} }}}
| other
| #default = {{{other|}}} 

}}<noinclude>

This is the {{tl|namespace detect}} meta-template.

It helps other templates detect what type of page they are on.

It detects and groups all the different namespaces used on LDSTech Wiki into several types:

:'''main''' = Main/article space, as in normal LDSTech articles.
:'''talk''' = Any talk space, such as page names that start with "Talk:", "User talk:", "File talk:" and so on.
:'''user, LDSTech, file, mediawiki, template, help, category''' = The other namespaces except the talk pages.
:'''other''' = Any namespaces that were not specified as a parameter to the template. See explanation below.

For backwards compatibility this template also understands the old name '''image''' for '''file'''. But using '''image''' is now deprecated.

=== Usage ===

This template takes one or more parameters named after the different page types as listed above. Like this:

<pre>
{{namespace detect
| main = Article text
| talk = Talk page text
| other = Other pages text
}}
</pre>

If the template is on a main (article) page, it will return this:

:{{namespace detect| demospace=main
| main = Article text
| talk = Talk page text
| other = Other pages text
}}

If the template is on any other page than an article or a talk page it will return this:

:{{namespace detect
| main = Article text
| talk = Talk page text
| other = Other pages text
}}

The example above made the template return something for all page types. But if we don't use the '''other''' parameter or leave it empty then it will not return anything for the other page types. Like this:

<pre>
{{namespace detect
| file = File page text
| category = Category page text
| other =
}}
</pre>

On any pages other than file and category pages the code above will render nothing.

:{{namespace detect
| file = File page text
| category = Category page text
| other =
}}

By using an empty parameter you can make it so the template doesn't render anything for some specific page type. Like this:

<pre>
{{namespace detect
| main =
| other = Other pages text
}}
</pre>

The code above will render nothing when on mainspace (article) pages, but will return this when on other pages:

:{{namespace detect
| main =
| other = Other pages text
}}

=== Demospace and page ===

For testing and demonstration purposes this template can take two parameters named '''demospace''' and '''page'''.

Demospace understands any of the page type names used by this template, including the '''other''' type. It tells the template to behave like it is on some specific type of page. Like this:

<pre>
{{namespace detect
| main = Article text
| other = Other pages text
| demospace = main
}}
</pre>

No matter on what kind of page the code above is used it will return this:

:{{namespace detect
| main = Article text
| other = Other pages text
| demospace = main
}}

The '''page''' parameter instead takes a normal pagename. It makes this template behave exactly as if on that page. The pagename doesn't have to be an existing page. Like this:

<pre>
{{namespace detect
| user = User page text
| other = Other pages text
| page = User:Example
}}
</pre>

No matter on what kind of page the code above is used it will return this:

:{{namespace detect
| user = User page text
| other = Other pages text
| page = User:Example
}}

It can be convenient to let your template understand the demospace and/or page parameter and send it on to the {{tl|namespace detect}} template. Then do like this:

<pre>
{{namespace detect
| main = Article text
| other = Other pages text
| demospace = {{{demospace|}}}
| page = {{{page|}}}
}}
</pre>

If both the '''demospace''' and '''page''' parameters are empty or undefined then the template will detect page types as usual.

=== Parameters ===

List of all parameters:

<pre>
{{namespace detect
| main =
...
| other =
| demospace = {{{demospace|}}} / main / talk / user /
LDSTech / file / mediawiki / template /
help / category / other
| page = {{{page|}}} / User:Example
}}
</pre>

Note: Empty values to the "main" ... "category" parameters have special meaning.


[[Category:Templates|Namespace detect]]
</noinclude>

Template:Meetinghouse base

2010-09-24T20:18:11Z

Cottrells: use {{namespace detect}} for auto categories

{{Box
| float=right
| color=ldstech
| width=255px
| title=[[{{{product}}}]]
| content=<div style="font-size:90%;">
{{#if:{{{omit-benefits|}}}||{{{!}} style="background:#f2f3e5"
{{!}}-
{{!}}
*[[{{{product}}} benefits|Benefits]]
*[[{{{product}}} policies and guidelines|Policies]]
*[[{{{product}}} requirements|Requirements]]
*[[Availability of {{{product}}} products and components|Availability]]
{{!}}}}
*[[Get started with {{{product}}}|Get started]]
*[[{{{product}}} training|Training]]
*[[Local insights on {{{product}}}|Local insights]]
*[[Answers about {{{product}}}|Answers]]
{{#if:{{{omit-benefits|}}}||{{!}}} }}
----
{{{product-specific-links|}}}
----
<center>'''Related Topics'''</center>
*[[Meetinghouse technology]]
{{{related-topics|}}}
----
<center>{{navbar|{{{template-name|{{{product}}}}}}}}</center>
</div>
}}
<includeonly>{{namespace detect
| main = [[Category:{{{product}}}| ]][[Category:Meetinghouse technology]]
| template =
| other =
}}
</includeonly><noinclude>

== Purpose ==
This template is an infobox for Meetinghouse technology product articles. It will provide a common look and feel for all [[Meetinghouse technology]] wiki pages, which will help readers navigate between related product articles.

== Usage ==
This template has five parameters.

; product : The name of the product
; template-name : (optional) Name of the template, if this is the same as the product name this parameter is not required
; product-specific-links : Product specific links
; related-topics : Links to related topics
; omit-benefits : If this parameter is supplied and is not blank, omit the column of Benefits, Policies, Requirements, and Availability links

This template is not intended to be directly used, but rather it is intended to be a source for creation of other templates. To use this template, follow these steps:

# Search for the name of the template you want to create (e.g., Template:Meetinghouse Webcast”)
#* If the template doesn’t exist, click on the red link that appears
#* If the template does exist, then edit the source of the existing template
# Type <nowiki>{{Meetinghouse base|product= |product-specific-links= |related-topics= |omit-benefits= }}</nowiki>
# Define the ''product'' parameter with your product name
# Define the ''product-specific-links'' parameter with a bulleted list of any product-specific links
# Define the ''related-topics'' parameter with a bulleted list of links to any related topics
# Define the ''omit-benefits'' parameter as any non-blank value if this is not a product and so you want to omit the Benefits and related links
# Save the template
# Use the template in all your product wiki pages by inserting '''<nowiki>{{AAA}}</nowiki>''' at the start of your wiki page (where AAA is your template name)

[[Category:Index box templates|{{PAGENAME}}]]
</noinclude>

Template:Namespace detect

2010-09-24T20:16:26Z

Cottrells: edit

Template:Namespace detect

2010-09-24T20:15:19Z

Cottrells: remove non-existent templates add documentation

{{#switch:
{{lc: 

{{#if:{{{demospace|}}}
| {{{demospace}}}
| {{#ifeq:{{NAMESPACE}}|{{ns:0}}
| main
| {{#ifeq:{{NAMESPACE}}|{{TALKSPACE}}
| talk
| {{NAMESPACE}}
}}
}}
}}
}}


| main = {{{main| {{{other|}}} }}}
| talk = {{{talk| {{{other|}}} }}}
| user = {{{user| {{{other|}}} }}}
| wikipedia = {{{wikipedia| {{{other|}}} }}}
| file
| image = {{{file| {{{image| {{{other|}}} }}} }}}
| mediawiki = {{{mediawiki| {{{other|}}} }}}
| template = {{{template| {{{other|}}} }}}
| help = {{{help| {{{other|}}} }}}
| category = {{{category| {{{other|}}} }}}
| portal = {{{portal| {{{other|}}} }}}
| other
| #default = {{{other|}}} 

}}<noinclude>

This is the {{tl|namespace detect}} meta-template.

It helps other templates detect what type of page they are on.

It detects and groups all the different namespaces used on LDSTech Wiki into several types:

:'''main''' = Main/article space, as in normal LDSTech articles.
:'''talk''' = Any talk space, such as page names that start with "Talk:", "User talk:", "File talk:" and so on.
:'''user, LDSTech, file, mediawiki, template, help, category''' = The other namespaces except the talk pages.
:'''other''' = Any namespaces that were not specified as a parameter to the template. See explanation below.

For backwards compatibility this template also understands the old name '''image''' for '''file'''. But using '''image''' is now deprecated.

=== Usage ===

This template takes one or more parameters named after the different page types as listed above. Like this:

<pre>
{{namespace detect
| main = Article text
| talk = Talk page text
| other = Other pages text
}}
</pre>

If the template is on a main (article) page, it will return this:

:{{namespace detect| demospace=main
| main = Article text
| talk = Talk page text
| other = Other pages text
}}

If the template is on any other page than an article or a talk page it will return this:

:{{namespace detect
| main = Article text
| talk = Talk page text
| other = Other pages text
}}

The example above made the template return something for all page types. But if we don't use the '''other''' parameter or leave it empty then it will not return anything for the other page types. Like this:

<pre>
{{namespace detect
| file = File page text
| category = Category page text
| other =
}}
</pre>

On any pages other than file and category pages the code above will render nothing.

:{{namespace detect
| file = File page text
| category = Category page text
| other =
}}

By using an empty parameter you can make it so the template doesn't render anything for some specific page type. Like this:

<pre>
{{namespace detect
| main =
| other = Other pages text
}}
</pre>

The code above will render nothing when on mainspace (article) pages, but will return this when on other pages:

:{{namespace detect
| main =
| other = Other pages text
}}

=== Demospace and page ===

For testing and demonstration purposes this template can take two parameters named '''demospace''' and '''page'''.

Demospace understands any of the page type names used by this template, including the '''other''' type. It tells the template to behave like it is on some specific type of page. Like this:

<pre>
{{namespace detect
| main = Article text
| other = Other pages text
| demospace = main
}}
</pre>

No matter on what kind of page the code above is used it will return this:

:{{namespace detect
| main = Article text
| other = Other pages text
| demospace = main
}}

The '''page''' parameter instead takes a normal pagename. It makes this template behave exactly as if on that page. The pagename doesn't have to be an existing page. Like this:

<pre>
{{namespace detect
| user = User page text
| other = Other pages text
| page = User:Example
}}
</pre>

No matter on what kind of page the code above is used it will return this:

:{{namespace detect
| user = User page text
| other = Other pages text
| page = User:Example
}}

It can be convenient to let your template understand the demospace and/or page parameter and send it on to the {{tl|namespace detect}} template. Then do like this:

<pre>
{{namespace detect
| main = Article text
| other = Other pages text
| demospace = {{{demospace|}}}
| page = {{{page|}}}
}}
</pre>

If both the '''demospace''' and '''page''' parameters are empty or undefined then the template will detect page types as usual.

=== Parameters ===

List of all parameters:

<pre>
{{namespace detect
| main =
...
| other =
| demospace = {{{demospace|}}} / main / talk / user /
LDSTech / file / mediawiki / template /
help / category / other
| page = {{{page|}}} / User:Example
}}
</pre>

Note: Empty values to the "main" ... "category" parameters have special meaning.

<includeonly>

[[Category:Templates]]


</noinclude>

Template talk:Namespace detect

2010-09-21T15:33:42Z

Cottrells: /* Restore template request */

== Restore template request ==
Would it be possible to restore this template. It can then be used to suppress automatic categories for page not in the main namespace. For example the [[:Category:Meetinghouse technology]] currently contains more than a dozen templates that I feel do not need to be included in the category, but are due to the way the {{tl|Meetinghouse base}} template is written. Using a restored '''namespace detect''' template would allow this issue to be overcome. --[[User:Cottrells|Steve]] 15:33, 21 September 2010 (UTC)

Template:Meetinghouse base

2010-09-21T14:58:27Z

Cottrells: remove category sort <space>

{{Box
| float=right
| color=ldstech
| width=255px
| title=[[{{{product}}}]]
| content=<div style="font-size:90%;">
{{#if:{{{omit-benefits|}}}||{{{!}} style="background:#f2f3e5"
{{!}}-
{{!}}
*[[{{{product}}} benefits|Benefits]]
*[[{{{product}}} policies and guidelines|Policies]]
*[[{{{product}}} requirements|Requirements]]
*[[Availability of {{{product}}} products and components|Availability]]
{{!}}}}
*[[Get started with {{{product}}}|Get started]]
*[[{{{product}}} training|Training]]
*[[Local insights on {{{product}}}|Local insights]]
*[[Answers about {{{product}}}|Answers]]
{{#if:{{{omit-benefits|}}}||{{!}}} }}
----
{{{product-specific-links|}}}
----
<center>'''Related Topics'''</center>
*[[Meetinghouse technology]]
{{{related-topics|}}}
----
<center>{{navbar|{{{template-name|{{{product}}}}}}}}</center>
</div>
}}
<includeonly>
[[Category:{{{product}}}| ]][[Category:Meetinghouse technology]]</includeonly><noinclude>

== Purpose ==
This template is an infobox for Meetinghouse technology product articles. It will provide a common look and feel for all [[Meetinghouse technology]] wiki pages, which will help readers navigate between related product articles.

== Usage ==
This template has five parameters.

; product : The name of the product
; template-name : (optional) Name of the template, if this is the same as the product name this parameter is not required
; product-specific-links : Product specific links
; related-topics : Links to related topics
; omit-benefits : If this parameter is supplied and is not blank, omit the column of Benefits, Policies, Requirements, and Availability links

This template is not intended to be directly used, but rather it is intended to be a source for creation of other templates. To use this template, follow these steps:

# Search for the name of the template you want to create (e.g., Template:Meetinghouse Webcast”)
#* If the template doesn’t exist, click on the red link that appears
#* If the template does exist, then edit the source of the existing template
# Type <nowiki>{{Meetinghouse base|product= |product-specific-links= |related-topics= |omit-benefits= }}</nowiki>
# Define the ''product'' parameter with your product name
# Define the ''product-specific-links'' parameter with a bulleted list of any product-specific links
# Define the ''related-topics'' parameter with a bulleted list of links to any related topics
# Define the ''omit-benefits'' parameter as any non-blank value if this is not a product and so you want to omit the Benefits and related links
# Save the template
# Use the template in all your product wiki pages by inserting '''<nowiki>{{AAA}}</nowiki>''' at the start of your wiki page (where AAA is your template name)

[[Category:Index box templates|{{PAGENAME}}]]
</noinclude>

Talk:Letters and policies archive

2010-09-10T07:27:04Z

Cottrells: /* Satellite program schedule */ thanks

== Computer policy for FHCs ==

Would it be possible to locate and upload the 2008 update to the "Policy and Guidelines for Computers in Family History Centers"? It's been out quite a while now, but is not posted publicly anywhere that I am aware of. I can't imagine why it would be any more confidential than the 2005 version. -- [[User:Aebrown|Aebrown]] 21:00, 21 May 2009 (UTC)

: I see that the 2008 version has now been uploaded. Thanks -- that is very helpful! -- [[User:Aebrown|Aebrown]] 17:09, 22 May 2009 (UTC)

== Satellite program schedule ==
The satellite program schedule for the following calendar year has normally been issued at the end of August. Is there a delay on the 2011 schedule? I see that some dates are posted on [http://www.lds.org/calendar lds.org/calendar]. Would it be wise to use these when planning our calendar for 2011?. --[[User:Cottrells|Steve]] 17:24, 9 September 2010 (UTC)

: No, the 2011 schedule was released at about the same date as in previous years. The letters were dated 26 August 2010. I have uploaded the letters and included them in the list. Thanks for the reminder! -- [[User:Aebrown|Aebrown]] 18:31, 9 September 2010 (UTC)

:: Thank you. --[[User:Cottrells|Steve]] 07:27, 10 September 2010 (UTC)

Talk:Letters and policies archive

2010-09-09T17:24:41Z

Cottrells: /* Satellite program schedule */ query about 2011 schedule

Letters and policies archive

2010-09-09T17:20:48Z

Cottrells: wikilink Satellite program schedule

This site contains a repository of official letters from Church headquarters that are relevant to clerk and technology issues. Some of the most helpful documents are official policy statements. For a more complete list, see the [[Official Communications Library]].

{| border="1" cellspacing="0" cellpadding="2"
|- align="center"
! Title !! Date !! Type
|-
| [[media:09997_000_notice.pdf|Accountability for Young Single Adults]] (revised [[quarterly report]])|| 15 Nov 2009 || Instructive
|-
| [[media:09974_000_notice.pdf|Dates for Tithing Settlement and Annual Tithing Reports]]|| 15 Oct 2009 || Policy
|-
| 2010 [[Satellite program schedule]] - [[media:2010_Satellite_Program_Schedule-US-Canada-Caribbean.pdf|US/Canada/Caribbean]] - [[media:2010_Satellite_Program_Schedule-Latin_America.pdf|Latin America]] - [[media:2010_Satellite_Program_Schedule-Europe-Africa.pdf|Europe/Africa]] - [[media:2010_Satellite_Program_Schedule-Asia-Pacific.pdf|Asia/Pacific]] || 27 Aug 2009 || Instructive
|-
| [[media:Policy and Guidelines for Computers Used by Clerks for Church Record Keeping.pdf|Policies and Guidelines for Computers Used by Clerks for Church Record Keeping]] || 18 Aug 2009 || Policy
|-
| [[media:09922_000_notice.pdf|Meetinghouse Local Unit Copier Program - U.S. and Canada ]]|| 13 Apr 2009 || Instructive
|-
| [[media:PBOWebcastLetterForUSCanada.pdf|PBO Webcasting Letter for U.S. and Canada ]]|| 09 Feb 2009 || Instructive
|-
| [[media:PBOWebcastLetterOutsideUSCanada.pdf|PBO Webcasting Letter outside U.S. and Canada ]]|| 09 Feb 2009 || Instructive
|-
| [[media:FHCComputerPolicy.pdf|Policy and Guidelines for Computers in Family History Centers]] || 01 Nov 2008 || Policy
|-
| 2009 [[Satellite program schedule]] [[media:06959_000_2009Satellite_letter.pdf|U.S., Canada, Caribbean]] || 29 Aug 2008 || Instructive
|-
| [[media:08058_000_notice.pdf|Broadband Internet Services in Meetinghouses - U.S. and Canada]] || 08 Aug 2008 || Policy
|-
| [[media:08006_000_notice.pdf|Church Unit Financial Statements - U.S., Canada, and Puerto Rico]] || 12 Jun 2008 || Instructive
|-
| [[media:06978_000_letter.pdf|Travel Costs]] || 16 May 2008 || Instructive
|-
| [[media:06908_000_notice.pdf|Broadband Internet Services in Meetinghouses - Utah areas only]] || 26 Mar 2008 || Policy
|-
| [[media:06820_000_notice.pdf‎|Broadband Internet Services in Meetinghouses]] || 29 Feb 2008 || Policy
|-
| [[media:06809_000_notice.pdf|Connecting Stake and Ward Clerk Computers to Church Communications Network (CCN) Internet Connections]] || 11 Feb 2008 || Policy
|-
| [[media:03930_000_notice.pdf|Toll-free Support Number for Unit Copiers, Printers, Multi-function Devices]] || 09 Oct 2006 || Instructive
|-
| [[media:01582_000_notice.pdf|Unauthorized Use of Copyrighted Materials]] || 22 Feb 2006 || Policy
|-
| [[media:00779_000_Aug05_notice.pdf|Online Missionary Recommendation System]] || 22 Aug 2005 || Instructive
|-
| [[media:00691_000_Jul05_letter.pdf|Training Lessons for Church Record Keeping]] || 20 Jul 2005 || Instructive
|-
| [[media:00253_000_Mar05_notice.pdf|Meetinghouse Local Unit Copier Program Changes]] || 18 Mar 2005 || Policy
|-
| [[media:24739_000_Dec04_letter.pdf|Authorized Church Web Sites]] || 13 Dec 2004 || Policy
|-
| [[media:21812_000_notice.pdf|Discontinuation of Local Church Unit Web Sites]] || 15 Mar 2001 || Policy
|}

[[Category:Unit Administration]]

Category:Family Safety

2010-07-14T12:12:41Z

Cottrells: Created page with '{{catmain|Family safety with technology}} This category contains all articles related to Family safety with technology. Category:Contents'

{{catmain|Family safety with technology}}

This category contains all articles related to Family safety with technology.

[[Category:Contents]]

Template:Meetinghouse base

2010-07-14T06:33:11Z

Cottrells:

{{Box
| float=right
| color=ldstech
| width=252px
| title=[[{{{product}}}]]
| content=<div style="font-size:90%;">
{{{!}} style="background:#f2f3e5"
{{!}}-
{{!}}
*[[{{{product}}} benefits|Benefits]]
*[[{{{product}}} policies and guidelines|Policies]]
*[[{{{product}}} requirements|Requirements]]
*[[Availability of {{{product}}} products and components|Availability]]
{{!}}
*[[Get started with {{{product}}}|Get started]]
*[[{{{product}}} training|Training]]
*[[Local insights on {{{product}}}|Local insights]]
*[[Answers about {{{product}}}|Answers]]
{{!}}}
----
{{{product-specific-links|}}}
----
<center>'''Related Topics'''</center>
*[[Meetinghouse technology]]
{{{related-topics|}}}
----
<center>{{navbar|{{{template-name|{{{product}}}}}}}}</center>
</div>
}}
<includeonly>
[[Category:{{{product}}}| ]]</includeonly><noinclude>

== Purpose ==
This template is an infobox for Meetinghouse technology product articles. It will provide a common look and feel for all [[Meetinghouse technology]] wiki pages, which will help readers navigate between related product articles.

== Usage ==
This template has four parameters.

;product:The name of the product
;template-name:(optional) Name of the template, if this is the same as the product name this parameter is not required
;product-specific-links:Product specific links
;related-topics:Links to related topics

This template is not intended to be directly used, but rather it is intended to be a source for creation of other templates. To use this template, follow these steps:

# Search for the name of the template you want to create (e.g., Template:Meetinghouse Webcast”)
#* If the template doesn’t exist, click on the red link that appears
#* If the template does exist, then edit the source of the existing template
# Type <nowiki>{{Meetinghouse base|product= |product-specific-links= |related-topics= }}</nowiki>
# Define the ''product'' parameter with your product name
# Define the ''product-specific-links'' parameter with your product name
# Define the ''related-topics'' parameter with your product name
# Save the template
# Use the template in all your product wiki pages by inserting '''<nowiki>{{AAA}}</nowiki>''' at the start of your wiki page (where AAA is your template name)

[[Category:Index box templates|{{PAGENAME}}]]
</noinclude>

Template:Meetinghouse base

2010-07-14T06:32:49Z

Cottrells: /* Usage */ add new parameter

{{Box
| float=right
| color=ldstech
| width=252px
| title=[[{{{product}}}]]
| content=<div style="font-size:90%;">
{{{!}} style="background:#f2f3e5"
{{!}}-
{{!}}
*[[{{{product}}} benefits|Benefits]]
*[[{{{product}}} policies and guidelines|Policies]]
*[[{{{product}}} requirements|Requirements]]
*[[Availability of {{{product}}} products and components|Availability]]
{{!}}
*[[Get started with {{{product}}}|Get started]]
*[[{{{product}}} training|Training]]
*[[Local insights on {{{product}}}|Local insights]]
*[[Answers about {{{product}}}|Answers]]
{{!}}}
----
{{{product-specific-links|}}}
----
<center>'''Related Topics'''</center>
*[[Meetinghouse technology]]
{{{related-topics|}}}
----
<center>{{navbar|{{{templatename|{{{product}}}}}}}}</center>
</div>
}}
<includeonly>
[[Category:{{{product}}}| ]]</includeonly><noinclude>

== Purpose ==
This template is an infobox for Meetinghouse technology product articles. It will provide a common look and feel for all [[Meetinghouse technology]] wiki pages, which will help readers navigate between related product articles.

== Usage ==
This template has four parameters.

;product:The name of the product
;template-name:(optional)Name of the template, if this is the same as the product name this parameter is not required
;product-specific-links:Product specific links
;related-topics:Links to related topics

This template is not intended to be directly used, but rather it is intended to be a source for creation of other templates. To use this template, follow these steps:

# Search for the name of the template you want to create (e.g., Template:Meetinghouse Webcast”)
#* If the template doesn’t exist, click on the red link that appears
#* If the template does exist, then edit the source of the existing template
# Type <nowiki>{{Meetinghouse base|product= |product-specific-links= |related-topics= }}</nowiki>
# Define the ''product'' parameter with your product name
# Define the ''product-specific-links'' parameter with your product name
# Define the ''related-topics'' parameter with your product name
# Save the template
# Use the template in all your product wiki pages by inserting '''<nowiki>{{AAA}}</nowiki>''' at the start of your wiki page (where AAA is your template name)

[[Category:Index box templates|{{PAGENAME}}]]
</noinclude>

Template:Meetinghouse base

2010-07-14T06:25:37Z

Cottrells:

{{Box
| float=right
| color=ldstech
| width=252px
| title=[[{{{product}}}]]
| content=<div style="font-size:90%;">
{{{!}} style="background:#f2f3e5"
{{!}}-
{{!}}
*[[{{{product}}} benefits|Benefits]]
*[[{{{product}}} policies and guidelines|Policies]]
*[[{{{product}}} requirements|Requirements]]
*[[Availability of {{{product}}} products and components|Availability]]
{{!}}
*[[Get started with {{{product}}}|Get started]]
*[[{{{product}}} training|Training]]
*[[Local insights on {{{product}}}|Local insights]]
*[[Answers about {{{product}}}|Answers]]
{{!}}}
----
{{{product-specific-links|}}}
----
<center>'''Related Topics'''</center>
*[[Meetinghouse technology]]
{{{related-topics|}}}
----
<center>{{navbar|{{{templatename|{{{product}}}}}}}}</center>
</div>
}}
<includeonly>
[[Category:{{{product}}}| ]]</includeonly><noinclude>

== Purpose ==
This template is an infobox for Meetinghouse technology product articles. It will provide a common look and feel for all [[Meetinghouse technology]] wiki pages, which will help readers navigate between related product articles.

== Usage ==
This template has three parameters.

;product:The name of the product
;product-specific-links:Product specific links
;related-topics:Links to related topics

This template is not intended to be directly used, but rather it is intended to be a source for creation of other templates. To use this template, follow these steps:

# Search for the name of the template you want to create (e.g., Template:Meetinghouse Webcast”)
#* If the template doesn’t exist, click on the red link that appears
#* If the template does exist, then edit the source of the existing template
# Type <nowiki>{{Meetinghouse base|product= |product-specific-links= |related-topics= }}</nowiki>
# Define the ''product'' parameter with your product name
# Define the ''product-specific-links'' parameter with your product name
# Define the ''related-topics'' parameter with your product name
# Save the template
# Use the template in all your product wiki pages by inserting '''<nowiki>{{AAA}}</nowiki>''' at the start of your wiki page (where AAA is your template name)

[[Category:Index box templates|{{PAGENAME}}]]
</noinclude>

Template:Meetinghouse base

2010-07-14T06:25:16Z

Cottrells: change parameter for template name include default

{{Box
| float=right
| color=ldstech
| width=252px
| title=[[{{{product}}}]]
| content=<div style="font-size:90%;">
{{{!}} style="background:#f2f3e5"
{{!}}-
{{!}}
*[[{{{product}}} benefits|Benefits]]
*[[{{{product}}} policies and guidelines|Policies]]
*[[{{{product}}} requirements|Requirements]]
*[[Availability of {{{product}}} products and components|Availability]]
{{!}}
*[[Get started with {{{product}}}|Get started]]
*[[{{{product}}} training|Training]]
*[[Local insights on {{{product}}}|Local insights]]
*[[Answers about {{{product}}}|Answers]]
{{!}}}
----
{{{product-specific-links|}}}
----
<center>'''Related Topics'''</center>
*[[Meetinghouse technology]]
{{{related-topics|}}}
----
<center>{{navbar|{{{templatename|product}}}}}</center>
</div>
}}
<includeonly>
[[Category:{{{product}}}| ]]</includeonly><noinclude>

== Purpose ==
This template is an infobox for Meetinghouse technology product articles. It will provide a common look and feel for all [[Meetinghouse technology]] wiki pages, which will help readers navigate between related product articles.

== Usage ==
This template has three parameters.

;product:The name of the product
;product-specific-links:Product specific links
;related-topics:Links to related topics

This template is not intended to be directly used, but rather it is intended to be a source for creation of other templates. To use this template, follow these steps:

# Search for the name of the template you want to create (e.g., Template:Meetinghouse Webcast”)
#* If the template doesn’t exist, click on the red link that appears
#* If the template does exist, then edit the source of the existing template
# Type <nowiki>{{Meetinghouse base|product= |product-specific-links= |related-topics= }}</nowiki>
# Define the ''product'' parameter with your product name
# Define the ''product-specific-links'' parameter with your product name
# Define the ''related-topics'' parameter with your product name
# Save the template
# Use the template in all your product wiki pages by inserting '''<nowiki>{{AAA}}</nowiki>''' at the start of your wiki page (where AAA is your template name)

[[Category:Index box templates|{{PAGENAME}}]]
</noinclude>

Template:FamilySafetyIndex

2010-07-14T06:20:50Z

Cottrells: fix vde link

{{Box
| float=right
| color=ldstech
| width=252px
| title=[[Family safety with technology|Family safety]]
| content=<div style="font-size:90%;">
* [[The Internet (Family Safety)|The Internet]]
* [[Mobile devices (Family Safety)|Mobile devices]]
* [[Social Networking (Family Safety)|Social networking]]
* [[Email (Family Safety)|Email]]
----
<center>'''Media Choices'''</center>
* [[TV & Movies (Family Safety)|TV & movies]]
* [[Video Games (Family Safety)|Video games]]
* [[Online Games (Family Safety)|Online games]]
----
<center>'''Common Concerns'''</center>
* [[Pornography (Family Safety)|Pornography]]
* [[Malicious software (Family Safety)|Malicious software]]
* [[File & music sharing (Family Safety)|File & music sharing]]
* [[Identity theft (Family Safety)|Identity theft]]
</div>
----
<center>{{navbar|FamilySafetyIndex}}</center>
}}
<includeonly>
[[Category:Family safety]]</includeonly><noinclude>

== Documentation ==
Use this template to include an index of the major '''Family safety with technology''' articles within the wiki. This index will appear in the top right corner of the article page.

=== Categorization ===
Pages that include this template will be automatically included in the [[:Category:Family safety]]

=== Usage ===
Simply insert the template near the top of the article by typing '''<nowiki>{{FamilySafetyIndex}}</nowiki>'''.

Template:Fontcolor

2010-07-13T15:32:35Z

Cottrells: deeper cat

{{#if:{{{3|}}}|<span style="background-color:{{{2|inherit}}};color:{{{1|inherit}}};">{{{3|}}}</span>|<span style="color:{{{1|inherit}}};">{{{2|}}}</span>}}<noinclude>

== Usage ==
'''<nowiki>{{fontcolor|text_color|background_color|text}}</nowiki>'''

Examples:
* '''<nowiki>{{fontcolor|red|this is an important note}}</nowiki>''': {{fontcolor|red|this is an important note}} (text is red).
* '''<nowiki>{{fontcolor||yellow|text with yellow background}}</nowiki>''': {{fontcolor||yellow|text with yellow background}} (note that the text_color parameter is blank, so only the background color changes)
* '''<nowiki>{{fontcolor|yellow|green|yellow text on a green background}}</nowiki>''': {{fontcolor|yellow|green|yellow text on a green background}}

[[Category:Formatting and function templates|Fontcolor]]
</noinclude>

Template:-

2010-07-13T15:32:06Z

Cottrells: deeper cat

<includeonly><br clear="all" /></includeonly><noinclude>
Use {{tl|-}} after any floating elements and before elements you do not wish to float together with the first set.

== Details ==
{{tl|-}} contains the markup:
<pre>
<br clear="all" />
</pre>
This causes any previously-established float to clear.

The unusual name of this template is a mnemonic for an imaginary horizontal line, which separates floating elements above from those below.

[[Category:Formatting and function templates|-]]
</noinclude>

Template:!

2010-07-13T15:31:46Z

Cottrells: deeper cat

|<noinclude><br/>
This is an auxiliary template allowing one to encode "<code>|</code>"
within template and parser function parameters. To get the symbol in final output this template is unnecessary, better use "<code>&#124;</code>" which is rendered the same. Use this template in parameter values of templates and parser functions of which the result is used in table syntax, since this requires the "real" pipe character.

This template cannot be used for putting the character as text in a wiki table; in that case, again, "<code>&#124;</code>" can be used.

Note that the table syntax code "<code>!</code>" (exclamation mark) can be used directly in parameter values, so for that a template like this is not needed.

[[Category:Formatting and function templates|!]]
</noinclude>

TechWiki - User contributions [en]

Tech Broadcasts

TechWiki talk:Guidelines

Directory

Tech.churchofjesuschrist.org

Facebook

Category:Social networking

Basic blog features

Inner City Project

Helpful articles and tutorials for sharing the gospel online

Talking about online missionary work at church

Helpful quotes related to social media

Blogging

Foreign language blogging

Youtube

Facebook

Flickr

Flickr

Talk:Leader Resources and Clerk Resources

Community Development Security Essentials

Template:MobileGospelLibraryIndex

User talk:Emerylynn

Category:Gospel Library for Android

Category:IOS applications

Category:Gospel Library for iOS

Category:Projects

Tech Projects

Gospel Library for iOS user interface examples on iPad

Main Page

User talk:Pliniovolponi

User talk:Pliniovolponi

Main Page

Global Service Center

Template:Namespace detect

Template:Meetinghouse base

Template:Namespace detect

Template:Namespace detect

Template talk:Namespace detect

Template:Meetinghouse base

Talk:Letters and policies archive

Talk:Letters and policies archive

Letters and policies archive

Category:Family Safety

Template:Meetinghouse base

Template:Meetinghouse base

Template:Meetinghouse base

Template:Meetinghouse base

Template:FamilySafetyIndex

Template:Fontcolor

Template:-

Template:!