Hi All,<div><br></div><div>First sorry if I am asking this at wrong place. (In that case, please let me know right place to ask this...)</div><div><br></div><div>Now... </div><div>During review process of our first theme, I felt that there are some "internal" guidelines which decides:</div>
<div><ul><li>What feature should go inside theme OR plugin? </li><li>Which libraries/third-party codes a theme can use?</li><li>May be some more...</li></ul></div><div>All above comes into picture towards end of review process.</div>
<div>For example - I got to know that libraries like timthumb are banned here. </div><div>Also theme-developers has restrictions on adding features in their theme code because somebody thinks a particular functionality should be part of plugin!</div>
<div><br></div><div>My concern is, for our next theme, which is actually our internal base-theme (sort of framework) and contains features like:</div><div><ol><li>Social bookmarking/Sharing controls (twitter/facebook/etc buttons)</li>
<li>Advertising options (like Google AdSense/BuySellAds/Kontera etc)</li><li>Typography options (font-faces/font-sizes/etc) </li><li>Layout Options (2-column/3-column/etc)</li><li>Content Options (Thumbnail size/summaries/read-more settings)</li>
<li>Other options like feedburner integration, favicon/logo upload</li></ol></div><div>There were SEO options also which we plan to retire in favor of wordpress-seo plugin by yoast.</div><div><br></div><div>To give you better ideas, just think of themes at themeforest which provides theme-options.</div>
<div>We have many clients on themeforest for which above said internal framework has been maintained and continuously updated from a year.</div><div><br></div><div>Now question is - if we decide to release our framework in open-source, which features we need to remove (if any) to maintain compliances here?</div>
<div><br></div><div>Also, can we upload themes we have developed for themeforest here? </div><div>Will there be any extra regulations regarding features & options themes at themeforest provides? </div><div>Just a note - themeforest publishers are very aggressive. On one instant a client sent us list of 30+ plugins which he wanted to integrate in a wordpress-theme! </div>
<div> </div><div>We have many themes in our repo, originally developed for themeforest but never launched for various reasons (most common is client defaulting payment). </div><div>We are owners of all graphics/code which we want to release on wordpress theme repo, of course under GPL :-)</div>
<div><br></div><div>==</div><div><br></div><div>My second question is regarding parent-child theme.</div><div><br></div><div>Here is what we want to achieve.</div><div><ol><li>Our base theme (framework) is common across all our themes [Parent]</li>
<li>Each theme has its own set of local changes [Child]</li></ol><div>We want to leverage power of parent-child theme to push updates. If there is any change in base-framework - all child theme users should get a notification about new update of parent theme.</div>
<div><br></div>
<div>Not sure if possible here, specially as SVN access is not available on theme-repo (like we have access to SVN on plugin-repo).</div></div><div><br></div><div>Regarding release - should we release parent and child theme separately? Is there any extra guideline on parent-child theme release.</div>
<div><br></div><div>Also while answering please consider 3-level relationship => parent-child-grandchild as well!</div>
<div><br></div><div>==</div><div><br></div><div>The only purpose of asking all questions in advance here is to save our development efforts and also precious time of theme review team.</div><div><br></div><div>I hope to get some good suggestions/guidance/inputs here. </div>
<div><br></div><div>Thanks All,</div><div>-Rahul</div><div><br></div><br clear="all">--<br>Rahul Bansal | Founder & CEO | rtCamp Solutions Pvt. Ltd.<br>Mobile: +91-9860501882 | Web: <a href="http://rtcamp.com/" target="_blank">http://rtcamp.com/</a><br>
<br>