YamlDotNet VS PublishToDev

When it comes to YAML serialization and deserialization in .NET, YamlDotNet is a go-to library with over 100 million downloads on NuGet. It is also integrated into various projects by Microsoft and the .NET team, despite the absence of an official Microsoft YAML library for .NET.

Looking at the sample, it doesn’t look like navigation the ‘representation model’ is that much different from doing the same for a JSON document. I suggest trying to make that work.

If you don't want the jank, YAML supports comments. https://github.com/aaubry/YamlDotNet can read commented files just fine, and can probably emit them as well with some custom handling code.

I think you should provide your input here, if you haven't already.

In the past I've used DotNetYaml for this. This library allows you to serialize and deserialize between YAML and your own objects.

The frontmatter string needs to be deserialised to a strongly-typed FrontMatter instance, using the YamlDotNet library. Then, change the Published value to true.

There's the tool called PublishToDev built by one of my colleagues, Todd, which schedules to publish articles on Dev.To. It's super useful because I can schedule my posts whenever I want to publish them on there. As soon as I saw this tool, I wanted to clone code in .NET because it would be beneficial to practice: