[wp-trac] [WordPress Trac] #28509: Allow themes specifically meant to be parent themes to prevent activation

[WordPress Trac]

#28509: Allow themes specifically meant to be parent themes to prevent activation
-------------------------+------------------------------
 Reporter:  nathanrice   |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Themes       |     Version:  3.9.1
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by Otto42):

 Replying to [comment:26 F J Kaiser]:
 > Parent themes that are not intended to be used as stand alone themes are
 fact.

 But still "wrong", from a UX perspective.


 > If you still feel uncomfortable with the idea of parent/child themes not
 both being fully functional themes, try to see it like this: Sender &
 Receiver Themes. This is something we simply need when we want to start
 building "WebApps on the WordPress platform". One theme for setting up the
 App and defining routes and another one to have stylesheets and actual
 templates which return JSON (built by template tags).

 Or one "plugin" for creating an "App" and a theme to define how it looks.

 I'm not discounting the idea completely. Really. I'm just uncomfortable
 with defining a condition where a theme can be "not-a-theme". If we need a
 third category, then let's invent it.

 Themes should be about how the site looks, **and nothing else**. If we
 need extra ways to hook in, then let's define them appropriately, and
 create a better way.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/28509#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform