Just a list of frameworks. Yeah, I know jQuery is rad, but I was hoping to see some actual advice on the prototyping process, as opposed to the coding process.
For the rails kids, we have Bort (<a href="http://github.com/fudgestudios/bort/tree/master" rel="nofollow">http://github.com/fudgestudios/bort/tree/master</a>)
I really shouldn't nitpick-- particularly on something thrown together in a week by one person-- but I can't resist: I bet you'd double the fraction of people looking at the site who actually build a list if it lets you start building a list before signing up. After I've built one you can remind me that I should sign up if I want to keep it.<p>Its much better to let people get their feet wet with out jumping through the hoop of a sign-up.
As cool and useful as Pinax is, calling it "well documented" isn't <i>entirely</i> accurate considering the fact that there is barely any documentation to speak of.
What's everyones take on using something like Pinax where a lot of things are done and bundled up for you?<p>I've never been a huge fan of this approach. I like Django because it removes some of the annoying parts of creating a web app, but I don't like when the user registration, commenting, profiles, avatars, and more site-specific functionality like "groups/message boards" are pre-built for me
For prototyping we just starting using Axure. <a href="http://axure.com/" rel="nofollow">http://axure.com/</a><p>Adobe has a Thermo but it's still in labs. <a href="http://labs.adobe.com/wiki/index.php/Thermo" rel="nofollow">http://labs.adobe.com/wiki/index.php/Thermo</a>