On Sat, Aug 13, 2011 at 11:32 AM, Jean Hollis Weber <firstname.lastname@example.org> wrote:
English Content > Documentation > Developers Guide seems like the best
place for it. It also could fit under HowTos/Tutorials, but as it's
aimed more at (extension) developers than end users, the DevGuide area
seemed more relevant.
Tom has put it on the wiki, but as it needs work, I thought adding it to
Alfresco would be good. I am writing a note to the list seeking someone
to tidy up the English and make any other needed changes.
I just downloaded and had a brief look at the two files.
Installing_extensions_08-11-2011.odt would seem like content to
replace the extensions coverage in 0109GS3-SettingUpAndCustomizing.odt
of the GS guide
Publishing_extensions_08112011.odt would indeed seem to fit in the
DevGuide area, but I suspect it's still a work in progress, because
I'm not sure that http://extensions-test.libreoffice.org/ is yet at a
mature state, and I don't know if Andreas and Gustavo will maintain
the material we keep on Alfresco.
I can put Publishing_extensions_08112011.odt on my list of
longer-range to-do's, after the Power User guide, for proofreading and
correction, once the work on Alfresco is much more advanced.
@Gustavo, @Andreas: any comments?
Unsubscribe instructions: E-mail to email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/documentation/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy