1. Ahmad Awais

    Timber is a great plugin. Huge props to Jared and the team. Been using it for several projects, as a matter of fact I wrote a series of Tutorials about Kick-Starting development with Twig with Timber at Tuts+ (Link: http://ahmda.ws/1VXPdFc )


  2. Mark Root-Wiley

    No judgement of the plugin itself, but I’m a little surprised this made it into the repo given the recent “no frameworks” post: https://make.wordpress.org/plugins/2016/03/01/please-do-not-submit-frameworks/


    • sarah

      Perhaps it was among the many exceptions to this rule that were “grandfathered in” when they started enforcing it. ¯\_(ツ)_/¯


    • Otto

      Timber has been in the repository for almost 3 years now. This isn’t a “new” plugin by any means, this is just about it reaching a “1.0” release number.


      • Mark

        Aha. Misunderstood that. Thanks for clarifying. The plugin team rocks.


        • Samuel "Otto" Wood

          What we “allow” in the repository is an ever evolving thing. It changes frequently, as needed, based on problem points and things we see on a daily basis. For example, whenever a new widget on social-media-service-x comes out, we immediately get deluged with dozens of plugins to implement said feature. After the first few, we start asking authors “how is this different than this other one?” People get surprisingly pissed off at that question. ;)

          The point is that having a dozen plugins all identical isn’t good for the directory or the users. So what we allow or disallow is subject to constant change. It’s never personal. But it always feels personal. That’s a bummer that I see no way to fix.


    • fwolf

      Actually, Timber is not a framework, its a template engine.
      What you do with it is up to you though :)

      cu, w0lf.


  3. Das

    Maybe it is a god alternative for people with decent JS and low PHP knowledge, but imo, the WordPress way of teeming with PHP is a great opportunity.
    Using twig and this plugin is like making “love” with second extra condom ;)


  4. Paul

    I’ve always disagreed with Timber’s unofficial motto. The Loop is one of WordPress’ most powerful features, you just have to know how to weild it.


  5. Zulfikar

    OK jokes aside. Never understood anything that is alternative to the native “loop” – why replace one of the power points of WordPress?


  6. Jared Novack

    @Paul @Zulfikar: my issue with the loop is that the output of code can change based on the context it occurs in. My comfort zone is that a function should always return the same value when sent the same arguments. In the context of `the_loop` this isn’t always the case.

    I realize this is a feature, not a bug. Event-based architecture and so on and so on…

    Ditching the loop isn’t for everyone, and I realize I’m substituting one opinion for another. It’s definitely not the right approach for someone who’s trying to integrate with the wider WP ecosystem: your woos, your eventcalendarpros, your yoasts. My strong belief is that this opinion (MVC-like and a separation of PHP from HTML) makes more sense when growing a theme over time and sharing responsibilities between diff’t types of developers. Oh and not having <?php and ?> tags everywhere


  7. Peter Shackelford

    The strongest benefit I have gained from using twig is it’s template inheritance model. It has made it easier to modularize my template files. Twig embed takes a little while to wrap your head around, but once you do, it is powerful. http://twig.sensiolabs.org/doc/tags/embed.html

    My team works with both WordPress and Drupal. Because Drupal is adopting twig and our product applications use django, using twig creates more opportunity for both cross training and shared understanding.

    I have been keeping tabs on what the Craft CMS community is doing as they have been active in helping their community take advantage of twig.


Comments are closed.

%d bloggers like this: