[{"data":1,"prerenderedAt":433},["ShallowReactive",2],{"footer-primary":3,"footer-secondary":93,"footer-description":119,"digging-the-rabbit-hole-platform":121,"digging-the-rabbit-hole-platform-next":163,"sales-reps":182},{"items":4},[5,29,49,69],{"id":6,"title":7,"url":8,"page":8,"children":9},"522e608a-77b0-4333-820d-d4f44be2ade1","Solutions",null,[10,15,20,25],{"id":11,"title":12,"url":8,"page":13},"fcafe85a-a798-4710-9e7a-776fe413aae5","Headless CMS",{"permalink":14},"/solutions/headless-cms",{"id":16,"title":17,"url":8,"page":18},"79972923-93cf-4777-9e32-5c9b0315fc10","Backend-as-a-Service",{"permalink":19},"/solutions/backend-as-a-service",{"id":21,"title":22,"url":8,"page":23},"0fa8d0c1-7b64-4f6f-939d-d7fdb99fc407","Product Information",{"permalink":24},"/solutions/product-information-management",{"id":26,"title":27,"url":28,"page":8},"63946d54-6052-4780-8ff4-91f5a9931dcc","100+ Things to Build","https://directus.io/blog/100-tools-apps-and-platforms-you-can-build-with-directus",{"id":30,"title":31,"url":8,"page":8,"children":32},"8ab4f9b1-f3e2-44d6-919b-011d91fe072f","Resources",[33,37,41,45],{"id":34,"title":35,"url":36,"page":8},"f951fb84-8777-4b84-9e91-996fe9d25483","Documentation","https://docs.directus.io",{"id":38,"title":39,"url":40,"page":8},"366febc7-a538-4c08-a326-e6204957f1e3","Guides","https://docs.directus.io/guides/",{"id":42,"title":43,"url":44,"page":8},"aeb9128e-1c5f-417f-863c-2449416433cd","Community","https://directus.chat",{"id":46,"title":47,"url":48,"page":8},"da1c2ed8-0a77-49b0-a903-49c56cb07de5","Release Notes","https://github.com/directus/directus/releases",{"id":50,"title":51,"url":8,"page":8,"children":52},"d61fae8c-7502-494a-822f-19ecff3d0256","Support",[53,57,61,65],{"id":54,"title":55,"url":56,"page":8},"8c43c781-7ebd-475f-a931-747e293c0a88","Issue Tracker","https://github.com/directus/directus/issues",{"id":58,"title":59,"url":60,"page":8},"d77bb78e-cf7b-4e01-932a-514414ba49d3","Feature Requests","https://github.com/directus/directus/discussions?discussions_q=is:open+sort:top",{"id":62,"title":63,"url":64,"page":8},"4346be2b-2c53-476e-b53b-becacec626a6","Community Chat","https://discord.com/channels/725371605378924594/741317677397704757",{"id":66,"title":67,"url":68,"page":8},"26c115d2-49f7-4edc-935e-d37d427fb89d","Cloud Dashboard","https://directus.cloud",{"id":70,"title":71,"url":8,"page":8,"children":72},"49141403-4f20-44ac-8453-25ace1265812","Organization",[73,78,84,88],{"id":74,"title":75,"url":76,"page":77},"1f36ea92-8a5e-47c8-914c-9822a8b9538a","About","/about",{"permalink":76},{"id":79,"title":80,"url":81,"page":82},"b84bf525-5471-4b14-a93c-225f6c386005","Careers","#",{"permalink":83},"/careers",{"id":85,"title":86,"url":87,"page":8},"86aabc3a-433d-434b-9efa-ad1d34be0a34","Brand Assets","https://drive.google.com/drive/folders/1lBOTba4RaA5ikqOn8Ewo4RYzD0XcymG9?usp=sharing",{"id":89,"title":90,"url":8,"page":91},"8d2fa1e3-198e-4405-81e1-2ceb858bc237","Contact",{"permalink":92},"/contact",{"items":94},[95,101,107,113],{"id":96,"title":97,"url":8,"page":98,"children":100},"8a1b7bfa-429d-4ffc-a650-2a5fdcf356da","Cloud Policies",{"permalink":99},"/cloud-policies",[],{"id":102,"title":103,"url":81,"page":104,"children":106},"bea848ef-828f-4306-8017-6b00ec5d4a0c","License",{"permalink":105},"/bsl",[],{"id":108,"title":109,"url":81,"page":110,"children":112},"4e914f47-4bee-42b7-b445-3119ee4196ef","Terms",{"permalink":111},"/terms",[],{"id":114,"title":115,"url":81,"page":116,"children":118},"ea69eda6-d317-4981-8421-fcabb1826bfd","Privacy",{"permalink":117},"/privacy",[],{"description":120},"\u003Cp>A composable backend to build your Headless CMS, BaaS, and more. \u003C/p>",{"id":122,"slug":123,"vimeo_id":124,"description":125,"tile":126,"length":127,"resources":8,"people":128,"episode_number":132,"published":133,"title":134,"video_transcript_html":135,"video_transcript_text":136,"content":8,"status":137,"episode_people":138,"recommendations":149,"season":150,"seo":8},"3262bf03-ab28-45e1-a824-c0418b29927a","platform","917617587","In this episode, Kevin walks through the code and backend of Directus TV.","d4b0a23c-8836-4bd4-89d8-ca82ea1654d5",10,[129],{"name":130,"url":131},"Kevin Lewis","https://directus.io/team/kevin-lewis",4,"2024-03-04","The Platform","\u003Cp>Speaker 0: Hello, and welcome back to Digging the Rabbit Hole. In this episode, I'm gonna run through the codebase and the Director's project, which powers Directus TV to give you a little bit of an insight in how we use Directus at Directus to deliver Directus TV. Now before we jump into code and the Directus project, I basically wanna take some time to show you what I would call the 3 main pages of Directus TV. Firstly, we have this home page here. In the home page, we have this big global featured item here with a couple of buttons, and we also have these category sliders.\u003C/p>\u003Cp>Categories contain shows, and inside of shows, we have this show page. This is the 2nd page. This is an individual show listing. So here in trace talks, we have some information about the show. We have a button to play the latest episode, and then we have a listing of episodes.\u003C/p>\u003Cp>You'll also notice there are seasons. So seasons exist in the data model. A good one to demonstrate that is actually around the world here because we have 2 seasons. So here we have season 1, 2023, and we have season 2, 2024. Now the 3rd page, if we step into one of these, is the actual episode page.\u003C/p>\u003Cp>So in here, we have a video embed, which we'll talk about in a moment. We have a back to show button, a next episode button, which we'll talk about also, metadata about both the show and the episode, and a list of people, and a list of resources, and they both conditionally are shown or hidden depending on where the data exists there. So that's a little bit of a rundown of these pages. We have a home page. We have a show page.\u003C/p>\u003Cp>We have an episode page. Now let's look at the directors data model that powers this, and it's very, very similar to the pages. Firstly, we have shows. Each one of these is a different show, director scene scapes, quick connect, I made this, 100 apps in a 100 hours, and so on. Individual shows have a slug.\u003C/p>\u003Cp>This dictates the URL for that show. The title, a little one liner, which is what is actually shown here on the home page so people know what to expect from this show. A description, and then these three graphics. So we have a tile, a logo, and a cover. To show you how they relate here, if I go into a 100 apps in a 100 hours, we have the logo, we have the background here, and then we have the tile, which is, this view here.\u003C/p>\u003Cp>That's the tile. So we have the tile, the logo, and the cover. Next, we have seasons. Seasons are almost like a junction collection really. Every show has seasons.\u003C/p>\u003Cp>A season is just a show, a number, and a year. And then we have episodes. I've pre filtered this down here just to make sure that we're not getting a huge, huge list of shows, but just a manageable number here. So each individual episode, these are all the episodes of season 1 of Quick Connect, have a published date. This is useful for both displaying in the website, but also for RSS feeds.\u003C/p>\u003Cp>The status, because, of course, we upload all of these in bulk, and then we just change the status and the publish date and re rebuild the site on the day of publishing. Season and episode number, the slug for the URL and the title, the Vimeo ID, which again, we'll talk about in just a moment, a tile description, people, and resources. The tile is, if I go into quick connect, is this this here, each individual tile. And having tiles is useful, of course, for generating social tags, social meta tags. So that's a little rundown.\u003C/p>\u003Cp>Now before we continue, let's quickly talk about Vimeo. We use Vimeo to host our video for a number of reasons, primarily because they have a really good player that works cross platform and also will adapt to the needs of the viewer. If you have less, you know, less bandwidth, it will drop the quality of the video that you get delivered. And to be frank, I just didn't wanna build that. So it's good to lean on other platforms as appropriate.\u003C/p>\u003Cp>Finally, we have categories. These are for the homepage. So these are those sliders of categories. It just has a status, a title, and shows that can be sorted, and these can also be sorted which change the order of the categories and the order of the shows within a category. That's a little bit of a rundown of the director's project.\u003C/p>\u003Cp>Let's do a little rundown of the code now, and hopefully, it should all look reasonably, you know, reasonably sensible given the concepts that we've spoken about so far. So here we have the home page. In a home page, we have a hero. That's that top kind of graphic unit with the featured item, And this grabs data from the global's collection in director, so I didn't show that. Here is the global's collection, and there is a featured item there.\u003C/p>\u003Cp>So that populates the TV hero. And we also have the TV category, which lists all of the categories. Now this is a custom component here inside of TV. We have custom category, which are the sliders. We have the, the show, which are the individual tiles.\u003C/p>\u003Cp>We have the navigation, which goes in the hero. That's a separate item because on the on the actual episode page, it's not nested within the, within the hero, but on the other pages that is nested in the hero. So it's a it's a separate element. That's the hero. Then we have the individual episodes.\u003C/p>\u003Cp>This is for the show listing page with the horizontal I'll show you. With these, that is a TV show here. We use that in a few places. And so they kind of cascade. So on the home page here, we have the categories.\u003C/p>\u003Cp>The categories render the shows. Then over in an individual show page here, we have the hero unit once again. And then we have all of the oh, I'm I'm in the wrong section here. This is where I wanna be. We have the hero, and then we have, each of the seasons being looped over.\u003C/p>\u003Cp>And inside of that, we have each episode. Once again, we're just using directors. So we're grabbing the we're grabbing the show. We're grabbing the latest episode because that's the button here. So it's play latest episodes.\u003C/p>\u003Cp>So we wanna know what that is. We grab all the episodes. We grab all the seasons, and we jam those together here to create our data model. And once again, we just have some SEO meta tags here. In the individual episode page, it pins mostly on this iframe, of course, but we do have this additional data.\u003C/p>\u003Cp>We have back to show, and we also have what's coming up next. Now this is interesting. So the bottom will either say next season or next episode. It will say next season if it's the last episode in a season, or it will say next episode if there is another episode in this season that we're in now. We also just render all of the kind of static information for that episode.\u003C/p>\u003Cp>Looking down at the code here, we grab the episode data here based on whatever is in the URL, and we grab the next item. So the next item will firstly always be of this show. You know, if we're in a 100 apps in a 100 hours, we wanna return an episode of a 100 apps in a 100 hours. And either there will be, an episode in this season, but one episode up, or there won't be because we'll be in the last episode of a season. And in that case, we will want to get one season up and episode number 1.\u003C/p>\u003Cp>Right? And so next, we'll either end up with the next episode, the first episode of the next season, or nothing. And we can conditionally show that next button and what it says based on what is returned. That's a pretty cool use of directors' filter syntax there. And then just a little date for matter.\u003C/p>\u003Cp>Once again, just some just some SEO meta tags. So that's really Directus TV. Pretty, like, straightforward data model. The only thing I would perhaps do differently on reflection is I wouldn't, hard code people. I wouldn't hard code people here into each episode, but I would make that a relational collection.\u003C/p>\u003Cp>But that's fine. We can always enhance that in future. Because I wanna show you stuff that's relevant to everyone, we won't dig into Directus TV live today. But that is a a breakdown of how Directus TV works, both in terms of the mental models and the concepts of shows, seasons, episodes, and categories, how they relate to a data model and how they relate to a code base. So I hope you found this interesting, and we'll see you in the next episode.\u003C/p>","Hello, and welcome back to Digging the Rabbit Hole. In this episode, I'm gonna run through the codebase and the Director's project, which powers Directus TV to give you a little bit of an insight in how we use Directus at Directus to deliver Directus TV. Now before we jump into code and the Directus project, I basically wanna take some time to show you what I would call the 3 main pages of Directus TV. Firstly, we have this home page here. In the home page, we have this big global featured item here with a couple of buttons, and we also have these category sliders. Categories contain shows, and inside of shows, we have this show page. This is the 2nd page. This is an individual show listing. So here in trace talks, we have some information about the show. We have a button to play the latest episode, and then we have a listing of episodes. You'll also notice there are seasons. So seasons exist in the data model. A good one to demonstrate that is actually around the world here because we have 2 seasons. So here we have season 1, 2023, and we have season 2, 2024. Now the 3rd page, if we step into one of these, is the actual episode page. So in here, we have a video embed, which we'll talk about in a moment. We have a back to show button, a next episode button, which we'll talk about also, metadata about both the show and the episode, and a list of people, and a list of resources, and they both conditionally are shown or hidden depending on where the data exists there. So that's a little bit of a rundown of these pages. We have a home page. We have a show page. We have an episode page. Now let's look at the directors data model that powers this, and it's very, very similar to the pages. Firstly, we have shows. Each one of these is a different show, director scene scapes, quick connect, I made this, 100 apps in a 100 hours, and so on. Individual shows have a slug. This dictates the URL for that show. The title, a little one liner, which is what is actually shown here on the home page so people know what to expect from this show. A description, and then these three graphics. So we have a tile, a logo, and a cover. To show you how they relate here, if I go into a 100 apps in a 100 hours, we have the logo, we have the background here, and then we have the tile, which is, this view here. That's the tile. So we have the tile, the logo, and the cover. Next, we have seasons. Seasons are almost like a junction collection really. Every show has seasons. A season is just a show, a number, and a year. And then we have episodes. I've pre filtered this down here just to make sure that we're not getting a huge, huge list of shows, but just a manageable number here. So each individual episode, these are all the episodes of season 1 of Quick Connect, have a published date. This is useful for both displaying in the website, but also for RSS feeds. The status, because, of course, we upload all of these in bulk, and then we just change the status and the publish date and re rebuild the site on the day of publishing. Season and episode number, the slug for the URL and the title, the Vimeo ID, which again, we'll talk about in just a moment, a tile description, people, and resources. The tile is, if I go into quick connect, is this this here, each individual tile. And having tiles is useful, of course, for generating social tags, social meta tags. So that's a little rundown. Now before we continue, let's quickly talk about Vimeo. We use Vimeo to host our video for a number of reasons, primarily because they have a really good player that works cross platform and also will adapt to the needs of the viewer. If you have less, you know, less bandwidth, it will drop the quality of the video that you get delivered. And to be frank, I just didn't wanna build that. So it's good to lean on other platforms as appropriate. Finally, we have categories. These are for the homepage. So these are those sliders of categories. It just has a status, a title, and shows that can be sorted, and these can also be sorted which change the order of the categories and the order of the shows within a category. That's a little bit of a rundown of the director's project. Let's do a little rundown of the code now, and hopefully, it should all look reasonably, you know, reasonably sensible given the concepts that we've spoken about so far. So here we have the home page. In a home page, we have a hero. That's that top kind of graphic unit with the featured item, And this grabs data from the global's collection in director, so I didn't show that. Here is the global's collection, and there is a featured item there. So that populates the TV hero. And we also have the TV category, which lists all of the categories. Now this is a custom component here inside of TV. We have custom category, which are the sliders. We have the, the show, which are the individual tiles. We have the navigation, which goes in the hero. That's a separate item because on the on the actual episode page, it's not nested within the, within the hero, but on the other pages that is nested in the hero. So it's a it's a separate element. That's the hero. Then we have the individual episodes. This is for the show listing page with the horizontal I'll show you. With these, that is a TV show here. We use that in a few places. And so they kind of cascade. So on the home page here, we have the categories. The categories render the shows. Then over in an individual show page here, we have the hero unit once again. And then we have all of the oh, I'm I'm in the wrong section here. This is where I wanna be. We have the hero, and then we have, each of the seasons being looped over. And inside of that, we have each episode. Once again, we're just using directors. So we're grabbing the we're grabbing the show. We're grabbing the latest episode because that's the button here. So it's play latest episodes. So we wanna know what that is. We grab all the episodes. We grab all the seasons, and we jam those together here to create our data model. And once again, we just have some SEO meta tags here. In the individual episode page, it pins mostly on this iframe, of course, but we do have this additional data. We have back to show, and we also have what's coming up next. Now this is interesting. So the bottom will either say next season or next episode. It will say next season if it's the last episode in a season, or it will say next episode if there is another episode in this season that we're in now. We also just render all of the kind of static information for that episode. Looking down at the code here, we grab the episode data here based on whatever is in the URL, and we grab the next item. So the next item will firstly always be of this show. You know, if we're in a 100 apps in a 100 hours, we wanna return an episode of a 100 apps in a 100 hours. And either there will be, an episode in this season, but one episode up, or there won't be because we'll be in the last episode of a season. And in that case, we will want to get one season up and episode number 1. Right? And so next, we'll either end up with the next episode, the first episode of the next season, or nothing. And we can conditionally show that next button and what it says based on what is returned. That's a pretty cool use of directors' filter syntax there. And then just a little date for matter. Once again, just some just some SEO meta tags. So that's really Directus TV. Pretty, like, straightforward data model. The only thing I would perhaps do differently on reflection is I wouldn't, hard code people. I wouldn't hard code people here into each episode, but I would make that a relational collection. But that's fine. We can always enhance that in future. Because I wanna show you stuff that's relevant to everyone, we won't dig into Directus TV live today. But that is a a breakdown of how Directus TV works, both in terms of the mental models and the concepts of shows, seasons, episodes, and categories, how they relate to a data model and how they relate to a code base. So I hope you found this interesting, and we'll see you in the next episode.","published",[139],{"people_id":140},{"id":141,"first_name":142,"last_name":143,"avatar":144,"bio":145,"links":146},"82b3f7e5-637b-4890-93b2-378b497d5dc6","Kevin","Lewis","a662f91b-1ee9-4277-8c9d-3ac1878e44ad","Director of Developer Experience at Directus",[147],{"url":131,"service":148},"website",[],{"id":151,"number":152,"year":153,"episodes":154,"show":160},"5a656532-6f30-42e9-9a11-24b0b9041642",1,"2024",[155,156,157,122,158,159],"30a30326-0bd0-4a40-b680-8c652f58a746","4aa1ba58-7820-40a4-9196-5e186be53f3a","8fc804e1-786d-4a14-bddd-74d2785b20a6","8fdf7563-f9e4-4321-ae64-d009b0fddfaf","1db8f535-b44b-4b5d-9937-a922ae7560db",{"title":161,"tile":162},"Digging the Rabbit Hole","19c63cdb-35e3-457f-97fd-653500c9eff7",{"id":158,"slug":164,"season":151,"vimeo_id":165,"description":166,"tile":167,"length":168,"resources":8,"people":169,"episode_number":174,"published":133,"title":175,"video_transcript_html":176,"video_transcript_text":177,"content":8,"seo":8,"status":137,"episode_people":178,"recommendations":181},"reception","917614369","In this episode, John and Kevin discuss the early feedback and reception to Directus TV and it's shows.","743f964d-41fa-4dda-8e09-0750c92cadca",14,[170,171],{"name":130,"url":131},{"name":172,"url":173},"John Daniels","https://directus.io/team/john-daniels",5,"The Reception","\u003Cp>Speaker 0: Hello, and welcome to the final episode of digging the rabbit hole. This is a series that is born out of getting a lot of questions about how this has all come together. And today, John is joining me, to talk about some initial feedback we got. John, would you like to introduce yourself?\u003C/p>\u003Cp>Speaker 1: Yeah. Thanks, Kevin. Glad to be part of the series. John Daniels, one of the team members here at Directus. Been here for about 2 years, so it's exciting to see where Directus was when we started to now where we are with, Directus TV and where we are with the platform.\u003C/p>\u003Cp>Speaker 0: Awesome. And, of course, you're you're part of our field team, I suppose, is one way to frame it.\u003C/p>\u003Cp>Speaker 1: Yeah. Definitely part of the field team. I help teach about Directus, you know, work with our enterprise customers, kind of everything.\u003C/p>\u003Cp>Speaker 0: Excellent. And so Directus TV has now existed for a couple of months. And you obviously are, you know, in the same way that as developer relations person, I mean, with the community, in my Discord and our GitHub, you're in with customers and enterprise users of directors. And I just thought we could use this last episode to be a little bit reflective perhaps about some of the early feedback that we've got about the platform.\u003C/p>\u003Cp>Speaker 1: Yeah. Yeah. Yeah. Some, yeah, some of the early feedback has been great. My most favorite piece of feedback is when I hop on a a call with somebody I've never met before, and they say, hey.\u003C/p>\u003Cp>I've seen your face before on videos. So that's always pretty fun. It makes me feel more important than I am, but that's some good feedback, which means it it does let me know that people are watching the videos, which is cool, especially because the videos that I'm in are a little bit more nondirectus focused, and it means they're just watching our content. So that's been some of the feedback that I enjoy, but also feedback more so around Directus TV in general has been it's been it's been widely popular at least from the people that I'm talking to. People talk about all the different types of series that are on there.\u003C/p>\u003Cp>They do appreciate the Direct us focused ones and the non direct us focused ones. But they really love the fact that the ones that are focused on direct us kind of showcase the the flexibility of the platform. Yeah. That's always that's always been one of our problems is you can do so much with Directus, and and, you know, how do you show all of that? And so I think a series like 100 apps, 100 hours is really beneficial both for people who are starting to explore Directus, but also for me as I'm talking to these people.\u003C/p>\u003Cp>Because because I'll talk to people who are trying to build an Airbnb clone or trying to build a swag platform. And so it's great for me. If they haven't seen it, I'll send it to them and they'll they love it because it's typically right up their alley. But a lot of times, they'll come in having seen those episodes. And so feedback in general has been fantastic.\u003C/p>\u003Cp>People love the entertaining value of it because it's not just a bunch of people, you know, training and being kind of boring. That's not who we are. And it's also making me famous, which is really awesome.\u003C/p>\u003Cp>Speaker 0: Well, there we go. There we go. You know, it's interesting you mentioned a 100 apps, 100 hours. You know, I would say and and we've alluded to this in episodes before this. That's probably been our series that's also had the most criticism, and it's pretty clear what the criticism is and where it comes from.\u003C/p>\u003Cp>And it comes from not meeting people's expectations with what they are or what they're expecting to see. They're expecting Right. Like purely educational, instructional, best practice driven content because that is what companies do. Right? That is what companies do when they're trying to educate people in creating content around their product.\u003C/p>\u003Cp>That isn't the goal of a 100 apps in a 100 hours. It is Yeah. It is an entertainment show where we watch Brian sweat for 60 minutes, try and figure it out against the clock. There may sometimes not be best practices being honored. I mean, certainly isn't instructional.\u003C/p>\u003Cp>And that's interesting. Maybe it's a sign that actually there's a demand for, you know, instructional content around building out use cases. But, yeah, it's just interesting that that isn't quite people aren't quite understanding that even having watched a fair amount of the video itself.\u003C/p>\u003Cp>Speaker 1: Yeah. That's actually a really good that's a fair point, I think. Whereas the the people I'm talking to, they're looking for a platform they can use to build these platforms or build their products. Mhmm. And so they're really just looking to see if Directus can do that.\u003C/p>\u003Cp>And so the people that I'm talking to are coming to coming to us watching these videos saying, can Directus do this? And we say, hey. We've, you know, we've built this really tiny version of this app in an hour. Mhmm.\u003C/p>\u003Cp>Speaker 0: And\u003C/p>\u003Cp>Speaker 1: so I I guess the people that I'm talking to just wanna see that that's something that people do in Directus. So they can see that someone's trying to build a this clone or whatever. So, but I can totally understand where people want to actually then dive deeper and understand what is the step by steps that I need\u003C/p>\u003Cp>Speaker 0: Yeah.\u003C/p>\u003Cp>Speaker 1: To build an Airbnb clone. But if you look at something like that, that would be a whole series in itself, just building one of those clones the proper way. I mean, there's it took Airbnb, you know, 6 months probably to to develop a prototype. And so that would be a lot more than a a 60 minute session. But that that's I totally understand that where typical people would be or people who know Directus want to then dive deeper into actually doing that work.\u003C/p>\u003Cp>Speaker 0: And I suppose there's 2 outcomes there in terms of future content. One of them is, yes. Okay. We will build out these use cases, you know, and and help you build them as well. I fear, you know, considering the first season of a 100 apps in a 100 hours is 10 episodes.\u003C/p>\u003Cp>That's effectively 10 series worth of content and we're just not equipped to to do that realistically. The other side is, and this is a series that we're planning, you know, and I think it's a pretty, pretty natural thing to create, which is a set of short demos where directors is being used well as these use cases. So maybe there's something where, well, historically, we haven't had that much use case based content. Now we have something but it is almost it has this baggage of being this entertainment show where that might not be where people are expecting, expecting it to go. So maybe there's a strict back version, which is just and here's the endpoint maybe.\u003C/p>\u003Cp>Yeah. Yeah. That's certainly interesting.\u003C/p>\u003Cp>Speaker 1: Yeah. I mean, obviously, any technology needs the the actual training on the product. And so I'd love to see us get to that point where we do release these hey. Build a build a very simple CMS in 5 minutes, or here's direct us in 5 minutes, and here's direct us in 30 minutes. I'd love to even see a certification training program eventually, but, obviously, with a smaller team that that takes a whole different workload there too.\u003C/p>\u003Cp>But I think over time, we'll add more and more much like our YouTube videos were back in the day focused on Directus and how to use Directus. We'll bring that content back into Directus TV because it's it's what we wanna do and it's what people are asking\u003C/p>\u003Cp>Speaker 0: for as well. Absolutely. And, you know, some of what you're describing is in the works as well in various guises. But, yeah, more instructional, more walk through content, more use case driven inspiration as Brian called it in a previous episode, less instruction, maybe inspiration would be a better word. Yeah.\u003C/p>\u003Cp>Interesting. I agree, though. From my side, the feedback generally has been pretty good. You know, not every and here's the thing, not every season, not every series has to be for everyone. So, you know, we have a lot of interview based content.\u003C/p>\u003Cp>Some people are just not interested in the interview format. That's totally cool. Some people just want instruction. Some people want effectively demos in some form or another, whether it's the whole, you know, the whole platform, whether it's discrete parts of the platform or whether it's use cases or case studies or things like that. And some people wanna be entertained.\u003C/p>\u003Cp>And the lovely thing about this platform we've got is we don't have to double down on any one of those. We just need to always have our eye on making sure the ratios are right. And we also spoke about this in an earlier episode. I don't believe the ratio is right today. The byproduct of this whole platform having come about in 6 weeks is that there was a lot more interview content created and less instructional content because one is easier to make than the other.\u003C/p>\u003Cp>But we're addressing that, we're addressing that. There are a lot of shows, There are a lot of shows in the works. The day this releases, we announce our spring slate, but we're already working on the summer and the full slate of content as well, which is really exciting.\u003C/p>\u003Cp>Speaker 1: Yeah. I mean, people just want less John and and more instructions, and I totally get that. You know? There's There's only so much Why\u003C/p>\u003Cp>Speaker 0: not instruction from John?\u003C/p>\u003Cp>Speaker 1: Yeah. That'd be kind of interesting because I'm on the the I'm on the side of the house that's kind of I always tell people I'm middle level technical. Like, I understand how to use direct us, but I'm not gonna go and build that Airbnb clone. So that would actually probably be an interesting series, honestly, is watch a middle level technical person build an Airbnb clone or something like that. So that would probably be entertaining.\u003C/p>\u003Cp>Speaker 0: There actually was there is a series pitch with this vibe, but it is, it's Matt Matt who isn't a developer. It's definitely I think we're all everyone who works with directors is quite technically minded. Like, we are technical problem solvers. The amount of code with which we can do that with varies from individual to individual and team to team. But, yeah, that's a really interesting format too.\u003C/p>\u003Cp>But, yeah, there there's so much. Have you, you know, have you got any other the answer can be no, but has there been any other kind of top line feedback that you've got that could be interesting? Yeah.\u003C/p>\u003Cp>Speaker 1: I think, I think the top line feedback is exactly what you just mentioned. Not every show is for every person. I mean, even myself, I I try and watch every episode of everything that comes out, but there's there's certainly some series that I tend to gravitate towards. So I think that's the good feedback is, not every not every series is for every person, but every person can try and find a series that that fits for them or that they enjoy. So that's one of the pieces of feedback.\u003C/p>\u003Cp>Obviously, I haven't heard necessarily too much of the I need to dive deeper into these topics, but I'm talking to people who are traditionally newer to direct us. But I can understand that feedback. But then in general, people are watching it, and they're they're glad that we have it. They're glad that we have this content platform, both for the entertainment value, but also for the educational value in the hey. You know, Directus can do what I think it can do, and I can see a really quick video about that.\u003C/p>\u003Cp>So I think the feedback in general has just been that people enjoy the fact that we have it and the fact that there's something that they can find,\u003C/p>\u003Cp>Speaker 0: you\u003C/p>\u003Cp>Speaker 1: know, value in, whether it's a couple series or one series or there's probably a few people out there who watch every series. So I think the feedback in general has been great. And it's been great for me when again, just to reiterate, when people come and and start to learn about Directus to just point them to a video. You know? Just be like, go watch this series.\u003C/p>\u003Cp>Go watch this episode. You know, it's fantastic. So that's been great for me too.\u003C/p>\u003Cp>Speaker 0: And as an educator, the person who looks after our docs or lead leading the team who look after our docs, it's very much the same the same there as well, which is the more content we can create that's valuable and solves people's problems, the more reference material we have when that content can help people and the less time we can spend doing the almost, like, repetitive education, right, because we have collateral to back it up. And, yeah, director's TV definitely plays an important part of that. In terms of feedback also, you know, we we track some basic metrics, simple things, what gets watched, how long of each thing gets watched, do people watch stuff and then end up elsewhere on our website, and does that turn into results for us? Absolutely. As part of having our own media platform is that we we know.\u003C/p>\u003Cp>You know, we we can build build in that analytics and tweak that for our own purposes. There is currently an issue on the GitHub repo for the website to implement a feedback widget like on our documentation so we can get a more rich feedback about how people are finding individual shows and episodes, but that's that's later. For now it's just what's being watched, for how long, does it turn into some form of outcome, and of course the fact that we can use it to help educate people, or inspire them or entertain them or to build relationships and highlight community stories.\u003C/p>\u003Cp>Speaker 1: Yeah. Yeah. No. I think it's been great. And and there's even things on there like scenescapes, which I think we only have 2 of right now.\u003C/p>\u003Cp>But even though one of the scenes is outside of my window, I'll even put it on sometimes. Or when I'm traveling, I'll put it on and just listen to music and play. So I think, again, the fact that there's we're trying to create series for everybody and for all types of things is awesome.\u003C/p>\u003Cp>Speaker 0: Yeah. And, of course, the other scene scapes is here in Berlin with me. Yeah. Really fun. Thank you so much, John, for joining joining me, and thanks for tuning in to Digging the Rabbit Hole.\u003C/p>\u003Cp>We hope you found this series insightful. We may well we may well renew it for another season when there's interesting developments. But for now, thank you very much. Enjoy all the other content we have here on directors TV and I'll see you we'll see you in our respective next video hosts.\u003C/p>\u003Cp>Speaker 1: Thanks, everyone.\u003C/p>","Hello, and welcome to the final episode of digging the rabbit hole. This is a series that is born out of getting a lot of questions about how this has all come together. And today, John is joining me, to talk about some initial feedback we got. John, would you like to introduce yourself? Yeah. Thanks, Kevin. Glad to be part of the series. John Daniels, one of the team members here at Directus. Been here for about 2 years, so it's exciting to see where Directus was when we started to now where we are with, Directus TV and where we are with the platform. Awesome. And, of course, you're you're part of our field team, I suppose, is one way to frame it. Yeah. Definitely part of the field team. I help teach about Directus, you know, work with our enterprise customers, kind of everything. Excellent. And so Directus TV has now existed for a couple of months. And you obviously are, you know, in the same way that as developer relations person, I mean, with the community, in my Discord and our GitHub, you're in with customers and enterprise users of directors. And I just thought we could use this last episode to be a little bit reflective perhaps about some of the early feedback that we've got about the platform. Yeah. Yeah. Yeah. Some, yeah, some of the early feedback has been great. My most favorite piece of feedback is when I hop on a a call with somebody I've never met before, and they say, hey. I've seen your face before on videos. So that's always pretty fun. It makes me feel more important than I am, but that's some good feedback, which means it it does let me know that people are watching the videos, which is cool, especially because the videos that I'm in are a little bit more nondirectus focused, and it means they're just watching our content. So that's been some of the feedback that I enjoy, but also feedback more so around Directus TV in general has been it's been it's been widely popular at least from the people that I'm talking to. People talk about all the different types of series that are on there. They do appreciate the Direct us focused ones and the non direct us focused ones. But they really love the fact that the ones that are focused on direct us kind of showcase the the flexibility of the platform. Yeah. That's always that's always been one of our problems is you can do so much with Directus, and and, you know, how do you show all of that? And so I think a series like 100 apps, 100 hours is really beneficial both for people who are starting to explore Directus, but also for me as I'm talking to these people. Because because I'll talk to people who are trying to build an Airbnb clone or trying to build a swag platform. And so it's great for me. If they haven't seen it, I'll send it to them and they'll they love it because it's typically right up their alley. But a lot of times, they'll come in having seen those episodes. And so feedback in general has been fantastic. People love the entertaining value of it because it's not just a bunch of people, you know, training and being kind of boring. That's not who we are. And it's also making me famous, which is really awesome. Well, there we go. There we go. You know, it's interesting you mentioned a 100 apps, 100 hours. You know, I would say and and we've alluded to this in episodes before this. That's probably been our series that's also had the most criticism, and it's pretty clear what the criticism is and where it comes from. And it comes from not meeting people's expectations with what they are or what they're expecting to see. They're expecting Right. Like purely educational, instructional, best practice driven content because that is what companies do. Right? That is what companies do when they're trying to educate people in creating content around their product. That isn't the goal of a 100 apps in a 100 hours. It is Yeah. It is an entertainment show where we watch Brian sweat for 60 minutes, try and figure it out against the clock. There may sometimes not be best practices being honored. I mean, certainly isn't instructional. And that's interesting. Maybe it's a sign that actually there's a demand for, you know, instructional content around building out use cases. But, yeah, it's just interesting that that isn't quite people aren't quite understanding that even having watched a fair amount of the video itself. Yeah. That's actually a really good that's a fair point, I think. Whereas the the people I'm talking to, they're looking for a platform they can use to build these platforms or build their products. Mhmm. And so they're really just looking to see if Directus can do that. And so the people that I'm talking to are coming to coming to us watching these videos saying, can Directus do this? And we say, hey. We've, you know, we've built this really tiny version of this app in an hour. Mhmm. And so I I guess the people that I'm talking to just wanna see that that's something that people do in Directus. So they can see that someone's trying to build a this clone or whatever. So, but I can totally understand where people want to actually then dive deeper and understand what is the step by steps that I need Yeah. To build an Airbnb clone. But if you look at something like that, that would be a whole series in itself, just building one of those clones the proper way. I mean, there's it took Airbnb, you know, 6 months probably to to develop a prototype. And so that would be a lot more than a a 60 minute session. But that that's I totally understand that where typical people would be or people who know Directus want to then dive deeper into actually doing that work. And I suppose there's 2 outcomes there in terms of future content. One of them is, yes. Okay. We will build out these use cases, you know, and and help you build them as well. I fear, you know, considering the first season of a 100 apps in a 100 hours is 10 episodes. That's effectively 10 series worth of content and we're just not equipped to to do that realistically. The other side is, and this is a series that we're planning, you know, and I think it's a pretty, pretty natural thing to create, which is a set of short demos where directors is being used well as these use cases. So maybe there's something where, well, historically, we haven't had that much use case based content. Now we have something but it is almost it has this baggage of being this entertainment show where that might not be where people are expecting, expecting it to go. So maybe there's a strict back version, which is just and here's the endpoint maybe. Yeah. Yeah. That's certainly interesting. Yeah. I mean, obviously, any technology needs the the actual training on the product. And so I'd love to see us get to that point where we do release these hey. Build a build a very simple CMS in 5 minutes, or here's direct us in 5 minutes, and here's direct us in 30 minutes. I'd love to even see a certification training program eventually, but, obviously, with a smaller team that that takes a whole different workload there too. But I think over time, we'll add more and more much like our YouTube videos were back in the day focused on Directus and how to use Directus. We'll bring that content back into Directus TV because it's it's what we wanna do and it's what people are asking for as well. Absolutely. And, you know, some of what you're describing is in the works as well in various guises. But, yeah, more instructional, more walk through content, more use case driven inspiration as Brian called it in a previous episode, less instruction, maybe inspiration would be a better word. Yeah. Interesting. I agree, though. From my side, the feedback generally has been pretty good. You know, not every and here's the thing, not every season, not every series has to be for everyone. So, you know, we have a lot of interview based content. Some people are just not interested in the interview format. That's totally cool. Some people just want instruction. Some people want effectively demos in some form or another, whether it's the whole, you know, the whole platform, whether it's discrete parts of the platform or whether it's use cases or case studies or things like that. And some people wanna be entertained. And the lovely thing about this platform we've got is we don't have to double down on any one of those. We just need to always have our eye on making sure the ratios are right. And we also spoke about this in an earlier episode. I don't believe the ratio is right today. The byproduct of this whole platform having come about in 6 weeks is that there was a lot more interview content created and less instructional content because one is easier to make than the other. But we're addressing that, we're addressing that. There are a lot of shows, There are a lot of shows in the works. The day this releases, we announce our spring slate, but we're already working on the summer and the full slate of content as well, which is really exciting. Yeah. I mean, people just want less John and and more instructions, and I totally get that. You know? There's There's only so much Why not instruction from John? Yeah. That'd be kind of interesting because I'm on the the I'm on the side of the house that's kind of I always tell people I'm middle level technical. Like, I understand how to use direct us, but I'm not gonna go and build that Airbnb clone. So that would actually probably be an interesting series, honestly, is watch a middle level technical person build an Airbnb clone or something like that. So that would probably be entertaining. There actually was there is a series pitch with this vibe, but it is, it's Matt Matt who isn't a developer. It's definitely I think we're all everyone who works with directors is quite technically minded. Like, we are technical problem solvers. The amount of code with which we can do that with varies from individual to individual and team to team. But, yeah, that's a really interesting format too. But, yeah, there there's so much. Have you, you know, have you got any other the answer can be no, but has there been any other kind of top line feedback that you've got that could be interesting? Yeah. I think, I think the top line feedback is exactly what you just mentioned. Not every show is for every person. I mean, even myself, I I try and watch every episode of everything that comes out, but there's there's certainly some series that I tend to gravitate towards. So I think that's the good feedback is, not every not every series is for every person, but every person can try and find a series that that fits for them or that they enjoy. So that's one of the pieces of feedback. Obviously, I haven't heard necessarily too much of the I need to dive deeper into these topics, but I'm talking to people who are traditionally newer to direct us. But I can understand that feedback. But then in general, people are watching it, and they're they're glad that we have it. They're glad that we have this content platform, both for the entertainment value, but also for the educational value in the hey. You know, Directus can do what I think it can do, and I can see a really quick video about that. So I think the feedback in general has just been that people enjoy the fact that we have it and the fact that there's something that they can find, you know, value in, whether it's a couple series or one series or there's probably a few people out there who watch every series. So I think the feedback in general has been great. And it's been great for me when again, just to reiterate, when people come and and start to learn about Directus to just point them to a video. You know? Just be like, go watch this series. Go watch this episode. You know, it's fantastic. So that's been great for me too. And as an educator, the person who looks after our docs or lead leading the team who look after our docs, it's very much the same the same there as well, which is the more content we can create that's valuable and solves people's problems, the more reference material we have when that content can help people and the less time we can spend doing the almost, like, repetitive education, right, because we have collateral to back it up. And, yeah, director's TV definitely plays an important part of that. In terms of feedback also, you know, we we track some basic metrics, simple things, what gets watched, how long of each thing gets watched, do people watch stuff and then end up elsewhere on our website, and does that turn into results for us? Absolutely. As part of having our own media platform is that we we know. You know, we we can build build in that analytics and tweak that for our own purposes. There is currently an issue on the GitHub repo for the website to implement a feedback widget like on our documentation so we can get a more rich feedback about how people are finding individual shows and episodes, but that's that's later. For now it's just what's being watched, for how long, does it turn into some form of outcome, and of course the fact that we can use it to help educate people, or inspire them or entertain them or to build relationships and highlight community stories. Yeah. Yeah. No. I think it's been great. And and there's even things on there like scenescapes, which I think we only have 2 of right now. But even though one of the scenes is outside of my window, I'll even put it on sometimes. Or when I'm traveling, I'll put it on and just listen to music and play. So I think, again, the fact that there's we're trying to create series for everybody and for all types of things is awesome. Yeah. And, of course, the other scene scapes is here in Berlin with me. Yeah. Really fun. Thank you so much, John, for joining joining me, and thanks for tuning in to Digging the Rabbit Hole. We hope you found this series insightful. We may well we may well renew it for another season when there's interesting developments. But for now, thank you very much. Enjoy all the other content we have here on directors TV and I'll see you we'll see you in our respective next video hosts. Thanks, everyone.",[179,180],"6d120d9b-61cb-4541-9abc-1cb910f63e43","e6a451ac-f6ae-427b-8a7f-1e784eee765d",[],{"reps":183},[184,239],{"name":172,"sdr":8,"link":185,"countries":186,"states":188},"https://meet.directus.io/meetings/john2144/john-contact-form-meeting",[187],"United States",[189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236,237,238],"Michigan","Indiana","Ohio","West Virginia","Kentucky","Virginia","Tennessee","North Carolina","South Carolina","Georgia","Florida","Alabama","Mississippi","New York","MI","IN","OH","WV","KY","VA","TN","NC","SC","GA","FL","AL","MS","NY","Connecticut","CT","Delaware","DE","Maine","ME","Maryland","MD","Massachusetts","MA","New Hampshire","NH","New Jersey","NJ","Pennsylvania","PA","Rhode Island","RI","Vermont","VT","Washington DC","DC",{"name":240,"link":241,"countries":242},"Michelle Riber","https://meetings.hubspot.com/mriber",[243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268,269,270,271,272,273,274,275,276,277,278,279,280,281,282,283,284,285,286,287,288,289,290,291,292,293,294,295,296,297,298,299,300,301,302,303,304,305,306,307,308,309,310,311,312,313,314,315,316,317,318,319,320,321,322,323,324,325,326,327,328,329,330,331,332,333,334,335,336,337,338,339,340,341,342,343,344,345,346,347,348,349,350,351,352,353,354,355,356,357,358,359,360,361,362,363,364,365,366,367,368,369,370,371,372,373,374,375,376,377,378,379,380,381,382,383,384,385,386,387,388,389,390,391,392,393,394,395,396,397,398,399,400,401,402,403,404,405,406,407,408,409,410,411,412,413,414,415,416,417,418,419,420,421,422,423,424,425,426,427,428,429,430,220,431,432],"Albania","ALB","Algeria","DZA","Andorra","AND","Angola","AGO","Austria","AUT","Belgium","BEL","Benin","BEN","Bosnia and Herzegovina","BIH","Botswana","BWA","Bulgaria","BGR","Burkina Faso","BFA","Burundi","BDI","Cameroon","CMR","Cape Verde","CPV","Central African Republic","CAF","Chad","TCD","Comoros","COM","Côte d'Ivoire","CIV","Croatia","HRV","Czech Republic","CZE","Democratic Republic of Congo","COD","Denmark","DNK","Djibouti","DJI","Egypt","EGY","Equatorial Guinea","GNQ","Eritrea","ERI","Estonia","EST","Eswatini","SWZ","Ethiopia","ETH","Finland","FIN","France","FRA","Gabon","GAB","Gambia","GMB","Ghana","GHA","Greece","GRC","Guinea","GIN","Guinea-Bissau","GNB","Hungary","HUN","Iceland","ISL","Ireland","IRL","Italy","ITA","Kenya","KEN","Latvia","LVA","Lesotho","LSO","Liberia","LBR","Libya","LBY","Liechtenstein","LIE","Lithuania","LTU","Luxembourg","LUX","Madagascar","MDG","Malawi","MWI","Mali","MLI","Malta","MLT","Mauritania","MRT","Mauritius","MUS","Moldova","MDA","Monaco","MCO","Montenegro","MNE","Morocco","MAR","Mozambique","MOZ","Namibia","NAM","Niger","NER","Nigeria","NGA","North Macedonia","MKD","Norway","NOR","Poland","POL","Portugal","PRT","Republic of Congo","COG","Romania","ROU","Rwanda","RWA","San Marino","SMR","São Tomé and Príncipe","STP","Senegal","SEN","Serbia","SRB","Seychelles","SYC","Sierra Leone","SLE","Slovakia","SVK","Slovenia","SVN","Somalia","SOM","South Africa","ZAF","South Sudan","SSD","Spain","ESP","Sudan","SDN","Sweden","SWE","Tanzania","TZA","Togo","TGO","Tunisia","TUN","Uganda","UGA","United Kingdom","GBR","Vatican City","VAT","Zambia","ZMB","Zimbabwe","ZWE","UK","Germany","Netherlands","Switzerland","CH","NL",1773850438300]