Isamu Takeda

<p>This block has the function of editing Markdown documents using SimpleMDE, and by parsing Markdown documents using marked, it can assign specific blocks to the converted HTML elements.<br />
This function allows users to customize Markdown documents using the styling functions of the corresponding blocks, allowing for a wide range of styling.<br />
The following are the blocks that are applied when Markdown documents are parsed into HTML elements.</p>
<ol>
<li>H element: itmar/design-title</li>
<li>P element: core/paragraph</li>
<li>PRE element: itmar/code-highlight</li>
<li>IMG element: core/image</li>
<li>BLOCKQUOTE element: core/quote</li>
<li>LI element: core/list</li>
<li>TABLE element: core/table</li>
</ol>
<p>The H element is also generated as a table of contents, and has the function of displaying nested items according to level.<br />
This plugin does not require any external resources (all scripts and styles are included locally)</p>
<h3>Related Links</h3>
<ul>
<li><a href="https://github.com/itmaroon/markdown-block" rel="nofollow ugc">markdown-block:Github</a></li>
<li><a href="https://github.com/itmaroon/block-class-package" rel="nofollow ugc">block-class-package:GitHub</a>  </li>
<li><a href="https://packagist.org/packages/itmar/block-class-package" rel="nofollow ugc">block-class-package:Packagist</a> </li>
<li><a href="https://www.npmjs.com/package/itmar-block-packages" rel="nofollow ugc">itmar-block-packages:npm</a>  </li>
<li><a href="https://github.com/itmaroon/itmar-block-packages" rel="nofollow ugc">itmar-block-packages:GitHub</a></li>
</ul>
<h3>Arbitrary section</h3>
<ol>
<li>
<p>PHP class management is now done using Composer.<br />
<a href="https://github.com/itmaroon/block-class-package" rel="nofollow ugc">GitHub</a><br />
<a href="https://packagist.org/packages/itmar/block-class-package" rel="nofollow ugc">Packagist</a></p>
</li>
<li>
<p>I decided to make functions and components common to other plugins into npm packages, and install and use them from npm.<br />
<a href="https://www.npmjs.com/package/itmar-block-packages" rel="nofollow ugc">npm</a><br />
<a href="https://github.com/itmaroon/itmar-block-packages" rel="nofollow ugc">GitHub</a></p>
</li>
</ol>
<h3>External services</h3>
<ol>
<li>This plugin uses EasyMDE to implement the editing function of Markdown documents. This is an open source JavaScript library provided under the MIT license.<br />
<a href="https://github.com/Ionaru/easy-markdown-editor/blob/master/LICENSE" rel="nofollow ugc">EasyMDE LICENSE</a><br />
EasyMDE comes with a spell check feature.<br />
When using this feature, it will try to load an external file (en_US.aff / en_US.dic) from a CDN. To avoid this, this plugin sets spellChecker: false, when instantiating EasyMDE, so that the external file will not be loaded.</li>
<li>This plugin uses marked to parse Markdown documents and convert them to HTML elements. This is an open source JavaScript library provided under the MIT license.<br />
<a href="https://github.com/markedjs/marked/blob/master/LICENSE.md" rel="nofollow ugc">marked LICENSE</a></li>
</ol>


MarkDown Block

This block converts Markdown documents into blocks for styling web pages.

Rich Tabor

<h3>Comments that only render in the block editor</h3>
<p>I honestly enjoy drafting articles either locally in Ulysses, or on <a href="https://richtabor.com" rel="nofollow ugc">my blog</a> using the <a href="https://useiceberg.com/?utm_source=wp-org&utm_medium=markdown-comment-block&utm_campaign=readme-description" rel="nofollow ugc">Iceberg Editor</a>. While I do love Iceberg, once I publish an article I typically bring back the default Gutenberg experience — thus removing any comments I previously added.</p>
<p>Having the ability to add, and keep, any relevant editing comments within my posts, without rendering them on the front-end, means that I am freed up to mentally jot any idea down without thinking about it. It is simply natural and convenient.</p>
<p><a href="https://richtabor.com/markdown-comments/?utm_source=wp-org&utm_medium=markdown-comment-block&utm_campaign=readme-learnmore" rel="nofollow ugc">Learn more about Markdown Comment →</a></p>
<h3>What’s interesting about Markdown Comment:</h3>
<h4>1. Editor only</h4>
<p>The block only renders within the editor. For developers reading this, that means there’s no save function. I don’t want my unfinished ideas, reminders, and notes rendered within my post – even if they’re hidden by CSS.</p>
<h4>2. Helpful block transforms</h4>
<p>I added a couple transforms, to and from headings and paragraphs, and a raw shortcut when you type <code>%%</code> and hit the [space] key. This lets me quickly add comments, and even convert whole paragraphs or headings to a comment.</p>
<h4>3. Easily resolve comments</h4>
<p>To support that path towards simplicity, I wanted a method to quickly resolve — i.e. banish — a comment entirely. So, I added a toolbar control to quickly resolve the comment, removing the block entirely.</p>
<h4>4. No rich text support</h4>
<p>Comments need to have minimal impact on editing, and feel as natural as possible. That’s why there are no typical RichText controls (although you can still bold, italicize and add hyperlinks). And while you <em>can</em> change the color of the comment — there are no other typographic controls.</p>
<h4>5. Entirely CSS Variable ready</h4>
<p>Global styles and full site editing are opening the door for themes to be heavily powered by CSS variables. Blocks should be designed with that same mentality, which is exactly what I did here. I added simple CSS variables with fallbacks that are the default values. To further theme the comment, there’s no need to override any styles with classes, just write a few CSS variables.</p>


Markdown Comment Block

Add markdown inspired comments to posts that render only within the block editor.

MarkDown Block vs Markdown Comment Block