It seems that i am getting mixed ideas from their requirements and what you are saying here. So the question is: can i buy Visual Composer and use it with a theme including it in the theme or not? If not, what could i do? I would hate to have to recreate the wheel if it already was created ( the visual composer )
All that i can say is go with asus. Had HP. Didn’t turn out so well after waranty expired.
mountainthemes saidNo, but users prefer a variety of themes. If all use the same framework, all have the same basic things in them, and those things might not please all users.
From an user point of view do you prefer 45 different frameworks ?
I don’t mean the front end framework. I mean the back end framework like option tree, advanced custom fields and so on. You can do everything you want.An option could be (like Acf) an extendible Envato framework. Any developer has the same base code but anyone can extend it (via plugins). This would be the best way in my opinion.
Now… Envato!! I know you are busy with the bundle, but wheres the FAQ??
Parallelus saidFrom an user point of view do you prefer 45 different frameworks ?
That would be the beginning of a mass exodus from ThemeForest. It would be one thing to offer an option framework like they’ve done with OptionsTree, but to force one (at this stage) would not be acceptable.I can see a community like this being built around a framework where users develop themes specific to that framework and can sell them on the framework marketplace. There are a number of sites doing this, but TF is not structured this way and authors would run screaming if a requirement to use the TF framework were forced on them. 10 new TF like sites would pop up over night to gobble up all the newly available authors looking for a place to sell their work.
No, but users prefer a variety of themes. If all use the same framework, all have the same basic things in them, and those things might not please all users.
Well this bundle is expected every year, so you should get used to a bundle in tgis time frame
Hey envato. It’s time to update your guidelines. A lot of answers were given on this thread. Do you want us to go over all these pages to figure out what can we and what we cannot do? For example: how about theme specific widget? Can we put within theme? I almost sure you already answered that question, but i don’t have time to go over 39 pages. So, it’s time to clean up this mess.
+1 Update your guidelines! And create the FAQ that you promised.
No offense, but with these changes you will only make the customers here have a worse experience than before, because your standards are not clear and do not cover every aspect and every author will end up choosing their own way of doing stuff. This changes are just bad. The only one i have to say i agree with is the shortcode one. The other moves to plugins are just useless.
At the moment i have spend some time reading this whole thread and i am clear of one thing: you have no idea what you want us to do.
I think that you want to make the functionality part of the theme portable to other themes. Basically what woocommerce does. BUT what author wants to spend time on a plugin for lets say their slideshows, and than allow the buyer to take that plugin and use it unlimited times with other themes. What is that? You are confusing wp.org with premium themes.