Heh. Whatever nifty location rewriting javascript you're using makes it impossible for me to browse your site - eg. http://www.nutrivise.com/#terms/ just points to your homepage.
Also: the 'terms of use' on that page are bogus. "The most advanced nutrition system [evar!!1!]" vs. "NUTRIVISE MAKES NO WARRANTIES ABOUT THE ACCURACY, RELIABILITY, COMPLETENESS, OR TIMELINESS OF THE MATERIAL OR THE WEB SITE ... WHETHER BASED ON THIRD PARTY INFORMATION OR ON RATINGS GENERATED BY NUTRIVISE." Oh? So what are people paying you for then, if not expert advice that you're willing to stand behind?
The location rewriting is the Backbone router stuff that uses pushState. Pretty common HTML5 stuff, you'd have to be using a moderately old web browser. Most common one we're aware of that's guilty of not supporting this is Firefox 3. What's yours in this case?
This is how terms of use work on most websites. In our case, we're in a particularly tricky situation because the meal plans we lay out have the ability to be incredibly useful to our users, but only if they actually comply with them.
Since compliance isn't something we can ensure without a human being watching them 24/7 (including when they're asleep in case they're sleep-eaters, an actual phenomenon), we have to put in place that terms of use for that reason and others.
Others including situations like people with severe allergies. We cannot guarantee the absence of allergens in recipes/food coming from some of our third party sources. To guarantee as much would endanger the health of our users and would be irresponsible.
I'm sorry you don't feel we don't stand behind our product. We really do stand behind what we do and believe we're working on something that has the potential to help a large portion of westerners with weight issues.
The nutrition researchers and dietitians we work with feel so strongly about our product that it's being used in a weight loss case study involving many subjects that will allow us to further refine our already substantial improvement on the current state of consumer nutrition.
My email is in my profile, contact me if you'd like to discuss this further. I'd be interested to hear what you think we could do to better show we feel confident about our software.
The problem is that a lot of it is hacky and somewhat specific to our site. Not necessarily generalizable.
I will say this though, I've been using Fabric for a very long time and abuse it with glee.
Are there any dev-opsy/provisioning/whatever type pain points you'd like a blog post or exposition on?
Edit: I'm the CTO. I'm open to open sourcing our stuff, but the lack of generalizability makes it less than useful. There's an abundance of magic in our stack that automates everything. Idempotence was a core design goal.
Edit2: For local development, I automate everything surrounding the python packages and the virtualenvs for the various repos we have as well. It's pretty damned handy.