1.
5 ‘real-world’ reasons to
go headless. The agency
perspective.
5

2.
Hello!
Andrew Whitehead.
CREATIVE & MANAGING DIRECTOR

3.
So, why am I up here?
#2
The lovely folk at Kentico
asked me!
#1
To provide an agency's real-world
perspective on using Kentico Cloud.

4.
To give some credibility - completed projects.
Wine Australia
website
Devotion
website
Sekisui House
live auction platform
Why Kentico Cloud: streamline the
content development process.
Why Kentico Cloud: speed-to-market
and availability of resource.
Why Kentico Cloud: isolate content
within a bespoke application.

5.
To give some credibility - in-progress projects.
Environmental cleaning
solutions website
Health fund
mobile application
Construction management
website
Why Kentico Cloud: budget and
creative requirements.
Why Kentico Cloud: multi-
platform content serving.
Why Kentico Cloud: limited
requirements.

6.
≠
It’s important to remember that...
Kentico CMS/EMS

7.
In plain English, a headless CMS is…
...a content hub that pushes your content to multiple devices in any format
you wish. Traditional CMS platforms require you to think about page
layouts, custom code, security, scalability, and performance. However, a
headless CMS focuses your attention on the content.

8.
As agencies, we usually ask what’s in it for us?
Why change what’s already working?

9.
Simple.
Additional revenue streams - lower budget projects = less getting bogged-down.
Embrace the resurgence of brochureware.
Seamlessly manage multi-channel content.
Change our resource dependencies (roadblocks).
Rapidly deliver solutions - both longterm and short lifespan.
Constantly iterate the front-end with no impact to the CMS.
Remain fresh - keep our team engaged.

10.
REASON 1
Flexibility.

11.
1. Use any programming language.
2. Use your own process, or create a new one.
3. Retain staff longer - devs love using the latest technology.
4. Get developers up and running quicker as there is little onboarding.
5. The intended experience is not constrained (or dictated) by the CMS.

12.
Devotion website.
● 2 weeks start to finish
● Front-end built in Vue.js
● Content entry prior to
front-end build

13.
REASON 2
Accessibility.

14.
1. Make content accessible to any channel or device via the API - think
web, mobile, kiosks, wearables, digital experiences etc.
2. Innovate and try new things as you’re delivering content components,
not pages.
3. Meet the needs of many customer scenarios - not aligned to one
vertical or segment of the market.

15.
Big health fund application
(in development).
● Built using React Native
● Data provided by ERP
API
● Content provided by
Kentico Cloud

16.
REASON 3
Control.

17.
1. Separate content (and its management) from its presentation.
2. Remove availability, security, performance, upgrade, and backup
concerns, as these belong to Kentico (the vendor) - simply control the
website or application.
3. Let people focus on what they’re good at - set your frontends free from
the structures of backend - eliminate “div-itis”.
4. Redesign your site without re-implementing the CMS.
5. Enable flexible workflows for different processes: reviews, approvals,
archiving, translation.

18.
Sekisui House
live auction platform.
● $20 million auction
● 7 days development
● Content written and
entered in parallel
● 1000+ concurrent users

19.
REASON 4
Speed.

20.
1. Deliver things much quicker - agency teams can work simultaneously.
2. Remove bottlenecks/barriers that traditionally exist.
3. Deliver solutions that are fast.
4. Shift display logic to client-side and streamline the backend - leading to
increased responsiveness.
5. Backend becomes system of record - interaction happens real-time in
the browser.

21.
Wine Australia.
● Used for ‘draft’ content
preparation while site
being built on Kentico
EMS (staged across)
● 3 months saved on
content creation
● 1700+ content items
written and reviewed
● Complex workflows

22.
REASON 5
Creativity.

23.
1. Content/experience comes first.
2. As the content is separated from the technology, it’s easy to go
‘beyond the website’ and open up a whole new world of content-
managed, and integrated (or centralised) experiences.
3. Multiple frontends can peacefully coexist.

24.
Environmental cleaning
solutions website.
● Brochureware with
complex frontend design
● Budget didn’t allow for
Kentico CMS
● Client entering all content
now (ahead of frontend)

25.
So, to summarise...
Kentico Cloud is not Kentico CMS/EMS - be selective.
Think speed to market.
Look to add additional revenue streams.
Use the awesome Kentico support team.
Get creative - don’t be constrained by the platform you currently use.
Embrace simplicity - no infrastructure concerns.

26.
Thanks +
Questions ?

27.
Visit us
Level 1, 168 Oxford Street
Paddington NSW 2021
Australia
Contact us
+61 2 9356 7900
hello@devotion.com.au
See what we’re up to
www.devotion.com.au
Thank you.