Add marketing docs from dotjuice-elementor-tools, dotjuice-elementor-tools-pro, and dotjuice-pagespeed
This commit is contained in:
@@ -0,0 +1,15 @@
|
|||||||
|
# EspoCRM Lead Capture
|
||||||
|
|
||||||
|
Send Elementor form submissions straight into EspoCRM — no manual re-entry, no separate integration tool.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
A contact or lead form on your site is only half the job — those submissions need to end up in your CRM to actually be followed up on. Without a direct integration, that usually means either manually copying leads across from an email inbox, or paying for a third-party automation tool just to bridge two systems that should talk to each other directly.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Add "EspoCRM Webhook" as a submit action on any Elementor Pro Form, point it at your EspoCRM Lead Capture endpoint, and every submission is sent straight through in real time — no separate integration platform, no delay. Paste an example payload from EspoCRM and field mapping is worked out automatically. UK phone numbers are formatted consistently before they arrive, so your CRM data stays clean without any manual tidying.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Leads land in EspoCRM the moment a form is submitted, formatted consistently, with nothing manual in between.
|
||||||
29
marketing/dotjuice-elementor-tools-pro/documentation/marketing/overview.md
Executable file
29
marketing/dotjuice-elementor-tools-pro/documentation/marketing/overview.md
Executable file
@@ -0,0 +1,29 @@
|
|||||||
|
# Dotjuice Elementor Tools Pro
|
||||||
|
|
||||||
|
The premium widget set for serious WooCommerce stores — AJAX product filtering, a fully custom cart, quick view, custom product tabs, frontend ACF forms, and watermark-free screenshots.
|
||||||
|
|
||||||
|
## Built for stores that have outgrown the basics
|
||||||
|
|
||||||
|
The free Dotjuice Elementor Tools plugin covers the everyday styling gaps in WooCommerce. Pro goes further, adding the kind of advanced shopping-experience features that used to mean custom development: faceted filtering with clean bookmarkable URLs, a cart widget with instant AJAX quantity updates, a quick-view modal that keeps shoppers on the page, and a fully rebuilt product tabs system with deep styling reach into your reviews section.
|
||||||
|
|
||||||
|
## What's included
|
||||||
|
|
||||||
|
**Woo Product Filter** — a genuine faceted filtering system: category, tag, brand, or any custom attribute, with list or colour-swatch display, AJAX-refreshed results, and clean, bookmarkable, shareable filtered URLs — the kind of filtering shoppers expect from major ecommerce sites.
|
||||||
|
|
||||||
|
**Woo Cart** — a complete, from-scratch cart widget with a two-column layout, an optional instant AJAX quantity-update mode with no page reload, and dozens of styling controls reaching every part of the cart, coupon box, and totals panel.
|
||||||
|
|
||||||
|
**Woo Quick View** — lets shoppers preview a product in a popup without leaving your shop grid, triggered by a button that appears automatically across your product loops, complete with hover-preloading so the popup feels instant.
|
||||||
|
|
||||||
|
**Woo Custom Product Tabs** — a full rebuild of the WooCommerce product tabs area as a styleable desktop-tabs/mobile-accordion component, with the ability to add unlimited custom tabs and deep styling control down into your reviews and rating form.
|
||||||
|
|
||||||
|
**Woo Add Product Tab** — the lightweight option when you just need to bolt one extra tab onto the existing WooCommerce tabs, no rebuild required.
|
||||||
|
|
||||||
|
**ACF Frontend Form** — let visitors edit Advanced Custom Fields content directly from the front end, using ACF's own native form interface, no admin access required.
|
||||||
|
|
||||||
|
**Watermark-free screenshots** — every Screenshot Capture widget from the free plugin renders clean, with no Dotjuice watermark.
|
||||||
|
|
||||||
|
**EspoCRM Lead Capture** — send Elementor Pro Form submissions straight into EspoCRM in real time, with automatic field mapping and UK phone number formatting.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
The advanced WooCommerce shopping-experience features that turn a functional store into a genuinely modern one — filtering, cart, and quick view that feel like they were custom-built, without the custom development cost.
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# ACF Frontend Form
|
||||||
|
|
||||||
|
Let visitors edit Advanced Custom Fields content from the front end — no admin access, no wp-admin, just a form on your page.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Advanced Custom Fields is one of the most powerful tools in WordPress for structured content, but editing it has always meant going into wp-admin. For membership sites, directories, community-submitted content, or client self-service portals, that's a real barrier.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
ACF Frontend Form renders ACF's own native form interface — the same tabs, repeaters, and field layouts you're used to from the admin edit screen — directly on any front-end page, for the post or page currently being viewed. Choose exactly which field groups are editable, and whether the post title and content are included too.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Genuine front-end content editing, using ACF's real, familiar form fields — not a simplified imitation.
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
# Woo Add Product Tab
|
||||||
|
|
||||||
|
Add one extra tab to your product page's existing tabs — no template rebuild required.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Sometimes you just need one more tab next to WooCommerce's Description, Additional Information, and Reviews — a sizing guide, a shipping note, a care instructions panel — without rebuilding the entire tabs section.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo Add Product Tab appends a single, fully-editable tab to WooCommerce's native tabs, with a title, rich-text content, and control over where it sits in the tab order — all visually, in a few clicks.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
One extra tab exactly where you want it, without touching the rest of your product tabs setup.
|
||||||
|
|
||||||
|
*Need to rebuild and restyle the whole tabs area, with multiple custom tabs and accordion support on mobile? See [Woo Custom Product Tabs](woo-custom-product-tabs.md).*
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Woo Cart
|
||||||
|
|
||||||
|
A complete, from-scratch cart widget — with instant AJAX quantity updates and deep styling control, no Elementor Pro required.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
A store's cart page is one of the last steps before checkout, and default cart styling rarely matches the rest of a carefully designed store. Elementor Pro has its own cart widget, but if you're not on Elementor Pro, or you want more granular styling control than it offers, there's a gap.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo Cart is a ground-up cart widget: item rows with thumbnail, name, variation details, a quantity stepper, and pricing; a coupon box; and a totals panel with checkout button — all restyled through more than a dozen dedicated style sections. Switch on AJAX quantity updates and shoppers can adjust amounts without a page reload at all, with the totals panel updating live, including coupon and discount rows.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A cart experience that feels instant and looks exactly like the rest of your store, without needing Elementor Pro.
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Woo Custom Product Tabs
|
||||||
|
|
||||||
|
A complete rebuild of your product tabs — styleable down to the reviews and rating form, with a built-in mobile accordion.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
WooCommerce's default product tabs (Description, Additional Information, Reviews) are functional but offer minimal styling control, and turn into an awkward stacked layout on mobile with no accordion behaviour built in.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo Custom Product Tabs replaces the entire tabs area with a fully restyled desktop-tabs / mobile-accordion component. Hide any of the default tabs you don't need, add as many custom tabs as you like — rich text, or an entire embedded Elementor template — and reach deep into the reviews section itself: avatar styling, star ratings, review cards, and the review submission form all get their own dedicated controls.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A product tabs section that looks genuinely custom-built, with reviews that finally match the rest of your store's design — and a proper accordion on mobile, not just a cramped stack.
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
# Woo Product Filter
|
||||||
|
|
||||||
|
Genuine faceted product filtering — category, attribute, brand, or tag — with instant AJAX results and clean, shareable URLs.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Shoppers expect to filter by colour, size, brand, or category and see results update instantly, with a URL they can bookmark or share. Building that properly — with correct product counts, dependent filters, and URLs that still work when shared or reloaded — is normally a serious development project.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo Product Filter gives you as many filter groups as you need, each pulling from a category, tag, brand, or any custom attribute, displayed as a list or as clickable buttons — including real colour swatches for attributes like colour. Results refresh instantly via AJAX (or update the page URL directly, your choice), term counts update live so shoppers always see what's actually available, and every filtered view has a clean, bookmarkable URL that reproduces the exact same results when shared or reloaded — even with JavaScript disabled.
|
||||||
|
|
||||||
|
You can even set up dependent filters — a "Size" group that only appears once a category is chosen, for example — for a genuinely guided filtering experience.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
The kind of faceted filtering shoppers expect from major ecommerce sites, built entirely through Elementor controls.
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Woo Quick View
|
||||||
|
|
||||||
|
Let shoppers preview a product without ever leaving your shop grid.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Every click away from a product grid is a chance for a shopper to lose momentum — and browsing a busy category means a lot of back-and-forth between the grid and individual product pages just to check details, sizes, or images.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo Quick View adds a button to every product in your grid that opens the full product view in a popup — sizes, images, description, add to cart — without navigating away. The button appears automatically across your product loops once switched on, including on variable products where it can replace the "Select options" link entirely. Hovering a button quietly preloads the popup content in the background, so by the time a shopper actually clicks, it feels instant.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A faster, more fluid browsing experience that keeps shoppers on your grid, discovering more products instead of clicking in and out of individual pages.
|
||||||
31
marketing/dotjuice-elementor-tools/documentation/marketing/overview.md
Executable file
31
marketing/dotjuice-elementor-tools/documentation/marketing/overview.md
Executable file
@@ -0,0 +1,31 @@
|
|||||||
|
# Dotjuice Elementor Tools
|
||||||
|
|
||||||
|
Free, practical Elementor widgets built for real WordPress and WooCommerce sites — screenshot capture, dark mode, WooCommerce styling fixes, and small utilities that solve problems the native widgets don't.
|
||||||
|
|
||||||
|
## Why these widgets exist
|
||||||
|
|
||||||
|
Elementor's own widget library, and even Elementor Pro's, leaves gaps — especially around WooCommerce, where the native shop and product widgets often need extra work to look and behave the way a real store needs. Dotjuice Elementor Tools fills those gaps with a set of focused, well-built widgets, each solving one specific problem well rather than trying to be a do-everything mega-plugin.
|
||||||
|
|
||||||
|
## What's included
|
||||||
|
|
||||||
|
**Screenshot Capture** — drop a live, auto-updating screenshot of any URL onto your page, styled and cached like a normal image.
|
||||||
|
|
||||||
|
**Dark Mode Toggle** — a site-wide light/dark mode switch that works with your existing Elementor Global Colors, no redesign required.
|
||||||
|
|
||||||
|
**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.
|
||||||
|
|
||||||
|
**Image Carousel Transform** — add hover effects, filters, and a cleaner lightbox trigger to Elementor Pro's native Image Carousel.
|
||||||
|
|
||||||
|
**WooCommerce widgets** — a set of five widgets addressing the most common WooCommerce styling and layout gaps: clickable variation buttons instead of dropdowns, styled category tiles, an attribute-driven extended product grid, consistent My Account styling, and styleable pagination.
|
||||||
|
|
||||||
|
**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.
|
||||||
|
|
||||||
|
## Built to work with what you already have
|
||||||
|
|
||||||
|
Every widget in this plugin is designed to sit alongside your existing theme, Elementor Pro, and WooCommerce setup rather than fight it — extending native functionality where possible instead of replacing it wholesale.
|
||||||
|
|
||||||
|
## Free forever, with a Pro upgrade path
|
||||||
|
|
||||||
|
Every widget listed here is free, permanently. [Dotjuice Elementor Tools Pro](../../../dotjuice-elementor-tools-pro/documentation/marketing/overview.md) adds advanced WooCommerce widgets (AJAX product filtering, a full cart widget, quick view, custom product tabs), ACF frontend forms, and watermark-free screenshots for stores and sites that need to go further.
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
# Product Attribute Colours
|
||||||
|
|
||||||
|
A proper colour manager for your product attributes — the missing piece behind real colour swatches on your store.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
WooCommerce doesn't have a built-in way to say "this Red attribute term is actually this exact shade of red" — so building colour swatches for variable products usually means custom development or a dedicated (often paid) swatches plugin.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Product Attribute Colours gives every term in any of your product attributes (Colour, Material, or any custom attribute) its own colour picker, with support for multiple terms sharing the same swatch colour — perfect for near-identical shades like "Ash", "Carbon Grey", and "Slate" that should all display the same swatch.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A central place to define your product colours once, ready to power colour swatches anywhere on your store that supports them.
|
||||||
|
|
||||||
|
*Configuring colours here is free. Displaying them as clickable swatches on your product pages uses the [Woo Add to Cart Transform](widgets/woo-add-to-cart-transform.md) widget's swatch mode, which is a [Pro](../../../dotjuice-elementor-tools-pro/documentation/marketing/overview.md) feature.*
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
# Dark Mode Toggle
|
||||||
|
|
||||||
|
A one-click, site-wide dark mode switch — using the color palette you've already built in Elementor.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Dark mode is one of the most-requested features on modern websites, but building it properly usually means maintaining a whole second stylesheet, or wiring up custom CSS variables by hand across every template.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dark Mode Toggle works directly with Elementor's own Global Colors — the primary, secondary, text, and accent colors you've already set up as part of your site's design. Add the toggle anywhere on your site, choose a dark palette for each of those four global colors, and clicking it switches your entire site into dark mode instantly, remembered for that visitor on their next visit too.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A genuine site-wide dark mode, built entirely from colors you already control through Elementor — no separate stylesheet to maintain.
|
||||||
|
|
||||||
|
*Note: this widget relies on your theme and Elementor Kit consistently using Elementor's Global Colors throughout your design — the more consistently they're used, the more complete the dark mode effect will be.*
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Extended Product Loop
|
||||||
|
|
||||||
|
Show every colour, size, or style variant of a product as its own tile — a "shop by option" grid, not just a shop by product.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
A standard product grid shows one tile per product, no matter how many colours or variants it comes in — a shopper browsing "red items" has to click into a t-shirt product just to discover it comes in red at all.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Extended Product Loop builds a grid that includes each individual product variant matching a chosen attribute as its own tile, alongside your regular products — so a t-shirt with three colour options can show as three separate, individually-imaged tiles in a "shop by colour" style layout.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A browsing experience built around the attribute your customers actually shop by, not just the parent product list.
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
# Image Carousel Transform
|
||||||
|
|
||||||
|
Give Elementor Pro's native Image Carousel the hover effects and polish it doesn't have out of the box.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Elementor Pro's Image Carousel widget is functional but visually plain — no built-in hover transforms, no filter effects, and a lightbox trigger that takes over the whole slide rather than offering a dedicated zoom button.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Image Carousel Transform adds a layer of styling on top of the native carousel: hover and normal-state transforms (scale, offset), box-shadow and CSS filter effects, a forced consistent slide height, and the option to move the lightbox trigger into its own small zoom button rather than making the entire slide clickable.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A carousel that looks like it came from a premium page-builder theme, styled entirely through Elementor controls — no custom CSS required.
|
||||||
|
|
||||||
|
*Note: this widget styles Elementor Pro's Image Carousel widget elsewhere on the page — it doesn't render a carousel of its own.*
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Keyword Linker
|
||||||
|
|
||||||
|
Turn chosen keywords into links automatically, across every post and page — without editing content by hand.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Internal linking (and the occasional important external link) is one of those SEO and UX basics that's simple in theory but tedious in practice: every time you mention a term you want linked, you have to remember to add the link manually, in every post, every time.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Define a keyword once, tell it where to link, and Keyword Linker automatically turns every matching mention of that word across your site's content into a link — with control over how many times per page it should link, whether to bold the result, and whether the link opens in a new tab or carries a "nofollow" attribute.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Consistent internal (or external) linking across your whole site, maintained from one central list instead of hunting through old posts by hand.
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Markdown Widget
|
||||||
|
|
||||||
|
Embed a live Markdown file directly into your page — always showing the current version, with no copy-pasting.
|
||||||
|
|
||||||
|
## 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.
|
||||||
|
|
||||||
|
## 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.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A documentation or changelog page on your WordPress site that's always current, sourced directly from wherever the Markdown file actually lives.
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
# Screenshot Capture
|
||||||
|
|
||||||
|
A live, always-current screenshot of any website — dropped onto your page like a normal image, with full styling control.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Showcasing another website — a client's project, a partner site, a "before" example — usually means manually taking a screenshot, uploading it, and remembering to update it whenever the target page changes. It's tedious, and the image goes stale the moment the source page is updated.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Screenshot Capture fetches a real screenshot of any URL you give it, on desktop, tablet, or phone dimensions, full-page or single-viewport, and displays it exactly like an image widget — with the same transform, hover, box-shadow, and filter controls you'd expect from a premium Elementor widget. Screenshots are cached automatically, so your page stays fast, and a one-click refresh in the editor lets you pull a fresh capture whenever you need one.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A portfolio, case study, or partner showcase page that always shows a real, current view of the site it's linking to — without a manual screenshot workflow.
|
||||||
|
|
||||||
|
*Free version screenshots include a small watermark. [Dotjuice Elementor Tools Pro](../../../../dotjuice-elementor-tools-pro/documentation/marketing/overview.md) removes it.*
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
# Woo Add to Cart Transform
|
||||||
|
|
||||||
|
Turn WooCommerce's plain variation dropdowns into clickable buttons — the way a modern product page should look.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
WooCommerce's default variable-product selector is a set of `<select>` dropdowns — functional, but visually dated compared to the button and swatch-based selectors shoppers expect from modern ecommerce sites.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo Add to Cart Transform converts those native dropdowns into a clean row of clickable buttons, fully restyled through Elementor controls — normal, hover, and selected states, spacing, borders, and typography all included. It also cleans up a few default WooCommerce quirks along the way: a clearer "reset selection" link, and per-variation pricing that always shows so shoppers always know exactly what they're about to pay.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A product options selector that looks and feels current, without touching a line of custom CSS or template code.
|
||||||
|
|
||||||
|
*Colour swatches for attributes like colour options are a [Pro](../../../../dotjuice-elementor-tools-pro/documentation/marketing/overview.md) feature — the free version gives you styled buttons.*
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Woo Categories Transform
|
||||||
|
|
||||||
|
Turn WooCommerce's plain category tiles into a genuinely styleable grid.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
When WooCommerce displays product subcategories — on your shop page, or wherever you list categories — the default markup offers very little styling control: a basic image and a title, with no easy way to add hover effects, overlays, or a polished card layout.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo Categories Transform restructures the category tile markup and gives you full control over it: box styling with borders and shadows, image hover transforms and filters, and a positioned content overlay for the category title — including a subtle blur effect behind the text if you want it.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Category tiles that look like a designed product grid, not a default WooCommerce archive.
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Woo My Account Transform
|
||||||
|
|
||||||
|
Give WooCommerce's My Account area the same design polish as the rest of your store.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
The My Account page — order history, downloads, account forms — is one of the most-visited parts of any WooCommerce store, but it's usually the most visually neglected, since it's built from WooCommerce's own default markup rather than your page builder.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo My Account Transform applies consistent, on-brand button and link styling across the entire My Account area — buttons on forms, order actions, and download links all pick up the same styled look, in normal and hover states.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
An account area that finally looks like it belongs to the rest of your site, not a leftover default template.
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Woo Page Numbers
|
||||||
|
|
||||||
|
Fully styleable pagination for your shop and product archive pages.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
WooCommerce's default "Previous / 1 2 3 / Next" pagination is functional but plain, and offers very little native styling control — especially for showing which page a shopper is currently on.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo Page Numbers wraps WooCommerce's pagination with dedicated styling controls: colours, borders, and spacing for the normal state, the hover state, and — separately — the currently active page, so it's always visually obvious where a shopper is in your catalogue.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Pagination that matches the rest of your store's design, without writing custom CSS to override WooCommerce's defaults.
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Woo Taxonomy List
|
||||||
|
|
||||||
|
A flexible, fully-styled term list for any taxonomy — categories, tags, product categories, or any custom taxonomy your site uses.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Building a "Shop by Category" footer block, a category sidebar, or a sitemap-style navigation list usually means either a rigid built-in widget with few styling options, or custom template code.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Woo Taxonomy List displays terms from any taxonomy on your site — flat (every term as one list) or hierarchical (chosen parent categories with their children nested beneath), with an optional clickable heading, term counts, custom icons, and deep styling control over every part of the list: parent items, child links, spacing, markers, and hover states.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A polished, on-brand category or taxonomy navigation block, built entirely through Elementor controls.
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# WooCommerce Account Settings
|
||||||
|
|
||||||
|
The everyday WooCommerce account-page tweaks every store eventually needs — without a custom code snippet.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Every WooCommerce store eventually wants a small adjustment to the default account experience: hiding a tab nobody uses, sending customers straight to their orders instead of a generic dashboard, or keeping certain product categories out of the main shop listing. None of these are hard to do with custom code, but they shouldn't require it either.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
WooCommerce Hacks gives you toggle switches for the account-page adjustments stores ask for most often — hiding the Dashboard or Downloads tabs, redirecting straight to order history, a cleaner post-logout destination — plus a category picker for excluding specific product categories from your main shop page.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
The small account-experience refinements that make a store feel deliberately built, available as simple toggles instead of custom development work.
|
||||||
15
marketing/dotjuice-pagespeed/documentation/marketing/advanced.md
Executable file
15
marketing/dotjuice-pagespeed/documentation/marketing/advanced.md
Executable file
@@ -0,0 +1,15 @@
|
|||||||
|
# Advanced
|
||||||
|
|
||||||
|
Server-side tuning for sites that want to squeeze out every remaining bit of overhead.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Beyond what shows up in a page's HTML, WordPress runs background processes that cost server resources regardless of whether a specific site actually benefits from them — a dashboard polling mechanism firing every fifteen seconds, a legacy remote-publishing protocol most sites never use, and WooCommerce's own scripts loading in full even on pages that have nothing to do with shopping.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dotjuice Pagespeed lets you throttle or disable WordPress's Heartbeat API (the background polling that powers autosave and "someone else is editing this" notices), disable XML-RPC if you don't use remote publishing tools, and stop WooCommerce's cart and shop scripts from loading on pages that aren't part of your shop.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Less background server load, and WooCommerce's overhead confined to the pages that actually need it.
|
||||||
19
marketing/dotjuice-pagespeed/documentation/marketing/caching.md
Executable file
19
marketing/dotjuice-pagespeed/documentation/marketing/caching.md
Executable file
@@ -0,0 +1,19 @@
|
|||||||
|
# Full-Page Caching
|
||||||
|
|
||||||
|
The single biggest lever for WordPress speed, and the first thing any performance audit will tell you to fix.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Every WordPress page load runs the same expensive process from scratch: connect to the database, run dozens of queries to assemble the content, execute PHP for your theme and every active plugin, then finally send HTML to the browser. For a typical visitor, that's the difference between a server response in a few milliseconds and one that takes the better part of a second — before a single image or stylesheet has even started downloading.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dotjuice Pagespeed builds a static snapshot of each page the first time it's requested, then serves that snapshot directly to every visitor after — bypassing WordPress, your database, and PHP entirely. It's the difference between a librarian re-writing a book from memory every time someone asks for it, versus just handing over a printed copy.
|
||||||
|
|
||||||
|
Mobile and desktop visitors get their own separate cached versions automatically, so responsive layouts and mobile-specific content are never mixed up.
|
||||||
|
|
||||||
|
Cached pages don't go stale, either — the moment you publish or update a post, its cached copy (and your homepage) are cleared instantly, and the plugin can even pre-warm the new cache in the background so your first visitor doesn't pay the "empty cache" cost.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Server response times measured in single-digit milliseconds instead of hundreds — the foundation every other optimisation in this plugin builds on top of.
|
||||||
17
marketing/dotjuice-pagespeed/documentation/marketing/cdn.md
Executable file
17
marketing/dotjuice-pagespeed/documentation/marketing/cdn.md
Executable file
@@ -0,0 +1,17 @@
|
|||||||
|
# CDN Integration
|
||||||
|
|
||||||
|
Serve your optimised stylesheets and scripts from a CDN hostname, with a single URL change.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
If you already use a content delivery network to serve assets closer to your visitors geographically, your CSS and JavaScript still need to point at that CDN's hostname rather than your own server for the benefit to apply.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dotjuice Pagespeed rewrites the URLs of your stylesheets and scripts to point at your CDN hostname automatically, once you tell it what that hostname is — no manual find-and-replace across your theme or plugins required.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Your optimised CSS and JS served from your CDN with one setting, instead of a manual hunt through every place a stylesheet or script URL is generated.
|
||||||
|
|
||||||
|
*Note: this rewrites stylesheet and script URLs specifically. If you're looking to move your entire media library — images, uploaded documents, and so on — onto a CDN, that typically requires a dedicated media-CDN plugin or your CDN provider's own WordPress integration alongside this feature.*
|
||||||
17
marketing/dotjuice-pagespeed/documentation/marketing/css-optimisation.md
Executable file
17
marketing/dotjuice-pagespeed/documentation/marketing/css-optimisation.md
Executable file
@@ -0,0 +1,17 @@
|
|||||||
|
# CSS Optimisation
|
||||||
|
|
||||||
|
Fewer, smaller, smarter stylesheet requests — one of the fastest ways to improve how quickly a page visibly appears.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
A typical WordPress page loads CSS from half a dozen sources or more: your theme, Elementor, WooCommerce, and every plugin with its own styling. Each one is a separate request the browser must complete before it can safely paint the page — and by default, the browser won't show anything until every one of them has loaded. That's render-blocking, and it's a direct hit to your First Contentful Paint and Largest Contentful Paint scores.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dotjuice Pagespeed combines your local stylesheets into a single optimised file and strips out everything that isn't needed to render the page — comments, unnecessary whitespace — without touching the actual styling. Fonts and CDN resources you don't control are left exactly as they are.
|
||||||
|
|
||||||
|
For sites that want to go further, asynchronous CSS loading removes even that single combined stylesheet from the critical rendering path entirely: the browser paints the page using a small snippet of essential "critical" styling you provide, while the full stylesheet loads quietly in the background and takes over once ready.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Fewer HTTP requests, a smaller total payload, and — when paired with critical CSS — a page that visibly renders before its full stylesheet has even finished downloading.
|
||||||
15
marketing/dotjuice-pagespeed/documentation/marketing/database.md
Executable file
15
marketing/dotjuice-pagespeed/documentation/marketing/database.md
Executable file
@@ -0,0 +1,15 @@
|
|||||||
|
# Database Cleanup
|
||||||
|
|
||||||
|
Every WordPress site quietly accumulates clutter. This clears it out.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Post revisions pile up every time you save a draft. Abandoned auto-drafts never get deleted. Spam comments sit in your database waiting to be emptied. Plugins leave behind transient cache entries and orphaned metadata long after they're no longer needed. None of this is dramatic on its own, but on a site that's been running for a few years, it adds up to a noticeably larger, slower-to-query database — and a heavier backup every single time.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dotjuice Pagespeed gives you one-click cleanup for the most common sources of database bloat — revisions, drafts, spam, expired cache entries, and orphaned data — with a live view of how much each category is currently holding. Prefer to set it and forget it? Turn on scheduled cleanup and choose how often it runs automatically.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A leaner, faster-to-query database and a smaller backup — housekeeping that used to mean a manual phpMyAdmin session, now a single click.
|
||||||
15
marketing/dotjuice-pagespeed/documentation/marketing/html-optimisation.md
Executable file
15
marketing/dotjuice-pagespeed/documentation/marketing/html-optimisation.md
Executable file
@@ -0,0 +1,15 @@
|
|||||||
|
# HTML Optimisation
|
||||||
|
|
||||||
|
Trim the document itself, and stop paying for features WordPress loads by default that most sites never use.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
WordPress ships with a handful of scripts and behaviours switched on for every site regardless of whether it needs them — emoji support for older browsers, embed discovery scripts, and more. Combined with unminified HTML output, that's requests and bytes spent on nothing your visitors actually benefit from.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dotjuice Pagespeed minifies your final HTML output, strips WordPress's legacy emoji-detection script that modern browsers don't need, and gives you the option to disable oEmbed discovery entirely. On top of that, it automatically appends `font-display: swap` to your Google Fonts so visitors see readable text immediately in a fallback font rather than invisible text while the web font downloads — and it can add DNS prefetch hints for any third-party domain you rely on, shaving connection setup time off those requests.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A smaller HTML document, fewer unnecessary background requests, and text that's always visible to your visitors, never hidden waiting on a font file.
|
||||||
17
marketing/dotjuice-pagespeed/documentation/marketing/images.md
Executable file
17
marketing/dotjuice-pagespeed/documentation/marketing/images.md
Executable file
@@ -0,0 +1,17 @@
|
|||||||
|
# Image Loading
|
||||||
|
|
||||||
|
Load what's visible first, and make sure the one image that matters most for your score is never held back.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Images are usually the heaviest part of any web page, and by default every one of them competes for bandwidth the moment the page starts loading — including the ones several screens below the fold that a visitor may never even scroll to. At the same time, Google's Largest Contentful Paint metric usually points straight at your biggest above-the-fold image, so if that specific image gets deprioritised by generic optimisation, your score suffers even though "everything is optimised."
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dotjuice Pagespeed applies native lazy loading to every image and iframe below the fold, so browsers only spend bandwidth on them as a visitor scrolls close — without any JavaScript library, and without the blank-placeholder flash some older lazy-load techniques cause.
|
||||||
|
|
||||||
|
At the same time, it recognises your designated hero image and does the opposite: forces it to load with maximum priority and never lazily, so the exact element Google measures for Largest Contentful Paint is always fetched as fast as possible.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Bandwidth spent where it counts, on what's actually visible — and your single most important image, prioritised rather than accidentally deferred.
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
# JavaScript Optimisation
|
||||||
|
|
||||||
|
Keep the browser's main thread free for what visitors actually came to see, instead of tying it up running scripts they don't need yet.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
JavaScript is expensive in a way CSS isn't: the browser has to download it, parse it, and often execute it before it can continue rendering the page — and a lot of what loads on a typical WordPress page (analytics trackers, chat widgets, marketing pixels) has nothing to do with what a visitor sees in the first few seconds.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dotjuice Pagespeed combines and minifies your local scripts to cut down on requests, then goes further with two complementary techniques: deferring scripts so they run after the page has rendered rather than blocking it, and — for scripts that genuinely don't need to run until a visitor interacts with the page at all — delaying them until the first scroll, click, or tap.
|
||||||
|
|
||||||
|
Every exclusion is handled automatically. jQuery, Elementor's own scripts, checkout and payment processors, and any script carrying page-specific data are detected and left untouched, so the aggressive optimisations apply only where they're safe.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A page that's interactive sooner, because the browser isn't stuck executing a marketing pixel's JavaScript before it can respond to a click.
|
||||||
29
marketing/dotjuice-pagespeed/documentation/marketing/overview.md
Executable file
29
marketing/dotjuice-pagespeed/documentation/marketing/overview.md
Executable file
@@ -0,0 +1,29 @@
|
|||||||
|
# Dotjuice Pagespeed
|
||||||
|
|
||||||
|
A free, professional-grade performance plugin for WordPress. Full-page caching, CSS/JS optimisation, image lazy loading, database cleanup, and Core Web Vitals improvements — all from one dashboard, no configuration expertise required.
|
||||||
|
|
||||||
|
## Why WordPress sites are slow by default
|
||||||
|
|
||||||
|
Every time an anonymous visitor loads a WordPress page, the server rebuilds it from scratch: dozens of database queries, PHP execution for the theme and every active plugin, then the HTML is assembled and sent. Do that for every visitor, every time, and even a well-built site struggles to load in under a second — which matters, because page speed affects both how visitors experience your site and how Google ranks it.
|
||||||
|
|
||||||
|
Dotjuice Pagespeed attacks this from every angle a real optimisation audit would cover:
|
||||||
|
|
||||||
|
## What's included
|
||||||
|
|
||||||
|
**Full-page caching** — the biggest single win. Once a page is built, it's saved as a static file and served directly, skipping WordPress, the database, and PHP entirely on repeat visits. This is what takes a server response time from around a second down to a few milliseconds.
|
||||||
|
|
||||||
|
**CSS & JavaScript optimisation** — combines and minifies your stylesheets and scripts, removes render-blocking CSS from the critical path, and defers or delays JavaScript that doesn't need to run immediately — all without breaking Elementor, WooCommerce, or the other plugins your site depends on.
|
||||||
|
|
||||||
|
**Smart image loading** — modern native lazy loading for everything below the fold, paired with automatic priority loading for your hero image so the Largest Contentful Paint metric that Google measures isn't accidentally delayed.
|
||||||
|
|
||||||
|
**HTML & resource hints** — HTML minification, removal of WordPress's default emoji and embed scripts nobody asked for, DNS prefetching, and preconnect hints that shave milliseconds off every third-party request.
|
||||||
|
|
||||||
|
**Preloading** — automatic cache warming the moment you publish, so your first real visitor never pays the "cold cache" tax, plus a one-click sitemap preload for warming your entire site at once.
|
||||||
|
|
||||||
|
**Database housekeeping** — clears out the post revisions, spam comments, and expired transients that quietly bloat every WordPress database over time, with both one-click cleanup and a scheduled autopilot mode.
|
||||||
|
|
||||||
|
**Built for real WordPress sites** — every optimisation is written to work alongside Elementor, WooCommerce, and the plugin ecosystem, not against it. Scripts with dependencies, localized data, or webpack bundles are automatically detected and left untouched rather than broken.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
A faster time-to-first-byte, fewer render-blocking requests, better Core Web Vitals scores, and a leaner database — delivered through sensible defaults that work out of the box, with room to fine-tune every setting as you learn what your site needs.
|
||||||
19
marketing/dotjuice-pagespeed/documentation/marketing/preload.md
Executable file
19
marketing/dotjuice-pagespeed/documentation/marketing/preload.md
Executable file
@@ -0,0 +1,19 @@
|
|||||||
|
# Preloading
|
||||||
|
|
||||||
|
Stop waiting for the browser to discover what it needs — tell it in advance.
|
||||||
|
|
||||||
|
## The problem it solves
|
||||||
|
|
||||||
|
Browsers work through a page's resources largely as they discover them, request by request. That discovery process itself takes time, and for the resources that matter most to how fast a page *feels* — your hero image, your web fonts, the third-party services your theme relies on — that delay is pure waste.
|
||||||
|
|
||||||
|
There's a second, quieter problem too: the very first visitor to a freshly published page pays the full "build this page from scratch" cost, because nothing has been cached yet.
|
||||||
|
|
||||||
|
## How it helps
|
||||||
|
|
||||||
|
Dotjuice Pagespeed tells the browser exactly what to prioritise: your designated hero image loads with maximum urgency, key web fonts are preloaded before they're needed, and connections to services you actually use (analytics, fonts, embeds) are opened in advance rather than discovered mid-page.
|
||||||
|
|
||||||
|
On the server side, the moment you hit publish, the plugin quietly visits the new page itself in the background — so by the time a real visitor arrives, the cache is already warm. And with one click, you can do the same for your entire site at once.
|
||||||
|
|
||||||
|
## The result
|
||||||
|
|
||||||
|
Your most important image and fonts, prioritised instead of left to chance — and a cache that's always warm before a real visitor needs it.
|
||||||
Reference in New Issue
Block a user