Views
Mifos documentation should be...
Well-written
Strive for proper grammar and punctuation. Care about your readers and inspire them to do the same.
Lightweight
Don't use a Word document when you don't need to. Use standard, widely accepted formats like plain text and HTML whenever possible. Open, lightweight formats can more easily be edited, indexed, compressed, tracked, and shared by everyone for many years to come.
Evolving
Start small. Work-in-progress/draft documents belong on mifos.org! As you read through documentation, feel free to refactor it so it makes more sense.
Version-tracked
All content added to mifos.org is automatically version-tracked. This greatly eases collaboration and provides an indispensable historical reference. Documents committed to a subversion repository are also version-tracked. Use change notes and commit log messages to explain your changes.
Targeted
Think about who your audience is and write to them. Imagine yourself teaching and speaking to others face to face.
Used
Follow the rest of the goals and this should take care of itself. Conversely, stagnant and inaccurate documentation should be removed and/or replaced.
In Plain Sight
By now you'll have noticed the hints in other goals to work on content "in the open" or "in plain sight". This is the case if documents are created and developed on mifos.org. Leverage the transparency of Free/Libre/Open Source Software development to ensure your document meets all the goals on this page.