1
Experience
* I have written documentation for several XOOPS modules, most recently for
Protector V3, and contributed to preparation of the XOOPS operations guide.
* Edit and produce a number of print and electronic publications, in addition to one medium sized XOOPS website.
Proposal
* A simple email newsletter should be developed and dispatched to community members at regular intervals, summarising the latest news, modules, themes etc with direct links to download new resources.
* I offer to put *new* XOOPS documentation written by the community into professional page layout for distribution of print-quality PDF files (subject to reasonable limits). Of course, distribution in other formats will be still be necessary.
* I recommend that the development of documentation be undertaken as an open process, that encourages occasional contributions from members of the wider community, rather than depending on a small group of people. I suggest the team should prepare a 'priority list' of documents that need to be written (based on community input) and then try to organise an open community effort in writing them!
* I would like to be upfront with everyone that my own contributions are occasional and not continuous.