Anyone using trunk documentation, be aware I'm doing a big refactor in the process of splitting up the documentation. Which is as follows
drools-docs-generaluserguide
drools-docs-expert
drools-docs-flow
drools-docs-fusion
drools-docs-guvnor
drools-docs-solver

I'm struggling to what to call them, are they each "user guides". Drools Expert User Guide, Drools Flow User Guide. Or is it better to just hvae Drools Expert Docuementation, Drools Flow Documentation. Not sure. Also The User Guide is now just release notes, history/background info and general introduction, install guide. Its entitled Drools Introduction and General User Guide. That kinda sucks, anyone got a better name?

I was going to split out documentation into it's own docbook modules, but as we have a separation of expert, flow and fusion I think it might get too fragmented. So I'll move examples docs back into the last chapter of each book. With the general splitting up it should be more manageable now having examples in the main project manuals.

Mark
_______________________________________________
rules-dev mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/rules-dev

Reply via email to