@ dtbaker — Sorry, definitely won’t be going on Github. Building this was a $XX,XXX investment for competitive advantage. Not trying to be Scrooge-y, but this is a business. If it’s successful, expanding into a SaaS offering is an option.
@ ait — Short answer: the product will only be sold on ThemeForest (the license), but the updates will be sold/distributed by me.
True, I also do not like the way Evanto set the price, however after some thought if Evanto allowed the author to set the price where would that lead? It would lead to authors undercutting each other, after a few years the most fully featured scripts would be sold for like $5 because of the undercutting. So it would be an even worse situation.
Simple solution that Envato will never let happen: minimum price and no maximum.
Having the lowest priced marketplace is good economics for Envato with high traffic and many authors, but bad economics for the average author. If authors had pricing discretion, an individual’s income may rise but Envato’s would probably fall.
Paid support seems ok and already in practice, but how do you plan to offer paid upgrades?
I’ll be charging for updates very soon. Waited years and years and years and years (that’s 4 years) for Envato to take its head out of the sand, but they finally spoke in November 2014 they think paid support (i.e. access to writing item comments) not paid updates is the way to go. I think that’s absurd and monetizing something of far less value.
Have spent several months time + money investing in building a platform for distributing and selling updates independent of selling the initial license (though it allows for that too). You will need a verifiable license to buy updates of course.
Note: I’ve always charged for consulting and customizations, and provided basic support for free (<5 minute Q&A). People have no problem paying for services when they get value. I’m simply tired of Envato forcing authors to give away updates for free — if not by policy — but by pressures designed into the marketplace.
Time to put on your business suit and be Jack Donaghy.
Envato won’t build the tools that authors have been asking for (for years) to keep up with the support volume on ThemeForest. Authors go to external support systems because it makes support half-way manageable. It’s not because we want to complicate the buyer’s experience. Envato just isn’t pulling its weight in building the platform both authors and buyers need.
You need to buy a new license for each project. It doesn’t change if you modify the theme or make child themes, you’re still using the base and need a license for each project.
Think of it like buying a Mustang from Ford. You can customize it and sell it. But you can’t just walk back onto Ford’s lot and take another Mustang without paying for it to keep distributing “your” version of the Mustang.
You can buy the license, provide the customized version to your clients, and charge them more than the theme’s cost for your services. That’s why most people here do that buy themes.
I update my changelog after each release: http://acumen-magento.gravdept.com/tour/changelog/
It’s a manual process, but it’s more readable. That isn’t necessarily true from extracting git commits.
For documentation (especially on large projects or with multiple contributors) it’s probably better to look into generators that scan your code for DocBlocks. Haven’t really found the need for it in themes/plugins because the if you’re already writing the DocBlock that’s usually enough documentation for simple things.
All the hours