Tech Forum

kd7mha wrote:Here is what I have been working on

https://docs.google.com/spreadsheets/d/ ... sp=sharing

Nice!

kd7mha wrote:Here is what I have been working on
https://docs.google.com/spreadsheets/d/ ... sp=sharing

This is a really nice, simple system. You could even add teachers if you wanted to. The hard part is what was mentioned above, directing members to "go to Google Docs for X, Facebook for Y, etc." Does your ward only teach one Sunday School class?

I put a link on the ward newsletter, it could also be shared on Facebook, etc.
we have 2 Gospel Doctrine classes, I just won't list the Instructors
Realized that I lost the Instructor field when I changed the layout

I was wondering mainly about Gospel Principles, which seems to be missing.

kd7mha wrote:Here is what I have been working on

https://docs.google.com/spreadsheets/d/ ... sp=sharing

Great idea, thanks for sharing

sbradshaw wrote:I was wondering mainly about Gospel Principles, which seems to be missing.

I just used the classes that were populated in Lesson Schedules for this year in our Ward

We have been using a portion of our First Sunday Priesthood Meeting to promote the use of electronic devices and LDS.org to the members. One of the key tools we have been emphasizing has been the Lesson Schedule as a means of preparing for their Sunday Lesson as well as the ability to go right to the lesson material from there. The suggested workaround methods would not be as effective. Why give up on something that is already in place?

Why give up on something that is already in place?

I was asking the same thing, I submitted a similar question in feed back, they are good to respond, I also got this link with a short article.

It is a good idea in theory, but here’s the problem—only 750 of the Church’s 30,000 wards and branches use it.

A cost-benefit analysis showed it was too expensive to update, given that so few wards and branches actually use it.

Here is a link to the article so you can read it http://ldsmediatalk.com/2016/11/22/less ... continued/
It goes on to suggest possible replacements which could be done locally.
I am also sad about this being discontinued, but at list this article gave it some closure for me.

As mentioned above, we certainly should put development time and server resources and bandwidth into those tools most used and most helpful, with an eye toward future functionality.

(Edited 11-27: removed redundant comments)

Hi 1968leocomeeatabite,
Thanks very much for posting that article explaining the "why". I found that very helpful and will use it when I receive the same questions from members of my stake.