Overview #
Divi is an Elegant Themes WordPress theme with a visual page builder, template library, global design system, and theme-level layout controls. It can build complete marketing, business, and ecommerce sites without a separate page-builder plugin.
When to use it. Use it when the team wants a visual editing workflow and is prepared to manage global presets, reusable sections, responsive settings, and performance as a unified design system.
Before You Begin #
Platform compatibility. Use a WordPress and PHP combination supported by the current developer release. Minimum versions can change; verify the current official product page or plugin/theme metadata before production deployment. Do not bypass an activation or compatibility warning without identifying its cause.
Requirements and dependencies #
- – A working WordPress site and administrator access.
- – The installable Divi theme ZIP.
- – An Elegant Themes account and API key are required for official automatic updates.
- – WooCommerce only for store functionality.
Pre-installation checks #
- – Back up the site and test a theme switch on staging.
- – Record current menus, widgets, templates, custom code, and builder dependencies.
- – Keep the downloaded ZIP compressed and confirm it is the theme Installer.
Installation #
- 1. Download the installable ZIP from the Nippy Launch Resource Library and keep it compressed.
- 2. Open Appearance > Themes > Add New Theme > Upload Theme.
- 3. Choose the Divi ZIP, select Install Now, and activate the theme.
- 4. Open Divi > Theme Options and configure identity, navigation, integrations, and performance settings deliberately.
- 5. Create or edit a page and enable the Visual Builder.
- 6. Assign the primary menu and set the home page under Settings > Reading.
License Activation #
- 1. Go to Divi > Theme Options > Updates.
- 2. Enter the Elegant Themes username and a valid API key from the account, save, and confirm authentication succeeds. (First, check whether the Pro version is already active, as manual license entry may not be required.)
- 3. Do not paste an account password into the API-key field. The Nippy Launch archive does not by itself include an Elegant Themes account or API key.
- 4. If you require a Divi API key specifically for your website, please contact us through your Client Area with your website details, and we will provide you with one.
Important. A premium download does not automatically establish ownership of the original developer’s account, license key, automatic-update service, cloud features, or direct support. Use only Credentials that are valid for this site and were supplied through an authorized account or an explicit Nippy Launch entitlement.
Initial Setup #
- 1. Set global colors, fonts, spacing, buttons, and presets before building many pages.
- 2. Configure the Theme Builder only for templates that truly need global replacement.
- 3. Review Divi performance options after the design is stable and test each optimization with forms and third-party scripts.
- 4. Configure WooCommerce templates and complete a test purchase when applicable.
Recommended Configuration #
- – Use global presets and Theme Builder templates to reduce page-by-page overrides.
- – Keep custom CSS and code snippets documented; use a child theme for PHP or theme-file changes.
- – Optimize hero media, background video, and animation for mobile.
- – Avoid loading two visual builders on the same page.
- – Test cached and logged-out views after enabling static CSS, deferred scripts, or other performance controls.
Main Features #
The installed edition can provide the following primary capabilities. Availability may depend on the active plan, add-ons, and current release.
- – Visual drag-and-drop page building
- – Global design presets and reusable library items
- – Theme Builder templates for headers, footers, posts, products, and archives
- – Responsive design controls
- – WooCommerce design modules and marketing layouts
How to Use It #
Practical starting workflow. Create global brand colors and type presets, build one landing page with a reusable call-to-action section, and test that section on a second page. Then inspect phone and tablet modes before publishing.
Integrations #
- – WooCommerce
- – Email marketing and form services through Divi modules or supported plugins
- – Caching, CDN, and optimization tools require testing with Divi’s own performance settings.
Enable an integration only after its account ownership, permissions, data flow, and failure behavior have been tested. Keep secret Credentials out of page content and screenshots.
Common Issues & Troubleshooting #
- – Theme upload fails. Confirm the ZIP is the installable Divi theme and check the hosting upload limit.
- – Visual Builder does not load. Clear caches, test with browser extensions disabled, review Divi Support Center status, and isolate plugin conflicts on staging.
- – Changes are not visible. Clear Divi static CSS, page cache, server cache, and CDN cache.
- – Global template affects unexpected pages. Review Theme Builder assignment and exclusion rules.
- – Automatic updates fail. Verify the Elegant Themes username/API key pair and outbound HTTPS access.
If the problem persists, reproduce it on staging, capture the exact error and relevant logs, and compare the behavior with nonessential plugins temporarily disabled. Restore the production site rather than troubleshooting destructively in place.
Updating the Plugin or Resource #
- 1. Create a backup and update Divi on staging.
- 2. Review release notes, clear generated CSS/cache, and test global templates, forms, sliders, menus, responsive layouts, and checkout.
- 3. Keep child-theme customizations separate from the parent update.
- – Confirm that the backup completed and can be accessed independently of WordPress.
- – Review the official changelog and compatibility notes.
- – Update during a low-risk window and keep a tested rollback path.
- – Clear relevant caches and perform the product-specific functional tests listed above.
Uninstallation #
- 1. Activate a default theme before deleting Divi.
- 2. Export Divi Library items and document Theme Builder templates and custom code.
- 3. Pages built with Divi modules may leave shortcodes or require rebuilding in the replacement system.
Deactivation and deletion are not the same as data removal. Confirm the product’s current cleanup options, Database tables, uploaded files, remote data, connected accounts, and continuing external billing or scheduled actions before removal.
Security & Best Practices #
- – Restrict access to Divi code and integration fields.
- – Do not embed secret API Credentials in visible modules.
- – Keep API keys private and rotate them if exposed.
- – Test form spam protection, consent text, and external scripts.
- – Use unique administrator accounts, least-privilege roles, HTTPS, and multi-factor authentication where supported.
- – Keep the resource, WordPress, PHP, theme, and dependencies on supported versions.
- – Store backups and recovery instructions outside the WordPress site.
Final Checklist #
- ✅A restorable backup was created before installation or major configuration.
- ✅All required core plugins, themes, services, and accounts are active.
- ✅The resource is installed and activated without WordPress or PHP errors.
- ✅The product-specific initial and recommended settings are complete.
- ✅The practical workflow was tested as an administrator and as the intended visitor/customer/member.
- ✅Email, payments, webhooks, cron, cache, and integrations were tested where applicable.
- ✅Security, privacy, consent, data retention, and access rules were reviewed.
