GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
We should add somewhere in the docs the template best practices for reusability/extensibility. For instance, when providing a template with many blocks, it is better to create an empty template that just extends the real template to allow the developer to override the empty template in its own app.
I still don't agree this should be the solution. It's almost saying like you can only properly extend a template from an existing bundle if the creator wants you to, and made preparations for that. Creating 2 template files for each lay-out seems very redundant.
All in all I still think there should be a way to target the "overwritten" template.
@weaverryan this should get labelled with 'Acitonable'
We do have a section in the templating chapter called "Three-level Inheritance", which talks about this approach. I'm not sure if we should add more - in then early examples of showing templating inheritance, I don't think we should burden the explanation with extra layers. We do mention in this section that this approach is a best-practice in vendor bundles.