I need to be able to resolve some custom URIs ("noda-type://" etc) - I believe I can do this with CommonMarkSettings but there's no way of providing any in MarkdownViewEngine. This could be a property in MarkdownViewEngineOptions, then passed along in MarkdownPage.

I have two different layouts I need to support: one for the user guide, and one for a developer guide.

Ideally, I could default to the user guide but have a file in the developer directory that changes the layout. However, failing that, it wouldn't be awful to have:

@layout DeveloperLayout.md
@page title="Foo"

in each developer guide page. But at the moment, I think only a single directive is supported per file. Perhaps it should read a line at a time until it finds something which isn't a directive (and processing the directives as it goes), and then concatenate the rest of the file with that...

I'm in the habit of putting spaces in assignments, so I had

@page title = "Foo"

... at which point Substring fails. Perhaps the regex for the values should just capture the key/value pairs with regex groups? That would be simpler.

Now if we have a model like this:

@model firstName="Jon" lastName="Doe"

This will work {{FirstName}}, but {{firstName}} doesn't

So the mustache nugget case should respect the case of the model property, in above example this {{firstName}} should work fine

This code in MarkdownPage does nothing useful:

if (!String.IsNullOrEmpty(markdown))
{
    markdown.Remove(0, directiveLine.Length - 1);
}

I suspect the intention was markdown = markdown.Remove(...) but that would do the wrong thing anyway - this code should just be removed.

(Sorry for reporting it like this - I'll gear up to create pull requests soon. :)

Using HTML in Markdown is slightly painful - if you have blank lines followed by indented HTML, they're treated as code, for example. Additionally, quite a lot of what I'd personally like to include code for would be in the layout rather than the body - and while this is planned for MDVE, it's not there yet.

How feasible would it be to load a layout in regular Razor, but then render the body of the view in Markdown? MDVE would still be responsible for finding the right Markdown file - and even the right layout file - to start with, but then ask Razor to render the layout, calling back into MDVE (possibly with a tag helper?) for the body.

I don't know much about the Razor details, and it may be infeasible or impractical, but it would be great if possible.

This looks like exactly the project I'm looking for in order to serve the Noda Time user guides. However, in order to contribute to it - and even use it as a nuget package - I'd need there to be a suitable licence stating how it can be used. (I'd personally appreciate either Apache 2.0, MIT, or BSD, but obviously YMMV.)

It's the time to create a NuGet package probably named My.AspNetCore.Mvc.Markdown and publish it to nuget.org