Quote:
Originally Posted by DirectPixel
It just ended up requiring too much of my time that could've been spent on doing other things that pay better and are personally more enjoyable.
As much as I love designing, it really becomes a pain to test and debug each skin every time a new release comes out, while still providing support for the skin (and for those who haven't upgraded)--in addition to doing custom design work and maintaining clients' servers and being on-call for back-end tech-support.
You do realize that vBulletin uses the <font> tag everywhere, especially on showthread and BBCode-generated code, right?  What I've (slowly) come to accept with vBulletin is that while you can get standards-compliant XHTML code, you can never go beyond that (except for recoding every single template, of course) and achieve semantically-correct code, tableless layout, and seperation of XHTML content and visual display.
(This auto-merge code is pretty neat!)
|
Have you ever just thought about maybe offering budget templates for ?5 -?10 a chuck to the mass market that come with "no support" due the the price there sold for as an alternative method of still selling mass-market templates. But at a budget price with no support because of the price structure there sold for. Then that would free up the support side of them templates sold, while still offering templates at a budget price for specific vBulletin versions only.
That would then leave another avenue to make cash from sales and not have to worry about supporting them low cost templates.