 Florian asks, I want to use the news articles in SharePoint. Ooh, lowercase p in SharePoint. That's a problem. Oh, that's a demand. They're news articles in SharePoint for internal documentations. Is it possible to create something like a copy of that site template and adding a custom entry to the menu like new documentation? And is it also possible to filter the news web part based on a custom column of my site and adding the entry to this column in a simple way when adding a new article? This is one of my favorite tricks. I actually did a Tip Tuesday on this, the filtering part of it. But I love to take things like HR documentation and convert them into pages so that it's not just a doc, like a 250 page employee manual. Here's the employee manual broken out into specific topics on pages and then a link with the PDF version as a resource if they need to have the printable version because it's easier to keep up, it's always live, and it's more searchable than a PDF document. And then I use a custom column and the gotcha is that you can only use those custom columns as a filter in that site. It's not cross-site, it's only in that site. So you can, it's a custom property is what you filter by. And I always create one called newsfeed. And then in my different news web parts filter by whatever's in that newsfeed. Those are my tricks, but I did do a Tip Tuesday on that. I can give you a link to that if you want to. So I wonder why they're going with news page and not just a site page. What would the rationale be for that? Well, site pages are news pages. They're just designated as news. And I like those because it's hard enough to keep your SharePoint sites fresh with new information. Every year you can recycle because you may have new people just take that same news. And now it's just another, did you know? And we have this, here's our education benefit or here's what we offer as far as leave options or things that you can just recycle on your site as news. And I think as long as they weren't putting that on the homepage where there's actually news news and article news, that would be fine. So a dedicated site perhaps or a site where the topic's a little bit different than all company news. I do appreciate the question. A copy of that site template, not exactly but you can have an additional site and have news. Yeah, you can have news web parts anywhere you want to but to have it say new documentation don't know of a way to edit the default labels inside of a web part modern. So what you may just need to do is just have a text above the web part instead of showing the web part title. So it doesn't say news or something like that. You could do something very fancy there, very fancy. I'm sorry, very fancy does not apply to that but different and just explain to folks that it's out of the box. That's what you have unless I'm looking at you now you go to an app and you utilize an app to kind of capture some of this. I've had customers over the past that went to the Power Platform and they used a Power app to host their documentation and create it, search it and then make it findable utilizing a list in the background. That's interesting. One of the things that came to mind when I was hearing the question for the first time is they're talking about templating, reusability. I believe we have that functionality inside of a site page. They could create their own page template. I think it might be able to be leveraged as a news article as well, but they could put their corporate branding, their standard layouts and have some reusability there. And then now Sherry brought up adding the custom column and having those custom like news article attributes and the other metadata attributes that are there. But there's something else we can do if it was going to scale beyond the site and we would use a metadata term store, which is a mouthful to say, but basically it's that same custom column, but held at a much higher level that your SharePoint administrator could help facilitate. And so creating that type of taxonomy for the organization is something that you could just leverage in one site or across multiple sites to have consistency in what you're calling those columns or those values. But it's interesting that this, I mean, these problems, these fundamental problems around documentation have existed for my 32 years in tech. In the late 90s, I mean, one of the things we started using is a software configuration management. So code management software with the branching and labeling, but to manage the complexity of the documentation and break it up in a way just like what we're talking about. So it's not all in one single doc and harder to search and to go and edit and have it broke out by the outline the various components. So then you can assign to somebody to update this section or the rest of the documentation, doesn't need to be touched if there are no changes to it, but just that relevant section that needs to be updated can be modified and have its own history around that. But it's, these are the same fundamental issues that organizations are asking for around documentation. As old as SharePoint itself. All the old, yeah, before that, but it's all the old problems are all new, just new people. We worried about this most, those people that I worked with on these problems back in the 90s have all retired and the new generation saying, hey, this is an issue. I do this. It is. But I do like the approach that Sherry outlined just have everything as a site page or news article. It's probably like one less click to get at the actual content versus like drilling into that PDF file. Yeah. Well, you just have to remember that the pages library is just like any other document library. You can customize it, add workflows to a pages library, just like any of there's lists and there's libraries, the only two bones of SharePoint and pages libraries are just a special library with a different content type. And you can do like Sherry saying, just like a document library, you can do content approval. So just because somebody saves a page or submits a page, like in the news, you submit the page, but it doesn't mean the whole world's gonna see it. It can go through a process, make sure the right information is there before it's exposed to the rest of the organization. Yeah. And you're not talking about heavy-handed approval processes. You're like, this is all out of the box. This is stuff that just works. Just content approval. Yeah. The whole button in versioning settings. Yeah. Versioning settings or advanced settings? Yes, one of the two. One of the two. Okay. For my 15 years at SharePoint, I always have to flip a mental coin. Which one am I going to play? But I think it's in versioning setting because then you can, I think, because then is when you say who gonna brew drafts or whatever. Okay. But we don't have to be on that one. Those are two places, I always tell SharePoint admins, side admins, go in there and look at what's in there. Things like being able to turn off the, or so it opens like your Excel files directly in Excel and not in the web first. Things like that. There's a lot of great settings in those two little checkboxes. Mm-hmm. Yep. Great.