Re: CMS for simple content based websites.
"Sanjay Goel" <[email protected]> Wed, 18 Oct 2006 00:30:57 +0530
| Newsgroups | gmane.comp.cms.cms-forum.general |
|---|---|
| Message-ID | <[email protected]> |
--===============1191838844== Content-Type: multipart/alternative; boundary="----=_Part_60323_517447.1161111657385" ------=_Part_60323_517447.1161111657385 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Yes exactly, is that how typo3 works. Their documentation says otherwise. Thanks Sanjay On 10/18/06, Nagita Karunaratne <[email protected]> wrote: > > Hi Sanjay, > > Let's say there is a HR manager who needs to add a new position to the > employment page. > > This person has edit/add privileges to the page(s) that lists open > positions. > > They create the job requirements content etc and save the content on the > page. > > The page will not go 'live' until it is approved by the admin. > > The admin has no need to create a task for the HR manager. The HR > manager may edit at will any page to which they have privileges. Final > decision on what becomes public is up to the admin. > > Is this what you require? > > Thanks, > Nagita > > > > On 10/17/06, Sanjay Goel <[email protected]> wrote: > > Nagita, > > Its like this. Content Author has permissions to edit to some or all > pages > > of the portal. Content Author makes whatever changes he likes, whenever > he > > likes and submits it to the Reviewer, who reviews and publishes so that > the > > changes reflect on the live site. > > > > In case of Typo3, the admin first needs to assign a task to Content > Author. > > Then the author submits this task. This whole concept of assigning task > > again and again is painful. > > > > > > Thanks > > Sanjay > > > > On 10/17/06, Nagita Karunaratne <[email protected]> wrote: > > > 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 > > > > > > > > > > > -- > > > > Sanjay Goel > > http://sanjaygoel.blogspot.com > -- Sanjay Goel http://sanjaygoel.blogspot.com ------=_Part_60323_517447.1161111657385 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Yes exactly, is that how typo3 works. Their documentation says otherwise.<br><br>Thanks<br>Sanjay<br><br><div><span class="gmail_quote">On 10/18/06, <b class="gmail_sendername">Nagita Karunaratne</b> <<a href="mailto:[email protected]"> [email protected]</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Sanjay,<br><br>Let's say there is a HR manager who needs to add a new position to the <br>employment page.<br><br>This person has edit/add privileges to the page(s) that lists open positions.<br><br>They create the job requirements content etc and save the content on the page.<br><br>The page will not go 'live' until it is approved by the admin. <br><br>The admin has no need to create a task for the HR manager. The HR<br>manager may edit at will any page to which they have privileges. Final<br>decision on what becomes public is up to the admin.<br><br>Is this what you require? <br><br>Thanks,<br>Nagita<br><br><br><br>On 10/17/06, Sanjay Goel <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br>> Nagita,<br>> Its like this. Content Author has permissions to edit to some or all pages <br>> of the portal. Content Author makes whatever changes he likes, whenever he<br>> likes and submits it to the Reviewer, who reviews and publishes so that the<br>> changes reflect on the live site.<br>><br> > In case of Typo3, the admin first needs to assign a task to Content Author.<br>> Then the author submits this task. This whole concept of assigning task<br>> again and again is painful.<br>><br>><br>> Thanks <br>> Sanjay<br>><br>> On 10/17/06, Nagita Karunaratne <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br>> > Can you give an example of a workflow you envision?<br>> > Thanks, <br>> > Nagita<br>> ><br>> > On 10/17/06, Sanjay Goel <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br>> > > Nagita,<br>> > > I tried Typo3. Its workflow management is done by creating tasks for the <br>> > > content author by the admin. This is a painful way of workflow<br>> management.<br>> > > Also, in context editing is an addon kind of a thing for it. You can't<br>> > > create new content using the in-context editing feature. <br>> > ><br>> > > Thanks<br>> > > Sanjay<br>> > ><br>> > ><br>> > > On 10/17/06, Nagita Karunaratne <<a href="mailto:[email protected]">[email protected]</a>> wrote: <br>> > > > On 10/17/06, Sanjay Goel < <a href="mailto:[email protected]">[email protected]</a>> wrote:<br>> > > > > Hi,<br>> > > > > I have to create multiple websites with different templates. All <br>> these<br>> > > sites<br>> > > > > would be pretty simple only having content with no complex<br>> > > functionality.<br>> > > > > Can somebody suggest me a free/not so expensive CMS for this. <br>> > > > ><br>> > > > > The features I need are:<br>> > > > > 1. Easy Template Creation - Templates should easily be able to be<br>> > > created<br>> > > > > out of HTML files that my web designer creates. <br>> > > > > 2. In Context Editing - Something that WebGUI or Plone or Jahia<br>> provides<br>> > > is<br>> > > > > good.<br>> > > > > 3. Workflow - Content Approval workflow is a must. <br>> > > > ><br>> > > > > If its based on Java, it would be an added bonus.<br>> > > > ><br>> > > > > I have checked out lots of CMSes like Jahia (Expensive, bad at 1), <br>> > > Drupal<br>> > > > > (complex), Typo3 (bad at 3, not so good at 2), Mambo/Joomla (bad at<br>> 2)<br>> > > etc.<br>> > > > ><br>> > > ><br>> > > > TYPO3's main disadvantages are that it is difficult to implement by <br>> > > > the casual user and requires more server resources (cpu, memory). It<br>> > > > is an 'enterprise' level cms that does not play well in a shared<br>> > > > server environment. <br>> > > ><br>> > > > For (2), it has front-end editing which means the user can login and<br>> > > > add content to the pages directly without using the admin interface.<br>> > > > The admin interface is not that complex but you can remove access to <br>> > > > much of the functionality for simplification if the user is too<br>> > > > 'overwhelmed'.<br>> > > ><br>> > > > For (3), you can assign editing permission of specific pages to a user <br>> > > > and make sure that any page they do edit does not go 'live' until it<br>> > > > is approved.<br>> > > ><br>> > > > _Nagita<br>> > > ><br>> > > <br>> > ><br>> > ><br>> > > --<br>> > ><br>> > > Sanjay Goel<br>> > > <a href="http://sanjaygoel.blogspot.com">http://sanjaygoel.blogspot.com</a><br>> ><br>><br> ><br>><br>> --<br>><br>> Sanjay Goel<br>> <a href="http://sanjaygoel.blogspot.com">http://sanjaygoel.blogspot.com</a><br></blockquote></div><br><br clear="all"><br>-- <br>Sanjay Goel<br><a href="http://sanjaygoel.blogspot.com"> http://sanjaygoel.blogspot.com</a> ------=_Part_60323_517447.1161111657385-- --===============1191838844== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline