15:41 <guardian> hi

15:42 <guardian> which approach would you recommend: I want to use nanoc to build the documentation for different products. But those docs have to share content

15:42 <guardian> can data sources cope with this kind of setup?

17:40 <bobthecow> guardian: yes.

17:40 <bobthecow> so can git submodules.

18:47 <dkm> guardian: bobthecow: also consider git subtrees instead of submodules

18:47 <dkm> http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/

18:48 <dkm> guardian: I've gone even simpler (I think) and just use a separate git repo for each content source, then clone them somewhere in my nanoc site directory where various data sources are aware of them

18:50 <bobthecow> yep, subtrees work too.

18:50 <bobthecow> dkm: the reason i like submodules is that it's easy to get them to work with CI and deploy tools, since most of those automatically make 'em work.

18:55 <dkm> bobthecow: ah. I've only used them a little bit (subtrees too).

18:59 <guardian> basically, I have 1 nanoc site per product

18:59 <guardian> then I want common content shared between nanoc sites

19:00 <guardian> maybe a submodule for the shared content, could work