 Bonjour! Bonjour, mon nom est Michel Blume. I'm, again, switching to the wrong language. Sorry, my name is Michel Blume. I'm used to doing these in French and Montreal. So today, we're only going to be skimming the surface of how to prepare, think about our content that is not posts and not pages. Anything else would probably be something that we want to plan in advance and that we want to just think about to save time down the road, because any decision we make will impact many aspects of our projects. It's going to impact the wireframe aspect, it's going to impact the design, because all of these properties have to be applied and shown on the page itself. It's going to be impacting page templates because, as you can imagine, you probably want a special template to display the special data. It's going to affect all sorts of parts, including also thinking maybe of your web content people, the webmasters, because you want to make sure that it's easy for them to work and enter this data. And also, one of my roles is that the other than strong and italic, you should never have to write any HTML as a web content person. If not, it's that your back end has probably not been prepared accordingly to the project that you're working on. So what are we dealing with is the first thing you're going to be thinking about. It could be anything, because just to be clear, I'm talking about custom post types, but it's more of a concept than having to think about WordPress itself. This will apply to any web project, whether you're using WordPress or not. This is sort of the catalog of objects, of entities that you will be presenting. What is it? Is it a book? Is it a recipe? It doesn't have to be a physical object either. You could be selling e-books, tutorials, mp3s. It could be anything. So that would be sort of like our... Sorry, I'm not used to this microphone. It would be used, it would be like the base. Think of it as your archive pages. Think of it as the singles of books. Once we figure that out, what we're going to start thinking about is two main things. There are other considerations, but the two main things you want to think about is how are we going to sort this information and how are we going to filter it? Think about, again, just to take a random example, because I have not been thinking about books at all, how would we sort books? Do we care about sorting by ISBN number? Probably not, but we might be thinking about how to sort by author, but also by date of publication. If you were to enter this data into the, let's call it dumb content, not that it's dumb, it's that it's not useful for any queries. If you put it within a paragraph, it's going to be a horrible experience to try to sort it by that. So you want to think about, okay, let's make a special field just for our author. But once you do that, let's say I had three books, and my name is Michelle Bluma, chances are you don't want to sort by my first thing. So that's another consideration. How do we break down this information to make it easy to display, catalog, query, sort, and also filter? So you could go with Bluma, Michelle, but still chances are that it's going to be even easier down the road if you just break it down into two fields. So considerations that you might have about sorting. For filtering, again, just to take a random example, a book, you might want to filter by fiction, nonfiction, biographies. All of these are probably going to be set up as taxonomies, but how you do it is not really important today. It's just planning to do it because any of these steps might involve back-end code. And that one little bullet point in your project description when you're talking with your customer could end up being a 20-hour job, just a part of your project. And that's not something that's really fun to discover when you're at 65% completion and, of course, 95% budget. It's not really great to realize, oh, zut, I'm going to have to pay a subcontractor to do this, and it's going to really cut into my profit margin. So what we're going to start doing is just thinking about things. That's all. Today, that's all I'm talking about is thinking about anything. You can look around you. Anything that you're looking at is an object, an entity, and not to objectify anyone. It's really more that if you're looking at people and you see they're lanyards, you can just think to yourself, what is this? What is this lanyard? So it's a piece of cardboard. It is square. It's not really heavy. Most of these properties are uninteresting and useless. But some of them, mine is an X-Men one. I know you guys all seem to have a blue one. I don't know where you got yours. Those would be two products, and you would want to see how do I separate those, or how do I make it easy for the visitor to as quickly as possible get the information they have and do exactly what they need to get to that. As you can see, all sorts of examples. Some seem dumb. But the thing is when you're thinking about this, when you're in this process, don't try to be smart. What I mean by that is don't easily dismiss stuff. Earlier, I was talking about the ISBN number on a book. If you don't know, it's just a way to internationally catalog books, and I'm not going to say more, because I'm probably going to make a mistake. That is not useful for your visitor. It is honestly not useful for your designer, because they're just going to, even if you show it, it's just going to be a quick echo, and that's it. However, let's say that your customer is like, oh, you know what? I would really like to tie into Amazon's API for this. Well, the ISBN is probably a great unique identifier, and it won't have anything to do with your development or what you thought you needed to build a site. But tying into this external API might be two, five, 10, again, 20 hours of development time. Probably not 20, but just to give you an example of things that you don't think about necessarily in the beginning that might end up taking a lot of time and a lot of chunks of your budget. So that is the part about the little properties. Of course, this will also impact the web contents, the entry. I'm not going to go into how we enter this information, but as you can imagine, there are ways to make it a lot easier, again, for your web content person to enter them, classify them, and make it just pleasant for everyone. I was a little scared of running overboard over my time. I guess I'm not going to be, so this is going to go real quick. Just today, if you can, when you're walking around, like I was saying, just look at stuff and just try to think about it. And it'll seem like it's a futile, sort of boring thing to do, but after a while, all of this just comes too naturally, and it'll be super easy when you're planning, estimating, and preparing your project. I don't have a Q&A, but I... Hey. A random example, we have a book. Or rather, it would probably be a book publisher, so it would be a collection of books. This is a collection of things that we're talking about, right? So what is a book? Actually, I'll... Can anyone name properties of a book? Numbers of page, excellent. Paper. Language. Paper. Title. That is a very useful one, usually. Very good, very good. Un morceau de rebots. Which of these... You're publishing, and that is important, because we're probably going to want to look at books chronologically, and perhaps not the way you think. It might not be on the Show Us All Books page. It might be because you also entered authors as a piece of information. Maybe it takes on to me or a custom field. And on their page, you probably want to show their bibliography chronologically descending. I don't know if you've ever tried to sort information when it's like a random date within a piece of content. It's not going to happen. It's not going to work well. What you want is, first of all, a date entry field for your web master, or web content person. You will want to prepare queries. So that's for your back-end person. And all of this, if you prepare it, it's super quick to do. But not at the last minute when... We should have thought of that first. The paper or binding chances are that it's not really going to be useful. And I thought of those, and I thought, they're great, because sometimes, if you are a prestige publisher, if you're McSweeney's or something, you might want to present. But you probably won't be filtering by... I really would like a Stephen King novel, but only if it's on a beige stock. Otherwise, no. So all of this comes with... You just start realizing what is useful, what is not, and once you do that, you've planned it out. So as I was saying, I don't actually have a Q&A. But what I would like to offer you, though, is if ever you see me in the hallway track, which is anywhere here other than the three places, come see me. And if you want, we can just try to map something out on paper real quick, because, yes, the main tools you will need, I know, it's really expensive, but you will need a piece of paper and a pencil or pen. That's about it, because all of this is just done really free-flowing, but then all your meanings are going to be so much easier to get through. Does anyone have any questions? I will prepare a Q&A just for you. Any question at all? I know you're all waiting for Catherine. She always gives amazing talks. I get it. It's fine. I'm just the opening act. So, well, in that case, thank you very much. And really, I mean this. It's not just to be polite or something. Come see me. I'll gladly look at this stuff with you. Thank you very much.