This is an old revision of the document!
Contributing to documentation is an excellent way to support Evergreen, even if you are new to documentation. In fact, beginners often have a distinct advantage over the experts, more easily spotting the places where documentation is lacking or where it is unclear.
We welcome your contribution with planning, writing, editing, testing, translating to DocBook, and other tasks. Whatever your background or experience we are keen to have your help!
We are now looking for people to help produce the documentation. If you interested in participating, email the DIG facilitators at firstname.lastname@example.org or speak up on the documentation mailing list.
We're looking for volunteers to work on the following:
* Writing – Producing the documentation ("from scratch," and/or revised from existing materials). We're open to receiving content in any formats, such as Word or Open Office, but of course, we'd be delighted if you produced it in AsciiDoc!
* Testing – Comparing the documents with the functions they describe
* AsciiDoc conversion – For existing files that are not already in AsciiDoc, and new ones created by people writing in other formats
* Editorial review – Ensuring the documentation is clear and follows Evergreen DIG styleguide conventions
* CSS Design – Making the pages more attractive and user-ful
* XML Transform and Committers – Converting the files to HTML and PDF, making permanent changes, and uploading the files
Last Updated 4/27/2012
* We need people to review the draft 2.2 documentation available at http://docs.evergreen-ils.org/ and provide feedback on the discussion list or via the Launchpad bug reporting system. There are links to Launchpad throughout the documentation for this purpose.
* We need people to submit any documentation that may be out there on features new to version 2.2 to the documentation discussion list. Any format is okay.
* We need people willing to revise older documentation (1.6, 2.0, 2.1) to reflect any changes in 2.2 and write new documentation on features new to version 2.2. You may want to check the 2.2 outline and mention what you want to work on via the documentation discussion list to ensure you're not working on something someone else has already done, or in case there's the possibly of working with another volunteer on your topic.