I entered this Idea, but we’ll have to wait for the approval process.
Support Markdown in Textareas (KIN-I-7490)
Markdown is one of the more token friendly ways to store textual information. There are many tools that will convert the Markdown to output that supports font-size, color, links, etc.
It would be cool if Bold Reports supported Markdown, but for now it’s only text and HTML. 
Just looked at this yesterday because Outlook HTML Emails are always fun!
waits patiently to be able to vote on this idea
The UI should be actively converting to html for presentation anyway, so there’s an opportunity to store that html. Which is a really awful bad idea, but who knows anything can happen.
Storing the literal markdown text would be a good and right thing to do. Worst case scenario, if it’s consumed by something outside Epicor that doesn’t do markdown formatting things, raw markdown mostly makes intuitive sense to normal humans. Implementation should only modify presentation in the client. This I could get behind.
External things would get a little weird depending on which flavor of markdown syntax they use, but that’s not Epicor’s problem to solve.
Or as RTF, which is an equally Bad Idea 
, IMHO.
epicor already supports rtf
seems to support wtf too
SPOCK COME BACK THERE’S ANOTHER ONE
quiver at the thought of my md in a database field. depends what you wanna do with it i suppose.
This might be easier than ideas…
PROMPT:
Design an Azure Function that accepts GitHub‑Flavored Markdown, converts it to high‑fidelity GitHub‑styled HTML using Markdig (or markdown‑it), and returns HTML or PDF/image generated via a lazily‑loaded headless Chromium (Playwright). Provide architecture, flow, and code