3 commits

Author	SHA1	Message	Date
Prateek Saxena	8f1762a420	docs: Use the standard way of generating documentation ... * Move the files from the docs directory * Remove the generate script * Add npm task Change-Id: I2b404e132aab0be563c7abb9145ab607242c94cd	2016-03-11 16:13:50 +05:30
Kunal Mehta	21d47d362f	jsduck: Output to "docs/" like all other extensions ... Change-Id: Ia35bec1fff84f63a6bcd0ac42751d4b9190e9676	2016-02-14 22:55:30 -08:00
Timo Tijhof	8cf1956520	Update JSDuck config to standard jsduck.json ... Also * This way we don't need to pass the --config=jsduck.config.json parameter but can run plain 'jsduck' in Jenkins. Allowing it to use the standard job template. * Remove redundant wrapper. Pass directory in jsduck.json instead. And use warnings-exit-nonzero for exit code. Have to pass processes=0 due to https://github.com/senchalabs/jsduck/issues/525. Keeping a back-compat wrapper for now to allow easy migration from Jenkins. * Remove 'footer' override. * Use standard ' - Documentation' suffix, which makes the first part of the title render in bold. Change-Id: I6c9c7a1f29df0a72dc8cd0d37a83aaef23068062	2015-03-05 23:42:59 +01:00