Soliloquy Defaults - WordPress Plugin

Guide to Configuring Soliloquy Defaults for Consistent WordPress Sliders

Soliloquy Defaults is not meant to build a single attractive slider. Its real purpose is different: it lets you define the baseline settings that all new Soliloquy sliders will start with. In this guide, you'll learn how to use the addon in a way that actually saves time: which settings belong in the template, how to avoid breaking individual sliders, how to verify inheritance, and what to do if a new slider does not receive the settings you expected.

This guide is written for a site owner, editor, or developer who already works with Soliloquy and regularly creates multiple sliders: for the homepage, category pages, landing pages, promotions, portfolios, product collections, or seasonal content blocks. Instead of manually repeating the same setup for dimensions, behavior, navigation, captions, and related addons, you configure one utility slider called Soliloquy Default Settings and then use it as your starting point.

Below, you'll find pre-installation preparation, setup of the base slider, a practical example for a site with multiple promo blocks, result validation on the page, troubleshooting, a comparison with similar solutions, and an FAQ. This guide does not repeat the product's short description. It shows a working process from decision-making to safe testing on a live site.

What Problem the Addon Solves and When You Need It

The main value of Soliloquy Defaults becomes clear on sites where sliders are created regularly, not just once. A standard Soliloquy slider is configured through the familiar editing screen: images, configuration, extra tabs from enabled addons, publishing, and insertion via block, shortcode, insert button, or widget. That works well when there are only a few sliders. But once a site has several blocks built around the same logic, manual setup quickly becomes a source of small inconsistencies.

This addon is specifically designed to solve the problem of repeatability. After activation, you get a special utility slider called Soliloquy Default Settings. It looks like a regular slider, but it functions as a default settings profile. When you create a new slider, you can choose to inherit configuration from this utility set. As a result, the new slider starts with preconfigured values instead of a blank setup.

It is important to understand the product's boundary: Soliloquy Defaults does not replace Soliloquy itself, does not create content for the editor, and does not automatically turn old sliders into new templates. It provides a foundation for future sliders. That is why it works best before you start creating lots of slider blocks, not after the site has already accumulated dozens of mismatched sliders.

Typical Use Cases

In practice, the addon is especially useful in four situations. First, an agency builds WordPress sites and wants the client's editors to create new sliders according to one standard. Second, an online store or catalog regularly publishes seasonal collections where consistent height, arrow behavior, and slide speed matter. Third, a content site displays sliders in articles and categories but does not want to explain safe settings to editors every time. Fourth, the site uses multiple Soliloquy addons, such as themes, thumbnails, lightbox, schedule, or featured content, and you need to avoid forgetting the baseline values on each tab.

If the site only has one slider and it rarely changes, the addon may be unnecessary. In that case, it is simpler to configure that one slider manually and keep instructions for the editor. Soliloquy Defaults makes sense when you have a repeatable process: "create a new slider, upload images, adjust the content slightly, insert it on the page."

Which Settings Actually Belong in Defaults

You should not move everything into the utility settings set. Good default values are settings that stay the same most of the time: slider dimensions, responsive behavior, base image size, cropping, arrows, navigation dots, autoplay behavior, transition speed, a CSS class for consistent styling, and lightbox or thumbnail settings if they should match across most new sliders.

Bad default values are anything tied to a specific page: the image selection, caption text, custom links, an individual slide display date, a special height for one landing page, or a unique design theme for one campaign. Those are better configured after creating the specific slider. Otherwise, the addon stops being helpful and starts dragging unnecessary logic into every new block.

Practical rule: only put settings into Soliloquy Defaults that editors should receive automatically and rarely need to change. Anything tied to a specific page should be left for manual editing in the new slider.

Who Soliloquy Defaults Is a Good Fit For and Who Should Skip It

Soliloquy Defaults fits well into a workflow built around a repeatable visual standard. It does not make a slider "better" on its own, but it reduces the chance that two similar blocks will behave differently because someone forgot a setting. That is especially valuable on team-run sites: one person defines the standard, and everyone else creates sliders from it.

The addon is worth considering if you frequently create new Soliloquy sliders, use similar image dimensions, want to lock in consistent navigation behavior, work with multiple editors, or maintain client websites. It is also useful if the project relies on paid Soliloquy addons, because the tabs and settings available in the utility slider depend on which addons are active.

You should not install the addon just for a single homepage slider. You should not use it as a substitute for a design system if every slider on the site is intentionally unique. And you should not enable it without a plan if editors are used to freely changing how each block behaves. In that case, you first need to agree on what actually counts as the standard.

Editorial Teams

For an editorial team, the addon is helpful because it reduces the number of decisions required when creating a new block. The editor does not need to remember whether arrows are enabled, how cropping is configured, which size to choose, or which CSS class to add. They create a new slider, inherit the baseline setup, and focus on the content: images, captions, links, and slide order.

There is one nuance, though: editors need to understand that inherited settings can still be changed in a specific slider. If your workflow requires a strict standard, it is best to document the rules in a short internal guide: which fields can be changed, which ones should only be changed with approval, and how to check the result on a mobile screen.

Developers and Site Administrators

For a developer, Soliloquy Defaults is useful as a first-layer configuration system. You can define the baseline once, add a CSS class, verify output in the theme, confirm that the shortcode or block works correctly, and then hand over a ready-to-use workflow to the client. This is especially useful after theme setup, caching, image optimization, and styling are already in place.

At the same time, the addon does not replace proper compatibility testing. If sliders are not displaying because of a JavaScript error, a theme conflict, caching, or lazy loading, the utility settings set will not fix the problem by itself. What it can do is preserve the correct values once you have found the root cause.

Sites With a Single Unique Slider

If the site has one hero block on the homepage and it is not reused anywhere, configuring it through Defaults may just add an unnecessary layer. You will spend time setting up the utility slider without getting any meaningful benefit in return. In that kind of project, it is better to carefully configure the specific slider, test it across browsers, and document what images will be needed for future replacements.

What to Check Before Installation and Activation

Before installing the addon, it is not enough to confirm that WordPress is running. Soliloquy Defaults depends on the core Soliloquy plugin and on the addons available under your license. The official documentation lists license requirements for the Defaults Addon and notes that the available tabs in the utility slider depend on which addons are active. That means preparation starts by confirming that the site already has a working Soliloquy setup and a clear plan for the settings you want to standardize.

It is helpful to split this review into technical, content, and organizational preparation. The technical side answers whether the addon can be installed and function correctly. The content side asks whether you have the images and use cases the sliders are meant for. The organizational side defines who will be allowed to change the utility settings and who is responsible for checking the result.

Technical Preparation

• Make sure the core Soliloquy plugin is installed, activated, and able to create a regular test slider.
• Check whether the Defaults Addon is available under Soliloquy - Addons for your license.
• Update the core plugin and addons through the standard WordPress update flow if the admin panel shows available updates.
• Confirm that the editor who will be creating sliders has permission to work with the Soliloquy post type.
• If the site uses caching, minification, or a separate lazy load optimization layer, prepare a test page in advance that does not receive critical traffic.

You do not need to disable every plugin ahead of time. It is better to check standard Soliloquy first, then activate the Defaults Addon, and only move into targeted troubleshooting if you actually see conflict symptoms. That order preserves the real site environment and helps you avoid false conclusions.

Content Preparation

Sliders often break visually not because of the plugin, but because the images are inconsistent. If one slide is wide, another is vertical, a third is too small, and a fourth has text too close to the edge, no set of default settings will make the result look clean without media preparation. Before configuring Defaults, define a minimum standard: image aspect ratio, safe margins for text, acceptable file size, and a consistent caption style.

For a typical site, it makes sense to prepare 3 to 5 test images with the same aspect ratio, create a temporary page, and test your future baseline configuration there. If the project uses different types of sliders, such as a wide homepage cover and a narrow article slider, do not try to cover both cases with a single utility settings set. Defaults works best for the primary standard, while exceptions should be configured manually after the slider is created.

Permissions and Responsibility

The utility slider affects future sliders, so it is best to limit access to it. If any editor can change Soliloquy Default Settings however they like, new blocks will start behaving unpredictably. On a small team, it is enough to agree that the utility slider is edited by an administrator. In an agency project, it is better to document that rule in the site handoff instructions.

Safe approach: before changing the utility settings set, create a regular test slider, validate the new configuration there, and only then move the confirmed values into Soliloquy Default Settings.

Installing the Addon and Running an Initial Check

The Defaults Addon is installed through the standard Soliloquy addons section. According to the official instructions, you open the WordPress admin panel, go to Soliloquy - Addons, install the required addon, and then activate it. After activation, the slider list should show a utility item called Soliloquy Default Settings. That is the item you need to open for baseline configuration.

If the addon does not appear in the addons section, do not start by manually uploading a random archive from a third-party source. First, check the license, the user role, and the site's connection to Soliloquy updates. Third-party repackaged files may be outdated or modified, and for a production-site workflow, it is safer to rely on the official installation channel.

Installation Order

1. Open the WordPress admin panel while logged in as a user with administrator permissions.
2. Go to Soliloquy - Addons.
3. Find Defaults Addon and click Install if the addon is not installed yet.
4. After installation, click Activate.
5. Return to the Soliloquy list and locate Soliloquy Default Settings.
6. Open this utility slider and confirm that the configuration tabs are available.

At that point, do not rush into creating a production slider. First, you need to understand which tabs are available in your environment. The official documentation emphasizes that the settings tabs depend on active addons. If the site uses Lightbox, Themes, Thumbnails, or other extensions, their settings may appear in the utility slider. If an addon is disabled, its tabs and settings may disappear.

Initial Post-Activation Check

Open Soliloquy Default Settings and do not change anything in the first few moments. Review the screen the same way you would review a normal slider: is there a slide area, settings tabs, a Publish or Update button, and a sidebar code block if it is displayed? The utility slider is not meant to appear on a public page. Its job is to store settings. So do not evaluate it as if it were a finished content block.

Then create a temporary regular slider through Soliloquy - Add New. If the creation interface offers a configuration inheritance choice, select the option tied to Soliloquy Default Settings. Add 2 to 3 test images, save it, and insert the slider on a private or test page. That confirms not only that the addon is active, but that it is actually participating in the real workflow for creating new sliders.

How to Configure the Utility Slider Without Unnecessary Risk

Configuring Soliloquy Defaults should start with one question: what should a normal new slider look like on your site? Not the "most beautiful" version, not the "most feature-packed" version, but the normal one: the slider an editor can safely create multiple times and get a predictable result. That is why your utility settings set should favor calm, stable values.

The official addon logic is simple: open Soliloquy Default Settings, go through the tabs, set the base parameters, and save. The practical challenge is that Soliloquy may show different tabs depending on your license and active addons. So what follows is not a universal list of every field, but a practical decision-making order.

Dimensions and Images

Slider size affects everything: image quality, block height, loading speed, behavior on mobile screens, and how captions appear. If you are unsure, start with the aspect ratio already used in the site's design. For a wide homepage block, that may mean a large horizontal format. For an article or category page, a more moderate height may make sense. Do not set the height too small just to save space, because captions, arrows, and the mobile version can easily become cramped.

Soliloquy documentation includes a setting for adding width and height attributes to images. That is useful for performance requirements and layout stability, especially if the site is sensitive to layout shifts during loading. If that setting is available in your configuration, it is worth testing on a test page: enable it, save, clear the cache, and see whether the slider height stays stable while the page loads.

Cropping and a Consistent Aspect Ratio

Cropping helps keep slide heights consistent, but it can ruin images where the key subject sits near the edge. That is why cropping in Defaults should only be enabled if your team prepares images according to a consistent template. If editors upload random vertical and horizontal photos, it is better to tighten your media standards first rather than trying to compensate for everything with automatic cropping.

The test is simple: add one image with the subject centered, one with text close to the edge, and one with small details to a test slider. If inheritance does not cut off any important part of the slide, the chosen aspect ratio is safe. If it does, either change the size or make the image-preparation instructions stricter.

Navigation, Autoplay, and Speed

A slider should feel controllable. Arrows and dots help users understand that they are not looking at a static image. Autoplay can work well for a promo block, but it becomes annoying in a long article or catalog where the visitor is trying to read captions. That is why you should not enable aggressive autoplay in the default template if sliders will be used in different contexts.

A good compromise for Defaults is to keep navigation clear, choose a moderate transition speed, and avoid changing slides too frequently. If a particular campaign calls for more dynamic behavior, you can configure that later in the specific slider after it has been created.

Theme Settings and Additional Addons

If the site has Soliloquy addons enabled for themes, thumbnails, lightbox, or other modes, their settings may be part of the utility template. This is exactly where it is important not to enable everything "just in case." For example, lightbox makes sense for a photo gallery, but it is not always appropriate for a promo slider that links to pages. Thumbnails are useful for a large image set, but they can overload a small content block.

Only move addon settings into Defaults when they are part of the site's actual standard. If a mode is rarely needed, leave it turned off in the base settings set and enable it manually in the specific slider when necessary.

CSS Class and a Consistent Visual Style

The official tutorial for configuring default settings mentions that you can change configuration and CSS classes inside the utility slider. That is helpful if the site uses a consistent slider style. For example, you can define a class for future promo blocks and style it through the theme's standard Additional CSS area.

Here is a safe example that does not modify plugin files and is easy to roll back:

.site-promo-slider .soliloquy-caption {
  font-size: 16px;
  line-height: 1.45;
}

.site-promo-slider .soliloquy-caption a {
  text-decoration: underline;
}

Where to apply it: add the site-promo-slider class to the slider CSS class field if that field is available in your configuration, and place the CSS in Appearance - Customize - Additional CSS or in a child theme. How to test it: create a new slider with inheritance enabled, insert it on a test page, and make sure the captions changed only for the intended slider. How to roll it back: remove the CSS or remove the class from the slider.

Do not edit Soliloquy files or the active theme just to make a change like this. For small styling adjustments, Additional CSS or a child theme is enough.

Settings Inheritance: How Not to Confuse the Template With a Specific Slider

The most common logical mistake when working with Defaults is to treat the utility slider as a parent that always controls all of its children. In practice, it is safer to think of it as a starter template. A new slider receives the baseline values at creation time, and after that it can be edited as a standalone object. If you later change the utility settings set, you should not assume existing sliders are automatically rebuilt unless that behavior is explicitly confirmed by the interface or the documentation for your version.

This mindset protects you from unpleasant expectations. For example, you configure Defaults, create five promo sliders, then a month later change the transition speed in the utility slider and expect all five blocks to update. If the addon applies settings only as a starting configuration during creation, the old blocks will remain unchanged. That is why important standard changes should be tested on a new slider first, and then you can decide separately whether existing published sliders need to be updated.

How New Slider Creation Works

The official tutorial shows a workflow where, after configuring the utility slider, the user creates a new slider and chooses configuration inheritance through the Inherit Config from field. The Use Soliloquy Default Settings option loads the prepared values, after which you simply give the slider a name, add images, save it, and insert it on the page.

For an editor, that should feel like a clear sequence:

1. Create a new slider through Soliloquy - Add New.
2. Select inheritance from Soliloquy Default Settings if the interface offers that choice.
3. Add images to the slides area.
4. Review the configuration tabs and confirm that the baseline values are already in place.
5. Save the slider and insert it on a test page.

What to Change in the Utility Set and What to Change in a Specific Slider

Only change the standard in the utility settings set. For example, if all future promo sliders should receive a new CSS class, a consistent size, or a shared navigation mode, that belongs in Defaults. If one slider needs to be taller, use different arrows, have a special lightbox, or run at an unusual speed, change only that specific slider.

This distinction is especially important for agencies. When a client says, "make this slider a little slower," you should not immediately change Soliloquy Default Settings. Otherwise, the next promo block created a month later may inherit a private adjustment that was only needed for one page.

Versioning Without a Complex System

In the WordPress admin panel, you do not need a full version log for the utility slider. A simple rule is enough: before any major change, write down which parameters were changed and why in a note or internal document. If new sliders start looking worse afterward, you will quickly know what to roll back.

For a small site, you can use an even simpler approach: create a test slider named something like Defaults Test, apply the new configuration to it, check the public result, and then repeat only the confirmed settings in the utility set.

Practical Scenario: One Promo Slider Standard for Multiple Pages

Imagine a services website or a small catalog where promo sliders regularly appear on the homepage, service pages, and seasonal landing pages. The goal is to make sure every new block has the same height, clear navigation, clean captions, and predictable behavior on mobile screens. At the same time, the content of each slider is different: one page highlights services, another shows case studies, and a third promotes special offers.

Goal

You need to prepare a baseline configuration that will be applied to new promo sliders. The editor should spend time on images and copy, not on repeatedly configuring dimensions, navigation, and behavior. The visitor should see one consistent visual standard across different pages of the site.

Preparation

Before configuring anything, prepare 4 to 5 test images with the same aspect ratio. For a promo block, it is better not to use images with important text right at the edge, because responsive cropping and different screen sizes can hide part of the content. If your slides include captions, decide whether they should be baked into the image or handled as Soliloquy text. Plugin-based captions are easier to update, but they need to be checked for contrast and line wrapping.

Also create a test page that is either excluded from indexing or not linked from the menu. That is where you can insert new sliders and review the result without risking the homepage.

Setup Steps

1. Open Soliloquy Default Settings.
2. On the configuration tab, set the baseline dimensions that fit most promo blocks.
3. Choose calm, clear transition and navigation behavior so the user understands the slider is interactive.
4. If you use a CSS class for promo styling, add it in the appropriate field.
5. Review the tabs for enabled addons and turn on only the modes that are needed in almost all new promo sliders.
6. Click Update or Publish to save the utility settings set.
7. Create a new regular slider and choose inheritance from Soliloquy Default Settings.
8. Add the test images, save the slider, and insert it on the test page.

Result Validation

Open the test page in a normal browser window and then in mobile preview mode. Check more than just whether the slider is present. Look at the details: do all slides share the same height, are faces or product elements being cropped, are captions readable, are arrows visible, is empty space appearing before the slider loads, and does the slider conflict with nearby theme blocks?

Then create a second test slider with a different image set and apply inheritance again. If both results look like part of the same system, Defaults is configured correctly. If the second slider requires a long list of manual fixes, the baseline configuration is too narrow or the images do not match the standard.

Nuance: Different Slider Types on One Site

If the site uses both wide hero sliders and small sliders inside articles, one Defaults setup will not cover both scenarios perfectly. In that case, choose the most common scenario as your baseline. For the secondary type, create a separate internal instruction: which fields to change after inheritance, which sizes to choose, and which modes to disable. Do not try to configure the utility settings set so it is perfect for every case at once. That usually leads to a compromise that works well for no one.

How to Validate the Result After Configuration

Validating Soliloquy Defaults happens on two levels. The first is administrative: the new slider received the expected settings in the interface. The second is public: the slider displays correctly on the page, does not hurt loading speed, and does not conflict with the theme. You need both levels, because the interface may look correct while the page still breaks because of caching, JavaScript, theme CSS, or image optimization.

Administrative Validation

Create a new slider and immediately compare its tabs with Soliloquy Default Settings. You do not need to check every tiny detail if there are many settings. Pick 5 to 7 control parameters: size, image mode, navigation, autoplay, CSS class, and a key lightbox or thumbnail setting if one is used. If those match, inheritance is working.

If one parameter does not carry over, check whether it was actually saved in the utility settings set and whether it belongs to an active addon. Sometimes the problem is not Defaults at all, but the fact that the required addon is disabled or unavailable on the current site.

Public Validation

The public side matters more than it may seem. A slider can look fine in the admin area but end up with a different width because of the theme container, fail to load a script because of an optimizer, flicker on first load, or show static images instead of real transitions. That is why you should test the page the way a normal visitor would see it.

• Open the page both normally and in a private window to rule out the influence of a logged-in admin session.
• Check desktop, tablet, and mobile widths, especially if image cropping is enabled.
• Clear the site and browser cache if optimization tools are in use.
• Open the browser console and check for JavaScript errors related to the slider.
• Confirm that the shortcode, block, or widget is inserted on the intended page.

Checking Speed and Layout Stability

Soliloquy is positioned as a performance-focused slider, but real-world speed depends on more than the plugin itself. Large images, third-party fonts, video, lightbox, multiple sliders on one page, and aggressive animation can all make the result worse. Defaults helps standardize settings, but it does not replace media optimization.

For your baseline template, choose values that let the first slide appear quickly, keep the block height stable, and avoid pushing overly heavy images to mobile screens. If the setting for adding image dimensions is available, test it. If the site uses a separate lazy load optimization layer, pay extra attention to the first slide. In some cases, it makes sense to exclude the first visible slider from third-party lazy loading, but that decision should be based on the site's actual behavior.

Compatibility With Blocks, Shortcodes, Themes, and Caching

Soliloquy can be displayed in multiple ways: through the editor block, the insert button, shortcode, widget area, or a template tag in theme files. Defaults affects the slider's starting settings, but it does not change how the slider is output. That is why troubleshooting needs to separate two questions: was the slider created with the correct configuration, or is the slider failing to display in the chosen location?

Blocks and the WordPress Editor

Official Soliloquy materials mention support for a WordPress editor block. That is a convenient path for editors: select the Soliloquy block, choose the needed slider, and immediately see it as part of the page. If the slider was created through Defaults, the block simply renders the finished object. Make sure the correct slider is selected in the block, especially if several test sliders have similar names.

If the block does not appear in editor search or does not render in the Site Editor, check Soliloquy updates and the core plugin changelog. Recent Soliloquy changes have included fixes related to the block and editor, so for symptoms like this, keeping the core plugin current matters more than reconfiguring Defaults again.

Shortcodes and Widgets

Shortcode remains a reliable insertion method, especially if the page is built with the Classic Editor or inside a builder block that accepts shortcode. After the slider is published, Soliloquy shows the code in a sidebar panel. Use the shortcode itself, not the template tag, when working inside a post or page.

For a widget area, use the Soliloquy widget if it is available. That is more convenient than placing a shortcode inside a Custom HTML block. In both cases, though, Defaults should already have done its job when the slider was created. If the slider does not appear, first verify that the correct ID is being used, then check permissions, cache, and JavaScript errors.

The Theme and the Page Container

The theme can strongly affect how a slider looks: it may limit the container width, add extra spacing, cover the arrows, change link styles, or hide overflow. If a new slider received the correct settings but looks wrong on only one page, the cause is usually the page template or the theme CSS.

A low-risk way to test this is to insert the same slider on a clean test page with a standard template. If it looks fine there, the issue belongs to the specific template or builder section. If the problem repeats everywhere, go back to Soliloquy settings, script conflicts, and optimization.

Caching and JavaScript Optimization

Sliders depend on JavaScript. Caching plugins, script combination, and deferred-loading tools sometimes change the order in which files execute. The Soliloquy support forum includes symptoms such as blank space, static images, slider function errors, or issues after updates. That does not mean Defaults is broken. It may have created the settings correctly while public output was disrupted by optimization.

Safe cache troubleshooting: clear the cache, temporarily disable only JavaScript optimization for the test page, or exclude Soliloquy scripts from combination if your cache plugin supports that. Do not blindly disable half the site while live traffic is running. First reproduce the issue on a test page, then change one parameter at a time.

Helpful Settings for a Stable Workflow

Soliloquy Defaults becomes especially useful when it is supported by a small but clear workflow. Without a process, the utility slider can easily turn into a hidden setting that people only remember after something breaks. Below are practical rules that help keep things organized without adding unnecessary bureaucracy.

Consistent Slider Names

Slider names should help editors distinguish production blocks from test ones. For example, instead of Slider 1, use Promo - Home, Promo - Services, or Case Studies - Landing. The utility slider Soliloquy Default Settings is usually best left unchanged, because it is a recognizable entry point for admins and support staff.

Minimum Pre-Publish Checklist

• The slider was created with inheritance from the utility settings set.
• All images use an appropriate aspect ratio and do not place important text too close to the edge.
• Captions remain readable on a mobile screen.
• The shortcode, block, or widget is inserted in the correct location.
• After clearing the cache, the slider works in a private browser window.
• The console shows no errors related to Soliloquy or the slider scripts.

You can hand this list to an editor. It is short, but it covers most of the issues that are invisible in the admin area. If the editor creates a lot of sliders, a checklist like this will save more time than trying to predict every possible setting in advance.

When to Change Defaults

Change the utility settings set when the site's overall standard changes: a redesign, a new height for promo blocks, a different navigation mode, a decision to disable autoplay for all future sliders, or a move to a new addon set. Do not change it because of one page, one promotion, or one problematic image.

After making a change, create a new test slider and verify inheritance. Do not judge the effect by looking at old sliders unless you are certain they are supposed to update from the utility settings set. This approach removes confusion between "new standard" and "old published block."

When Soliloquy Defaults Is the Right Choice

Soliloquy Defaults is worth using if you have already chosen Soliloquy as your main slider tool and want to reduce manual repetition. Its strength is not flashy animation or a separate visual editor, but a stable starting standard for new sliders. That is especially useful on sites where multiple people work on content or where new promo blocks appear regularly.

Before rolling it out, check the core Soliloquy plugin, confirm addon availability under your license, review the list of active extensions, test slider behavior on a test page, and evaluate the effect of caching. Then configure Soliloquy Default Settings, create a couple of test sliders with inheritance enabled, and make sure the public result matches your expectations.

If the addon solves your use case after testing, you can get the WordPress version and test it in the site's real workflow. Do not start by changing every existing block at once. Start with one new slider and a clear checklist. That will quickly show you whether the addon actually saves time in your project.

The selection criterion is simple: if new sliders are supposed to behave similarly, Soliloquy Defaults helps define that standard. If every slider is unique and built as a standalone design block, it is better to spend time on individual configuration or consider a more visual builder.