User talk:Vater - Revision history

Vater: /* reminder for myself */ new section

2012-12-19T05:48:33Z

‎reminder for myself: new section

Vater: /* Blank Lines */ no problem

2012-11-05T07:36:56Z

‎Blank Lines: no problem

Purgatori: /* Blank Lines */ new section

2012-11-05T07:00:50Z

‎Blank Lines: new section

Tigersharke: /* categorizing pages */

2012-08-24T23:27:37Z

‎categorizing pages

Tigersharke: /* categorizing pages */

2012-07-31T00:30:41Z

‎categorizing pages

Vater: thanks a lot! :-) but in this case it is latin, not a (possible) fail of my english :-D (please feel free to continue)

2012-07-30T14:35:49Z

thanks a lot! :-) but in this case it is latin, not a (possible) fail of my english :-D (please feel free to continue)

Tigersharke: /* thin client page */ :)

2012-07-30T05:43:44Z

‎thin client page: :)

Tigersharke: /* categorizing pages */

2012-07-30T05:42:52Z

‎categorizing pages

Tigersharke: /* categorizing pages */

2012-07-30T05:38:58Z

‎categorizing pages

Tigersharke: /* categorizing pages */ new section

2012-07-30T05:38:45Z

‎categorizing pages: new section

← Older revision		Revision as of 05:48, 19 December 2012
Line 119:		Line 119:

	--[[User:Tigersharke\|Tigersharke]] 22:38, 29 July 2012 (PDT)		--[[User:Tigersharke\|Tigersharke]] 22:38, 29 July 2012 (PDT)
		+
		+	== reminder for myself ==
		+
		+	* nbsp

← Older revision		Revision as of 07:36, 5 November 2012
Line 119:		Line 119:

	--[[User:Tigersharke\|Tigersharke]] 22:38, 29 July 2012 (PDT)		--[[User:Tigersharke\|Tigersharke]] 22:38, 29 July 2012 (PDT)
−
−	~~== Blank Lines ==~~
−
−	Sorry, that was a problem with the way Opera was copying text across to Emacs. I fixed the problem, but I'm quite new to the whole Mediawiki system, so I was unsure how to revert the page back to its previous state.

← Older revision		Revision as of 07:00, 5 November 2012
Line 119:		Line 119:

	--[[User:Tigersharke\|Tigersharke]] 22:38, 29 July 2012 (PDT)		--[[User:Tigersharke\|Tigersharke]] 22:38, 29 July 2012 (PDT)
		+
		+	== Blank Lines ==
		+
		+	Sorry, that was a problem with the way Opera was copying text across to Emacs. I fixed the problem, but I'm quite new to the whole Mediawiki system, so I was unsure how to revert the page back to its previous state.

@@ Line 104: / Line 104: @@
 == categorizing pages ==
-* '''Pages that are part of the handbook''' will have these categories: handbook, macro topic (such as control panel), topic (such as bluetooth manager). Whether micro topic or sub-micro topics get categories as well, is not as clear. They *could* but since those are often more verbose, they would probably need to be made a bit more concise (few words, like no more than 2 or three) without losing detail.
+* '''Pages that are part of the handbook''' will have these categories: handbook, macro topic (such as control panel), topic (such as bluetooth manager). Whether micro, nano, pico, or atto topics get categories as well, is not as clear. They *could* but since those are often more verbose, they would probably need to be made a bit more concise (few words, like no more than 2 or three) without losing detail.
 * Other pages on the wiki, may have the category ''pc-bsd wiki'' and a category of the ''topic'' it fits.

← Older revision		Revision as of 00:30, 31 July 2012
Line 109:		Line 109:

	* The category, ''categories'' is only for category pages and not to categorize normal pages.		* The category, ''categories'' is only for category pages and not to categorize normal pages.
		+
		+	* Categorizing images- similar hierarchy would be used as with handbook pages, especially to add a category tag for the page the image appears on.

	* It is okay to create new categories by giving a page a new category membership. It will display a redlink for the category which can be used to make it official and add a description for the new category.		* It is okay to create new categories by giving a page a new category membership. It will display a redlink for the category which can be used to make it official and add a description for the new category.

@@ Line 80: / Line 80: @@
 ----
-Solved!
+[http://en.wiktionary.org/wiki/salve#Latin Salve]!
 I cannot see "to much spaces" or other strange things. So probably I cannot help, at all.

← Older revision		Revision as of 05:38, 30 July 2012
Line 113:		Line 113:

	Thanks for your time and efforts on the wiki, it is certainly appreciated.		Thanks for your time and efforts on the wiki, it is certainly appreciated.
		+
		+	--[[User:Tigersharke\|Tigersharke]] 22:38, 29 July 2012 (PDT)

← Older revision		Revision as of 05:38, 30 July 2012
Line 101:		Line 101:

	--[[User:Vater\|Rg]] 15:57, 25 July 2012 (PDT)		--[[User:Vater\|Rg]] 15:57, 25 July 2012 (PDT)
		+
		+	== categorizing pages ==
		+
		+	* '''Pages that are part of the handbook''' will have these categories: handbook, macro topic (such as control panel), topic (such as bluetooth manager). Whether micro topic or sub-micro topics get categories as well, is not as clear. They could but since those are often more verbose, they would probably need to be made a bit more concise (few words, like no more than 2 or three) without losing detail.
		+
		+	* Other pages on the wiki, may have the category ''pc-bsd wiki''
		+
		+	* The category, ''categories'' is only for category pages and not to categorize normal pages.
		+
		+	Exploring to see how things are already and discovering what exists are the best ways to learn what to do. I cannot claim that there is perfect consistency through the entire wiki, or even the entire handbook portion of the wiki, but hopefully there is enough consistency to understand the intent and the general rule being applied. I have tried to document things in the Style Guidelines, and various other places (ie, on templates or categories). It never hurts to ask when you are unsure, but as you've also noticed, recent changes will alert you to where you may take a look whether changes are needed (in other words, you can use your best judgement and 'go for it,' you won't permanently wreck anything :).
		+
		+	Thanks for your time and efforts on the wiki, it is certainly appreciated.