[Fwd: First draft of "Producing LibreOffice User Guides"]

Earlier, I wrote,

The first draft of "Producing LibreOffice User Guides" is now in the
English Content > Community space on the Alfresco website for comment.

I now realise this document be better placed in the English Content >
Documentation > Resources space (where stimilar docs, and the chapter
template, are located), so I shall move it.

--Jean

Jean's Producing LibreOffice User Guides is a straight-forward
bootstrapping guide and well done. It doesn't go much in depth on the
usage of Alfresco specific tools or our workflow, and I suspect that
information will be included in the second volume to which Jean alluded.

To that second volume, I have re-uploaded LO_book_summary.ftl as a
report for use by documenters. With a few modifications it is now usable
again. I have also re-uploaded LO_master_summary.ftl which will require
some homogenization of our book sub-spaces as the code is not as
scalable. (LO_master_summary.ftl was the report which lent a full
project matrix-view like what we used on the wiki).

Questions: Should I homogenize our book sub-spaces? Should I set-up
our automated workflow again?

-- jdc

Earlier, I wrote,

The first draft of "Producing LibreOffice User Guides" is now in the
English Content > Community space on the Alfresco website for
comment.

I now realise this document be better placed in the English Content >
Documentation > Resources space (where stimilar docs, and the chapter
template, are located), so I shall move it.

Jean's Producing LibreOffice User Guides is a straight-forward
bootstrapping guide and well done. It doesn't go much in depth on the
usage of Alfresco specific tools or our workflow, and I suspect that
information will be included in the second volume to which Jean alluded.

Yes, I wanted us to have the workflow, access issues, etc fixed before writing about the use of Alfresco. Also, from memory your Alfresco boot camp document would fill that need quite nicely.

To that second volume, I have re-uploaded LO_book_summary.ftl as a
report for use by documenters. With a few modifications it is now usable
again. I have also re-uploaded LO_master_summary.ftl which will require
some homogenization of our book sub-spaces as the code is not as
scalable. (LO_master_summary.ftl was the report which lent a full
project matrix-view like what we used on the wiki).

Questions: Should I homogenize our book sub-spaces? Should I set-up
our automated workflow again?

I'm not sure what you mean by "homogenize". Make the structure of the book sub-spaces the same for each book? If so, I think that would be good to do (I had not yet found the time to do it). Most of the books do not need the "for rebranding" space, of course, and I was planning to remove them when no longer needed.

I think we very much need the automated workflow, and IMO the previous one met our needs and was working well, so yes please do set it up again. And thank you!

--Jean

Looks good.

Sorry about my lack of activity been pretty bogged down. Going to work on
things tonight though.

All spaces in Company Home/Documentation now have the same sub-space
structure. Drafts > Reviewed > Proofread > Published. A simple workflow
has been implemented where you can approve to progress the document to
the next step or reject to Drafts.

Docs which were in Rebranding are now in Drafts. Docs which were in
Salvaged have been moved to Company Home/Resources/<label> Salvaged.
The docs which were in the Next Version for the Writer Guide have been
moved to Company Home/Samples/Writer Guide Next Revision until we
decide a blanket layout for all books.

There were a few spaces which didn't seem to belong in Documentation, so
I moved them into the parent space. A general rule was if it ended in
Guide it stayed in Documentation.

-- jdc

Excellent! Thanks, Jeremy.

--Jean