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.

An, Hyeong-woo

<p>The plugin get markdown file URL like github raw content url. The plugin convert markdown file to html, and put it to post content.</p>
<p>It also provide text mode that write markdown in post edit page. Markdown text converted to html is put to editor. Text mode don’t use url.</p>
<p>이 플러그인은 마크다운 파일의 URL을 받아서 html로 변환하고 그걸 포스트 내용으로 집어넣습니다.<br />
기트허브 원본 내용 URL 같은 것을 활용할 수 있습니다.</p>
<p>포스트 편집 페이지에서 마크다운 텍스트를 작성하는 방법도 제공합니다. 마크다운 텍스트는 html로 변환돼 에디터에 들어갑니다.<br />
텍스트 모드를 사용하는 경우 URL은 사용하지 않습니다.</p>
<p><strong><a href="https://www.youtube.com/watch?v=wKcrIvlGVfo" rel="nofollow ugc">See intro video.</a></strong></p>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/wKcrIvlGVfo?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h4>Now you can migrate from Public link to Dropbox API</h4>
<p>I made up Mytory Markdown for Dropbox plugin. The plugin access Dropbox using API. So I divide the plugin to Mytory Markdown for Dropbox.<br />
Now you can install it in plugin page. This video describe how to migrate Public link to Dropbox API.</p>
<p>Install Mytory Markdown for Dropbox and activate it. Then see a video below.</p>
<p>[Youtube https://www.youtube.com/watch?v=ZmPWMBvGuS4]</p>
<p>If the video doesn’t be show, <a href="https://www.youtube.com/watch?v=ZmPWMBvGuS4" rel="nofollow ugc">click this to go to how to migration video</a>.</p>
<h4>이제 Public 링크를 드롭박스 API로 이전할 수 있습니다</h4>
<p>Mytory Markdown for Dropbox 플러그인을 만들었습니다. API를 이용해서 드롭박스에 접속하는 플러그인입니다. 별도로 만들었습니다.<br />
지금 플러그인 페이지에서 검색해 설치할 수 있습니다. 아래 비디오는 퍼블릭 링크를 드롭박스 API로 이전하는 방법을 설명합니다.</p>
<p>Mytory Markdown for Dropbox 플러그인을 설치한 뒤, 활성화하고 아래 비디오를 보세요.</p>
<p>(비디오는 위에서 보세요.)</p>
<h4>Features</h4>
<ul>
<li>This plugin get markdown file url like github raw content url. It convert markdown file to html, and put it to post content.</li>
<li>You can update post <strong>by editing file on your computer</strong>. e.g. <strong>By push your content to github</strong>. Of course, you can edit directly from github website.</li>
<li>If post was updated once, plugin check only URL server’s ETAG not full content. It is for speed.<br />
If ETAG was changed, plugin get new content and update post content. Or do nothing.</li>
<li>The plugin only pass converted html content to editor. Saving is WordPress’s work. So revision history is preserved.</li>
<li>The plugin is compatible with other plugins. Because the plugin updates only post content html. This doesn’t touch <code>the_content</code> process(vary plugins touch the process).</li>
<li>You can use <a href="http://michelf.ca/projects/php-markdown/extra/" rel="nofollow ugc">markdown extra syntax</a>.</li>
<li>It provide markdown editor that can use in post editing page instead of url.</li>
</ul>
<h4>Logic</h4>
<h4>On admin page</h4>
<p>On admin write page, put markdown url path. And click ‘update editor’ button. So markdown content converted to html is putted to editor. <a href="https://wordpress.org/plugins/mytory-markdown/screenshots/" rel="ugc">See screenshot 1</a>.</p>
<h4>On view page</h4>
<p>This plugin get file url(Github raw content url is recommended). And save header’s etag to postmeta and converted html to post_content.<br />
Next time on request same post, first this plugin olny get http etag.<br />
If changed etag, get md content and save again, or get html from post_content.</p>
<h4>This plugin divide title and content from md file</h4>
<p>If markdown file has <code>h1</code> this plugin puts first <code>h1</code> string to post_title. Of course, remove the <code>h1</code> from post_content so don’t print title twice.</p>
<h4>Source Code</h4>
<p><a href="https://github.com/mytory/mytory-markdown" rel="nofollow ugc">Mytory Markdown Github</a></p>
<h4>You can use Multimarkdown 6</h4>
<p>You can use the Muitimarkdown if you install it on your server. ((Website)[https://fletcher.github.io/MultiMarkdown-6/])</p>
<ol>
<li>
<p>Multimarkdown option will be enabled if a multimarkdown execution is on OS PATH and web server can run it.</p>
</li>
<li>
<p>Otherwise, you can define <code>MYTORY_MARKDOWN_MULTIMARKDOWN_EXECUTION</code> constant on <code>wp-config.php</code>.<br />
ex) <code>define('MYTORY_MARKDOWN_MULTIMARKDOWN_EXECUTION', '/opt/multimarkdown/bin/multimarkdown');</code></p>
</li>
</ol>


Mytory Markdown

The plugin get markdown file URL like github raw content url. It convert markdown file to html, and put it to post content.

Markdown Comment Block vs Mytory Markdown