[theme-reviewers] Removing core features

[Chip Bennett]

Bryan,

One easy, defining question in this case: would the user want that
configuration to persist, regardless of active Theme, or would the user
reasonably expect that configuration to change based on active Theme? In
this case, it is quite clear that if a user wants to hide the WordPress
version generator, that desire is entirely irrelevant to the active Theme.
Messing with rel links and what-not are SEO matters.

And removing wp_print_styles? Really? I can imagine a few front-end Plugins
that would be rather inconvenienced by that one.


On Wed, May 22, 2013 at 8:34 AM, Bryan Hadaway <bhadaway at gmail.com> wrote:

> *@Abhik*
>
> Well, even if it's "not okay" in general, if there's an interesting,
> relevant and useful reason for a theme to go against
> requirements/recommendations than an exception *can* be made in special
> cases (not in this case though it looks like).
>
> *@Chip*
>
> It's a shame, cause I actually think it would perfect for boilerplates.
> But, I can see how it might be too drastic of a change for someone
> switching from another theme that might cause alarm, though I'd think it
> would be well documented in the theme. Though, looking at the theme in the
> ticket they don't appear to explain or have a strong reason for this
> anyways.
>
> I might consider making this into a plugin myself and call it something
> like "Clean House". Is that a comprehensive list of things that can be
> unhooked?
>
> _______________________________________________
> 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/20130522/614773a9/attachment.html>