LDSTechForumProjects

Talk:Community Services version 2 Overview

Need to adjust article titles

The first two pages that have been created (Ward Directory Service and Scripture Search Service) are probably okay. But many of the other page names implied by the links are problematic and must be changed before pages are created. Obviously, generic titles such as "Getting Started" and "Security" will not work, because this wiki covers all sorts of projects that might document security or how to get started. Instead, the titles would have to be something like "Getting started (Community Services)" or "Community Services v2: Getting Started". You can still have the visible link be simpler, but in the wikitext you should change the link to be something like [[Getting started with Community Services|Getting started]]. -- Aebrown 18:17, 16 March 2010 (UTC)

You're right about that. These pages aren't even for public use until after the development conference, which is why I created them from a link inside my user profile. I just needed to have something out on the wiki for a meeting I was having today to discuss our documentation strategy for the web services we're releasing to the community on April 1st. I have a meeting with Tom Welch on Thursday where we're going to actually create the real structure, with a style guide that will include naming conventions for pages, templates (the reusable chunks of text type), templates (the design type), versioning standards (what to do when multiple versions of the service are in production), etc. So we won't be creating any of the pages that are listed in this doc. This was just to give a sample of what a documented API might look like in wiki form. -- doc_guy 22:22, 16 March 2010 (UTC)

Does this page supersede the content on this page: https://tech.lds.org/wiki/Community_Services_List_of_Services? --Tom Johnson 23:25, 1 September 2011 (UTC)

This page was last modified on 1 September 2011, at 16:25.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.