 Hello, everyone, and welcome to this week's Bite Size Talks. With me is Matthias. He is working at the data center of SILAP Lab and is also our infrastructure guru. And today he is going to talk about the new blog of NFCore. And off to you. Yes. Thank you very much. Hello, everybody. Yes, NFCore blog. You might have seen this blue little dot on the about page that we are now part of the blogosphere. Back to the early 2000s blog of the new cool thing. And yes, if you just go to NFCore slash blog, you'll find the initial blog posts. There will be more coming soon. And also it's a real blog. So we also have an RSS feed. And this RSS feed is also piped into the NFCore posts slack channel. So if you don't want to regularly look on that page, but still want to know when there's a new post, we will write probably also in the announcement channels. But every post will also be coming up in that channel automatically. Yes, with that, OK, so we have the blog. But why do we actually need a bloggers NFCore? And actually a long process and part of the whole website rewrite, Phil was always talking about, we should have a blog. We should have a blog. And other people were like, hey, why did you as NFCore decide this and this thing? And then we didn't really have a platform, except for the announcement channel to kind of write down. But once like it's a bit difficult sometimes to write longer texts. So we needed a place to write longer texts. Also maybe with some screenshots and everything nicely ordered, which should be like documentation because it's more time sensitive. But yeah, something like a blog maybe. Also for events like hackathons, we didn't really have a place to kind of share what we did during the hackathon. That was like the video, the wrap up video. But usually the photos are taken, stuff happens, and it just disappears. So with this, we hope you can also capture that a bit. Also like from us, from the infrastructure place, it is nice when we add stuff to tools that we have a place to kind of show it off a bit more besides the announcements or the tools channel. And also to the wider community, like if you have a bigger pipeline release with like a big new feature or something like that, would be a place, we can imagine, to post about it on a blog or other community-related things you think should be on a blog. So yeah, this is why we now have this platform and how do you add stuff to it? Well, you make similar to how you get a new NFCore pipeline. You make a proposal and new blog posts as like channel. You don't have to provide a tube map for this. You can just write down what you would like to have. Then if you get some thumbs up, you can make a card on our project board. It's the blog post project board on GitHub, on the GitHub organization. Then you assign yourself to this topic and you open a PR and that's it. How should this PR look like? Well, you know our website, it's Markdown. It's Markdown everywhere. Actually, it's Markdown and MDX. So to the MDX part later a bit more. But first, yes, you write a Markdown file. When you write it, it should be in the slash blog and then slash year directory and the contents directory. And then you write your Markdown and it needs this special front meta you see here, where some things as usual are required, some are not required. No worries too much about this. We have some sanity checks. So if you try to build your page with something missing or something incorrect, it will just not build. So you will not break anything. It will just not appear on your development platform. But let's quickly go through the front meta. So this is separated by three minus signs from the actual rendered Markdown text. You have the title and the subtitle, which is quite clear. Then you have an header image, which is like you saw before. Just an image which appears in the car, but also then in the blog post. There is then a requirement implemented that if you have an image, here for example, you can just use unsplash. You need to also have an alt text. So we make it a bit more accessible the whole thing. So that is something we check. If you have an image, you also need to have an alt text. Then also very important is the publication date, because that's when the Markdown is actually coming up on the website. It needs to be in this very nice iso format. So keep in mind, all the UTC offsets and stuff like that needs to be correct there. Otherwise something will be off. And then the authors where you just write an YAML array with your GitHub user names, which are then nicely rendered in all the different places. And also we have optionally a field for labels. We don't have so many posts yet to actually need filtering. But in the future, we are thinking of using these labels to filter your posts into different sections. And yes, and then you just write Markdown. And it is, of course, not just Markdown. It's the NFCORE flavor of Markdown. So you can write some callouts or admonitions. You can have fancy code blocks with file titles, highlighted lines, line numbers, whatever you want. And also you can use MDX. So you can take whatever component we have on the website, add it into your Markdown, and get it rendered. That was too fast. Sorry for that. Yes, main authors for this block are, of course, the core team and the outreach team, but also maintainers in general. And whoever in the community wants to contribute to it. We are quite open. Who wants to write, we, of course, don't really want too much advertisements for companies there. But in general, if it's of interest for the NFCORE community, I think we're pretty open to certain entries there. And when you then write your blog post, how can you actually look at it? There are two ways. The first one is more, I think, the easier one. Just on your local machine, run npm, run def, then go to the blog site on the local host. And you should see your blog post appear there. If you set the date correctly, be aware about the publication date. And also, then, when you submit the OPR, it will be built. And if the publication date is in time, it should also appear there. Yes, with that, are there any questions this whole new initiative of the NFCORE block? Well, this was very quick. You know my binds us talks. They are really bite-sized. Could you maybe elaborate a bit more about the publication date? Where do you give this publication date? Yes, so it is the front matter of the O. So here you just have pub date, which is then rendered. And if the current date is after this date, it will appear on the site. So if you want to actually schedule something for the future but still want to preview it, you need to first change that. I guess you could also change the local time on your machine. But maybe it's easier if you just change the public date to one day before. It actually should be published. And then don't forget to move it back. Otherwise it will be live. And as usual, our sites are built twice per day at 9 o'clock in the morning and 2 o'clock in the morning. And after this, they will appear. So they don't appear at midnight. If you said midnight there, they will appear the next build because everything is statically built. Cool. We also have a question in the chat from Bill. Do you have any ideas in queue for the block to give an idea of the kinds of topics we expect? Yes. So we have some like, I know that Satish, for example, is working on a bigger blog post about NF tests, about all the different fun things we want to do with NF tests, also a bit to support the documentation that we have a bit more of our reasoning for NF tests and how we see NF tests used. And that is one idea. Then other community events happening or surrounding NF core are also planned out. Another question is, how can I see updates? And do they go to Slack? Yes. As mentioned, there is the Slack, sorry. There's the Slack channel NF core posts and also the RSS feed. So with that, you can automatically announce that. Also, you have the blue dot on the website for one day after the post goes live. There's a blue dot here. And if you open next to the blog section, there is a new post. Actually, if you want to find the blog and don't remember the URL, it's in the about section. And the last question, when should stuff be a blog post? And when should it actually go in docs? That's a good question. And I think that's also something we ourselves need to find out a bit. But I think if it's more like time specific, it should be a blog post or also a bit less like less for a general audience, but more for some specific things. I think the blog post will be more helpful. And the docs should be more for general things. Right. But there could also be something that is both a blog post and docs. Yes. Or yes. Cool. Do we have any more? There's one more. No, it says blog posts don't need to be kept up today. That's correct. Yes. So blog post is just up to date at the moment it's published. Afterwards, it's updated. While the docs, of course, are always up to date. Right. People could also unmute themselves. I was a bit taken aback for how short it was, so I couldn't in time allow this. But if anyone has another question, they could, of course, also unmute themselves now. But yes, everything is still quite new. So we are also still thinking this platform out a bit. But it will, I think, also be fun and helpful to have this new way to document things, not like code documentation, but also like event documentation, which we were missing. I feel like, and of course. So if there are no more questions from the audience, which it seems like, then I would like to thank you for this talk. And as usual, Dijon Zuckerberg for Funding Bites I Stalks. And you all for listening into this Bites I Stalk in particular. Thank you very much. Bye.