Hm. Interesting.
If you would ask me before I would tell you that it is already happening (that's why the copy content is already there). But the Directory.GetFiles is really getting files from the root directory.

There is just one issue with modifying the blog files -> When you publish your app, the "bin" folder becomes the "project" root folder and the files in Content is just one. So when you change it, it will stay changed.

What is exactly the use case when you need to modify the files? Because maybe there is a better way.

Thanks for you PRs, appreciate that.

I honestly didn't think much about it, I saw that the example website already has those lines added but noticed the code doesn't make use of them.

A use case I can think of is to have the posts' read time calculated dynamically instead of having it hardcoded in the posts' front matter, or being able to upload the images in a post to a CDN while leaving the root files use the local copies for offline editing.

That sounds like a job for opt.AfterBlogParsedAndAddedAction. For example here I am doing exactly that - changing path for the images.

The posts live in memory for a brief period of time and you can can change them however you like..

the issue with opt.AfterBlogParsedAndAddedAction is that, as the name implies, comes after the blogs were parsed which makes it hard, for example, to count the words in a blog and calculate the reading time since you'll have to parse the html and extract it's content which is extra work