2018-03-02 7:44 GMT+01:00 Jan Matèrne (jhm) <apa...@materne.de>: > > > > > I made an attempt to convert the manual to HTML 5, the rationale > > > > being > > > > > that HTML 5 deprecates tt tag and recommends to replace it with > > > > > tags like code, kbd, samp and var, which could be used in a more > > > > consistent > > > > > way to achieve something closer to a semantic markup. > > > > > > > > > > I tried then to use the replacement tags as consistently as > > > > > possible in such a large body of text, but I realised that we > > > > > perhaps need a kind of a style guide. Would you like to discuss > > > > > it? Where would it best fit in the source code tree? > > > > > > > > > > > > > Isn't the HTML manual generated? Sure it's checked-in, but I > > thought > > > > there was a generation process. > > > > If that's the case (I may have dreamed it) then it's likely the > > > > generator that needs fixing, not the build product. --DD > > > > > > No. There were some experiments and maybe some pages were generated > > > during that experiment. > > > But the manual is a manual work. (double manual ;) > > > https://svn.apache.org/repos/asf/ant/sandbox/historical/xdocs/ > > > > > > > One may use xdoc and generate html with Doxia by calling its CLI. > > However, Ant sorely lacks a site generator on par with Maven site > > plugin. > > All generation requires a model to generate from. > AFAIK the site-plugin uses the pom for this purpose. > We don't have such a model in Ant. > Also I can't remember a wish for that. > Additionally I don't know any project (in my company) that uses these > sites. Maybe > they are useful for open source projects. >
site plugin gets a lot of configuration from pom.xml, but there's site.xml, too. Perhaps if a wrapper of Doxia sitetools with a distinct skin would be used if it were available? Gintas
