You could find designers with PSD’s and convert them to WordPress using your framework and then sell them here.
I think it’s time that the Software Freedom Law Center update their opinion on themes as derivative works. Since 2009, when this post (http://wordpress.org/news/2009/07/themes-are-gpl-too/) was written, WordPress themes have come a long way. The SFLC based their opinion on the “classic” and “default” themes included with WordPress 2.8. These themes were little more than the standard “loop” pages (index.php, page.php, etc.) and some code in functions.php but today’s themes are much more complex than that, with options panels, page builders, etc. Today’s themes have massive library folders with code that could easily work without WordPress. This additional code is not necessarily derivative of WordPress code, and therefore not necessarily subject to GPL. I think it is time that the SFLC re-evaluate their opinion on all PHP in themes being derivative.
Been working for quite a few months on my newest app, and it gets approved for the same price as an app I spent 30 minutes on.. sort of discouraging
You should make more 30 minute apps then! I’m just about to wrap up my first plugin to submit (saved the documentation for last), but I’‘m wondering whether it is worth it to have a $10-$20 regular license and $50-$100 extended and maybe sell a few hundred copies. I was planning to make a full theme and include the plugin, but I might just go for the theme from the start. $45-55 regular license and a $2250-$2750 extended sounds a lot more appealing.
So far I have seen some authors creating around 5 or even more themes that run on the same main code, slider, shortcodes and even structure, just the styling of either the font and other elements varie, hence leading to the question if I may use some elements again in future works.
You’ll find that the first time you create a theme from scratch you end up writing a lot of code that can be reused for your second theme. The admin panel can probably be reused, as can most of the shortcodes and widgets. A lot of the templates will likely be the same, such as the index, page, search, 404, etc. I bet you could submit the same theme 10 times and just change the stylesheet and the name.
The new license rules require you to get permission from the author, but the author can allow everyone permission by placing a note on the item page. This author put the following note on the item page:
If you want to use the RevSlider in your Theme here on ThemeForest too please purchase 1 extended license for each theme (as long as there is no Developer License available) you put on the marketplace! If you have questions about this agreement please contact us: http://www.themeforest.net/user/themepunch#from
Be sure to take a screenshot of that and keep it on file
I plan to release my first plugin in the next few weeks. I’m going to refuse to allow other authors to use it in themes, and then I’ll release my own themes including the plugin, and advertise them as the only themes that include the plugin ($20 value). Hopefully it boosts sales!
Any word from Envato staff on the scenario I presented above? I know that the terms do allow you to register on behalf of a “third party (which may include your employer or other entity)”, so clearly this is allowed. So what if you work for a big company and you create an account on their behalf. When you quit, the company should keep the account. The same principle should apply for a company of one. If I register an account on behalf of FillerSpace Inc, and then resign, the company should still own the account. If someone then buys FillerSpace Inc, the account did not transfer, it still belongs to the same company.
Technically, you could transfer your membership, even though the terms say you can’t. You are allowed to register on behalf of a third party (e.g. your employer or business). You can then sell the business that owns the account. The membership still belongs to the business, so no transfer took place, but the business belongs to the new owner.