RE: brainstorming about wyona

My thoughts exactly!

- These should be separate blocks: Cocoon (not to be included in Wyona, but
installed separately) - the CMS - the pubs

- You should not have to install all pubs together with Wyona/Lenya, but be
able to install/create as many separate pubs as you like. Probably, the pubs
should even be in a separate CVS repository. As an example, see the concept
of cents at the project centipede (http://krysalis.org/centipede/). Think
about creating "*.lar" files, "lenya archives", that could be dropped in a
specific context to become lenya publications.

- One possibility to make getting started easier and enhance reusability,
would be to have templates, e.g. templates for pubs, for page types, etc...
The templates should also be in a separate directory / repository from the
rest (the CMS and the pubs). These could be copied and/or enhanced to build
your own publication.

Again, I know that this is a lot of work without immediate return, but I
believe that these steps are necessary if you want other people to be able
to use wyona/lenya to create publications. So, one of the strategic points
to discuss next wednesday might be if you *really* want other
people/companies to use wyona/lenya :-)

BTW, is the name change definitive now? If you cannot go on using wyona,
lenya is cool.


memo


> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Michael Homeijer
> Sent: Wednesday, January 08, 2003 10:51
> To: '[email protected]'
> Subject: RE: [Wyonacms-dev] brainstorming about wyona
>
>
> Hi Gregor,
>
> >From what i've seen of the Demo applications built with Wyona, I am very
> impressed with it. The problem I have with Wyona is getting to
> know it, and
> right now I am trying for the third time. Although there's some
> documentation missing, I don't think it can be fixed with documentation
> alone.
>
> IMHO Wyona should first focus on the architecture of the CMS before
> continuing.
>
> Some things to consider:
> - Seperately develop document CMS components / if possible
> disconnected from
> Wyona / Cocoon. This would make it possible for developers to use and test
> the components in their setup. I some of my past projects I have been
> looking at Wyona to see if I could reuse some components, but
> every time the
> effort required looked to much.
>
> If you concentrate on well defined interfaces and implementation of
> standards it should not be too hard to have multiple exchangeble
> components
> depending on project requirements. For instance JAAS based authentication
> components, stores, revision controllers, publishing components, workflow
> etc.
> - Seperate the Wyona kernel from the user interface. This would
> minimize the
> part of Wyona that is dependent on a company specific publication.
> - Create an administration application that is configurable.
> Looking at the
> mailing list, much of the effort goes into keeping all
> publications in Sync
> with each other. Copy / paste between publications creates a maintenance
> nightmare.
> - Create an infrastructure that makes it easy to publish a
> company specific
> publication.
>
> Again, I am very impressed with Wyona. I hope you will be able to
> bring the
> development of it to the next level.
>
> HTH,
> Michael
>
> -----Original Message-----
> From: Gregor J. Rothfuss
> To: [email protected]; [email protected]
> Sent: 8-1-2003 9:53
> Subject: [Wyonacms-dev] brainstorming about wyona
>
> dear wyona community,
>
> the wyona team is doing a retreat next wednesday (jan 15th)
> to ponder the roadmap for wyona cms.
>
> to make it a productive day, we would very much like
> to consider your input. please, if you have some spare
> time, either file enhancement requests at
> http://cvs.wyona.org/bugs/ (preferred) or reply to this thread.
>
> looking forward to your input,
>
> -gregor
>
> --
> Gregor J. Rothfuss   [email protected]  +41 1 272 9161
> Software Architect   Wyona AG, Hardstrasse 219, CH-8005 Zurich
> Open Source CMS      http://www.wyona.org http://www.wyona.com
>
> _______________________________________________
> WyonaCMS-dev mailing list
> [email protected]
> http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev
>
> _______________________________________________
> WyonaCMS-dev mailing list
> [email protected]
> http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.435 / Virus Database: 244 - Release Date: 30.12.2002
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.441 / Virus Database: 247 - Release Date: 09.01.2003