So what you may have noticed with many of the other templating engine integrations, they are much more than just allowing new templates. Timber for instance comes as almost a framework, with controllers and a new router.
The thinking process for integrating Blade into Sage was really to make it as light and drop-in as possible. We made sure to have the template hierarchy work the same, and we’ve squashed some bugs related to third party plugin templates.
We haven’t even really included many Blade directives. I’ve seen directives for WP_Query as well as ACF, and those can be helpful, but again not something that necessarily needs to be in a starter theme.
It should be relatively simple, but open ended to add in a controller like system. My thought was it could be similar to controller’s in other frameworks, however instead of returning a view with data passed to it, you can just filter the view data: https://github.com/roots/sage/blob/6ca3b3faa7e3ec29d01016fdc7bd656ff0e8a64e/src/filters.php#L50
With all that in mind, we will be writing a blog post pretty soon to cover Blade, let us know what you’d like to know about it.