In this lesson, we explore the ins and outs of the Editor X content manager.
It has been the best investment I made in my design journey so far. I would consider myself a novice but I honestly feel like I've gained a genuine professional insight into the process of creating a high-level website.
I'm an early adopter of the KreativePro Masterclass, and I love how well put together it is. Neftali takes you through each step of the process from paper sketches to marketing all with fun visuals & clear instructions!
editor X database model consists of collections. Think of them as buckets. Within each bucket, you have rows or entries. And each of those are made of columns of fields. Fields can be texts, numbers, images, video, and even reference to other buckets. We'll want to start by identifying the purpose of our site.
What data will we need to store? And if we plan to collect data from our visitors, typically it's always a good idea to sketch some flows around our data architecture. In our stream VR sites, we will need to display dynamic pages for every movie and game. Each page will need to have its own URL for ranking on Google and it'll need to be published by certain roles.
Only. We'll probably want create a collection for the categories like action, adventure, et cetera. This way, our users can easily browse and filter by their preferences. Every movie or game we publish we'll need a set of fields like cover a trailer, a summary categories, and even a multi reference field for cast members.
Finally, I can imagine users leaving a review. Or a score. So we could create a bucket for handling reviews that get submitted by paid users. The possibilities are endless and editor X gives us a lot of power. All right, guys, in our workspace, you'll be able to access our content manager by clicking this tiny table icon with there are tools.
Let's just create a blank collection. We got prompt to write a collection name and what this collection is for. I really like this because we can decide what kind of superpowers or permissions this bucket will have. For example. Will it be basic data and public for anybody to see, or will it be data we collect from our users, but don't worry.
We'll get into more of this later. Let's just give this collection name featured content. This will be for that cool slider in the homepage. Okay. So the interface is pretty straightforward. We just made our first database class. If we start adding some of these rows, you'll see how familiar this is. Three simple Excel sheets.
If we create new columns or fields, we can set a field name to help us identify it in our table. Let's give this one, the name of summary. Notice how the field key mirrors that name, this field key is invisible, but it is used. If you want to later connect data through editor X API. It's important to note that if you change the field name later, This field key will remain the same.
So if you do plan on working with Velo or custom code, give it a unique identifier that won't need to change often. Editor X gives us a pretty nice this, the field types to choose from some of the ones that I personally like are the bullying, the video and the media gallery. And you also get rich text, which is great for formatting blog articles, where you need full control of heading titles, bullet lists, and quotes.
We have this toggle to encrypt data. You'll want to use this when you're storing sensitive data. If we click on this hidden field button, we can see that by default editor X cleans up our table by hiding nonessential fields like row ID creation, dates, and owner. These are known as system fields and are required in any relational database model.
Go ahead and turn them on when you think it's best. For example, running a blog or something similar where you need other contributors. All these other filters are just for this current admin view, like table list gallery view, sorting and filtering data. These filters and sorting will only affect your admin view.
We'll take a look at how to apply them in our published website. Confined find the lines. I want you to understand the importance of unique identifiers in our collections. For example, this collection has a little flag icon in our title column. This is the main field of this color. When we create reference fields to other collections, say for example, the cast members that dropped down, we'll always use the main field to bind it or connect to it.
We'll cover it this better in our next lessons. Oh, and before I forget, one of my favorite features is the ability to have a sandbox to play around with before going live. This is very common when running data across teams, where you're working on a series of new patients. But you'll need to preview or dress them out before going live.
We can activate this feature by heading to our content on a Jordache. And under more actions, click advanced settings. Let's go ahead and enable the sandbox test environment, just like that. Now, when we go into our collections, we can see this new pills to quickly see what's in our playground versus what it's life.
Once we're ready, we just hit the sink sandbox too. And boom. We've got ourselves a smooth and safe environment to manage our data. Okay. In our next lesson, I want to talk about how real data flows in our site. So let's jump in.
Access our premium community including bonus tutorials, project files & weekly resources.LIFETIME 💎 ACCESS