✅ Deploy Preview for blazorstatic ready!

Name	Link
🔨 Latest commit	e3be540
🔍 Latest deploy log	https://app.netlify.com/sites/blazorstatic/deploys/677a81f925e6990009ac860a
😎 Deploy Preview	https://deploy-preview-52--blazorstatic.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

for tags why not use attributes? we already use reflection to get the site's routes so it shouldn't be an issue

i'm thinking something like this:

class MyFrontMatter {

    public string Title { get; set; }
    [BlogTags]
    public string[] categories { get; set; }
}

that way the user can name the variable whatever they wish or omit it completely if they don't need it without us having to maintain 2 different interfaces

for tags why not use attributes?

That made me think about the Tags from a different perspective...

Because Tags wont be List<string> anymore, but we still need the List<string> to parse the data from yml...

Which means we need to "free" the IFrontMatter from anything that is not used as strongly typed metadata... Which means we need to put it in Post (List<string> Tags in FrontMatter and List<Tag> Tags in Post), which kind of means we need to provide an interface for the Post itself...

It is somehow getting together. I will see, how the Attribute goes along with it..

The BlazorStaticWebsite/Content/Blog/release-1.0.0-beta.14.md file sums up the changes

Deploying blazorstatic with    Cloudflare Pages

View logs