Re: [Exist-development] eXist documentation rework

[Casey J. <cas...@jo...>]

Community,

As many of you know, our company provides a SaaS authoring and component
content management system built on eXist called easyDITA. DITA is a OASIS
XML standard for various types of technical documentation and publishing.

DITA adoption has been rapidly increasing in recent years because of the
standardization of the community as well as development of tools around the
standard to produce many types of documentation output from a single source.
(There are a lot of benefits of DITA, but I won't go into them here)

Our software is completely web based and handles many aspects of component
content management, collaboration, ticketing/workflow, and also has a fully
validating WYSIWYG editor for working with DITA. It also interoperates well
with oXygen, which has the ability to author DITA content as well.

These features may be very useful to the community because it allows
technical and non-technical alike to author robust XML based documentation,
re-use content, collaborate, manage document lifecycle and publish to
various formats/platforms. You can find out more about our product at
http://easydita.com

So that all being said, as a gesture of our appreciation to the eXist
community, we would be happy to offer a subscription of our SaaS free for
eXist documentation project. I can provide more details if the team is
interested.

Cheers,

Casey

On Wed, May 4, 2011 at 11:16 AM, Adam Retter <ad...@ex...> wrote:

> > 1. How is this issue of CSS and the "new design" related to the
> > project to revise documentation?  (I'm not saying there should be no
> > overlap - perhaps this makes perfect sense to do before the
> > documentation review begins.  I just haven't seen anyone explain why
> > it suddenly came up here in the thread about documentation.)
>
> Its not related. The documentation should be done first, it is
> completely distinct from the design.
>
> > 2. Is the discussion about documentation going on here in
> > exist-development or off-list?  I think it's best to keep important
> > matters discussed in the list, otherwise people will miss important
> > details.  In keeping with that, let me suggest that google docs are
> > sent out shouldn't be closed to a group but should be open to all,
> > with notifications about them here.
>
> Should be mostly here.
>
>
> I also found this very good example of how docbook can be used to
> produce well structured documentation -
>
> Explanation of their docbook construction and rules -
>
> http://anonsvn.jboss.org/repos/hibernate/core/trunk/documentation/manual/README
>
> Docbook build to produce, html one page, html seperate pages and pdf,
> in multiple languages -
>
> http://anonsvn.jboss.org/repos/hibernate/core/trunk/documentation/manual/pom.xml
>
> Actual docbook files -
>
> http://anonsvn.jboss.org/repos/hibernate/core/trunk/documentation/manual/src/main/docbook/en-US/
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
--
Casey Jordan
easyDITA a product of Jorsek LLC
"CaseyDJordan" on LinkedIn, Twitter & Facebook
Cell (585) 348 7399
Office (585) 239 6060
easydita.com


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.