|
I agree with eschwartz. Overriding templates via the resources mechanism is advanced usage, and you are on your own with maintaining those in the face of future changes to builtin resources. After all, the possible changes are not just changes to individual files. For instance, in the future I might decide to re-write the jacket mechanism completely and have it stop using templates in the resources folder at all.
Or a real example is that the currently in progress content server rewrite means that the resources used by the content server completely change. There is no simple mechanism to create a warning for such a complex change.
|