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:
<br>1. Easily themable/skinnable<br>2. Skins are portable to Plone<br>3. Data is easy to port to Plone portal types<br><br>If you make it possible to migrate TO the CMS e.g. from Joomla then you've got a winner, even better if it could somehow be made to use existing themes from other CMSes. Just dreaming :)
<br><br><div class="gmail_quote">On Dec 11, 2007 8:37 AM, Sebastian Ware <<a href="mailto:sebastian@urbantalk.se">sebastian@urbantalk.se</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;">
My penny... everybody who can creates a CMS at some point... how about<br>creating a CMS-construction kit where configuration and modifications<br>are done in code. Some components are allready available.<br><br>I have created a bare bones CMS for a couple of projects I am involved
<br>in. It is simple and isn't really geared towards website publishing<br>but rather content in general. I'd be happy to let you take a look at<br>it to see if you can use/abuse some of the ideas. However, right now,
<br>I can't commit to a project.<br><br>Mvh Sebastian<br><br>11 dec 2007 kl. 05.11 skrev Matt Bowen:<br><div><div></div><div class="Wj3C7c"><br>> Hi all,<br>><br>> For a few weeks now, a few of us have been tossing around (on blogs
<br>> and in IRC) the idea of writing a simple CMS in Grok. The goal is to<br>> keep the system simple, focusing on improving usability with<br>> subsequent releases instead of improved functionality. To keep<br>
> ourselves honest, we've set out with the goal of providing a<br>> migration path from the CMS to Plone; we figure that that will be so<br>> difficult that it will make us think twice about adding many features.
<br>><br>> With these few goals in place, I'd like to ask the community for<br>> comments and advice. I've set up a project page on OpenPlans that<br>> details what thinking has been done on the project, and there's an
<br>> IRC channel to discuss it if chat's your thing. Any advice is<br>> appreciated, and as things develop, if anyone thinks they'd be<br>> interested in working on such a project (planning, code, docs,<br>
> design, anything really), that would be wonderful. This is<br>> explicitly an open source project, and so the code will be licensed<br>> under an OSI license (ZPL 2.1 is my current plan) and in a public<br>> repository.
<br>><br>> Project Page: <a href="http://www.openplans.org/projects/concave/" target="_blank">http://www.openplans.org/projects/concave/</a><br>> IRC (freenode): #concave<br>><br>> Thanks for your time,<br>
> Matt Bowen<br>><br>> --<br></div></div>> blog: <a href="http://m.odul.us" target="_blank">http://m.odul.us</a> _______________________________________________<br>> Grok-dev mailing list<br>> <a href="mailto:Grok-dev@zope.org">
Grok-dev@zope.org</a><br>> <a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br><br>_______________________________________________<br>Grok-dev mailing list
<br><a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br><a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br></blockquote></div><br>