Morten Piibeleht

Any thoughts on how to approach it though? I don't see any obvious way to pass the `LinkRule`, or some of its fields, to the `parse_close_bracket` function. Right now, I...

I noticed that there is actually some precedent to having the parser functions be stateful closure, with the `ji` from `JuliaInterpolationRule` being used in the parser function: https://github.com/MichaelHatherly/CommonMark.jl/blob/7e6138c82ba784ac349829d9635faf4267fea479/src/extensions/interpolation.jl#L24-L44

I now have put together a WIP version of [a separate AST package](https://github.com/JuliaDocs/MarkdownAST.jl). It needs heaps of corner-case fixing, general cleanup and more documentation, but I think the only major...

Ah, I didn't consider keeping the code and API similar to the other implementations as a goal. The downside of sticking to those conventions is that it would restrict us...

> The next step I can take is to replace most of the container/element types, which should also be **trivial**, since I don't think I changed their fields (`Text` is...

When you say "the make file has to be re-executed", I presume you mean from scratch in a clean Julia session, as opposed to re-evaluating it in the current session?...

I am completely behind having this be the default behaviour. I think it would be more intuitive that way. I guess for an implementation, there would need to be a...

I have been looking at this a little bit, and I noticed that a reference link without a valid definition for the link label gets interpreted as a simple string....

I was thinking about how to properly implement finding these invalid reference links. My original implementation was to add another field to `InlineParser` that would contain the fallback, which the...

A small stopgap UX improvement related to this: if we could have the directory index page generate URLs with a trailing slash for directories, then I think it would remove...