[{"data":1,"prerenderedAt":509},["ShallowReactive",2],{"footer-primary":3,"footer-secondary":93,"footer-description":119,"tv-digging-the-rabbit-hole":121,"tv-digging-the-rabbit-hole-seasons":131,"tv-digging-the-rabbit-hole-episodes":143,"sales-reps":258},{"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.&nbsp;\u003C/p>",{"id":122,"title":123,"logo":124,"cover":125,"tile":126,"announcement_text":8,"description":127,"slug":128,"one_liner":129,"card_text":8,"status":130,"sort":8},"bdee500e-382c-4eeb-bf5b-1c4d3c39d35a","Digging the Rabbit Hole","3efa22ad-e45d-48bc-8aba-2bdcf5c4f1fb","2b253e0c-82fd-4ae8-9f68-aee91c2af69c","19c63cdb-35e3-457f-97fd-653500c9eff7","In this series, we cover Directus TV in full: the conception and inspiration, the technical setup, the lifecycle of a show from pitch to release, and how it’s been received so far. ","digging-the-rabbit-hole","Learn about Directus TV as a project - from conception to show creation and technical build.","published",[132],{"id":133,"number":134,"show":122,"year":135,"episodes":136},"5a656532-6f30-42e9-9a11-24b0b9041642",1,"2024",[137,138,139,140,141,142],"30a30326-0bd0-4a40-b680-8c652f58a746","4aa1ba58-7820-40a4-9196-5e186be53f3a","8fc804e1-786d-4a14-bddd-74d2785b20a6","3262bf03-ab28-45e1-a824-c0418b29927a","8fdf7563-f9e4-4321-ae64-d009b0fddfaf","1db8f535-b44b-4b5d-9937-a922ae7560db",[144,167,188,205,222,242],{"id":137,"slug":145,"vimeo_id":146,"description":147,"tile":148,"length":149,"resources":8,"people":150,"episode_number":134,"published":157,"title":158,"video_transcript_html":159,"video_transcript_text":160,"content":8,"seo":8,"status":130,"episode_people":161,"recommendations":164,"season":165},"idea","917623408","In this episode, Matt and Kevin discuss the inspiration behind the Directus TV project.","3c6dfa45-4322-44a8-9163-f163f2e2db29",14,[151,154],{"name":152,"url":153},"Kevin Lewis","https://directus.io/team/kevin-lewis",{"name":155,"url":156},"Matt Minor","https://directus.io/team/matt-minor","2024-03-04","The Idea","\u003Cp>Speaker 0: Hello, everyone, and welcome to the first episode of digging the rabbit hole. This is a series created almost in response to having quite a lot of interest into how this whole platform you're watching this show on came to be. Joining me today is my friend and colleague, Matt. Would you like to introduce yourself?\u003C/p>\u003Cp>Speaker 1: Yeah. Sure. Hey, everyone. I'm Matt Minor. Demand gen marketing, all of the things that you think of when it comes to marketing that's kind of undermined domain.\u003C/p>\u003Cp>So great to meet\u003C/p>\u003Cp>Speaker 0: you. Excellent. And well, we've met the audience might be meeting you for the first time. The in this first episode, I wanted to talk about the inception of directors TV as a project that our team even chose to pick up and work on. And this project was was your brainchild, really.\u003C/p>\u003Cp>It's been very much been a team effort to get it to work and get it out the door, but the inception of it was yours. So I'd love if we could talk a bit about why we're even bothering with this, how it came about inspiration, stuff like that.\u003C/p>\u003Cp>Speaker 1: Yeah. Yeah. So, to give you a little background on me and my background, I come from like kind of when you think of marketing, like everybody hates marketing because marketers ruined it from like the SAS world. So it was all about like, how can I quickly get an MQL? And you probably are familiar with this where people go and download ebooks and you have to give up your email and then you're immediately hounded by SDRs so they can hit that quota and then get the revenue somehow or some way.\u003C/p>\u003Cp>And I think that's put a lot of, I think it's I think it's really tarnished marketing because at the core of it is like we just want to connect people with a solution that's going to make their life better. That's it. And last year was my first experience in the dev tool world and actually marketing to developers and engineers and found out that they have very good meters. So the traditional playbooks don't work. And it was hard to learn that as an experience, but I think it made us all better and us as a company better because we realized we have to build relationships at scale.\u003C/p>\u003Cp>And the way to do that, I think, is by creating actual good content. And a lot of this came from your domain of DevRel. And how can we marry that with, like, the traditional marketing of connecting people to solutions? So those two things combined with the rise of AI last year that came out of nowhere, and I found a lot of, like, the content being put out was just overly, like it was.\u003C/p>\u003Cp>Speaker 0: It's garbage. It's garbage. It's, hey, I generated garbage.\u003C/p>\u003Cp>Speaker 1: Exactly. Yeah. Very garbage. And you can't I mean, you could use a tool like HeyGen to create, like, fake videos. But I think the way of the future is no actual one to 1 you watching somebody.\u003C/p>\u003Cp>And I think that's why people are addicted to TikTok and YouTube and all that stuff. So kind of a long winded answer, but that's kind of where the idea generated was, like an amalgamation of, like, all of these things of how can we create really good content that cuts through the noise that is helpful and doesn't, you know, isn't like us chasing the almighty dollar. Like, how can we actually help the ecosystem?\u003C/p>\u003Cp>Speaker 0: Yeah. And, I we will make a good developer relations practitioner practitioner out of you yet, mister Miner, because that's exactly that is the discipline of DevRel. And what this project really has become is almost expanding that outside of just the realm of DevRel, at least at directors and across the entire organizations as we have created shows that not only benefit lots of teams goals, but also get them involved. So that's been really, really pleasant as well. Can we talk a little bit about why we're not just then creating a bunch of shows on YouTube Because that is a completely viable approach.\u003C/p>\u003Cp>Right? We could be creating content on platforms where developers already are. And Yeah.\u003C/p>\u003Cp>Speaker 1: So no. That's a great, great question and great audience there because, obviously, YouTube is, like, the 2nd largest. It might I think it might have even eclipsed Google is like the largest search engine that people that people use the most used, I guess. And this is one hesitation we had when we were coming up with the idea and producing shows. And we're basically taking, we're taking YouTube out of the\u003C/p>\u003Cp>Speaker 0: we're taking YouTube out\u003C/p>\u003Cp>Speaker 1: of the equation and we're going to build it ourselves, which is like, but there's billions of people that use YouTube and we're starting from ground.\u003C/p>\u003Cp>Speaker 0: So discovery engine. It's a discovery engine.\u003C/p>\u003Cp>Speaker 1: Exactly. Yeah. So, actually, I had a great conversation with Anthony Canada, who's the CEO over at Audience Plus, which they have a platform that does what we're doing with with, DirectTV. They built like a sass around it all around own media. They're really building that.\u003C/p>\u003Cp>They're doing a really good job. And I actually asked that question. I was like, look, we're we're basically discovering this or we're basically abandoning this giant discovery platform and starting from scratch. And he was like, you know, when you go to YouTube, like, very seldom do people hang out on YouTube, watch out like hours of content like they do on Netflix. They they go to Netflix to binge.\u003C/p>\u003Cp>They go to YouTube for like the quick highlights. And same thing with TikTok. Like you go to TikTok, you've got 30 to 62nd videos and you're just scrolling through kind of that. Yeah. Getting that endorphin hit and then like going to the next one sort of thing.\u003C/p>\u003Cp>So he's like, well, what he said was we're finding a lot of companies are starting to put their best content on YouTube and like cutting out the short snippets, the best bits, the highlights, basically, and then pushing people back to their own media because that's what own media is like. You you own the audience. You're not, renting it from YouTube or Google. You're giving them the good stuff. And then if they really, truly like what you're doing and you're getting by it, then they'll come to your platform and subscribe.\u003C/p>\u003Cp>So that's the reasoning behind it. It's kind of an interesting dynamic for sure. But\u003C/p>\u003Cp>Speaker 0: the the not the renting your audience is something I was hoping you were gonna say because I think that's that's so so true. And the other benefit of owned platform and not just own media, but own platform is you get to you get the almost editorial decision around the curation of content. I feel like on YouTube and other platforms, their recommendation engine doesn't work always in the benefit of your audience, right? It works in the benefit of the goals of the platform. And you can present it in the way that makes sense for you and your audience.\u003C/p>\u003Cp>Right? We've trimmed a bunch of fat. If you look at a YouTube player or any of these platforms, you know, you look at the players and the pages that house the media, and we are very direct. We are very like, here is the content, here is the necessary information to help you get the most of it and move up move on. Now here's the next the next part if there is one or whatever.\u003C/p>\u003Cp>Here's some related content. We we have curated that experience quite intentionally for people as well. Mhmm. Yeah. We don't have availability elsewhere.\u003C/p>\u003Cp>Speaker 1: No. Yeah. And, like, just personal, like, experience. Like, when I go to YouTube, I have a 2 year old daughter, so I've got Paw Patrol intermixed with like marketing and a mix of music videos. It's it's curated to me and my interests.\u003C/p>\u003Cp>But, as like a professional, I I can't go to YouTube and and use it. I I typically go to LinkedIn, which is, you know, another, channel that's own media. I go to, like, Hockey Stack, which is a, they have a own media channel, which is really good. Watch a few videos there, podcasts. I have a few select things I go to, but there's no one single place I can go that has a bunch of really good content to help me get better.\u003C/p>\u003Cp>And that's kind of what we're trying to build.\u003C/p>\u003Cp>Speaker 0: And these these platforms, like you mentioned, HockeyStack, I've seen their platform too. It's very much aimed at their audience marketers. Right? And there isn't a lot out there that is aimed at this this audience that directors has, which is primarily developers, not exclusively, but primarily developers. There aren't a lot, if any, platforms for them.\u003C/p>\u003Cp>So I think that's interesting too. Don't get me wrong. There's a lot of video content out there for developers, curated video content too, but a lot of it is instructional. What we're doing now is we are it's purely around upskilling and continued professional development. And we're trying to and we'll talk about this in a in a future episode of Digging the Rabbit Hole.\u003C/p>\u003Cp>We've curated a content library, which is a little more multifaceted around all of the interests that our audience might have.\u003C/p>\u003Cp>Speaker 1: Yeah. No. And we talked to Jason Linkedorf about this too. And he he also believes this is where media content, it's all going for the developer world. So, it's just really cool to have, like, that mindshare with, like, somebody like Jason, who's obviously doing an incredible job building building a brand, putting out incredible shows.\u003C/p>\u003Cp>And I think it is, like he says, like, the the industry is going that way. So it's just cool to to play a part in it in what we're doing with Directus TV.\u003C/p>\u003Cp>Speaker 0: Yeah. Awesome. Before we wrap up this first episode of Dicking the Rabbit Hole, was there anything you wanted anything else you wanted to talk about in terms of the inception of the oh, another interesting note that I I have actually. The inception of this platform happened in March 2023, being a very small scrappy marketing team. It it was mentioned, you know, it had some headspace for a few weeks and it never really got off the ground.\u003C/p>\u003Cp>Right? It never became a thing we did. The whole thing came up. We finished our 1st leap week, our 1st week of announcements at the end of October 2023, and then there was a void left in our hearts. What what what fills this huge amount of stress now?\u003C/p>\u003Cp>Speaker 1: Yeah. Exactly.\u003C/p>\u003Cp>Speaker 0: And and it literally between, like, the 1st week of November and, like, just before Christmas when we released director's TV, that was the entire window in which the whole thing was formalized, built, content was made and edited and released. It was about a 6 week period, and we continue to work in that scrappy way. There's a future episode on our process and how we've managed to and how we've managed to make this work. But yeah, was there anything else you want to talk about in terms of inception?\u003C/p>\u003Cp>Speaker 1: No, I just remember actually, I remember the stand up that we had and I was like, hey, like, like content's like doing really well. What if we just all, like, made our own video series and we had our own, like, Netflix sort of thing? Yeah. And everybody was a content house. Yeah.\u003C/p>\u003Cp>Everybody was like, Oh, yeah, maybe one day, because we had so many different things going on. But as time went on and we found content was going really well, and we were able to actually produce really good content. And we have a lot of incredible people, people in this team like, John and Pedro, who are sales reps, and they host podcasts with, you know, engineering leaders and they're willing to jump in. We even did like a.\u003C/p>\u003Cp>Speaker 0: Trace talks, by the way, for people watching this. You can watch that now. But this\u003C/p>\u003Cp>Speaker 1: is the first place I've worked where everybody wants to join in and help build content.\u003C/p>\u003Cp>Speaker 0: Absolutely.\u003C/p>\u003Cp>Speaker 1: And like do good content. And I think if you have that buy in with the team, it's a lot easier to pull off. So we're we're continuing getting there. I'm really excited with what we've done so far. And don't sell yourself short, Kevin.\u003C/p>\u003Cp>Like, you're the one that pulled all this together. So you're you're the linchpin of all this happening. So it always helps to have somebody like that on the team that can project manage and\u003C/p>\u003Cp>Speaker 0: Thank you very much. I'll I'll pay you for that compliment later. Yep. So this is the first episode of digging the rabbit hole. This is, I think it's gonna end up being a 5 part series.\u003C/p>\u003Cp>In future episodes, they're all available now. We're gonna release this in in one bundle, for you to watch. In the next episode, we're gonna talk about what gets made, how do we actually, you know, people across directors pitch shows into Matt and I. How do we decide what actually will get built and what are the purposes of different shows? What are the motivations and what are the kind of the decision factors that make that happen.\u003C/p>\u003Cp>Then we're gonna talk about the process that we've created that allows us to output such a huge amount of content while not actually having any individual, like, owning director's TV. Like, this is this is one of the many projects that are run, and that is that is enabled by strong processes and playing into our team's strengths and weaknesses and building processes that that, account for those. We'll talk about that as well. Then we'll talk about the actual technical build, this platform right here. It's part of our website.\u003C/p>\u003Cp>How does it work? Spoiler, of course, it utilizes directors to manage content, but we'll also dig into the code, and see how that all gets pulled through. And then finally, we will chat with some of our field team around some of the early reception for this platform and how it's been going so far. So I think that's I think that's it, Matt.\u003C/p>\u003Cp>Speaker 1: That's it. Thanks for having me.\u003C/p>\u003Cp>Speaker 0: Thanks for thanks for coming. And until the next episode, bye for now.\u003C/p>\u003Cp>Speaker 1: Bye.\u003C/p>","Hello, everyone, and welcome to the first episode of digging the rabbit hole. This is a series created almost in response to having quite a lot of interest into how this whole platform you're watching this show on came to be. Joining me today is my friend and colleague, Matt. Would you like to introduce yourself? Yeah. Sure. Hey, everyone. I'm Matt Minor. Demand gen marketing, all of the things that you think of when it comes to marketing that's kind of undermined domain. So great to meet you. Excellent. And well, we've met the audience might be meeting you for the first time. The in this first episode, I wanted to talk about the inception of directors TV as a project that our team even chose to pick up and work on. And this project was was your brainchild, really. It's been very much been a team effort to get it to work and get it out the door, but the inception of it was yours. So I'd love if we could talk a bit about why we're even bothering with this, how it came about inspiration, stuff like that. Yeah. Yeah. So, to give you a little background on me and my background, I come from like kind of when you think of marketing, like everybody hates marketing because marketers ruined it from like the SAS world. So it was all about like, how can I quickly get an MQL? And you probably are familiar with this where people go and download ebooks and you have to give up your email and then you're immediately hounded by SDRs so they can hit that quota and then get the revenue somehow or some way. And I think that's put a lot of, I think it's I think it's really tarnished marketing because at the core of it is like we just want to connect people with a solution that's going to make their life better. That's it. And last year was my first experience in the dev tool world and actually marketing to developers and engineers and found out that they have very good meters. So the traditional playbooks don't work. And it was hard to learn that as an experience, but I think it made us all better and us as a company better because we realized we have to build relationships at scale. And the way to do that, I think, is by creating actual good content. And a lot of this came from your domain of DevRel. And how can we marry that with, like, the traditional marketing of connecting people to solutions? So those two things combined with the rise of AI last year that came out of nowhere, and I found a lot of, like, the content being put out was just overly, like it was. It's garbage. It's garbage. It's, hey, I generated garbage. Exactly. Yeah. Very garbage. And you can't I mean, you could use a tool like HeyGen to create, like, fake videos. But I think the way of the future is no actual one to 1 you watching somebody. And I think that's why people are addicted to TikTok and YouTube and all that stuff. So kind of a long winded answer, but that's kind of where the idea generated was, like an amalgamation of, like, all of these things of how can we create really good content that cuts through the noise that is helpful and doesn't, you know, isn't like us chasing the almighty dollar. Like, how can we actually help the ecosystem? Yeah. And, I we will make a good developer relations practitioner practitioner out of you yet, mister Miner, because that's exactly that is the discipline of DevRel. And what this project really has become is almost expanding that outside of just the realm of DevRel, at least at directors and across the entire organizations as we have created shows that not only benefit lots of teams goals, but also get them involved. So that's been really, really pleasant as well. Can we talk a little bit about why we're not just then creating a bunch of shows on YouTube Because that is a completely viable approach. Right? We could be creating content on platforms where developers already are. And Yeah. So no. That's a great, great question and great audience there because, obviously, YouTube is, like, the 2nd largest. It might I think it might have even eclipsed Google is like the largest search engine that people that people use the most used, I guess. And this is one hesitation we had when we were coming up with the idea and producing shows. And we're basically taking, we're taking YouTube out of the we're taking YouTube out of the equation and we're going to build it ourselves, which is like, but there's billions of people that use YouTube and we're starting from ground. So discovery engine. It's a discovery engine. Exactly. Yeah. So, actually, I had a great conversation with Anthony Canada, who's the CEO over at Audience Plus, which they have a platform that does what we're doing with with, DirectTV. They built like a sass around it all around own media. They're really building that. They're doing a really good job. And I actually asked that question. I was like, look, we're we're basically discovering this or we're basically abandoning this giant discovery platform and starting from scratch. And he was like, you know, when you go to YouTube, like, very seldom do people hang out on YouTube, watch out like hours of content like they do on Netflix. They they go to Netflix to binge. They go to YouTube for like the quick highlights. And same thing with TikTok. Like you go to TikTok, you've got 30 to 62nd videos and you're just scrolling through kind of that. Yeah. Getting that endorphin hit and then like going to the next one sort of thing. So he's like, well, what he said was we're finding a lot of companies are starting to put their best content on YouTube and like cutting out the short snippets, the best bits, the highlights, basically, and then pushing people back to their own media because that's what own media is like. You you own the audience. You're not, renting it from YouTube or Google. You're giving them the good stuff. And then if they really, truly like what you're doing and you're getting by it, then they'll come to your platform and subscribe. So that's the reasoning behind it. It's kind of an interesting dynamic for sure. But the the not the renting your audience is something I was hoping you were gonna say because I think that's that's so so true. And the other benefit of owned platform and not just own media, but own platform is you get to you get the almost editorial decision around the curation of content. I feel like on YouTube and other platforms, their recommendation engine doesn't work always in the benefit of your audience, right? It works in the benefit of the goals of the platform. And you can present it in the way that makes sense for you and your audience. Right? We've trimmed a bunch of fat. If you look at a YouTube player or any of these platforms, you know, you look at the players and the pages that house the media, and we are very direct. We are very like, here is the content, here is the necessary information to help you get the most of it and move up move on. Now here's the next the next part if there is one or whatever. Here's some related content. We we have curated that experience quite intentionally for people as well. Mhmm. Yeah. We don't have availability elsewhere. No. Yeah. And, like, just personal, like, experience. Like, when I go to YouTube, I have a 2 year old daughter, so I've got Paw Patrol intermixed with like marketing and a mix of music videos. It's it's curated to me and my interests. But, as like a professional, I I can't go to YouTube and and use it. I I typically go to LinkedIn, which is, you know, another, channel that's own media. I go to, like, Hockey Stack, which is a, they have a own media channel, which is really good. Watch a few videos there, podcasts. I have a few select things I go to, but there's no one single place I can go that has a bunch of really good content to help me get better. And that's kind of what we're trying to build. And these these platforms, like you mentioned, HockeyStack, I've seen their platform too. It's very much aimed at their audience marketers. Right? And there isn't a lot out there that is aimed at this this audience that directors has, which is primarily developers, not exclusively, but primarily developers. There aren't a lot, if any, platforms for them. So I think that's interesting too. Don't get me wrong. There's a lot of video content out there for developers, curated video content too, but a lot of it is instructional. What we're doing now is we are it's purely around upskilling and continued professional development. And we're trying to and we'll talk about this in a in a future episode of Digging the Rabbit Hole. We've curated a content library, which is a little more multifaceted around all of the interests that our audience might have. Yeah. No. And we talked to Jason Linkedorf about this too. And he he also believes this is where media content, it's all going for the developer world. So, it's just really cool to have, like, that mindshare with, like, somebody like Jason, who's obviously doing an incredible job building building a brand, putting out incredible shows. And I think it is, like he says, like, the the industry is going that way. So it's just cool to to play a part in it in what we're doing with Directus TV. Yeah. Awesome. Before we wrap up this first episode of Dicking the Rabbit Hole, was there anything you wanted anything else you wanted to talk about in terms of the inception of the oh, another interesting note that I I have actually. The inception of this platform happened in March 2023, being a very small scrappy marketing team. It it was mentioned, you know, it had some headspace for a few weeks and it never really got off the ground. Right? It never became a thing we did. The whole thing came up. We finished our 1st leap week, our 1st week of announcements at the end of October 2023, and then there was a void left in our hearts. What what what fills this huge amount of stress now? Yeah. Exactly. And and it literally between, like, the 1st week of November and, like, just before Christmas when we released director's TV, that was the entire window in which the whole thing was formalized, built, content was made and edited and released. It was about a 6 week period, and we continue to work in that scrappy way. There's a future episode on our process and how we've managed to and how we've managed to make this work. But yeah, was there anything else you want to talk about in terms of inception? No, I just remember actually, I remember the stand up that we had and I was like, hey, like, like content's like doing really well. What if we just all, like, made our own video series and we had our own, like, Netflix sort of thing? Yeah. And everybody was a content house. Yeah. Everybody was like, Oh, yeah, maybe one day, because we had so many different things going on. But as time went on and we found content was going really well, and we were able to actually produce really good content. And we have a lot of incredible people, people in this team like, John and Pedro, who are sales reps, and they host podcasts with, you know, engineering leaders and they're willing to jump in. We even did like a. Trace talks, by the way, for people watching this. You can watch that now. But this is the first place I've worked where everybody wants to join in and help build content. Absolutely. And like do good content. And I think if you have that buy in with the team, it's a lot easier to pull off. So we're we're continuing getting there. I'm really excited with what we've done so far. And don't sell yourself short, Kevin. Like, you're the one that pulled all this together. So you're you're the linchpin of all this happening. So it always helps to have somebody like that on the team that can project manage and Thank you very much. I'll I'll pay you for that compliment later. Yep. So this is the first episode of digging the rabbit hole. This is, I think it's gonna end up being a 5 part series. In future episodes, they're all available now. We're gonna release this in in one bundle, for you to watch. In the next episode, we're gonna talk about what gets made, how do we actually, you know, people across directors pitch shows into Matt and I. How do we decide what actually will get built and what are the purposes of different shows? What are the motivations and what are the kind of the decision factors that make that happen. Then we're gonna talk about the process that we've created that allows us to output such a huge amount of content while not actually having any individual, like, owning director's TV. Like, this is this is one of the many projects that are run, and that is that is enabled by strong processes and playing into our team's strengths and weaknesses and building processes that that, account for those. We'll talk about that as well. Then we'll talk about the actual technical build, this platform right here. It's part of our website. How does it work? Spoiler, of course, it utilizes directors to manage content, but we'll also dig into the code, and see how that all gets pulled through. And then finally, we will chat with some of our field team around some of the early reception for this platform and how it's been going so far. So I think that's I think that's it, Matt. That's it. Thanks for having me. Thanks for thanks for coming. And until the next episode, bye for now. Bye.",[162,163],"6a71981e-78e4-4dc0-8535-1ee9b137878f","72fcbab8-e5ef-4751-8dce-c0f28adfa674",[],{"id":133,"number":134,"show":122,"year":135,"episodes":166},[137,138,139,140,141,142],{"id":138,"slug":168,"vimeo_id":169,"description":170,"tile":171,"length":172,"resources":8,"people":173,"episode_number":178,"published":157,"title":179,"video_transcript_html":180,"video_transcript_text":181,"content":8,"seo":8,"status":130,"episode_people":182,"recommendations":185,"season":186},"shows","918834415","In this episode, Bryant and Kevin discuss what shows are being commissioned and why. ","514df5ce-fbc9-41fc-972b-99da764eb893",18,[174,175],{"name":152,"url":153},{"name":176,"url":177},"Bryant Gillespie","https://directus.io/team/bryant-gillespie",2,"The Shows","\u003Cp>Speaker 0: Hello, and welcome to the 2nd episode of Digging the Rabbit Hole. This is a series where we dive into the conception creation and initial feedback around directors TV, this platform, which you are watching this show on. And joining me today is my friend and colleague. Bryant, would you like to introduce yourself?\u003C/p>\u003Cp>Speaker 1: Yes. Yes. I so for a long time, I was the resident YouTube guy, but now that we've got some more faces, happy to be a part of the SIEV. I'm Bryant, a developer advocate here at Directus, and, yeah, create a ton of videos and content. You'll find me on the 100 apps series.\u003C/p>\u003Cp>Speaker 0: A 100 apps and some other upcoming series as well, short hops, the joy of theming, which will be announced the day this goes live so that these these exist, and others as well. Absolutely. In this chat, I wanted to talk a little bit about what actually gets made. We've already spoken about the conception of directors TV and in the future we'll talk about the process of actually getting stuff built. But there's this bit in the middle of actually thinking up shows and then as a team deciding which ones get commissioned into seasons.\u003C/p>\u003Cp>So I thought we could talk a little bit about that. And what better place to start? Yeah. Thank you. What better place to start than actually, I wanna talk about a 100 apps in a 100 hours.\u003C/p>\u003Cp>Could we actually open with you describing what the series is?\u003C/p>\u003Cp>Speaker 1: Yeah. So a 100 apps, 100 hours is basically me speed running, building a full app or or getting as far along as I can using Directus and whatever other tools are available at that point, whether it's, Nux for the front end or, even I I think some of the episodes make some chat gpt in there to, like, speed things along, but it's definitely like an meant to be entertainment, and a good showcase of, like, what is actually possible with tools like Directus. Like, what can you achieve in an hour?\u003C/p>\u003Cp>Speaker 0: And it's it's actually quite novel as well because it isn't an educational series. It's not like step by step come with me. I figured it out. You know, I'm gonna show you how to do it. No.\u003C/p>\u003Cp>We're watching you sweat for an hour figuring out how to do\u003C/p>\u003Cp>Speaker 1: it. Yeah. I it like, when I first started, and I can't remember exactly what the like, the foundational, like, hey, this is what we're gonna do moment was. It was just like, hey, we're I wanna build some cool stuff. We're gonna record it.\u003C/p>\u003Cp>I I think that's how this started.\u003C/p>\u003Cp>Speaker 0: I actually looked back at the pitch note for a 100 apps in a 100 hours, and the show was definitely originally called Brian Build Cool Shit, and it turned into a 100 apps in a 100 hours. I looked at the history of the pitch, which is kinda funny.\u003C/p>\u003Cp>Speaker 1: Yeah. Yeah. It's it's awesome to see how these things evolve. But, like, the I I can remember that, like, recording, like, the first couple of episodes, I was really, like, concerned because, you know, a lot of the other educational content that we do is is very polished and robust and, like, hey. We're gonna get you from point a to point b.\u003C/p>\u003Cp>But, like, what what they see in a 100 apps, 100 hours is is just me sweating through the real, like, warts and all. Like, there's there's no editing in between, like, the graphics and, like, the intros and everything. It's it's just, you know, one hour of me talking to myself as I build something.\u003C/p>\u003Cp>Speaker 0: And there are other show formats, of course. I think 100 Apps in a 100 Hours is probably one of the examples of a more novel format that we currently have. We definitely got some more in the works that I don't even think we will have announced by the time this show goes out. But we have, you know, I think quite a lot of our series at the moment are like straight up interview format. The specifics of what who is being interviewed and the topic in which they're being interviewed change from series to series.\u003C/p>\u003Cp>We have quite a lot of series based content trace talks where John and Pedro talk to engineering leaders about their career leading to being, you know, it's engineering leaders. There's learning things I love to hate, which is my series where it's nothing to do with directors. We just Yep. I I get people in who who are my friends, who know about tech that has some kind of reason I've been avoiding it and try and help me understand. And I hope that that helps the audience understand that's not conceited.\u003C/p>\u003Cp>I really do not know about these topics, and I really seek to learn about them in the time together.\u003C/p>\u003Cp>Speaker 1: I really dig the concept of that one of, like, hey, like, convince me. There's, like, that one meme that's like, there's a guy in the park, and it's like, hey. GraphQL is bad. Like, convince me, or GraphQL is great. Convince me.\u003C/p>\u003Cp>So I I love the concept of that one.\u003C/p>\u003Cp>Speaker 0: Do you wanna know what? Convincing is a degree. Like, the way that show opens is I say, right. Let me level set. Here's what I think I know about the topic.\u003C/p>\u003Cp>So we're not gonna go from 0. Like, here's what I think I know about the topic. Help me get to that. And here are my skepticism or uncertainties. Help me navigate those.\u003C/p>\u003Cp>So it's not even convincing. Like, we did an episode AI for devs, and I was like, I'm not not trying to convince me to use AI tools here in my development practice. I just wanna see how people use it and challenge some of the assumptions I have, which was successfully done. Web 3, it wasn't convinced me, you know, that I that I wanna build web 3 apps. It's I just do not understand how they they work.\u003C/p>\u003Cp>Yeah.\u003C/p>\u003Cp>Speaker 1: It turned the light on for me. Exactly.\u003C/p>\u003Cp>Speaker 0: So that there's that series. There's, beyond the call where Esther interviews people who build directors extensions about the extensions that they've built in their journey, their journey using direct. So so they all have different vibes, but that is an interview format. Then we have quite instructional educational content like stack up or like quick connect, which is all about or make it real time, which are like step by step tutorials that you can pause and, you know, do yourself and and they are definitely more polished and considered.\u003C/p>\u003Cp>Speaker 1: I think, hey, like, one of the questions that I I probably already know the answer to this, but it, like, yeah, the expectations for Directus TV, right, would probably be like, hey. Here's a bunch of content that's exclusively focused on Directus. And, you know, as what the ringleader of the Directus TV circus, I guess you could call it, That's, hey, that's cool, I guess. It's very organized and and well constructed, but, you know, there's a lot of different content, and not all of it's specifically about direct us. Like Exactly.\u003C/p>\u003Cp>Was that decision made?\u003C/p>\u003Cp>Speaker 0: Because then you're only drawing people who already wanna know about direct us. You know, learning things I love to hate is an example of a show where I think in one of the 5 episodes, there is there is like an obvious lead back to direct assist the GraphQL episode. And it was about like the selective querying. And the fact that you can do that with direct to says REST API as well. But other than that, that is just a general interest series because we know you and I, as people who do developer relations, that we know what we want to watch, we know what our peers want to watch and find interesting.\u003C/p>\u003Cp>Don't get me wrong, enough of that content needs to help people discover and understand and be successful with and expand their usage of director. Sure. But that is not every show. At that point, you know, you're basically just building out tutorials and various ilks. And it's very self serving.\u003C/p>\u003Cp>And that isn't what we're doing here. We're trying to, you know, well, what are we trying to do? It depends on the show, right? So, you know, I think all of our shows exist to do one of a number of things or one or more of a number of things. To educate absolutely, to build relationships with with our guests for the interview series.\u003C/p>\u003Cp>We have to highlight stories from our community members and give them a platform where we have a reasonable sized platform. You know, we can we can boost them or simply to entertain because they're fun. And they're interesting. And there's more of those coming up too. So depends on the show, right?\u003C/p>\u003Cp>The balance needs to be that it's net positive for directors, but just by providing that content is net is net benefit.\u003C/p>\u003Cp>Speaker 1: So also that needs to be very interesting and fun to do some of these shows as well.\u003C/p>\u003Cp>Speaker 0: Yeah. Absolutely. I'm having a blast putting shows together, whether I'm doing it from, like, an operational standpoint and other people are, like, recording raw footage and conceptualizing them or I'm the person putting them together as well. So we take some time to talk about and actually, I wanna ask you, I wanna set the scene. Answer ask the question answer the question and ask you what you think because I'm curious.\u003C/p>\u003Cp>Right? So in our in our next episode, we're gonna talk a bit about the process from pitch to release of a of a series. But just focusing in on that first step, we get an idea. And we have a space internally where we ask people to pitch internally. So not just ever, I'm not just marketing, but across the org, sales success engineering, great.\u003C/p>\u003Cp>Pitch a show idea, and we can help people, you know, navigate it. And every time they people want to pitch, we ask them to actually fill in a quite annoying format. Like we ask them to put in work upfront. We ask them to give us the rough concept. Think about the format.\u003C/p>\u003Cp>Think about who is the audience of this because not every show is for developers, I think especially not going forward. You know, many shows are there for technical people, but not all software developers. What does it aim to do for us? Like, what is what does directors get out of this? Are we gonna be educating, building relationships, you know, building positive community and so on or entertaining.\u003C/p>\u003Cp>We say, who is gonna be involved in this? Is it just you? Is it you and guests? Is it you and other colleagues and so on? What's the length of a season?\u003C/p>\u003Cp>Speaker 1: And It's crucial to that part.\u003C/p>\u003Cp>Speaker 0: Yeah. I think so too. And outline the first three episodes. And that obviously requires stepping back and really having a think upfront. And I'm kind of curious, like, we also this information upfront to once we go, all share a vision of how the show is going to materialize.\u003C/p>\u003Cp>How has that been for you? I'm curious as someone who has pitched many shows. So,\u003C/p>\u003Cp>Speaker 1: it like, for me, ideas come from many different places. And, like, some of the pitches that I've put together have obviously been, like, very, I would call, weak just because it's like, hey. An idea pops into\u003C/p>\u003Cp>Speaker 0: my light on detail.\u003C/p>\u003Cp>Speaker 1: There you go. Light on detail. Right? Because it's either like, it's popped up by, a trigger on some other content that I was watching. Like, hey.\u003C/p>\u003Cp>This could be a, you know, like, a watching a game show, for instance. Oh, hey. This might make a interesting series around x, y, and z on direct to CV or on a walk with my kids. So as far as, like, the the pitching process, like, it creating the ideas, I take influences everywhere. So, like, the ideas never stop.\u003C/p>\u003Cp>As far as, like, which ones to pursue, I I think, like, I use it as a holding tank and then let it sit for a day. Yeah. And then if I come back if I come back to it and I'm like, hey. I really wanna pursue this. This is this is still good, then I would flesh it out.\u003C/p>\u003Cp>So there's a lot for me in there that are, like, half baked, But, you're not saying it's not a great idea, but just, like, other ideas were\u003C/p>\u003Cp>Speaker 0: Yeah. Better or or they take more time. Because, I mean, that's also worth noting. You know, the initial release of directors TV and the initial slate of shows, which I'll call the winter slate, right, the winter 2023 slate. As today, on the day of this release, we've announced our spring slate for 2024.\u003C/p>\u003Cp>They take a different amount of effort. When we launched directors TV, it was 6 weeks from conception to release. And there was quite a lot of new content. I think we created 8 new shows, we had some content already that we that we packaged up and released on directors TV as well. And that's how we kind of seeded our initial content.\u003C/p>\u003Cp>And our initial release was a ton of interview content because interview content doesn't take a lot of effort. Once you have a guest committed and you have a rough format outlined, which you can do in a couple of bullet points, you can rinse and repeat that that format and generate lots of fantastic content. Instructional content, however, takes a lot more time. 100 acts in a 100 hours is an incredible format. Like, I'm I'm so happy with how you've, like, formatted it because it is quite a high impact series, both in terms of entertainment and I would say education, not in terms of how to build use cases, but understanding that these use cases can be built in direct us.\u003C/p>\u003Cp>Speaker 1: Yeah. I look at it as inspiration\u003C/p>\u003Cp>Speaker 0: is what I'm sure. But the in its very conception, the format is low on time. You know, there's maybe I I I mean, how much prep do you do before you hit record and spend an hour?\u003C/p>\u003Cp>Speaker 1: Do you know? On on things like Netflix or Airbnb, like, obviously, users of those applications, so I've got a fair bit of what's going on. For some of the other ones, like a PIM or some of the other use cases, just like a a quick Google search. And I wanted to keep it that way. And, you know, we've we've had a a fair bit of feedback from folks that are like, hey.\u003C/p>\u003Cp>I'm I'm expecting educational content, but that's kind of, like, you know, goes against the grain of the the concept of the show of, like What\u003C/p>\u003Cp>Speaker 0: what what do you mean? Feedback in a later episode, but 100 acts in a 100 hours will feature in that because you've hit you've hit on something really interesting around meeting expectations. But we're doing something new, so we're also having to rebuild the expectations and and correct expectations and\u003C/p>\u003Cp>Speaker 1: Yeah. Too. And that's that plays into, like, the ideas as well. It's like, hey. Is this gonna be well received?\u003C/p>\u003Cp>You know? One of the one of the other shows that I had a ton of fun recording was dev thoughts, which are, like, dev dad jokes, but, essentially, they were\u003C/p>\u003Cp>Speaker 0: 2 of them.\u003C/p>\u003Cp>Speaker 1: Yeah. Yeah. They were stolen from SNL, the old, Jack Handy deep thoughts skit, for those who who are familiar with SNL. But, like, our audience is, you know, international. And without knowing that skit from SNL, does this land or not?\u003C/p>\u003Cp>You know? So there was there's a lot of that that factors into, like, should we pursue this show or not?\u003C/p>\u003Cp>Speaker 0: Absolutely. Absolutely. Yeah. No. I I I think you nailed it there.\u003C/p>\u003Cp>But what's interesting, though, is this feel like the initial release of director's TV was a little light on technical content. Actually, it was a lot of interviews and that's that is because it only took 6 weeks to materialize. But as we produce our as we release our spring slate and work on our summer and even our 4th slate at this point in time, really, we're getting to fill out these different content types, including more novel, really, really, I think quite exciting formats that are just gonna I think they're gonna be hits like I really I the things I would love to watch. And so, yeah, I'm just so I'm so excited for folks to enjoy our spring slate of shows and to see what else we have coming. Some of those more novel formats, though, will take a lot more production time.\u003C/p>\u003Cp>And that's why now that has to be factored in to the length of a season to whether it can even go ahead and the timeline on which we can produce it as well. Thank you, Brian, for joining me. I've had a blast talking about this.\u003C/p>\u003Cp>Speaker 1: Well, this is the first time that we've this is kind of like our postmortem internally. Right? Because we developed this thing in 6 weeks, hit the ground running, and and since then, it's been both feet on the gas. Like, hey. Let's keep going.\u003C/p>\u003Cp>You know, let's deliver new content. So We're we're now where we're at is is been yeah. This is fun.\u003C/p>\u003Cp>Speaker 0: I agree. And, yeah, I we're now at the point where we have enough content that is produced that is going out. You know, it's hit it's it's done. It's it's the editing is finished. It's ready, but it is scheduled to go when it goes.\u003C/p>\u003Cp>But we are now looking ahead. And so we have time now and only now really to to look at and talk about how this all came about. And I I I'm talking about it. It's quite nice to, you know, revalidate some of those decisions we previously made. And as we finish out the season with some initial feedback from our audience and our communities and our customers, It'll be interesting to see how the future of directors TV may, even if it's just process driven or, you know, changing what we commission or the ratios of education versus entertainment versus interview and, you know, community highlighting and all of that, how that may change over time.\u003C/p>\u003Cp>Last month, I looked at the numbers. Last month, we released over 8 shows, we released 27 episodes and about 12 hours of content, which is wild. Mind blowing. Exactly. Right?\u003C/p>\u003Cp>Exactly. Wicked, thank you so much for joining me, and thank you so much for joining us. We'll see you in the next episode. Bye for now. Yeah.\u003C/p>\u003Cp>Thanks, Kevin.\u003C/p>","Hello, and welcome to the 2nd episode of Digging the Rabbit Hole. This is a series where we dive into the conception creation and initial feedback around directors TV, this platform, which you are watching this show on. And joining me today is my friend and colleague. Bryant, would you like to introduce yourself? Yes. Yes. I so for a long time, I was the resident YouTube guy, but now that we've got some more faces, happy to be a part of the SIEV. I'm Bryant, a developer advocate here at Directus, and, yeah, create a ton of videos and content. You'll find me on the 100 apps series. A 100 apps and some other upcoming series as well, short hops, the joy of theming, which will be announced the day this goes live so that these these exist, and others as well. Absolutely. In this chat, I wanted to talk a little bit about what actually gets made. We've already spoken about the conception of directors TV and in the future we'll talk about the process of actually getting stuff built. But there's this bit in the middle of actually thinking up shows and then as a team deciding which ones get commissioned into seasons. So I thought we could talk a little bit about that. And what better place to start? Yeah. Thank you. What better place to start than actually, I wanna talk about a 100 apps in a 100 hours. Could we actually open with you describing what the series is? Yeah. So a 100 apps, 100 hours is basically me speed running, building a full app or or getting as far along as I can using Directus and whatever other tools are available at that point, whether it's, Nux for the front end or, even I I think some of the episodes make some chat gpt in there to, like, speed things along, but it's definitely like an meant to be entertainment, and a good showcase of, like, what is actually possible with tools like Directus. Like, what can you achieve in an hour? And it's it's actually quite novel as well because it isn't an educational series. It's not like step by step come with me. I figured it out. You know, I'm gonna show you how to do it. No. We're watching you sweat for an hour figuring out how to do it. Yeah. I it like, when I first started, and I can't remember exactly what the like, the foundational, like, hey, this is what we're gonna do moment was. It was just like, hey, we're I wanna build some cool stuff. We're gonna record it. I I think that's how this started. I actually looked back at the pitch note for a 100 apps in a 100 hours, and the show was definitely originally called Brian Build Cool Shit, and it turned into a 100 apps in a 100 hours. I looked at the history of the pitch, which is kinda funny. Yeah. Yeah. It's it's awesome to see how these things evolve. But, like, the I I can remember that, like, recording, like, the first couple of episodes, I was really, like, concerned because, you know, a lot of the other educational content that we do is is very polished and robust and, like, hey. We're gonna get you from point a to point b. But, like, what what they see in a 100 apps, 100 hours is is just me sweating through the real, like, warts and all. Like, there's there's no editing in between, like, the graphics and, like, the intros and everything. It's it's just, you know, one hour of me talking to myself as I build something. And there are other show formats, of course. I think 100 Apps in a 100 Hours is probably one of the examples of a more novel format that we currently have. We definitely got some more in the works that I don't even think we will have announced by the time this show goes out. But we have, you know, I think quite a lot of our series at the moment are like straight up interview format. The specifics of what who is being interviewed and the topic in which they're being interviewed change from series to series. We have quite a lot of series based content trace talks where John and Pedro talk to engineering leaders about their career leading to being, you know, it's engineering leaders. There's learning things I love to hate, which is my series where it's nothing to do with directors. We just Yep. I I get people in who who are my friends, who know about tech that has some kind of reason I've been avoiding it and try and help me understand. And I hope that that helps the audience understand that's not conceited. I really do not know about these topics, and I really seek to learn about them in the time together. I really dig the concept of that one of, like, hey, like, convince me. There's, like, that one meme that's like, there's a guy in the park, and it's like, hey. GraphQL is bad. Like, convince me, or GraphQL is great. Convince me. So I I love the concept of that one. Do you wanna know what? Convincing is a degree. Like, the way that show opens is I say, right. Let me level set. Here's what I think I know about the topic. So we're not gonna go from 0. Like, here's what I think I know about the topic. Help me get to that. And here are my skepticism or uncertainties. Help me navigate those. So it's not even convincing. Like, we did an episode AI for devs, and I was like, I'm not not trying to convince me to use AI tools here in my development practice. I just wanna see how people use it and challenge some of the assumptions I have, which was successfully done. Web 3, it wasn't convinced me, you know, that I that I wanna build web 3 apps. It's I just do not understand how they they work. Yeah. It turned the light on for me. Exactly. So that there's that series. There's, beyond the call where Esther interviews people who build directors extensions about the extensions that they've built in their journey, their journey using direct. So so they all have different vibes, but that is an interview format. Then we have quite instructional educational content like stack up or like quick connect, which is all about or make it real time, which are like step by step tutorials that you can pause and, you know, do yourself and and they are definitely more polished and considered. I think, hey, like, one of the questions that I I probably already know the answer to this, but it, like, yeah, the expectations for Directus TV, right, would probably be like, hey. Here's a bunch of content that's exclusively focused on Directus. And, you know, as what the ringleader of the Directus TV circus, I guess you could call it, That's, hey, that's cool, I guess. It's very organized and and well constructed, but, you know, there's a lot of different content, and not all of it's specifically about direct us. Like Exactly. Was that decision made? Because then you're only drawing people who already wanna know about direct us. You know, learning things I love to hate is an example of a show where I think in one of the 5 episodes, there is there is like an obvious lead back to direct assist the GraphQL episode. And it was about like the selective querying. And the fact that you can do that with direct to says REST API as well. But other than that, that is just a general interest series because we know you and I, as people who do developer relations, that we know what we want to watch, we know what our peers want to watch and find interesting. Don't get me wrong, enough of that content needs to help people discover and understand and be successful with and expand their usage of director. Sure. But that is not every show. At that point, you know, you're basically just building out tutorials and various ilks. And it's very self serving. And that isn't what we're doing here. We're trying to, you know, well, what are we trying to do? It depends on the show, right? So, you know, I think all of our shows exist to do one of a number of things or one or more of a number of things. To educate absolutely, to build relationships with with our guests for the interview series. We have to highlight stories from our community members and give them a platform where we have a reasonable sized platform. You know, we can we can boost them or simply to entertain because they're fun. And they're interesting. And there's more of those coming up too. So depends on the show, right? The balance needs to be that it's net positive for directors, but just by providing that content is net is net benefit. So also that needs to be very interesting and fun to do some of these shows as well. Yeah. Absolutely. I'm having a blast putting shows together, whether I'm doing it from, like, an operational standpoint and other people are, like, recording raw footage and conceptualizing them or I'm the person putting them together as well. So we take some time to talk about and actually, I wanna ask you, I wanna set the scene. Answer ask the question answer the question and ask you what you think because I'm curious. Right? So in our in our next episode, we're gonna talk a bit about the process from pitch to release of a of a series. But just focusing in on that first step, we get an idea. And we have a space internally where we ask people to pitch internally. So not just ever, I'm not just marketing, but across the org, sales success engineering, great. Pitch a show idea, and we can help people, you know, navigate it. And every time they people want to pitch, we ask them to actually fill in a quite annoying format. Like we ask them to put in work upfront. We ask them to give us the rough concept. Think about the format. Think about who is the audience of this because not every show is for developers, I think especially not going forward. You know, many shows are there for technical people, but not all software developers. What does it aim to do for us? Like, what is what does directors get out of this? Are we gonna be educating, building relationships, you know, building positive community and so on or entertaining. We say, who is gonna be involved in this? Is it just you? Is it you and guests? Is it you and other colleagues and so on? What's the length of a season? And It's crucial to that part. Yeah. I think so too. And outline the first three episodes. And that obviously requires stepping back and really having a think upfront. And I'm kind of curious, like, we also this information upfront to once we go, all share a vision of how the show is going to materialize. How has that been for you? I'm curious as someone who has pitched many shows. So, it like, for me, ideas come from many different places. And, like, some of the pitches that I've put together have obviously been, like, very, I would call, weak just because it's like, hey. An idea pops into my light on detail. There you go. Light on detail. Right? Because it's either like, it's popped up by, a trigger on some other content that I was watching. Like, hey. This could be a, you know, like, a watching a game show, for instance. Oh, hey. This might make a interesting series around x, y, and z on direct to CV or on a walk with my kids. So as far as, like, the the pitching process, like, it creating the ideas, I take influences everywhere. So, like, the ideas never stop. As far as, like, which ones to pursue, I I think, like, I use it as a holding tank and then let it sit for a day. Yeah. And then if I come back if I come back to it and I'm like, hey. I really wanna pursue this. This is this is still good, then I would flesh it out. So there's a lot for me in there that are, like, half baked, But, you're not saying it's not a great idea, but just, like, other ideas were Yeah. Better or or they take more time. Because, I mean, that's also worth noting. You know, the initial release of directors TV and the initial slate of shows, which I'll call the winter slate, right, the winter 2023 slate. As today, on the day of this release, we've announced our spring slate for 2024. They take a different amount of effort. When we launched directors TV, it was 6 weeks from conception to release. And there was quite a lot of new content. I think we created 8 new shows, we had some content already that we that we packaged up and released on directors TV as well. And that's how we kind of seeded our initial content. And our initial release was a ton of interview content because interview content doesn't take a lot of effort. Once you have a guest committed and you have a rough format outlined, which you can do in a couple of bullet points, you can rinse and repeat that that format and generate lots of fantastic content. Instructional content, however, takes a lot more time. 100 acts in a 100 hours is an incredible format. Like, I'm I'm so happy with how you've, like, formatted it because it is quite a high impact series, both in terms of entertainment and I would say education, not in terms of how to build use cases, but understanding that these use cases can be built in direct us. Yeah. I look at it as inspiration is what I'm sure. But the in its very conception, the format is low on time. You know, there's maybe I I I mean, how much prep do you do before you hit record and spend an hour? Do you know? On on things like Netflix or Airbnb, like, obviously, users of those applications, so I've got a fair bit of what's going on. For some of the other ones, like a PIM or some of the other use cases, just like a a quick Google search. And I wanted to keep it that way. And, you know, we've we've had a a fair bit of feedback from folks that are like, hey. I'm I'm expecting educational content, but that's kind of, like, you know, goes against the grain of the the concept of the show of, like What what what do you mean? Feedback in a later episode, but 100 acts in a 100 hours will feature in that because you've hit you've hit on something really interesting around meeting expectations. But we're doing something new, so we're also having to rebuild the expectations and and correct expectations and Yeah. Too. And that's that plays into, like, the ideas as well. It's like, hey. Is this gonna be well received? You know? One of the one of the other shows that I had a ton of fun recording was dev thoughts, which are, like, dev dad jokes, but, essentially, they were 2 of them. Yeah. Yeah. They were stolen from SNL, the old, Jack Handy deep thoughts skit, for those who who are familiar with SNL. But, like, our audience is, you know, international. And without knowing that skit from SNL, does this land or not? You know? So there was there's a lot of that that factors into, like, should we pursue this show or not? Absolutely. Absolutely. Yeah. No. I I I think you nailed it there. But what's interesting, though, is this feel like the initial release of director's TV was a little light on technical content. Actually, it was a lot of interviews and that's that is because it only took 6 weeks to materialize. But as we produce our as we release our spring slate and work on our summer and even our 4th slate at this point in time, really, we're getting to fill out these different content types, including more novel, really, really, I think quite exciting formats that are just gonna I think they're gonna be hits like I really I the things I would love to watch. And so, yeah, I'm just so I'm so excited for folks to enjoy our spring slate of shows and to see what else we have coming. Some of those more novel formats, though, will take a lot more production time. And that's why now that has to be factored in to the length of a season to whether it can even go ahead and the timeline on which we can produce it as well. Thank you, Brian, for joining me. I've had a blast talking about this. Well, this is the first time that we've this is kind of like our postmortem internally. Right? Because we developed this thing in 6 weeks, hit the ground running, and and since then, it's been both feet on the gas. Like, hey. Let's keep going. You know, let's deliver new content. So We're we're now where we're at is is been yeah. This is fun. I agree. And, yeah, I we're now at the point where we have enough content that is produced that is going out. You know, it's hit it's it's done. It's it's the editing is finished. It's ready, but it is scheduled to go when it goes. But we are now looking ahead. And so we have time now and only now really to to look at and talk about how this all came about. And I I I'm talking about it. It's quite nice to, you know, revalidate some of those decisions we previously made. And as we finish out the season with some initial feedback from our audience and our communities and our customers, It'll be interesting to see how the future of directors TV may, even if it's just process driven or, you know, changing what we commission or the ratios of education versus entertainment versus interview and, you know, community highlighting and all of that, how that may change over time. Last month, I looked at the numbers. Last month, we released over 8 shows, we released 27 episodes and about 12 hours of content, which is wild. Mind blowing. Exactly. Right? Exactly. Wicked, thank you so much for joining me, and thank you so much for joining us. We'll see you in the next episode. Bye for now. Yeah. Thanks, Kevin.",[183,184],"a9323e06-ac6d-4d41-9b02-4520cd9e0546","3a36ddcb-22b2-4151-b906-4e3149830252",[],{"id":133,"number":134,"show":122,"year":135,"episodes":187},[137,138,139,140,141,142],{"id":139,"slug":189,"vimeo_id":190,"description":191,"tile":192,"length":193,"resources":8,"people":194,"episode_number":196,"published":157,"title":197,"video_transcript_html":198,"video_transcript_text":199,"content":8,"seo":8,"status":130,"episode_people":200,"recommendations":202,"season":203},"production","918868401","In this episode, Kevin discusses the efficient processes created to enable show creation at scale. ","4bce4584-b5b0-4002-bbee-c3836c8b716f",7,[195],{"name":152,"url":153},3,"The Production","\u003Cp>Speaker 0: Hello, and welcome back to Digging the Rabbit Hole. And in this episode, we're going to talk a bit about how a show goes from a pitch through to release. Now in the last episode, we discussed that very first part. We discussed what a pitch looks like and why we may choose to commission a show over others. But there is obviously a really big gap between agreeing to do something and getting it out the door.\u003C/p>\u003Cp>Let's start by talking a bit about some of our team's strengths, because I think that helps contextualize the process we've created as well as some of our shortcomings. So, our strengths. Right. Really good at making video, actually. Really good at taking something from idea, creating the graphics required, actually filming, editing, and finally, publishing content.\u003C/p>\u003Cp>We have a few people in the organization who are good at this from various teams. So the ability to create video was never a challenge. And in fact, I would go as far as to say, many of our team have an affinity towards creating video content, but there are some challenges. Firstly, all of those steps that I just described take a lot of time. And in fact, time is the challenge with this project.\u003C/p>\u003Cp>We don't have a dedicated person running directors TV, and indeed, it would always require a cross team effort, right, to make sure shows have, you know, a few different faces involved in them. Being a 35 person company across the board from core engineering through to marketing sales, you know, general administrative over in developer relations, all of us, 35 people, is that we move really, really quickly. But by moving quickly, projects that you have to keep returning to are often the projects, that get left behind, and indeed, this has happened. There are video series on our YouTube channel, where there were 2 or 3 episodes, and then we simply run out of time. There was always something more important, more pressing, you know, more impactful to do, and those series were just left, unloved.\u003C/p>\u003Cp>So that is a little bit of context as to our team. Really good at making video, but it takes a lot of time and time is the enemy. So what did we do? We created a process which basically involves batching work. When an idea is pitched, it is pitched with a number of episodes that will be produced or that are being pitched as part of that series.\u003C/p>\u003Cp>Sometimes that's a negotiation, you know, sometimes we pair it back, Sometimes we will increase it and so on, but we have a clear idea what is going to be created and how many episodes will be released. We have a big content calendar. It's basically populated now, like, 4 or 5 months ahead of time, which is lovely. So, when an idea is accepted, it also comes with a release date, and that release date will be months away realistically for most shows. From there, we work back.\u003C/p>\u003Cp>A week before that is the editing deadline, and then generally, like, 2 to 4 weeks before that, depending on the series and the complexity of the edit, is the deadline for all the footage. Instead and this is the key. Instead All of the recording happens together. Then we have an amazing editor, Nat. He was gonna join me on this episode, but he's a little unwell.\u003C/p>\u003Cp>And that will basically then get the whole package. 100 acts in a 100 hours an episode a series is 10 episodes. He gets all 10 episodes raw recording at once. Now the team don't need to care about the editing so much. We just have to care about producing the raw footage.\u003C/p>\u003Cp>We hand it off, and that creates 1 episode if it's a new show for a look and feel so we can approve it, make sure it feels good, tweak it, and so on, and then he can go and batch edit them all. Batch upload them all, batch prepare them all inside of the director's instance that runs director's TV. More about that in the next episode. And then each day, we simply release, distribute, and share. And that allows us to pour our full energy into making sure that people are actually watching them, that we're actually doing episodes justice by sharing them far and wide in communities that will find that content interesting.\u003C/p>\u003Cp>And that's really it. That is the process. So stuff goes from a pitch to being approved, then the planning portion comes in. Some shows, you know, I I have to go out and find guests, for example, then there's a filming part. Once the filming part has concluded, there is an editing part, and then we go ahead load it all into the director's project that runs director's TV, and we go ahead and release it.\u003C/p>\u003Cp>And so, yeah, I wanted to talk just very briefly about this process we've created because it is what enables this absolute powerhouse of a content production machine is this process. Now don't get me wrong. That isn't without its challenges to actually be able to block out time to using a 100 apps and a 100 hours as an example to do the minimal preparation for each episode and then record it. I mean, you're talking now half a week completely carved out or, you know, half a day every day for a week or however that may may be organized. But you are we're demanding more time of our team, but just in a batch.\u003C/p>\u003Cp>And then they know I don't have to worry about finding the time for this series, on an ongoing basis because that's then taken care of, and centralized as well. So that's a little bit, about how it works. We also have a design team who managed to create all of the lovely graphics for each of our shows. We're giving each show its own unique identity look and feel while making sure they look good as a collective when presented with each other. And I think that's kind of it.\u003C/p>\u003Cp>Yeah. I just wanted to give a little bit of a rundown about this process we've created, about how we kind of batch the work. And the other fantastic thing about batching work is it allows us to do what we have done today on the release day of this episode, which is, release into you know, know what's coming, an entire slate of shows, and the confidence that we will be able to deliver that slate because all the recordings done, Most of the editing is done, and then it's all just, you know, batch kind of admin work. So this was an episode all about the process. I hope you have enjoyed it, and we'll see you in the next episode of digging the rabbit hole.\u003C/p>\u003Cp>Bye for now.\u003C/p>","Hello, and welcome back to Digging the Rabbit Hole. And in this episode, we're going to talk a bit about how a show goes from a pitch through to release. Now in the last episode, we discussed that very first part. We discussed what a pitch looks like and why we may choose to commission a show over others. But there is obviously a really big gap between agreeing to do something and getting it out the door. Let's start by talking a bit about some of our team's strengths, because I think that helps contextualize the process we've created as well as some of our shortcomings. So, our strengths. Right. Really good at making video, actually. Really good at taking something from idea, creating the graphics required, actually filming, editing, and finally, publishing content. We have a few people in the organization who are good at this from various teams. So the ability to create video was never a challenge. And in fact, I would go as far as to say, many of our team have an affinity towards creating video content, but there are some challenges. Firstly, all of those steps that I just described take a lot of time. And in fact, time is the challenge with this project. We don't have a dedicated person running directors TV, and indeed, it would always require a cross team effort, right, to make sure shows have, you know, a few different faces involved in them. Being a 35 person company across the board from core engineering through to marketing sales, you know, general administrative over in developer relations, all of us, 35 people, is that we move really, really quickly. But by moving quickly, projects that you have to keep returning to are often the projects, that get left behind, and indeed, this has happened. There are video series on our YouTube channel, where there were 2 or 3 episodes, and then we simply run out of time. There was always something more important, more pressing, you know, more impactful to do, and those series were just left, unloved. So that is a little bit of context as to our team. Really good at making video, but it takes a lot of time and time is the enemy. So what did we do? We created a process which basically involves batching work. When an idea is pitched, it is pitched with a number of episodes that will be produced or that are being pitched as part of that series. Sometimes that's a negotiation, you know, sometimes we pair it back, Sometimes we will increase it and so on, but we have a clear idea what is going to be created and how many episodes will be released. We have a big content calendar. It's basically populated now, like, 4 or 5 months ahead of time, which is lovely. So, when an idea is accepted, it also comes with a release date, and that release date will be months away realistically for most shows. From there, we work back. A week before that is the editing deadline, and then generally, like, 2 to 4 weeks before that, depending on the series and the complexity of the edit, is the deadline for all the footage. Instead and this is the key. Instead All of the recording happens together. Then we have an amazing editor, Nat. He was gonna join me on this episode, but he's a little unwell. And that will basically then get the whole package. 100 acts in a 100 hours an episode a series is 10 episodes. He gets all 10 episodes raw recording at once. Now the team don't need to care about the editing so much. We just have to care about producing the raw footage. We hand it off, and that creates 1 episode if it's a new show for a look and feel so we can approve it, make sure it feels good, tweak it, and so on, and then he can go and batch edit them all. Batch upload them all, batch prepare them all inside of the director's instance that runs director's TV. More about that in the next episode. And then each day, we simply release, distribute, and share. And that allows us to pour our full energy into making sure that people are actually watching them, that we're actually doing episodes justice by sharing them far and wide in communities that will find that content interesting. And that's really it. That is the process. So stuff goes from a pitch to being approved, then the planning portion comes in. Some shows, you know, I I have to go out and find guests, for example, then there's a filming part. Once the filming part has concluded, there is an editing part, and then we go ahead load it all into the director's project that runs director's TV, and we go ahead and release it. And so, yeah, I wanted to talk just very briefly about this process we've created because it is what enables this absolute powerhouse of a content production machine is this process. Now don't get me wrong. That isn't without its challenges to actually be able to block out time to using a 100 apps and a 100 hours as an example to do the minimal preparation for each episode and then record it. I mean, you're talking now half a week completely carved out or, you know, half a day every day for a week or however that may may be organized. But you are we're demanding more time of our team, but just in a batch. And then they know I don't have to worry about finding the time for this series, on an ongoing basis because that's then taken care of, and centralized as well. So that's a little bit, about how it works. We also have a design team who managed to create all of the lovely graphics for each of our shows. We're giving each show its own unique identity look and feel while making sure they look good as a collective when presented with each other. And I think that's kind of it. Yeah. I just wanted to give a little bit of a rundown about this process we've created, about how we kind of batch the work. And the other fantastic thing about batching work is it allows us to do what we have done today on the release day of this episode, which is, release into you know, know what's coming, an entire slate of shows, and the confidence that we will be able to deliver that slate because all the recordings done, Most of the editing is done, and then it's all just, you know, batch kind of admin work. So this was an episode all about the process. I hope you have enjoyed it, and we'll see you in the next episode of digging the rabbit hole. Bye for now.",[201],"c62bcadd-1e08-4a15-8b64-1ef02da14c0d",[],{"id":133,"number":134,"show":122,"year":135,"episodes":204},[137,138,139,140,141,142],{"id":140,"slug":206,"vimeo_id":207,"description":208,"tile":209,"length":210,"resources":8,"people":211,"episode_number":213,"published":157,"title":214,"video_transcript_html":215,"video_transcript_text":216,"content":8,"seo":8,"status":130,"episode_people":217,"recommendations":219,"season":220},"platform","917617587","In this episode, Kevin walks through the code and backend of Directus TV.","d4b0a23c-8836-4bd4-89d8-ca82ea1654d5",10,[212],{"name":152,"url":153},4,"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.",[218],"687c6fd3-0c41-47ab-8a08-7055d24d69c8",[],{"id":133,"number":134,"show":122,"year":135,"episodes":221},[137,138,139,140,141,142],{"id":141,"slug":223,"vimeo_id":224,"description":225,"tile":226,"length":149,"resources":8,"people":227,"episode_number":232,"published":157,"title":233,"video_transcript_html":234,"video_transcript_text":235,"content":8,"seo":8,"status":130,"episode_people":236,"recommendations":239,"season":240},"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",[228,229],{"name":152,"url":153},{"name":230,"url":231},"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.",[237,238],"6d120d9b-61cb-4541-9abc-1cb910f63e43","e6a451ac-f6ae-427b-8a7f-1e784eee765d",[],{"id":133,"number":134,"show":122,"year":135,"episodes":241},[137,138,139,140,141,142],{"id":142,"slug":243,"vimeo_id":244,"description":245,"tile":246,"length":247,"resources":8,"people":248,"episode_number":247,"published":157,"title":250,"video_transcript_html":251,"video_transcript_text":252,"content":8,"seo":8,"status":130,"episode_people":253,"recommendations":255,"season":256},"kit","917616799","In this episode, Bryant shows you around the template for creating your own streaming service with Directus, based on Directus TV.","30a3bb54-f021-45c3-aba7-94d7bbb14024",6,[249],{"name":176,"url":177},"The Kit","\u003Cp>Speaker 0: Hello, and welcome back to digging the rabbit hole. We've gone through this journey of talking about DIRECTV from its inception to its release, the processes we've created and some of the early feedback. I actually have brought Brian back on. Hello, Brian, you're back for let's call it an epilogue, talking about building your own versions of directors TV for your projects and organizations. Yeah.\u003C/p>\u003Cp>Happy to be back. Thanks for bringing me back on to just show this off. Right? One of the questions that you've already answered is, you know, what powers this thing? But we created a template for folks who want to dig a\u003C/p>\u003Cp>Speaker 1: little deeper and maybe dig their own rabbit hole. So I'm just gonna walk you through the template just so you could see what's available. So the data model for the streaming platform, this very closely mirrors Directus TV itself. We have shows. So these are the actual collections of episodes.\u003C/p>\u003Cp>You could see here we've got some sample content like dev thoughts and a 100 apps, 100 hours. When you dig into that, you could see the title, the slug that you're using on the front end for the URL. We've got some announcement text and all these different images, that go on various\u003C/p>\u003Cp>Speaker 0: This looks familiar.\u003C/p>\u003Cp>Speaker 1: It does it? It should. Yeah. But rather than create sample content for this, I said, well, let's just steal what we already have. So, within that, you have your different seasons.\u003C/p>\u003Cp>And within the seasons, you have a number, a year, some actual episodes where this is where the the meat and potatoes of the content lives. A title description. We're using Vimeo to host those videos, so we've got a Vimeo ID. You could just as well upload a file into Directus and serve that or use a third party, YouTube or Wistia or some other service as well. Transcripts are available.\u003C/p>\u003Cp>We've got a tile. You can attach resources, and you can even add your different people, which is a relationship, which is really nice so that you don't have to keep typing those same people in every single episode. So we've got different collections there for the people. You can see you and I in there, a couple of handsome gentlemen. We have different categories.\u003C/p>\u003Cp>So interviews, code with us, short hops, these are the same ones on Directus TV. I'm sure they look familiar to you, Kevin. And then added a couple other things here for sessions. So, ideally, you'd be generating these from the front end where you're tracking, the visitor ID, you know, generating a UUID, or if a person is logged in to your streaming platform, you can track their episodes that they've watched, the start and end time, and then track that session time. As well as the last piece of the puzzle here is ratings.\u003C/p>\u003Cp>So within each show, ideally on the front end, you've got a like, dislike, or a a love interaction, so that that you can know which shows are resonating with the audience. So that is\u003C/p>\u003Cp>Speaker 0: Super nice.\u003C/p>\u003Cp>Speaker 1: Yeah. It's super nice. Also a preview of of what's available, in our premium subscription, which is direct us plus, where you can get access to this data model along with others that you see up here, like headless LMS or PIM, status page, multi tenant SaaS that's not actually in this demo. So there's a a lot more on the other side for you. Directus plus comes with some, advanced workshops that, we run on a monthly basis as well.\u003C/p>\u003Cp>And I I really hope it's going to be tremendously valuable to the community.\u003C/p>\u003Cp>Speaker 0: Yeah. That's awesome. Thank you so much for just taking a moment to show us through this. And then even though we've already covered code in a previous episode of digging the rabbit hole, reminder that our website is open source, and it is within our website site that Directus TV lives as you're thinking about implementing the front end for something like this. You've taken what I originally did with Directus TV and expanded it further.\u003C/p>\u003Cp>People being its own collection, which may be something we we end up needing to to do, adding ratings, adding sessions. Maybe this is stuff we'll do. I think we've already spoken about feedback and ratings at the very least. So it's really nice to see the thing that I built kind of enhanced a little bit further, and available on directors plus. And again, yeah, if you need that front end kind of inspiration or some code patterns that we've used, you can feel free to map those straight out of our site.\u003C/p>\u003Cp>I\u003C/p>\u003Cp>Speaker 1: totally forgot that that was even available.\u003C/p>\u003Cp>Speaker 0: Yeah. Yeah. Yeah. Absolutely. Yeah.\u003C/p>\u003Cp>Speaker 1: Well, thanks again for bringing me on, Kevin, and, I I Thank you. Really enjoyed this series as a whole, and I love being part of Directus Plus. So kudos to you for bringing it all together.\u003C/p>\u003Cp>Speaker 0: Thank you very much. Directus Plus is not to do with me. I'll say thanks to you for Directors Plus, but I'll take the thanks for Directors TV. Thank you very much. Thank you very much for joining us for this season.\u003C/p>\u003Cp>I've been Kevin, says Brian, which you knew. I don't know why I decided to go out like this. I think we're just gonna hit stop record now. Bye.\u003C/p>","Hello, and welcome back to digging the rabbit hole. We've gone through this journey of talking about DIRECTV from its inception to its release, the processes we've created and some of the early feedback. I actually have brought Brian back on. Hello, Brian, you're back for let's call it an epilogue, talking about building your own versions of directors TV for your projects and organizations. Yeah. Happy to be back. Thanks for bringing me back on to just show this off. Right? One of the questions that you've already answered is, you know, what powers this thing? But we created a template for folks who want to dig a little deeper and maybe dig their own rabbit hole. So I'm just gonna walk you through the template just so you could see what's available. So the data model for the streaming platform, this very closely mirrors Directus TV itself. We have shows. So these are the actual collections of episodes. You could see here we've got some sample content like dev thoughts and a 100 apps, 100 hours. When you dig into that, you could see the title, the slug that you're using on the front end for the URL. We've got some announcement text and all these different images, that go on various This looks familiar. It does it? It should. Yeah. But rather than create sample content for this, I said, well, let's just steal what we already have. So, within that, you have your different seasons. And within the seasons, you have a number, a year, some actual episodes where this is where the the meat and potatoes of the content lives. A title description. We're using Vimeo to host those videos, so we've got a Vimeo ID. You could just as well upload a file into Directus and serve that or use a third party, YouTube or Wistia or some other service as well. Transcripts are available. We've got a tile. You can attach resources, and you can even add your different people, which is a relationship, which is really nice so that you don't have to keep typing those same people in every single episode. So we've got different collections there for the people. You can see you and I in there, a couple of handsome gentlemen. We have different categories. So interviews, code with us, short hops, these are the same ones on Directus TV. I'm sure they look familiar to you, Kevin. And then added a couple other things here for sessions. So, ideally, you'd be generating these from the front end where you're tracking, the visitor ID, you know, generating a UUID, or if a person is logged in to your streaming platform, you can track their episodes that they've watched, the start and end time, and then track that session time. As well as the last piece of the puzzle here is ratings. So within each show, ideally on the front end, you've got a like, dislike, or a a love interaction, so that that you can know which shows are resonating with the audience. So that is Super nice. Yeah. It's super nice. Also a preview of of what's available, in our premium subscription, which is direct us plus, where you can get access to this data model along with others that you see up here, like headless LMS or PIM, status page, multi tenant SaaS that's not actually in this demo. So there's a a lot more on the other side for you. Directus plus comes with some, advanced workshops that, we run on a monthly basis as well. And I I really hope it's going to be tremendously valuable to the community. Yeah. That's awesome. Thank you so much for just taking a moment to show us through this. And then even though we've already covered code in a previous episode of digging the rabbit hole, reminder that our website is open source, and it is within our website site that Directus TV lives as you're thinking about implementing the front end for something like this. You've taken what I originally did with Directus TV and expanded it further. People being its own collection, which may be something we we end up needing to to do, adding ratings, adding sessions. Maybe this is stuff we'll do. I think we've already spoken about feedback and ratings at the very least. So it's really nice to see the thing that I built kind of enhanced a little bit further, and available on directors plus. And again, yeah, if you need that front end kind of inspiration or some code patterns that we've used, you can feel free to map those straight out of our site. I totally forgot that that was even available. Yeah. Yeah. Yeah. Absolutely. Yeah. Well, thanks again for bringing me on, Kevin, and, I I Thank you. Really enjoyed this series as a whole, and I love being part of Directus Plus. So kudos to you for bringing it all together. Thank you very much. Directus Plus is not to do with me. I'll say thanks to you for Directors Plus, but I'll take the thanks for Directors TV. Thank you very much. Thank you very much for joining us for this season. I've been Kevin, says Brian, which you knew. I don't know why I decided to go out like this. I think we're just gonna hit stop record now. Bye.",[254],"b12c7288-a4fe-430a-8bfa-c034200f27ad",[],{"id":133,"number":134,"show":122,"year":135,"episodes":257},[137,138,139,140,141,142],{"reps":259},[260,315],{"name":230,"sdr":8,"link":261,"countries":262,"states":264},"https://meet.directus.io/meetings/john2144/john-contact-form-meeting",[263],"United States",[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],"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":316,"link":317,"countries":318},"Michelle Riber","https://meetings.hubspot.com/mriber",[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,431,432,433,434,435,436,437,438,439,440,441,442,443,444,445,446,447,448,449,450,451,452,453,454,455,456,457,458,459,460,461,462,463,464,465,466,467,468,469,470,471,472,473,474,475,476,477,478,479,480,481,482,483,484,485,486,487,488,489,490,491,492,493,494,495,496,497,498,499,500,501,502,503,504,505,506,296,507,508],"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",1773850417279]