Title: System Markdown Alternate Author: Fabio Balossi Published: ઓગસ્ટ 9, 2026 Last modified: ઓગસ્ટ 28, 2026 --- પ્લગીન શોધો ![](https://ps.w.org/system-markdown-alternate/assets/banner-772x250.png?rev=3639207) ![](https://ps.w.org/system-markdown-alternate/assets/icon-256x256.png?rev=3639207) # System Markdown Alternate [Fabio Balossi](https://profiles.wordpress.org/system4pc/) દ્વારા [ડાઉનલોડ](https://downloads.wordpress.org/plugin/system-markdown-alternate.0.49.3.zip) [જીવંત પૂર્વદર્શન](https://gu.wordpress.org/plugins/system-markdown-alternate/?preview=1) * [વિગતો](https://gu.wordpress.org/plugins/system-markdown-alternate/#description) * [સમીક્ષાઓ](https://gu.wordpress.org/plugins/system-markdown-alternate/#reviews) * [સ્થાપન](https://gu.wordpress.org/plugins/system-markdown-alternate/#installation) * [ડેવલપમેન્ટ](https://gu.wordpress.org/plugins/system-markdown-alternate/#developers) [સપોર્ટ](https://wordpress.org/support/plugin/system-markdown-alternate/) ## વર્ણન System Markdown Alternate publishes a clean, machine-readable Markdown representation of your content. Append `.md` to any supported permalink and you get YAML front matter plus the post body converted to Markdown — with marketing clutter, forms and navigation widgets stripped out. ``` https://example.com/my-post/ → HTML https://example.com/my-post.md → Markdown (front matter + content) ``` It is built for the era of AI assistants, agents and technical scrapers that prefer plain Markdown over rendered HTML. It is **not** a generic SEO plugin. **[Read the full documentation](https://diecieventi.github.io/system-markdown-alternate/)**— installation, every setting in the panel, the endpoints, the shortcodes, the integrations and troubleshooting. #### Key features * **`.md` endpoint** for every supported, published, public post. * **Content negotiation**: the same Markdown is returned for `Accept: text/markdown` or `?format=markdown` requests. The `Accept` header is parsed with q-values, so a client that prefers HTML (higher q) still gets HTML. * **`Vary: Accept`** on negotiable URLs, so caches and CDNs that honour it keep the HTML and Markdown representations of the same address apart. Because some page caches key by URL only and ignore `Vary`, the negotiated Markdown (and ` 406`) responses are also sent non-cacheable, so safety never depends on `Vary` alone. * **Markdown discovery in HTML and HTTP**: supported canonical pages advertise the representation with both `` in the document head and a typed `Link: rel="alternate"` response header. The HTTP form is also available to `HEAD` requests. When `/llms.txt` is enabled, the same pages also point at it with `rel="describedby"`, the relation added by version 2 of the llms.txt specification, so an agent can find the site’s index from any article. * **Correct HTTP headers**: `Content-Type: text/markdown`, `X-Robots-Tag` (default` noindex, follow`) and a `Link: rel="canonical"` back to the HTML. * **Clean conversion**: Gutenberg blocks are rendered individually (no injected related/CTA blocks), excluded blocks/shortcodes/CSS classes are removed, code blocks become fenced blocks, URLs are made absolute, and an embedded video, tweet or track leaves a link to what it embeds rather than an empty gap. Clickable link cards keep their name too: the invisible overlay link such cards are built from takes the name the markup declares, instead of arriving with no text at all. * **`/llms.txt` endpoint** (optional): an index of your content for LLMs and AI agents. An optional **enriched mode** (off by default) adds a site summary, a curated “Key content” section, a description for each entry and an `Optional` section for older posts. Another optional toggle appends the **last modified date** (`updated: YYYY-MM-DD`) to every entry, so crawlers can spot changed content without re-fetching each URL. * **Custom taxonomies in the front matter** (optional, nothing selected by default): tick the taxonomies you want and their terms are added as a `taxonomies:` block, alphabetically ordered. Nothing is ever published automatically: a taxonomy registered by another plugin appears in the panel unticked, and taxonomies with no public term archive are labelled as internal. * **Extra custom fields** (optional, empty by default): list the post meta keys whose values belong in the document and they are appended to the body. One setting covers ACF, JetEngine, Meta Box and WordPress’s own Custom Fields box, because underneath they all store post meta — so a page whose text comes partly from a template’s fields is no longer published half missing. Nothing is detected automatically, and posts without the field keep their document and their cache validator untouched. * **Object cache** with proactive invalidation on post edit, plugin update and settings change: a persistent object cache is used when one is available, falling back to transients otherwise. * **Optional `.md` hit counter** (off by default): counts how many times the Markdown endpoint is served, split bot vs human, with a further breakdown naming a few known AI crawlers (ClaudeBot, GPTBot, PerplexityBot, CCBot) among the bot total. Privacy by design: only aggregate daily totals are stored — no IP addresses, no user-agent strings, no per-visitor data, no cookies, no external calls. * **Bricks pages get a real `.md`**: rendered through Bricks’ own API (never re- implemented), with the same excluded-shortcode/excluded-class rules as everything else, plus a new “excluded builder elements” list for Bricks chrome (forms, nav menus, share bars, tables of contents, breadcrumbs). A post switched back to _Render with WordPress_ is unaffected. Detection is per post, never per post type: a site that builds its pages with Bricks while its articles stay in the ordinary editor keeps every one of those articles. * **Other page builders are handled honestly**: a post rendered by Elementor, Divi, WPBakery, Oxygen, Beaver Builder or Breakdance has no Markdown representation— its content is not in `post_content`, or is there as the builder’s own layout shortcodes — so it returns 404 instead of an empty or misleading document, and it stays out of `/llms.txt`, the alternate links and the shortcodes. * **Admin panel** to choose which post types are exposed and to tune cache, exclusions and headers — no post type is exposed until you pick one. Each type shows what its published posts are actually built with (for example _12 Bricks, 3 Gutenberg_), so a page builder that costs you the Markdown version is visible before it surprises you. * **Shortcodes** `[sysmda_md_url]` (the Markdown URL), `[sysmda_md_download]` ( a bare download link), and `[sysmda_md_actions]` (an opt-in Copy as Markdown split button with copy, new-tab view and download actions). * **Optional integrations**, shown only when the related plugin is active: - **Advanced Custom Fields**: add a subtitle and a TL;DR (from ACF fields) as a preamble between the H1 and the body. - **GenerateBlocks 2.x**: a `{{sysmda_md_url}}` Dynamic Tag, available automatically, usable in element fields (e.g. a Button URL). * **Developer-extensible**: every behaviour above — which content is served, the headers, the caching, the conversion pipeline, the front matter and `/llms.txt`— is exposed as a WordPress filter. See the FAQ below for examples and a link to the full documented list. ## સ્ક્રીનશોટ [⌊Settings — General: pick the content types that expose a .md (nothing is served until at least one is ticked) and set the cache TTL. The sidebar reports the /llms. txt status at a glance.⌉⌊Settings — General: pick the content types that expose a .md (nothing is served until at least one is ticked) and set the cache TTL. The sidebar reports the /llms.txt status at a glance.⌉[ Settings — General: pick the content types that expose a `.md` (nothing is served until at least one is ticked) and set the cache TTL. The sidebar reports the `/llms. txt` status at a glance. [⌊Settings — Markdown output: what stays out of the .md. Excluded shortcodes, blocks and CSS classes (leave empty for the built-in defaults), plus the custom taxonomies added to the front matter and the ACF fields.⌉⌊Settings — Markdown output: what stays out of the .md. Excluded shortcodes, blocks and CSS classes (leave empty for the built-in defaults), plus the custom taxonomies added to the front matter and the ACF fields.⌉[ Settings — Markdown output: what stays out of the `.md`. Excluded shortcodes, blocks and CSS classes (leave empty for the built-in defaults), plus the custom taxonomies added to the front matter and the ACF fields. [⌊Settings — llms.txt: enable the endpoint, the enriched output and the last modified date on each entry, then add the site summary and the curated key content.⌉⌊Settings— llms.txt: enable the endpoint, the enriched output and the last modified date on each entry, then add the site summary and the curated key content.⌉[ Settings — llms.txt: enable the endpoint, the enriched output and the last modified date on each entry, then add the site summary and the curated key content. [⌊Settings — Integrations: the [sysmda_md_url], [sysmda_md_download] and [sysmda_md_actions] shortcodes, with the GenerateBlocks and ACF detection status.⌉⌊Settings — Integrations: the [sysmda_md_url], [sysmda_md_download] and [sysmda_md_actions] shortcodes, with the GenerateBlocks and ACF detection status.⌉[ Settings — Integrations: the `[sysmda_md_url]`, `[sysmda_md_download]` and `[sysmda_md_actions]` shortcodes, with the GenerateBlocks and ACF detection status. [⌊Settings — Advanced: the X-Robots-Tag header, the opt-in LiteSpeed cache bypass rules and the .md hit counter, split bot vs human.⌉⌊Settings — Advanced: the X-Robots- Tag header, the opt-in LiteSpeed cache bypass rules and the .md hit counter, split bot vs human.⌉[ Settings — Advanced: the `X-Robots-Tag` header, the opt-in LiteSpeed cache bypass rules and the `.md` hit counter, split bot vs human. [⌊The [sysmda_md_actions] split button on the front end: copy the Markdown, view it in a new tab, or download it — no theme styling required.⌉⌊The [sysmda_md_actions] split button on the front end: copy the Markdown, view it in a new tab, or download it — no theme styling required.⌉[ The `[sysmda_md_actions]` split button on the front end: copy the Markdown, view it in a new tab, or download it — no theme styling required. ## સ્થાપન 1. Upload the plugin to `/wp-content/plugins/` or install it through the Plugins screen in WordPress. 2. Activate the plugin. 3. Go to **Settings Markdown Alternate** and select at least one post type under ** Supported post types**. Until you do, the plugin stays inactive. 4. Visit any supported post and append `.md` to its URL. No rewrite rules are added, so no permalink flush is required. ## એફએક્યુ (FAQ) ### Why is nothing served at the .md URL? By default no post type is enabled. Open **Settings Markdown Alternate** and tick at least one post type under **Supported post types**. ### Which content does NOT get a .md version? Anything the endpoint would not be able to serve honestly: * content types not enabled in the settings page; * drafts, pending and private content, and password-protected posts; * media attachments (always excluded); * posts with a **non-standard post format** — aside, status, quote, link, gallery, image, video, audio, chat. These are short snippets, usually untitled, with no editorial body worth serving as a document. Use the `sysmda_markdown_excluded_post_formats` filter to change that; * posts **rendered by an unsupported page builder** — Elementor, Divi, WPBakery, Oxygen, Beaver Builder or Breakdance. Their content is stored outside `post_content`, or stored in it as the builder’s own layout shortcodes, so the Markdown would come out either empty or full of layout wrappers converted as prose. A 404 is the honest answer; use the `sysmda_markdown_unsupported_builders` filter if you would rather have the empty document. **Bricks pages are supported** and get a real `.md`, rendered through Bricks’ own API — see the next question; * **WooCommerce’s cart, checkout and my-account pages**. They are ordinary published pages, but their body without a shopping session is WooCommerce’s own placeholder text, not anything written for a reader. The shop page is unaffected — that one is real content. Use the `sysmda_markdown_excluded_woocommerce_pages` filter to change that. That last rule is decided **per post**, from the builder’s own render mode. Activating a builder does not affect posts you did not build with it, and a post you switched back to the WordPress editor keeps its Markdown version even though the builder data is still stored. Nothing is read from the post content, so an article quoting`[ et_pb_section]` in a code sample is not mistaken for a Divi page. ### How does the Bricks `.md` work? The `.md` is built by calling Bricks’ own `\Bricks\Frontend::render_data()` on the page’s stored element tree — the plugin never re-implements Bricks’ elements. The existing `md-exclude` CSS class already works on any Bricks element (set it in the element’s _CSS Classes_ field); a new **Excluded builder elements** list under _Settings Markdown Alternate Markdown output_ additionally strips Bricks chrome by default— forms, nav menus, share bars, tables of contents, breadcrumbs — the same way excluded CSS classes are stripped, and it only adds to that list, never replaces it. A page switched to _Render with WordPress_ is served from `post_content` as usual, whether or not Bricks data is still stored on it. Markdown is also never served for URL _variants_ of a post — its feed, its oEmbed view, its trackback endpoint, paged comments and the sub-pages of a post split with` ` — even with `Accept: text/markdown`. Only the canonical permalink and its `.md` URL return Markdown. ### What does the Markdown output look like? Each `.md` response is a UTF-8 document with a YAML front-matter block (title, URL, Markdown URL, published/modified dates, and — when available — author, featured image, categories, tags and a description), followed by the `# Title` heading and the post body converted to clean Markdown. The exact keys, their order and the escaping rules are documented as a stable contract, with conformance tests, in the [Markdown output format](https://github.com/diecieventi/system-markdown-alternate/blob/main/docs/output-format.md) reference. ### Can I include my custom taxonomies? Yes. Open **Settings Markdown Alternate Markdown output** and tick the ones you want under _Custom taxonomies_: the front matter then carries a `taxonomies:` block with their terms, sorted alphabetically. Categories and tags already have their own keys and are not repeated. Nothing is selected by default and nothing is ever added implicitly — a taxonomy registered by a plugin you install later shows up in the list unticked, so it cannot start publishing itself. Taxonomies used for editorial classification only, with no public term archive (“publicly queryable” off), are labelled as internal in the list: they are still selectable, but only on purpose. Developers can curate the list further with the `sysmda_front_matter_taxonomy_slugs` filter. ### How do I exclude part of a post from the Markdown? Add one of the CSS classes `no-md`, `md-exclude` or `exclude-from-markdown` to a block; the element (and its children) is removed from the Markdown output. You can customize the list with the `sysmda_markdown_excluded_classes` filter. ### Does it affect my SEO? The `.md` responses are sent with `X-Robots-Tag: noindex, follow` and a `Link: rel ="canonical"` header pointing back to the HTML version, so search engines are told to prefer the original page. ### How do I get the Markdown URL in a button or template? Use the `[sysmda_md_url]` shortcode. If you run GenerateBlocks 2.x, the `{{sysmda_md_url}}` Dynamic Tag is available automatically — use it in element fields such as a Button URL. When the post has no `.md`, the tag resolves to an empty value so GenerateBlocks can hide the element instead of leaving a broken link. ### How do I add Copy as Markdown actions for readers? Use `[sysmda_md_actions]`. It renders a GitHub-style split button: the main action copies the complete Markdown document, while the dropdown offers **Copy as Markdown**,** View as Markdown** in a new tab and **Download Markdown**. Use `[sysmda_md_actions id="123"]` for a specific post. The component renders only where the shortcode is placed. Its small stylesheet and dependency-free script are loaded only on pages that actually render it, including placements in templates, widgets and secondary loops. The menu opens aligned to the button and drops below it, moving to the opposite side or above only when the screen edge leaves no room. Like the other shortcodes, it outputs nothing when the target post has no Markdown version. ### How do I let readers download the .md instead of opening it? Use the `[sysmda_md_download]` shortcode. It prints a link that saves the file: ``` [sysmda_md_download] [sysmda_md_download text="Save the Markdown"] [sysmda_md_download id="123"] ``` The link carries the HTML `download` attribute, which is what tells the browser to save the file instead of displaying it. The file name comes from the post slug. Nothing changes on the server side: the `.md` URL itself behaves exactly as it always has, so opening it directly still shows whatever your browser normally does with a Markdown file. The shortcode outputs a plain link with a single `sysmda-md-download` class, and the plugin loads **no CSS and no JavaScript** on your site for it. Any styling is your theme’s job. Like `[sysmda_md_url]`, it outputs nothing when the post has no Markdown version, so it can never produce a link to a 404. ### Is the .md content cached? Yes (default 24h). It uses a persistent object cache when one is available and falls back to transients otherwise. The cache is regenerated automatically when the post is edited, when the plugin is updated, or when you save the settings — and also when something outside the post changes what the Markdown says: a synced pattern, the featured image, the description, an ACF field, the author’s display name, the permalink structure or the site address. That is the cache inside WordPress. Caches _outside_ it — your browser, a page cache, Varnish, a CDN — are told `Cache-Control: public, max-age=0, must-revalidate`: they may keep a copy, but they must ask the site whether it is still current before serving it, and the answer is a small `304 Not Modified` when nothing changed. So a `.md` cannot keep circulating after you edit the article, without depending on anyone purging it — which matters, because page caches purge the article’s URL and do not know its `.md` version exists. If your infrastructure has its own purge mechanism and you would rather trade that guarantee for raw speed, the `sysmda_cache_control` filter lets you set a real lifetime. ### Can I customize the plugin from my own code? Yes: the plugin is developer-extensible through WordPress filters — which content is served, the HTTP headers, the caching, every stage of the conversion pipeline, the front matter and `/llms.txt` can all be changed from a theme or a site plugin. A few examples: ``` add_filter( 'sysmda_markdown_output', fn( $md, $post ) => $md . "\n---\nCustom footer.\n", 10, 2 ); add_filter( 'sysmda_markdown_excluded_classes', fn( $classes ) => array_merge( $classes, array( 'my-private-block' ) ) ); add_filter( 'sysmda_llms_txt_enriched', '__return_true' ); ``` Every filter, with its default value, what changing it does and how much compatibility it promises, is documented here: [Developer extension API](https://github.com/diecieventi/system-markdown-alternate/blob/main/docs/filters.md). Hooks are labelled Stable or Advanced: the Advanced ones are supported and documented, but may still evolve while the plugin is pre-1.0. The Markdown output format itself is a separate, stronger contract. ### Content negotiation misbehaves behind LiteSpeed cache. What can I do? Some LiteSpeed cache configurations key the page cache by URL only and ignore `Vary: Accept`, so a cached representation can be served regardless of the `Accept` header. The plugin already tells the cache not to store the negotiated Markdown; if requests for Markdown on the permalink still receive cached HTML, enable **LiteSpeed cache compatibility** in **Settings Markdown Alternate Advanced**: it adds `.htaccess` rules that make Markdown-negotiating requests bypass the LiteSpeed page cache (normal browser traffic stays cached; on other servers the rules are inert). Then purge the LiteSpeed cache. The explicit `.md` URLs are not affected and remain fully cacheable. Not sure whether your host is affected? Whether a LiteSpeed server honours `Vary: Accept` depends on the host and cannot be detected automatically, so if in doubt simply enable the option: it is the safe choice, and on hosts that already behave correctly the rules are just redundant. To test it yourself: open a post in a normal browser first (so its HTML gets cached), then request the same permalink with a Markdown Accept header, for example: ``` curl -A "Mozilla/5.0" -H "Accept: text/markdown" https://example.com/my-post/ ``` If the response is HTML (often with an `x-litespeed-cache: hit` header) instead of Markdown, your server ignores `Vary: Accept` and you need the option. The browser- like `-A` value matters: a WAF/CDN may block non-browser user agents. ### Does it work behind a CDN (Cloudflare, Fastly, Varnish)? The `.md` URLs need nothing from you. The negotiated permalink depends on your CDN, and the difference matters: * the dedicated `.md` URLs are their own cache key — one URL, one representation, nothing to mix up. Any CDN may store them, and `Cache-Control: public, max-age =0, must-revalidate` means it must revalidate before reuse, which is a cheap ` 304 Not Modified` when nothing changed. This route works everywhere, with no configuration; * the **negotiated** permalink (`Accept: text/markdown` on the HTML page’s own URL) is sent `no-store`, so a Markdown response is never stored and can never be handed to a browser that asked for HTML. That closes the harmful direction, but it cannot fix the opposite one: if your CDN caches the HTML page by URL and ignores `Vary: Accept`, a later Markdown request is answered at the edge, PHP never runs, and the client simply gets HTML. `Vary: Accept` is sent on every negotiable response, which is all a cache that honours it needs. So for the negotiated route one of these has to be true: your CDN honours `Vary: Accept`, or you configure it to bypass the cache — or to vary its cache key — for requests whose `Accept` mentions `text/markdown`. On LiteSpeed the plugin ships that bypass for you: see the previous entry. If you are not sure which case you are in, the three-request test below tells you in a few seconds. And the `.md` URL keeps working regardless — it is what the `rel="alternate"` link and `/llms.txt` advertise, so agents following either one are unaffected. Two more things worth knowing. Some CDNs rewrite validators in transit — Cloudflare turns a strong `ETag` into a weak one — which the plugin handles: incoming validators are compared with the weak-comparison rules, so revalidation keeps working either way. And if you would rather have the CDN really cache the `.md` instead of revalidating it, set a lifetime with the `sysmda_cache_control` filter, keeping in mind that nothing purges a `.md` when you edit the post. ### How do I check my cache is not mixing HTML and Markdown? Send three requests to the same permalink, in this order, and compare the `content- type` of each: ``` curl -sI -A "Mozilla/5.0" -H "Accept: text/markdown" https://example.com/my-post/ curl -sI -A "Mozilla/5.0" -H "Accept: text/html" https://example.com/my-post/ curl -sI -A "Mozilla/5.0" -H "Accept: text/markdown" https://example.com/my-post/ ``` The first and third must answer `text/markdown`, the second `text/html`. If the second returns Markdown, or the third returns HTML, something in front of PHP is serving one stored representation to everyone: look at the `age`, `x-cache`, `cf- cache-status` or `x-litespeed-cache` headers to see which layer, and purge it (on LiteSpeed, see the entry above). To check revalidation on a `.md` URL, read its `etag` and send it back: ``` curl -sI -A "Mozilla/5.0" https://example.com/my-post.md curl -sI -A "Mozilla/5.0" -H 'If-None-Match: W/"paste-the-etag-here"' https://example.com/my-post.md ``` The second request should answer `304` with no body. A `200` instead is usually not the plugin: some stacks strip conditional headers from the request before PHP ever sees them (observed with nginx configured to cache the location). It is a missed optimisation, not a correctness problem — the response is still current. As above, the browser-like `-A` value matters: a WAF/CDN may block non-browser user agents outright, and a block page is easy to mistake for a plugin bug. ## સમીક્ષાઓ આ પ્લગઇન માટે કોઈ સમીક્ષાઓ નથી. ## ફાળો આપનાર & ડેવલપર્સ આ ઓપન સોર્સ સોફ્ટવેર છે. નીચેના લોકો એ આ પ્લગિન માટે ફાળો આપ્યો છે. ફાળો આપનારા * [ Fabio Balossi ](https://profiles.wordpress.org/system4pc/) [“System Markdown Alternate” ને તમારી ભાષામાં અનુવાદ કરો.](https://translate.wordpress.org/projects/wp-plugins/system-markdown-alternate) ### વિકાસમાં રસ ધરાવો છો? [કોડ બ્રાઉઝ કરો](https://plugins.trac.wordpress.org/browser/system-markdown-alternate/), જોવો[અસ્વીએન રેપોઝિટરીમાંથી](https://plugins.svn.wordpress.org/system-markdown-alternate/), અથવા સબ્સ્ક્રાઇબ કરો[ડેવલપમેન્ટ](https://plugins.trac.wordpress.org/log/system-markdown-alternate/) દ્વારા[આરઅસઅસ](https://plugins.trac.wordpress.org/log/system-markdown-alternate/?limit=100&mode=stop_on_copy&format=rss). ## ચેન્જલૉગ #### 0.49.3 * Updated the wordpress.org listing screenshots to the current settings panel ( previously several versions out of date) and added a sixth screenshot showing the `[sysmda_md_actions]` front-end split button. Metadata and repository tooling only — no plugin code, output or behaviour changes. #### 0.49.2 * The Live Preview blueprint now lands on the site’s front page instead of a raw`. md` response, so a first-time visitor sees an ordinary WordPress site to click around rather than a downloaded file with no context. Metadata and repository tooling only — no plugin code, output or behaviour changes. #### 0.49.1 * The plugin now ships a `.wordpress-org/blueprints/blueprint.json`, which enables the **Live Preview** button on this listing page: visitors can try the plugin live, active, in WordPress Playground, with no install. Metadata and repository tooling only — no plugin code, output or behaviour changes. [View the full changelog](https://github.com/diecieventi/system-markdown-alternate/blob/main/CHANGELOG.md) ## મેટા * વર્ઝન **0.49.3** * છેલ્લી અપડેટ: **4 કલાક પહેલા** * સક્રિય સ્થાપનો: **10 કરતા ઓછા** * વર્ડપ્રેસ વર્ઝન ** 6.1 અથવા ઉચ્ચતર ** * **7.0.4** સુધી પરીક્ષણ કર્યું * PHP સંસ્કરણ ** 7.4 અથવા ઉચ્ચતર ** * ભાષા * [English (US)](https://wordpress.org/plugins/system-markdown-alternate/) * ટૅગ્સ: * [AI](https://gu.wordpress.org/plugins/tags/ai/)[content negotiation](https://gu.wordpress.org/plugins/tags/content-negotiation/) [LLM](https://gu.wordpress.org/plugins/tags/llm/)[llms.txt](https://gu.wordpress.org/plugins/tags/llms-txt/) [markdown](https://gu.wordpress.org/plugins/tags/markdown/) * [વિગતવાર દૃશ્ય](https://gu.wordpress.org/plugins/system-markdown-alternate/advanced/) ## પૉઇન્ટ્સ હજુ સુધી કોઈ સમીક્ષા સબમિટ કરવામાં આવી નથી. [તમારા અભિપ્રાયો](https://wordpress.org/support/plugin/system-markdown-alternate/reviews/#new-post) [બધા સમીક્ષાઓ જુઓ](https://wordpress.org/support/plugin/system-markdown-alternate/reviews/) ## ફાળો આપનારા * [ Fabio Balossi ](https://profiles.wordpress.org/system4pc/) ## સપોર્ટ કંઈક કહેવું છે? મદદ જોઈએ છે? [આધાર ફોરમ જુઓ](https://wordpress.org/support/plugin/system-markdown-alternate/)