Quorum

The challenge

Quorum sells one idea: when a server fails, boot it from the recovery copy in minutes instead of waiting hours for a restore. Its buyers are IT leaders comparing backup, high availability, DRaaS, and clean-room recovery, often in the middle of a ransomware scare, and the vocabulary gets dense fast.

The site had to do three jobs at once. Make the product legible to a buyer who is still learning the category, give search engines real depth on the terms those buyers look up, and carry forward years of white papers and guides whose links already live in other people’s bookmarks and search results.

A site the team can own

We built on WordPress with the Avada builder so Quorum’s marketing team edits pages visually, and kept every Quorum-specific behavior in a versioned child theme and small purpose-built plugins rather than in the parent theme or the database. Upgrading Avada never overwrites the work, and every change is reviewable in Git.

Product pages cover the onQ family (Flex, Cloud, Appliance, and Cloud-to-Cloud), and seven solution pages break the offer down by the problem a buyer is actually trying to solve: disaster recovery, high availability, DRaaS, direct-to-cloud, cloud protection, ransomware recovery, and clean-room recovery.

A glossary that links itself

Recovery buyers search for terms like RTO, immutability, and logical air gap before they search for vendors. Quorum publishes a glossary entry for each, and we wrote a plugin that links those terms wherever they appear across the site, automatically.

It reads the glossary at render time, so a new entry starts linking the moment it is published. It matches longest phrase first, treats acronyms like DR and HA as case-sensitive so ordinary words are never caught, skips headings, buttons, code, and existing links, and never links a page to itself. It edits only the text between tags, so the builder’s markup passes through untouched.

Keeping the archive alive

Quorum’s white papers had lived at /resource/ URLs for years, while the new site files posts under /resources/. Rather than redirect every paper, we taught WordPress both patterns: posts in the White Papers category keep their original singular URLs, and everything else uses the new structure. Retired pages like the standalone white paper index permanently redirect to their live replacements.

Each paper sits behind a HubSpot download form, restyled inside its frame to match the site, so every download is captured in HubSpot. Six long-form recovery guides (ransomware, VMware, healthcare, a buyer’s guide, and two comparisons) carry hand-written titles and descriptions for search.

Details that usually get skipped

Avada’s desktop mega menus do not translate to a phone, so we rebuilt mobile navigation from the same menu data: real buttons that report whether their submenu is open, one submenu at a time, and the Escape key closes the menu and returns focus to its toggle. Critical header styles print before first paint so tablet widths never flash both header layouts.

The 404 page points lost visitors to onQ, ransomware recovery, and business continuity instead of a dead end. And a small must-use plugin keeps Avada’s compiled font and icon URLs portable, rebuilding its caches once per environment, so the same codebase moves between local, staging, and production on Kinsta without broken icons.

Google PageSpeed Insights