I like to use Semantic HTML and Markdown together and this allows me to use it right inside the Editor with the appropriate controls. Markdown is great for things like codeblocks, much better than going with a plugin that you have to learn something new or use a separate interface for codeblocks.
Other markdown plugins only convert your markdown to HTML without actually letting you just drop it in the post. It is also a great way to allow less tech-savvy users to use a non-block editor without learning HTML. It is a win-win plugin that I highly recommend. ]]>
Everything is working apart from modifying the image url in the post.
The post is uploading, the images are uploading and the frontmatter is working.
But the url of the images doesn’t change from…
_images/
…to the location of the image.
I have the Classic Editor set as default. Here is the code in the post for an image…
<figure class="wp-block-image size-full">
<img src="_images/image-file-name.png" alt="" />
</figure>I checked here and on GitHub and I couldn’t find a solution to the problem. Could it perhaps be a conflict with another plugin.
Cheers
Mac2Net
One thing to note is that is uses Markdown instead of a Rich Text Editor. GREAT in my opinion, but thought people would like to know that.
]]>Thanks a lot!!
]]>For users familiar with markdown writing, this plugin is more suitable for working in front-end editors, without jumping to back-end editing, without excessive use of the mouse, and with almost no need to leave the keyboard with both hands, it can smoothly express some advanced documents. For me, I have been using the O2 front-end editor all along, and the only remaining one issue is that it cannot be fully compatible with this plugin. I may continue to discuss it in my previous post.
]]>It is fantastic to get rid of Block Editor (Gutenberg) and Classic Editor!
]]>We write a lot of our content in Markdown and Jetpack has great support for being able to write/paste in/ maintain this format in the standard WP fields, however ACF fields have never supported (there were some community hacks years ago that never fully worked and were abandoned.
Someone please consider carrying over support for this from Jetpack or as an independent feature.
]]>I guess this is bevause of the Docs use of the TinyMCE front-end doc editing?
Is there a way to make this amenable to Markdown integration or if not replace the Docs TinyMCR with the wordpress editor that integrates with Jetpack’s Markdown settings?
]]>But, unfortunately I see that the streaming option doesn’t work anymore. So I had to disable this option and enable the typewriting effect. Also I noticed when the typewriting is working the code is coming raw and markdown characters stays in the chat like #, **, ` and etc.</p>
<p>Best regards,<br>Ivan.</p>
]]>
Another thing missing is the preview of the highlight themes for code. But it is certainly a minor aspect.
]]>