Welcome to the Slackware Documentation Project


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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
talk:slackdocs:styleguide [2012/08/30 22:20 (UTC)]
talk:slackdocs:styleguide [2012/09/14 21:44 (UTC)] (current)
Line 14: Line 14:
 ---- ----
 The way in which you added that footnote put the parser on the wrong foot :-) \\ Look at how I fixed that footnote. Powerful syntax.  \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2012/08/30 15:19// The way in which you added that footnote put the parser on the wrong foot :-) \\ Look at how I fixed that footnote. Powerful syntax.  \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2012/08/30 15:19//
 +>Back when I used to smoke and drink, I used to pay powerful sin taxes. HA! :-P  Humor is a good thing. Yes, footnote syntax very cool. It even shows when you hover over the number. Thanks, Eric. G'night...  --- //[[wiki:user:nocturnal.slacker|V. T. Eric Layton]] 2012/08/30 19:07//
 ---- ----
 +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//
 +If capitalization is a US-english style only, it should NOT be used. Its just my opinion, but the wiki is international, not US.\\ 
 +Concerning this page, I removed the translation notes and linked to the translation guidelines. Also, shouldn't we re-order the page ? It's not really consistent like this. For example sections concerning edits (ie. modifications) should be AFTER the general rules (ie. A General Note on Style, ...).\\ 
 +I would move sections in this order:
 +  * 1. A General Note on Style
 +  * 2. Page Editing Etiquette
 +  * 3. Editing Policy
 +  * (everything else being left in the actual order)\\ 
 + --- //[[wiki:user:zithro|zithro]] 2012/09/14 14:04//

In Other Languages
QR Code
QR Code talk:slackdocs:styleguide (generated for current page)