Working with Divi 5

On a Divi 5 site, PressConduit covers most of what you'd otherwise click through by hand. This page lists it in plain terms so you know what to ask for.

Pages and modules

• Change one module at a time. Text, colors, spacing, links, whatever you'd edit in the builder. It doesn't have to rewrite the whole page to fix one button.
• Add, move, copy and delete modules, and swap one module for another.
• Turn a section into a loop that repeats for each post, product or category, and show live content like the post title or a custom field.
• Show or hide a module by rule (logged in, on mobile, a certain date), and set up click, hover and scroll effects.
• Save and reuse styles (presets) and Divi Library items.

Whole-site settings

• Theme Options, the Customizer (all of it: fonts, colors, header, menus, footer, buttons, mobile), and the builder performance settings.
• Global colors, design variables, breakpoints, custom CSS and custom fonts.
• Who can do what in Divi (the Role Editor), and the code Divi adds to every page.
• Per-page settings like page CSS, spacing and hiding the menu.
• Canvases (slide-in menus and pop-ups) and Theme Builder templates.

Moving things between sites

• Export a page, a Divi Library pack, a whole Theme Builder setup, or a site's Divi settings, and load them on another site.
• Imports add new things. They don't overwrite what's there. If something can't move (like a rule tied to one specific page), it tells you instead of guessing.

Phones and tablets

• Ask it to check a page for mobile problems: columns that never stack, headings and padding that stay desktop-sized, fixed widths wider than a phone, rows that can't wrap, and menus that turn into a jumble.
• Ask it to fix them. It only adds tablet and phone settings. Your desktop design isn't touched, and settings you already made for phones are left alone.
• It can build a phone menu: a "Menu" button that opens a slide-in panel with your links, while your normal menu stays as it is on desktop.
• The check reads the page's settings, so it can't see the finished page. Ask it to look at the page at phone width as well.

Building a page from a screenshot

• Paste a screenshot or mockup into the chat and ask for the page. It writes down each section, sets up your colors and fonts, builds with real Divi modules, checks phone width, and compares the result to your image.
• It builds the page in seconds from a short description of the layout: sections, columns, headings, text, buttons, card grids, and labeled stand-ins for photos. The columns already stack on phones. Things like background images, icons, forms and live data are added afterwards.
• Photos and logos can't be pulled out of a picture. It uses clearly labeled stand-ins and lists them, or you can hand it the originals.
• If the original site is live, tell it the address. It can read the real text instead of guessing from the picture.

What it leaves to you

• API keys and account passwords. Those never travel in an export.
• Creating a split test. Divi 5 has no screen for that, so the assistant can only read results from tests set up earlier.
• Anything you'd rather see first. Ask it to show you a setting before it changes it.

Staying safe

Every change is saved first, so you can undo it. Read Undo and the activity log. For anything big, like importing a whole Theme Builder or a settings file, try it on a staging site first.

Divi 4 sites keep their existing tools. The tools above only appear on Divi 5.