Choosing a CMS for your business can be a daunting task! Let us guide you though some of the pitfalls and important benefits to consider.

1. Choosing a CMS Solution
1
What Every Business User Should Know!

2. What is a Content Management System?
A CMS allows users to manage marketing, sales, and services
content for multiple sites easily, efficiently and quickly.
It should offer a mix of usability, power, and flexibility to help
teams optimize their digital channels.
22

3. Choosing a CMS is a Business Decision
This may be surprising to hear, but choosing a CMS should be a
business decision not a technical one.
A CMS is just a tool which should make the overall management
of content easier and more effective.
If a CMS solution does not allow users to quickly change and
deliver content, it has failed to serve its primary purpose.
33

4. Major CMS Platforms Today
● Adobe AEM (formerly CQ, formerly Day)
● Magnolia CMS
● Ektron
● Sitecore
● DotNetNuke and PhpNuke (including variants)
● Drupal
● Proprietary and custom build solutions
*Note that blogging platforms like Wordpress are not truly considered a CMS!
44

5. Every CMS solution will say it
can do everything...
Business users need to decide
if the CMS really meets their needs
in both the short and long term.
5

6. Typical CMS Approaches
PAGE FOCUSED
● In a page-based solution, most
content is managed as
individual pages.
● Typically, this requires some
knowledge of HTML and limits
the granularity in which
changes can be made without
specialized customization.
66
CONTENT FOCUSED
● Content-based solutions
usually define a hierarchy of
data which can be associated
to templates.
● This promotes a central
manageable content repository
and separate templates and
designs.

7. Page vs. Content Editing*
77
*Editable regions in red - The content approach gives a user far more control and less
risk of error.

8. Content and Publishing Workflows
One of the most important aspects of a
CMS solution is the CMS Workflow. It is
crucial that a CMS workflow can be
designed that supports your content
strategy, governance plan and any
internal business rules.
The right workflow can ensure that any
published content has the correct
approvals and optimize this process
within your organization.
88
Design
UpdatePublish
Approval

9. Questions You Should Consider
● How granular do I expect to manage content?
● How do I publish content?
● How much of my content can be reused?
● Do I plan on creating multiple and/or similar sites?
● Is it important for users to manage content?
● How often will I change my content?
● How often do I expect to need development support?
● What types of changes to content do I expect?
● How many places do I expect to change or add content?
99

10. The Future: Content-as-a-Service
A newer trend for CMS’s is the “content-as-a-service” approach to
managing and delivering content (also known as a “headless” CMS.)
Using this approach, a CMS serves as a data store and API only, with
all rendering and assembly of that data left to external processes.
Using this approach, authors get a customized and simplified tool
for managing their content, and designers can break free of the
confines of a particular platform.
1010

11. Logicdrop CMS Engine
In response to the overwhelming demand for a
better solution, we have crafted our own
in-house content management technology.
With a focus on Content-as-a-Service delivery,
our platform helps maximize user impact and
engagement while providing improvements
and optimizations though the entire lifecycle of
page and content development.
1111

12. Case Study: Kajeet Mobile Magnolia CMS Integration
THE PROBLEM:
Kajeet needed to manage digital content in
an easy to use way and expose that content
as well as multiple auxiliary data sources to
external applications which were not
Magnolia based.
● Needed a pure REST API
● Needed to handle multiple datasources
● Data was too complicated for external
applications to integrate with
1212
OUR SOLUTION:
Using our platform we created an API that sat
on top of Magnolia and provided the data in a
understandable JSON format for external
applications to consume. Internally, Kajeet
was still able to take advantage of Magnolia
and manage their content and assets.
● Used Magnolia as a “headless” CMS
● Used our platform to aggregate sources
● Applied transformers to cleanse the data

13. Case Study: Ford Dealer Site Platform
THE PROBLEM:
The Ford brand and dealer sites were based
on a legacy Java platform that was difficult
to manage, update, and deploy in a timely
fashion. Hundreds of different vendors need
to be able to interact with the system and
update content and various external sources
provided additional data not in the CMS.
● Content was unmanageable
● Long delivery times for any changes
● Difficult to change content
1313
OUR SOLUTION:
Completely re-architected the platform using
the JCR to provide a centralized location for
managing content. Sped up the
time-to-delivery by taking advantage of
custom publishing which reduced the overall
time from weeks to minutes.
● Restructured content using tags
● Page templating system
● Custom content entry screens

14. Our CMS Background
We once spent over a year analyzing numerous CMS solutions in
order to make a single recommendation to a global client.
Over seven years architecting and implementing large enterprise
CMS solutions using various technologies.
Many large CMS implementations for Fortune 1000 clients.
Currently, responsible for architecting the global CMS solution
for Ford.
1414

15. To learn more about our services and products,
schedule an executive briefing today:
+1 (888) 229-2817
www.logicdrop.com
1515