This may be worth looking into. I waffle on whether this sort of thing is ultimately a good decision — you're relying on someone else's framework, it takes a while to learn and master, and once you decide to go with it you're essentially stuck with it. But isn't that the case with any pseudo-framework developed for a website design? I should test this on a little project.
Particletree: Reflections of an Interface Designer
Some rather obvious reflections, but valuable all the same -- the continued appearance of articles like this shows how important these lessons are. On the volatility of web apps, designers, the relationship thereof, and how important the user is.
On starting over. "It's better to have something we're both proud off than to try and salvage the work done so far. Sometimes you have to go all the way through the design process before you realize that you've built the wrong thing."
"The need for these distinctions becomes moot, of course, when no secondary actions are present. Make sure you really need each secondary action on a form and don’t add them indiscriminately."