Web ReDesign: Workflow that Works
I must admit that at first, I was skeptical upon reading the first chapter. It seemed as though this book was meant for a huge team, with a budget, and plans and that it was more of a project planning book than an actual web redesign book. However, how can one redesign a website without a process? Even though our budget for this site is $0 (not including hourly wages) and there is essentially one person working on it, there still must be a web redesign process to follow. Infact, this is made much simplier when only one or two people are involved, there is less people to keep track of. This book does a very good job of outlining the proper steps in preparation for a site redesign. This book appeals to everyone, from the 30 person webteam, to the solo webmaster. Why learn from your own mistakes, when you can learn from others, who have already made the mistakes? This book appears to be the accumulation of alot of hard work, and this certainly (in my opinion) adds a validity behind what you are told when you read this.
Things that I found interesting and important:
-Addressing the concepts of Content-View, Site-View and Page-View
(Most of this pertains to the first two chapters in the book)
It turns out the problem with the form last night was that I was opening form.html with a filehandle instead of ./form.html. ARG!
Once it's done, I think this form will be easier to maintain and update than the current classrooms form because it references an external HTML file for the form, which means that it can work easily with any other form as long as it passes the same variables. Now that it's importing the form correctly, I just have to work on the internal logic and error-checking.
Lemon-wise, I was messing with the review functions. I'll shortly be closing the current review session so I can make a new form, self-review, and sesion. It looks like I'll have to make a new scheduling pass because some things are broken in Late Night Happiness, like scheduling any hours in the testing lab.
I've got it up at staff.washington.edu/ggt/form.cgi , but it isn't working right now with the changes I've made to it since yesterday.
I'm trying to set it up like the classroom request form, where all of the submissions and everything are done within the same file, but for some reason it doesn't like printing out HTML from an if statement. I'll have to poke at it more tomorrow.
Basically, I'm trying to get it to flow like:
-check for a form variable denoting whether the user is new or not.
-if new, show the form html
-if has submitted the form, check the data
-if the data is bad, return an error page with fields in it to correct the errors
-if the data is good, do stuff with it and show a confirmation page