Are you implying that your web site does not have any "little comp-sci type things on the server" aspects?
"Add an opacity slider for shapes"
This seems like the kind of thing that probably does have a little comp-sci part to it. Do you have an abstraction for shapes? Maybe a unit test for the API underlying the slider, that validates that all selected shapes now have the opacity value passed from the slider?
Maybe that doesn't fit the design of your code, but I strongly suspect there is some unit testable part of that task. The point being, unit testable things should have unit tests, and most tasks might have some unit testable part.
For the issues I listed above, how many of them do you actually consider to be testable, using TDD's "write your tests first" definition of the word.
- "Timeline ticks don't line up with grid when changing scale"
- "Resizing shapes is jerky in FireFox"
- "Need a button you can hit to pull up a simple Help screen"
- "Add an opacity slider for shapes"
Unit testing rendering correctness during mouse actions? Unit testing for UI features? Unit testing for CSS? Hacka please.
If you're doing little comp-sci type things on the server then sure you can do TDD. It makes sense in the context of building a string library or wrapping somebody else's API. In the web startup world though, how often are you actually doing that stuff?