... This is why I expected there to be a ton of topics opened here on the forums about working together. You all have businesses in an open source community. The new submission requirements are a perfect opportunity to truly take advantage of this fact.
What I mean by this is that people from the TF community should be creating GitHub projects to handle these things so that users aren’t running into these problems. As theme authors, you have an ideal chance to work together and build something that’s actually useful for your users in both the short and long term.If all TF theme authors are putting their own shortcodes into their own plugins, then everyone is kind of missing the point that the phase 2 submission requirements are attempting to address. ...
@greenshady – Thank you so much for your clarification on each question. I was wondering the same thing on the second question that there should be some kind of “global” or “standard” plugin that is flexible enough for most authors then we can build our works on top of it. Whether the plugin comes from the authors collaboration or officially from Envato, it should be working great in this case for both users and authors. (Not quite sure that this is too ideal or practical in the real world though.)
Unfortunately that the phase 2 of the submission requirements didn’t state anything about this. I could see only “the functionality/shortcodes must be in the plugin” stuff. If the situation is still like this until the effective time comes (November, 2013), I’m afraid that the authors, including me, couldn’t avoid creating self plugins containing shortcodes to pass the review process (and yes, the issue like the sample scenario in my second question will persist).
I believe that Envato and every staff are working hard on it to make the phase 2 requirements much more precise so the authors have the right direction to go in both short and long terms. Hopefully to see the official words from Envato soon.
I think this might be already discussed before, but I’m still curious that:
1.) If we need to put all shortcodes into plugin in order to prevent the lost of user content when switching themes, does it mean that we also need to put all shortcode CSS styling with the plugin?
I ask because if we don’t put styling with the plugin, the content will surely exist after switching but they will mess up with no proper CSS in the new theme. It is then useless in my opinion.
But if we do put styling with the plugin, the content and CSS will exist in the new theme but the style might not match with overall look and feel of the new theme (and there may be some CSS conflict occurred). Is that the user issue to customize the plugin styles? We do not need to worry about this issue right?
2.) If every author put the shortcodes into their own plugins, don’t you think that the user/buyer will end up with more useless plugins after switching themes?
Scenario: Author “John” published his theme with “John Plugin” that included all the shortcodes to be used with the theme. A user bought and used his theme. Several months later, the user wanted to use another theme from author “Mary” who also made her theme with “Mary Plugin”.
The user switched the theme from John’s to Mary’s. Perfect. The content and shortcodes were still there because “John Plugin” is still active. But he then realized that in order to make the styles of shortcode work well with Mary’s theme, he needed to use “Mary Plugin”. And now the user also noticed that there are mixed custom fields and meta boxes of those two plugins on the page’s edit screen.
The problem here is: if the user disable “John Plugin” to use “Mary Plugin”, he will get messy shortcodes/content generated by “John Plugin” and the plugin is then useless. This is not different from “not using plugin at all” in the first place.
How do you advise in this case? What’s your opinion?
3.) Regarding the previous concern, you might think that then most authors should use any of the existing plugins instead of creating their own plugins.
If so, don’t you think that the theme author’s ideas and creativity will be limited by the existing plugins? What if the author wanted more “unique” styles and functionality that none of the existing plugins could provide?
I totally agree and I’m all in for the new requirements to embrace with WordPress best practice but I still have some questions as above. It would be great if someone can point me to the right direction.
I recommend MediaTemple (VPS).
Thank you all for your great suggestions! Now I have more things to learn in the coming week. Hope I’m not going to tear my hair out while working with it.
Could you guys advise where to start learning how to make the theme fully supports WooCommerce plugin? Are there any requirements or checklist available too?
Perhaps the “food” keyword may be a good start to find the themes/templates that fit with truffles product. Try this link: http://themeforest.net/search?utf8=%E2%9C%93&term=food
Using Visual Composer plugin