Comments on: Fedora CMS focus and scope http://iquaid.org/2008/08/19/fedora-cms-focus-and-scope/ ... the four laws of humanity ... Thu, 04 Mar 2010 21:48:37 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: King InuYasha http://iquaid.org/2008/08/19/fedora-cms-focus-and-scope/comment-page-1/#comment-2482 King InuYasha Fri, 22 Aug 2008 13:05:15 +0000 http://iquaid.org/?p=163#comment-2482 Perhaps, Enano CMS could be tailored to the needs of the Fedora Project. It has wiki, security settings, and static modes that can be activated per-page, per-section, or throughout the whole thing. Possibly the Fedora Project theme could be converted to an Enano CMS theme so that all of it matches together. The Enano CMS 1.1.x series is improved by leaps and bounds over the 1.0.x series. There is a fine-grained ACL system, a high security user authentication system, and a lot of expandability. Fedora's User system that connects koji, bodhi, and other systems together could be integrated into the Enano CMS system with a plugin module. Perhaps, Enano CMS could be tailored to the needs of the Fedora Project. It has wiki, security settings, and static modes that can be activated per-page, per-section, or throughout the whole thing. Possibly the Fedora Project theme could be converted to an Enano CMS theme so that all of it matches together. The Enano CMS 1.1.x series is improved by leaps and bounds over the 1.0.x series.
There is a fine-grained ACL system, a high security user authentication system, and a lot of expandability. Fedora’s User system that connects koji, bodhi, and other systems together could be integrated into the Enano CMS system with a plugin module.

]]> By: quaid http://iquaid.org/2008/08/19/fedora-cms-focus-and-scope/comment-page-1/#comment-2479 quaid Thu, 21 Aug 2008 06:56:12 +0000 http://iquaid.org/?p=163#comment-2479 @Couf: Good question, I'd forgotten that FWN was looking in to a CMS solution. We've mainly discussed using Wordpress MU for FWN. That would leave the workflow as a manual process. FWN would be welcome to use any CMS solution, but it's not on my direct must-do list. @Couf: Good question, I’d forgotten that FWN was looking in to a CMS solution.

We’ve mainly discussed using Wordpress MU for FWN. That would leave the workflow as a manual process.

FWN would be welcome to use any CMS solution, but it’s not on my direct must-do list.

]]> By: couf http://iquaid.org/2008/08/19/fedora-cms-focus-and-scope/comment-page-1/#comment-2473 couf Wed, 20 Aug 2008 07:34:16 +0000 http://iquaid.org/?p=163#comment-2473 @Nicu: That is solvable by using caching mechanisms so that the CMS doesn't need to use multiple database queries to build up the page. Something else: will we use this for FWN stuff too (news.fp.o)? @Nicu: That is solvable by using caching mechanisms so that the CMS doesn’t need to use multiple database queries to build up the page.

Something else: will we use this for FWN stuff too (news.fp.o)?

]]> By: nicu http://iquaid.org/2008/08/19/fedora-cms-focus-and-scope/comment-page-1/#comment-2472 nicu Wed, 20 Aug 2008 06:57:22 +0000 http://iquaid.org/?p=163#comment-2472 In my understanding, the main reason to move the www.fp.o pages away from the wiki and to make them static was performance: around a release, when the traffic increase a lot, it hammered the entire website (including the wiki). So putting back a CMS will not create the same problem again? Or the idea is to use the CMS only behind the scene to edit the content and staticize the pages before publishing them? In my understanding, the main reason to move the http://www.fp.o pages away from the wiki and to make them static was performance: around a release, when the traffic increase a lot, it hammered the entire website (including the wiki).
So putting back a CMS will not create the same problem again? Or the idea is to use the CMS only behind the scene to edit the content and staticize the pages before publishing them?

]]>