Child templates and overrides
Child templates are the greatest example of overrides, and they are even more powerful than them. This is because many third-party templates include already overrides of some standard parts in the template’s /html folder, and these overrides may be modified by template updates. Overrides made in child templates, instead, are safe from template and system updates, as they are in a separate position and are not altered.
In a child template, you can make all the desired overrides with all the features that we discovered in Chapter 13, Customize Everything with Overrides. Also, in this case, we can create overrides for Modules, Components, Plugins, and Layouts.
When you create an override in a child template, the /html folder is created automatically in the child’s folder structure and, as usual, it contains all the overrides created for the child template, as in Figure 14.8.
Figure 14.8 – Child templates...
