SIMPLYIRFAN MARKDOWN
SimplyIrfan Markdown compatibility with REEID Translate
SimplyIrfan Markdown compatibility with REEID Translate is being reviewed using official plugin documentation. Generates clean .md URLs for public posts, pages, and selected custom post types without creating duplicate physical files or altering original HTML. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What SimplyIrfan Markdown does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
SimplyIrfan Markdown is documented in the Other category with 8 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How SimplyIrfan Markdown compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Generates clean .md URLs for public posts, pages, and selected custom post types without creating duplicate physical files or altering original HTML.
- Converts rendered front-end pages to Markdown, preserving server-side output from Gutenberg blocks, shortcodes, themes, tables, and figures.
- Includes YAML front matter with metadata such as title, ID, slug, dates, canonical URL, excerpt, taxonomy terms, and featured image details.
- Supports optional HTTP content negotiation allowing clients to request Markdown via Accept: text/markdown headers on standard HTML URLs.
- Implements cache-aware handling using Vary: Accept headers and integrates with supported WordPress caching plugins while remaining agnostic to CDN configurations.
- Provides configurable CSS selectors to define main content containers and exclude unwanted elements like navigation or banners.
- Offers developer filters for access control, taxonomy inclusion, front matter customization, schema generation, and cache TTL management.
- Operates entirely on the WordPress site without requiring external APIs, SaaS services, or sending post content off-server.
TRANSLATION BOUNDARY
SimplyIrfan Markdown capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
SimplyIrfan Markdown and REEID Translate FAQ.
What does SimplyIrfan Markdown do?
SimplyIrfan Markdown has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does SimplyIrfan Markdown have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from SimplyIrfan Markdown?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate SimplyIrfan Markdown in a multilingual WordPress workflow.
REEID documents SimplyIrfan Markdown functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.