I've been looking at Nuxeo as a basis for an upcoming project and have
been quite impressed by its design and its goals, and especially the
quality of the documentation. However the docs and HOWTOs I've found
seem to be on each of two extremes: end user "how to use Nuxeo's webapp"
and developer "how the Nuxeo core is implemented".
I'm having a hard time finding guidance for the "in between": how an
"end user" integrator is expected to adapt it to specific requirements.
My project would need to present a customized interface which
incorporates my customer's corporate logo and accepted styles (i.e.
imagine a "MyCustomerDocs powered by Nuxeo" branding rather than
straight "Nuxeo").
Ideally, there's a demo project that shows how to do some or all of the
following. We hoped to be able to take a prebuilt, stable release of
Nuxeo and then add configuration to create such a customized application:
* replace the nuxeo theme with something else - changing colors,
adding a custom logo, etc.
* integrate with a single signon systems (siteminder, corporate ldap,
etc.)
* configure the various underlying components (e.g. underlying the
jackrabbit / lucene repository configuration, how to configure
repository meta data variables, etc.)
* add additional workflow / drools rules
I've poked around the subversion repository and see some undocumented
modules (e.g. NxSample), but it's not clear to me how (I'm still having
problems getting the trunk sources to test cleanly on my development
machine, so am hoping to take a step back and attempt building a small
sample app against the stable binary release -- is that possible?
Sorry if this is explained somewhere in the docs -- if so, just point me
at them!
Thanks,
Steve
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
