Content Modeling for React Developers

Rate this content

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 React developer.

7 min
23 Jun, 2022


Sign in or register to post your comment.

AI Generated Video Summary

Haushal, a Developer Advocate at Contentful, discusses content modeling and its importance in providing a great user experience. He uses his Cookbook web app as an example to explain how he structures and organizes content. The overall content model emphasizes reusability and considerations for content governance and platform selection. Content modeling is an iterative process, and Haushal provides resources for further learning and development.

1. Introduction and Background

Short description:

Hi everyone, I'm Haushal, a Developer Advocate at Contentful. I have been exploring Europe and experimenting with different technologies and frameworks. Check out my projects on my website or connect with me on Twitter.

Hi everyone and thank you for joining. In my lightning talk, my name is Haushal and I work at Contentful. As I was saying I am originally from India but I live in Berlin for 15 months. Still exploring Europe. Still exploring or still trying to be a more Berliner. And I work as a Developer Advocate at Contentful. I recently joined Contentful. And it has been an amazing experience because I get to experiment a lot with different technologies and framework. And share with the wider community and I kind of love doing that and I be a bit very build a lot of year projects so you can check it out on my website or just hit me up on Twitter.

2. Content Modeling and Cookbook Web App

Short description:

Today, I will discuss content modeling and its importance in providing a great user experience. I will use my Cookbook web app as an example to explain how I am structuring and organizing the content. Starting with wireframing, I identified the key elements for the recipe content type, including title, description, images, ingredients, and instructions. To ensure consistency, I created a separate content type for ingredients. Let's dive into the details.

All right so today I'm going to talk about content because in the past two years the amount of content that we have generated is massive. I mean everyone out there has created content in some form or another. In November last year during the Black Friday sale we saw a massive increase in the API request that we got at Contentful APIs. For example the GraphQL requests were increased by 550% while the content delivery API or CDA was increased by 73%. And so as a developer I believe it is on us to make sure that we provide that amazing experience not just to our users but to our team.

But how do we do that and what is content modeling. So basically a content model allows you to structure and organize your code. Now remember as you have the technical expertise but not all your content creators, all your designers would have that technical expertise. So we need to make sure that we provide that value and we provide that easy workflow for them to create content.

So that's quite enough of theory let's get into action and I want to talk today about Cookbook because I have taken cooking as a hobby recently and I'm trying to create a web app because I am a programmer and I believe I can do that. But anyways, so in the couple of next slides I'm going to talk about my approach of how I am modeling my content for this particular application. So I've taken the top-down approach so that I can break down the elements into smaller pieces into smaller chunks which would basically help me to reiterate my content model over and over again. So I started out with wireframing. I'm terrible at design. Don't judge me on the design but this is what I envision my web app to be. So a simple web app which shows a list of recipes and each of these cards basically have an image, a title and a description.

So this simple wireframework gave me an idea of what information I need in my content type. So in Contentful, this is what my content model looks like for the recipe content type. So now I have the title, I have the description and I have images. But we are missing two important things. If I open each or any of those recipes, it has a title, it has the images, it has the description but it needs to have those ingredients as well as the instructions on how to cook them. Otherwise no one knows how to cook their particular recipe and it's going to be just a mess. So with this page I kind of realized, OK, I have a few of these information but I need the ingredients as well as instructions. And that's what I went ahead and added in Contentful. So I added two other fields. One is ingredients and the other one is instructions. Now in ingredients, if you see it, it says its reference because ingredients are going to be shared among other recipes as well. Hence I created a separate content type for ingredients and I'm going to show you just that. So this is my ingredient content type and it has a name and a type. I know there's too many types going on in this talk so I'm just gonna try to avoid using that word.

3. Content Model Overview and Considerations

Short description:

This section explains the overall content model, highlighting the relationships between the recipe, ingredients, type, and assets. It emphasizes the importance of reusability in content modeling and the considerations for content governance and platform selection. It also mentions the iterative nature of content modeling and provides resources for further learning and development.

But this is how my ingredient content type looks like. And this is the overall content model, so the recipe has a reference to ingredients, ingredients has a reference to type, and recipe also has an ingredient to the assets which basically contains the images.

Now one of the other features that I kept in mind when I was building this content model was reusability, because as react developers we build on components and we want to make sure that we use those components again and again and we don't like to quote those lines of code again and again. And that's what I did over here. I knew I was gonna have ingredients for a lot of recipes which are going to be common and that's how I selected ingredients to be a separate content type.

The next is content governance. Now this is mainly important when you are working with your team and your team is going to be the one who is going to create the content, publish the content and review the content. This is where you have to decide on what kind of workflow or what kind of content governance do you want. Do you need to give access, do you need to give publish access to everyone and only a limited amount of people need to have that access. And the next is, and the next very important thing is platform, because you need to decide which platform this content is going to be used. Is it just going to be web, is it just going to be mobile, is it going to be both or is it also going to be a voice enabled application. So that is also one of the key factors that you need to keep in mind.

And remember, nobody gets content model right in one pass. I showed you the SCP content type that I created. It only had three fields earlier, but as and when I was creating and designing my wireframe, I realized I need to put in more and more fields over there to make more sense. So it's fine to have an incomplete content type at first, but get the feedback from your team, try to think more about it and then create your content type.

A few resources that I would like to share with you all, we have a Learning Center where we have trainings where you can learn more about Contentful and content modeling. And we have a developer portal where you can get all the developer resources, so if you just want to get started, the developer portal is the best place to go.

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