Can we include the script which will be initialized and used by plugins only? It doesn’t used in the theme while plugins aren’t connected, but it loads. For example, slider is used in the shortcodes, while “CPT” plugin is connected and for any other advanced options. It’s very bad if you have to duplicate the script and use different dependencies.
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.