"Decoupling" is hot in the content management world, but the hype threatens obscure the real reasons to separate your content management from your content delivery platforms. In this talk from Drupalcon 2018, the history of decoupling and the reasons it can make sense are combined with useful heuristics for planning your own project.

1. An API Won’t Fix
Your Content Problem
Or, what we talk about when we talk about decoupling
Drupalcon 2018
eaton@lullabot.com

2. I’m @eaton.
I work for Lullabot.
We decoupling.

10. This cycle isn’t new…
…But it’s very, very hot.

11. This cycle isn’t new…
…But it’s very, very hot.

15. Innovation
Inflated expectation
Disillusionment
Enlightenment
Productivity

16. ‣ “It’s faster”
‣ “You can use the newest FED tech”
‣ “It’s future-proof”
‣ “You’ll be able to hire the best devs”
‣ “Because Medium.com, somehow”

17. |təˈmeɪtoʊ|
|təˈmɑːtəʊ|

19. “You Did It Wrong”
is not enough

21. Content Reuse

22. Costly Redesigns

23. Crippled FEDs

24. Bored engineers
with NPM

25. ‣ Reduce the effort of reusing,
repurposing content
‣ Implement new designs without
rebuilding the backend
‣ Let FEDs leverage cutting edge
tools and techniques

31. Assets
Components
Structure
Ephemera
Design
Metadata

32. That’s the
hard stuff.

36. We can do this!

38. Client apps are just
one toolwe use

39. Tech ≠ Strategy

40. Clear principles
reduce tech
whiplash