This is an addon for the Postie plugin (email-to-post). It does nothing on its own - Postie must be installed and active.<\/p>\n\n
By default, Postie saves emailed content as a flat HTML\/text blob, so a post created from an email opens in the block editor as one big Classic\/HTML block rather than proper paragraph\/heading\/image blocks - and a big blob is difficult to edit afterward.<\/p>\n\n
SLNWP Html and MD Blocks for Postie converts that emailed content into real, individually-editable Gutenberg blocks before the post is saved with the ability to further format using markdown syntax within Wrap the part of the email you want parsed as Markdown in This is deliberate, not automatic: this plugin never guesses whether some arbitrary content \"looks like\" Markdown - only content inside an explicit <<\/p>\n\n div>\/, or an aligned<\/p>\n\n <<\/p>\n\n div> that only uses <<\/p>\n\n div> no longer collapses into a single opaque HTML block instead of converting to real blocks\n* Fix: an inline image wrapped in a no-op (e.g. Word's mso-no-proof span) now becomes its own image block instead of being lost inside a paragraph\n* New: preserve paragraph\/heading text alignment and image alignment (left\/center\/right) from the source HTML\n* Fix: converted heading blocks now include the wp-block-heading class Gutenberg expects<\/p>\n\n <<\/p>\n\n p>, which made every paragraph individually opaque to Parsedown's raw-HTML-passthrough rule\n* Fix: a bare URL auto-linked by the mail client inside Markdown image\/link syntax (e.g. Thunderbird's freetext links) broke image\/link recognition - now unwrapped before parsing\n* New: bullet and numbered lists now convert to real core\/list blocks (with nested sub-list support) instead of falling back to core\/html<\/p>\n\n<md>...<\/md><\/code>.<\/p>\n\n\n
#<\/code>\/##<\/code> headings, blank-line paragraphs, **bold**<\/code>, [links](url)<\/code>, *<\/code>\/-<\/code> lists, ><\/code> quotes) wrapped in an explicit <md>...<\/md><\/code> block is parsed into native blocks. See the FAQ below.<\/li>\ncore\/image<\/code> blocks referencing the real WordPress attachment Postie already created, not bare <img><\/code> tags.<\/li>\ncore\/list<\/code> blocks (with each item as its own core\/list-item<\/code>, including nested sub-lists), not plain text.<\/li>\n><\/code>) become real core\/quote<\/code> blocks, with their contents as native inner blocks.<\/li>\ncore\/html<\/code> block, so content is never silently dropped.<\/li>\n<\/ul>\n\n\n\n
\n
How do I get Markdown syntax converted?<\/h3><\/dt>\n
<md><\/code> and <\/md><\/code> tags, each on their own line:<\/p>\n\n<md>\n# My Heading\n* A list item\n* Another item\n<\/md>\n<\/code><\/pre>\n\n<md>...<\/md><\/code> block is ever parsed as Markdown. Content outside the wrapper (or the whole email, if you don't use one) is treated as plain content. As a side benefit, content inside <md>...<\/md><\/code> is also fully shielded from Postie's own content-processing (its newline-collapsing, ---<\/code>-line signature stripping, and #subject#<\/code> inline-subject extraction all run before this plugin ever sees the content, and could otherwise silently damage unwrapped Markdown syntax that happens to resemble one of those conventions) - using <md><\/code> sidesteps all of that automatically, with no workaround needed.<\/p><\/dd>\n\n<\/dl>\n\n\n0.1.19<\/h4>\n\n
\n
0.1.18<\/h4>\n\n
\n
0.1.17<\/h4>\n\n
\n
0.1.16<\/h4>\n\n
\n
for line breaks - as Outlook\/OWA and Word produce) is now inherited by the paragraphs, headings, lists and images inside it, instead of being dropped.<\/p>\n\n0.1.15<\/h4>\n\n
\n
0.1.14<\/h4>\n\n
\n
0.1.13<\/h4>\n\n
\n
0.1.12<\/h4>\n\n
\n
0.1.11<\/h4>\n\n
\n
0.1.10<\/h4>\n\n
\n
0.1.9<\/h4>\n\n
\n
0.1.8<\/h4>\n\n
\n
0.1.7<\/h4>\n\n
\n
0.1.6<\/h4>\n\n
\n
0.1.5<\/h4>\n\n
\n
0.1.4<\/h4>\n\n
\n
0.1.3<\/h4>\n\n
\n
0.1.2<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n