How to Add a Changelog, Roadmap & Knowledge Base to Divi & Avada

Divi and Avada do not include built-in changelog, roadmap, or knowledge base modules. This guide shows how to add all three to either builder using their native code elements, in under five minutes per page. The same workflow covers single-page embeds, theme-builder global widgets, and external subdomains.

Try it yourself: Start your free plan and embed a changelog via Divi's Code Module or Avada's Code Block. No credit card required.

Why does a Divi or Avada agency site need a changelog?

Divi and Avada share the same core audience: WordPress agencies building and maintaining client sites. Both themes are built for agencies that deliver polished websites and need to communicate ongoing work.

Client deliverables become visible. Instead of sending status emails or compiling PDF reports, embed a changelog directly on the client's site. Every design update, plugin upgrade, and content revision gets logged with context, timestamps, and screenshots. Clients check progress on their own schedule.

SaaS and membership sites need product changelogs. If your SaaS marketing site runs on Divi or Avada, your product changelog should live on that same site. Visitors see your development velocity. Subscribers get notified when you ship. Prospects gain buying confidence.

Replace scattered communication. Phone calls, Slack messages, and email threads about "what changed" get replaced by a single, searchable record.

Divi ships with extras that pair well with a public changelog. The Divi membership includes Bloom for email opt-ins and Monarch for social sharing, plus the built-in Divi Leads split testing engine that few other WordPress builders match. Avada counters with Avada Studio and Avada Layouts, a library of pre-built section, page, and full-website templates that ThemeFusion has expanded steadily since the 2020 builder rewrite. Both feature sets reinforce why these themes win agency mandates, and why a changelog belongs on top of them rather than inside a separate tool.

ProductLift provides a changelog for Divi and a changelog for Avada with categorized entries, rich media, email notifications, and reaction buttons. For tips on writing effective updates, see how to write release notes.

Over 1 million sites run Divi and 950,000+ run Avada. Neither builder ships with a native changelog, roadmap, or knowledge base module, leaving agencies to stitch together feedback tools across every client retainer. (Elegant Themes, ThemeForest Avada Sales)

How do you add a changelog to a Divi or Avada site?

The integration uses each builder's native code element. No third-party plugins required for either theme.

Divi: Code Module

1. Open the Divi Builder on any page
2. Click the gray plus icon to add a new module
3. Search for Code and select the Code Module
4. Paste the ProductLift embed snippet (iframe or JavaScript) into the code content area
5. Click the green checkmark to save the module
6. Save and exit the Divi Builder

The Code Module preserves raw HTML and scripts without Divi's visual editor stripping anything out. You can also use the Text Module and switch to the "Text" tab (not "Visual") for simpler embeds alongside other content.

Avada: Code Block Element

1. Open the page in Fusion Builder
2. Click Add Element and search for Code Block
3. Select the Code Block element
4. Paste the ProductLift embed snippet into the code area
5. Save and publish the page

Avada's Dynamic CSS system will not conflict with ProductLift's styles because the embed is sandboxed.

Divi: Theme Builder for site-wide placement

Edit your global template in the Divi Theme Builder. Add the ProductLift notification widget code to the header or footer template area using a Code Module. Every page on your site then shows a changelog notification badge.

Avada: Layout Builder for site-wide placement

Open Avada > Layouts and edit your global layout. Add the ProductLift notification widget code to the header or footer layout section. Every page shows a changelog notification badge without editing individual pages. You can use Avada's conditional logic to show the changelog only on specific pages or to specific user roles.

Divi: A/B testing for placement optimization

Divi's built-in split testing lets you test changelog placement. Create two versions of a section: one with the changelog visible inline, another with just a notification widget. Divi tracks which version drives more engagement. This is a unique advantage over other WordPress builders that lack native A/B testing.

Both methods take under five minutes. ProductLift is hosted externally, so there are zero theme conflicts with either Divi or Avada updates.

Embed methods at a glance

Why does a Divi or Avada site need a public roadmap?

Whether you run an agency, a SaaS product, or a WooCommerce store, a public roadmap answers the question every user eventually asks: "What are you building next?"

For agencies: A shared roadmap on the client's site replaces status meetings. Project milestones move through columns as you deliver. Clients check progress on their own schedule, leave comments on specific items, and see transparent timelines.

For SaaS companies: Your product roadmap on your Divi or Avada marketing site serves both acquisition and retention. Prospects see active development. Existing customers see their requested features moving through the pipeline and stay engaged instead of churning.

For theme and addon developers: If you sell Divi child themes, Avada configurations, or WordPress plugins, a public roadmap shows customers which features are coming next. Users vote on what matters, reducing guesswork about where to invest development time.

ProductLift provides a roadmap for Divi and a roadmap for Avada that embed directly into either builder. Read our complete guide to public roadmaps for strategy and best practices.

How do you add a public roadmap to a Divi or Avada site?

The same modules handle roadmap embeds. Roadmaps benefit from a full-width layout because they display status columns (Planned, In Progress, Shipped) side by side.

Divi

Open the Divi Builder on your dedicated roadmap page. Create a full-width row with a single column. Add a Code Module and paste the ProductLift roadmap embed code. The interactive roadmap renders with voting, comments, and status columns inside your Divi layout.

For site-wide access, use the Divi Theme Builder to add a roadmap notification widget to your global header or footer template. You can also use Divi's built-in A/B testing to experiment with different roadmap placements and measure engagement.

Avada

Open the page in Fusion Builder. Create a full-width container with a single column. Add a Code Block element and paste the embed code. Adjust the container padding in Avada's element settings to give the roadmap enough space.

Avada's Layout Builder supports conditional display based on user roles. This means you can show the roadmap only to logged-in users, which is useful for client portals where you want to share project progress without exposing it publicly.

Both embeds are fully responsive and adapt to column widths across desktop, tablet, and mobile breakpoints.

Why does a Divi or Avada site need a knowledge base?

Divi and Avada power complex business websites with WooCommerce stores, membership areas, booking systems, and multi-language content. That complexity generates support volume that a simple FAQ page cannot handle.

Both builders include FAQ elements (Divi's Accordion Module, Avada's FAQ Element), but these are basic: no search, no categories, no analytics, and no way to track what users are looking for. They work for a handful of entries but break down past 20 articles.

ProductLift provides a knowledge base for Divi and a knowledge base for Avada with full-text search, nested categories, helpful/not helpful voting, and AI-generated articles from shipped changelog entries. For a complete walkthrough, see our guide on how to create a knowledge base.

How do you add a knowledge base to a Divi or Avada site?

Divi

Create a dedicated help center page in Divi Builder. Add a full-width row with a single column. Insert a Code Module and paste the ProductLift knowledge base embed code. The KB renders with full search, category browsing, and article navigation inside your Divi layout.

For site-wide search access, use the Divi Theme Builder to add a ProductLift KB search widget to your global header template. Visitors search for help articles from any page without navigating to the dedicated help center.

Avada

Create a help center page in Fusion Builder. Add a full-width container with a single column. Insert a Code Block element and paste the embed code. Use Avada's conditional display rules to show the search widget only on specific pages or to specific user roles.

External subdomain (both builders)

Host your knowledge base at help.yoursite.com and link to it from your navigation menu. This keeps your Divi or Avada layouts completely untouched while giving visitors a full help center experience.

Quick Comparison: Divi vs. Avada Integration

Both builders handle ProductLift embeds cleanly with no performance overhead. The main difference is Divi's built-in A/B testing for optimizing placement, while Avada offers more granular conditional display rules through its Layout Builder. If you use both builders across different client projects, the same ProductLift account and embed codes work in either one.

How It All Connects: The Journey Model

Divi by Elegant Themes and Avada by ThemeFusion share a defining commercial trait: both are sold predominantly through lifetime licenses. Once a customer pays for Lifetime Divi or a perpetual Avada license, the relationship is forever, and the customer expectation is that the product keeps shipping updates worth that lifetime fee. The Journey Model is built for exactly that long-tail relationship.

1. A lifetime Divi or Avada license holder submits feedback on your feedback board requesting a theme refinement, a new module, or a child-theme variant
2. Other lifetime license holders vote, and the request accumulates a measurable demand signal that ElegantThemes or ThemeFusion can defend in their roadmap meetings
3. You promote the post to your roadmap as "v4.27 update" and license holders watch the status change in real time on the public roadmap
4. When the update ships, the post becomes a changelog entry. Every lifetime customer subscribed to the changelog feed receives an automatic notification, with their original request quoted in the email when the request was theirs
5. AI generates a knowledge base article from the shipped feature, and the same notification email is the natural moment to ask the customer for a Themeforest review, which compounds the long-tail social proof every theme business depends on

For agencies maintaining 30 client sites on Divi or Avada, the same model collapses across the entire portfolio: client end-users feed requests into a shared board, the agency prioritizes once, ships across the portfolio, and every client end-user who voted is notified on their respective branded site automatically. One workflow covers a 30-site book without 30-fold rework.

Pricing

The Divi and Avada audience is dominated by agencies on retainer, and agency math is unforgiving on per-seat tools. A typical agency runs 30 client sites under one retainer umbrella, with each client expecting their own branded changelog, roadmap, and help centre. Stacking per-client or per-seat pricing across 30 client portfolios kills the retainer margin fast: even a $5/site/month tool eats $150/month off the agency's bottom line, and most feedback tools meter higher than that.

ProductLift starts at a flat $19/month (billed annually) with unlimited tracked users and voters. One ProductLift workspace covers every client site in the agency's portfolio at the same flat rate. Whether you maintain 5 Divi sites or 30 Avada sites under retainer, the bill stays at $19/mo. No per-client cost, no per-seat escalation, no usage caps.

That ROI math is what makes ProductLift a clean fit for the Divi and Avada agency model: $19/mo flat across 30 client retainers works out to roughly 63 cents per client per month, which the agency absorbs without renegotiating any client contract. Every plan includes changelog, roadmap, knowledge base, feedback boards, AI prioritization, and white-label branding. You can also explore the changelog for WordPress page for general WordPress setup details.

$150/month versus $19/month. A typical $5/site feedback tool eats $150/month off a 30-client retainer agency's bottom line. A flat ProductLift workspace works out to roughly 63 cents per client without renegotiating any contract. (ProductLift Pricing)

FAQ

Does the embed work with both Divi's Visual Builder and Back-end Builder?

Yes. The Code Module works in both the Divi Back-end Builder and the Visual (front-end) Builder. You paste the embed code once, and it renders correctly in both editing modes.

Will the embed conflict with Divi or Avada updates?

No. ProductLift is hosted externally. There are no files in your theme directory, no database tables, and no PHP hooks. When Divi or Avada releases an update, your embed continues working exactly as before.

Can I show the roadmap only to logged-in users?

Yes. In Avada, the Layout Builder supports conditional display based on user roles, so you can restrict the roadmap to logged-in visitors. In Divi, you can use Divi's display conditions or a membership plugin to control visibility.

How does this compare to FAQ plugins?

Both Divi's Accordion Module and Avada's FAQ Element display static question/answer pairs on a single page. They have no search, no categories, and no analytics. ProductLift's knowledge base includes instant search with fuzzy matching, hierarchical categories, view analytics, and AI article generation from shipped features. The built-in FAQ elements work for five or ten questions. For anything larger, a dedicated knowledge base is the better choice.

Can I use Divi's A/B testing with the changelog?

Yes. Wrap the changelog embed in a Divi section, create an A/B test, and set up a variation with a different placement or a notification widget instead. Divi tracks which version gets more engagement, helping you find the optimal approach.

Can I customize the look to match my Divi or Avada design?

Yes. ProductLift offers full color, font, and layout customization. The white-label option removes all ProductLift branding. The embed adapts to your column width automatically in both Divi and Fusion Builder.

Will it slow down my site?

No. ProductLift is hosted on external servers. The embed code loads asynchronously and adds no database queries, no PHP execution, and no files to your WordPress installation. Your page speed scores remain unaffected.

Is there a free plan?

Yes. ProductLift offers a free plan so you can test the full platform before committing. No credit card required to start.

Can agencies white-label the changelog across multiple client sites?

Yes. Every plan includes white-label branding, so the "Powered by ProductLift" mark is removed and each client site shows its own colors, fonts, and logo. One ProductLift workspace can host separate boards per client, and each board can be embedded on a different Divi or Avada site with its own custom domain like feedback.clientdomain.com. Agencies maintaining 30 retainer sites pay the same flat $19/month rather than a per-client fee.

How do Divi and Avada update cycles affect the embed?

Both vendors ship frequent releases. Elegant Themes pushes Divi updates regularly through the WordPress dashboard, and ThemeFusion publishes Avada updates roughly every few weeks alongside its Avada Studio additions. Because ProductLift loads from an external script, the embed keeps rendering through any builder, theme, or core WordPress update. You do not have to retest the changelog code after each Divi or Avada upgrade.

Try it yourself: Start your free plan and ship a public changelog this week. The free plan gives you full access to white-label branding, custom domains, and unlimited end-users.