@Clément Bénier: writing the setup script is one thing. But for the generation to work correctly, you may have to tweak the code related to config files sourcing/aggregation. I mean: the config files sourced by node.js scripts (docs-tools/conf/AppDefault.js + docs-webtemplate/conf/AppDefault.js). Note that it's just a warning and the existing code may be right and well written
The final judge is to generate the current doc site with the 2 methods (old one with docs-agl, new one with your script) and observe the diff. No diff = good to go !
New AGL docs website is now split into several repositories :
https://github.com/automotive-grade-linux/docs-webtemplate
https://github.com/automotive-grade-linux/docs-sources
https://github.com/automotive-grade-linux/docs-tools
A script or a makefile must allow to easily setup and generate AGL doc website.
Needs:
script / makefile must be part of docs-webtemplate repo (root repo to clone to generate AGL docs)
support multi branches (based on a config file that differs from a branch to another) in order to allow generation of master or master-next docs
clone docs-tools repo in the right location
install requested dependencies when need
check if node_modules dir exists under docs-tools, if not run "npm install"
check if jekyll and other requested tools are install, if not rise an error with the right command line to execute (eg. sudo zypper install ruby ... )
fetch docs-sources documentation part as any other external docs repo (IOW add docs-sources in yaml fetch file)