Wanna scale up? Make sure your CMS is ready for it!

Slide 1

Slide 1 text

@stefanjudis Wanna scale up? Make sure your CMS is ready for it!

Slide 2

Slide 2 text

@stefanjudis www.stefanjudis.com Heyo, I'm Stefan!

Slide 3

Slide 3 text

It's a great time to be a developer. The world is full of APIs!

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

jamstack.org

Slide 6

Slide 6 text

stefanjudis.com

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

css-tricks.com/the-all-powerful-front-end-developer/

Slide 9

Slide 9 text

Buying is almost always cheaper and faster than building.

Slide 10

Slide 10 text

The concept of decoupled content management

Slide 11

Slide 11 text

Content platform architecture Content Delivery Content Management Content Preview Scalable APIs READ READ / WRITE READ Editor Interface

Slide 12

Slide 12 text

Content platform architecture Editor Interface You and not your CMS make technology decisions. Content Delivery Content Management Content Preview Scalable APIs READ READ / WRITE READ

Slide 13

Slide 13 text

APIs at Scale !== Content at Scale

Slide 14

Slide 14 text

Building a single site is "easy"

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

What's important when content requirements scale up?

Slide 18

Slide 18 text

How fast can you move? What's your TTC? (time to content)

Slide 19

Slide 19 text

Are your developers productive (and happy) working with the platform?

Slide 20

Slide 20 text

0 % 14 % 28 % 42 % 56 % 70 % Better compensation Wanting to work with new tech Curious about new opportunities Better work/life balance insights.stackover fl ow.com/survey/2020#work-job-hunt-factors Developer job hunt factors

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Do your marketers and content creators like the platform?

Slide 23

Slide 23 text

Does the platform integrate well with other systems?

Slide 24

Slide 24 text

Is it fl exible?

Slide 25

Slide 25 text

Does it scale? (whatever this means)

Slide 26

Slide 26 text

A few lessons learned from growing with our customers

Slide 27

Slide 27 text

Content modelling is an art

Slide 28

Slide 28 text

Title Body Tags Author Description Title Body Tags Author Description Title Body Tags Author Description Posts / Pages Title Body Tags Description Author ARTICLE Name Date Talk EVENT Name Number of slides TALK Speaker A content graph Name Pro fi le image PERSON Avoid content duplication. De fi ne the required content structures.

Slide 29

Slide 29 text

Title Body Tags Description Author ARTICLE Name Date Talk EVENT Name Number of slides TALK Speaker Name Pro fi le image PERSON RESTful APIs with Client Libraries

Slide 30

Slide 30 text

Title Body Tags Description Author ARTICLE Name Date Talk EVENT Name Number of slides TALK Speaker Name Pro fi le image PERSON RESTful APIs with Client Libraries Fetch what you need

Slide 31

Slide 31 text

Title Body Tags Description Author ARTICLE Name Date Talk EVENT Name Number of slides TALK Speaker Name Pro fi le image PERSON RESTful APIs with Client Libraries Fetch what you need

Slide 32

Slide 32 text

contentmodel.io

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

Consider your content model very carefully!

Slide 35

Slide 35 text

Avoid WYSIWYG and Markdown content!

Slide 36

Slide 36 text

HTML in your content

Slide 37

Slide 37 text

Hardcoded links

Slide 38

Slide 38 text

JSON-based Rich Text

Slide 39

Slide 39 text

{ "nodeType": "document" , "data": {} , "content": [ { "nodeType": "paragraph" , "data": {} , "content": [ { "nodeType": "text" , "value": "This text is " , "data": {} , "marks": [ ] } , { "nodeType": "text" , "value": "important" , , Rich Text is clean JSON! const options = { renderMark: { [MARKS.BOLD] : text = > {text} < / Bold>, }, renderNode: { [BLOCKS.PARAGRAPH] : (node, children) = > { return {children} < / Text>; } }, renderText: text = > text.replace('!', '?'), }; documentToReactComponents(document, options);

Slide 40

Slide 40 text

github.com/contentful/rich-text

Slide 41

Slide 41 text

You will make mistakes in your content model

Slide 42

Slide 42 text

Name Pro fi le image PERSON First Name Pro fi le image PERSON Last Name

Slide 43

Slide 43 text

There has to be a way for programmatic content and content model changes. module.exports = function (migration) { const categoryFromTags = (tagList) = > { if (tagList.includes('javascript')) { return 'Development' } return 'General'; } migration.transformEntries({ contentType: 'blogPost', from: ['tags'], to: ['category'], transformEntryForLocale: async (from, locale) = > { return { category: categoryFromTags(from.tags[locale]) } } }); }

Slide 44

Slide 44 text

But even then, you can't "just YOLO " it! * You Only Live Once – similar to "Just do it"!

Slide 45

Slide 45 text

Environments MASTER

Slide 46

Slide 46 text

Environments MASTER

Slide 47

Slide 47 text

Environments MASTER Create development environment. (a copy of MASTER) FEATURE

Slide 48

Slide 48 text

Environments MASTER FEATURE Change content and content model. Write a migration script.

Slide 49

Slide 49 text

Environments MASTER FEATURE Apply migration to MASTER.

Slide 50

Slide 50 text

Environments and Aliases RELEASE-1 RELEASE-2 Create a MASTER alias.

Slide 51

Slide 51 text

Environments and Aliases RELEASE-1 RELEASE-2

Slide 52

Slide 52 text

Environments and Aliases RELEASE-1 RELEASE-2

Slide 53

Slide 53 text

Environments and Aliases RELEASE-1 RELEASE-2 Roll back if you need to.

Slide 54

Slide 54 text

Safe development environments CI/CD ready Quick migrations and rollbacks Environments and Aliases

Slide 55

Slide 55 text

www.contentful.com/help/cms-as-code/ www.contentful.com/developers/docs/concepts/deployment-pipeline/

Slide 56

Slide 56 text

Developers have to be safe to be productive.

Slide 57

Slide 57 text

Your content creators have to feel at home.

Slide 58

Slide 58 text

Stefan First Name PERSON Judis Last Name Content Delivery API Published content Content Preview Stefano First Name PERSON Judis Last Name Content Preview API Unpublished content

Slide 59

Slide 59 text

Preview API

Slide 60

Slide 60 text

The editing interface has to be extensible!

Slide 61

Slide 61 text

Content platform architecture Editor Interface Content Delivery Content Management Content Preview Scalable APIs READ READ / WRITE READ How do to extend and adjust an interface in the cloud?

Slide 62

Slide 62 text

The App Framework

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

Custom validations Open source components The App Framework

Slide 65

Slide 65 text

f36.contentful.com contentful- fi eld-editors.netlify.app

Slide 66

Slide 66 text

A 3rd party ecosystem

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

. . . . . .

Slide 69

Slide 69 text

No content

Slide 70

Slide 70 text

Access controls are essential in larger teams

Slide 71

Slide 71 text

Only certain people should be allowed to change the content model!

Slide 72

Slide 72 text

Image optimisation

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

No content

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

No content

Slide 78

Slide 78 text

Isn't it "just" an interface on a NoSQL database?

Slide 79

Slide 79 text

Summary Flexible and fast content modelling CI/CD ready via programmatic content changes Environments and aliases JSON based Rich Text Preview functionality Roles & permissions Extensible interface Work fl ows Images API 3rd party integrations Uptime, SLAs, support Developer community Open source libraries