So, you mean to say, let buyer purchase regular or extended licenses themselves for these plugins according to their requirement? We as authors will create a theme based on these popular plugins and let buyer’s decide which plugin they want? Is that what you trying to say?
Doesn’t seem like a bad idea. Why can’t we simply include the slider exports in our theme package, for example? If a buyer wants to go buy the slider at CodeCanyon, they can simply import the sliders as needed.
The reason I even brought plugins up is the cliche “5 plugins included for a $300 value! 40+ demos! Buy now, this is an amazing value!” marketing approach which has become commonplace here. Many authors thrive on this type of sales pitch, which brings us back to the root of the problem with bloated themes. Are we selling themes, or bundles?
My previous posts were intended to be food for thought, more than anything. Although getting rid of extended licenses would help put a stop to this trend with bloated products, and make packaging multiple demos into a single theme package more difficult, I doubt it will ever happen.
Plugin bundling is fine. This ain’t about plugin bundling. This topic is all about multipurpose themes priced ridiculously low. If theme has 10+ demos with bundled plugins, such multipurpose themes should have their own category and an altogether different pricing.
I respectfully disagree, I believe plugin bundling encourages bloat and this “swiss-army knife” mentality which is the root of the problem (bundling is also a huge security risk, but that’s another topic entirely). Buyers have come to expect bloated packages, we’re not even selling themes at this point—people think they’re buying a complete website, which I suppose they are when you consider the current situation.
Authors are cramming as many “goodies” into their download package as possible to increase sales and stay competitive. This may come in the form of plugins, or demos, or theme settings… at the end of the day we’re talking about bloat, aren’t we?
The “get rid of extended licenses” scenario was just one example, regardless of what is done I’m sure profits would likely suffer (at least in the short term).
I spoke to Collis about this, and he put me in contact with Stephen Cronin about it, who said they would look into it internally and told me to chase him up on it, but I decided not to follow it up, as it is clear to me that no one with the power at Envato has the desire to change it, either through being out-of-touch with the WordPress world or through sheer fear of dealing with such a big pink elephant.
I think it boils down to profits, really, Envato will lose money if they change their policy and deal with the problem. Let’s just say, hypothetically, that Envato got rid of the extended license and authors were no longer allowed to package page builders or slider plug-ins with their theme as a starting point. How does this effect the market?
The “powerhouse” CodeCanyon authors would probably see an increase in regular license sales and ultimately their overall profits (it only takes about 5-6 regular license sales to add up to an extended license price). Many customers would just pay the extra $20-30 for the plugin if they really wanted/needed it for their site.
Most ThemeForest authors, on the otherhand, would be completely screwed. Sure, there are some talented WP authors here that have written their own page builder or slider and these people would be fine. But an overwhelming majority of WP authors strike me as designers first, developers second, these authors rely on frameworks or plugins to compete with legitimate developers.
In this scenario, Envato would see a huge drop in WP sales and miss out on millions of dollars. I think the same would happen if changes were made to how demos are packaged, or priced. The company will have to take a significant hit in profits if they really want to make a difference, I don’t see much changing.
Any thoughts about this !?
Happy for my T-Wolves, I didn’t see the Tyus Jones trade coming either so that was a nice surprise! Knicks fans would have complained no matter who they picked.
Towns/Okafor will probably take a year or two to adapt to the NBA game, too, this is usually the case for rookies. Regardless of who the Knicks had picked, there would likely have been an adjustment period.
What were Knicks fans expecting? It’s going to take a lot more than a first round pick to fix that roster.
Eclipse when using Mac OS X, and good ol’ gedit when using Ubuntu + Gnome.
As a developer, I grew up using Eclipse but if you’re a Linux user and looking for something more lightweight I recommend checking out gedit! With plugins, you can essentially turn Gnome’s default editor into something like Coda or Sublime Text for free.
I hope the Warriors win it. The bench is deep and Lebron is only one man .
I feel sorry for Klay Thompson, he’s worked his tail off this year and doesn’t deserve to miss the finals… hopefully everything works out in the end and he’s healthy enough to play. Warriors are going to need him!
His agent is now saying he has passed all concussion tests, which is a good sign.
Bulls vs Warriors that would be a tough match up.. I like to see the bulls in the finals but they need to beat Cavs first
Although Kevin Love’s scoring is down this year, he was still a key part of the Cavs’ offense—even if he isn’t shooting, he opens up the floor for Kyrie/LeBron. Cleveland is going to miss his offensive presence and rebounding against a very good Bulls team!
I’m hoping for Bulls vs. Warriors as well.
You need to understand that a vast majority of Drupal authors aren’t designing their themes—they’re simply converting already existing templates which were originally released in the WordPress or HTML categories. Most of these authors are front-end developers, not designers or even Drupal developers for that matter.
As a result, you’re not going to see much unique work… all of the functionality and design elements have already been decided by the original author of the HTML or WP version.
I totally hear you and agree with your assessment, but as long as Envato keeps approving these generic conversions and buyers keep buying them, I don’t see much changing. In my opinion, conversions should not automatically be approved anymore, and Envato should start enforcing Drupal coding standards as well.
I know this isn’t really an achievement and something we can simply toggle on/off via user settings, but a badge bringing attention to the “available for freelance” option would be awesome. Right now, a small text area on our user profile is the only place where this feature is displayed.
A considerable amount of my income over the past couple of years has come from ThemeForest customers asking for customizations to the themes I sell, it would be great if our availability was made more prominent around the market and badges do appear on a variety pages (not just our user profile).