Get the full overview of the new major release of Magnolia CMS.

1. Magnolia 6

2. Agenda
Overview
New UI
Content types
UI framework
Adopting Magnolia 6
Beyond Magnolia 6
Q&A
Rasmus Skjoldan, Chief marketing officer
Antti Hietala, Senior product manager
Christopher Zimmermann, Senior product manager

3. A ton
of exciting
new things

4. A redesigned UI, the find bar,
content types, our first AI features,
voice commands, auto-tagging,
customize apps and so much more…

5. Something larger
than features

6. 5 focus areas
Clear, simple and modern UI
Lending our UI to integrations
Using external content
AI Deep learning
Speed for digital marketing

7. Clear, simple
and modern UI
Marketers should enjoy working with Magnolia
Users are guided in their interactions with the product with meaningful navigation
elements, clear lines, boxes and forms and a central search feature.

8. Lending our UI to
integrations
Magnolia 6 is designed to be integrated with other systems beyond the data layer. Our
research pointed to technical integrations being insufficient if not deeply embedded in
UX/UI. The solution is a UX framework with UI patterns for each key integration-
category.

9. The search at the heart of the Magnolia 6 user interface.
Found on every page of the new Magnolia interface, a new feature called the Find Bar
offers powerful full-text search across all your content, no matter the app.
Developers can integrate any REST-compliant data source to be able to search
through content that's not stored in Magnolia.
Using external
content

10. AI
Deep learning
Magnolia Periscope Result Ranker
Our neural network-based AI engine brings the power of deep-learning to the Find Bar
search results. The more you search, the more Magnolia learns from your behavior
and preferences and the better your search results get. Magnolia suggests top hits and
ranks all your search results based on what it has learned.

11. Speed for digital
marketing
Create content types to speed up projects with a few lines of frontend code.
All this can be done using light development and deployed directly to a running
environment.
Combining Content Types with Magnolia’s REST endpoint API makes it an ideal match
for headless projects.

12. + Marketing power
Personalization
Magnolia 6 makes it possible to combine
explicit and implicit personalization so you
can individualize content and experiences
according to visitors’ profiles and intent.
Power personalization with machine learning
With machine learning providing relevant
topics for your customer segments, you can
personalize your content more effectively.
Launch targeted campaigns
Magnolia’s campaign manager lets you
easily create, manage, automatically
schedule, and reuse entire campaigns.
Automatic asset optimization makes sure
you deliver the perfect experience on any
channel or device.

13. Our customer focus
—Digitally savvy enterprises
—Prioritizing quality of customer experience
—Short time-to-value expectations

14. Why focus on design?

15. Why design?
— Marketers need an interface that doesn’t overwhelm but help
— Best-of-breed focused customers need seamless workflows

17. #MagnoliaPartners | @magnolia_cms#MagnoliaPartners | @magnolia_cms

18. “It's a HUGE step in the right
direction”
Deane Barker, author of Web Content Management from O’Reilly

19. “I really love this design
— it looks very, very nice”
(customer in Dubai)

20. “A central search bar like this
is absolutely awesome”
(Dutch customer)

21. “Smarter contextual search will
help our customers do their job
better and bring their content to
market faster.”
(US partner)

24. New UI
Antti Hietala, Senior product manager

25. Demo of our new UI

26. Find Bar
• Search all content in one place
• Adapts results real-time as you type
• Filter by type, tags, dates and authors
• Results ranked by neural network that learns from your search behavior.
• Voice commands

27. Image recognition
• Recognizes and tags image assets automatically
• Helps you find assets faster
• Local neural network — basic, good for starting
• Amazon Rekognition — advanced, impressive accuracy
• Integrate your own service for specialized imagery

28. Content Types
Christopher Zimmermann, Senior product manager

29. Content Model
the key types of content in your project,
the properties that each of those types have,
and their relationships

30. Example
Content
Model
Sporting Boats
Boat
Manufacturer
Boat TypeLength
Type
Manufacturer
Name
Address
Name
Description

31. Example
Content
Model
City Tours
Walking Tour Hotspots
Description
Tour Date
Hotspots
Name
Address
Rating

32. Backend Devs
Information
Architects
Marketing
Frontend Devs
Content Types
Content
Creators

34. How
does
it
work?

35. /contentTypes/hotspot.yaml /contentTypes/walkingtour.yaml

36. /apps/hotspots.yaml /apps/walkingTours.yaml

37. /apps/hotspots.yaml
App Tuning
Developers
have full control

40. Demo

42. Before Now
669 lines
Lines of config to create an app
14 lines

43. Benefits
Create apps fast
Authors can enter content right away
Frequent task is way faster
Improved evaluations, onboarding & PoC’s
Convincing headless
1. Build management UI
2. Deliver content via REST

44. Benefits
Speed
Speed
Speed

45. Unique
—Simple YAML Files
—Full power of Magnolia
—UX Flexibility
—Java
—Light Development
—Content Hierarchies

46. Status
—Developer Preview

47. UI Framework update

48. Why update?
√ Hasn’t happened for some years
√ Based on Vaadin 7 (that’s quite old)
√ Complicated parts

49. New UI Framework
• Cleaner and faster customization
• Simplified app mechanics
• Simplified app configuration

50. New UI Framework
• Less custom low-level code (GWT),
• in favour of stock Vaadin (including e.g. built-
in accessibility features)
• No deprecated Vaadin 7 code

53. Composable UI
√ component-driven patterns
√ separation of concerns
√ reactive UI state management
√ develop and customise with less hassle

54. Back end data-binding
√ Vaadin 8 implementations (lambdas!)
√ deprecate JcrContainer layer
√ datasource-agnostic base implementations

55. Back end data-binding
√ datasource-agnostic base implementations
√ JCR support
√ REST support in works

56. Form data-binding
√ simplified field API
√ UI and binding logic separation
√ custom form layouts
√ cross-field awareness

57. Status: Developer Preview
√ messages and tasks apps already use it
√ minimal API breaks to come
√ other apps run over Magnolia 5 UI framework

58. Adopting Magnolia 6

59. Client: To migrate from 4.5 to Magnolia 5,
estimated effort/costs by partner was bigger
than original implementation. How much is
migration to Magnolia 6 going to cost us?

60. Nada

61. “I’ve noticed there’s not even major version for
most of the modules, is that right?”
Christoph Meier

62. Drop-in upgrade
Just replace libraries in existing installation

63. Custom apps
Restyled automatically

64. Builds
Update poms, check libs, remove duplicates, fix
deprecated code … the “usual”,
don’t expect more effort than move from 5.6 to
5.7.

65. Is Magnolia 6 worth the upgrade effort?
Considering wealth of features and
improvements as well as low costs of upgrade,
answer is …
__ABSOLUTELY__

66. Magnolia 6
just the beginning

67. “The cognitive effort to process stats from
our analytics tools and bridge that to
meaningful action in the CMS is too high.”

70. More humble software
Not the center of the Universe – we work in a
digital ecosystem of applications
Lend our UI to other software
Decrease lock-in

71. Analyst work

72. Our engagement with Forrester & Gartner
What’s in it for you?
- Improving our industry understanding
- Solving critical capabilities & use cases
- Sanity-checking of our strategic plans

73. Where to find more?

74. Demo
magnolia-cms.com/magnolia-6
Release notes
Overview video

75. Updated roadmap

76. Questions