-
-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Communicate that Timber v2 is more than a templating system for WordPress #2334
Comments
Good idea @szepeviktor! I completely agree. The big sell for us at SiteCrafting was not just that you could use Twig (although that was a significant factor) - it was that you could write in a much more OO style that encouraged a more disciplined separation of concerns. In particular, it allowed us to get much closer to the MVC pattern. Of course WP still manages to find plenty of ways to break those abstractions 😛 so my only caveat would be against making absolute-sounding statements like, "Timber lets you write MVC code in WordPress." |
Absolute-sounding statements? But that's what marketing is all about! |
@jarednova you're right, that's literally the only thing that marketing is about. What I actually meant to say is that we should only EVER make absolute statements! |
there we go, that's the spirit!! |
I've added 2.0 and docs labels since I think this is something we really need to look into. A lot of hard went into the fine folks that worked on 2.x for so long, so a bit of marketing is deserved. |
Yes, I agree. But let this issue not be a blocker to release, let’s tackle this after the release. |
Currently we suggest that Timber can only be used for templating thus outputting (HTML) content.
It would be nice to list in what aspects Timber v2 is more than that.
The text was updated successfully, but these errors were encountered: