In the case you describe you might nevertheless want to use a subtheme if the changes you'll be making on the one you'll use as starter are mostly cosmetic and you want to benefit from future bug corrections or ameliorations that the authors of the starter theme might introduce.
These days, theme's are viewed much like contributed modules which code you usually do not alter but rather override in other places. Personally, I think themes are quite different from modules and that there's a good chance that future ameliorations of a theme produce unexpected results on your website but, nevertheless, this seems to be the current mainstream thinking nowadays.
Roberto
------------ On Sun, March 13, 2011 4:44 pm, Fred Jones wrote:
Here http://drupal.org/node/225125 one can find a few ideas why one might want to use a subtheme. But if I have a site that needs only one theme, it's just one site, and there's no real interest in playing with ideas of different looks, is there any reason to use a subtheme of Zen or Blueprint as opposed to how I always do it and just make a fresh, 'regular' theme?
Thanks.
[ Drupal support list | http://lists.drupal.org/ ]