A proven way to do a common store job on one platform.
Every builder and platform has its own habits. A Pathway writes them down, so the change is made the way that platform expects.
- Written by hand. Our developers write each Pathway and ship it in a release. None of it is generated on the fly.
- Loaded for you. It loads on its own for the sites it applies to. You do not pick it or set anything up.
- Your site's own list. Each site has its own Pathway list. A site owner, or we, can add a guide or switch one off.
Hale Ceramics · Online shop
Webgentic for ecommerce · WooCommerce
Put a weekend sale banner on the homepage and add Sale to the menu.
PLAN
- Read the guide that applies to this store.
- Add the banner to the homepage and build the sale page.
- Add Sale to the menu and save a note for each change.
Saved with a plain-English note
Restore any earlier version in one click
The store jobs a request starts from.
These are the jobs stores ask for most. Webgentic for ecommerce plans each one for your platform.
Sales and promotions
A sale banner, a sale page and a Sale link in the menu, put up the same morning.
Launch landing pages
A page for a new range or a launch, written, published and linked from the menu.
Category text
Category descriptions rewritten so shoppers and search engines can tell what is in each one.
Search terms
The terms people already search for are read from Search Console and the page is rewritten around them.
Products, prices and stock are not built yet. Those jobs go through Store care or the Orchestrator.
Pathways by platform.
This is every Pathway that exists today. We list a new one only when it is finished.
| Pathway | Platform | What it covers | When it loads |
|---|---|---|---|
| Divi 4 | WordPress page builder | For sites built on the Divi 4 builder. The page content is pulled out as text, changed, and saved back with a revision kept. | Loads for sites running Divi 4. |
| Divi 5 | WordPress page builder | For sites built on Divi 5, which stores pages as blocks instead of the Divi 4 shortcodes. It covers the new format, moving older content across and the usual traps. | Loads for sites running Divi 5. |
| Magento Page Builder | Magento | For Magento sites that build CMS pages and blocks with Page Builder. | Loads on its own for the sites it applies to. |
No Pathway yet for Elementor, Beaver Builder, Visual Composer, Oxygen or Drupal.
Webgentic for ecommerce still works on those sites. WordPress builders other than Divi are treated as ordinary WordPress sites, and Drupal sites are files only. They just have no builder-specific guide.
How a Pathway shows up when you ask.
You never ask for a Pathway. You ask for the job, and the guide is already there.
You ask in plain words
Type what you want changed in the panel on your store, as you would to a colleague.
The guide loads
If the site is on a platform with a Pathway, Webgentic for ecommerce reads it before it plans. The Divi guides load for their own version only.
The change follows the guide
You see the plan, then watch the change appear on the page. Every change is saved with a plain-English note you can restore.
New Pathways arrive in releases.
When a Pathway ships, it goes in the changelog with the release. We add it to this page at the same time.
Questions about Pathways
Do I have to choose or install a Pathway?
No. A Pathway loads on its own for the sites it applies to. A site owner, or we, can add one or switch one off.
Who writes the Pathways?
Our developers, by hand. They ship in releases and appear in the changelog.
Is there a Pathway for Elementor?
Not yet. Webgentic for ecommerce works on an Elementor site as an ordinary WordPress site, without a builder-specific guide.
Is there a Pathway for Drupal?
No. Drupal sites are handled as files only, and there is no platform guide for them.
Something else on your mind?
Ask us directly and a developer will reply.
Ask a question
Ask for the job. The guide is already there.
Join the waiting list and we will be in touch when your place comes up.
