Watch this Tech Talk: https://do.co/video_dphiri The role of content management systems keeps evolving and in the self hosted utopia we're approaching, it's easy to get lost in a sea of micro services. I'll be explaining what makes a good CMS, things to consider when picking one and why Strapi is a great pick for your business, taking the API-first approach and extending its usefulness to other parts of your business. About the Presenter Daniel Madalitso Phiri is a retired podcaster and developer interested in developer tooling, and is currently a Developer Advocate at Strapi. New to DigitalOcean? Get US $100 in credit when you sign up: https://do.co/deploytoday To learn more about DigitalOcean: https://www.digitalocean.com/ Follow us on Twitter: https://twitter.com/digitalocean Like us on Facebook: https://www.facebook.com/DigitalOcean Follow us on Instagram: https://www.instagram.com/thedigitalocean/ We're hiring: http://do.co/careers

2. Developer Relations
Daniel Madalitso Phiri
Disk Jockey
malgamves

3. CMS - Content Management System
Content Model - Collection of related fields
DX - Developer Experience
definitions

4. I’ll have a few nautical
references
Ships and Oceans are…
interesting

5. overview
- Planning your voyage
- Getting a crew onboard
- Being resourceful at sea

6. Planning your voyage🗺

7. Building Software is only preparation
for your journey..

8. Software goes beyond just how it’s
built

9. How do you maintain and scale your
software?

10. Unreliable and Inaccessible software
is as good as no software

11. “A sturdy launchpad makes for a
better lift off”
-moi

12. This concept can extend itself way
beyond just software..

13. To even... content

14. Content extends into every part of our
lives

15. “Content is Queen or King..”

16. Content is at the center of your
modern business..

17. The API first approach of Headless
CMSs makes this scaling simpler

18. Headless means we deliver content to any
frontend via and API
���� ⌚
Content

19. Tip 1: Go Headless

20. Getting a crew onboard 🏃‍♀

21. You’re creating workflows

22. Every team should be covered

23. A Workflow
💻
👩‍💻
👩‍🏫
Application
Content Team
Developer Team
End Users

24. Optimize for your Content Team
👩‍🏫

25. Robust UI
Access Control
A wealth of fields
Reusable Content Models
Great UX

26. Optimize for your Developer Team
👩‍💻

27. Robust DX
API Flexibility
Wealth of resources
Wealth of Integrations

28. A successful team is a successful
business

29. In optimizing for each team, you’re
enabling easier scalability of your
content

30. scaling content goes two ways
Build your API once, display on different frontends.
Build flexible content models once, reuse anywhere.

31. Tip 2: Optimize for efficiency

32. Being resourceful at sea 🌊

33. Get the most out of what you have

34. Headless at it’s core promotes
extensibility

35. Capture business value beyond
Content
&
Extend functionality

36. Customizability
Support for 3rd Party Services
Handle end user Auth
Rich plugin ecosystem
Is it Open Source?**

37. Tip 3: Extend your CMS

38. Tip 1: Go Headless
Tip 2: Optimize for efficiency
Tip 3: Extend your CMS
summary

39. … but wait

40. Everything I mentioned is at the core
of how Strapi is built..
There aren’t that many open source
headless cms that do this

41. Strapi is a Headless CMS
Open source.
100% JavaScript.
Customizable. Self-hosted.
Plugins system. GraphQL.
its..

42. bit.ly/strapi-droplet
to test out Strapi free

43. Bon Voyage 🙏

44. strapi.io/getting-started
resources

45. ● thank you...and smooth sailing