| 52 | |
| 53 | == Why use includes instead of inheritance? == |
| 54 | |
| 55 | We think that includes are both simpler and more natural for templating. |
| 56 | |
| 57 | Template inheritance is a concept that fits well with template languages where a master template provide “slots” that are “filled” by the inheriting templates. However, Markup has no such feature, and instead uses the more powerful and flexible concept of [wiki:MarkupTemplates#py:match match templates]. |
| 58 | |
| 59 | Furthermore, XInclude is a W3C standard, which means that it is more likely to be supported in authoring tools than some esoteric custom notation for including external resources. |