1 00:00:00,000 --> 00:00:03,520 Before we dive in, just a quick word about our supporter for this Deep Dive, Safe 2 00:00:03,520 --> 00:00:04,200 Server. 3 00:00:04,200 --> 00:00:08,080 They manage the hosting for this software, and they're ready to support you with 4 00:00:08,080 --> 00:00:08,100 your 5 00:00:08,100 --> 00:00:09,940 digital transformation too. 6 00:00:09,940 --> 00:00:16,280 You can find more info at www.safeserver.dst. 7 00:00:16,280 --> 00:00:18,440 Welcome back to the Deep Dive. 8 00:00:18,440 --> 00:00:21,510 Today we're looking at the sources you sent over, and we're going to peel back the 9 00:00:21,510 --> 00:00:21,900 layers 10 00:00:21,900 --> 00:00:24,580 on something called static site generators. 11 00:00:24,580 --> 00:00:25,580 Sounds maybe a bit technical. 12 00:00:25,580 --> 00:00:27,040 Yeah, it can sound that way at first. 13 00:00:27,040 --> 00:00:30,840 But honestly, for your projects, it could be this really empowering shortcut to 14 00:00:30,840 --> 00:00:31,300 getting 15 00:00:31,300 --> 00:00:33,280 your ideas online. 16 00:00:33,280 --> 00:00:37,250 So our mission here is to give you a clear, straightforward understanding, 17 00:00:37,250 --> 00:00:37,940 especially 18 00:00:37,940 --> 00:00:41,540 if you're kind of new to this and just want a simpler way to publish stuff. 19 00:00:41,540 --> 00:00:42,540 Exactly. 20 00:00:42,540 --> 00:00:47,300 And we're zoning in on one specific tool today, a Python-based one called Pelican. 21 00:00:47,300 --> 00:00:48,300 That's the plan. 22 00:00:48,300 --> 00:00:53,480 So for this Deep Dive, we've really dug into the key info from two main places, the 23 00:00:53,480 --> 00:00:53,800 official 24 00:00:53,800 --> 00:00:57,260 Pelican website itself, and also its GitHub repository. 25 00:00:57,260 --> 00:01:02,040 And these give us a really good picture of what Pelican is, how it actually works, 26 00:01:02,040 --> 00:01:02,280 and 27 00:01:02,280 --> 00:01:03,960 importantly, what you can do with it. 28 00:01:03,960 --> 00:01:07,930 We want to be sure you leave this with a really clear sense of why this might be a 29 00:01:07,930 --> 00:01:08,760 great option 30 00:01:08,760 --> 00:01:10,420 for your own website or project. 31 00:01:10,420 --> 00:01:11,660 Okay, sounds good. 32 00:01:11,660 --> 00:01:12,980 Let's unpack this then. 33 00:01:12,980 --> 00:01:17,760 So many of you listening probably have a sense of how lots of websites work, right? 34 00:01:17,760 --> 00:01:22,860 They often have these complex databases running in the background. 35 00:01:22,860 --> 00:01:23,860 Definitely fetching data. 36 00:01:23,860 --> 00:01:27,900 Yeah, talking to servers that are running pretty intricate code. 37 00:01:27,900 --> 00:01:32,140 It's almost like imagine a busy restaurant kitchen, right? 38 00:01:32,140 --> 00:01:36,920 Every dish made fresh to order, ingredients pulled from this huge pantry. 39 00:01:36,920 --> 00:01:38,900 It's powerful, sure. 40 00:01:38,900 --> 00:01:40,300 Definitely powerful for dynamic stuff, yeah. 41 00:01:40,300 --> 00:01:42,320 But it can also be quite daunting to manage. 42 00:01:42,320 --> 00:01:46,440 You need server knowledge, constant updates, security worries. 43 00:01:46,440 --> 00:01:50,480 It feels like you need to be a top chef just to make a simple sandwich sometimes. 44 00:01:50,480 --> 00:01:51,560 That's a good analogy. 45 00:01:51,560 --> 00:01:56,240 So for sites that are mostly about content, like a blog maybe or a portfolio, what 46 00:01:56,240 --> 00:01:56,260 if 47 00:01:56,260 --> 00:01:57,420 there was just a simpler way? 48 00:01:57,420 --> 00:02:01,100 What if you didn't meet all the database stuff or complex server programming? 49 00:02:01,100 --> 00:02:04,900 And what's really interesting is there is a fundamentally simpler way. 50 00:02:04,900 --> 00:02:08,600 And Pelikan, well, it's a perfect example of that whole philosophy is what's known 51 00:02:08,600 --> 00:02:08,700 as 52 00:02:08,700 --> 00:02:10,740 a static site generator. 53 00:02:10,740 --> 00:02:12,020 And it's written in Python. 54 00:02:12,020 --> 00:02:15,700 Its main job is actually brilliantly straightforward. 55 00:02:15,700 --> 00:02:20,420 Instead of that dynamic kitchen, you basically pre-bake everything. 56 00:02:20,420 --> 00:02:21,700 Oh, OK. 57 00:02:21,700 --> 00:02:25,640 You write your website content using simple text files formats like Markdown or 58 00:02:25,640 --> 00:02:26,780 maybe restructured 59 00:02:26,780 --> 00:02:27,780 text. 60 00:02:27,780 --> 00:02:30,570 Think of them as just, you know, enhanced text documents, easy to write in any 61 00:02:30,570 --> 00:02:31,060 editor. 62 00:02:31,060 --> 00:02:32,060 Right. 63 00:02:32,060 --> 00:02:33,060 I use Markdown sometimes. 64 00:02:33,060 --> 00:02:34,060 It's pretty clean. 65 00:02:34,060 --> 00:02:35,060 Exactly. 66 00:02:35,060 --> 00:02:40,180 Then Pelikan takes those text files and just transforms them into a complete ready-to-go 67 00:02:40,180 --> 00:02:41,180 website. 68 00:02:41,180 --> 00:02:44,820 HTML, CSS, JavaScript files, all static. 69 00:02:44,820 --> 00:02:48,700 Static meaning no processing needed on the server when someone visits it. 70 00:02:48,700 --> 00:02:49,700 Precisely. 71 00:02:49,700 --> 00:02:50,700 No static code running. 72 00:02:50,700 --> 00:02:52,940 No database lookups for that page view. 73 00:02:52,940 --> 00:02:54,700 The files are just served as they are. 74 00:02:54,700 --> 00:02:58,640 And the insight here is how that simplicity makes the site inherently more secure, 75 00:02:58,640 --> 00:02:58,940 much 76 00:02:58,940 --> 00:03:02,500 faster and honestly cheaper to host and maintain. 77 00:03:02,500 --> 00:03:03,500 Right. 78 00:03:03,500 --> 00:03:04,500 Because there's less to go wrong, less to manage. 79 00:03:04,500 --> 00:03:05,500 Exactly. 80 00:03:05,500 --> 00:03:09,740 It's a different way of thinking about web architecture, especially for content-heavy 81 00:03:09,740 --> 00:03:10,740 sites. 82 00:03:10,740 --> 00:03:11,980 That does shift the perspective. 83 00:03:11,980 --> 00:03:17,100 So the real sort of magic is turning that simple text into these static files. 84 00:03:17,100 --> 00:03:19,340 HTML, CSS, JavaScript. 85 00:03:19,340 --> 00:03:24,940 Does that mean hosting gets really easy compared to a typical WordPress site or 86 00:03:24,940 --> 00:03:25,460 something? 87 00:03:25,460 --> 00:03:26,460 Oh, absolutely. 88 00:03:26,460 --> 00:03:27,460 Almost trivial sometimes. 89 00:03:27,460 --> 00:03:31,140 I remember spending a whole weekend one time debugging some rogue plugin that 90 00:03:31,140 --> 00:03:31,660 crashed my 91 00:03:31,660 --> 00:03:32,940 simple blog. 92 00:03:32,940 --> 00:03:37,540 Honestly, if I'd known about tools like Pelican back then, it could have saved a 93 00:03:37,540 --> 00:03:38,580 lot of hassle. 94 00:03:38,580 --> 00:03:39,700 We've all been there, I think. 95 00:03:39,700 --> 00:03:43,910 So what does the simplicity mean for you listening right now when you just want to 96 00:03:43,910 --> 00:03:44,700 get your stuff 97 00:03:44,700 --> 00:03:45,700 out there? 98 00:03:45,700 --> 00:03:47,720 It really means less fuss, right? 99 00:03:47,720 --> 00:03:51,180 Less server admin headache and just an easier path to getting published. 100 00:03:51,180 --> 00:03:54,580 And if we look at Pelican's core features, they're all built around this idea. 101 00:03:54,580 --> 00:03:57,460 First, you get what we could call content freedom. 102 00:03:57,460 --> 00:03:58,460 Okay. 103 00:03:58,460 --> 00:04:01,140 Write in your favorite editor, use markdown or restructure text. 104 00:04:01,140 --> 00:04:03,180 They're easy to learn, widely used. 105 00:04:03,180 --> 00:04:05,220 Second, automated generation. 106 00:04:05,220 --> 00:04:08,970 A simple command you run and poof, it rebuilds your site from your text files when 107 00:04:08,970 --> 00:04:09,380 things 108 00:04:09,380 --> 00:04:10,380 change. 109 00:04:10,380 --> 00:04:11,380 Like hitting compile almost. 110 00:04:11,380 --> 00:04:12,380 Sort of, yeah. 111 00:04:12,380 --> 00:04:16,980 But for your website, third, and this is key, easy hosting. 112 00:04:16,980 --> 00:04:21,610 Because the output is just plain static files, HTML, CSS, JS, you'd host it 113 00:04:21,610 --> 00:04:23,140 literally anywhere. 114 00:04:23,140 --> 00:04:28,740 Any basic web server cloud stores like S3, Netlify, GitHub pages, anywhere they can 115 00:04:28,740 --> 00:04:29,220 serve 116 00:04:29,220 --> 00:04:30,220 files. 117 00:04:30,220 --> 00:04:32,140 No special PHP or Python hosting needed? 118 00:04:32,140 --> 00:04:33,140 Nope, not at all. 119 00:04:33,140 --> 00:04:34,140 Yeah. 120 00:04:34,140 --> 00:04:35,140 Just needs to serve files. 121 00:04:35,140 --> 00:04:38,900 And finally, because it is all just files, it's naturally version control ready. 122 00:04:38,900 --> 00:04:43,020 Easy to use with Git, track changes, collaborate, Pelican's own code is on GitHub, 123 00:04:43,020 --> 00:04:43,580 so it fits 124 00:04:43,580 --> 00:04:44,820 right into that workflow. 125 00:04:44,820 --> 00:04:47,610 That version control aspect is huge, especially if you're working with others or 126 00:04:47,610 --> 00:04:48,020 just want 127 00:04:48,020 --> 00:04:49,020 a safety net. 128 00:04:49,020 --> 00:04:50,020 OK. 129 00:04:50,020 --> 00:04:51,020 So that's the solid foundation. 130 00:04:51,020 --> 00:04:52,020 Simple, efficient. 131 00:04:52,020 --> 00:04:55,870 But, you know, often the things that make you really choose a tool are the extra 132 00:04:55,870 --> 00:04:56,360 bits, 133 00:04:56,360 --> 00:04:57,900 the sort of wow factors. 134 00:04:57,900 --> 00:05:02,220 Does Pelican have things like that beyond just the basic text to HTML? 135 00:05:02,220 --> 00:05:03,500 That's a fair question. 136 00:05:03,500 --> 00:05:06,660 And yeah, it does pack quite a few punches beyond the basics. 137 00:05:06,660 --> 00:05:10,650 For instance, it handles both chronological content, your typical blog posts or 138 00:05:10,650 --> 00:05:11,120 articles 139 00:05:11,120 --> 00:05:15,680 ordered by date, and also static pages like an about page or a contact page. 140 00:05:15,680 --> 00:05:16,680 Really smoothly. 141 00:05:16,680 --> 00:05:17,680 Ah, good. 142 00:05:17,680 --> 00:05:18,680 So it's not just for blogs. 143 00:05:18,680 --> 00:05:19,680 Not at all. 144 00:05:19,680 --> 00:05:21,100 And for how it looks. 145 00:05:21,100 --> 00:05:25,060 It uses site themes built with Jinja 2 templates. 146 00:05:25,060 --> 00:05:27,820 Jinja is a pretty popular templating engine in the Python world. 147 00:05:27,820 --> 00:05:28,820 Right. 148 00:05:28,820 --> 00:05:32,740 So that gives you a ton of flexibility to customize the appearance without digging 149 00:05:32,740 --> 00:05:33,440 into Pelican's 150 00:05:33,440 --> 00:05:34,500 core code. 151 00:05:34,500 --> 00:05:36,220 You can really make it look unique. 152 00:05:36,220 --> 00:05:37,220 Nice. 153 00:05:37,220 --> 00:05:39,180 What about reaching a wider audience? 154 00:05:39,180 --> 00:05:43,860 Well, it has built-in support for publishing articles in multiple languages. 155 00:05:43,860 --> 00:05:45,020 Which is quite neat. 156 00:05:45,020 --> 00:05:48,970 It handles the structure needed to serve, say, an English and a Spanish version of 157 00:05:48,970 --> 00:05:49,260 your 158 00:05:49,260 --> 00:05:50,260 site. 159 00:05:50,260 --> 00:05:51,260 Oh wow. 160 00:05:51,260 --> 00:05:52,380 That's actually a big deal for some projects. 161 00:05:52,380 --> 00:05:53,500 It really can be. 162 00:05:53,500 --> 00:05:57,100 It also automatically generates Atom and RSS feeds. 163 00:05:57,100 --> 00:06:00,630 These are those feeds people can subscribe to in feed readers so they get notified 164 00:06:00,630 --> 00:06:00,980 about 165 00:06:00,980 --> 00:06:02,940 your new posts automatically. 166 00:06:02,940 --> 00:06:04,380 Great for building loyal readership. 167 00:06:04,380 --> 00:06:05,900 Essential for blogs, yeah. 168 00:06:05,900 --> 00:06:10,240 And if you're writing about tech, it has code syntax highlighting using a library 169 00:06:10,240 --> 00:06:10,580 called 170 00:06:10,580 --> 00:06:12,060 Pigments. 171 00:06:12,060 --> 00:06:15,460 Makes code snippets in your articles look really clean and readable. 172 00:06:15,460 --> 00:06:19,780 Oh, that's crucial for technical blogs or documentation, definitely. 173 00:06:19,780 --> 00:06:24,420 And another big one, if you're maybe thinking of switching from something else, Pelikan 174 00:06:24,420 --> 00:06:29,840 can actually import existing content from platforms like WordPress, DotClear, or 175 00:06:29,840 --> 00:06:30,100 even 176 00:06:30,100 --> 00:06:31,460 just from RSS feeds. 177 00:06:31,460 --> 00:06:34,040 Seriously, that could save hours of manual work. 178 00:06:34,040 --> 00:06:36,140 It's a huge help for migration, yeah. 179 00:06:36,140 --> 00:06:38,980 And performance-wise, it focuses on fast rebuild times. 180 00:06:38,980 --> 00:06:42,860 It uses caching and only writes out files that have actually changed. 181 00:06:42,860 --> 00:06:46,740 So regenerating the site, even with lots of content, stays pretty quick. 182 00:06:46,740 --> 00:06:47,740 Smart. 183 00:06:47,740 --> 00:06:49,740 Doesn't rebuild everything every single time. 184 00:06:49,740 --> 00:06:50,740 Exactly. 185 00:06:50,740 --> 00:06:53,740 And lastly, if there's something specific you need that isn't built in, there's a 186 00:06:53,740 --> 00:06:54,060 really 187 00:06:54,060 --> 00:06:56,500 rich plugin ecosystem. 188 00:06:56,500 --> 00:06:59,200 Lots of community-contributed plugins to add features. 189 00:06:59,200 --> 00:07:01,580 Or you can write your own if you're comfortable with Python. 190 00:07:01,580 --> 00:07:02,580 Wow. 191 00:07:02,580 --> 00:07:04,100 This list is genuinely impressive. 192 00:07:04,100 --> 00:07:08,180 It starts simple, but there's clearly a lot of power under the hood. 193 00:07:08,180 --> 00:07:12,220 The multi-language support, the importer, those are really practical wins. 194 00:07:12,220 --> 00:07:13,220 They really are. 195 00:07:13,220 --> 00:07:16,530 And I actually stumbled on a little fun fact about the name, speaking of neat 196 00:07:16,530 --> 00:07:17,060 things. 197 00:07:17,060 --> 00:07:19,380 Apparently, Pelican is an anagram. 198 00:07:19,380 --> 00:07:20,380 Of what? 199 00:07:20,380 --> 00:07:21,380 Of a calipin. 200 00:07:21,380 --> 00:07:24,140 It's a French word for a small notebook. 201 00:07:24,140 --> 00:07:25,140 Huh. 202 00:07:25,140 --> 00:07:26,140 That's clever. 203 00:07:26,140 --> 00:07:28,420 A little nod to organizing your notes into a site. 204 00:07:28,420 --> 00:07:29,420 I like that. 205 00:07:29,420 --> 00:07:30,420 Yeah, me too. 206 00:07:30,420 --> 00:07:35,100 All right, so we've established Pelican is powerful, versatile, sounds great. 207 00:07:35,100 --> 00:07:38,060 But the big question for a lot of listeners, especially the beginners we're 208 00:07:38,060 --> 00:07:38,780 thinking about 209 00:07:38,780 --> 00:07:42,660 today is, can I actually use this? 210 00:07:42,660 --> 00:07:46,940 How easy is it to get started if you're maybe not super technical? 211 00:07:46,940 --> 00:07:48,860 That's the crucial question, isn't it? 212 00:07:48,860 --> 00:07:51,940 And the answer is, it's designed to be pretty accessible. 213 00:07:51,940 --> 00:07:55,990 The official quick start guide really aims to get you going quickly, even if maybe 214 00:07:55,990 --> 00:07:56,260 you 215 00:07:56,260 --> 00:07:58,340 haven't used the command line much before. 216 00:07:58,340 --> 00:07:59,540 Okay, let's hear it. 217 00:07:59,540 --> 00:08:00,700 Let's talk us through it. 218 00:08:00,700 --> 00:08:05,440 Imagine I'm, say, a student wanting a simple portfolio or someone starting a hobby 219 00:08:05,440 --> 00:08:06,040 blog. 220 00:08:06,040 --> 00:08:08,020 How do I go from zero to seeing something? 221 00:08:08,020 --> 00:08:09,020 Right. 222 00:08:09,020 --> 00:08:10,020 So step one is installation. 223 00:08:10,020 --> 00:08:14,060 Assuming you have Python on your computer, which many systems do, or it's easy to 224 00:08:14,060 --> 00:08:14,220 install, 225 00:08:14,220 --> 00:08:16,300 you just open your terminal or command prompt. 226 00:08:16,300 --> 00:08:17,300 Okay. 227 00:08:17,300 --> 00:08:18,300 That black window thing? 228 00:08:18,300 --> 00:08:19,300 Yep. 229 00:08:19,300 --> 00:08:23,980 You type this command, python-m pip install pelican markdown. 230 00:08:23,980 --> 00:08:24,980 You hit enter. 231 00:08:24,980 --> 00:08:27,760 Pip is Python's package installer. 232 00:08:27,760 --> 00:08:32,050 This usually takes less than a minute, and it downloads and installs Pelican and 233 00:08:32,050 --> 00:08:32,340 the 234 00:08:32,340 --> 00:08:33,780 bits needed for markdown. 235 00:08:33,780 --> 00:08:34,780 Okay. 236 00:08:34,780 --> 00:08:35,780 Pip install pelican markdown. 237 00:08:35,780 --> 00:08:36,780 Got it. 238 00:08:36,780 --> 00:08:37,780 Step two, you create your project. 239 00:08:37,780 --> 00:08:41,980 So you make a new folder somewhere for your website, let's call it MyAwesomeSite. 240 00:08:41,980 --> 00:08:44,740 You navigate into that folder in your terminal. 241 00:08:44,740 --> 00:08:45,980 Using CD probably? 242 00:08:45,980 --> 00:08:46,980 Exactly. 243 00:08:46,980 --> 00:08:47,980 Using CD MyAwesomeSite. 244 00:08:47,980 --> 00:08:51,220 Then right there, you type pelican quickstart and hit enter. 245 00:08:51,220 --> 00:08:52,220 Pelican quickstart. 246 00:08:52,220 --> 00:08:53,220 Okay. 247 00:08:53,220 --> 00:08:55,650 This command starts a little interactive questionnaire that'll ask you things like, 248 00:08:55,650 --> 00:08:56,100 what's the title 249 00:08:56,100 --> 00:08:57,100 of your site? 250 00:08:57,100 --> 00:08:58,180 What's the author? 251 00:08:58,180 --> 00:09:00,280 And importantly, what's the main URL going to be? 252 00:09:00,280 --> 00:09:05,020 Like https.my-awesome-site.com or whatever. 253 00:09:05,020 --> 00:09:06,300 You just answer the questions. 254 00:09:06,300 --> 00:09:08,900 And it sets up the folders and basic files for me. 255 00:09:08,900 --> 00:09:09,900 Precisely. 256 00:09:09,900 --> 00:09:12,880 Creates the basic structure, like a content folder for your articles, an output 257 00:09:12,880 --> 00:09:13,260 folder 258 00:09:13,260 --> 00:09:16,580 for the generated site, a settings file, all ready to go. 259 00:09:16,580 --> 00:09:17,580 Okay. 260 00:09:17,580 --> 00:09:18,580 Structures there. 261 00:09:18,580 --> 00:09:19,580 Now, the actual content. 262 00:09:19,580 --> 00:09:21,020 Step three. 263 00:09:21,020 --> 00:09:22,180 Write your first article. 264 00:09:22,180 --> 00:09:23,180 You just open. 265 00:09:23,180 --> 00:09:27,540 The text editor could be notepad, VS code, supplying text, anything. 266 00:09:27,540 --> 00:09:30,880 You create a new file inside that content folder it made. 267 00:09:30,880 --> 00:09:32,740 Let's call it firstpost.md. 268 00:09:32,740 --> 00:09:33,740 The MD is for Markdown. 269 00:09:33,740 --> 00:09:34,740 Right. 270 00:09:34,740 --> 00:09:38,540 Inside that file, you put a few lines at the very top for metadata. 271 00:09:38,540 --> 00:09:43,100 Like my first post, 20, 23, 10, 27, 0.00. 272 00:09:43,100 --> 00:09:44,100 Scalica. 273 00:09:44,100 --> 00:09:45,100 Musings. 274 00:09:45,100 --> 00:09:49,020 Then just below that, you start writing your actual article content using Markdown 275 00:09:49,020 --> 00:09:49,700 formatting. 276 00:09:49,700 --> 00:09:52,380 You know, like this is my first post using Pelican. 277 00:09:52,380 --> 00:09:53,380 That's pretty cool. 278 00:09:53,380 --> 00:09:54,380 Simple enough. 279 00:09:54,380 --> 00:09:55,660 Title, date, category, then the text. 280 00:09:55,660 --> 00:09:56,660 Exactly. 281 00:09:56,660 --> 00:09:57,900 And step four, the payoff. 282 00:09:57,900 --> 00:09:59,100 Preview your site. 283 00:09:59,100 --> 00:10:00,340 You go back to your terminal. 284 00:10:00,340 --> 00:10:02,420 Make sure you're still in your main project folder. 285 00:10:02,420 --> 00:10:03,460 My awesome site. 286 00:10:03,460 --> 00:10:05,260 And you type Pelican Nessure RL. 287 00:10:05,260 --> 00:10:06,260 Pelican Nessure RL. 288 00:10:06,260 --> 00:10:08,020 What does the RRN do? 289 00:10:08,020 --> 00:10:09,020 Good question. 290 00:10:09,020 --> 00:10:12,420 That R tells Pelican to keep running and automatically regenerate the site if you 291 00:10:12,420 --> 00:10:13,340 change any content 292 00:10:13,340 --> 00:10:14,340 files. 293 00:10:14,340 --> 00:10:17,180 And Desk tells it to launch a simple local web server so you can view the site. 294 00:10:17,180 --> 00:10:18,180 Ah. 295 00:10:18,180 --> 00:10:19,180 Handy. 296 00:10:19,180 --> 00:10:20,180 So it builds it and serves it locally. 297 00:10:20,180 --> 00:10:21,180 Yep. 298 00:10:21,180 --> 00:10:24,610 So it builds the site into the output folder and then usually say something like, 299 00:10:24,610 --> 00:10:24,820 serving 300 00:10:24,820 --> 00:10:28,340 site at http.localhost.800. 301 00:10:28,340 --> 00:10:31,320 You just open your regular web browser, go to that address. 302 00:10:31,320 --> 00:10:33,540 And I should see my site. 303 00:10:33,540 --> 00:10:34,540 With my first post. 304 00:10:34,540 --> 00:10:38,380 You should see your brand new site using the default theme initially with my first 305 00:10:38,380 --> 00:10:38,700 post 306 00:10:38,700 --> 00:10:39,700 right there. 307 00:10:39,700 --> 00:10:41,500 It's usually a real aha moment. 308 00:10:41,500 --> 00:10:42,500 OK. 309 00:10:42,500 --> 00:10:47,100 Those four steps, install, quick start, write a file, preview. 310 00:10:47,100 --> 00:10:49,260 That does sound genuinely manageable. 311 00:10:49,260 --> 00:10:52,790 It really lowers the barrier to just getting something up and running quickly, 312 00:10:52,790 --> 00:10:53,220 which is 313 00:10:53,220 --> 00:10:55,340 fantastic for learning and experimenting. 314 00:10:55,340 --> 00:10:56,340 That's the whole idea. 315 00:10:56,340 --> 00:10:57,720 Get you focused on content quickly. 316 00:10:57,720 --> 00:11:02,520 Now, if someone does run into a little snag or wants to go beyond that basic setup, 317 00:11:02,520 --> 00:11:02,700 where 318 00:11:02,700 --> 00:11:04,300 does the community aspect come in? 319 00:11:04,300 --> 00:11:05,780 You mentioned it's open source. 320 00:11:05,780 --> 00:11:06,780 Right. 321 00:11:06,780 --> 00:11:07,780 And that's a huge strength. 322 00:11:07,780 --> 00:11:09,800 Pelican is fundamentally an open source project. 323 00:11:09,800 --> 00:11:13,460 It lives on GitHub and it's pretty active looking at the stats. 324 00:11:13,460 --> 00:11:17,740 It has over 13,000 stars, about 1800 forks. 325 00:11:17,740 --> 00:11:18,900 That's quite a lot. 326 00:11:18,900 --> 00:11:20,500 That indicates a healthy user base. 327 00:11:20,500 --> 00:11:21,500 Definitely. 328 00:11:21,500 --> 00:11:24,420 It means people are using it, interested in it, contributing to it. 329 00:11:24,420 --> 00:11:27,670 So for you as a user, that means the code is well tested and there's a community 330 00:11:27,670 --> 00:11:27,980 around 331 00:11:27,980 --> 00:11:28,980 it. 332 00:11:28,980 --> 00:11:31,720 If you hit a problem, chances are someone else has too. 333 00:11:31,720 --> 00:11:34,600 And there might be a solution on an issue tracker or forum. 334 00:11:34,600 --> 00:11:35,660 And the license. 335 00:11:35,660 --> 00:11:38,300 It's licensed under the AGPL 3.0. 336 00:11:38,300 --> 00:11:42,940 That's a strong copy left license, ensuring it stays free and open source. 337 00:11:42,940 --> 00:11:47,810 And if you peek under the hood, it's mostly Python, about 89%, then some CSS and 338 00:11:47,810 --> 00:11:48,220 ginger 339 00:11:48,220 --> 00:11:49,220 for templating. 340 00:11:49,220 --> 00:11:50,220 Okay. 341 00:11:50,220 --> 00:11:52,860 So a strong open source foundation. 342 00:11:52,860 --> 00:11:56,730 If our listeners are thinking, okay, I want to try this or maybe even, hey, I could 343 00:11:56,730 --> 00:11:57,060 help 344 00:11:57,060 --> 00:11:58,060 out. 345 00:11:58,060 --> 00:12:01,020 What are the best places to go for help or to get involved? 346 00:12:01,020 --> 00:12:02,020 Great question. 347 00:12:02,020 --> 00:12:03,300 There are several avenues. 348 00:12:03,300 --> 00:12:07,540 First stop for almost any question should be the official Pelican documentation. 349 00:12:07,540 --> 00:12:12,150 It's really comprehensive, well written, covers everything from the basics right up 350 00:12:12,150 --> 00:12:13,020 to advanced 351 00:12:13,020 --> 00:12:14,860 customization and plugin development. 352 00:12:14,860 --> 00:12:16,900 Always good to have solid docs. 353 00:12:16,900 --> 00:12:17,900 Absolutely essential. 354 00:12:17,900 --> 00:12:22,140 Then if you want to actually contribute back, you can do that on GitHub. 355 00:12:22,140 --> 00:12:25,980 You could submit pull requests if you find a bug and fix it, or if you add a new 356 00:12:25,980 --> 00:12:26,740 feature. 357 00:12:26,740 --> 00:12:31,290 You could help triage issues that other people report, confirming bugs, asking for 358 00:12:31,290 --> 00:12:32,300 more info, 359 00:12:32,300 --> 00:12:37,140 or a really valuable way to help is by improving the documentation itself. 360 00:12:37,140 --> 00:12:39,020 Clearer docs help everyone. 361 00:12:39,020 --> 00:12:41,820 That's often overlooked, but yeah, it's so important. 362 00:12:41,820 --> 00:12:45,030 If you just want to support the project financially, keep the development going, 363 00:12:45,030 --> 00:12:45,660 you can donate 364 00:12:45,660 --> 00:12:50,420 to the Pelican dev team, they have links on their site, like donate.getpelican.com, 365 00:12:50,420 --> 00:12:50,420 or 366 00:12:50,420 --> 00:12:53,260 they're on platforms like LibrePay. 367 00:12:53,260 --> 00:12:56,140 Every little bit helps maintain and improve the tool. 368 00:12:56,140 --> 00:12:59,540 And we should also mention, one of the project's key supporters is Fortressa 369 00:12:59,540 --> 00:13:00,620 companies sponsoring 370 00:13:00,620 --> 00:13:02,940 open source like this makes a real difference. 371 00:13:02,940 --> 00:13:04,540 Definitely good to acknowledge the supporters. 372 00:13:04,540 --> 00:13:08,880 Okay, so wrapping things up a bit, we've taken this deep dive into Pelican. 373 00:13:08,880 --> 00:13:12,060 It's a static site generator written in Python. 374 00:13:12,060 --> 00:13:16,540 The big takeaway seems to be how it simplifies getting a website online. 375 00:13:16,540 --> 00:13:18,060 You write in simple text files. 376 00:13:18,060 --> 00:13:19,060 Like Markdown. 377 00:13:19,060 --> 00:13:20,060 Right. 378 00:13:20,060 --> 00:13:21,060 Like Markdown. 379 00:13:21,060 --> 00:13:23,280 Pelican turns them into a full HTML website. 380 00:13:23,280 --> 00:13:26,020 No complex database needed on the live site. 381 00:13:26,020 --> 00:13:29,460 No tricky server-side code just to display your content. 382 00:13:29,460 --> 00:13:33,410 It feels really accessible, powerful too, especially if you're starting out and 383 00:13:33,410 --> 00:13:33,700 want 384 00:13:33,700 --> 00:13:37,260 a blog or a portfolio without the usual backend headaches. 385 00:13:37,260 --> 00:13:38,260 Yeah. 386 00:13:38,260 --> 00:13:41,300 It puts the power back in your hands, focusing you on the content. 387 00:13:41,300 --> 00:13:45,170 What's really fascinating to me here is just that core idea of static generation 388 00:13:45,170 --> 00:13:46,260 itself. 389 00:13:46,260 --> 00:13:50,480 How tools like Pelican strip away all those layers of complexity we often associate 390 00:13:50,480 --> 00:13:50,820 with 391 00:13:50,820 --> 00:13:51,820 websites. 392 00:13:51,820 --> 00:13:52,820 Exactly. 393 00:13:52,820 --> 00:13:55,960 It makes things simpler, faster, more secure in many cases. 394 00:13:55,960 --> 00:13:59,220 It really lowers the barrier for anyone who just wants to publish something online. 395 00:13:59,220 --> 00:14:03,350 It makes a solid web presence feel much more achievable, regardless of how 396 00:14:03,350 --> 00:14:04,220 technical you 397 00:14:04,220 --> 00:14:05,220 are. 398 00:14:05,220 --> 00:14:06,220 It's quite empowering. 399 00:14:06,220 --> 00:14:07,220 It really is. 400 00:14:07,220 --> 00:14:11,620 And that leads to maybe a final thought for you, the listener. 401 00:14:11,620 --> 00:14:16,100 Now that you know how accessible static site generation can be with tools like Pelican, 402 00:14:16,100 --> 00:14:18,340 what new possibilities does that open up? 403 00:14:18,340 --> 00:14:20,060 Is it that blog you've been meaning to start? 404 00:14:20,060 --> 00:14:22,060 A simple site for a side project? 405 00:14:22,060 --> 00:14:24,200 Maybe documentation for something you're building? 406 00:14:24,200 --> 00:14:25,440 The tools are there? 407 00:14:25,440 --> 00:14:27,420 And maybe simpler than you thought. 408 00:14:27,420 --> 00:14:31,100 And before we go, once again, a huge thank you to our supporter, SafeServer. 409 00:14:31,100 --> 00:14:34,480 For all your hosting needs and digital transformation support, remember to check 410 00:14:34,480 --> 00:14:36,900 them out at www.SafeServer.de.