[theme-reviewers] Theme name slug question

[Chip Bennett]

The theme-slug-as-namespace Guideline should not be taken to be *quite* so
dogmatic. The ultimate intent is to avoid a namespace clash. Such clashes
can happen when using abbreviations or acronyms based on the Theme name (or
when using arbitrary namespaces), which is why the Guideline is written the
way it is.

Personally, I think it would be fine for you to use "weaver", "weaver-ii",
"weaver-mini", or whatever.

Note that this becomes important when building off of a framework (i.e. a
drop-in code library). You would either need to use the textdomain defined
in the framework, or else search-and-replace within the framework (which
defeats the purpose of using a drop-in code library in the first place).

Chip

On Thu, Sep 6, 2012 at 12:00 PM, Bruce Wampler <weavertheme at gmail.com>wrote:

> 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.
>
> I have an existing theme (Weaver II) and its slug 'weaver-ii'. It is a
> large theme, and has lots of support functions.
>
> 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.
>
> 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.
>
> Bruce Wampler
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120906/b0eefc1b/attachment.htm>