| We're concerned about the upgrade path, but so far we've upgraded from 3.1 to current without any issues. MTV can break a lot of plugins that filter front-end output. But it depends on how you use it. It doesn't have to. We like having function exports be hard-coded. Making all functions available to the templating engine is unnecessary. It's pretty trivial to declare new functions to use in the templates, and it doesn't have to be done in the MTV plugin, you can declare those in your theme or plugin. We are always involved with our end users and we design the templates. Our users can't install plugins or themes and we typically lock down lots of settings. So we don't mind if we break template tags because we have complete control over how our sites are used. MTV has it's own template structure and supports all sorts of template inheritance. That all comes from Twig. It also supports child theme inheritance, if you're using MTV to build your themes all of your themes. We've tried to get around the future-update-breaking-shit issue by making the core of MTV sit on top of WordPress. It's totally possible to build an app with MTV and no WordPress. Again - MTV works for us, but won't work for everyone. And it's really only useful if you're gonna build a site from scratch. |