<div dir="ltr">Hi,<div><br></div><div>I submitted a theme (<a href="http://themes.trac.wordpress.org/ticket/11255">http://themes.trac.wordpress.org/ticket/11255</a>), it was reviewed and not approved because it uses a drop-in library (<a href="https://github.com/slobodan/WordPress-Theme-Customizer-Boilerplate">Theme Customizer Boilerplate</a>). It's something I developed, plan to use in other themes as well and hope others will find useful too.</div>
<div><br></div><div>As reviewer pointed out, because of Customizer Boilerplate, there are two different prefixes in theme folder, one used by theme's functions (thsp_), the other one (thsp_cbp_) by Customizer Boilerplate.</div>
<div><br></div><div><a href="http://make.wordpress.org/themes/2012/03/14/theme-frameworks-and-namespacing-guidelines/">Theme Frameworks and Namespacing Guidelines</a> post states that something like this is allowed when Theme frameworks are used. In that post Theme framework is defined as "not a stand-alone Theme, but rather a “drop-in” code library used to facilitate Theme development", which would be a perfect way to describe Customizer Boilerplate. </div>
<div><br></div><div>So, can I keep Customizer Boilerplate as a drop-in library, with its own prefixes and all, or do I have to rename its functions so prefix is the same? Doing that would make maintaining boilerplate and using it in themes difficult though.</div>
<div><br></div><div>Thanks.<br clear="all"><div><div dir="ltr"><font size="1"><font face="arial, helvetica, sans-serif">
</font><p style="font-weight:800"><font face="arial, helvetica, sans-serif">---</font></p><p>
</p><p><font face="arial, helvetica, sans-serif"><span style="font-weight:800">Slobodan Manic</span></font><br></p><p style="font-family:tahoma,sans-serif"></p></font></div></div>
</div></div>