I love LDSTech!
|Communicate with me|
|Cell||801-613-8776 (Call or Text)|
|If you see "techgurufloyd" or "cognifloyd" anywhere on the internet, it's me.|
Project Docs - Temporary Playground
The purpose of LDSTech includes helping people to "Learn about how the Church is using technology" and "Contribute to Church technology projects". Learning about what is already developed will help community members to contribute more effectively and reuse existing projects. In these pages, I am trying to help people understand the design of various church products/websites and how they can reuse or include the design in the community projects. Please enjoy this documentation, tear it apart (to make it better), and help me to fill in the blanks. Discussion is welcome!
Here's some of the documentation I would like to create or see made available to the community.
- Document how to use/integrate with various apps (and other parts of lds.org) in other community projects. Note that there is already some great docs for many of these services. The docs may need to be expanded (possibly here instead of there) to take into account the visual design of some parts of lds.org.
- Add a section in User:Cognifloyd/Design of lds.org or a new page that describes the unique visual styles in the following sections of lds.org:
- Other sites that could potentially use some documentation down the road (or sites that I want to see [better] ways to integrate with them):
- Online Store
- The Vineyard
- Seminary & Institutes sites
- Mormon Radio
- Employment sites
- mormon.org: User:Cognifloyd/Design of mormon.org
- There isn't documentation on mormon.org for now as it is seems that projects won't be using the visual layout of mormon.org for the forseeable future.
- However, ohfp has an element called "sashy" that seems to get content from mormon.org. Documentation on how to use quotes from mormon.org would be beneficial if it really is a service and not just static copies.
- Various Church Websites
- A list of lots of websites, some of which have old designs. When a site gets a facelift, I might document it if it seems it might be beneficial at some point for the community.
- new document on XQuery and MarkLogic
- lds.org uses Marklogic to store all of the content. If a community project ever needs a more intimate integration with lds.org, XQuery might be just the ticket to success.