Week 004 - Website Requirements and Docos
Hours: 3-4
Am going through the briefs and other information that Naomi has presented as well as starting to nut down the documentation - I'm a bit worried because Peter and I are bogged down with half the documentation each, and we have less than a week to do it.
I'm confident that we'll be okay, but it'd be nice to have a few more days to complete it. I gave Peter a poke yesterday to see what he thought and he sent an email off to Tom. I know that we're suppose to have it done in time for Naomi to have a read, my aim had been to get it completed the week before hand in - but we didn't get the information till last week and there's no way we'll be done by this week! :)
We've discussed our sections: I based it on last semester's documentation. Basically whatever sections Peter and I did last semester, we're doing again this semester as I figured the sections we know we can stick with and get done faster because we know what to expect. So I'm taking on Detailed Project Requirements, Budgets, Work Breakdowns, Plans for Testing the System, Documentation Plans. I have one more section to do, but am going to leave it up to Peter to dole out for me.
Anyway, as I was working through the content I had a thought about the website. Currently the thought is to host the site at the EcoCenter: but does that mean that we'll have to stick to their requirements/resolutions etc?
I had a look:
http://www.ecocentre.com/westgatepark.html
Currently it's almost like a newsleteter format and we're hoping for a centralized content section with lots of white space around as to not make the information so daunting. Will we have any site requirements that we have to stick with? And how much space can/do we have?!?!? And accessibility? And while it looks like they're not limited to one html page: it still looks as though we would have to follow the styling conventions of the eco-centre page.
Maybe, if a domain name is obtainable - it could serve as a redirection? i.e. here's some basic info - now go to our website for more details! Because if we are stuck with the ecocenter place - it seems a bit hard to design the layout to the suggested outlay as given by Naomi in the brief... well it maybe possible, but certainly won't be as "pretty" as we would like to make it!
I suppose we'll have to ask - but focus first is on documentation!
Tom said that Naomi and the rest of the Friends are enthusiastic about the project, which is good as Peter and I last semester were dumped with not only someone leaving our group (in Studio 2) but also with the council deciding 5 weeks into the semester that he didn't think we could use a DVD, when that's what we've been telling him from day 1!
A few questions have cropped up during documentation process
- licensing issues: I was going through budgets and I realised that if the design that we have decided upon (i.e. half flash half web) Friends would have to obtain a license... but if they were non-profit, would they be exempt? Or would they still have to obtain one as it is not for "personal" use? And if so, how would we/they go about getting one?
- documentation plans/training users
What documents do we need? I can understand having to train or introduce the person maintaining the site to the website, to ensure they know where everything is and how to change things - but what about documentation? what would they need? A step-by-step guide to changing page? Troubleshooting? (eep!) I suppose it would depend on the knowledge of the "basic Dreamweaver" person... Could it be as simple as letting them know file structures and naming conventions etc? Navigational charts?
Am going through the briefs and other information that Naomi has presented as well as starting to nut down the documentation - I'm a bit worried because Peter and I are bogged down with half the documentation each, and we have less than a week to do it.
I'm confident that we'll be okay, but it'd be nice to have a few more days to complete it. I gave Peter a poke yesterday to see what he thought and he sent an email off to Tom. I know that we're suppose to have it done in time for Naomi to have a read, my aim had been to get it completed the week before hand in - but we didn't get the information till last week and there's no way we'll be done by this week! :)
We've discussed our sections: I based it on last semester's documentation. Basically whatever sections Peter and I did last semester, we're doing again this semester as I figured the sections we know we can stick with and get done faster because we know what to expect. So I'm taking on Detailed Project Requirements, Budgets, Work Breakdowns, Plans for Testing the System, Documentation Plans. I have one more section to do, but am going to leave it up to Peter to dole out for me.
Anyway, as I was working through the content I had a thought about the website. Currently the thought is to host the site at the EcoCenter: but does that mean that we'll have to stick to their requirements/resolutions etc?
I had a look:
http://www.ecocentre.com/westgatepark.html
Currently it's almost like a newsleteter format and we're hoping for a centralized content section with lots of white space around as to not make the information so daunting. Will we have any site requirements that we have to stick with? And how much space can/do we have?!?!? And accessibility? And while it looks like they're not limited to one html page: it still looks as though we would have to follow the styling conventions of the eco-centre page.
Maybe, if a domain name is obtainable - it could serve as a redirection? i.e. here's some basic info - now go to our website for more details! Because if we are stuck with the ecocenter place - it seems a bit hard to design the layout to the suggested outlay as given by Naomi in the brief... well it maybe possible, but certainly won't be as "pretty" as we would like to make it!
I suppose we'll have to ask - but focus first is on documentation!
Tom said that Naomi and the rest of the Friends are enthusiastic about the project, which is good as Peter and I last semester were dumped with not only someone leaving our group (in Studio 2) but also with the council deciding 5 weeks into the semester that he didn't think we could use a DVD, when that's what we've been telling him from day 1!
A few questions have cropped up during documentation process
- licensing issues: I was going through budgets and I realised that if the design that we have decided upon (i.e. half flash half web) Friends would have to obtain a license... but if they were non-profit, would they be exempt? Or would they still have to obtain one as it is not for "personal" use? And if so, how would we/they go about getting one?
- documentation plans/training users
What documents do we need? I can understand having to train or introduce the person maintaining the site to the website, to ensure they know where everything is and how to change things - but what about documentation? what would they need? A step-by-step guide to changing page? Troubleshooting? (eep!) I suppose it would depend on the knowledge of the "basic Dreamweaver" person... Could it be as simple as letting them know file structures and naming conventions etc? Navigational charts?
posted by J at 10:46 AM
0 Comments:
Post a Comment
<< Home