So rather than waiting further we decided to instrument the existing web interface — not a terribly elegant or reliable solution but it works for now.

The configuration file itself can be treated as an extension if it contains a setup() function.

The project also adheres closely to the Google Python Style Guide.

We use a combination of [JSHint](http://jshint.com) and [JSCS](http://jscs.info) for helping confirm code style conformance.

Please stick to strict, 80-column line limits except for small exceptions that would still be readable if they were truncated. Eliminate trailing whitespace wherever possible.

Copy your extension’s ID from the chrome://extensions page. Chrome generates this ID the first time you install the extension and will reuse it each time your rebuild or reinstall the extension

Add a node symlink. This is needed because the node binary from Ubuntu is called nodejs but many packages will try to run it as node:

Please consult the administration documentation for more information on accessing the admin dashboard.

Once installed, running nsqd in its default configuration should suffice for integration with h in a development environment

The h project uses ElasticSearch (v1.0 or later) as its principal data store for annotation data, and requires the ElasticSearch ICU Analysis plugin to be installed

Using the bookmarklet or otherwise embedding the application may not be possible on sites accessed via HTTPS due to browser policy restricting the inclusion of non-SSL content.

If you don’t have your h/node_modules/.bin directory on your PATH then you’ll get errors because the Node modules you’ve installed can’t be found (for example: Program file not found: uglifyjs). To add the Node modules to your PATH:

If you want to annotate a site that’s served over https then you’ll need to serve h over https as well, otherwise the browser will refuse to launch h and give a mixed-content warning.