markdown-on-save
Markdown on Save
Allows you to compose content in Markdown on a per-item basis. The markdown version is stored separately, so you can deactivate this plugin any time.
Proof Health
Open evidenceCommercial opportunities need traceable source links before they are treated as build-worthy.
89.9% of this page's analysis has direct source links.
0 rows here require auditable proof before promotion.
0 rows have source counts but still need direct links.
Related Opportunities
1 marketSource Evidence
Open evidence explorer[Plugin: Markdown on Save] Converting Posts from Former Markdown Plugin: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes live[Plugin: Markdown on Save] Markdown for comments ?: users show missing feature, support, migration pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes liveUpdate markdown-extra.php from verion 1.2.6 to 1.2.8: users show compatibility, missing feature, support pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes liveMarkdown Button Missing after Upgrade to WP 4.4: users show bugs, missing feature pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes liveBug: Footnotes do not work correctly on front page of WordPress blogs: users show bugs, compatibility pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes liveDoes not play well with hard-wrapped paragraphs: users show missing feature, support pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes livePHP Markdown's issue with the way WordPress processes text: users show bugs, compatibility pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes liveRestoring an older vesion switch back in HTML: users show compatibility, migration pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes liveThe plugin does not have a valid header.: users show bugs, setup pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes live[Plugin: Markdown on Save] Link Titles: users show bugs pain that may indicate a product gap.
Buyer: publishers, content teams, and agencies · Wedge: check formatting publishing, media, metadata, and editorial handoffs before content goes liveCompetitor Context
16 shownRepeated Themes
0 shownNo repeated plugin-level themes have been generated yet.
Collected Signals
20 shown from 25 collectedSimple. Works. As advertised.: users praise easy, reliable, which suggests what competitors already do well.
Evidence: Simple.Really good idea: praise conversation with limited structured signal.
Evidence: Really good idea You have the advantage of using Markdown rather than the horrible Gutenberg block system while also being able to let someone else edit in the Classic Editor. You have the advantage of using Markdown rather than the horrible Gutenberg block system while also being able to let someone else edit in the Classic Editor.Markdown Button Missing after Upgrade to WP 4.4: users show bugs, missing feature pain that may indicate a product gap.
Evidence: Markdown Button Missing after Upgrade to WP 4.4 Thanks for the great plugin.Compatibility with WordPress Liveblog?: users show compatibility pain that may indicate a product gap.
Evidence: Compatibility with WordPress Liveblog?Works great: users praise reliable, quality, which suggests what competitors already do well.
Evidence: Works great Works perfectly, thanks Mark!Update markdown-extra.php from verion 1.2.6 to 1.2.8: users show compatibility, missing feature, support pain that may indicate a product gap.
Evidence: Update markdown-extra.php from verion 1.2.6 to 1.2.8 Hi guys, currently Markdown on Save uses markdown-extra 1.2.6 (1) Is it possible to update to PHP Markdown Extra 1.2.8 ( http://michelf.ca/projects/php-markdown/classic/ )?Restoring an older vesion switch back in HTML: users show compatibility, migration pain that may indicate a product gap.
Evidence: Everything works fine except the new versionning system introduced in wordpress 3.7.The plugin does not have a valid header.: users show bugs, setup pain that may indicate a product gap.
Evidence: Getting error “The plugin does not have a valid header.” when activating plugin.Bug: Footnotes do not work correctly on front page of WordPress blogs: users show bugs, compatibility pain that may indicate a product gap.
Evidence: Bug: Footnotes do not work correctly on front page of WordPress blogs In Michel Fortin’s PHP Markdown Extra, footnotes link to something like http://www.chickensinenvelopes.net/#fn:978.1 on the main page, with the ‘978’ denoting the post and the ‘1’ denoting the number of the footnote.Convert to Markdown by default?: users show missing feature pain that may indicate a product gap.
Evidence: Would it be possible to have a plugin settings pane that just had a tickbox that could switch the default behaviour of the plugin from a white box to a black box?Does not play well with hard-wrapped paragraphs: users show missing feature, support pain that may indicate a product gap.
Evidence: Does not play well with hard-wrapped paragraphs When formatting a post with hard-wrapped paragraphs, either wordpress or the plugin adds a line-break after each line-wrap, leading to an excessively ragged right margin, or, worse, orphaned words that have overflowed right before the line break (especially prevalent in blockquotes).PHP Markdown's issue with the way WordPress processes text: users show bugs, compatibility pain that may indicate a product gap.
Evidence: PHP Markdown's issue with the way WordPress processes text PHP Markdown has a small problem with the way WordPress processes text, which I noticed in the upcoming WordPress flagship theme Twenty Thirteen .Previewing a Page seems to not render markdown…: users praise reliable, value, which suggests what competitors already do well.
Evidence: Previewing a Page seems to not render markdown… On the new version, when editing a page, if you hit preview the markdown isn’t rendered… (Haven’t tried it for a post or a CPT) http://wordpress.org/extend/plugins/markdown-on-save/ On the new version, when editing a page, if you hit preview the markdown isn’t rendered… (Haven’t tried it for a post or a CPT) htv.1.2 ?: neutral conversation with limited structured signal.
Evidence: v.1.2 ? No Changelog for v.1.2 version ? http://wordpress.org/extend/plugins/markdown-on-save/ No Changelog for v.1.2 version ? http://wordpress.org/extend/plugins/markdown-on-save/ Looks like WordPress.org had a hiccup and didn’t update that. Bumped it to trigger a rebuild. Thanks! Looks like WordPress.org had a hiccup and didn’t update that. Bumped it to tRecovering Markdown: users show performance pain that may indicate a product gap.
Evidence: http://wordpress.org/extend/plugins/markdown-on-save/ Well, if you saved your Database, you should have your Markdown table.[Plugin: Markdown on Save] Link Titles: users show bugs pain that may indicate a product gap.
Evidence: [Plugin: Markdown on Save] Link Titles Links formatted with a title are not being parsed properly.[Plugin: Markdown on Save] tags?: users show support pain that may indicate a product gap.
Evidence: Is there a standard way to do it or is it not supported?[Plugin: Markdown on Save] Converting Posts from Former Markdown Plugin: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Evidence: [Plugin: Markdown on Save] Converting Posts from Former Markdown Plugin Before installing this plugin, I was using a different Markdown plugin.[Plugin: Markdown on Save] Markdown for comments ?: users show missing feature, support, migration pain that may indicate a product gap.
Evidence: Hello, your plugin lacks a feature I liked with Fortin’s plugin: the ability to use Markdown language in the comments.[Plugin: Markdown on Save] Markdown Parser Bug: Link title not processed: users show bugs pain that may indicate a product gap.
Evidence: [Plugin: Markdown on Save] Markdown Parser Bug: Link title not processed I tried to put the title attribute in a link and it failed to parse the markdown at all.