Am Freitag, 13. Juni 2008 15:17 schrieb Andreas Hartmann:
> […]

> Wolfgang Jeltsch schrieb:
> […]

> > Where’s the source tree if I created my publication using the web
> > interface? Is there any at all?
>
> no, there is no source tree. The "Create publication" web interface is
> not intended for development, rather to create new publication instances
> in a production environment.

So what do I “develop” then?  I thought, I develop a publication.  Do I 
develop a “publication template” or whatever which can be instantiated 
several times?

I have to say that it’s really difficult to get all this information because 
the Lenya documentation is really lacking at this point.  You have some 
tutorials with step-by-step instructions, some isolated descriptions of 
concepts and some in-depth descriptions of very specialized things but you 
don’t have any documentation which gives you an introduction to the whole 
picture and the relationships between the different things.  This makes it 
really hard to start using Lenya and it might frighten off many potential 
users.  If I wouldn’t have been impressed by the pro-standards and 
pro-flexibility approach of Lenya that much, I’d probably have switched to 
some other CMS and in fact, I almost had used OpenCms instead of Lenya.

> […]

> > What about the documents of my publication? Will they be lost during
> > redeployment? 
>
> I'd recommend not having any content in the source tree to avoid the
> risk of overriding productive documents.

Why does Lenya mix content and “source” by default then?  (I think, you 
meant “build”, not “source” by the way.)

> […]

So I want to build a simple website first.  Basically, I want a publication 
similar to the default publication but with less features (e.g., resource 
types).  Later I’ll probably want more advanced things and therefore use 
additional features.  How should I start?

> -- Andreas

Best wishes,
Wolfgang

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to