I think one thing we should look at is breaking up the documentation to address different audiences' needs. There is stuff for system administrators, stuff for architects and developers, stuff for librarians, and stuff for end users all in one big pot. We should consider, post 1.6, whether we can sort all of that content into a set of smaller, more focused documents addressing each audience a little more distinctly.
We need all of the material, for a good documentation package. But we may do well to draw sharper boundaries around the different types of content. Aside from helping the different audiences to answer for themselves the question, "so what do I need to read?" this may also make it easier for us to see where a particular audience is underserved. -- Mark H. Wood, Lead System Programmer [email protected] Friends don't let friends publish revisable-form documents.
pgpGqCZbtn2B9.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
