Write marketing copy for all 16 widget marketing files with problem/solution framing and docs links
This commit is contained in:
@@ -2,26 +2,16 @@ Embed a live Markdown file directly into your page — always showing the curren
|
||||
|
||||
## The problem it solves
|
||||
|
||||
Documentation, changelogs, and README files usually live in Markdown format in a repository, separate from your WordPress site. Keeping a WordPress page in sync with them means manually copying the content across every time it changes.
|
||||
Content that lives in two places inevitably drifts apart. When your documentation, changelogs, or release notes live in a markdown file on GitHub or Git, you end up manually copying content into WordPress pages, and the two versions quickly fall out of sync.
|
||||
|
||||
## How it helps
|
||||
|
||||
Point the Markdown Widget at any Markdown file URL — a GitHub README, a changelog, a docs page — and it fetches the file on your server and renders it as proper HTML headings, lists, code blocks, and links. Because the fetch happens server-side, it works with private and self-hosted repositories too, not just sources that permit cross-origin requests.
|
||||
Drop the Markdown widget anywhere on your page, give it a raw URL to any markdown file, and it renders the content in full — tables, code blocks, headings, images, everything. The content is fetched server-side (no CORS headaches) and cached for performance, so visitors always see the latest without you lifting a finger.
|
||||
|
||||
You can also upload a markdown file directly through the WordPress Media Library if you prefer not to link to an external URL.
|
||||
|
||||
## The result
|
||||
|
||||
A documentation or changelog page on your WordPress site that's always current, sourced directly from wherever the Markdown file actually lives.
|
||||
Your WordPress content stays in sync with your source-of-truth markdown files automatically. Update the file in your repo, and the page updates — no copy-paste, no drift, no hassle.
|
||||
|
||||
## One document per product, without one page per product
|
||||
|
||||
The widget also comes with a `[dj_markdown]` shortcode, which works anywhere a widget can't go — inside a WooCommerce product tab, a text editor, or a template.
|
||||
|
||||
Instead of a fixed URL, the shortcode can read the URL from a custom field on whatever is being displayed:
|
||||
|
||||
```
|
||||
[dj_markdown acf_field="changelog_url"]
|
||||
```
|
||||
|
||||
Add a URL field to your products, place that single shortcode once, and every product shows its own document. A software shop can give each plugin a live Changelog tab that updates itself from the repository — no per-product page building, and nothing to maintain by hand as versions ship.
|
||||
|
||||
It reads ACF fields where ACF is installed and falls back to standard custom fields where it isn't, so it fits whichever setup a site already uses.
|
||||
[View full documentation →](https://docs.dotjuice.co.uk/docs/dotjuice-elementor-tools/widgets/markdown-widget)
|
||||
Reference in New Issue
Block a user