No one is against a stricter code moderation. It’s kindly great to improve our skill level.
The problem concerns just to plugins that will come with themes and have no relation to another themes. What is a sense to convert an options framework or shortcodes into a plugin? Bad code will never works properly regardless of whether a plugin is or embedded code and it will not reflects on the compatibility with other plugins. It’s a damn pain for customers/authors only. In any case, a buyer does not find any paid/free solution to get the functionality like in our demo if our “Custom Portfolio Plugin” (just for example) is crooked and I’m not even talking about the styles of specific design. “Lego” themes are not for TF in my opinion.
Thanks! It’s nice plugin but an archive from github is broken. Anyone has it?
Yep, the same. It decreases into the habit in due course, but sometimes I worry a lot
I can suggest you to polish coding skills because your layout is not good at all. Also check a difference between look and feel of your template and of any one from Themeforest.
Thank you for your e-mail! We’ll respond as soon as possible.
Totally agree with VF. At nowadays there are too many new items get approved on the same day and popular files go out too fast. I think Envato staff already working on some kind of solution
As for me design is nice but a bit generic. I think it is somewhere between typical and minimal design, but neither the one nor the other. If you want a minimal design, you should review the typography and whitespace. If typical, then add more details that would attract the attention of buyers.
Design is a more important part of the work for TF, IMO . Usually 50/50 – designer/developer, not a couple hundred dollars
While I agree that a couple hundred dollars is somewhat low for the amount of work, I disagree that it’s worth 50%, considering how many hours of work that have to be put into converting a PSD into a fully functional website. Like I said before though: the low flat rate would only be for the first item. The reason for this is that in order to pay you more, I have to make more money first. After I start making money, I would be more than willing to pay larger amounts. I have to start somewhere thoughAlso, I tend to try and avoid the partnership business model, because there is no guarantee that the contracted individual will actually get paid for his/her hard work. The flat rate model that I proposed would make it so that I personally assume all of the risk. However, if a designer is willing to take the risk of doing a partnership, then I’ll be open to negotiating a fair profit split, or alternatively doing a combination of a profit splitting with a low flat rate.
Yes, I know how many hours devs spend on conversion, but PSD is a basis of quality work and the result – high sales in the future. A code and theme features is a secondary question. For this reason, I believe that designer/coder or dev have to split 50/50.