1. How to keep Drupal relevant in the
Git-based and API-driven CMS era
by enzo - Eduardo Garcia / weKnow#DrupalSouth

2. $ whoami
enzo - Eduardo Garcia
enzo@weknowinc.com
enzolutions
enzolutions
drupal.org/u/enzo
enzo.weknowinc.com

3. 1 Colombia.com.co 60%
2 CostaRica.co.cr 35%
3 Australia.com.au (Tasmania) 5%
$ traceroute

4. weAre

5. weGive
3,300,779

6. Drupal … Drupal … Drupal

7. weKnow

8. When all you have is a
hammer, everything looks
like a nail.

10. The Traditional Headless

11. ●
Drupal Headless API + Front-end library
Fetch

12. ●
Symfony API + Front-end library
Fetch

13. Challenges

14. Challenges
> Reliability
> Security
> Hosting
> Performance

15. Reliability - The Traditional Stack

16. Reliability - The Traditional Stack

17. Reliability - The Headless Stack

18. Reliability - A more advanced Stack

19. Security
> System dependencies
> Stack dependencies
> Platform dependencies core
> Custom modules dependencies hosted
> Third party libraries hosted

20. Hosting
> Managing a complicated stack is not easy.
> Requires knowledge of managing servers, databases,
cache, DNS, backups, automation, and much more.
> The more complex your stack is to support your
production site, the more expensive it becomes.

21. Performance
Visitor Server CMS Database

22. Back to the flat-files

23. Everything old
is new again

24. git-based

25. Improving the UX providing a GUI
when using a Git-based CMS.

26. git-based + UI using a PaaS
● NetlifyCMS ● Forestry ● Cloud Cannon

27. Using Drupal to provide a GUI and
content for a Git-based/API-driven CMS.

28. Drupal CMS + Tome to export as Flat Files
+ ● Build

29. Decoupling the
"Content Management GUI"
from the
“Production Environment".

31. Blazing fast site generator for React

32. The Content Mesh
● https://www.gatsbyjs.org/blog/2018-10-18-creating-compelling-content-experiences/

35. Getting Started

36. ● Build● API

37. Feel free to turn off your Drupal after build
●https://twitter.com/ckaotik/status/647020262001614848

38. Performance
Visitor CDN

39. The API Driven CMS Stack

40. Challenges
• Use a markdown editor with Drupal.
• https://www.drupal.org/project/tui_editor
• Preprocess inline-images on markdown. (we wrote a plugin for that)
• Deploy site from Drupal.
• https://www.drupal.org/project/build_hooks
• Learn Javascript
• Learn ReactJS
• Learn GraphQL

41. What is Gone
• Twig
• Render array
• Theme layer
• Theme preprocessing
• *Views (use GraphQL instead)
• Data modeling.
• Content editor capabilities,
revisions, moderation and
scheduling.
• Pathauto
• Site Settings
What to keep using

42. Must have plugins
• gatsby-source-drupal
• gatsby-transformer-remark
• gatsby-remark-images
• gatsby-remark-external-links
• gatsby-plugin-sharp
• gatsby-transformer-sharp
• gatsby-plugin-react-helmet

43. Choose the right tool for
the job

44. Thank you … Questions?
Feel free to ping me during the event,
at the parties, after-parties, and twitter @enzolutions

45. weDemo

46. weDemo