Safari for Windows should be a closed project.
Sorry this is against forum regulation, stuff will reply asap.
I mean sample themes as free wordpress themes of the month from Themeforest or any other featured themes developed by various developers and offered for free.
You are actually an older Envato netizen, anyway the list is quite simple:
THE GENERAL VIEW
- notepad++ / brackets
- photoshop +/- gimp
- wordpress kit
- frameworks: redux, favpress, unyson, option tree
- sample themes, free themes
- video tutorials
- use brain
- do creative
- don’t copy others
- be unique
Would this mean I can’t sell my support anymore? What next, paid customisations, so I can’t charge for customisations anymore?
This is another problem Envato have to deal with if they insist on their policy change. Many authors already offer paid support how can you deal with this.Please guys give suggestions for this situation. If anyone interested in reading my suggestion, it’s in the previous page … http://themeforest.net/forums/thread/item-support-timeout-gathering-more-data/140559?page=21#1109070
We should just remove the term support from the equation, it’s too open for interpretation.
Make some kind of warranty mandatory (item has no bugs – bugs will be fixed, item works as advertised, item will be updated for x months). This will also remove a lot of frustration from authors, as with the term support, of course some people will think you will do a certain degree of customizations for them, or install WordPress for them and so on. Nobody will think of those things if you change the term support to the term warranty.Then give authors the ability to sell support, customizations and so on on a voluntary basis with their own prices (in a given range – similar to the old elite author price adjustment tool), give us a forum for that and take your 30% off of that.
Agreed- “Zero bugs policy” kinda terms we used to describe the warranty we would given to our work/customization- it works nicely to give proper impression that “item has no bugs – bugs will be fixed, item works as advertised, item will be updated for x months”.“Support” is a vague term- gives wrong message most of the time if not always.
+1 This sounds great.
Well Ciprian, some simply edit directly to those Bootstrap CSS files, others use addition CSS over the BS css, or both methods combined, but the late and perhaps more important method for future development is pre-processed css, using LESS or SASS, I would recommend SASS, some users find it more powerful, but I have to stick with LESS, for no real reason, it’s just because I started to work with. So it gives you some control over the final outcome with little hustle on finding where is the damn border/margin/hex in the css for this specific case, no no, we have to forget that now. Now the final css is a very well organized+optimized css with less work.
So head over to github and grab the LESS or SASS sources and go through all the documentation or tutorials you can find.
Best of luck.
I ignore the tone of the message, lack of politeness, capital letters, asaps and all other things, I just read what the problem is and treat the message as a regular one and give the proper response.
Most of the customers change their attitude after receiving a standard message that ignores their tone, for the very few customers that don’t, they get ignored.The only problem with this method that works fine for me is that after support becomes mandatory I’m not sure that I can ignore any customers or if I will get into trouble by doing that.
Collis was talking about author issued refunds, and I think this is very much the case here. As of today’s terms, you can politely ask your customer to change his hosting if it’s a server side issue, or ask him to request a refund, as wasting time for anyone is real the damage, not the money lost of refund.
What about LIVE Composer by DanyDuchaine? It also has a lite (free) version.
Looks promising and very friendly.