This guide explains how application developers consume ProMarkdown. It starts with the MarkdownTextBlock control, then moves through rendering configuration, source-aware editing, hit testing, theming, and extension points.
Install ProMarkdown for the control and the core parsing, rendering, editing, selection, layout, theme, and hit-testing services. The default control configuration is enough for common Markdown documents.
Plugin packages are opt-in. Registration is explicit so applications control syntax, rendering behavior, editor selection, startup cost, and transitive dependencies.
The public service contracts let applications render outside the stock control, map rendered content back to source, provide custom editor surfaces, or introduce new Markdown syntax and visuals.