Hi Lenya devs,
there seems to be a consensus that it would be a good idea to ship the
docu publication as an example instead of the default publication.
This raises the question how the content should be handled. A
fundamental issue is that each installation would contain a fork of the
website content. Do you consider this a problem? Could it cause confusion?
There are several options:
a) Use a separate SVN repository for the content which is shared by the
project website and the application (e.g., via svn:externals). This
would require to commit our website content (potentially cumbersome,
might be automated).
b) Don't include the full documentation content, but only a couple of
pages which aren't likely to change often, and try to keep these pages
up to date.
c) Use the content of the current default publication, i.e. share only
the layout.
d) Don't include any meaningful content at all, only some "Hello World"
pages. This would require only a minimum of maintenance.
e) …
WDYT?
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
