[wp-trac] [WordPress Trac] #35395: Provide a better gateway for code-based theme customizations with the Customizer
WordPress Trac
noreply at wordpress.org
Wed Oct 19 19:58:55 UTC 2016
#35395: Provide a better gateway for code-based theme customizations with the
Customizer
-----------------------------------------+-------------------------
Reporter: celloexpressions | Owner: johnregan3
Type: feature request | Status: closed
Priority: normal | Milestone: 4.7
Component: Customize | Version:
Severity: normal | Resolution: fixed
Keywords: has-screenshots needs-patch | Focuses:
-----------------------------------------+-------------------------
Comment (by pingram3541):
Another thought that just occurred to me is better built in enqueueing of
theme styles and scripts based on file structure, similar to the existing
wp model for pages, posts partials/templates where the file structure and
naming conventions define how wp loads css and js files.
How cool would it be for me to drop in a css file
/mytheme/css/page_home_20.css and WP to automatically load that file only
on the page with a slug of "home" with a priority of 20. Obviously I
haven't thought much deeper on this and there may be a good reason for not
doing this but in the case of saving files from the customizer as it
pertains to css, this could be the good ol logic needed to remove needing
to hook into the db for css. Think of the awesomeness we could with the
live editor in that we can employ a view for diffs not only against the
recently proposed "changesets", i.e. customizer textarea history but also
with actual files residing in the theme folder simply based on naming
structure.
Heck at base value, I'd love the idea of being able to simply create and
properly name a css file in my theme and never worry about touching
functions.php for this!
--
Ticket URL: <https://core.trac.wordpress.org/ticket/35395#comment:72>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list