Support Markdown rendering

[khalidabuhakmeh]

Allow folks to take a markdown file and render it to the console.

https://github.com/charmbracelet/glow

[mcon]

I'm going to have a shot at this, looks like it's not too tricky to use https://github.com/xoofx/markdig (I'll be working here: https://github.com/mcon/spectre.console/tree/markdown - should have something of decent quality shortly)

[mcon]

PR here if anyone's interested: #204

[enginexon]

Is this still interesting topic for community? Was it already implemented?

[patriksvensson]

@enginexon A spike PR was opened at #204, but nothing was completed. It's up for grabs.

[frankhaugen]

I like the general concept, but I think the implementation should be a "Document", that is a full width panel, and have some internals for paging etc., but leaves the content up te "extension" through a DocumentContent -type that is inheritable, or something, at least it should allow one to override the raw content and then when it hits the renderer it is in "markup", so the internet at large could then just introduce their own nuget named something like: Spectre.Console.Document.Markdown, and you will get the community to provide the extension, (Markdown might be internally made, since someone already made some code for that in above mentioned PR).

It feels like a natural addition to have some sort of "document viewer", that have in the case of markdown 1 file per page, but being able to construct a "Pagable Document Viewer" would be awesome, but it needs some actual design an forthought to make it "fit" into the whole of spectre

[FrankRay78]

Should this really be a core part of spectre.console, or would it best be located in some form of contrib project? (like what Cake does, here: https://github.com/cake-contrib)

I often wonder the same thing each time I consider making a spectre.console widge for asciichart.

[frankhaugen]

Conceptually I like it, but "contrib" named nugets are usually a "red flag" for many, (at least two different teams I've worked with have had bad experience with "anything goes" contrib packages), so should probably brand it "Spectre.Console.Extensions" or "Spectre.Console.Community", and then try to motivate the community to use that as a prefix.

Personally, I like granualar nugets, so I would be urked by needing to get asciichart if I just want Markdown, so a singular "contrib" project should regardless aim for granularity, (makes handling bugs easier aswell)