With regards to Envato providing a support system. I want to voice out that we have features that we find important in a support system aside from plainly providing customer support. Our team for example wants to build our brand and audience, so we have an opt-in mailing list inclusion during sign ups. We will soon also put in links to our other items for marketing. Those stuff would most likely not on the priority list when building a support system.

Basically what WordPress Demo does is that it allows easy creation of demonstration websites for your theme and plugin previews. It allows your potential customers to create their own personal sandbox with back-end access, so that they can give your plugin a full spin. They can fully play around with all of your cool features. This is more powerful than just showing people the front-end.

Previously, allowing people to access your demo was only possible if you create a WordPress site and do a lot of heavy configurations like creating backups and cron jobs for resetting the database and files every few hours. WordPress Demo takes care of everything for you, no more fancy configurations, all you need is to turn your site into a multisite instance and install the plugin.

But personal sandboxes are just the tip of the iceberg. Aside from easy to create sandboxes, WordPress Demo has a bunch of awesome features that help with giving the best demonstration of your plugin. One of which is the preview bar that spans the top of your demo sites. Your visitors would be able to switch between the different plugins you have, view the demo in different screen sizes (desktop, tablet or mobile views), redirect to the purchase link for the product, and they can launch a sandbox directly from the preview bar.

WordPress Demo also supports reCAPTCHA to protect sandbox creation from robots and spam. You can also enable sandboxes to be email activated. Email activation is really helpful if you want to build up your email list for future projects.

Our goal is to let developers worry less about creating a demo site and focus more on their own awesome products.

@kprovance I’ll have to point out that the first two facts of yours may be incorrect. Here’s what I know about GPL:

When GPL is in place, he can change the code any way he wants and can rebrand it to whatever he wants, just as long as if released publicly, the modified framework should still have the same GPL license. I don’t think attribution is required unless specified in the license. Of course, morally the original author and project should be attributed.

@SimpleRain & @kprovance Going back to the topic, I don’t think @splendous is talking about stealing, rebranding and selling the modified framework. From the original post, I gather that he just wants to fork Redux and tailor fit it to his needs, adding features as their themes need them.

@splendous, I think it would be better to just use Redux as it is and build your theme around it without modifying it. You’ll get the benefit of bug fixes and new features for the framework, without implementing them yourself. Instead of developing it further, just create extensions that work with it. Personally, forking it and modifying it completely would be more work and time consuming if you’re simply doing it to create themes.

Since we are in the topic of frameworks, I would like suggest for you to take a look at Titan Framework.

Meta boxes can also be created as well as theme customizer sections with live previews. The options you mentioned aren’t yet available in Titan, although they have already been suggested in the issue tracker in GitHub.

Titan’s getting more and more awesome contributors. Those options will be coming in soon