[wp-trac] [WordPress Trac] #63007: Bundled themes: Stylesheets for block themes are missing path data for inlining

[WordPress Trac]

#63007: Bundled themes: Stylesheets for block themes are missing path data for
inlining
-----------------------------------+-------------------------------
 Reporter:  westonruter            |       Owner:  westonruter
     Type:  enhancement            |      Status:  accepted
 Priority:  normal                 |   Milestone:  6.9
Component:  Bundled Theme          |     Version:
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch 2nd-opinion  |     Focuses:  css, performance
-----------------------------------+-------------------------------

Comment (by westonruter):

 Replying to [comment:24 poena]:
 > There are pros and cons for both using the core tool and for placing it
 in the theme.
 > Using the tool that is already in core means that we, those
 participating in the discussion, needs to do very little, and long term,
 it is less to maintain.
 > Adding the tools to the themes means there are more files to manage and
 keep up to date. And I may be wrong but doing this usually falls on one or
 two people for every release.
 > The pros are that a beginner developer can keep using the themes as
 examples, and all they need is the built, distributed theme. They don't
 have to concern themselves with a development version of WordPress.

 For the sake of both the core build process and for the sake of developers
 who fork the themes, how about the minification process be available in
 both? Granted, this is more relevant to #63012 which is specifically about
 minification for all themes. As seen in my [https://github.com/WordPress
 /wordpress-develop/pull/8396 PR], adding minification for bundled themes
 is trivial for using core's existing tooling since it's just a matter of
 adding paths to `Gruntfile.js`.

 But for the sake of developers who fork a theme who do not have core's
 build tooling available, each theme could also have a `package.json` that
 also provides the same minification tooling. This would indeed be more to
 maintain, but it would address the concern of providing devs with the
 ability to keep the minified files updated after edits to the CSS source
 files. Nevertheless, as part of the release it could be core's tooling
 that is used for minification, so the tooling bundled with each theme
 wouldn't need to be maintained in order to actually perform a release.

 > But what if its not the only option?
 > Removing the style.css meta data still has not been looked at.

 Being able to eliminate the CSS files entirely sounds great, although that
 would just eliminate the need for this ticket and not the overall need to
 minify CSS for all themes (#63012).

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