[MAGNOLIA-309] Implement static publishing / export of final html Created: 10/Mar/05  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 2.1 Final
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: Dave Denis Assignee: Unassigned
Resolution: Won't Do Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

all


Template:
Acceptance criteria:
Empty
Date of First Response:

 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.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:16:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.