[wp-trac] [WordPress Trac] #33472: Templating Engine
WordPress Trac
noreply at wordpress.org
Thu Apr 21 06:50:22 UTC 2016
#33472: Templating Engine
-----------------------------+---------------------------------------
Reporter: KalenJohnson | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Themes | Version: 4.4
Severity: normal | Resolution:
Keywords: ongoing | Focuses: administration, template
-----------------------------+---------------------------------------
Comment (by schlessera):
I think that ''any'' templating engine would probably provide many
benefits compared to the raw PHP approach we have now, if only to push
developers into using a more structured approach, properly separating the
concerns.
However, I would much prefer not focusing this discussion on "What
templating engine should we use?", but rather on "How should we extend
WordPress so that we can smoothly drop in different templating engines?".
This is a much more future-proof approach, and whatever the current trendy
engine of choice is will not limit us in a few years.
So, how would we go about molding the current filters and data structures
into something of a "Templating API" that can use different
implementations depending on a site's needs? This "Templating API" could
still provide a backwards-compatible standard implementation shipped with
WordPress, and it would make it trivial to build additional, reusable
templating engines that can be installed/used when required.
I know that WordPress advocates the "decisions, not options" approach. I
think this is a good approach for end-users, but the changes we are
talking about here are targeted at developers. Developers drive
innovation, and it should be in WP's best interest to not unnecessarily
block that innovation with arbitrary choices.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/33472#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list