Re: CMS for simple content based websites.
"Nagita Karunaratne" <[email protected]> Tue, 17 Oct 2006 11:14:14 -0700
| Newsgroups | gmane.comp.cms.cms-forum.general |
|---|---|
| Message-ID | <[email protected]> |
Can you give an example of a workflow you envision? Thanks, Nagita On 10/17/06, Sanjay Goel <[email protected]> wrote: > Nagita, > I tried Typo3. Its workflow management is done by creating tasks for the > content author by the admin. This is a painful way of workflow management. > Also, in context editing is an addon kind of a thing for it. You can't > create new content using the in-context editing feature. > > Thanks > Sanjay > > > On 10/17/06, Nagita Karunaratne <[email protected]> wrote: > > On 10/17/06, Sanjay Goel <[email protected]> wrote: > > > Hi, > > > I have to create multiple websites with different templates. All these > sites > > > would be pretty simple only having content with no complex > functionality. > > > Can somebody suggest me a free/not so expensive CMS for this. > > > > > > The features I need are: > > > 1. Easy Template Creation - Templates should easily be able to be > created > > > out of HTML files that my web designer creates. > > > 2. In Context Editing - Something that WebGUI or Plone or Jahia provides > is > > > good. > > > 3. Workflow - Content Approval workflow is a must. > > > > > > If its based on Java, it would be an added bonus. > > > > > > I have checked out lots of CMSes like Jahia (Expensive, bad at 1), > Drupal > > > (complex), Typo3 (bad at 3, not so good at 2), Mambo/Joomla (bad at 2) > etc. > > > > > > > TYPO3's main disadvantages are that it is difficult to implement by > > the casual user and requires more server resources (cpu, memory). It > > is an 'enterprise' level cms that does not play well in a shared > > server environment. > > > > For (2), it has front-end editing which means the user can login and > > add content to the pages directly without using the admin interface. > > The admin interface is not that complex but you can remove access to > > much of the functionality for simplification if the user is too > > 'overwhelmed'. > > > > For (3), you can assign editing permission of specific pages to a user > > and make sure that any page they do edit does not go 'live' until it > > is approved. > > > > _Nagita > > > > > > -- > > Sanjay Goel > http://sanjaygoel.blogspot.com