[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
talk:slackdocs:styleguide [2012/08/31 02:10 (UTC)] nocturnal.slackertalk:slackdocs:styleguide [2012/09/09 09:51 (UTC)] – Another comment on capitalisation rule brianl
Line 18: Line 18:
  
 ---- ----
 +Shouldn't the Style Guide also be signed by its author? [[wiki:user:kikinovak|Niki Kovacs]] Tue Sep  4 07:14:48 CEST 2012
 +
 +>Most Slackdocs documentation, if not all, has been written by staff. Personally, I don't care about author attribution on these "rules and regs" type articles. Many of the articles, this one for instance, have numerous contributors. Just my thoughts. :-)  --- //[[wiki:user:nocturnal.slacker|V. T. Eric Layton]] 2012/09/04 10:45//
 +
 +----
 +"Follow proper capitalization rules for words in titles and headings." Aren't we being pedantic? Personally, I find this a little too fussy and unnecessary. A Pain In The Arse, or a Pain in the Arse.  --- //[[wiki:user:brianl|Brian Lawrence]] 2012/09/08 06:01//
 +
 +>Actually, proper capitalization is an important part of any written language, in my opinion, and should be respected. A site with poor examples of writing and proper use of language by the staff members doesn't set much of an example for those utilizing the site, I wouldn't think. By the way, neither of your examples above are properly capitalized were they to be used as titles. Minor words such as "in" and "the" should not be capitalized. I feel we should take pride in how language is used on this site, hence the style guidelines.  --- //[[wiki:user:nocturnal.slacker|V. T. Eric Layton]] 2012/09/08 16:07//
 +
 +>> Titles and headings should tell the reader what the article or section is about, simple as that. The title and headings of the article that started this debate, Niki's HowTo on NTP, did that. And what is more important for the purposes of this site, the instructions in the article worked. I do not think that anyone who wants to write an article should be worrying about whether it meets the approval of The Chicago Manual of Style or NIVA.  --- //[[wiki:user:brianl|Brian Lawrence]] 2012/09/09 02:25//
 +----
 +I had the same thought about that. Capitalizing every word is typical US-english style. We are trying to not just cater to the US population, remember? I personally think capitalizing every word is ugly. Try capitalizing a whole sentence... it looks awful. \\ Nevertheless, from the point of view of "unified look and feel" I can understand why you would want all headers capitalized. \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2012/09/08 06:59//
 +
 +
 +
 talk:slackdocs:styleguide ()