Changelog

Fixed: text that could come out invisible, in four more places. Each one was text that carried no colour of its own, so it fell back to your site's normal dark text and landed on something dark. Gallery titles and captions on a dark band came out at 1.00:1 - the same colour as what they sat on. A timeline date came out barely readable on the two styles that paint their card dark. The heading on a highlighted pricing tier came out dark on your brand colour. And a contact form on a dark band left its Send button unreadable - that one was there long before any of the ready-made styles, on the plain form anyone gets by default. All four now take a colour paired to whatever they actually stand on, from your own palette, so they still follow a re-brand. Two of these corrections are in the styles themselves rather than in the plugin's code, so re-install the styles to pick them up (Design System, or Preset catalog > Update presets - neither touches your colours or fonts).

New: ready-made styles now reach fifteen kinds of module, up from four. Tabs, timelines, galleries, contact forms, team members, image blocks, accordions, sign-up forms and more can each be given a named style - "card", "inverse", "bordered", "elevated", "showcase" and so on - and the page points at that style rather than copying it, so changing the style later updates every page using it. Tabs are worth a special mention: the tab buttons themselves could never be given a readable colour before, because they sit on a strip Divi paints a fixed grey. The tab styles paint that strip and colour the labels together, which is the only safe way to do it.

New: Claude can now discover those styles. They shipped in 2.0.1 but nothing told Claude they existed, so it could only reach one by accident. It is now given the full list, along with when a style will be refused - a style is left off, with the reason reported, rather than applied where it would be unreadable.

Fixed: the highlighted pricing tier's heading was hard to read. On the default pricing style, Divi paints the highlighted tier's heading in your brand colour and the text on it stayed dark - 2.68:1, well under what people with reduced vision need. That heading now uses the same light panel the other pricing styles already use, so the heading and the "best value" line both read clearly. If you prefer the brand-coloured heading, the "bold", "accent" and "cards" styles keep it and pair the text to it.

Fixed: the connection test could report a connection that had never happened. The test sends a real request to your own connector address to prove it answers - and that request was being counted as "Claude reached this site", which is what the dashboard reads to decide whether you are connected. So on a site Claude had never touched, pressing the test button was enough to make it claim otherwise. The test still runs and still tells you whether the address answers; it no longer leaves a footprint. This matters because "Claude has never reached this site" is the most useful thing we can tell you when a connection is failing, and it was being erased by the act of checking.

Fixed: the alternating timeline never alternated. Ask for a zig-zag timeline - the layout where entries sit left, right, left down the line - and you got a single column on the right instead. We were sending Divi the word "alternate" where it expects "alternating", so it discarded the setting and fell back to its own default without saying anything. Both words are accepted now. Choosing the "alternating" ready-made style also sets that layout for you, since a style with that name and a single column of cards was telling you something untrue.

Fixed: text on a card inside a dark section could come out invisible. A timeline placed on a dark background rendered every heading and date in a pale colour on the light card Divi draws behind them - unreadable, and the same shade top to bottom. The cause is worth stating plainly: when a module carries no background of its own, we were choosing its text colour from the band BEHIND it rather than from the card it actually sits on, so the check meant to stop unreadable text was producing it. Anything Divi draws its own panel for - timelines, testimonials, accordions, tabs, blog cards - is now coloured against that panel.

Fixed: the free version could not be downloaded, and would never have updated. The plugin was telling our own update service that the free version lives on WordPress.org. It does not - it has never been listed there - so anyone asking for the free version was handed a link to a page that does not exist, and free installs were checking a WordPress.org listing for updates that was never going to answer. Both now come from us. If you are on the free version, this is the release that lets you receive the next one.

Fixed: the set-up wizard could dead-end. On the "What to add" step, "Open the design system" left the wizard entirely and there was no way back to the step you were on. The design system now opens inside set-up, and a new step shows the ready-made styles you have just installed - previously set-up finished by telling you a number and never showing you what it bought you.

New: the pages we build for you now use your ready-made styles. Until now a generated page was styled one element at a time, so the styles you had installed sat unused on the pages that most needed them - and editing one changed nothing on them. A blog section now takes the card style that suits the band it sits on, and buttons and blurbs can be given a named style ("hero", "compact", "card", "elevated" and so on). Because the page points AT the style rather than copying it, changing that style later updates every page using it. Where a style would be unreadable in its position - a light-backed list on a dark band, say - it is left off and the reason is reported rather than applied and hoped for.

Fixed: spacing inside several ready-made styles never applied. The gap between blog cards, between gallery images, between icon-list rows and tab panels, and above and below dividers, was stored in a form the browser could not read - so it was skipped in silence and those blocks fell back to a default gap. Nothing errored and nothing looked obviously wrong, which is why it stood. If you have already installed the design system, re-install the styles to pick this up - the correction is in the styles themselves, not in the plugin's code.

Fixed (please read if you build pricing pages): a price could render invisible. On a pricing table the price is the one number that must be legible, and on any tier that is not the highlighted one it was coming out white on white - measured at 1.00:1. Nothing errored: the module simply set no colour for it, and Divi paints text with no colour of its own in whatever it inherits. Every module the design system knows about now leaves with a readable colour on any text it carries, chosen from your own palette so it still follows a re-brand.

New: the Design System screen now tells you when a brand colour has stopped following your site colours. Your brand colours normally follow the colours set on your site, so changing one there updates every shade, every ready-made style and every page built from it. If that link is ever broken - a colour replaced with a fixed value - the same name quietly means two different things, and pages come out in a colour your palette says you are not using. Nothing reported that before; it does now.

New: the Design System screen now tells you when your presets point at something that is not installed. A design system can be installed incompletely - colours and sizes written, fonts skipped - and every preset that used those fonts then points at nothing. Divi renders a missing value as nothing at all, so this was invisible: the styles looked untouched rather than broken, and in the builder the font simply could not be picked. Measured on a real site: 282 preset settings pointing at three fonts that were not there. You are now told, and can connect them to fonts you already have without changing anything else.

Fixed: "Build pages from my preset library" showed as off while it was on. The switch and the feature disagreed, so the screen said one thing and your pages did another - and saving any setting from that screen would then have turned it off for real.

Fixed: saving from inside the set-up wizard threw you out of the wizard and left you on the Settings page with no way back to the step you were on.

Fixed: a button's label could be unreadable on its own fill. The label used the ink paired with your primary colour, while the button filled with Divi's own primary - two colours a site can let drift apart. Measured at 4.12:1 where 4.5 is the minimum. The label is now graded against the fill it actually renders on, and a colour you set yourself is still left alone.

Fixed: a deleted colour or font still counted as installed. Divi does not remove a value you delete - it archives it, and the record stays. Anything that reads the raw list therefore saw a deleted value as present, while everything pointing at it rendered as nothing. Deleted values are now treated as gone, which is what they are.

Fixed: hero headings ignored your type scale. The largest text on a page was written in as a fixed size while everything around it stayed linked to your scale - so changing the scale reflowed the whole page except its biggest element. Hero headings now use the scale like everything else, and still fall back to a considered fluid size on a site that has not installed one.

Fixed: the duplicate-values panel looked broken. "Keep" and "Remove" were labels styled to look like buttons, so clicking them did nothing, and the buttons that do the work were below a list that can run to fifty entries. They are now plainly labels, the controls are at the top, and two entries that share a name show their id so you can tell which is which.

New (this is the headline): pages the AI builds now reference your presets, so editing a preset in the Visual Builder restyles every page that used it — the way the rest of your design system already works. Previously a generated page carried its own copy of the styling and could not be re-themed. This is on by default for Pro from this version; if you would rather newly built pages keep the styling they were built with, there is a switch for it in Settings. Pages you have already built are never touched.

New (the other headline): the whole admin is new. Home tells you the state of your site and what you can do about it; the Design System screen shows every colour, font and size the system holds, with the ones you can edit made editable; the Colour checker grades every pair your site can put together and offers a fix; the Preset catalog lists all 490 styles with what each is for. There is a set-up wizard that looks at your site first and changes nothing without asking.

New: 278 pre-styled modules across 105 module kinds — cards, icon lists, tabs, toggles, timelines, team grids, galleries, pricing tables, counters, dividers and more. Ask for a pricing table and it arrives looking composed, in your colours and type, rather than as Divi's defaults for you to style by hand.

New: re-link the pages you built on the free plan. On the free plan the AI writes size values into the page as fixed numbers, because linking them to your variables is a Pro feature. On upgrading, that left every page you had already built frozen. Divi Connect can now find those values and reconnect them to the variables they came from — previewed first, and every page is snapshotted before anything changes.

New: set your own brand colours. Six slots — primary, secondary, accent, background, surface and text. Fill an empty one and everything that hangs off it is worked out and written alongside: the lighter and darker steps, the hover state, and a text colour that is legible on it.

New: restore colours that were deleted. Removing a colour in Divi's own Variables panel leaves everything that used it pointing at nothing, and no reinstall brings it back. Divi Connect can now work it out again from your own brand colours — not copied from one of ours — and puts it back at the value it had.

New: fonts are editable, with a picker that draws each family in its own typeface rather than listing 1,950 names in the interface font.

New: import an image from a URL, and read or change site settings — the three things a beta tester could not finish a real site without.

New: one button that describes your site for a support email. Troubleshoot now has a Copy diagnostics button: your Divi and WordPress versions, whether Claude has ever reached the site, what your design system holds, your other plugins, and the last ten changes made here and by whom. It also says whether your plugin files all came from the same install, which is the difference between a real fault and a half-finished update. It contains no passwords and not your connector key — only a short fingerprint of the key, enough to tell whether the one in your connector is the one on your site.

Fixed (accessibility, please read): the uppercase label presets never actually uppercased anything. "DL Kicker" and "DL Eyebrow", in all their variants, set uppercase in a place Divi reads only for italic and underline. Everything else about them worked — the mono typeface, the letter-spacing, the colour — which is why it went unnoticed. Six presets, corrected.

Fixed: a percentage on a bar counter could be unreadable. Divi draws the number twice, and the copy you can see straddles the filled part of the bar and the track behind it, so no single colour could clear both. Measured at 1.01:1. The bar and its track now share a colour the number is legible on.

Fixed: a person's role could be unreadable on the feature card. It was set in the accent colour on a dark card — 2.23:1, and worse on some flavours. It now uses a lighter step of the same accent, which keeps the look and clears the contrast requirement on all five flavours.

Fixed (please read if you use the flavour builder): a look installed from "Build a flavour" was frozen. The colours were right, but they were written in as fixed values instead of as references to your brand, so changing a brand colour afterwards moved nothing. Every derived colour now installs as a reference, exactly as the five bundled looks do.

Fixed (safety): Undo could report success and restore nothing. It only ever happened with "Confirm before overwriting a page" switched on — that is, on the sites most careful about their content. Undo now reads the page back after writing and compares it, rather than trusting its own reply.

Fixed (safety): reverting your design system could do the same. The twin of the fault above, in the part that puts back colours, fonts, sizes and presets rather than page content — and it reported the numbers it had *meant* to restore, so a failure arrived looking like a success with the right figures beside it. A revert now reads all four stores back afterwards and names exactly what did not come home. Separately, if a change ever goes ahead without a restore point being saved, the Design System screen now tells you at the time, rather than leaving you to discover it when you try to undo.

Improved: pages built on the free plan now use fluid sizes. Type and spacing are written in as clamp() values that scale with the screen, rather than as fixed pixel numbers. The free plan still writes the values into the page instead of linking them to your size variables — that link is what the Professional plan adds, and what lets a later change to your scale reflow every page — but what gets written is now the same considered scale, so a free page reads properly on a phone and on a wide monitor without anyone adjusting anything.

Improved: the plan comparison in the plugin was wrong about itself. The sidebar told free users that managing the design system was a Professional feature. It is not: installing a look's colours and fonts, setting your six brand colours, changing the site-wide fonts and re-deriving colours from your brand are all free. What the Professional plan adds is the preset catalog, the fluid size scale, and letting Claude write to the design system directly. Corrected in the sidebar and in what the plugin tells Claude about its own plans.

Changed: Divi 5.7 is now the stated minimum. The documentation already said 5.7 while the plugin itself accepted 5.0, so a site in between was told it qualified by one and not the other. One number now, and it is the one that was advertised.

Fixed: the message shown when re-linking older pages is a Professional feature used a different error code from every other plan message, which could make it read as a permissions problem rather than an upgrade prompt.

Improved: a large unused copy of your presets is cleared out, once. Divi keeps its presets in a record of their own, but a second, stale copy had been sitting in the theme options beside it — on one site 904 KB of the 930 KB that record held, and nothing ever read a byte of it. Every colour and font change was rewriting the lot. It is removed the next time you open wp-admin, and only when your real preset store is present and healthy. Nothing you can see changes.

Fixed: the readability checker could suggest the colour you already had. On some backgrounds the suggestion it offered was the current colour, so the button appeared to do nothing — and the "after" preview claimed a pass while showing the same ratio as the failure. The suggestion is now measured before it is offered, and a pair that genuinely has no answer says so and names the colour to change instead.

Fixed (accessibility): two of the five looks had an accent too pale to use as a control. Electropop and Jungle read 1.80:1 and 1.69:1 against a light card, where WCAG asks for 3:1 for a button, rule or chip. Both accents were deepened along their own hue — the colour is recognisably the same — and now clear it.

Fixed: colours you deleted were still being counted. Divi archives a deleted colour rather than removing it, and Divi Connect was still reading the archived ones, so the totals on one screen disagreed with another and roles that no longer existed were reported as needing attention.

Fixed: invisible text on two dark presets. The testimonial card left the author, job title and company with no colour of their own, so they fell through to the site's text colour and rendered black on black; a closed accordion row did the same with its title.

Improved: the contrast guard now checks dark mode as well as light. Ten of the colour pairings have their worst case in dark, and until now they were only ever checked by hand.

Improved: an inverse pricing table is no longer offered, because it cannot be built — a plan column that is not the featured one always uses Divi's own light background, and there is no setting to change it. The variant it replaces is an accent-headed grid.

Improved (accessibility): every screen in the plugin is now graded, in both light and dark themes — text against its background, and controls against the surface they sit on, which is a separate requirement and was not being checked at all. Fifteen kinds of control got a visible edge as a result.

Improved: every one of the 490 presets now says what it is for, and nine that had been shipping without doing anything now do something.

Improved: more of the catalog is tonal — the card families, badges and labels gain the same four steps, so a set of cards can differ in weight without differing in colour.

Improved: image ratios and column grids are built on Divi's own controls. The pack now ships no custom CSS at all, so what you get is editable in the Visual Builder like anything else.

Removed: two border widths that were too thin to see. "DL Border Width XS" never rendered thicker than 0.76px at any screen width, and "DL Border Width S" was under a pixel on phones and over one on desktop — so a border set with either was invisible, or appeared only on large screens. Neither can draw a line, so both have been retired along with the size variables behind them. Sites that already have them keep them; nothing you have built changes.

Security: hardened the URL check on image import against addresses that resolve to the host itself or to a cloud metadata service.

Security: reading a reference page now applies that same check. Asking Divi Connect to read a page's layout sends your server to fetch it, and WordPress's own validation does not cover the address range cloud hosts use to hand out credentials. Both routes now use one check, applied before the request is made.

Note for free users: nothing changes in how the AI builds your pages. Pre-styled modules arrive with the same look; their values are written into the page rather than linked, exactly as before.

Fixed (accessibility): the button on a call-to-action panel could be invisible as a shape. On the two brightest new flavours the button was painted near-white on a bright panel, so its label read perfectly but its edges did not exist — measured at 1.80:1 on Electropop and 1.69:1 on Jungle, against the 3:1 that accessibility guidance requires for a control's boundary. The button now reverses its panel instead, which is what the hand-built version of the same panel already did: every flavour, light and dark, now clears the requirement with room to spare (worst case 5.19:1).

Improved (visible, please read): pages come out a third shorter, with nothing removed. The design system was putting a card's padding around every module, including plain paragraphs and headings, which stacked on top of the padding the section and the column already had. A page that is mostly empty space reads as bland however good the individual pieces are: on the test page, 74% of the height was empty and it measured 9,584px, against 7,204px for the same content afterwards. Things that actually draw a box - columns, cards, panels, pricing tables, testimonials, forms - keep their padding, because there the padding is the inside of the box. Sites you already have are not re-themed: your presets change only when you next install a flavour.

Fixed (important): a comparison table with four options fell apart. The columns were given a width that added up to slightly more than the row, so every row wrapped, the last option dropped onto a line of its own and the columns stopped lining up - which is the entire point of a comparison table. It also happened with eight options, and with six, nine or ten the table was narrower than it should have been. Every option count now fits exactly.

Fixed (important): offering to "snap" a size to one of your design tokens could wreck the value. Only sizes written as a plain number could ever be matched, and almost every size in the design system is a fluid range, so out of 61 tokens exactly two were ever considered - a zero-width gap and a 999px pill. A 3px rule was therefore offered a 0px gap, and accepting would have flattened it to nothing. Fluid sizes are now matched properly, a border width is only matched against border tokens, and how close counts as close now scales with the size instead of being a flat 6px that called 3px "near" zero.

Fixed: an automatically added card could quietly break text contrast. Text is checked against the section's background, and then a card was painted behind it, so a pair that passed the check could render below the accessible minimum - measured at 5.26:1 before the card and 4.47:1 after. The card is now skipped, with a note, when it would do that.

Fixed: a divider's thickness was ignored when set by token name. "DL border-l" was dropped silently while "gvid-dl-border-l" worked, even though both are documented.

Fixed: setting a section's width by token name made it narrower than typing the same width as a number - about 1,098px instead of 1,373px, so text wrapped more and the page grew.

Fixed: the contact section always centred its copy, forcing a second centred band onto pages that already had one; and its form's button ignored your accent colour and shipped in Divi's stock blue. The copy beside a form now reads left, and the button takes your colour with its text checked for legibility against it.

Fixed (important, please read): editing one module could delete third-party modules from the page. If a page contained modules from another plugin - Divi Pixel, DiviFlash, Divi Supreme and the like - asking Claude to change a single module rewrote the page and dropped every one of them, reporting success. On a real test page 15 of them vanished and the page shrank from 8,759 bytes to about 2,000. Containers holding only a third-party module were also collapsed, which is why pasting the module back was not enough to repair the page. Third-party modules are now passed through untouched, keeping their position and nesting, on every editing tool and when appending a section to an existing page.

Fixed (important): changing one global colour deleted the others. Setting a single colour replaced your whole custom palette instead of updating that one entry, which took a site from 23 design-system colours down to 1 and left every preset that used them with nothing to point at. Colours you do not mention are now kept. Replacing the whole palette is still possible, but you have to ask for it.

New: changes to your design system can be undone. Setting colours, variables or presets directly now takes a snapshot first, so any of it can be reverted from History like a page edit. Previously only the bulk installs were snapshotted, and the everyday changes had no undo at all. A run of small edits leaves one restore point from before the run, and anything that deletes always leaves its own.

Fixed: a long editing session could throw away the checkpoint you needed. Page history keeps the last 20 changes, so a big pass over one page pushed out the state from before it began. The first checkpoint of each day is now kept and cannot be pushed out by later edits.

New: Claude can see third-party modules on a page. They were invisible to it, so it had no way to know they were there or to warn you. It now reports which ones a page contains, and that it cannot edit them.

New: five new design-system flavours - Meridian, Foundry, Monolith, Electropop and Jungle - replacing Editorial, Modern SaaS and Warm. The old three leaned on the same look every AI-built site uses; these do not, and each is contrast-checked in both light and dark. Meridian is the new default. Sites already using one of the old flavours keep their colours exactly as they are; nothing is re-themed by updating.

New: Design DNA has its own tab in the Design System, instead of sharing the Flavours tab with the canvas, the saved-flavour list and the revert list.

New: a Shop tab, marking where ready-made flavours and section packs will live.

Fixed: the flavour install warning claimed the per-page preview was "coming". It has been there since 1.8.1. The note now tells you how to use it, and what it can and cannot show you.

Fixed: twelve presets rendered as blank cards on the Preset Library page. A preset written in light ink - the "On Inverse" faces, the dark cards, the Success/Warning/Danger badges - was being demoed on a white card, so its text was invisible. Each now sits on the surface it was designed for.

Removed: the live preset previews in the Design System tab. Each preset was drawn as a small specimen, which meant painting a preset's own text colour onto the dashboard's own background - so the "On Inverse" styles, whose text is near-white by design, rendered invisible. The full inventory ("All presets on this site") stays where it was, and the generated Preset Library page remains the accurate way to see presets, because it renders them on real modules.

Improved: the Elevated card shape is calmer. Its shadow was a wide, diffuse cloud that made cards read as floating rather than lifted; it is now tighter and pulled back under the card.

New: pages Claude builds now follow your Design DNA. All seven settings — corner radius, spacing density, section rhythm, content width, button role, button shape and motion — now shape the pages Claude builds, not just the presets you apply by hand. Set your site to sharp and tight, or rounded and roomy, and the pages it builds change with it.

Improved (visible): generated pages look designed, not drafted. Feature, step, stat, team, benefit and value sections now come out as proper cards — with your corner radius, your border colour, your shadow and your spacing — instead of loose text floating on the page. Sections you compose yourself get the same treatment when you put two or more columns side by side.

Improved: generated pages use your brand's colours, not invented ones. Around thirty hardcoded colours have been replaced with your own roles, so an accent panel is your accent, a tinted callout is your surface, and a divider is your border colour — on any flavour, not just the one they happened to be picked for.

New: anchor links. Give a section an id and link to it with "#that-id", so a "Book a table" button in the hero can jump to the booking form.

New: Claude gets told when a section came out empty. If a wrong or missing content key would have published a blank band, the build now says so — naming the key it expected and the one you probably meant — instead of silently publishing nothing.

New: a nudge when a section background change is invisible. Two of the light surface steps side by side differ by about 1.06:1, which reads as one flat page; the build now points that out and suggests anchoring the page with a genuinely distinct band.

Fixed: card titles could be invisible. A section colour meant for text on the section background was being applied to text that landed on a card instead — measured at 1.1:1 on a light card in a dark band. Text now takes its colour from whatever it actually sits on.

Fixed: grids no longer strand a card on its own line. A three-across grid given four items rendered three then a lone one; item widths now follow the count and split evenly. Rows of five or more items that previously collapsed into a full-width stack now lay out properly.

Fixed: buttons follow your button shape. A generated button was pinned to a fixed corner radius and ignored the shape you chose, so a page could show pill buttons in its pricing cards and square ones in its hero.

New: Design DNA — set your site's durable style decisions once (how round corners are, how much air there is, how tall sections run, how wide content sits, which button your brand leads with, and how much things move) and every install follows them. It sits beside the flavour canvas in the Design System tab, and Claude can read and set it too. Leaving it alone changes nothing: the defaults reproduce exactly what you have today.

New: dark card variants. Every card composite now has a Dark twin for placing on an inverted band, with text that stays legible on it (measured 16.9:1, versus text that would otherwise have been invisible against the dark surface).

New: your forms look designed. Input fields now get a recessed fill, a soft border and a clear focus state that highlights the field you are typing in — on the contact form and the email opt-in, light and dark.

New: more ways to style the same things — four more button styles (including a quiet Subtle and a Ghost for dark panels, plus Large and Small), three more heading presets, and Bordered / Flat / Elevated shapes for every card.

Improved (visible): pricing tables no longer render plain. The plan name, price, subtitle, currency and excluded items now all take your fonts and sizes, and the header sits on your own surface instead of Divi's grey — which also fixes text that was slightly too faint to read comfortably.

Improved: pages Claude builds now use your preset library. Blurb titles and body copy in generated sections take their type from your design system rather than being decided page by page, so editing a preset changes the pages you already built. This is the first step; more section types follow.

Fixed (important): six sizes were stuck. Four small text sizes and two small spacing steps were meant to shrink on larger screens and never did — they were frozen at their phone-sized value on every screen. They now scale as intended. NOTE: this changes spacing and small text slightly on pages that use them; it is the behaviour they were always meant to have.

Improved: text on an inverted section is legible. Presets that set text on a dark band were rendering it the same colour as the band itself. New "On Inverse" text styles fix it.

Improved: card hover. Cards now lift gently on hover instead of snapping, and every card that uses a shadow inherits it.

Improved: the Style Guide's preset library page, a duplicate-preset checker that only merges what is provably safe, a rehearsal you can run before installing over an existing design system, and a presets-only install for sites that already have their own size scale.

Fixed (important): a page could lose all its styling and show raw code. When Claude tidied up duplicate design tokens, or built a WooCommerce cart/checkout page, the page's formatting could be stripped and raw block markup shown on screen. The cause was an escaping bug in how the content was saved; every place that writes a page has been audited and corrected. If a page was affected, restore it from its History (the design system takes a snapshot before it changes anything).

New: Flavours — save and switch your whole look. Save your current colours, fonts and spacing as a named "flavour", capture your existing site as a starting flavour, and switch between them. Import and export flavours as a file to move a look between sites (Pro). And preview a flavour on a single page before you commit it site-wide (values linked to a variable shift in the preview; nothing is saved until you install).

New: find and merge duplicate design tokens. If your Variables or Colours panel has the same value saved twice under different names, Divi Connect can now find them, show you where each is used, and safely consolidate them — relinking every page that referenced the retired token so nothing breaks. Ask Claude to check for duplicates, or use the new card in the Design System tab.

New: choose what happens on an install conflict. When you install a design system over one that's already there, you can now pick merge (add what's missing), replace, or keep both.

Improved: installs now report what they left behind — including any duplicate tokens found — so you can see the real result of an install, not just "done".

Improved: more presets out of the box, and a gentle nudge to install the design system on a site that has none (updating the plugin alone never installs presets — you install them once with a design system).

Improved: the design history is now a single Undo / Redo / Restore bar instead of a stack of rows, and Redo now works reliably (it used to get stuck after the first undo).

Improved: the size scale stays in order after it grows, so newly-added sizes no longer sort to the bottom.

Improved: the bundled Divi 5 Skill is updated to 0.6.5 — it was teaching one text-escaping rule backwards, which could double-escape angle brackets in hand-written HTML.

Security: hardened two internal paths — importing a reference URL and sideloading an image can no longer be pointed at private network addresses, and the plugin's own protected post meta now requires edit permission rather than accepting any authenticated write.

Fixed (important): an edited page could keep showing its OLD version on the front end. Divi caches a stylesheet per page, and our edits never cleared it, so a change made through Claude could stay invisible until the page was opened and saved in the Visual Builder. Every page write now clears that cache.

New: set the site's default heading and body font in one step, including families Divi's own Customizer cannot reach.

Fixed: a batch of build-quality issues — cards on a dark section no longer render white text on a white card, a gradient passed as a section background is now applied as a gradient instead of being ignored, button corner-radius and height set on a preset now reach every button, common icon names are accepted as aliases, deleting a Theme Builder template works, and a template meant for the whole site is no longer scoped to one page.

Improved: the one-click Style Guide page now documents the WHOLE size system — gap, radius, border, width and measure each get their own section, and every scale renders smallest to largest instead of in storage order. It now covers your design tokens only; the preset library moves to its own page in a later release.

New: the Design System. Install a complete, coordinated design system on your site in one command — colours, fonts, spacing and, on Pro, a fluid type/size scale and a full set of presets, all working together. Then change your whole site's look — colours, fonts, spacing — without rebuilding a single page: your existing pages re-theme automatically. There's a new Design System tab in the Divi Connect dashboard to preview and install a look, and a one-click "Style Guide" page generator that lays out every colour, font, size and preset on one editable page. (Free: colours, fonts and adopting your existing look. Pro: the fluid size scale and the presets.)

New: one-click revert for the Design System. Installing a look now takes an automatic snapshot of your whole design system first — colours, fonts, sizes and presets — so any site-wide change is a single click to undo, all the way back to how your site looked before you installed anything. Revert from the Design System tab, or just ask Claude to undo it. Reverting saves a snapshot of the current state first, so it's safe to try.

Improved: the Design System tab is clearer. It's now organised into three tabs — Current System (what's installed), Presets (browse every preset) and Flavours (build or switch your whole look) — and each colour now shows what it's actually used for (e.g. "Accent — hero backgrounds, icons, highlights").

Fixed: the preset preview gallery. Heading presets now show their true size scale, and light "inverse" icons no longer vanish against a white background.

New: match a reference. Point Claude at a live web page — "make it like this" — and it can now read that page's structure (its sections, headings, images and calls-to-action) and rebuild it on your site in your own design system, instead of guessing from a screenshot. It reads layout and content, not exact colours, so the result comes out in your brand. For a page already on your own site, Claude reads its real structure directly.

Improved: fewer silent misses when building. If Claude uses a key a section pattern doesn't recognise (a common typo), build_page now tells you instead of quietly leaving that bit blank.

Fixed: font families now load correctly in the design-system preview and byte-match how Divi itself writes them, so what you preview is what visitors get.

New: a much larger section-pattern library. build_page can now build pages from around 200 ready-made, responsive sections (up from 28) — about, team, careers and contact; SaaS and developer sections (changelog, roadmap, metrics, API, status board, code samples, pricing); industry sets for education, health, real-estate, travel, nonprofit and legal; and content and media (blog, video, podcasts, galleries, carousels, timelines) — and more. Ask for the section you want by name; most are built on Divi's own native modules so they stay fully editable.

Improved: people sections now use Divi's native Person module. Team, speaker, practitioner, agent and trainer cards render as real Divi Person modules — photo, name, role, bio and social icons — so they stay fully editable in the builder.

Improved: membership and pricing sections can now use Divi's native Pricing Tables module.

Fixed: buttons had too little padding. Button padding was being sent on an attribute Divi ignores, so buttons fell back to a cramped default and short labels left an empty gap beneath the text — every button now gets proper, balanced padding.

Fixed: images in showcase and hero sections now centre correctly — a large screenshot or video thumbnail no longer sits off to the left.

Fixed: text, eyebrow and badge alignment is now editable in the Visual Builder. They were positioned with a baked margin the VB alignment control couldn't override; they now use Divi's real alignment, so you can re-align them by hand.

Improved: assorted section polish — left-aligned feature and service icons now sit beside their text, card grids centre a partial last row, the tabs pattern keeps its active tab readable, and the timeline uses Divi's standard layout by default (ask for "alternate" to get a zig-zag).

Fixed: fonts from your design system now actually load for visitors. When Claude set a heading or body font using one of your global font variables, the page pointed at the right font — so it looked correct in the Visual Builder — but Divi was never told the font was in use, so it never loaded it. Visitors silently got a fallback (usually a generic serif) while the Builder showed the real thing. New pages now load the font you picked.

Note: pages built before this update still carry the old reference. Rebuild the page, or re-apply the font, to pick up the fix — updating alone won't change pages that already exist.

Fixed: intermittent time-outs and 503 errors. Viewing a page's rendered result used to make your site quietly fetch its own URL, which needs a second server process at the same time — on smaller hosting plans that could exhaust the pool and make calls hang or return a 503. Claude now renders the page in-process instead, so it no longer needs that second process. It's also much faster and works on drafts. (Reproduced on a real shared host: 503s eliminated, roughly 3.5x faster under load.)

Fixed: hand-written HTML now just works. When you (or Claude) write raw HTML into a module value on create/update, the server now escapes it for you — pass real <p>/<strong> tags as-is, no more escaping catch-22.

Improved: much smaller tool responses. Duplicating a page no longer dumps the whole copy back; single edits return just the section you changed (not the entire page tree); and the design system can be fetched in a compact summary. Faster, and far less likely to overflow the assistant's context.

Improved: more readable pages by default. Body paragraphs get a comfortable reading width instead of running edge-to-edge, and buttons meet a 44px minimum tap target on mobile.

Improved: better self-checking after a build. The built-in Divi 5 Skill now has a post-build polish pass — Claude reviews the rendered result against objective layout/accessibility heuristics and fixes issues in place instead of leaving them.

New: a library of 28 ready-made section patterns. build_page can now assemble a page from named, professionally-designed, responsive sections — hero, features, pricing, testimonials, stats, FAQ, team, logo strip, feature list, timeline, gallery, comparison, newsletter, tabs, slider, social follow, blog, portfolio, video, countdown, skills, contact, map, before/after and more — many built on Divi's own native modules so they stay fully editable in the builder. Ask for the section you want instead of describing raw layout.

New: name the layers (Pro). Optionally have Claude give every section, row and module a descriptive name so the Visual Builder layers view is easy to read and navigate on the pages it builds.

New: build long pages in stages. build_page can now ADD sections to an existing page instead of rebuilding it, so a big multi-section page builds reliably a few sections at a time (each step is additive and undoable) — no more all-at-once time-outs.

Improved: padding and margin changes now always take effect. A spacing tweak to one module could previously do nothing if it was sent on a slightly-wrong attribute path; Claude's edits are now placed on Divi's real spacing path (and the correction is reported), so "the padding didn't change" is fixed.

Improved: build_page can now rename an existing page when you build into it (previously the new title was ignored on an existing page).

Improved: clearer Free vs Pro. The current plan and exactly what each tier covers are now surfaced up front, so there are no surprises about what needs Pro.

Improved: hand-written pages that contain raw special characters (curly quotes, accented letters, em dashes) now warn that some AI clients can corrupt them in transit, and point you to safe escapes or to build_page (which handles text for you).

New: reuse a proven layout. Claude can now copy one or more sections from an existing page, post or project straight into another one — so you can start a new page (or case study) from sections you already like instead of rebuilding them.

New: fill Gutenberg (non-Divi) posts with content. For the agency pattern where clients stay in the block editor while a Divi Theme Builder template supplies the design, Claude can now write plain Gutenberg content into an existing post and switch it out of Divi-builder mode.

New: set a page/post/project's Featured Image directly — give a media-library ID or an image URL (fetched in for you) — and set an excerpt on pages too (posts and projects already supported it).

New: better-designed pages by default. The built-in Divi 5 Skill is updated (Divi 5.9 Grid Editor support and guidance to avoid common "AI-design" clichés), build_page can now use richer looks (background images with readable overlays, badges, tilted/scaled cards, variable fonts), and it now warns when a design shows tell-tale AI slop (emoji used as icons, raw code dumped into a page, buttons with no hover, one generic font everywhere).

New: History & Restore and the Activity Log are now FREE for everyone (previously Pro) — recover any page and see a full change history without a licence. Project memory stays Pro.

New: the free plan now works on an unlimited number of sites.

Improved: catch placeholder or wrong contact details before they go live. When Claude sets a global variable, it now flags values that look like placeholders (example.com, [email protected], 555-1234) or an email on a domain that isn't your site's — e.g. an agency address left in a client's site.

Improved: new pages keep your theme / Theme Builder header and footer by default; pass a "blank" template only when you deliberately want a full-bleed, chrome-less page.

Improved: clearer Free vs Pro — a full per-feature matrix is now documented so there are no surprises about what needs Pro.

Fixed: converting a previously-Gutenberg page to Divi (via build or update) no longer leaves a blank Visual Builder — the page is registered as a Divi builder page so it opens and edits correctly.

Fixed: editing an inline reference to a global layout used to silently change nothing (Divi renders it from the master). Claude is now told, and can edit the master layout by id to update it everywhere it's used.

Fixed: surgical one-module edits now run the same WCAG-AA contrast check as a full build, so a quick "modernise" tweak can't quietly leave text unreadable on its background.

Fixed: spacing issues in spec-built pages. Enlarged text (e.g. a big testimonial quote) could render with its lines overlapping — it now gets a proportional line-height automatically. And a card with its own background colour now gets sensible inner padding by default, so its text isn't jammed against the edge.

New: a redesigned Divi Connect admin dashboard. The plugin's screens are now one tidy, tabbed console under a single "Divi Connect" menu — with a new Overview landing page, an Account tab, and a light/dark theme toggle that remembers your choice.

New: Divi Connect now checks your environment before it writes a design system. If the Divi 5 theme isn't active (or the site is still on Divi 4), colour/variable/preset changes are stopped with a clear message instead of quietly going nowhere, and a warning appears on the Divi Connect and Plugins screens until Divi 5 is active.

New (Pro): Claude can now set your brand's five core colours in one go. Divi's factory global colours (Primary, Secondary, Heading, Body, Link) are now read and overwritten in place — so a brand palette updates those swatches directly instead of adding five duplicates to your colour picker.

New (Pro): clean up your design system. Claude can now delete specific global colours, variables or presets — or clear a whole group — without you having to hand-edit them in Divi.

Improved: when you run several sites, each with its own connector, the connector now identifies itself by site name and domain in Claude's permission prompt, so it's easier to approve the right one.

Fixed: editing a Divi Portfolio project one module at a time now works. Reading a project's module outline (and add / edit / move / remove a single module in place) previously only worked on pages and posts — projects can now be edited surgically like any other content.

Maintenance: updated the Freemius licensing SDK to 2.13.4.

New: a "Settings" page (Divi Connect → Settings) with optional safety switches. "AI always plans first" — the AI pauses before building any new page to ask a few planning questions (who it's for, the key sections, your brand, the main call-to-action) and show you a short plan to approve first, for better structure at the cost of a few more tokens. "Always save new pages as drafts" — every new page, post or project the AI creates is saved as a draft for you to review instead of being published straight to your live site. "Confirm before overwriting a page" — the AI must stop and ask before it replaces the whole content of an existing page, so a live page can't be rewritten by accident. All are off by default; the last two are recommended on live/client sites, and none of them block small in-place edits.

New (Pro): three more Settings switches for extra control on live and client sites. "Protect global design & Theme Builder" — the AI must confirm before changing anything site-wide (global colours, variables, presets, or a Theme Builder header/footer/template). "Read-only (draft-only) mode" — the AI can read and build drafts but can't publish, delete, or change site-wide design, so you stay in full control of what goes live. "Stick strictly to my design tokens" — pages the AI builds now auto-snap colours/sizes that match your variables to those variables (and flag any hardcoded colour with no match), so everything stays on-brand and re-themeable.

New: the page builder now sticks to your design system by default. A colour that exactly matches one of your global colours is bound to that colour variable automatically, you can refer to a variable by its label ("Primary") instead of its id, and an unknown token is flagged rather than silently dropped — so pages come out referencing your variables, not a pile of one-off hardcoded values. (Referencing size/number variables is a Pro feature; on the free plan sizes use clamp()/px values — colours and fonts are unaffected.)

New: design reconciliation for imported designs. When you build with colours/sizes that are CLOSE to your existing variables (e.g. a design brought over from Figma), the AI pauses and asks how to handle them: "snap" to your existing variables, "adopt" — update your variables to the new values site-wide (Pro), or "append" — add them as new variables and keep yours (Pro). No more accidental palette drift.

Improved: tidier admin menu — Connection is now the landing page (the separate Overview page is gone), History and the Activity Log are combined into one "History & Activity" page, and the order now reads Connection, Troubleshoot, History & Activity, Memory, Settings, Endpoints.

Improved: the built-in Divi 5 Skill now includes a render-tested case-study / project layout (alternating image + text rows) so project and case-study pages come out with a proper design instead of a plain stack.

Maintenance: updated the Freemius licensing SDK to 2.13.3.

Fixed: adding, editing, moving or removing a single module now always saves. Previously, with "Confirm before overwriting a page" turned on, a one-module edit could report success while the change silently didn't stick. And a section added without any settings of its own could lose its inner layout on save; both now persist correctly.

Fixed: a malformed global preset can no longer break preset saving for your whole site. Presets are now normalised to the current format when written, so one bad entry can't stop the Divi builder from saving any preset (including your own). If a site is already stuck this way, ask the AI to "repair my presets" (new recovery tool) to fix it without changing any of your styling.

New: Divi Portfolio "Projects" are now supported — Claude can create, read, edit, duplicate and list Projects (case studies / portfolio items), not just pages and posts, including their project categories and tags. Best workflow for a consistent look: ask Claude to duplicate one of your existing projects and edit the copy, so the new one keeps your case-study layout. (Only appears on sites that have Divi's Portfolio enabled.)

New: Claude can now read your site's real Divi 5 module schema — the available modules and their exact settings — so it builds against the actual structure instead of guessing (fewer broken layouts). Three new read-only tools: list modules, get a module's fields, and the shared styling groups.

New: edit an existing page one module at a time — add, change, move or remove a single module in place — instead of rebuilding the whole page. It's faster and cheaper, and it leaves the rest of the page untouched. Ask things like "make the hero heading bigger" or "add a button under the intro."

New: a safety net for edits. Every change Divi Connect makes is automatically snapshotted first, so nothing is lost. Recover any page for free from the new Divi Connect → History screen (a list of snapshots with a Restore button); Pro users can also just tell Claude "undo that" and it rolls the page back in chat. Restores are themselves undoable. A new Divi Connect → Activity Log shows a full change history — when, what, and who (the WordPress user for manual edits, or Claude for connector changes) — handy for peace of mind and client hand-off.

New (Pro): project memory — Claude remembers this site's conventions between sessions (palette, fonts, tone, "always do X"), and they're loaded automatically each session so you don't repeat yourself. Manage them under Divi Connect → Memory, or just tell Claude "remember that…".

New: the free Divi 5 Skill is now built into the connector — no separate install, and it's always matched to your plugin version. Claude loads it automatically when it connects and pulls just the parts it needs for the task, so pages come out higher quality out of the box (this works on the hosted claude.ai connector too, including free accounts, where a manually-added Skill often isn't available).

Improved reliability: the essential Divi 5 block rules (the ones that otherwise cause blank or broken pages) are now sent to Claude together with your design system every time it starts a build, so pages come out correctly even in a session where the full Skill wasn't loaded. The builder version Claude stamps also now always matches your installed Divi.

Improved first drafts: when Claude goes to build a brand-new page without having loaded the built-in Skill yet, it's prompted once to load the Skill and run a quick plan first — so it asks the right questions and gets the structure right the first time. If you've asked it to just build immediately, it proceeds on retry (this never blocks you). Editing existing pages is unaffected.

Fixed: icons now render reliably across Divi-built pages — feature cards (blurbs), the Icon module and Icon Lists — whether Claude builds from a spec or from markup. (Icon glyphs were being altered when the page was saved, leaving a blank space.) For feature cards you can just name the icon you want — a FontAwesome name ("magnifying-glass"), a Divi icon name, or a hex codepoint — and the server builds the correct icon, with optional size and colour.

Fixed: the "Activate your license" link on the Overview page now always goes somewhere that works for your current state, instead of occasionally dead-ending on a "not allowed" screen before your account is connected. Users mid-activation now see a clear "confirm your email" note.

Changed: Divi Connect now has its own top-level admin menu (instead of sitting under Settings) — easier to find, with Overview, Connection, Troubleshoot and Endpoints as sub-pages.

Fixed: the Freemius Account page is now reachable. It was registered but had no visible menu link, so license management (Sync, Change Plan, Deactivate, Billing) and the "Join the Beta program" opt-in were effectively hidden. Account and Upgrade now appear under the Divi Connect menu.

Improved: the license/opt-in screens now show the Divi Connect logo and explain why connecting matters, so you don't accidentally skip activation and end up silently on the free tier.

After activation you now land on the Divi Connect settings page.

New: after a plugin update, a reminder prompts you to refresh Claude's connector so it picks up any newly added tools (the tool list is cached when you connect). A matching "Refresh Claude's tool list" tip is on the settings page.

Fixed: Divi-built blog posts are now proper builder posts — they open and save in the Visual Builder without the body being wiped. (Previously a connector-created post could lose its content the first time you edited and saved it in the builder.) Editing an affected older post repairs it automatically.

New: choose how a post is built — a full Divi-designed post (editable in the Visual Builder) or plain content styled by your Theme Builder single-post template. Claude asks when it's not obvious.

New: duplicate a page or post — Claude can copy an existing one (design, layout, featured image and categories included) into a new draft to edit from there, so you can reuse a design as a starting point.

New: Claude can find a page or post by its title, so you can say "duplicate my Services page" without looking up IDs.

New: connection health check on the settings page — if your web host's firewall or anti-bot/DDoS protection is blocking Claude, the page tells you exactly that and how to fix it (allowlist Anthropic's IPs or exclude /wp-json/) instead of a confusing "couldn't connect" error.

New: your plan (Free or Professional) is now shown clearly on the settings page, with a one-click "activate your license" link when you're on Free — so a license key that hasn't been activated yet no longer leaves you silently on the free tier missing Pro features.

New: Claude can now read an existing Theme Builder layout (header, footer or body) and edit it in place, instead of rebuilding it from scratch — so tweaks to your global header/footer keep everything else intact.

New: reminders to install the free Divi 5 Skill for best results — a notice on the Divi Connect settings page, plus an instruction sent to Claude when it connects (without the Skill, generated pages can come out lower quality).

Settings page now lists the new "read Theme Builder layout" endpoint.

Better-looking pages from build_page: new section presets (hero, features, cta, steps) — describe a common section and the plugin assembles a tidy, well-spaced layout (structure, spacing, type scale and alignment handled for you).

Design safeguards: unknown colour/size/font variables are now skipped (the element inherits a sensible colour instead of Divi's default) and reported back, and text colour is checked for WCAG AA contrast — auto-set over a known background, or flagged when a chosen colour would be hard to read. Check the new "warnings" in the response.

Fixed gradient global variables created via the API not rendering: they are now stored in Divi's structured gradient format, so they appear in the Variable Manager and emit a front-end CSS value (previously a gradient variable saved but showed empty and produced no output). Send a settings object — e.g. {"type":"linear","direction":"180deg","stops":[{"color":"#000","position":0},{"color":"#fff","position":100}]} — rather than a raw CSS gradient string.

Fixed dividers built from a compact spec rendering a double line (the module's native line now carries the color instead of stacking a separate border).

Fixed margins given as a positional list ([top, bottom, left, right]) being ignored when building from a spec.

Documentation: clarified that the free Divi 5 Skill is recommended alongside the plugin so Claude writes valid, on-brand Divi 5.

Build pages from a compact component spec: Claude sends a small structured layout and the plugin expands it into valid Divi 5 markup server-side — fewer tokens and no more blank-page mistakes (escaping, structure, and design-system tokens are handled for you).

See your results: a new tool returns a published page's rendered HTML plus its page-specific Divi CSS, so Claude can check spacing, contrast, and alignment and fix issues instead of building blind.

Blog posts can now be authored with the Divi Builder OR plain Gutenberg — choose per post ("builder": "divi" | "gutenberg").

Reusable global layouts now actually embed on pages (reference by id via "globalModule"); added a list endpoint to find existing ones.

Smart quotes, dashes and emoji written as numeric HTML entities are preserved correctly on insert (no more corruption).

Page/post responses now include non-blocking authoring warnings (e.g. a page built mostly from Code modules).

The design system now reports which token buckets are empty, so Claude can offer to generate colors/variables when a site has none.

Edit pages in place: read a page's Divi markup and update it without delete-and-recreate (keeps the URL and history).

Create real WordPress blog posts (not just pages) with Divi, including categories, tags, and excerpt.

Theme Builder: build global headers and footers (site-wide), update a layout's content, and delete templates safely.

Manage the design system reliably: global colors now appear in the Variables panel, and size/font/gradient variables are created in Divi 5's real store (fonts are now supported).

New page option to render the theme/Theme Builder header and footer around a page instead of full-bleed.

Fixed a Theme Builder encoding issue that could dump raw HTML/CSS as visible text.

Delete safety: deleting a page now requires explicit confirmation and moves it to Trash (recoverable) by default; permanent deletion is opt-in.

Claude confirms with you before deleting any page.

Refreshed the Settings page connector details and endpoint reference.

Free and Professional tiers.

Native MCP server for claude.ai and Claude Desktop custom connectors.

Design system reads Divi 5 active variables, colors, gradients, and presets.

Markup validation prevents blank/broken pages.

Site-aware connector identity for multi-site setups.