schematics of a usable web wiki
Throughout the past couple of weeks I think that we have successfully implemented our thoughts throughout newer developments including delicious and thinkature. I do believe that the hardest part is over in the beginning phases of development, because just getting the ideas down onto something concrete is half the battle. I feel that the audio file pointed out a huge gray area for the class, which was that our audience was not general and that it was variable. The audience analysis depends on the topics brought about by the concerns and repercussions of the collapse. Although, the collapse of the bridge could affect many people around the country, our wiki will be very successful if we can narrow the focus of the audience. Step one in our success should be accurately narrowing our audience analysis.
The second main focus for success should be shed upon developing task lists. In BrownEtAl, task lists "help you to create a more accurate schedule, and a detailed task list helps to better track the progress of the project." I agree with this 100%. Task lists can always change throughout the course and development of a project, but to get them down in a sequential order is again half the battle. You can map progress with office project or excel which gives you duration time slots which is extremely useful.
The third and main focus for success is putting the wiki together in a usable way on the web so that people that seek out information can easily find it and gather it in a timely fashion. How do we do this? Organizing our information under categories that cater to the cognates of visual rhetoric (emphasis, arrangement, conciseness, clarity, and ethos). Usability.gov claims that 63% of web users don't find the information they need on their first try, and it takes the average person 7 seconds before they give up on the site altogether. If we can develop a website that is pleasing to the eye and user friendly, I think that is success entirely.