Hello all,<br><br><div class="gmail_quote">On Dec 11, 2007 2:51 PM, David Bain <<a href="mailto:david.bain@alteroo.com">david.bain@alteroo.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think there is space in the market for a simple CMS (i.e. no workflow etc...) I fully agree with having a migration path. Sure construction kit would be nice, but a single CMS that people can share efforts at polishing would be useful. I think the biggest win would be to ensure that it is:
</blockquote><div>+1,<br>I am also interested to have a simple CMS for managing general content.<br>I hope to join the project as soon as time permits. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>1. Easily themable/skinnable<br>2. Skins are portable to Plone</blockquote><div><br>If it was doable with Deliverance, we may have less to reinvent, and it would be ready for the future ?<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>3. Data is easy to port to Plone portal types<br></blockquote><div><br>Could be possible if the content types technology itself is shared between Plone and Grok. There were discussions here and in the Plone community about this kind of convergence. That would be a huge win to have to write the content class code once and deploy either on Grok or Plone.
<br><br>Cheers,<br>Kamon<br></div></div>