Chip Bennett has done a great job of corralling all the feedback so far but needs more community input on the theme names that are allowed in the WordPress repo.
Many of you already know the existing guidelines:
- Themes are not to use WordPress in their name. For example My WordPress Theme, WordPress AwesomeSauce, and AwesomeSauce for WordPress would not be accepted. After all, this is the WordPress Theme repository.
- Themes are not to use the term Theme in their name, such as: AwesomeSauce Theme. Same reason as above … it’s aTheme repository.
- Themes may use the WP acronym in the Theme name, such as WP AwesomeSauce.
- Themes are not to use version-specific, markup-related terms (e.g. HTML5, CSS3, etc.) in their name.
- Themes are not to use related terms (e.g. Blog, Web Log, Template, Skin, etc.) in their name.
- Themes are not to use Theme author/developer credit text in their name. For example AwesomeSauce by John Q. Developer(makes for a much better credit link); or, SEO/SPAM-seeded text, such as: AwesomeSauce by Awesome Free WP Themes (this is just not going to pass).
- Themes are not to use related Theme names (e.g. WP Twenty Eleven, Twenty Eleven WP, The Twenty Eleven, etc.) in their name.
It’s worth noting that these are required for all new themes and greatly encouraged for existing themes that may have been submitted prior to expressed guidelines – they have been naturally grandfathered in but are encouraged to come around with an update.
What Chip is looking for is further feedback on the existing guidelines and the conversations that have been swirling around thus far.
Things that cover the use of WordPress in the name, generic terms (like HTML5, CSS3) or even related terms (like Blog, Template, Skin), the use of the developer’s name or creator’s name, etc.
Join the conversation and put in your thoughts if you’ve got them. Have you ever been rejected from submission to the WordPress repo or had issues with your naming conventions?
Start the conversation