homotechsual · ffa68553 · ffa68553
--- a/docs/framework/templates/customizing.md
+++ b/docs/framework/templates/customizing.md
+# Customizing Built-in Screens
+
+!!! caution "Use extensions instead"
+
+   The methods on this page are of historical interest and may be helpful in understanding legacy code, but overriding templates and php files is strongly discouraged for any new customisations. These approaches need attention whenever you upgrade and will cause a range of problems from subtle to major if you forget about them.
+   
+   As CiviCRM evolves, the recommended ways of customizing it change.   The current preferred method is to Create an Extension to implement Hooks and use the API.  If you can't find a way to use existing hooks to accomplish what you want, discuss it on StackExchange or Chat.  It may be appropriate to add a new hook to core.
+   
+   (It is possible to override templates and php in an extension, but you face the same problems when it comes to upgrading - don't do it!)
--- a/docs/framework/templates/index.md
+++ b/docs/framework/templates/index.md
+patch if you need to use a template that isn't yet complying. For more
+information about submitting a bug or issue, read about the CiviCRM
+community.
+
+## Displaying more content and adding Ajax features
+
+If your modifications go further than "simple" modifications of the
+layout, but need to display more content than the one assigned to the
+template by default, or to add Ajax functionality, use the CiviCRM API.
+Please read more information about using the CiviCRM API from Ajax to
+pursue this approach.
+
+In most cases, using the CiviCRM APIs should be simple and only takes a
+few extra lines of modifications.
+
+## Appending jQuery or other code to a template