The HTML5 exporter in Construct 2 includes Google's V8 Javascript engine. This means both the editor and runtime parts of plugins can be written in javascript. This makes it much, much easier to extend Construct - previously you had to have relatively good knowledge of C++, which is a difficult language to learn, as well as Microsoft Visual C++ (the full version of which is expensive, and the express versions are difficult to set up for the SDK). Now you can do it on any computer in any text editor (even Notepad). I use Notepad++ myself, which is basically an advanced Notepad, and has syntax highlighting for javascript.
Custom javascript plugins are a good substitute for Python scripts for advanced users, too. You can easily put together some custom functionality for your own project once you're familiar with the SDK.
Plugins also only need to be written once for both the 32-bit and 64-bit versions of Construct - the V8 engine handles the differences itself.
Location of plugins
Plugins are stored under <install path>\exporters\html5\plugins. Each plugin has its own folder, with four files:
edittime.js - defines everything the editor needs to know about the plugin.
runtime.js - defines the plugin methods that run in the browser.
common.js - prepended to both edittime.js and runtime.js, in case there's any code that is in common to both files. No plugins currently use this, it was added in anticipation of code duplication.
PluginIcon.ico - icon file loaded by the editor to represent the plugin.
To make a plugin, simply copy and paste another plugin's folder and start editing the files. (There's no template yet - sorry!)
Documentation
There is no SDK documentation right now, mainly because there's just no time to get it all written down. Also, the SDK is subject to change at any time! If you write a plugin now, be prepared to have to change it to fix it after some releases. This is due to the nature of pre-alpha software: it will change a lot, and it will break things.
The best way to learn about the Javascript SDK is to read the source code to the other plugins. There are a couple of other javascript source files that are prepended to the plugin sources that will help you learn about the features available. These are under <install path>\exporters\html5, and are:
common_prelude.js - prepended to both edittime scripts and runtime scripts.
edittime_prelude.js - prepended only to edittime scripts.
preview_prelude.js - prepended only to runtime scripts.
The rest of the scripts in that folder are for the browser runtime. You can have a look through them if you want your plugin to hack around with the engine. Due to the nature of Javascript your plugin can modify any part of the runtime at any time. However, it is undocumented as to which parts will definitely break if you change them, and which parts can safely be modified. If you're not sure, make a forum post asking.
Minification
It is not necessary to minify/obfuscate your scripts. Construct 2 gives the option to minify script on export.
Hope that helps get you started! Just be warned, the SDK may change at any time as functionality is added and changed.