> ## Documentation Index > Fetch the complete documentation index at: https://vr-it-services-pro.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > Which plugins Vara SaaS expects, which are optional, and how to avoid bloat. # Recommended plugins # Recommended plugins Vara SaaS works on its own. These are the plugins it knows about, what each is for, and what happens if you skip it. ## The two the theme manages These are the plugins the setup wizard knows how to install. > **[Elementor](/integrations/elementor.md)** > > **Required for the demo pages.** The fastest way to build landing pages, and what the four imported layouts are built with. The wizard installs and activates it for you. > **[Contact Form 7](/integrations/contact-form-7.md)** > > **Required for the demo contact page.** A lightweight block-friendly form plugin. The Contact page layout contains a Contact Form 7 shortcode. > [!WARNING] > > **The demo Contact page will render a broken shortcode without Contact Form 7**, and even with the plugin installed it references a form ID from another site. You must create a form and re-insert it. The exact steps are on the [Contact Form 7](/integrations/contact-form-7.md) page. ## Strongly recommended, not required These aren't managed by the wizard, but each fills a gap the theme deliberately leaves open. > **A caching plugin** > > **WP Super Cache, LiteSpeed Cache, or W3 Total Cache.** The theme optimises its own assets well, but nothing caches HTML output. On a shared host this is usually the single biggest speed win available to you. > **An SEO plugin** > > **Yoast SEO or Rank Math.** The theme outputs Open Graph tags and a minimal `WebSite` schema, but that is not a substitute for title templates, XML sitemaps, or per-post metadata. See [SEO](/performance/seo.md). > **An image optimisation plugin** > > **ShortPixel, Imagify, or Smush.** The theme serves native WordPress images and does not compress or resize them. See [Performance](/performance/optimization.md). > **A security plugin** > > **Wordfence, Sucuri, or Solid Security.** Login protection, firewalling, and malware scanning. None of this is theme functionality. ## Useful additions > **A menu or navigation plugin** > > Only if you need a megamenu or conditional menus. The theme's own menu handles nested dropdowns several levels deep, keyboard navigation, and viewport-aware flipping. See [Header and menus](/customization/header-and-menus.md). > **A form plugin with richer fields** > > If Contact Form 7 is too limited, the theme styles its fields consistently, but the feature set comes from the plugin. Alternatives: WPForms, Ninja Forms, Formidable. > **An analytics plugin** > > The theme does not track anything and makes no third-party requests by default. Any analytics you add is entirely your choice and entirely under your control. > **A translation plugin** > > Only needed for a non-English site. Arabic translation files ship with the theme. See [Localisation](#localisation) below. ## Plugins the theme is careful around The theme detects page builders other than Elementor so it steps aside for them. If you use one of these, Vara SaaS will not add its own container or title to the page. | Plugin | How the theme detects it | | - | - | | Beaver Builder | `_fl_builder_data` meta, `FLBuilderModel` class | | Divi | `_et_pb_use_builder` meta, `et_fb` query argument | | Bricks | `_bricks_page_content_2` meta, `bricks` query argument | See [Other page builders](/integrations/other-builders.md) for the details and the caveats. > [!WARNING] > > Only **Elementor** has deep integration — brand colors are written into its global palette. With Beaver Builder, Divi, or Bricks, the theme still steps aside for layout, but your brand colors are not injected into that builder's global settings. Set them in the builder itself. ## What the theme will not conflict with You can safely use these without expecting theme-level conflicts: * **Gutenberg blocks** — `theme.json` supplies the palette, fonts, and sizes. See [Block editor](/integrations/block-editor.md) * **Contact Form 7** and other block-based form plugins * **Yoast SEO, Rank Math, and All in One SEO** — the theme's output is limited to Open Graph tags, a theme-color meta, and one JSON-LD block, which all three handle without duplicating * **Comment plugins** — the theme uses WordPress's own threaded comments at depth 100 * **Translation plugins** — the text domain is `vara-saas` throughout ## Avoiding bloat A short, honest performance note. The theme is lean on its own — no tracking, no external font requests, no dashboard widgets, no admin page bloat. A typical Vara SaaS install loads roughly: * One main stylesheet * One small dynamic-vars stylesheet * One portfolio/theme stylesheet * One self-hosted font stylesheet * Font Awesome * Plus one conditional stylesheet on blog and single views * Two small deferred JavaScript files Everything beyond that is your plugins. Ten well-behaved plugins will always beat three heavyweight ones, and adding a plugin for a feature you use once a year is usually a bad trade. **Before adding a plugin** Ask: does the theme already do this? If not, is the plugin lightweight and actively maintained? Does it inject a third-party script on every page? Would a small snippet in a child theme be less weight? See [Child themes](/developers/child-themes.md). ## Localisation The theme uses the text domain `vara-saas` and ships with an **Arabic** translation already compiled. Translations live at [translate.wordpress.org/projects/wp-themes/vara-saas](https://translate.wordpress.org/projects/wp-themes/vara-saas), where anyone can contribute or download a language pack. > [!NOTE] > > If you find an untranslated string, the `.pot` catalogue in the theme is currently incomplete. Report it on the [support forum](https://wordpress.org/support/theme/vara-saas/) and it will be regenerated in a future release. ## Next steps > **[Run the setup wizard](/introduction/setup-wizard.md)** > > Installs Elementor and imports the demo pages in one pass. > **[Plugin compatibility](/integrations/plugin-compatibility.md)** > > How to test a plugin against the theme before committing to it. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.