Talk:ETH Zurich 2006

From 2006.igem.org

Revision as of 11:25, 26 September 2006 (view source) Olga (Talk | contribs) (→Some stuff from the original page) ← Older edit		Latest revision as of 11:27, 30 October 2006 (view source) Dimo (Talk | contribs) m
(9 intermediate revisions not shown)
Line 5:		Line 5:
	-->		-->
		+	'''Structure'''
-	= Availability =	+	I suggest to put the coordination part to the bottom and add a "team" part instead to the top --[[User:Dimo|Dimo]] 05:29, 30 October 2006 (EST)
-	I think, the following chart is also not necessary any more (it has never been applicable from my point of view).	+
-	Anyway, we could put known longer absences here.
-	* Dimo: I will not be in Zurich from September 4-19
-	* Alexandra:
-	**I will not be in Zurich from Juli 27 to August 6
-	**I will not be available after 16.00 o'clock in August 21-27
-	* Ol'ga:
-	** away August 16 - 23
-	** away September 1- 10
		+	'''writing everything small?'''
-	== Availability chart ==	+	I propose to have a correct usage of capital letters within our wiki (if possible). Texts are hard to read if everything is written small. Furthermore, it gives the impression of being not competent. --[[User:Dimo|Dimo]] 10:03, 26 October 2006 (EDT)
-	Sorry Alexandra, the table I made is terrible to edit, so I think we can use that: [http://www.doodle.ch/dpstPwMnysUQ]
-	The meaning of the marks is inverted, make '''marks where you are not available!!''' (to save clicking work on your part I hope ;))	+	'''everything on one page?'''
		+
		+	should this all stay on the entry page? with all the details? --[[User:Dimo|Dimo]] 10:06, 12 October 2006 (EDT)
		+
		+	: I see little reason to separate it, espacially at this point, unless there is a compelling reason why something cannot sensibly be placed on the front page. Maybe when finishing the documentation I'll worry about dividing it up. Granted the table of contents are too long but this wiki does not provide any means to control which sections show up there ... --[[User:Ajk|Ajk]] 10:13, 12 October 2006 (EDT)
		+
		+	'''Table of Contents on the Wiki'''
		+
		+	:You can eliminate the computer generated TOC by adding
		+
		+	:<underscore><underscore>NOTOC<underscord><underscore>        (Note: change the <underscore> to the underscore character)
		+
		+	:to the page.  Then, you can write your own TOC entries with total control. -- Randy
		+
		+	:: Thanks for the hint. As long as the wiki is volatile I want to have it generated automatically though. --[[User:Ajk|Ajk]] 04:01, 16 October 2006 (EDT)

---

Latest revision as of 11:27, 30 October 2006

Structure

I suggest to put the coordination part to the bottom and add a "team" part instead to the top --Dimo 05:29, 30 October 2006 (EST)

writing everything small?

I propose to have a correct usage of capital letters within our wiki (if possible). Texts are hard to read if everything is written small. Furthermore, it gives the impression of being not competent. --Dimo 10:03, 26 October 2006 (EDT)

everything on one page?

should this all stay on the entry page? with all the details? --Dimo 10:06, 12 October 2006 (EDT)

I see little reason to separate it, espacially at this point, unless there is a compelling reason why something cannot sensibly be placed on the front page. Maybe when finishing the documentation I'll worry about dividing it up. Granted the table of contents are too long but this wiki does not provide any means to control which sections show up there ... --Ajk 10:13, 12 October 2006 (EDT)

Table of Contents on the Wiki

You can eliminate the computer generated TOC by adding

<underscore><underscore>NOTOC<underscord><underscore> (Note: change the <underscore> to the underscore character)

to the page. Then, you can write your own TOC entries with total control. -- Randy

Thanks for the hint. As long as the wiki is volatile I want to have it generated automatically though. --Ajk 04:01, 16 October 2006 (EDT)