Currently, Markdown rendering is handled by a basic goldmark implementation that produces standard HTML. With the switch to the Accessibility-based pasting strategy, we now have a cleaner path to customize the appearance of the pasted content by applying CSS styles to the generated HTML.
Proposal:
Introduce a configuration mechanism that allows users to define styles for Markdown rendering. This would replace the old richtext configuration logic with a more standard CSS-based approach.
Key Features:
- A configuration file (e.g.,
styles.yaml) to define visual properties for HTML elements (h1, p, blockquote, code, etc.).
- The ability to inject a
<style> block or apply inline styles during the Markdown-to-HTML conversion process in the internal/md package.
- Support for custom fonts, colors, and spacing that Mail.app can interpret when the HTML is pasted.
This feature would restore the customization capabilities of the server while leveraging the robustness of native HTML rendering in Mail.app.
Currently, Markdown rendering is handled by a basic
goldmarkimplementation that produces standard HTML. With the switch to the Accessibility-based pasting strategy, we now have a cleaner path to customize the appearance of the pasted content by applying CSS styles to the generated HTML.Proposal:
Introduce a configuration mechanism that allows users to define styles for Markdown rendering. This would replace the old
richtextconfiguration logic with a more standard CSS-based approach.Key Features:
styles.yaml) to define visual properties for HTML elements (h1,p,blockquote,code, etc.).<style>block or apply inline styles during the Markdown-to-HTML conversion process in theinternal/mdpackage.This feature would restore the customization capabilities of the server while leveraging the robustness of native HTML rendering in Mail.app.