The document discusses strategies for keeping Drupal relevant in an era dominated by git-based and API-driven content management systems (CMS). It outlines challenges related to performance, reliability, and security in both traditional and headless CMS architectures, while proposing solutions like using Drupal in tandem with modern front-end libraries and frameworks. Key recommendations include leveraging git-based services and tools, optimizing user experience, and adapting to evolving development practices.

1. How to keep Drupal relevant in the
Git-based and API-driven CMS era
by Jesus Manuel Olivas / weKnow#BADCamp

2. $ whoami
Jesus Manuel Olivas
jmolivas@weknowinc.com
jmolivas
jmolivas
drupal.org/u/jmolivas
jmolivas.weknowinc.com

3. Mexicali
Mexico + California
Calexico
California + Mexico
$ ifconfig

4. weAre

5. weKnow

6. weGive
2,572,697

7. Drupal … Drupal … Drupal

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

10. Traditional Monolithic CMS

11. Decoupling the frontend

12. Traditional Monolithic CMS + Particle (Design System)

13. The Traditional Headless

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

15. ●
Symfony API + Front-end library
Fetch

16. Challenges

17. Challenges
> Performance
> Reliability
> Security
> Hosting

18. Performance
Visitor Server CMS Database

19. Reliability - The Traditional Stack

20. Reliability - The Traditional Stack

21. Reliability - The Headless Stack

22. Reliability - A more advanced Stack

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

24. 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.

25. PaaS Headless CMS

26. ●
Strapi, Contentful (PaaS) + Front-end library
Fetch

27. Back to the flat-files

28. Everything old
is new again

29. git-based

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

31. git-based + UI using a PaaS

32. GravCMS Flat Files + Particle (Design System)

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

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

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

37. Blazing fast site generator for React

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

39. Drupal API + GatsbyJS
● Build

42. Getting Started

43. ● Build● API / GraphQL

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

45. Performance
Visitor CDN

46. The API Driven CMS Stack

47. Challenges

48. Challenges

49. Challenges

50. Challenges
• Use a markdown editor with Drupal. (we wrote a module for that)
• Preprocess inline-images on markdown. (we wrote a fix for that)
• Deploy site from Drupal. (we wrote a module for that)
• Learn Javascript
• Learn ReactJS
• Learn GraphQL

51. 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

52. 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

53. Choose the right tool for
the job

54. Design System - Atomic Design

55. UI Development Environment

56. https://events.drupal.org/seattle2019/sessions/how-keep-drupal-relevant-git-based-and-api-driven-cms-era
Want to see this talk at DrupalCon Seattle?, ask for it

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