Support requests for HTML templates is almost a non factor. Some of my HTML templates i didn’t get any support request in 6 months, yet i get a few sales each week for them.
If anything, you get customisation requests, which can lead to nice paid job and ongoing relationships with buyers.
If your template has bugs or bad documentation, you will get users make sure you’re aware of it in your comments – but if you do a good job at writing your documentation, things should be rolling without much friction.
Like visualkicks said, most buyers of HTML templates have some HTML / CSS skills, because there’s not much you can do with a static template if you can’t dive in a code editor, no matter how well your template code is structured.
Australia is incredibly difficult to migrate into.
Even after marrying my Australian wife, it took me a good 3 weeks full time to fill up paperwork, get all the checks needed (criminal checks, fingerprints, chest x-ray, mental tests, character assesments, etc..). It was almost a joke how crazy specific the requirements were.
Oh, it also cost me about AU$ 3,000 in administration fees to lodge the visa applications, get all the documents translated, approved (‘JP’d as they call it) etc.
It was well worth it though, AUS is a truly amazing place to live in.. But it’s not coming easy or cheap, that’s for sure!
Aaaaand 6 days later it’s re-enabled, without changing anything, and without any explanation / apology on what may have happened.
Like i said before, i was not expecting crazy sales over Christmas, and i understand the reviewer took a family break – but it would be nice to just have a “oops, my bad that was a mistake” or an actual reason behind the soft-disable.. Not just re-enable it and pretend it never happened..
Welcome to the land of uber-bloated “multi-purpose” themes
The easiest i guess is to contact the author of the theme on their profile page or check their documentation / support avenues.
I personally hate working with huge themes like that – for the exact reason you mention. You need to figure out how things work, which goes against the WordPress philosophy of being intuitive and quick to get started.
P.S: A bit of a personal question: Did you buy any of your Apple products (iMac, Macbook, etc) from Envato earnings?
Well my envato earnings are really not doing much else than helping paying bills and purchase other envato items
I guess you could say that the envato earnings partially contributed to the purchase of this MacBook Air, but it was definitely not a case of “yeah, let’s withdraw some of my earnings and pay the laptop with that”. I wish though!
Honestly i was skeptical about the Macbook Air regarding performance for CPU heavy tasks, but i ended up getting one opting for portability / battery length, and i couldn’t be happier with it.
I still have my iMac for working from home, but my MB Air is following me everywhere on the go and it works brilliantly. Never let me down so far – hands down the best laptop i ever owned in terms of “making things easier”. Super lightweight, seemingly indestructible, lightning fast to startup / launch apps.. Love it!
So my question is…which computer is best for facbooking, tweeting, programming, and envato-ing
For these kind of tasks – i absolutely recommend the Macbook Air. I am running all my front end development tools on it (photoshop, illustrator, codekit, sublime text, node.js, gulp, etc) and everything runs perfectly fine. If you’re into motion graphics on After Effects, maybe it might reach some limitations, but man i am thoroughly impressed by the performances of that little beast.
On a related note, one of my MODX themes was soft disabled for 2 reasons that make no sense to me, and most probably come from one user complaining to support.
1) the template is not installing properly. The reviewer added a gif of the upload process, and uploaded the theme in a completely wrong location, which explains the unsuccessful outcome. The install process is clearly explained in my documentation.
2) The reviewer is asking for “tips on how to get started with my theme” when my documentation is very detailed with screenshots and a lot of information.
Question to Envato reviewer: did you actually take the time to look at my documentation or did you just take the user’s complaints at face value and soft-disabeld my item before really looking into it?
It’s been now more than 3 days since i asked the reviewer for precisions / follow-up, and nothing is happening since it’s Christmas.
Not that i was expecting incredible sales during the X-mas days, but this is really annoying to have an item i have worked very hard on just being soft-disable for a totally random reason that could have been cleared within 5 e-mails with a simple e-mail to me.
Come on, envato! What’s happening to you?
What i would do is try set the files up in the easiest possible way for the buyer (that will not necessarily be familiar with Grunt) but also make the use of your dev environment available for those who want to use it.
You don’t have to add the bower_components folder – if your files contain the bower.json file the buyers should be able to pull all the dependencies from that file.
What i usually do is provide all the developing environment files (except bower_json and grunt / gulpfile) and have the production files compile in a /dist folder. The novice buyer can just work with the /dist files, while advance users can harness the power of the dev environment with preprocessing like Jade, Sass, CoffeeScript etc.
As long as your documentation clearly explains how to use the files for your project, you can upload any folder structure you wish.