[wp-trac] [WordPress Trac] #33472: Templating Engine

[WordPress Trac]

#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 swissspidy):

 > 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.

 What would be some first steps to do this? Which limitations currently
 exist? Note that there are now more filters in the template hierarchy, and
 plenty of developers already use Twig or similar in their custom themes.

 Btw, I think with the REST API now in core, we're going to see more sites
 with a decoupled frontend and JavaScript-heavy themes. Even without the
 REST API, you can totally use WordPress for the backend and something
 completely different in the frontend.

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