Forrest's greatest strength (and weakness) is that it sits on top of the stonking great XML generating/transforming/aggregating/serializiing engine called Cocoon. You can do *anything* with Cocoon. Want to suck in ten RSS feeds, merge them, transform them to SVG and output a PNG? No problem. However we are trying to solve real-world problems, and for this we need real use-cases. This is the page for them.
What does your project need from a doc system? What would your dream doc system be able to do? Please click the 'edit text' link below and let us know.
Wouldn't it be better if issues/feature requests get logged using the proper tools? Also, I have seen duplication of issues across the status.xml file and Jira. If we add yet another location, we'll never be able to properly follow up. -- StevenNoels
- Native Docbook support