![](https://secure.gravatar.com/avatar/cedc4d83943006afe3994fb0a0455f82.jpg?s=120&d=mm&r=g)
Hello, These suggestions are a bit a reply to the thoughts of James Fisher. It would be nice, to have once in the future at least 2 up to date context documentations: - a context user manual For me, it's the merge of all scattered articles and manuals. Each chapter treats a particular subject, such as "columns" or "footnotes". It seems, that Taco is working on such a manual. - a context command reference manual This is just the xml-database used by texshow. Each command should be described in detail with every possible options. On the one hand, texshow uses this database, on the other hand a well structured command reference can be generated as pdf-file. Filling in all the details in both projects is a lot of work, so perhaps it would be a good idea, to set up a system, that makes it easy for users to contribute to these projects (patches) and easy for Taco and Hans to acknowledge or reject those patches. This "system" would be nothing else as some vcs (git or svn for example) with some commit-hooks, that manage the acknowledgement by Hans and Taco (and perhaps others). The tex-files of the user-manual are already under version control, and the xml-database is only the cont-en.xml file, that would need to be put under version control too. So, perhaps with not too much effort, users can be easily invited to contribute to the documentation projects and the quality can be assured through the acknowledgements of the developers. Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/