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.

Michael Sablone

<p>LLM Markdown exposes your public WordPress posts and pages as real <code>.md</code> routes.  Simply append .md to any supported post or page URL to access its Markdown representation.</p>
<p>Each Markdown document includes structured YAML front matter and clean content extracted from the rendered HTML.</p>
<p>Designed for:</p>
<ul>
<li>LLM and AI ingestion</li>
<li>Headless and hybrid workflows</li>
<li>Content export pipelines</li>
<li>SEO-friendly alternate representations</li>
</ul>
<p>Example:</p>
<pre><code>https://example.com/my-post.md
</code></pre>
<p>Features:</p>
<ul>
<li>Real <code>.md</code> URLs</li>
<li>YAML front matter (title, dates, taxonomy, URL)</li>
<li>Selector-based content extraction</li>
<li>Respects password protection</li>
<li>Optional respect for noindex</li>
<li>Per-post-type control</li>
<li>Caching for performance</li>
<li>Adds <code><link rel="alternate" type="text/markdown"></code></li>
</ul>
<p>No Gutenberg lock-in. No content duplication. No custom post types required.</p>


LLM Markdown – Expose Content as .md

Expose WordPress posts and pages as real .md URLs with YAML front matter for LLMs, AI ingestion, and headless workflows.

Markdown Comment Block vs LLM Markdown – Expose Content as .md