1 00:00:00,000 --> 00:00:02,280 Hey, everyone, and welcome to another deep dive. 2 00:00:02,280 --> 00:00:06,120 Today, we're taking a closer look at Neos CMS. 3 00:00:06,120 --> 00:00:07,920 Neos CMS. 4 00:00:07,920 --> 00:00:11,240 Is it just another system for managing your website content, 5 00:00:11,240 --> 00:00:13,600 or is there something more to it? 6 00:00:13,600 --> 00:00:16,400 We've got their website and a peek into their GitHub repo, 7 00:00:16,400 --> 00:00:18,720 so let's see what we can uncover. 8 00:00:18,720 --> 00:00:19,360 OK. 9 00:00:19,360 --> 00:00:22,200 And a quick shout out to our sponsor, Safe Server. 10 00:00:22,200 --> 00:00:24,320 They can help with all sorts of digital transformation 11 00:00:24,320 --> 00:00:27,360 projects, including hosting tricky software. 12 00:00:27,360 --> 00:00:32,760 Check them out at www.safeserver.de. 13 00:00:32,760 --> 00:00:33,760 Very cool. 14 00:00:33,760 --> 00:00:35,720 Now, back to Neos. 15 00:00:35,720 --> 00:00:38,840 Right off the bat, their website hits you with this headline. 16 00:00:38,840 --> 00:00:42,040 Easily create, manage, and optimize content that is loved. 17 00:00:42,040 --> 00:00:42,760 Loved. 18 00:00:42,760 --> 00:00:43,880 Catchy, right? 19 00:00:43,880 --> 00:00:44,400 Yeah. 20 00:00:44,400 --> 00:00:45,880 But is there any substance behind it? 21 00:00:45,880 --> 00:00:47,480 Well, I think what's interesting here 22 00:00:47,480 --> 00:00:49,520 is they're aiming at two different groups. 23 00:00:49,520 --> 00:00:51,160 The content creators, obviously, who 24 00:00:51,160 --> 00:00:54,360 need something easy to use, and then the developers, 25 00:00:54,360 --> 00:00:57,720 who need that flexibility and control behind the scenes. 26 00:00:57,720 --> 00:00:59,440 Yeah, it's like trying to build a car that's 27 00:00:59,440 --> 00:01:02,000 both a luxury sedan and a sports car, right? 28 00:01:02,000 --> 00:01:03,200 Can you really have both? 29 00:01:03,200 --> 00:01:04,800 So let's look at the features and see 30 00:01:04,800 --> 00:01:06,700 if it lives up to the hype. 31 00:01:06,700 --> 00:01:10,560 They talk about an inline, YSI Ouija editor. 32 00:01:10,560 --> 00:01:11,800 Click and type, it's that easy. 33 00:01:11,800 --> 00:01:13,120 Yeah, the click and type. 34 00:01:13,120 --> 00:01:16,280 Sounds great for anyone who's not a coding wizard. 35 00:01:16,280 --> 00:01:17,680 That's exactly it, right? 36 00:01:17,680 --> 00:01:19,960 It's for the folks who just want to focus 37 00:01:19,960 --> 00:01:22,520 on the words and the images and not 38 00:01:22,520 --> 00:01:24,640 have to mess with the code underneath. 39 00:01:24,640 --> 00:01:27,480 So it's like working on a Google Doc almost. 40 00:01:27,480 --> 00:01:30,000 Yeah, like a live collaborative Google Doc 41 00:01:30,000 --> 00:01:31,480 where you see the changes as you type. 42 00:01:31,480 --> 00:01:34,520 But then how do you keep things looking good? 43 00:01:34,520 --> 00:01:36,960 If everyone's got free reign over this style, 44 00:01:36,960 --> 00:01:38,040 it's going to be a mess. 45 00:01:38,040 --> 00:01:43,800 Yeah, so Neos uses the system of predefined styles. 46 00:01:43,800 --> 00:01:45,840 It's kind of like giving everyone 47 00:01:45,840 --> 00:01:50,960 a set of stylish Lego blocks to build with right. 48 00:01:50,960 --> 00:01:54,280 So they've got some creative freedom, 49 00:01:54,280 --> 00:01:57,560 but the overall design stays consistent. 50 00:01:57,560 --> 00:02:01,480 OK, so that's one side of it, the content creation part. 51 00:02:01,480 --> 00:02:03,440 But what about the developers? 52 00:02:03,440 --> 00:02:05,160 I mean, their get-up page is pretty bold. 53 00:02:05,160 --> 00:02:08,800 It says, Neos is crafted by and for developers. 54 00:02:08,800 --> 00:02:10,320 No magic happening. 55 00:02:10,320 --> 00:02:12,760 You are in full control over what you do. 56 00:02:12,760 --> 00:02:13,960 Wow, yeah. 57 00:02:13,960 --> 00:02:14,920 That's a big claim. 58 00:02:14,920 --> 00:02:15,920 Yeah, it is. 59 00:02:15,920 --> 00:02:17,920 What kind of control are we talking about here? 60 00:02:17,920 --> 00:02:20,120 Well, with Neos, developers can define 61 00:02:20,120 --> 00:02:23,720 the structure of the content, like what types of content 62 00:02:23,720 --> 00:02:25,560 the website can even handle. 63 00:02:25,560 --> 00:02:28,360 They're not limited to just preset templates 64 00:02:28,360 --> 00:02:30,360 or rigid structures. 65 00:02:30,360 --> 00:02:32,040 So it's not a cookie cutter website 66 00:02:32,040 --> 00:02:33,840 where you can really make it your own. 67 00:02:33,840 --> 00:02:37,240 It's like building a custom house instead 68 00:02:37,240 --> 00:02:40,400 of settling for one that's prefabricated. 69 00:02:40,400 --> 00:02:41,160 I don't like that. 70 00:02:41,160 --> 00:02:44,400 You have the freedom to create exactly what you need. 71 00:02:44,400 --> 00:02:46,840 And I see they also have this idea of planned extensibility. 72 00:02:46,840 --> 00:02:47,760 Planned extensibility. 73 00:02:47,760 --> 00:02:49,220 So they're anticipating that you're 74 00:02:49,220 --> 00:02:50,320 going to want to add your own stuff. 75 00:02:50,320 --> 00:02:51,080 Yeah, exactly. 76 00:02:51,080 --> 00:02:52,280 Like they know developers are going 77 00:02:52,280 --> 00:02:54,080 to want to build their own unique features. 78 00:02:54,080 --> 00:02:57,240 So they've built in all these hooks and APIs 79 00:02:57,240 --> 00:03:00,440 so you can seamlessly integrate your own code. 80 00:03:00,440 --> 00:03:01,960 And looking at their community, it 81 00:03:01,960 --> 00:03:03,840 seems like people are taking advantage of that. 82 00:03:03,840 --> 00:03:04,340 Definitely. 83 00:03:04,340 --> 00:03:06,760 Over 640 free add-ons. 84 00:03:06,760 --> 00:03:07,600 That's impressive. 85 00:03:07,600 --> 00:03:08,560 That's a lot. 86 00:03:08,560 --> 00:03:09,080 Yeah. 87 00:03:09,080 --> 00:03:11,120 And speaking of community, the repository 88 00:03:11,120 --> 00:03:13,280 makes it very clear. 89 00:03:13,280 --> 00:03:14,960 NEOs is open source. 90 00:03:14,960 --> 00:03:16,280 Open source, yeah. 91 00:03:16,280 --> 00:03:18,980 What's the big deal about that for developers? 92 00:03:18,980 --> 00:03:22,520 Well, it means the code is basically an open book. 93 00:03:22,520 --> 00:03:26,240 Anyone can see it, understand how it works, even modify it. 94 00:03:26,240 --> 00:03:26,800 Wow. 95 00:03:26,800 --> 00:03:28,600 For developers, this is huge. 96 00:03:28,600 --> 00:03:32,480 It means they can collaborate, contribute back to the project, 97 00:03:32,480 --> 00:03:35,240 even create their own versions of the software. 98 00:03:35,240 --> 00:03:38,600 So it's like a giant group project in a good way. 99 00:03:38,600 --> 00:03:39,260 It is. 100 00:03:39,260 --> 00:03:39,760 It is. 101 00:03:39,760 --> 00:03:42,760 It's all about innovation and shared learning. 102 00:03:42,760 --> 00:03:44,920 So we've got this CMS that's user-friendly, 103 00:03:44,920 --> 00:03:48,800 developer-friendly, and has a strong open source community. 104 00:03:48,800 --> 00:03:49,400 Yeah. 105 00:03:49,400 --> 00:03:51,560 But does it actually work in the real world? 106 00:03:51,560 --> 00:03:52,240 That's a crime. 107 00:03:52,240 --> 00:03:54,000 Does NEOs really deliver? 108 00:03:54,000 --> 00:03:54,880 That's the question. 109 00:03:54,880 --> 00:03:56,000 Let's find out. 110 00:03:56,000 --> 00:03:58,680 Let's look at a real-world example. 111 00:03:58,680 --> 00:04:00,440 One of the case studies is Cornelson. 112 00:04:00,440 --> 00:04:01,320 Cornelson, OK. 113 00:04:01,320 --> 00:04:04,920 They're a big educational publisher. 114 00:04:04,920 --> 00:04:09,400 And they use NEOs to manage hundreds of websites. 115 00:04:09,400 --> 00:04:10,280 Hundreds. 116 00:04:10,280 --> 00:04:10,840 Hundreds. 117 00:04:10,840 --> 00:04:12,080 Oh, that's a lot to juggle. 118 00:04:12,080 --> 00:04:15,440 Each with its own design and content. 119 00:04:15,440 --> 00:04:16,620 That sounds like a nightmare. 120 00:04:16,620 --> 00:04:17,120 Yeah. 121 00:04:17,120 --> 00:04:19,760 It's like herding cats, but with websites. 122 00:04:19,760 --> 00:04:21,000 But with websites, yeah. 123 00:04:21,000 --> 00:04:23,120 But Cornelson's case study shows how NEOs 124 00:04:23,120 --> 00:04:27,280 can handle these big multi-site situations. 125 00:04:27,280 --> 00:04:30,880 You can manage all that content from one central place. 126 00:04:30,880 --> 00:04:31,400 Oh, OK. 127 00:04:31,400 --> 00:04:35,320 While still giving each website its own look and feel 128 00:04:35,320 --> 00:04:36,280 and functionality. 129 00:04:36,280 --> 00:04:39,080 So it's like a conductor leading a massive orchestra. 130 00:04:39,080 --> 00:04:42,000 Everything's playing its part, but it all sounds harmonious? 131 00:04:42,000 --> 00:04:42,480 It does. 132 00:04:42,480 --> 00:04:42,980 It does. 133 00:04:42,980 --> 00:04:44,520 And that's why NEOs is being used 134 00:04:44,520 --> 00:04:46,840 by all sorts of organizations, big and small. 135 00:04:46,840 --> 00:04:49,600 OK, so we've seen how NEOs balances those two sides. 136 00:04:49,600 --> 00:04:53,000 You know, easy for users, powerful for developers, 137 00:04:53,000 --> 00:04:55,380 and it can handle some pretty big projects. 138 00:04:55,380 --> 00:04:58,320 But the digital world never stands still, right? 139 00:04:58,320 --> 00:05:00,240 What about the future of NEOs? 140 00:05:00,240 --> 00:05:01,200 That's right. 141 00:05:01,200 --> 00:05:04,600 Their GitHub is all abuzz about NEOs 9. 142 00:05:04,600 --> 00:05:06,000 NEOs 9, yeah. 143 00:05:06,000 --> 00:05:08,360 And something called an event-sourced content 144 00:05:08,360 --> 00:05:09,760 repository. 145 00:05:09,760 --> 00:05:10,800 Event-sourced. 146 00:05:10,800 --> 00:05:12,560 That sounds pretty techy. 147 00:05:12,560 --> 00:05:13,520 What's the big deal there? 148 00:05:13,520 --> 00:05:14,020 It is. 149 00:05:14,020 --> 00:05:15,480 It's a big step forward. 150 00:05:15,480 --> 00:05:20,280 And this event-sourced content repository, or ESCR, 151 00:05:20,280 --> 00:05:21,400 is at the heart of it. 152 00:05:21,400 --> 00:05:21,900 ESCR. 153 00:05:21,900 --> 00:05:22,480 Yeah. 154 00:05:22,480 --> 00:05:23,360 Think of it like this. 155 00:05:23,360 --> 00:05:27,360 Instead of just storing the latest version of your content, 156 00:05:27,360 --> 00:05:30,000 NEOs actually keeps track of every single change that's 157 00:05:30,000 --> 00:05:30,980 ever been made. 158 00:05:30,980 --> 00:05:36,160 So like a super detailed undo button for your whole website. 159 00:05:36,160 --> 00:05:37,480 That's a good way to put it. 160 00:05:37,480 --> 00:05:41,320 You can go back and see exactly who changed what and when. 161 00:05:41,320 --> 00:05:42,800 That's amazing. 162 00:05:42,800 --> 00:05:44,680 You can literally rewind time. 163 00:05:44,680 --> 00:05:45,480 You can. 164 00:05:45,480 --> 00:05:49,000 So if I accidentally delete something, I just hit undo, 165 00:05:49,000 --> 00:05:50,240 and it's like it never happened. 166 00:05:50,240 --> 00:05:50,920 Too much. 167 00:05:50,920 --> 00:05:52,640 That's almost too good to be true. 168 00:05:52,640 --> 00:05:55,600 It's not magic, but it's close. 169 00:05:55,600 --> 00:05:57,920 Since every change is recorded, you 170 00:05:57,920 --> 00:06:00,360 can step back through the history of your content. 171 00:06:00,360 --> 00:06:02,400 You can revert to any previous state, 172 00:06:02,400 --> 00:06:04,240 and you don't lose any data. 173 00:06:04,240 --> 00:06:05,040 That's incredible. 174 00:06:05,040 --> 00:06:07,960 So it's not just about recovering from mistakes. 175 00:06:07,960 --> 00:06:11,640 It's like you have this incredible control 176 00:06:11,640 --> 00:06:14,360 over how your content evolves. 177 00:06:14,360 --> 00:06:17,760 Yeah, it's about having a detailed version 178 00:06:17,760 --> 00:06:21,520 history for every piece of content on your site. 179 00:06:21,520 --> 00:06:24,080 And I bet that's really useful for analyzing 180 00:06:24,080 --> 00:06:25,320 how things are performing, too. 181 00:06:25,320 --> 00:06:26,520 Oh, absolutely. 182 00:06:26,520 --> 00:06:29,160 You can see how every little tweak affects your engagement 183 00:06:29,160 --> 00:06:29,680 and all that. 184 00:06:29,680 --> 00:06:30,680 Yeah. 185 00:06:30,680 --> 00:06:33,920 You can see how a particular piece of content 186 00:06:33,920 --> 00:06:36,560 has performed over time, and you can see what changes 187 00:06:36,560 --> 00:06:37,720 were made along the way. 188 00:06:37,720 --> 00:06:41,280 It's a goldmine for content editors and marketers. 189 00:06:41,280 --> 00:06:42,800 It's like a content time machine. 190 00:06:42,800 --> 00:06:43,320 It is. 191 00:06:43,320 --> 00:06:47,720 OK, this event source thing is blowing my mind a little bit. 192 00:06:47,720 --> 00:06:49,440 It's pretty powerful stuff. 193 00:06:49,440 --> 00:06:50,840 But what about the developers? 194 00:06:50,840 --> 00:06:54,200 Does this new system mean they have to learn 195 00:06:54,200 --> 00:06:55,680 a whole new set of skills? 196 00:06:55,680 --> 00:06:56,760 That's a good question. 197 00:06:56,760 --> 00:06:59,840 And the good news is that Neos has made this transition 198 00:06:59,840 --> 00:07:01,440 as smooth as possible. 199 00:07:01,440 --> 00:07:06,480 They've got tons of documentation, migration tools, 200 00:07:06,480 --> 00:07:10,360 code examples to help developers get up to speed. 201 00:07:10,360 --> 00:07:13,360 The core principles of Neos, like the custom content 202 00:07:13,360 --> 00:07:16,760 modeling and extensibility that we were talking about, 203 00:07:16,760 --> 00:07:18,240 those are still the same. 204 00:07:18,240 --> 00:07:21,520 So it's like getting a new phone with a faster processor, 205 00:07:21,520 --> 00:07:22,880 but all your apps still work. 206 00:07:22,880 --> 00:07:23,720 Yeah, exactly. 207 00:07:23,720 --> 00:07:25,840 They've improved the core, but it's still 208 00:07:25,840 --> 00:07:28,400 the same familiar experience for developers. 209 00:07:28,400 --> 00:07:30,860 But they've also added new tools specifically 210 00:07:30,860 --> 00:07:33,200 for this event source repository, right? 211 00:07:33,200 --> 00:07:33,840 Oh, yeah. 212 00:07:33,840 --> 00:07:36,840 They've got new tools, new APIs, all designed 213 00:07:36,840 --> 00:07:41,840 to give developers more control and flexibility with how 214 00:07:41,840 --> 00:07:43,480 they manage content. 215 00:07:43,480 --> 00:07:45,120 This is sounding really powerful. 216 00:07:45,120 --> 00:07:45,620 It is. 217 00:07:45,620 --> 00:07:47,200 But what about the practical stuff? 218 00:07:47,200 --> 00:07:50,520 Does it require any special setup or infrastructure? 219 00:07:50,520 --> 00:07:51,960 That's an important point. 220 00:07:51,960 --> 00:07:55,280 While this event source repository 221 00:07:55,280 --> 00:07:58,440 is designed to be scalable and efficient, 222 00:07:58,440 --> 00:08:01,200 it does require some careful thought 223 00:08:01,200 --> 00:08:03,120 about your infrastructure. 224 00:08:03,120 --> 00:08:06,160 Traditional relational databases, 225 00:08:06,160 --> 00:08:08,640 the ones that most websites use, 226 00:08:08,640 --> 00:08:11,920 might not be the best fit for this kind of system. 227 00:08:11,920 --> 00:08:14,560 So you can't just throw it on any old server 228 00:08:14,560 --> 00:08:16,280 and expect it to run smoothly. 229 00:08:16,280 --> 00:08:17,720 Probably not. 230 00:08:17,720 --> 00:08:21,600 NEOs recommends using a database that's specifically 231 00:08:21,600 --> 00:08:24,960 designed for handling lots and lots of event data. 232 00:08:24,960 --> 00:08:26,040 Like what? 233 00:08:26,040 --> 00:08:29,080 Like a document database or a time series database. 234 00:08:29,080 --> 00:08:32,080 It's like choosing the right fuel 235 00:08:32,080 --> 00:08:33,560 for a high performance engine. 236 00:08:33,560 --> 00:08:34,320 Oh, I like that. 237 00:08:34,320 --> 00:08:37,000 You need the right stuff to make it run properly. 238 00:08:37,000 --> 00:08:39,400 So it's not just about picking a hosting provider. 239 00:08:39,400 --> 00:08:40,720 It's about picking the right one. 240 00:08:40,720 --> 00:08:41,280 Exactly. 241 00:08:41,280 --> 00:08:44,440 One that understands this whole event sourcing thing. 242 00:08:44,440 --> 00:08:47,600 You need a hosting partner that can offer 243 00:08:47,600 --> 00:08:50,280 the scalability, the performance, the reliability 244 00:08:50,280 --> 00:08:52,960 that this kind of system needs. 245 00:08:52,960 --> 00:08:55,600 Well, if any of our listeners are looking for that kind 246 00:08:55,600 --> 00:08:58,200 of expertise, I know the place. 247 00:08:58,200 --> 00:09:00,720 Safe Server, they're experts in all things 248 00:09:00,720 --> 00:09:02,120 digital transformation. 249 00:09:02,120 --> 00:09:06,640 You can find them at www.safeserver.d. 250 00:09:06,640 --> 00:09:07,980 Great resource. 251 00:09:07,980 --> 00:09:09,680 Now, before we move on, I want to go back 252 00:09:09,680 --> 00:09:11,920 to something you mentioned earlier, the NEOs community. 253 00:09:11,920 --> 00:09:12,720 The community. 254 00:09:12,720 --> 00:09:17,600 It seems like every time we hit a new challenge with NEOs, 255 00:09:17,600 --> 00:09:19,800 the community pops up as a key resource. 256 00:09:19,800 --> 00:09:21,240 They're amazing. 257 00:09:21,240 --> 00:09:24,000 What is it about this community that makes it so special? 258 00:09:24,000 --> 00:09:28,000 Well, it's a really welcoming group, very active. 259 00:09:28,000 --> 00:09:30,440 And they're all passionate about NEOs. 260 00:09:30,440 --> 00:09:32,020 And they love to help each other out. 261 00:09:32,020 --> 00:09:35,120 You can find them on the forum, in the Slack channel, 262 00:09:35,120 --> 00:09:37,240 even at meetups and conferences. 263 00:09:37,240 --> 00:09:39,480 They're always sharing code, answering questions, 264 00:09:39,480 --> 00:09:41,240 collaborating on new projects. 265 00:09:41,240 --> 00:09:43,640 Like a real sense of shared purpose, right? 266 00:09:43,640 --> 00:09:44,140 It is. 267 00:09:44,140 --> 00:09:44,640 It is. 268 00:09:44,640 --> 00:09:47,640 It makes working with NEOs really enjoyable. 269 00:09:47,640 --> 00:09:49,800 You're not just using a piece of software. 270 00:09:49,800 --> 00:09:51,960 You're part of something bigger. 271 00:09:51,960 --> 00:09:52,640 I love that. 272 00:09:52,640 --> 00:09:54,120 It's like a club. 273 00:09:54,120 --> 00:09:57,100 But for people who love building great websites. 274 00:09:57,100 --> 00:09:58,400 Exactly. 275 00:09:58,400 --> 00:10:00,440 So how do you actually get started with NEOs? 276 00:10:00,440 --> 00:10:03,680 How do you go from this intriguing concept 277 00:10:03,680 --> 00:10:06,160 to an actual working website? 278 00:10:06,160 --> 00:10:07,600 That's a good question. 279 00:10:07,600 --> 00:10:12,120 And the good news is that NEOs has made it really easy 280 00:10:12,120 --> 00:10:13,160 to get started. 281 00:10:13,160 --> 00:10:14,960 They've got a detailed installation 282 00:10:14,960 --> 00:10:16,440 guide on their website. 283 00:10:16,440 --> 00:10:19,180 And they even have this command line tool 284 00:10:19,180 --> 00:10:22,480 that can help you create a new project in minutes. 285 00:10:22,480 --> 00:10:24,720 So it's not like those old school CMSs 286 00:10:24,720 --> 00:10:27,880 where you had to battle with FTP and server configuration. 287 00:10:27,880 --> 00:10:28,560 No, no, no. 288 00:10:28,560 --> 00:10:31,320 NEOs is all about modern development. 289 00:10:31,320 --> 00:10:33,440 So getting started is a breeze. 290 00:10:33,440 --> 00:10:36,520 You can have a basic NEOs instance running 291 00:10:36,520 --> 00:10:39,760 on your computer or a staging server with just a few commands. 292 00:10:39,760 --> 00:10:42,080 And then once you've got that basic setup, 293 00:10:42,080 --> 00:10:44,960 you can start customizing it, adding your own templates, 294 00:10:44,960 --> 00:10:46,600 integrating it with other systems. 295 00:10:46,600 --> 00:10:48,520 That sounds pretty straightforward. 296 00:10:48,520 --> 00:10:49,560 It is. 297 00:10:49,560 --> 00:10:51,760 But I'm guessing there's more to it 298 00:10:51,760 --> 00:10:53,080 than just clicking a few buttons. 299 00:10:53,080 --> 00:10:53,920 Of course. 300 00:10:53,920 --> 00:10:55,580 What are some things people need to think 301 00:10:55,580 --> 00:10:57,840 about when they're first implementing NEOs? 302 00:10:57,840 --> 00:11:01,400 Well, one of the first things is your hosting environment. 303 00:11:01,400 --> 00:11:02,000 OK. 304 00:11:02,000 --> 00:11:04,440 As we talked about before, that event-sourced content 305 00:11:04,440 --> 00:11:09,040 repository, it really benefits from a database that's 306 00:11:09,040 --> 00:11:12,240 designed for all that event data. 307 00:11:12,240 --> 00:11:15,340 So you'll want to choose a hosting provider that 308 00:11:15,340 --> 00:11:20,120 offers the right kind of database and infrastructure. 309 00:11:20,120 --> 00:11:22,080 It's like making sure you've got the right fuel 310 00:11:22,080 --> 00:11:22,760 for your engine. 311 00:11:22,760 --> 00:11:23,560 Exactly. 312 00:11:23,560 --> 00:11:25,480 You wouldn't put regular gas in a Ferrari. 313 00:11:25,480 --> 00:11:26,400 Exactly. 314 00:11:26,400 --> 00:11:27,800 OK, so hosting is important. 315 00:11:27,800 --> 00:11:30,000 What about the development process itself? 316 00:11:30,000 --> 00:11:33,800 Any challenges or best practices that people should keep in mind? 317 00:11:33,800 --> 00:11:39,520 Well, one of Nios's strengths is its flexibility, how extensible it is. 318 00:11:39,520 --> 00:11:39,800 Right. 319 00:11:39,800 --> 00:11:43,000 But with that power comes responsibility, right? 320 00:11:43,000 --> 00:11:43,280 Yeah. 321 00:11:43,280 --> 00:11:49,960 It's important for developers to really embrace the Nios way of doing things. 322 00:11:49,960 --> 00:11:51,240 So use the tools they give you. 323 00:11:51,240 --> 00:11:53,760 Use the tools, use the APIs. 324 00:11:53,760 --> 00:11:54,880 Don't try to fight the system. 325 00:11:54,880 --> 00:11:56,040 Don't try to fight the system. 326 00:11:56,040 --> 00:11:56,680 Exactly. 327 00:11:56,960 --> 00:12:03,480 Nios has, you know, a clear architecture, a set of best practices, and it's all 328 00:12:03,480 --> 00:12:05,800 designed to make development efficient. 329 00:12:05,800 --> 00:12:11,640 So following those guidelines will make your projects more robust, more scalable, 330 00:12:11,640 --> 00:12:14,480 and easier to maintain over time. 331 00:12:14,480 --> 00:12:18,240 It's like learning the rules of the game before you start trying to break that. 332 00:12:18,240 --> 00:12:18,880 Exactly. 333 00:12:18,880 --> 00:12:19,400 Okay. 334 00:12:19,400 --> 00:12:21,040 What about testing and debugging? 335 00:12:21,040 --> 00:12:25,840 Any specific tools or techniques that are especially helpful in a Nios world? 336 00:12:26,360 --> 00:12:32,800 Well, Nios has its own built-in testing framework, so you can, you can write unit 337 00:12:32,800 --> 00:12:35,680 tests for your code, make sure everything's working as it should. 338 00:12:35,680 --> 00:12:39,720 And for, for debugging, you can use standard PHP debugging tools. 339 00:12:39,720 --> 00:12:42,760 Plus Nios has its own logging and error reporting. 340 00:12:42,760 --> 00:12:45,960 And of course, the community forum is a great place to get help. 341 00:12:45,960 --> 00:12:48,360 If you run into any, any tricky problems. 342 00:12:48,360 --> 00:12:49,440 Not like they've got you covered. 343 00:12:49,440 --> 00:12:50,840 They do, they do. 344 00:12:50,840 --> 00:12:55,960 But, but realistically, every software project hits a few snags along the way. 345 00:12:56,040 --> 00:13:00,480 Of course, what are some common pitfalls people encounter with Nios? 346 00:13:00,480 --> 00:13:02,760 And, and is there any way to avoid them? 347 00:13:02,760 --> 00:13:07,880 One common mistake is, is trying to do too much customization too early. 348 00:13:07,880 --> 00:13:12,920 You know, it's, it's tempting to jump in and start building all these fancy 349 00:13:12,920 --> 00:13:19,280 features, but, but it's often better to, to start with a solid foundation using 350 00:13:19,280 --> 00:13:24,120 news news, core features, and then, and then gradually add, add your custom 351 00:13:24,120 --> 00:13:25,000 elements as you go. 352 00:13:25,160 --> 00:13:28,000 So it's like building a house, you know, start with the foundation and the 353 00:13:28,000 --> 00:13:30,680 framing before you start adding the fancy finishes. 354 00:13:30,680 --> 00:13:31,400 Exactly. 355 00:13:31,400 --> 00:13:31,720 Okay. 356 00:13:31,720 --> 00:13:32,240 It makes sense. 357 00:13:32,240 --> 00:13:33,720 What about performance? 358 00:13:33,720 --> 00:13:37,480 I mean, we talked about choosing the right hosting environment, but, but are 359 00:13:37,480 --> 00:13:40,760 there other things developers can do to, to make sure their, their 360 00:13:40,760 --> 00:13:42,200 Nios website is fast? 361 00:13:42,200 --> 00:13:43,120 Oh, absolutely. 362 00:13:43,120 --> 00:13:47,880 Nios has, has a bunch of tools and techniques for optimizing performance. 363 00:13:47,880 --> 00:13:53,240 They've got caching mechanisms, uh, best practices for managing your, your assets, 364 00:13:53,520 --> 00:13:56,080 even integration with, with CDNs. 365 00:13:56,080 --> 00:13:57,840 So you can really, really fine tune it. 366 00:13:57,840 --> 00:13:58,680 You can. 367 00:13:58,680 --> 00:13:58,920 Okay. 368 00:13:58,920 --> 00:14:02,200 So it's, it's not just about throwing more hardware at the problem. 369 00:14:02,200 --> 00:14:06,360 It's about, it's about understanding Nios and, and using its, its 370 00:14:06,360 --> 00:14:07,720 optimization tools the right way. 371 00:14:07,720 --> 00:14:08,240 That's right. 372 00:14:08,240 --> 00:14:12,360 And remember the community is a great resource for, for performance tips. 373 00:14:12,360 --> 00:14:14,120 There's, there's a wealth of knowledge out there. 374 00:14:14,120 --> 00:14:17,000 So don't be afraid to, to ask questions. 375 00:14:17,000 --> 00:14:17,920 Always good advice. 376 00:14:17,920 --> 00:14:21,280 And speaking of valuable resources, a huge thank you to safe 377 00:14:21,280 --> 00:14:22,640 server for supporting this episode. 378 00:14:22,640 --> 00:14:22,880 Yes. 379 00:14:22,880 --> 00:14:23,320 Thank you. 380 00:14:23,680 --> 00:14:27,480 If you're, if you're looking for expert advice on hosting digital 381 00:14:27,480 --> 00:14:32,840 transformation, any of that, you can find them at www.safeserver.d. 382 00:14:32,840 --> 00:14:33,880 Definitely check them out. 383 00:14:33,880 --> 00:14:35,640 We've, we've covered a lot of ground here. 384 00:14:35,640 --> 00:14:36,080 Haven't we? 385 00:14:36,080 --> 00:14:41,160 We have exploring all these different facets of Nio CMS, its features, its 386 00:14:41,160 --> 00:14:46,400 architecture, the community, and even the practical side of, of implementing 387 00:14:46,400 --> 00:14:47,160 and developing with it. 388 00:14:47,160 --> 00:14:47,800 Yeah. 389 00:14:47,800 --> 00:14:51,360 As we wrap things up, I want to leave you with one, one final thought. 390 00:14:52,360 --> 00:14:57,560 Nios is, it's more than just a content management system. 391 00:14:57,560 --> 00:15:02,200 It's, it's a platform for, for innovation, for creativity. 392 00:15:02,200 --> 00:15:08,120 It gives developers the, the power to create these really unique web 393 00:15:08,120 --> 00:15:12,920 experiences and, and it gives content creators the tools they need to manage 394 00:15:12,920 --> 00:15:17,200 their content effectively, whether you're a seasoned developer or, or just starting 395 00:15:17,200 --> 00:15:21,480 out, I encourage you to, to check out Nios and, and see what you can create. 396 00:15:21,720 --> 00:15:22,600 Thanks for joining us. 397 00:15:22,600 --> 00:15:23,440 Thanks for having me. 398 00:15:23,440 --> 00:15:24,200 It's been a pleasure. 399 00:15:24,200 --> 00:15:24,840 Absolutely. 400 00:15:24,840 --> 00:15:26,200 They're, they're really great about that. 401 00:15:26,200 --> 00:15:29,480 There's, there's a forum where you can ask questions. 402 00:15:29,480 --> 00:15:32,680 There's a Slack channel and, and they're even like meetups and 403 00:15:32,680 --> 00:15:35,760 conferences where, where Nios developers get together. 404 00:15:35,760 --> 00:15:38,560 So you're not just, you know, left out in the cold to figure it all out on your own. 405 00:15:38,560 --> 00:15:39,400 No, no, not at all. 406 00:15:39,400 --> 00:15:43,720 And they even offer training courses and workshops if you, if you really 407 00:15:43,720 --> 00:15:49,120 want to go deep and learn best practices for, for building Nios websites. 408 00:15:49,280 --> 00:15:53,080 So they've, they've really built up this whole ecosystem to, to support people 409 00:15:53,080 --> 00:15:54,560 no matter what their skill level is. 410 00:15:54,560 --> 00:15:55,120 They have. 411 00:15:55,120 --> 00:15:55,440 Yeah. 412 00:15:55,440 --> 00:15:58,640 They've, they've put a lot of effort into, into making Nios approachable. 413 00:15:58,640 --> 00:15:59,480 That's awesome. 414 00:15:59,480 --> 00:16:03,240 It's, it's really cool to see that kind of commitment to community. 415 00:16:03,240 --> 00:16:03,600 Yeah. 416 00:16:03,600 --> 00:16:07,400 Speaking of, of pushing the boundaries, let's, let's go back to that event 417 00:16:07,400 --> 00:16:09,440 sourced content repository for a minute. 418 00:16:09,440 --> 00:16:10,480 The E S C R. 419 00:16:10,480 --> 00:16:10,640 Yeah. 420 00:16:10,640 --> 00:16:11,640 The E S C R. 421 00:16:11,640 --> 00:16:12,000 Yeah. 422 00:16:12,000 --> 00:16:16,440 We talked about how it's, it's like having this super detailed history of, of every 423 00:16:16,440 --> 00:16:21,720 change, but, but I'm still trying to wrap my head around what that means in, in 424 00:16:21,720 --> 00:16:22,360 practice. 425 00:16:22,360 --> 00:16:22,960 Yeah. 426 00:16:22,960 --> 00:16:27,080 Can you, can you give me a real world scenario where this would be like a 427 00:16:27,080 --> 00:16:27,800 lifesaver? 428 00:16:27,800 --> 00:16:28,240 Sure. 429 00:16:28,240 --> 00:16:32,880 Imagine you're, you're working on a really important page for your website. 430 00:16:32,880 --> 00:16:38,000 Maybe it's a big product launch or an important announcement and, and someone 431 00:16:38,000 --> 00:16:43,160 accidentally deletes a whole section of text in a traditional system. 432 00:16:43,240 --> 00:16:47,880 You might be, you know, scrambling to restore from backups, hoping you haven't 433 00:16:47,880 --> 00:16:51,280 lost too much work, frantically calling the IT department. 434 00:16:51,280 --> 00:16:51,840 Exactly. 435 00:16:51,840 --> 00:16:57,800 But, but with an event source repository, you can literally rewind time, you can 436 00:16:57,800 --> 00:16:59,280 undo that deletion. 437 00:16:59,280 --> 00:17:05,200 So you're telling me if I delete something, I can just hit undo and it's, it's 438 00:17:05,200 --> 00:17:06,120 like, it never happened. 439 00:17:06,120 --> 00:17:06,720 It is. 440 00:17:06,720 --> 00:17:08,040 That sounds magic. 441 00:17:08,040 --> 00:17:12,760 It's not magic, but, but it's close because, because every change is 442 00:17:12,760 --> 00:17:17,320 recorded as an event, you can, you can literally step back through the history 443 00:17:17,320 --> 00:17:22,480 of your content and see exactly who made each edit and when, so you can, you can 444 00:17:22,480 --> 00:17:26,040 revert to any previous state without, without losing any data. 445 00:17:26,040 --> 00:17:27,320 That's, that's incredible. 446 00:17:27,320 --> 00:17:27,800 It is. 447 00:17:27,800 --> 00:17:31,280 So, so it's not just about, you know, recovering from mistakes. 448 00:17:31,280 --> 00:17:37,280 It's, it's about having this, this amazing level of control over, over how 449 00:17:37,280 --> 00:17:38,800 your content develops over time. 450 00:17:38,800 --> 00:17:39,560 You've got it. 451 00:17:39,560 --> 00:17:42,440 You can even analyze how, how changes affect your engagement. 452 00:17:42,480 --> 00:17:43,200 Absolutely. 453 00:17:43,200 --> 00:17:46,840 You can see how a change impacted, you know, page views or, or conversions. 454 00:17:46,840 --> 00:17:48,480 It's, it's really powerful stuff. 455 00:17:48,480 --> 00:17:48,840 Yeah. 456 00:17:48,840 --> 00:17:50,800 It's like, it's like a content time machine. 457 00:17:50,800 --> 00:17:51,360 It is. 458 00:17:51,360 --> 00:17:51,720 It is. 459 00:17:51,720 --> 00:17:55,800 It turns content management from, from the static process into something 460 00:17:55,800 --> 00:17:58,720 much more, more dynamic and insightful. 461 00:17:58,720 --> 00:17:59,480 Okay. 462 00:17:59,480 --> 00:18:00,720 I'm, I'm sold. 463 00:18:00,720 --> 00:18:04,360 I'm officially geeking out over this, this event source thing. 464 00:18:04,360 --> 00:18:05,240 It's cool stuff. 465 00:18:05,240 --> 00:18:09,640 But, but I'm also wondering about the developers, you know, does this new system 466 00:18:09,640 --> 00:18:15,080 mean that they, they have to learn like a whole new set of skills or use 467 00:18:15,080 --> 00:18:16,200 totally different tools? 468 00:18:16,200 --> 00:18:17,520 That's a fair question. 469 00:18:17,520 --> 00:18:21,480 And, and the good news is that Nios has, has made this transition really, 470 00:18:21,480 --> 00:18:22,680 really developer friendly. 471 00:18:22,680 --> 00:18:23,160 Okay, good. 472 00:18:23,160 --> 00:18:27,440 They've got, um, they've got these guidelines, they've got migration tools. 473 00:18:27,440 --> 00:18:31,920 They even have code examples to help developers, you know, get up to speed 474 00:18:31,920 --> 00:18:36,720 with this, this new model and the core principles of Nios, the custom content 475 00:18:36,720 --> 00:18:40,480 modeling, the extensibility, those are all still the same. 476 00:18:40,480 --> 00:18:45,360 So it's like, like upgrading to a new phone with a faster processor, but all 477 00:18:45,360 --> 00:18:46,760 your apps still work the same way. 478 00:18:46,760 --> 00:18:47,920 That's a great analogy. 479 00:18:47,920 --> 00:18:48,440 Okay, good. 480 00:18:48,440 --> 00:18:51,240 Yeah, they've, they've enhanced the capabilities, but, but it's still a 481 00:18:51,240 --> 00:18:53,120 familiar experience for developers. 482 00:18:53,120 --> 00:18:56,920 That makes sense, but, but they have created some new tools specifically for 483 00:18:56,920 --> 00:18:59,600 working with this, this event sourced repository, right? 484 00:18:59,600 --> 00:19:05,760 They have, they've got, um, new tools and API specifically for interacting 485 00:19:05,760 --> 00:19:13,440 with this repository. So developers have even more control, more flexibility in how 486 00:19:13,440 --> 00:19:13,700 they 487 00:19:13,700 --> 00:19:18,880 manage content. This is sounding really, really impressive. It's a big step forward. 488 00:19:18,880 --> 00:19:18,960 But I'm 489 00:19:18,960 --> 00:19:25,020 also thinking about the practical side of things. Does this new approach require 490 00:19:25,020 --> 00:19:25,140 any 491 00:19:25,140 --> 00:19:32,040 special setup or infrastructure? Yeah, that's a crucial consideration. While this 492 00:19:32,040 --> 00:19:32,580 event 493 00:19:32,580 --> 00:19:37,560 source content repository is built to be really scalable and performant, it does 494 00:19:37,560 --> 00:19:38,880 require some 495 00:19:38,880 --> 00:19:44,640 thought in terms of your infrastructure. Traditional relational databases, the kind 496 00:19:44,640 --> 00:19:45,560 that most websites 497 00:19:45,560 --> 00:19:50,890 use, they might not be the ideal fit for this kind of system. So we might need 498 00:19:50,890 --> 00:19:51,160 something 499 00:19:51,160 --> 00:19:58,790 a little bit more specialized. You might, yeah. NEOs recommends using a database 500 00:19:58,790 --> 00:19:59,260 technology 501 00:19:59,260 --> 00:20:06,740 that's really well suited for this event sourced model. Like what? Like a document 502 00:20:06,740 --> 00:20:07,500 database 503 00:20:07,500 --> 00:20:14,560 or a time series database. These types of databases are designed for handling high 504 00:20:14,560 --> 00:20:15,000 volumes 505 00:20:15,000 --> 00:20:19,680 of data that's constantly being added to, which is exactly what we're talking about 506 00:20:19,680 --> 00:20:25,480 with event sourcing. So it's not just about choosing any random hosting provider. 507 00:20:25,480 --> 00:20:26,140 Right. 508 00:20:26,140 --> 00:20:31,340 You need one that really understands the ins and outs of event sourcing. Exactly. 509 00:20:31,340 --> 00:20:32,260 And ideally 510 00:20:32,260 --> 00:20:37,370 you want a hosting provider that has experience with NEO CMS specifically. So they 511 00:20:37,370 --> 00:20:37,780 can give 512 00:20:37,780 --> 00:20:41,420 you that tailored support, that guidance to make sure everything runs smoothly. To 513 00:20:41,420 --> 00:20:41,620 make 514 00:20:41,620 --> 00:20:46,560 sure you get the most out of NEOs. Well, speaking of valuable resources, you know, 515 00:20:46,560 --> 00:20:47,000 this episode 516 00:20:47,000 --> 00:20:51,570 is sponsored by Safe Server. Yes. And they happen to be experts in hosting and 517 00:20:51,570 --> 00:20:51,900 digital 518 00:20:51,900 --> 00:20:56,430 transformation. They are, yeah. So if you're looking for a reliable partner to help 519 00:20:56,430 --> 00:20:56,500 you 520 00:20:56,500 --> 00:21:05,570 navigate the world of NEOs and event sourcing, you can find them at www.safeserver.d. 521 00:21:05,570 --> 00:21:05,840 Definitely 522 00:21:05,840 --> 00:21:08,500 check them out. Now, before we move on, I want to go back to something you 523 00:21:08,500 --> 00:21:08,820 mentioned 524 00:21:08,820 --> 00:21:13,490 earlier, the NEOs community. Community, yeah. It seems like they play such a huge 525 00:21:13,490 --> 00:21:13,940 role in 526 00:21:13,940 --> 00:21:19,180 making this CMS so, so approachable. They do. Especially for new developers. 527 00:21:19,180 --> 00:21:19,540 Especially 528 00:21:19,540 --> 00:21:24,410 for new folks. Can you tell me a little bit more about what makes this community so 529 00:21:24,410 --> 00:21:25,020 special? 530 00:21:25,020 --> 00:21:31,500 Well, it's really the people. They're so welcoming and helpful, and they're all 531 00:21:31,500 --> 00:21:32,020 really 532 00:21:32,020 --> 00:21:38,710 passionate about NEOs. You can find them on the forum, on Slack, at meetups and 533 00:21:38,710 --> 00:21:40,180 conferences. 534 00:21:40,180 --> 00:21:44,100 They're always willing to share their knowledge, answer questions, help out with 535 00:21:44,100 --> 00:21:44,780 problems. 536 00:21:44,780 --> 00:21:49,620 It's amazing how much a strong community can contribute to an open source project. 537 00:21:49,620 --> 00:21:50,300 It really 538 00:21:50,300 --> 00:21:56,010 does create this feeling of shared ownership. It does, and that sense of community 539 00:21:56,010 --> 00:21:56,420 is one 540 00:21:56,420 --> 00:22:00,550 of the things that makes working with NEOs so enjoyable. It's not just using a 541 00:22:00,550 --> 00:22:00,980 piece 542 00:22:00,980 --> 00:22:05,740 of software. It's being part of something, something bigger. Yeah, I love that. It's 543 00:22:05,740 --> 00:22:12,260 like being a member of a club, but for people who build awesome websites. Exactly. 544 00:22:12,260 --> 00:22:12,500 So how 545 00:22:12,500 --> 00:22:17,800 do you actually get started with NEOs? How do you go from this intriguing concept 546 00:22:17,800 --> 00:22:18,060 to 547 00:22:18,060 --> 00:22:25,620 a working website? Well the good news is that NEOs has made the setup process 548 00:22:25,620 --> 00:22:27,660 really straightforward. 549 00:22:27,660 --> 00:22:32,660 They have a detailed installation guide on their website, and they even have this 550 00:22:32,660 --> 00:22:33,260 command 551 00:22:33,260 --> 00:22:40,270 line tool that can help you create a new NEOs project in minutes. So it's not like 552 00:22:40,270 --> 00:22:40,380 those 553 00:22:40,380 --> 00:22:45,420 old CMSs where you had to wrestle with FTP and server configurations just to get 554 00:22:45,420 --> 00:22:45,500 the 555 00:22:45,500 --> 00:22:50,930 basic framework up and running. No, no, no. NEOs is all about modern development 556 00:22:50,930 --> 00:22:52,320 practices. 557 00:22:52,320 --> 00:22:57,970 So the initial setup is a breeze. You can have a basic NEOs instance running on 558 00:22:57,970 --> 00:22:58,420 your 559 00:22:58,420 --> 00:23:04,440 computer or a staging server with just a few commands. And once you have that 560 00:23:04,440 --> 00:23:05,460 foundation, 561 00:23:05,460 --> 00:23:10,240 you can start customizing it, adding your own templates, integrating it with other 562 00:23:10,240 --> 00:23:10,940 systems. 563 00:23:10,940 --> 00:23:15,440 That sounds pretty straightforward. It is. But I'm guessing there's more to it than 564 00:23:15,440 --> 00:23:15,780 just 565 00:23:15,780 --> 00:23:19,510 clicking a few buttons. Of course, of course. What are some things that people 566 00:23:19,510 --> 00:23:19,900 should think 567 00:23:19,900 --> 00:23:24,810 about when they're implementing NEOs for the first time? Well, one of the first 568 00:23:24,810 --> 00:23:25,700 decisions 569 00:23:25,700 --> 00:23:31,510 you'll need to make is about your hosting environment. Okay. As we discussed 570 00:23:31,510 --> 00:23:32,480 earlier, 571 00:23:32,480 --> 00:23:38,950 the event-sourced content repository in NEOs 9, it can really benefit from a 572 00:23:38,950 --> 00:23:40,100 database that's 573 00:23:40,100 --> 00:23:45,710 specifically designed for handling high-volume event data. So you'll want to choose 574 00:23:45,710 --> 00:23:46,360 a hosting 575 00:23:46,360 --> 00:23:53,570 provider that offers the right type of database and infrastructure to support NEOs 576 00:23:53,570 --> 00:23:55,100 effectively. 577 00:23:55,100 --> 00:23:59,300 So it's like making sure you've got the right fuel for a high-performance engine. 578 00:23:59,300 --> 00:23:59,900 Exactly. 579 00:23:59,900 --> 00:24:04,060 You wouldn't put regular gas in a Ferrari. That's true. You need a hosting 580 00:24:04,060 --> 00:24:04,660 environment 581 00:24:04,660 --> 00:24:12,240 that can keep up with the demands of your NEOs project. So finding the right 582 00:24:12,240 --> 00:24:12,500 hosting 583 00:24:12,500 --> 00:24:18,590 partner is crucial. Yes, it is. But what about the development process itself? Are 584 00:24:18,590 --> 00:24:18,940 there 585 00:24:18,940 --> 00:24:25,220 any particular challenges or best practices that developers should keep in mind 586 00:24:25,220 --> 00:24:26,100 when they're 587 00:24:26,100 --> 00:24:33,760 building with NEOs? Well, one of NEOs' greatest strengths is its flexibility and 588 00:24:33,760 --> 00:24:34,820 extensibility. 589 00:24:34,820 --> 00:24:40,290 Right. But as they say, with great power comes great responsibility. It's important 590 00:24:40,290 --> 00:24:41,260 for developers 591 00:24:41,260 --> 00:24:46,780 to really embrace the NEOs way of doing things. So use the tools they give you. Use 592 00:24:46,780 --> 00:24:47,300 the tools, 593 00:24:47,300 --> 00:24:51,830 use the APIs. Don't try to fight the system. Don't fight the system. Exactly. NEOs 594 00:24:51,830 --> 00:24:52,260 has 595 00:24:52,260 --> 00:24:58,420 a clear architecture. It has a set of best practices, and it's all designed to make 596 00:24:58,420 --> 00:24:59,260 development 597 00:24:59,260 --> 00:25:05,370 efficient and maintainable. So by following those guidelines, developers can create 598 00:25:05,370 --> 00:25:05,820 these 599 00:25:05,820 --> 00:25:12,240 really robust and scalable NEOs projects that are easy to extend and maintain over 600 00:25:12,240 --> 00:25:12,980 time. 601 00:25:12,980 --> 00:25:16,760 It's like learning the rules of the game before you start trying to bend or break 602 00:25:16,760 --> 00:25:17,740 them. Exactly. 603 00:25:17,740 --> 00:25:23,460 Okay, what about testing and debugging? Are there any specific tools or techniques 604 00:25:23,460 --> 00:25:23,500 that 605 00:25:23,500 --> 00:25:29,380 are especially helpful in the NEOs environment? Well, NEOs has a built-in testing 606 00:25:29,380 --> 00:25:30,300 framework 607 00:25:30,300 --> 00:25:37,350 that makes it really easy to write unit tests for your code, which helps ensure 608 00:25:37,350 --> 00:25:38,100 that all 609 00:25:38,100 --> 00:25:43,420 your custom functionality is working correctly. For debugging, you can use standard 610 00:25:43,420 --> 00:25:44,340 PHP debugging 611 00:25:44,340 --> 00:25:51,110 tools along with NEOs' own logging and error reporting mechanisms. And of course, 612 00:25:51,110 --> 00:25:51,540 the community 613 00:25:51,540 --> 00:25:55,620 forum is always a great resource for troubleshooting and getting help from other 614 00:25:55,620 --> 00:25:56,480 developers. 615 00:25:56,480 --> 00:25:59,340 So it sounds like they've really, really thought of everything. 616 00:25:59,340 --> 00:26:03,340 They really have, yeah. But realistically, you know, every software 617 00:26:03,340 --> 00:26:07,480 project runs into some bumps in the road. Of course, of course. 618 00:26:07,480 --> 00:26:14,480 What are some common pitfalls or challenges that people often encounter with NEOs, 619 00:26:14,480 --> 00:26:14,840 and 620 00:26:14,840 --> 00:26:21,080 is there any way to avoid them? One common mistake that I see people make 621 00:26:21,080 --> 00:26:27,180 is trying to do too much customization too early on in the project. 622 00:26:27,180 --> 00:26:32,840 It's tempting to just dive in and start building all these fancy features right 623 00:26:32,840 --> 00:26:33,780 away, but it's 624 00:26:33,780 --> 00:26:42,400 often wiser to start with a really solid foundation, using NEOs' core features, and 625 00:26:42,400 --> 00:26:42,980 then gradually 626 00:26:42,980 --> 00:26:47,660 add custom elements as needed. It's like building a house, right? You start 627 00:26:47,660 --> 00:26:51,980 with the foundation and the framing before you start adding the fancy finishes. 628 00:26:51,980 --> 00:26:57,050 Exactly, and by taking a more iterative approach, you can ensure that your project 629 00:26:57,050 --> 00:26:58,040 stays manageable 630 00:26:58,040 --> 00:27:03,100 and that your custom code works seamlessly with the core NEOs framework. 631 00:27:03,100 --> 00:27:06,820 Makes sense, makes sense. What about performance? I mean, we talked about choosing 632 00:27:06,820 --> 00:27:07,500 the right 633 00:27:07,500 --> 00:27:13,660 hosting environment, but are there other things that developers can do to make sure 634 00:27:13,660 --> 00:27:14,420 their 635 00:27:14,420 --> 00:27:21,180 NEOs website is fast and responsive? Oh, absolutely. NEOs offers a variety of tools 636 00:27:21,180 --> 00:27:26,380 and techniques for optimizing performance. They've got caching mechanisms. They've 637 00:27:26,380 --> 00:27:26,660 got 638 00:27:26,660 --> 00:27:32,150 best practices for managing assets. They even have integration with content 639 00:27:32,150 --> 00:27:33,380 delivery networks. 640 00:27:33,380 --> 00:27:39,220 So you can really fine-tune things? You can. And by implementing those strategies, 641 00:27:39,220 --> 00:27:43,980 you can make sure that your website loads quickly and provides a smooth user 642 00:27:43,980 --> 00:27:45,020 experience. 643 00:27:45,020 --> 00:27:49,460 It's not just about throwing more hardware at the problem. It's about understanding 644 00:27:49,460 --> 00:27:49,620 how 645 00:27:49,620 --> 00:27:57,200 NEOs works and using its built-in optimization tools effectively. Exactly. And 646 00:27:57,200 --> 00:27:57,660 remember the 647 00:27:57,660 --> 00:28:03,100 community is a fantastic resource for sharing performance tips and best practices. 648 00:28:03,100 --> 00:28:03,100 There's 649 00:28:03,100 --> 00:28:08,540 a wealth of knowledge out there. That's great advice. And speaking of valuable 650 00:28:08,540 --> 00:28:09,180 resources, 651 00:28:09,180 --> 00:28:14,020 a big thank you to SafeServer for supporting this episode. Thank you, SafeServer. 652 00:28:14,020 --> 00:28:14,140 If you're 653 00:28:14,140 --> 00:28:19,130 looking for expert guidance on hosting digital transformation or anything in 654 00:28:19,130 --> 00:28:20,100 between, you 655 00:28:20,100 --> 00:28:27,870 can find them at www.safeserver.dd. Well, we've covered a lot of ground in this 656 00:28:27,870 --> 00:28:28,500 deep dive 657 00:28:28,500 --> 00:28:34,420 into Neos CMS. We have. We have. We've explored its features, its architecture, 658 00:28:34,420 --> 00:28:35,620 its community, 659 00:28:35,620 --> 00:28:40,690 and even the nuts and bolts of implementation and development. It's been a great 660 00:28:40,690 --> 00:28:41,460 overview. 661 00:28:41,460 --> 00:28:47,130 As we wrap things up, I want to leave you with one final thought. Okay. Neos is 662 00:28:47,130 --> 00:28:47,540 more 663 00:28:47,540 --> 00:28:52,860 than just a content management system. It is. It is. It's a platform for innovation, 664 00:28:52,860 --> 00:28:57,750 for creativity. It gives developers the power to create truly unique web 665 00:28:57,750 --> 00:28:59,980 experiences. Yeah. 666 00:28:59,980 --> 00:29:04,180 And it provides content creators with the tools they need to manage their content 667 00:29:04,180 --> 00:29:05,100 effectively, 668 00:29:05,100 --> 00:29:09,650 whether you're a seasoned developer or just starting out. I encourage you to 669 00:29:09,650 --> 00:29:10,460 explore the 670 00:29:10,460 --> 00:29:15,380 world of Neos and see what you can create. Thanks for joining us on this deep dive. 671 00:29:15,380 --> 00:29:16,940 Thanks for having me. It's been a pleasure.