eZ Community » Forums » General » Migration from existing platform to eZ
expandshrink

Migration from existing platform to eZ

Migration from existing platform to eZ

Tuesday 07 July 2015 9:26:16 am - 7 replies

Currently we are using Documentum as our Web Content Management System (WCMS) with some of the tailored functions. As the expiration of support, we are now carrying out a feasibilty study to look for the possibility of migrating to other open source CMS.
---------------------------
Hosted Web Site:
~50 Sites
---------------------------
--------------------------------------------------------------------------------------------------------------------------
Functions involved:
1. Upload of SELF-DEVELOPED websites (files including: html / htm + css, js, jpg, png etc) [Mainly html files]
2. Workflow for controlling the publish of uploaded files of SELF-DEVELOPED websites to staging or production server
(i.e. Uploaded file (status: WIP [Work in progress]) -> Start Approval Workflow (status: Staging, uploaded to staging server for preview) -> Approved by reviewer (status: Approve & Active, publish to production server for viewing by public users)
--------------------------------------------------------------------------------------------------------------------------
I have been looking for many different forums. It seems that only the website created by eZ (but NOT SELF-DEVELOPED websites) could be put on the workflow for further publishing. Could any forum members and professional give me some hints if my said functions could be done with eZ?
Thanks!!!

Tuesday 07 July 2015 10:54:55 am

The thing is that almost everything can be done with eZ Publish because it is not CMS but CMF. It means that if you miss something, you can develop it.

So for me your requirements are not clear at all. How these self-developed sites are connected to CMS/CMF? How do you manage it?

As for eZ Publish you shoul also think of your project size. Do you have huge database?

Tuesday 07 July 2015 11:13:22 am

Quote from Andrey Astakhov :

The thing is that almost everything can be done with eZ Publish because it is not CMS but CMF. It means that if you miss something, you can develop it.

So for me your requirements are not clear at all. How these self-developed sites are connected to CMS/CMF? How do you manage it?

As for eZ Publish you shoul also think of your project size. Do you have huge database?

Thanks for your prompt reply!! Let me further explain our current flow and the re-design flow.

Currenly, we are using Documentum as our CMS. Users from different department can upload their self-developed websites (html, css, js, jpg etc) to their corresponding web-cabinet. At this moment, the files would be in "WIP" status and version control + check in / out feature are also provided (i.e. 1.0 -> 1.1 -> 2.0 etc).

Then, they could submit those files to pre-defined workflow to seek for the approval from their site reviewer for publishing to production environment. At the same time, the status of the files would be changed from WIP to Staging and the files would be transferred to our "Staging" web server for preview by reviewer. Once the reviewer find that the web-site in Staging server is in order, they could press the approve button under the workflow and publish the web-site from Staging web server to Production server immediately or with scheduled time.

 

Now, we would like to re-design and simplify our flow as below:

1. Upload of SELF-DEVELOPED websites (files including: html / htm + css, js, jpg, png etc) [Mainly html files]

2. Workflow for controlling the publish of uploaded files of SELF-DEVELOPED websites to staging or production server
(i.e. Uploaded file (status: WIP [Work in progress]) -> Start Approval Workflow (status: Staging, uploaded to staging server for preview) -> Approved by reviewer (status: Approve & Active, publish to production server for viewing by public users)

***NO version control and check in / out function would be provided in the future.***

 

Actually, there is no direct linkage between our CMS and website. CMS is only used for version control and publishing. As I am not familiar with eZ platform, I would like to find out if there is any out-of-box solution from eZ to facilitate our operation.

Thanks!

Tuesday 07 July 2015 11:17:48 am

So self-developed sites are fully functional websites and you need a workflow to pass files through some steps, don't you?

Tuesday 07 July 2015 12:09:58 pm

Quote from Andrey Astakhov :

So self-developed sites are fully functional websites and you need a workflow to pass files through some steps, don't you?

Exactly!! I would like to have a platform to hold the uploaded files and start the workflow to publish to corresponding web server under different stage. Could ez Publish be used in this way?

Tuesday 07 July 2015 3:03:22 pm

Theoretically yes.

But not out-of-box.

eZ Publish is more about creating specific kinds of content, managing hundreds of content versions in dozens of languages, outputting rich content, configuring editorial workflows.

You don't need most of it. It seems that your need rather file management solution and there are no built-in tools in eZ Publish for this purpose.

Wednesday 08 July 2015 5:18:40 am

Quote from Andrey Astakhov :

Theoretically yes.

But not out-of-box.

eZ Publish is more about creating specific kinds of content, managing hundreds of content versions in dozens of languages, outputting rich content, configuring editorial workflows.

You don't need most of it. It seems that your need rather file management solution and there are no built-in tools in eZ Publish for this purpose.

So for creating specific kinds of content, does it mean that we have to use the complete workflow of eZ Publish?

(e.g. create web content with the functions/templates provided by eZ [xsl as layout and xml as content] -> version control for every piece of web content -> create the workflow for different conditions ->  publish the web-content to be viewed by public users when certain conditions meet.)

Everything should be done within the eZ Publish CMS instead of eZ + Standalone Web Servers?

So should I find another solution instead of "drilling" into eZ Publish?

Thanks!!!!

Modified on Wednesday 08 July 2015 5:22:35 am by Geane Chan

Sunday 26 July 2015 8:03:35 am

Hi Geane

Usually yes, but it is possible to use the eZ publish to do it AND ALSO help you integrating your current workflow with eZ, somehow, as Andrey pointed out, it will require way more info about the current solution,  some brain storming on how to do it, probably outside of the scope of the discussion here, a middle term solution, which I would recommend, would be to import all the current content into eZ, by parsing the current files and creating some code to help in the migration and then forget about the old workflow and just use eZ publish after the content has been imported. With the eZ online editor you can insert also HTML, JS and CSS using the literal tag, and you can upload images on the fly, so there is no need to keep uploading raw html files, by doing so you have the advantage of integrating the content with eZ find and easier update the design later.

I can promptly confirm that importing pure html content to eZ requires some considerable effort to parse the content and do all the necessary work, like generating the content structure, urls, etc but at the end of the day it worth all the headaches in the long run.

Modified on Sunday 26 July 2015 8:08:02 am by Thiago Campos Viana

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from