Maybe we can learn something from Daisy (please see below)
Thanks
Michi
-------- Original Message --------
Subject: [daisy] great job on daisy
Date: Fri, 15 Sep 2006 07:22:48 +0200
From: Philippe LAPLANCHE <[EMAIL PROTECTED]>
Reply-To: Daisy: open source CMS - general mailinglist
<[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Hi
I'm a new user and I'm very impressed with Daisy.
My goal is to have a corporate web site that any employee of a company
can customize easily and to have that web site published as static html
pages to an Apache Server.
Daisy made it happen in a few hours only (I used also a small shell
script using wget and lftp to publish to the live site). Daisy looks
very stable. After using Lenya, that was a huge relief. The
documentation is clear and I almost had no problem. Daisy is user
friendly, very powerful, well thought and very promising.
After using Cocoon and Lenya for a year, it was really easy for me to
build a custom skin. xslt templates are easy to write.
Thanks a lot to all Daisy contributors.
For me it would just have been a more straightforward and I would have
understood things faster if the installation process defined two sites
(with same content) much like the "Edit Site" and "Live Site" of Apache
Lenya. The live site would have a custom skin that doesn't show the wiki
stuff (top menu) but still show the navigation tree.
You could also have added a few sample documents organized in a tree
just to learn faster the use of the navigation document type.
I think a lot of people at first want to know how to transform a wiki
site into a normal site and that "Live site" would show them... I
wondered for a long time if I was using the right solution until I read
the Publishing:roadmap document, and that I read that the "publish-only
library" is still under development.
Learning with examples is the fastest.
Also I started using Lenya instead of Daisy because I thought Daisy was
just a wiki site dezigner and not a CMS (stupid me).
Besides that I am also asking you for some help about small details
because I don't know the best way to start.
- As a cocoon user I've always added a simple xslt:transform at the end
of my html rendering pipelines, before the serialization. The stylesheet
would get rid of namespaces definitions. Where should I put this
xslt:transform ? I'm afraid I'd break everything :-)
- Can I use the html serializer with STRICT DTD without any risk? If
not, how could I use it only in my "live" site?
- I18n: I will need the missing French translations of some labels of
the editor... I can do it if someone points me in the right directions
I also wish this for the future:
- A spell checker in the editor
- The ability, in the editor, to add custom xml tags in the page (in
custom namespace). These tags would get transformed later into html/fo
using custom templates in the skin. This would give more liberty in
style customization than just using css styles (am I wrong?)
Thank you again
Best Regards,
Philippe Laplanche
_______________________________________________
daisy community mailing list
Professional Daisy support:
http://outerthought.org/site/services/daisy/daisysupport.html
mail to: [EMAIL PROTECTED]
list information: http://lists.cocoondev.org/mailman/listinfo/daisy
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
