DMP FLO Suite - Content Management

DMP FLO Suite - Content Management - Image 1
Content Management interface
DMP FLO Suite - Content Management - Image 2
Front site built with content management
DMP FLO Suite - Content Management - Image 3
contentFLO entry point
Content Management with the DMP FLO Suite - Video
Click2Print, the DMP FLO Suite web to print application hosted by Drukkerij Kuypers - Video
Drukkerij Em. De Jong, customized web2print application designed for Domino’s Pizza with the DMP FLO Suite - Video

DMP FLO Suite takes the concept of a Content Management System (CMS) to new levels by integrating what is traditionally a web-only technology with your print production jobs. Whatever you previously delivered through your CMS (news items, FAQs, product information, etc.) can now be harnessed as data for print or other outputs within DMP FLO Suite.

 

One Database, Many Destinations

 

The ability to repurpose your data to many destinations greatly increases the efficiency of your workflow. Imagine a Web-to-print system where the client data you see online is the same data that are used in a final print job. This makes for no redundancy, less inaccuracy and vastly reduced turnaround and update times. DMP FLO Suite delivers on this dream by exploiting your CMS for more than just web publication.

 

A Two-Way Publishing Street

 

DMP FLO Suite is so adaptable that not only does it allow you to pull data you've published online into print, but you can reverse this process and send to the web any data that you might previously have used, for example, for a product catalog.

 

Flexible Web Applications

 

DMP FLO Suite's contentFLO module for CMS integration can be used to de-liver versatile and robust web applications. Built on .NET, developers can quickly add dynamic logic to their pages, allowing for advanced Web-to-print wizards, download centers etc. while relying of DMP FLO Suite's building blocks to provide the core functionality.

 

Key features included in DMP FLO Suite CMS

 

The following are just some of the key features in DMP FLO Suite's out-standing CMS tools:





 

The contentFLO module of the DMP FLO Suite is used to build custom websites. These websites can be used to publish the same data that you use elsewhere to create your printed catalogue. Or maybe it can contain the information of a typically website (news, FAQ, contact information, etc...)

But on top of that, contentFLO is also used to create web applications. By using the unprecedented flexibility of the DMP FLO Suite's scripting system, .NET code can be used to add dynamic logic to the web pages. This way, W2P wizards, download centers, etc... can be created in contentFLO.

Using the rest of the DMP FLO Suite as building blocks (e.g.: assetFLO as a source for a Document Center), development times of marketing applications are significantly reduced.

Included in the CMS:

  • Unlimited amount of databases for content management
  • HTML Templates
  • JS/CSS support
  • AJAX integration
  • VB.NET programming on top of the pages
  • Content management with customizable interface

Relevant documentation

FLOIntroductionToFLODevelopment.pdf
There are lots of ways to customize the way the FLO Suite is presented to end users. This document gives you a first glance at some of them.

PDF
(1465579 Kb)
FLOExamplesFrontsites_HR.pdf
This document contains some example applications that were built in the DMP FLO Suite. Each was custom made for the particular situation.

PDF
(5688688 Kb)
IntroductionForIT.pdf
An introduction of the DMP FLO Suite's features and functions for IT personnel.

PDF
(975939 Kb)
IntegratinExistingApplicationsInFLO.pdf
There are quite a few applications with features that don't exist in the FLO Suite. This document gives you some examples of integrating them into our system

PDF
(2073790 Kb)
IntegratingFLOinExistingApplications.pdf
In many cases, you or your customers might already have CMS applications running. This document gives you some examples on how to integrate them with FLO.

PDF
(528260 Kb)
FLOCaseNMBS_LR.pdf
The first phase of the Rail1 project consists of content and asset management (contentFLO & assetFLO). A web site had to be created for the external agents (resellers) of Rail1. Each agent has its own preferences/contracts/sales data/… In some cases this data has to be maintained by the agent himself, in other cases (e.g. for sales data), the information comes from monthly XML files, uploaded to the system.

PDF
(1896881 Kb)