Hey, > > At this stage of the project we are just researching which options > > current popular CMS systems > I think you should first pick a target audience and then > model your CMS towards that group of users with their application. Agree to disagree :) The few stars in the flood of available CMS systems have shown that a generalized approach IS possible. And especially with wicket it should be a breeze to individualize whatever you guys (Ted and Rick) come up with at the end of your project - if it is nice and abstract. If you focus too much on one group of users, in my experience you end up being stuck or having to write ugly workarounds once you want something a little more exotic.
On the other hand - and since wicket is in itself such a clean and flexible framework - being too abstract will have you end up with writing not very much at all since all the functionality is basically already 'there'. Just as always, it's a fine line - enjoy walking it! :) // Che ______________________________ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
