 Okay, what's up everyone? So I've been playing around with something I did this I think last week and I think it might be worth sharing just because it'll probably give some people some ideas. So let me tell you a problem, some kind of annoyance that I've had for a while and that is, well, maybe I should give context, right? So my channel is all about applied laziness. It's about, well, a sort of applied laziness with an asterisk on it in the sense that it's all about getting things done and getting things done efficiently, even if that sometimes means a bunch of setup and so that's what the channel is about. When I get down, down and dirty with the stuff I need to do on a daily basis, I want it to happen as quickly as possible, but sometimes you got to do, sometimes you got to install Gen2 before you do it, you know? So anyway, so in my idea here, my idea was, okay, so I have a resume, I have a CV and I also have a website and one thing I noticed I was always doing is I'd want to add something, let's say I had some minor accomplishment and I want to add it to a part of my CV, I'd also want to put it on my website, right? So pretty much, and I realized my website and my CV are basically the same thing, they're really structurally identical. So my crazy idea was why don't I just have basically the same file for both and that is have, you know, I didn't want to have a PDF for a website or something like that or an HTML file for like a CV, but you know, maybe I could take the structure of both of them abstract away and, you know, do what I need to do and, you know, not have to deal with the details. So that's what I did, I think I did this last weekend. So here is the idea. I have one little markdown file. This is effectively my resume and my CV or my resume CV and website right now. It's not my web, I haven't updated my website to have this on it, but this is, I'll put this up on a GitHub repository and you can check it out for your own purposes. So the idea here is I have sections, you know, they have different topics. I have subsections, you know, stuff like this. So classes, classes I taught at the University of Arizona, University of Georgia, stuff like that. All the kind of personal information I have about myself, the details don't matter. And I just have this one markdown file. Now what I do is I have a nice little make file, which you don't actually need a make file. You can just run these commands manually, but I convert this file to an HTML file and a PDF file with special, you know, style with a special style sheet or template to get everything I want. Now let me show you what the end result of this is. I just take that one file and I compile it with a particular style sheet and here, this is what I have. So here is the HTML file. Here's the website portion. So notice some things about it. It's, well, a website is just one big page. We have a nice clickable menu. All of this is totally automatic. This menu up here. So the different sections, so the, you know, big, the ones on top here are generated from the section headings. The ones that, you know, appear below are the subsections or whatever. So I can click on classes or something like this. So I can go down here and some things you can scroll over and they'll have extra information. So, oh, look, teaching evaluation. Let me read that. And this just goes to a PDF on my, like, website or something like that. So the general idea is basically all of that markdown file is just converted to this with a style sheet. So all of, oh, I should say this. So one of the important things is Pandoc has a nice little setting called table of contents and that's actually how I auto generate the nav bar. So what you do, well, let me show you, first off, let me rename this CSS file. If I reload this, this is what it looks like by default, like without the style sheet. But the table of contents option that you can feed Pandoc right here is, excuse me, right here, basically just takes the section headings and it creates this sort of structure here. So that's all really all I need. All I did is I, it labels it with a certain, you know, in certain CSS syntax, and I can, or excuse me, HTML syntax and I can make CSS, you know, traits for all of that stuff. So yeah, all of this is just, again, compiled automatically from, you know, the input. So now I don't really have to worry about any specifics on the website. I just make changes to the markdown file and the nav bar is automatically generated from all this stuff. If I move things around, if I reorder things, reemphasize things, all of that is just automatic. So that's that. Now the PDF portion is not necessarily any less interesting. So I'll pull up the PDF. Now this is a LaTeX PDF without using LaTeX. Well, I mean, I'm not writing it again. This is just based on the markdown file. And I have it, I've given it a separate, let me open up the make file again. So all you have to do is give Pandoc a template and I have a nice little template. And this file here will tell you what you want your sections to look like. Like I want mine to be bold and have this big line. I want my subsections to be in the center, stuff like that. So all the basics are again generated here. So this is exactly the same structurally as the HTML file. I just don't have to, I don't have to like convert it or anything myself. It just does it automatically. So there is, I will say, you know, this stuff I wish I could hide away like these bigger descriptions. I don't know of a way of sort of commenting out so to speak stuff in a LaTeX document or like through Pandoc. I mean there's definitely a way of doing it. But anyway, so on that actually, this template file that you give Pandoc to compile into the LaTeX document, this is I think Pandoc specific kind of syntax. I mean obviously it's LaTeX, but it has I think these ifs and elses are the stuff that are used by Pandoc. And if you want to get one of those, if you want to generate your own LaTeX template, it's actually super easy, you just type in Pandoc D and then LaTeX and that generate that actually spits out the default template. So if I want to do, you know, we'll put that into the file template and then I can make modifications to that. So that's all I did. I just opened this file up, made some changes and you know got what I want added in the different section headings and stuff like that. And that's all you have to do. So again, the idea behind it is just now that I've done all this work, I never have to think about making changes to my CV or my, well I do want to make some changes to the LaTeX template, but I don't really have to think about making changes to my CV and website is two separate things when I actually add something on there. Now I'm thinking of other ways, I think I mentioned on the forum, I'm thinking of other ways of doing sort of a similar paradigm. First off, I'd like, so I have just one page now, I'd like to sort of make a really quick website compiler that can take different, what mark down, I mean of course there are static site generators out there. I just sort of like to do it myself just to, just because whenever I use one of those they never really give me exactly what I want. So it was simple enough to do that. I might do one of, something like that. But on the other hand, another thing I was thinking about, I think I mentioned on the forum, was that I have an RSS feed and it'd be really nice if I could have Pandoc like convert that RSS feed or at least have it show up as a kind of a blog like instead where you have things you can click on, you know, you can show all the text, stuff like that and just sort of a good looking blog template. So if you know about that go ahead and you know give me whatever you got, but I'm probably gonna figure it out myself if you don't. So anyway, I think that's about it. So again just the idea is, you know, minimizing the work I have to do later by doing it all now. But yeah, it's actually really, it's really elegant I guess just having just one little file I can make changes to and I could probably do, I could probably do even crazier stuff with this now that I'm thinking about it. But yeah, that will be for other videos. So anyway, hope you enjoyed it. It'll be on a GitHub repo. So you can check it out yourself. You can do whatever you want with it. But that's all for this time. So I'll see you guys next time.