Add infos for the new JS template system.

diff --git a/JavascriptCSSDependencies.wiki b/JavascriptCSSDependencies.wiki
index f08356f..814ad56 100644
--- a/JavascriptCSSDependencies.wiki
+++ b/JavascriptCSSDependencies.wiki

@@ -64,6 +64,18 @@
 This was formerly done using the {{{ melangeContext }}} attribute of the script tag. So now there is no need to convert the JSON object to a string for the attribute, but you can just put the plain JSON file inside the context parameter of this function calling.
 All the {{{ tc() }}} calls are *synchronous*. This means that it automatically evaluates itself as {{{ [null, tc(), null] }}}. The reason to do this is because there is no way for JS scripts to know about their context in the page (e.g. pass some parameters from the Django template to the JS scope), so we need a small hack to make them so and attach them a context. When a JS template is loaded, it will register itself in a global "template queue" hosted in the main _melange.js_ file, in the _melange.templates_ object. The context is then attached to the *last* template that has been registered. So we can't allow another template to be attached before the former one has been coupled with a context.
 
+The JS code for each Django template should be put under {{ app/soc/content/js/templates }} and then following the same path the Django template has. To receive the context in the JS code, then, your code should be inside the following function:
+
+{{{
+melange.templates.inherit(
+  function (_self, context) {
+    // Your code here
+    // _self contains a reference to this function
+    // context contains the context added in your tc() call
+  }
+);
+}}}
+
 === function() ===
 
 You can also attach a custom inline function, which is a sort of callback that is called after the previous scripts are loaded and evaluated in the browser. This is discouraged unless really necessary, though: all the logic should be put outside the Django template in the separate JS template file.
\ No newline at end of file