[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.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
talk:slackdocs:styleguide [2012/09/04 05:15 (UTC)] – kikinovak | talk:slackdocs:styleguide [2012/09/14 21:44 (UTC)] (current) – zithro | ||
---|---|---|---|
Line 18: | Line 18: | ||
---- | ---- | ||
- | Shouldn' | + | Shouldn' |
+ | |||
+ | >Most Slackdocs documentation, | ||
---- | ---- | ||
+ | " | ||
+ | > | ||
+ | |||
+ | >> 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. --- // | ||
+ | ---- | ||
+ | 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, | ||
+ | ---- | ||
+ | If capitalization is a US-english style only, it should NOT be used. Its just my opinion, but the wiki is international, | ||
+ | Concerning this page, I removed the translation notes and linked to the translation guidelines. Also, shouldn' | ||
+ | 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)\\ | ||
+ | --- // |