Obviously, I have had more experience with WP than any other CMS platform. You’re probably also already aware that WordPress themes are the highest in demand on ThemeForest since these days it’s a much larger target market than say Joomla or Drupal.
Don’t pick a framework for just for it’s features. The more features, the more bloat. The more bloat, the more complicated it is and the more conflicting causing potential it has. While not always the case, such bloat can cause (sometimes serious) performance issues. Picking a framework for it’s features is somewhat like selecting a house for it’s appliances.
Instead first ask yourself, what kind of grid system you want. How many columns / how wide. For example, I never use anything less than 12 columns / 1170px or anything larger than 16 columns 2560×1600. Seek these details out and you’ll find that there’s many grids that are limited to just the small 960 grid which is getting older by the day. You don’t want to a something that has an old grid system because it’s got little if any future flexibility.
Hints: The Warp 7 WP framework accesses the webhost file system using direct PHP calls instead of using the recommended WP ones. This seems pretty lazy to me but not everyone feels the same. It also causes security issues on various hosts that your buyer might be using thereby making it your problem when it fails to work. The Gantry framework typically makes use of the MooTools (jQuery alternative) that I’ve seen cause multiple conflicts with 3rd party plugins. This is a carry over from their Joomla development and doesn’t always work well with WP’s built-in core jQuery.
I am still ignorant of so much but just know your theme’s foundation (if you didn’t build it yourself). There are too many frameworks available (even just for WP to go through each one here). So, try your best not to be ignorant of any unknown (known are fine if you can live with them) dragons / gremlins possibly lurking in your chosen framework with and you’ll be very thankfully you took the time to have a look around.
No, you can’t just take someone’s works change it a lot and call it yours. Using either frameworks would earn you a rejection here. For example, just so you’re aware even with the so called “Developer” license of Headway you aren’t given the “right” to redistribute the framework itself for resale purposes unless you do it on their own marketplace.
Another thing, any framework that actually grants resale distribution as a right but also expects you to distribute your work as a “Child Themes” is in IMO a bad idea since the end user now has little recourse but to modify the child theme, potentially loses their changes with each update. The proper thing to do would be to either build the theme from scratch using a custom made framework or any framework / foundation that lets you create a proper parent theme so that the end user can use a child theme for custom styling / modification purposes.
If you’re looking for shortcuts to the path of wealth here on ThemeForest, there’s not many legal / ethical ones (if any). You say you’re a designer. So, make a totally custom PSD design and submit it to TF. After it’s been approved, then code the PSD into HTML. Once that’s approved, code into a WP theme and get that approved. You’ll learn a lot along the way and you’ll know that you got started the right way. You don’t have to submit a PSD / HTML theme first but to submitting a WP theme as your first item could turn out to be quite the daunting / discouraging task without having more experience.
Even if approved, after you’ve sold your item then you should know how to support it. Do you want to know your item well enough to help your buyers with them problem. They usually can’t / won’t wait weeks for you to figure it out (possibly because you don’t understand all the code in your theme). Short-terms authoring isn’t very profitable around. You need a long-term plan.
It sucks you got duped but if you want to stick with the theme at least the fix can be relatively easy. Just buy a license for Neighborhood under your own account (even if you don’t think you should have to – don’t let the past hold you back any further) so that you can receive updates and Ed (the author) being the awesome guy that he generally is can have a proper change to do his best to sort your situation out.
I’m sure if you haven’t already wasted $55 of time, you probably will soon. Besides, the theme got a new update this week and you should probably apply it be before seeking support for an issue that may be fixed by being on the latest revision. You’ve probably missed more than one update that may be causing your issue right there. Hopefully, you’re running an unmodified version of the parent theme and / or all the changes were made to the included child theme.
It’s too bad the title of this thread can’t be changed to “Who has got an awesome and UNIQUE WordPress Drag and Drop Page Builder in their theme” to discourage postings about themes that feature the common / pedestrian / unmodified / uninspired copies of VC. Including VC in your theme isn’t awesome, it’s easy. It’s almost becoming the status quo here. Though there are some really talented authors out there doing some truly awesome things with their extended license purchase of VC.
Thanks for putting a note, the problem that you mentioned has been fixed. We’ve optimized the product about 40% . So it should works smoothly.
I see. Just tried it again – better. However, I’ll suggest the following…
1) The “Text Settings” popup / modal dialog is far too small (specifically the actual WYSIWYG content editor area) especially on large monitors with resolutions of 1920×1080 or 2560×1600. Feels somewhat claustrophobic in there. It’d be nice if it dynamically re-sized to fit the width of the screen. If that causes too many issues, making it bigger or even offering an option to specify the width manually would be great.
2) It’d be nice if the ””Full” state remained / persisted after the “Publish / Update” was pressed. It seems to want to keep reverting to “Compact” mode every time. Don’t know if that’s intentional or not.
Here you go:
My own Drag & Drop GT3 Page Builder http://www.gt3themes.com/wordpress-gt3-page-builder-plugin/There will be an official release soon. You will be able to use it in the themes for sale on TF
Does it support Bootstrap v3 and a 12 column / (at least an) 1170px grid? Bootstrap 2 and 960px grids just aren’t enough for my needs these days.
Why not just allow one “base” theme for a “base” price
If the author likes to offer a Woocomerce version (s)he should build an additional WP pluginThis way buyers get what they want (more features for more money), people don’t turn away cause of “bloated themes” and the homepage/popular page doesn’t get flooded
If the author likes to offer a BuddyPress version (s)he should build an additional WP plugin
A decent idea. That sounds like something that could possibly work. I’d support that kind of model anyway. The only problem with it is TF author may not want to be CC authors as well and the TF home flood is perhaps just shifted to CC instead? Authors that did this would get likely additional exposure by having Plugins.in addition to their Themes. That’s either a positive (IMO) or negative depending on how you look at it.
I would think one regular per client site would be enough as long as the buyer isn’t reselling your plugin inside a hosting bundle that includes your plugin. Even better would be for the clients to purchase the regular license themselves.
I suggest doing your research before investing in a theme. If you’re not comfortable either doing the research or can’t visualize how your site would look in a given theme. You may benefit from hiring a professional to properly guide you who may prevent you from making one or more potentially costly mistakes?
Thanks, Envato! It’s appreciated.
Diabolique saidResponsive isn’t just about making the website display on a mobile device…I have a new smartphone and using this site on is horrible so I don’t bother, and I probably am not alone
All modern smartphones can display full page (HD), there is too late for responsive layout.
Indeed you aren’t alone. I totally agree.1000%. It is needed and about more than just whether or not a site can load on any given mobile device or not.