Details
-
New Feature
-
Resolution: Won't Do
-
Minor
-
None
-
2.1 Final
-
None
-
None
-
all
-
-
Empty show more show less
Description
Magnolia should implement a publishing feature, much like the mid-tier CMSs such as RedDot and Rhythmyx offer. This basically works by publishing out static files to any number of web servers. The benefits:
- web servers can be added easily without configuring them for the CMS
- existing infrastructure can be maintained; an ASP or PHP shop can use Magnolia to publish out these types of files; it is easier to drop one J2EE CMS box in to an organization than to try and get them to switch their infrastructure
- content is not "trapped" in the CMS, if the CMS goes down, that's fine, the pages/files are all on the web servers
The challenges require detailed link/relationship management because the CMS should not re-publish the entire site if only a headline changes on a single press release. But on the other hand, all pages affected by this headline change (a news listing page, homepage and a random page linking to it for example) need to. The CMS needs to publish not only pages but media assets as well. Publishing is usually offered via FTP and file system and is tied to workflow (a publishing job can be kicked off when a page is approved or manually initiated).
I know there are a lot more details in the execution, I can whatever additional information I have.