Hi, Take care that you not solving a problem that we don’t really have yet. Premature optimisation and all that. Remember than many people who consume our content may not be maven experts and we want it to be simple for them to use. I’m all for DRY in code, but WET in test is better and easier to understand and that may also apply to the build files here and the audience we have.
Going down this path will likely add dependancies between releases with may cause delays in getting thing voted on and released which might also be a consideration. It is very likely for different presentation to use different resources so I’m not sure that having a common one even makes sense. For instance the CSS for my slide is different to the CSS to Chris's slides. (Although being CSS we could pull the common bits out and just override what you need.) The logos I used are also different to his (look at the footer). Thanks, Justin
