Thanks Vlad, we’ll definitively be getting there, hopefully really soon.
Also with a builder like this you hardly ‘design’ a theme for it. It’s more like a full site builder than something else.
As is with most builders – people who buy it kindoff design their own site.
And all they ever get is the same old same old paralax sections, sliders and columns with icons.Themes with those builders nowadays are too much of a blank canvas if you ask me.
It really depends from the approach the author wants to take.
Authors can definitely design a theme for it ( or with it ), an example would be this theme, it’s made with existing modules and options. And custom modules can be built as well of course.
It was the revolutionary one (world’s first, or atleast envato’s first) that brought Front End Live Editing to light, as far as I’m concerned. Then, all the other plugins, naturally, copied it. It was just too good not to.
If Dany did that before Visual Compo – he’d be rolling in $3m shoes now It’s literally no different than Visual Compo, even better in some areas such as the range of options you have to edit for each element…I’d say.
Hehe, the first “regular” page builder on Envato was mine as well.
My name is Slobodan, I partnered up with Dany about a year ago, you guys might remember Content Composer ( WPScientist ), but was only in my themes, was a mistake that I didn’t turn it into a plugin.
What about LIVE Composer by DanyDuchaine? It also has a lite (free) version. Looks promising and very friendly.
Thanks. It’ll get better and better, another update coming up this week and we also have some big plans with it ( but that’s all I dare to say, don’t want someone beating us to it )
Live Composer was buggy from the start and that killed it. He didn’t payed attention to performance and that’s a big mistake.
Version 1.0.6 will be mostly focused on performance.
Live Composer is the biggest thing we ever built and we’re really proud of it and will keep improving it, hopefully at one point it’s gonna get on top of that popular list
Which plugin caused this issue?
Haven’t heard of someone being soft-rejected for using TGMPA before, it’s the preferred method, we use in the last 3 themes and will continue to use it in upcoming ones. Perhaps it depends on the plugin, which one was the reason for the rejection?
Make sure you have mod_rewrite turned on in Apache settings.
Hehe, that was the first and could be the last time it happened.
Yeah, I thought so as well. But not sure because he won’t be making the websites for them, they’ll make them themselves.
Something like Orman’s “Dunked”. They register, pay for features and create the website.
It’s definitely not a single regular license. Either regular per user/website or extended. Hope someone from the Envato team will sort this out.
Got a question regarding my plugin and not sure what to answer, hoping someone here can clear it up.
Here’s the question ( a bit fixed up ):
I will build a website to give my clients/users the opportunity to create their own website. I do not charge them to build their websites, I will charge them for hosting and some other features. They will be able to create their own site. Which license do I need?
So, is this one regular, regular per customer or extended?