I honestly enjoy drafting articles either locally in Ulysses, or on my blog<\/a> using the Iceberg Editor<\/a>. While I do love Iceberg, once I publish an article I typically bring back the default Gutenberg experience \u2014 thus removing any comments I previously added.<\/p>\n\n 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>\n\n Learn more about Markdown Comment →<\/a><\/p>\n\n The block only renders within the editor. For developers reading this, that means there\u2019s no save function. I don\u2019t want my unfinished ideas, reminders, and notes rendered within my post - even if they\u2019re hidden by CSS.<\/p>\n\n I added a couple transforms, to and from headings and paragraphs, and a raw shortcut when you type To support that path towards simplicity, I wanted a method to quickly resolve \u2014 i.e. banish \u2014 a comment entirely. So, I added a toolbar control to quickly resolve the comment, removing the block entirely.<\/p>\n\n Comments need to have minimal impact on editing, and feel as natural as possible. That\u2019s why there are no typical RichText controls (although you can still bold, italicize and add hyperlinks). And while you can<\/em> change the color of the comment \u2014 there are no other typographic controls.<\/p>\n\n 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\u2019s no need to override any styles with classes, just write a few CSS variables.<\/p>\n\n\n Yes! If you're using Gutenberg (i.e. the block editor) on your site, you should have no issues with the block. It's relatively simple to modify the CSS variables to tweak the comment styling if you'd like \u2014 learn more here<\/a>.<\/p><\/dd>\n Please reach out via the official plugin support forum<\/a>.<\/p><\/dd>\n As a WordPress entrepreneur, designer and developer all wrapped up in one, @richard_tabor<\/a> is recognized as one of the top leaders in this post-Gutenberg era of WordPress. His design chops have topped the 2018 Automattic Design Awards and led him to found CoBlocks \u2013 a top-notch set of page builder blocks and tools for Gutenberg, ThemeBeans \u2013 a premier WordPress theme shop and Iceberg<\/a> \u2013 a markdown editor for Gutenberg.<\/p><\/dd>\n\n<\/dl>\n\n\nWhat's interesting about Markdown Comment:<\/h3>\n\n
1. Editor only<\/h4>\n\n
2. Helpful block transforms<\/h4>\n\n
%%<\/code> and hit the [space] key. This lets me quickly add comments, and even convert whole paragraphs or headings to a comment.<\/p>\n\n3. Easily resolve comments<\/h4>\n\n
4. No rich text support<\/h4>\n\n
5. Entirely CSS Variable ready<\/h4>\n\n
\n
markdown-comment-block<\/code> folder to your \/wp-content\/plugins\/<\/code> directory or alternatively upload the markdown-comment-block.zip file via the plugin page of WordPress by clicking 'Add New' and selecting the zip from your local computer.<\/li>\n\n
Can the Markdown Comment block be used with my theme?<\/h3><\/dt>\n
Where can I send feedback or ideas?<\/h3><\/dt>\n
Who's Rich Tabor?<\/h3><\/dt>\n
1.0.0<\/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.3<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n