I have a question about using the theme slug. One of the important goals of the slug is to create a "namespace" for the theme, and as far as I know, the interpretation has been to have every theme use its slug on all names. But this brings up an issue.<br>
<br>I have an existing theme (Weaver II) and its slug 'weaver-ii'. It is a large theme, and has lots of support functions.<br><br>I'm now thinking about developing a smaller version of the theme - called Weaver Mini, perhaps. Now, since I "own" the slug 'weaver-ii', would it be acceptable to reuse all that support code in the new theme (slug 'weaver-mini') while keeping the 'weaver-ii' name for the support code. Would make maintenance a lot easier, and it seems it preserves the intent of the theme slug rule. <br>
<br>Seems like a general policy on this could be really helpful for lots of theme developers who reuse code. Might even want to extend it to allow re-use of other theme libraries. I suspect there is code in my theme's support code that could be useful in other themes, and allowing reuse of my slug in other themes would help maintenance issues for sure. Since only one theme is active at a time, this seems like a safe way to preserve namespaces.<br>
<br>Bruce Wampler<br>