Content Modeling 101

Rate this content
Bookmark

In today's world, it's no surprise that "Content is King". It helps in telling a story and helping you reach out to more people. Most of the time, developers aren’t the ones managing this content. Hence, modeling content efficiently becomes crucial. Doing it well makes the content delivery process smooth for the team. But how does one go on with modeling content? What are the things that one should take care of? I’ll answer such questions in this talk, and share my approach to content modeling as a JavaScript developer.

7 min
16 Jun, 2022

Comments

Sign in or register to post your comment.

AI Generated Video Summary

This Talk provides an introduction to content modeling and its importance in organizing content for teams. It explores the top-down approach to simplify and make content models more reusable, using a recipe app as an example. The Talk also highlights the best practices for content modeling, including considering reusability, rendering for end users, content governance, platform considerations, and continuous iteration.

1. Introduction to Content Modeling

Short description:

Hey everyone, welcome to my talk, Content Modeling 101. I will discuss the importance of content modeling and how it helps organize content for the entire team. Let's dive into modeling a content for an app, specifically a recipe app. I learned about the top-down approach, which simplifies the content model and makes it more reusable. I created a JSON schema for the recipe content model, including title, description, ingredients, instructions, and images.

Hey everyone, and welcome to my talk, Content Modeling 101. Now, my name is Harsh Lagrawal, and I am originally from India, living in Berlin for 15 months now, and I work as a developer advocate at Contentful. And one of the fun parts I love about my job is that I get to experiment a lot with different technologies and framework, and share this learning with the wider community. So you can find about all these experiments and crazy stuff that I do on my website, or feel free to follow me on Twitter. Also, this is my first time in Amsterdam, so if you have any recommendations, please do let me know.

So today, I am going to talk about content, because in the past two years the amount of content that we have generated has been massive. I mean, almost everyone out there has been involved in creating content in some form or the other. And last year in November itself, during the Black Friday sale, we saw a massive amount of incoming requests being made to our Contentful APIs. The GraphQL API request increased by 550%, and the Content Delivery API, or the CDA, increased by 73%. And that was just in one month. And so I feel, as a developer, it is our duty to make sure that we are creating an amazing experience not just for our end users, but for our team as well. And that is where content modeling comes into the picture. But the question is, what is content modeling? So a content model basically gives structure and it helps you to organize your content. Now keep in mind, that not all content creators and designers have that technical expertise like us. Hence, the goal over here is to create a content model that will support the needs of the entire team, from content creators, designers, to developers.

Enough of the theory, let's try to get into action and try to model a content for an app. And this is an app that I am working on and I want to create for myself, because I have taken cooking as a hobby recently and I want to try out to build an app that I can store all my recipes and maybe share it with everyone else. And I want to build this because I am a programmer and I have the superpower to do that. But anyways, there are a few things that I learned when I was researching for this and I started working on it, and in the next couple of slides I will be talking about that. And one of the major things that I learned was about the top-down approach, because it helped me break down my content model and I was able to simplify the content model and make it more reusable. So I started playing around with the JSON schema and I created this JSON schema. So I have a content model which has a recipe which contains the title, a description, ingredients. Now if you see ingredients is an array and I'm going to come back to that. And then there are instructions and then the images. Once I had the JSON schema and I kind of had the visual representation of what I wanted to do, I simply translated it into the content model in Contentful and you can already see all this in Contentful. Now if you see or focus on the ingredients it says references, many. So what I went ahead and did was I created a different content type for ingredients. So if you go one layer deep this is what the ingredient JSON type JSON schema looks like. The ingredient has a name and it has a type. Now I am vegetarian.

2. Content Modeling Best Practices

Short description:

For content modeling, it's important to consider reusability and how the content will be rendered for the end user. Content governance, platform considerations, and continuous iteration are also key. Check out our learning center and developer portal for more details.

I don't eat meat. So for me I need to make sure you know what kind of ingredients I'm adding over there and it makes it easy for me to classify as well. So the type over here is again another content type and I'm sorry I'm repeating types too many times. So this is how it looks like in Contentful again.

Now I'm not going to go into the ingredient type because it's kind of similar but I wanted to give you a quick view of how different content types are connected with each other. So there's recipe which is referencing the ingredients. Recipe is referencing to ingredient type and recipe is also referencing to acid. So one of the important features of content modeling is reusability.

Now taking this example of the cookbook, a lot of the ingredients are used in a lot of different recipes and adding each of these recipes, sorry, these ingredients to each of these recipes individually does not make a lot of sense. And I personally believe that developers are kind of lazy and they always want to find the quickest and the shortest way to do stuff, so that's where reusability comes into the picture.

The next is a content model does not just do content, it also embodies the decision about how you want to render the content for the end user, how your team should publish and display the content. And we refer to this constellation of issues as content governance. And you also need to think about the platform, where and how will the users interact with your content. Is it just going to be only on the web? Are you going to go ahead and build a mobile application? Are your users gonna get this information on a voice enabled application? So that is one of, that is the other feature that you need to think about.

And lastly, remember, nobody gets content model right in one pass. It's a continuous process, so keep on iterating over it. Get the feedback from your team, from your users, and keep making changes. And if you want to learn more about content model or contentful, hop on to our learning center. We have some amazing courses where you can learn about them in much more details. We also have a developer portal if you want to just get started, look at the developer resources that we have. That's the correct place to go. And we are here at the booth and we have an interesting giveaway. So come say hi at the booth, grab some swags, and maybe participate in the giveaway.

Check out more articles and videos

We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

React Advanced Conference 2021React Advanced Conference 2021
39 min
Don't Solve Problems, Eliminate Them
Humans are natural problem solvers and we're good enough at it that we've survived over the centuries and become the dominant species of the planet. Because we're so good at it, we sometimes become problem seekers too–looking for problems we can solve. Those who most successfully accomplish their goals are the problem eliminators. Let's talk about the distinction between solving and eliminating problems with examples from inside and outside the coding world.
React Advanced Conference 2022React Advanced Conference 2022
30 min
Using useEffect Effectively
Can useEffect affect your codebase negatively? From fetching data to fighting with imperative APIs, side effects are one of the biggest sources of frustration in web app development. And let’s be honest, putting everything in useEffect hooks doesn’t help much. In this talk, we'll demystify the useEffect hook and get a better understanding of when (and when not) to use it, as well as discover how declarative effects can make effect management more maintainable in even the most complex React apps.
React Advanced Conference 2021React Advanced Conference 2021
47 min
Design Systems: Walking the Line Between Flexibility and Consistency
Design systems aim to bring consistency to a brand's design and make the UI development productive. Component libraries with well-thought API can make this a breeze. But, sometimes an API choice can accidentally overstep and slow the team down! There's a balance there... somewhere. Let's explore some of the problems and possible creative solutions.
React Summit 2023React Summit 2023
23 min
React Concurrency, Explained
React 18! Concurrent features! You might’ve already tried the new APIs like useTransition, or you might’ve just heard of them. But do you know how React 18 achieves the performance wins it brings with itself? In this talk, let’s peek under the hood of React 18’s performance features: - How React 18 lowers the time your page stays frozen (aka TBT) - What exactly happens in the main thread when you run useTransition() - What’s the catch with the improvements (there’s no free cake!), and why Vue.js and Preact straight refused to ship anything similar
React Summit 2023React Summit 2023
24 min
Debugging JS
As developers, we spend much of our time debugging apps - often code we didn't even write. Sadly, few developers have ever been taught how to approach debugging - it's something most of us learn through painful experience.  The good news is you _can_ learn how to debug effectively, and there's several key techniques and tools you can use for debugging JS and React apps.

Workshops on related topic

React Summit 2023React Summit 2023
170 min
React Performance Debugging Masterclass
Featured WorkshopFree
Ivan’s first attempts at performance debugging were chaotic. He would see a slow interaction, try a random optimization, see that it didn't help, and keep trying other optimizations until he found the right one (or gave up).
Back then, Ivan didn’t know how to use performance devtools well. He would do a recording in Chrome DevTools or React Profiler, poke around it, try clicking random things, and then close it in frustration a few minutes later. Now, Ivan knows exactly where and what to look for. And in this workshop, Ivan will teach you that too.
Here’s how this is going to work. We’ll take a slow app → debug it (using tools like Chrome DevTools, React Profiler, and why-did-you-render) → pinpoint the bottleneck → and then repeat, several times more. We won’t talk about the solutions (in 90% of the cases, it’s just the ol’ regular useMemo() or memo()). But we’ll talk about everything that comes before – and learn how to analyze any React performance problem, step by step.
(Note: This workshop is best suited for engineers who are already familiar with how useMemo() and memo() work – but want to get better at using the performance tools around React. Also, we’ll be covering interaction performance, not load speed, so you won’t hear a word about Lighthouse 🤐)
React Summit Remote Edition 2021React Summit Remote Edition 2021
177 min
React Hooks Tips Only the Pros Know
Featured Workshop
The addition of the hooks API to React was quite a major change. Before hooks most components had to be class based. Now, with hooks, these are often much simpler functional components. Hooks can be really simple to use. Almost deceptively simple. Because there are still plenty of ways you can mess up with hooks. And it often turns out there are many ways where you can improve your components a better understanding of how each React hook can be used.You will learn all about the pros and cons of the various hooks. You will learn when to use useState() versus useReducer(). We will look at using useContext() efficiently. You will see when to use useLayoutEffect() and when useEffect() is better.
React Advanced Conference 2021React Advanced Conference 2021
174 min
React, TypeScript, and TDD
Featured WorkshopFree
ReactJS is wildly popular and thus wildly supported. TypeScript is increasingly popular, and thus increasingly supported.

The two together? Not as much. Given that they both change quickly, it's hard to find accurate learning materials.

React+TypeScript, with JetBrains IDEs? That three-part combination is the topic of this series. We'll show a little about a lot. Meaning, the key steps to getting productive, in the IDE, for React projects using TypeScript. Along the way we'll show test-driven development and emphasize tips-and-tricks in the IDE.
React Summit 2023React Summit 2023
151 min
Designing Effective Tests With React Testing Library
Featured Workshop
React Testing Library is a great framework for React component tests because there are a lot of questions it answers for you, so you don’t need to worry about those questions. But that doesn’t mean testing is easy. There are still a lot of questions you have to figure out for yourself: How many component tests should you write vs end-to-end tests or lower-level unit tests? How can you test a certain line of code that is tricky to test? And what in the world are you supposed to do about that persistent act() warning?
In this three-hour workshop we’ll introduce React Testing Library along with a mental model for how to think about designing your component tests. This mental model will help you see how to test each bit of logic, whether or not to mock dependencies, and will help improve the design of your components. You’ll walk away with the tools, techniques, and principles you need to implement low-cost, high-value component tests.
Table of contents- The different kinds of React application tests, and where component tests fit in- A mental model for thinking about the inputs and outputs of the components you test- Options for selecting DOM elements to verify and interact with them- The value of mocks and why they shouldn’t be avoided- The challenges with asynchrony in RTL tests and how to handle them
Prerequisites- Familiarity with building applications with React- Basic experience writing automated tests with Jest or another unit testing framework- You do not need any experience with React Testing Library- Machine setup: Node LTS, Yarn
React Day Berlin 2022React Day Berlin 2022
53 min
Next.js 13: Data Fetching Strategies
WorkshopFree
- Introduction- Prerequisites for the workshop- Fetching strategies: fundamentals- Fetching strategies – hands-on: fetch API, cache (static VS dynamic), revalidate, suspense (parallel data fetching)- Test your build and serve it on Vercel- Future: Server components VS Client components- Workshop easter egg (unrelated to the topic, calling out accessibility)- Wrapping up
React Summit 2022React Summit 2022
160 min
React at Scale with Nx
WorkshopFree
The larger a codebase grows, the more difficult it becomes to maintain. All the informal processes of a small team need to be systematized and supported with tooling as the team grows. Come learn how Nx allows developers to focus their attention more on application code and less on tooling.
We’ll build up a monorepo from scratch, creating a client app and server app that share an API type library. We’ll learn how Nx uses executors and generators to make the developer experience more consistent across projects. We’ll then make our own executors and generators for processes that are unique to our organization. We’ll also explore the growing ecosystem of plugins that allow for the smooth integration of frameworks and libraries.