New trends in CMS development.

1. Next Generation CMS

2. Die finanziellen
Auswirkungen CMS
Die finanziellen Auswirkungen einer
Fehlentscheidung können dramatische
Ausmaße annehmen. The decision-
making process for choosing a content
management system must be in the
hands of the whole team.

3. Team Members
● Agency Owner
● CTO
● Markters
● Programmers
● Front-end Developers
● Content strategists
● Copywriters

4. Marktsondierung
CMS große Namen Type
Wordpress ● tempton
● facebook
● cnn
● bbc
● kununu blog
● techcrunch
● cnn
Opensource
Typo3 ● tu-dortmund
● m-plan
● klinikumdo
● ferchau
● amadeus-fire
Opensource
eZ Publish ● bvb Opensource

5. Marktsondierung
CMS große Namen Type
Drupal ● Nestle
● United States Naval
Opensource
Contao(Symfony) ● advocard
● phantasialand
● steinmueller
Opensource
Shopware ● melitta
● rewe-dortmund
● tigha
Opensource

6. Marktsondierung
CMS große Namen Type
Adobe Experience Manager ● Mercedes-benz
● Aldi-nord
● BMW
● Agcocorp
● Shell
● allianz
● usbank
● Dhl
● intel
● Hm
● siemens
Private
Microsoft SharePoint ● Maggi Private
Intershop ● netto-online
● misterspex
Private

7. Marktsondierung
CMS große Namen Type
Sitecore ● tuvsud Private
Hybris(SAP) ● lenovo
● swarovski
Private
Salesforce Commerce Cloud ● soliver
● Salesforce Commerce
Cloud
Private
imperia CMS ● kicker
● strato
Private
Bloomreach ● ing
● NS Dutch Railways

8. Goals Bank (Why to change our current developing Philosophy)
Goal
Cloud first Digital Experience (DXM, DX, CEM, CX or CXM)
Adopting Sass and moving to the cloud to stay in the market
Content First Approach
Want to use the latest tools and technologies in the market
Technology Freedom
Content First Mindset (Im trend)
Content-as-a-Service (CaaS) platform vs CMS
CEM platforms allow content to be personalized based on user origin, onsite
activity, repeated visits and other anonymous behavior.
Deliver a new website very quickly as the rebranding project had a strict
timeline

9. Goals Bank (Why to change our current developing Philosophy)
Goal
A modern, responsive, and content-managed solution on a small business
budget.
Bring our website into the 21st century (Modern Stack)
Switch an outdated brochure site, into a powerful business-building tool?
Digital Transformation
Try something different
Integrations Everywhere - Typeform, Stripe, and Mailchimp for Faster
Project Delivery
The ability to manage content for all of their channels from a single place
Keeping all of their content in one place and delivering it easily to different
channels

10. Parameters for our decision
Parameter
x times faster project delivery
x weeks to implement a website
x content types
x languages
x increase in page views
x increase in pages per session
x content items
x reduction in time spent making content changes
x saving in CMS and hosting costs
x saving in development costs
x API Requests
No more css in Database
Wordpress stops the creativity of Frontend Developer

11. Monolithic CMS ,“decoupled” CMS and “headless”?

12. Headless CMS Philosophy

13. ● Content Modeling
● Assets Manager
● Content Publishing
● Users Management
● Localization
● API
Must have Modules in every headless CMS

14. Content Model

15. Software As a Service

16. Content Hub

17. OmniContent Delivery

18. Produce Content on the Cloud, use it everywhere

19. Traditional Cms

20. Headless Cms

21. Comparison between traditional CMS and Headless CMS

22. ● Every Headless Solution must have:
○ Backend
○ Api
○ Frontend
Headless cms is a Philosophy, not dependent on any Technology Stacks

23. Server Stack (Content Hub)
Stack Technology link
Sulu Symfony/PHP https://sulu.io/
Brandneo Custom Headless
CMS
Symfony/PHP
Strapi NodeJs https://strapi.io/
Webiny NodeJs https://www.webiny.com/
Contentful Paas https://www.contentful.com/
Kontent Paas https://kontent.ai/
Getcockpit php/mongo
Directus php
Prime typescript

24. Api
Stack Technology link
Rest API/Graphql Symfony/PHP https://api-platform.com/

25. Frontend Stack
Stack Technology link
Twig/Symfony Symfony/PHP https://symfony.com/
React Javascript https://reactjs.org/

26. The technology Stack#1
Part Technology Stack Link
One Application Symfony / React / Twig
Content Delivery API Graphql API
Pros:
● We know all the Stack
● We can use it direct for our new Website.
Cons:
● Not a Headless Philosophy
● We cannot work Parallel

27. The technology Stack#2
Part Technology Stack Link
One Application Symfony / Sulu CMS https://sulu.io
Content Delivery API Rest API
Pros:
● We know all the Stack
● We can use it direct for our new
Website.
● One step towards Headless
Technology.
Cons:
● Not a Headless Philosophy
We cannot work Parallel

28. The technology Stack#3
Part Technology Stack Link
Backend contentful https://www.contentful.com/
Content Delivery API Graphql API
Frontend Symfony/Twig
Pros:
● 100% Headless Philosophy
● 100% Modern Stack
● We know all the Stack
● We can use it direct for our new Website.
Cons:
● Connected to third Party

29. The technology Stack#4
Part Technology Stack Link
Backend Developing Our Cass
Solution
Content Delivery API Graphql API
Frontend Symfony/Twig or React
Pros:
● 100% Headless Philosophy
● 100% Modern Stack
● We know all the Stack
● We can use it direct for our new
Website.
Cons:
Continuous Upgrade

30. The technology Stack#5
Part Technology Stack Link
Backend Strapi Headless
CMS/NodeJs
https://strapi.io/
Content Delivery API GraphQL API
Frontend Gatsby
Pros:
● 100% Headless Philosophy
● 100% Modern Stack
Cons:
● Learning cycle

31. The technology Stack#6
Part Technology Stack Link
Backend Webiny Headless
CMS/NodeJs
https://www.webiny.com/
Content Delivery API GraphQL API
Frontend REACT
Pros:
● 100% Headless Philosophy
● 100% Modern Stack
Cons:
● Learning cycle

32. The technology Stack#7
Part Technology Stack Link
Backend Strapi as Content Hub https://strapi.io/
Content Delivery API GraphQL API
Frontend React
Pros:
● Built on the Shoulders of Giants
● 100% Modern Stack
Cons:
● Learning cycle

33. The technology Stack#8
Part Technology Stack Link
Backend React
Content Delivery API The API Platform
Framework (RestApi +
Graphql)
https://api-platform.com
Frontend React https://demo-client.api-
platform.com/
Pros:
● 100% Headless Philosophy
● 100% Modern Stack
Cons:
● Learning cycle

34. The technology Stack#9
Part Technology Stack Link
Backend Symfony
Content Delivery API The API Platform
Framework (RestApi +
Graphql)
https://api-platform.com
Frontend React https://demo-client.api-
platform.com/
Pros:
● 100% Headless Philosophy
● 100% Modern Stack
Cons:
● Learning cycle

35. Ressourcen
● https://github.com/contentful/the-
example-app.php
● https://app.contentful.com/
● https://www.contentful.com/developer
s/docs/concepts/data-model/
● https://www.netlify.com/
● https://www.youtube.com/watch?v=fJ-
tUBJFM5w
● https://headlesscms.org/
● https://www.youtube.com/watch?v=Y
Rxl3GRysuI
● https://www.centigrade.de/blog/de/
● https://marketplace.bloomreach.com/
● https://www.sutsche.com/beratung/cm
s-auswahl
● https://www.heroku.com/php
● https://www.recombee.com/
● https://www.youtube.com/watch?v=s0
e27UysZc0