[wp-trac] [WordPress Trac] #24152: Use JSON as alternative to headers

WordPress Trac noreply at wordpress.org
Fri Mar 11 15:16:41 UTC 2016

#24152: Use JSON as alternative to headers
 Reporter:  ryanve           |       Owner:
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Themes           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  close            |     Focuses:

Comment (by schlessera):

 As an additional argument in favour of a separate metadata file (whatever
 the exact format):

 My themes all use a task runner (gulp) and have their stylesheet in an
 assets folder, in standard & minified form using content-hashed cache-
 busting in the file name (i.e. `assets/styles/mytheme-e5d74a3d.min.css`).

 Nevertheless, I need to keep an empty `style.css` stub file in the root
 folder, as this is the only way to identify my theme to WordPress. This is
 an arbitrary folder structure lock-in that goes against many best
 practices found on other platforms.

 Although I would heartily welcome a JSON file (even reusing
 `composer.json` would be fine, as it is pretty much a de-facto standard in
 the PHP world), any format would be fine as long as the "package"
 (plugin/theme/whatever else comes up) metadata is found in a separate
 metadata file.

Ticket URL: <https://core.trac.wordpress.org/ticket/24152#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list