Docs pass: add widget screenshots and expand the user guides
Add 21 screenshots across the Elementor Tools docs and rework the pages around them: clearer opening lines, settings tables that state defaults, and callouts for the parts people trip over. Also refreshes the Pro getting-started, Custom Product Tabs and Product Filter pages, plus the matching marketing copy. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -14,9 +14,9 @@ Elementor's own widget library, and even Elementor Pro's, leaves gaps — especi
|
||||
|
||||
**Keyword Linker** — automatically turn chosen keywords across your content into links, without manually editing every post.
|
||||
|
||||
**Markdown Widget** — embed a live Markdown file (a README, changelog, or documentation page) directly into a page.
|
||||
**Markdown Widget** — embed a live Markdown file (a README, changelog, or documentation page) directly into a page, or use its shortcode to pull the file from a custom field so each post or product shows its own document.
|
||||
|
||||
**WooCommerce widgets** — a set of four widgets addressing the most common WooCommerce styling and layout gaps: clickable variation buttons instead of dropdowns, styled category tiles, consistent My Account styling, and styleable pagination.
|
||||
**WooCommerce widgets** — a set of six widgets addressing the most common WooCommerce styling and layout gaps: clickable variation buttons instead of dropdowns, styled category tiles, an attribute-aware product grid with hover and image-rollover effects, consistent My Account styling, styleable pagination, and cascading taxonomy lists for "shop by category" navigation.
|
||||
|
||||
**WooCommerce Hacks** — an admin toolkit for the everyday WooCommerce account-page tweaks every store eventually needs (hiding tabs, redirect rules, category exclusions) plus a proper attribute colour-swatch manager.
|
||||
|
||||
|
||||
@@ -8,8 +8,22 @@ Documentation, changelogs, and README files usually live in Markdown format in a
|
||||
|
||||
## How it helps
|
||||
|
||||
Point the Markdown Widget at any publicly accessible Markdown file URL — a GitHub README, a changelog, a docs page — and it fetches and renders the file's content live in the visitor's browser, styled as proper HTML headings, lists, code blocks, and links.
|
||||
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.
|
||||
|
||||
## The result
|
||||
|
||||
A documentation or changelog page on your WordPress site that's always current, sourced directly from wherever the Markdown file actually lives.
|
||||
|
||||
## 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.
|
||||
|
||||
Reference in New Issue
Block a user