Would you be cutting it up onto a 'backbone' of our choosing (like 960.gs or blueprint) ? (Obviously this will depend on the overall design, but hopefully the idea is clear).
I was just thinking of something similar; Would everyone want HTML5 elements or rather not?
My thinking right now, is I would build an order form that has a few predefined options. I usually use my own CSS starting point but am familiar with 960.gs. Blueprint seems to be the other big one, so I could look into adding support for that.
But mostly, the markup and css would adhere to my standards. I would have to do this to make the development time minimal so charging to low price makes sense. I would of course offer example markup on the order website.
The benefit for a coder of having it built on blueprint is that it can be worked with immediately - otherwise one might as well be working with a template from a theme site with unknown/inconsistent markup.
Basing it off a well known framework should (a) make life easier for you, (b) give your work a hook other than low price-point.
Valid points. If there was interest in this I would offer the choice of Blueprint or 960.gs. As for HTML, I would use my starting template which resembles HTML5-Boilerplate and the choice of HTML5 elements(header, footer, article etc.) or not.
In theory, this would be a decent paying day-job. I spent the year of 2008 converting PSDs to WordPress themes for $500/theme. With that experience I can convert a PSD to markup in under an hour per page.
My thinking right now, is I would build an order form that has a few predefined options. I usually use my own CSS starting point but am familiar with 960.gs. Blueprint seems to be the other big one, so I could look into adding support for that.
But mostly, the markup and css would adhere to my standards. I would have to do this to make the development time minimal so charging to low price makes sense. I would of course offer example markup on the order website.