by
wakalab
0 (0 reviews)
Markdown Renderer for GitHub
Render GitHub Flavored Markdown in WordPress: Shiki code highlighting, Mermaid diagrams, and Chart.js charts. For documentation and dev blogs.
Markdown Renderer for GitHub ranks #20,539 among WordPress.org plugins with 50+ active installations, and was last updated Sep 16, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v2.11.22
Current Version v2.11.22
Updated 1 month ago
Last Update on 16 Sep, 2026
Refreshed 1 week ago
Last Refreshed on
Top 50% by installs
Downloads +21.5% this week
Rank
#20,539
—
No change
Active Installs
50+
+25%
KW Avg Position
50.7
0.4 worse
Downloads
5.3K
+5 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 60
50+
60+
1,590
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 5 more installs to reach 60+
Rank Changes
Current
#20,539
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.11.22
- Last Updated
- Sep 16, 2026
- Requires WP
- 6.8+
- Tested Up To
- 7.1.4
- PHP Version
- 8.2 or higher
- Author
- wakalab
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Markdown Renderer for GitHub
Open Markdown Renderer for GitHub > Manual, read the Getting Started tab, then create or edit a post with the Markdown block. Preview the front-end page and adjust the Code Block settings if needed.
Use the Markdown block in the block editor. In the Classic editor, widgets, or templates, wrap Markdown in the [gfmr_markdown] enclosing shortcode. The shortcode renders through the same core pipeline as the block.
Use the GitHub alert syntax: start a blockquote whose first line is > [!NOTE], then write the body on the following quoted lines. [!TIP], [!IMPORTANT], [!WARNING], and [!CAUTION] work the same way. The keyword must be alone on that first line, otherwise the block stays an ordinary blockquote.
Save the settings, clear page cache, CDN cache, browser cache, and any asset optimization cache. Then check a front-end post that actually contains a Markdown block or [gfmr_markdown] shortcode.
Usually yes. If output looks stale or broken, temporarily disable cache, minification, defer, and combine settings. If styles still look wrong, test briefly with a default WordPress theme to isolate theme CSS conflicts.
By default, no. Shiki, Mermaid, Chart.js, and markdown-it are bundled locally and served from your WordPress installation. Optional PlantUML and server-side Mermaid rendering can send diagram source to an external renderer only after you enable and configure those features. See Third Party Services for details.
The free plugin includes the main rendering features: GFM, Shiki, Mermaid, Chart.js, PlantUML, Table of Contents, structured data, multilingual options, and basic AI agent abilities. Pro is a separate, standalone plugin (it bundles all Free features) for advanced workflow features and priority support. You do not need Pro for the core rendering features.
Nothing is removed by default: deleting the plugin leaves its settings, caches, and post metadata in the database, so reinstalling restores your configuration. If you want a clean removal, enable "Remove Data on Uninstall" on the General Settings tab before deleting the plugin. That option is off by default and cannot be undone once the plugin is deleted.
Free plugin usage questions and reproducible bugs should go to the WordPress.org support forum. Pro license, billing, contract, refund, and account questions should not be posted in the WordPress.org forum; use the support guidance shown inside the plugin admin screen.
Include WordPress version, PHP version, plugin version, theme, affected feature, steps to reproduce, and relevant non-secret System Info from the plugin settings screen. Never share license keys, API keys, Application Passwords, tokens, cookies, or private account information.