No problem. I won't sully the WordPress site with my 'below par' (at least as far as you're concerned) work.
I never said that your work was sub-par. I said that generated code, such as that produced by Artiseer tends not to be up to current standards.
I have also taken a look at the background documentation of themes on the site and the main reason I started designing was for myself because I was very unhappy with what was available. There were numerous issues with formatting, etc. and there is plenty of documentation on WordPress' site regarding ongoing issues and bugs to do with themes that have been accepted and that supposedly use 'non-obsolete' code.
Indeed; it is a constant issue. There are Themes in the repository that are long-since out of date. I have no control over anything already in the repository.
My belief is that elitist attitudes such as yours only serve to stifle creativity. I take great offense at you referring to my themes as not being 'creative' or 'original'. They are both and have been and will continue to offer my work elsewhere.
Again: I've no intent or desire to stifle creativity.
By the way, what position do you hold with WordPress that you appear to be the guard at the gates keeping us 'bad folk' out????
I'm just a lowly Theme Review team member. On the one hand, I'm tasked with enforcing certain policies set by others (e.g. the license issue for other Themes on your site); on the other hand, my personal concern is raising the level of code quality, to help avoid issues of security and code obsolescence in the future.
PS. The reason I started designing my own themes is because every single theme I used from the WordPress library after every WordPress upgrade, the themes conflicted and became unusable. Evidence of this can be found on any one of my four blogs in which I posted about these problems.
Yes; Theme obsolescence is a huge problem. The Theme Review team has only been active for about 9 months. You should notice a sharp increase in code quality for Repository-hosted Themes submitted/updated since late last summer. But as of yet, we can do nothing regarding already approved Themes that are obsolete.
Ironically, Artiseer has been a huge contributor to the problem of code obsolescence. I can't tell you how many Themes I've seen submitted for review that were generated by Artiseer, using code that was several versions out of date.
I've had to do one upgrade since using my own themes on all of my sites - with no problems I might add? Maybe simplicity (or what you consider obsolescense?) is the best??
Simplicity is great. Simplicity isn't "obsolescence". Simplicity is also the polar opposite of Artiseer-generated code.
Here's the bottom line: you don't need Artiseer. You don't. I have complete faith that you can learn the WordPress template system entirely on your own. (I did it - and if I can do it, anyone can.) And when you do, you'll write better, cleaner code than anything Artiseer could ever hope to produce.