Disable blog reading for local development

[daveaglick]

We should be able to disable the reading of blogs when developing and previewing locally for a faster rebuild loop. This can be accomplished pretty easily with a new setting. I’ll submit a PR for this soon, so this is just a placeholder issue.

cc @nicoleabuhakmeh

[NikoMix]

For some random reason I've been crawling through the repo and issues and was tempted to implement this. I've seen you've had yourself assigned; hope I did not cause any issues by picking this up.

Best case I've saved you a few minutes :) Feel free to review the implementation @daveaglick

[daveaglick]

Awesome! Nice work - I've moved on a bit from this project, so I'm really happy to see some community members picking up some of the nice-to-have features (even if they'll be short-lived with the planned move to a CMS around the corner).

[NikoMix]

Thanks. Yea I've figured out later, that the changes only affected the "old" website. What's the plan with the repo then? Keep it for ingress of new issues/comments/remarks? Otherwise you might want to archive the repo and/or indicate the website is end-of-life

[daveaglick]

Yep, agreed. Setting the archived repo flag in GitHub is probably the best way to go here - not sure who can/would actually do that though.

[NikoMix]

Maybe for that exact reason I'd recommend to have a CODEOWNER File for each Repo in the .Net Foundation

Not sure where would be best to bring this up.

@Arhell Is this something you know/could help out with possibly?

[Arhell]

Unfortunately no, I only have access to these resources
https://github.com/dotnet-foundation/mod-dotnet-bot
https://github.com/dotnet-foundation/website
https://github.com/dotnet-foundation/membership

Otherwise, I mainly do updates and fix some little things, because I fixed everything that was needed in terms of the UI (front-end) a long time ago.

[NikoMix]

Okay. No worries, then I'll open a seperate Issue on that - as this is slightly out of topic then. Thanks everyone! :)