The problem with using two different XML editors is sometimes that it results in some unwanted diffs in the commits... but it had to tried to know.
As of DocBook, it's simpler if we only has a single documentation tool. It's also nice if everything follows the same visual style, though not strictly necessary. For me at least, working with the DocBook and XXE is about as efficient as it can get, so, I had no much motivation to look for alternatives. Except, it's somewhat a barrier if someone else wants to edit docs semi-seriously (i.e., not just typo fixes, but still not enough to invest into DocBook and XXE or something like that). But I expect that to hardly ever come up in reality. Anyway, if you strongly prefer AsciiDoc/Markdown, and add the generator to the build, I won't be picky. Though if someone has a proper DocBook editor ready (and that used to be a big "if"), then I'm not sure why would you going with the less capable formats. Site update. Of course, you get a subdirectory, and we link it from the menu. No problem so far. But you have to generate that sub-directory with something. If it's not DocBook, then docgen can't do that. On Sun, Feb 16, 2020 at 9:23 PM Siegfried Goeschl < [email protected]> wrote: > Hi Daniel, > > You should see my workload :-) > > Don't worry about DocGen - I worked with DocBook before and have Oxygen > XML Editor ... > > Having said that > > * When the PR is merged I would like to update the FreeMarker site to > reflect the changes > * Not sure if I want to write documentation for "freemarker-generator" in > DocBook - would prefer AsciiDoc or Markdown > > Thanks in advance, > > Siegfried Goeschl > > > > On 16.02.2020, at 21:00, Daniel Dekany <[email protected]> wrote: > > > > Hi, > > > > It's great that freemarker-generator progresses. I'm not sure when will I > > find the time to check it out thoroughly (work pressure is quite high > > nowadays), but I will be on it. > > > > As of updating the FreeMarker website, and writing documentation(!), I > > recommend using docgen, because FreeMarker Manual and Site is done with > > that as well. I also recommend grabbing a free version of the XMLMind XML > > Editor, and follow the instructions in the freemarker-docgen project to > set > > it up. It has a steep learning curve (don't expect a usual word > processor, > > it's a tree editor), but after that, it saved me a tons of time and pain > > over the years. > > > > > > On Sun, Feb 16, 2020 at 8:49 PM Siegfried Goeschl < > > [email protected] <mailto:[email protected]>> wrote: > > > >> Hi folks, > >> > >> I mostly done with merging the "freemarker-cli" into > >> "freemarker-generator" project - if you have some spare cycles to waste > >> please have a look at > >> > >> * https://issues.apache.org/jira/browse/FREEMARKER-129 < > https://issues.apache.org/jira/browse/FREEMARKER-129> < > >> https://issues.apache.org/jira/browse/FREEMARKER-129 < > https://issues.apache.org/jira/browse/FREEMARKER-129>> > >> * https://github.com/apache/freemarker-generator/tree/FREEMARKER-129 < > https://github.com/apache/freemarker-generator/tree/FREEMARKER-129> < > >> https://github.com/apache/freemarker-generator/tree/FREEMARKER-129 < > https://github.com/apache/freemarker-generator/tree/FREEMARKER-129>> > >> * https://github.com/apache/freemarker-generator/pull/5 < > https://github.com/apache/freemarker-generator/pull/5> < > >> https://github.com/apache/freemarker-generator/pull/5> > >> > >> As usual it is a tiny PR touching 200+ file :-) > >> > >> The next challenges after cleanup & merge > >> > >> * Initial release - need to get that stuff into the official Maven repo > ... > >> * Update the FreeMarker web site > >> * Build a community :-) > >> > >> > >> Thanks in advance, > >> > >> Siegfried Goeschl > >> > >> > > > > -- > > Best regards, > > Daniel Dekany > > -- Best regards, Daniel Dekany
