atom02 talk:Home

From student
(Difference between revisions)
Jump to: navigation, search
Line 5: Line 5:
 
__TOC__
 
__TOC__
  
==<b>1. Site structure</b>==
+
==<b>Site structure</b>==
  
 
1. The structure of your page is fairly clear, but, especially on the front page, try to avoid redundant information. e.g. Site plan, panoramic photos are practically copy-pasting what there is already in the brief (you can go to google map and street view from there). Most people who read the wiki know the site, focus your pages on what YOU are GOING to do with the site and WHY. --[[User:Tomek|Tomek]] 14:42, 22 September 2011 (CEST)
 
1. The structure of your page is fairly clear, but, especially on the front page, try to avoid redundant information. e.g. Site plan, panoramic photos are practically copy-pasting what there is already in the brief (you can go to google map and street view from there). Most people who read the wiki know the site, focus your pages on what YOU are GOING to do with the site and WHY. --[[User:Tomek|Tomek]] 14:42, 22 September 2011 (CEST)
Line 11: Line 11:
 
2. If you reference a page, like a wiki article of Jane Jacobs, write why. We all know who she is (I hope), what is important is WHY what she wrote is relevant for you. --[[User:Tomek|Tomek]] 14:42, 22 September 2011 (CEST)
 
2. If you reference a page, like a wiki article of Jane Jacobs, write why. We all know who she is (I hope), what is important is WHY what she wrote is relevant for you. --[[User:Tomek|Tomek]] 14:42, 22 September 2011 (CEST)
  
==<b>2. Content</b>==
+
==<b>Content</b>==
  
 
1. If you describe the questionnaire, You can just write one-two sentences on what is the intention behind it (and maybe a thumbnail image) and link it to a sub-page where you show more detail. Now you start with saying what the questionnaire is and only a few lines later you say what is its goal - the other way round. The same with traffic analysis. It would help to have a master point e.g. "Design input" where you first describe why and what kind of input your intervention requires, and only then, below, list questionnaires, traffic analysis and whatever else. --[[User:Tomek|Tomek]] 14:42, 22 September 2011 (CEST)
 
1. If you describe the questionnaire, You can just write one-two sentences on what is the intention behind it (and maybe a thumbnail image) and link it to a sub-page where you show more detail. Now you start with saying what the questionnaire is and only a few lines later you say what is its goal - the other way round. The same with traffic analysis. It would help to have a master point e.g. "Design input" where you first describe why and what kind of input your intervention requires, and only then, below, list questionnaires, traffic analysis and whatever else. --[[User:Tomek|Tomek]] 14:42, 22 September 2011 (CEST)

Revision as of 12:56, 22 September 2011

Please see http://www.mediawiki.org/wiki/Help:Talk_pages for discussion conventions --ChristianFriedrich 14:10, 22 September 2011 (CEST)

If you want to respond to a comment, start your response with a colon (":") in a new line below the comment you are responding to. If you respond to a response, put two colons ("::"), and so forth. After the end of your comment put "-- ~~~~" to automatically add your user name and time stamp (you can also use the "signature" button instead). -- Tomek 14:15, 22 September 2011 (CEST)


Contents


Site structure

1. The structure of your page is fairly clear, but, especially on the front page, try to avoid redundant information. e.g. Site plan, panoramic photos are practically copy-pasting what there is already in the brief (you can go to google map and street view from there). Most people who read the wiki know the site, focus your pages on what YOU are GOING to do with the site and WHY. --Tomek 14:42, 22 September 2011 (CEST)

2. If you reference a page, like a wiki article of Jane Jacobs, write why. We all know who she is (I hope), what is important is WHY what she wrote is relevant for you. --Tomek 14:42, 22 September 2011 (CEST)

Content

1. If you describe the questionnaire, You can just write one-two sentences on what is the intention behind it (and maybe a thumbnail image) and link it to a sub-page where you show more detail. Now you start with saying what the questionnaire is and only a few lines later you say what is its goal - the other way round. The same with traffic analysis. It would help to have a master point e.g. "Design input" where you first describe why and what kind of input your intervention requires, and only then, below, list questionnaires, traffic analysis and whatever else. --Tomek 14:42, 22 September 2011 (CEST)

Personal tools
Namespaces
Variants
Actions
Projects
Atoms
Toolbox