In an effort to plan and start writing all the new end-user
documentation we need for Preview we want to firm up all the pieces
we need so we can get those logged in bugzilla and assigned to owners
of the content. This really focuses on the "how-to" information for
people who are getting started with our products. A while back Mimi
sent out a list for feedback which I will summarize below. It is
assumed that this information will be part of the new
chandlerproject.org landing pages. Once we have compiled a list of
all the stuff we need, we will work on hierarchy (that is not part of
this discussion).
The documentation fits into 3 categories. To make this easier to
read, I have split this up into Journal pages....
+ End-user how-to stuff and screen casts
+ http://wiki.osafoundation.org/Journal/PreviewEndUserDocs20070326
+ Chandler Hub end-user docs
+ http://wiki.osafoundation.org/Journal/ChandlerHubEndUserDocs20070326
+ Information we would like to put in the FAQs (keep in mind we can
always add to the FAQs on an ongoing basis)
+ http://wiki.osafoundation.org/Journal/PreviewFAQ20070326
This does NOT include the current stuff on our wiki re: the projects,
planning, vision, how to help etc and all the various links we will
have off the pages. We will be reviewing all of that separately and
determine what of our existing documentation we can use and what is
missing. People will have a chance to iterate on this once we send
out the proposed site hierarchy. It also does NOT include code-
dependent deliverables like the "welcome note" which we are tracking
separately.
PLEASE RESPOND BY THE END OF THE DAY ON TUES WITH COMMENTS OR ADDITIONS.
Thanks,
Sheila
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
