1. Leaks and Law Firms
A Kentico Cloud Story
Andy Thompson

2. Hi, I’m Andy

4. Today’s plan:
1. Site 1: Leak Week
2. Why Kentico Cloud?
3. Process changes
4. Site 2: MSL
5. Key differences
6. Q & A

5. Kentico Cloud
is not Kentico CMS
If you take one thing away from this presentation, let that be it!

6. Leak Week
Marketing microsite:
● Short timeframe
● Content management
● Phased release approach

7. Leak Week
Why Kentico Cloud?
● Basic requirements
● Agile development model
● Full release control

8. Typical
Project Plan
In a time before Cloud...
Waterfall:
1. Design required before FED
2. FED required before templates
are implemented in Kentico
3. Templates required before
content entry can start
Design
FED
BED
Content
Plan
Wireframe

9. Headless CMS
Project Plan
Restrictions removed:
1. Roles working simultaneously
2. Content and planning together
3. Back end before front end
4. Dev and design simultaneous
5. Design and FED based on real
structure, content and even
functionality
Content
Design
BED
FED
Plan
Wireframe

10. Headless CMS
Project Plan
Restrictions removed:
1. Roles working simultaneously
2. Content and planning together
3. Back end before front end
4. Dev and design simultaneous
5. Design and FED based on real
structure, content and even
functionality

11. Leak Week:
Content
Modelling
Very early wireframes:
● Producer, Designer, Front-end
and Back-end devs all sat down
together to workshop
● Producer and dev then created
content types
● Front-end dev understood
requirements and limitations
● Designer had immediate
feedback to roll in to designs

12. Leak Week:
The Ugliest Page
In The World
Thanks to MVC:
● Ms and Cs complete before
markup even began
● Vs are super simple and already
include literally all the required
data
● Theoretically any dev could
implement layouts later

13. Proof:
MSL Work in Progress
We’ve got another project underway right now, and here’s a sneak
peek.

14. Case Study 2:
msl.net.au
Project started two weeks
ago:
● Wireframes complete
● Content entry complete (!!)
● BED 90% complete
● Designs 50% complete
● FED not started
Content
Design
BED
FED
Plan
Wireframe
You are here

15. Questions

16. MSL:
Content
All content from their
existing site:
● Content Types created
● Drafts ready for review
● Additional Types created as
required
● Client contacts invited into the
system immediately

17. MSL:
Wireframes
Wireframes are complete.
● Using real content and pages
● Under review by client
● Guiding devs on new Content
Types

18. MSL
Ugly Pretty Site
Back-end dev is almost
complete:
● All required routes, controllers,
views and custom functionality
built before design
● Boilerplate provides basic
bootstrap styles
● Dev using real content, and real
API right from the start

19. We cheated a bit.
But you can too!
● Best of breed
● MVC Boilerplate
● Azure Web Apps
● Awesome people
MSL: HOW?
[COLLABORATION INTENSIFIES]

20. Key Differences

21. Pros
Bottlenecks removed
Back-end dev starts WAY earlier
Devs love using the latest technologies
Super-simple infrastructure requirements (yay Cloud!)

22. Kentico Cloud
Product Team
They listen, and they act.

23. Cons
Feature set drastically reduced
Major change in approach required
Content editors can’t build pages (yet?)
Basic functionality requires dev (or more services)
NEW!
MVC Boilerplate!
Download it now!

24. In summary:
1. Kentico Cloud is not Kentico CMS
2. Project process gets jumbled, in a good way
3. Your devs are gonna love it

25. Questions
and ?Answers

26. Thanks for listening
Andy Thompson
@andythompy
getstarted.com.au/andy