Talk:How to create a meetinghouse technology wiki page

Please follow capitalization guidelines

It appears in much of what you are creating, you are fighting the wiki capitalization guidelines. It will be a lot easier if you'll just follow the standards and avoid title case everywhere. Then you can create links simply as [[Meetinghouse technology]] rather than the more complex [[Meetinghouse technology|Meetinghouse Technology]]. You'll save yourself and other wiki contributors a lot of work by deciding upfront on the right title strategy that meets the guidelines. This affects articles, headings, categories, and templates.

I tried to raise this issue on your user talk page but have received no response. It would be helpful to have a discussion on this and related issues. Thanks! -- Aebrown 14:48, 20 May 2010 (UTC)

What are the proper nouns in the (M)meetinghouse technology space?

Although we want to avoid title case, it does seem that some of the words and phrases in this space should be treated as proper nouns. For example, "Meetinghouse Webcast" is a specific technology, and so it does seem appropriate for it to be capitalized. The same would be true of "Meetinghouse Internet" (that one is obvious, since Internet is a proper noun).

But what about the word "Meetinghouse" and the phrase "meetinghouse technology"? Obviously the word "meetinghouse" is a common noun, but at times I have had the impression that when we use "meetinghouse" as a modifier to other words in this technology space, it almost becomes a proper noun. In an article or category name, it's easy to avoid this issue, since the first letter of the first word is always capitalized. But when we use such phrases in the middle of sentences, we have to know how to capitalize. So as an example, which of the following is correct?

  1. Select the appropriate Meetinghouse Technology for your stake.
  2. Select the appropriate Meetinghouse technology for your stake.
  3. Select the appropriate meetinghouse technology for your stake.

I could go with either 2 or 3; I only ask that we be consistent. But this decision will trickle through dozens of related decisions, so we should firm it up soon. Thoughts? (Please respond using the standard wiki practices for discussion pages.) -- Aebrown 15:26, 20 May 2010 (UTC)

Personally, I like #2. I am new to the wiki creation, so I didn't realize we could use the more simplified version of the link - I will do that. -- Knaptonks 15:59, 20 May 2010 (UTC)

Why is screen shot back on the left?

Knaptonks, I suppose it's a matter of preference, but I don't understand why you want the screen shot image to be on the left. With it on the left, the text is separated from the headings, and the bulleted list of categories doesn't display well -- depending on the size of the browser window, the list will almost certainly be split with some of the categories on to the right of the image, and others on the left margin. Both readability and overall visual appeal suffer.

On the other hand, when I moved the image to be on the right, all those problems were fixed; the category list was nice and vertical. I fail to see one single thing that is improved by the image being positioned on the left. Why did you change its position? -- Aebrown 22:28, 25 May 2010 (UTC)

Since there was no response in over a week, I went ahead and moved the image back to the right. -- Aebrown 14:21, 2 June 2010 (UTC)

Two reasons I prefer this on the left: 1. The image has to sit below the nav box. It creates too much white space on the left if the image is on the right. 2. When the image is on the right, it is too easy to confuse it with the "live" box - I am directing non-tech-savvy people to this page, and they mentioned to me some confusion as we were talking through the instructions. When I move it to the left, it is more clear to them that this is an image for instructional purposes, rather than a duplication of the "live" nav box. - Ken 16:27, 2 June 2010 (UTC)

This page was last modified on 2 June 2010, at 09:27.

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