Skip to content

Corrigan Companies

The Corrigan family of companies runs its websites as one WordPress multisite with a shared theme. It has grown to 11 sites, five of them live. I am its lead developer, and I have worked on it since May 2024 alongside several other developers: I wrote the development scope, set up the environments and most of the sites, moved the network onto new servers twice, launched four of the five live sites, and have had a hand in every launch.

  • Role Lead developer
  • Agency Perfect Afternoon
  • Network 11 sites, 5 live
  • Years 2024–2026
  • Work Scope · Environments · Servers · Launches
  • Stack WordPress · Multisite · DNS · Performance
The Corrigan Oil Co. home page, under a Corrigan Family of Companies bar: blue fuel tanker trucks behind the headline Treating customers like family since 1958, with a Call 1-800-FAST-OIL button

The network

One WordPress multisite with one shared theme runs the corporate site and the family’s companies: Corrigan Oil, Corrigan Propane, Corrigan Towing & Heavy Haul, Corrigan Global Logistics, Corrigan Climate Solutions, Corrigan Mechanical Contractors, Technical Environmental Services, Blue Water Industrial Products, Corrigan Environmental Solutions and Corrigan Construction. By mid-2026 five of them were live: Oil, Propane, Towing & Heavy Haul, Global Logistics and Climate Solutions.

In May 2024 I wrote the development scope that turned the approved Figma design into build instructions for the network’s first theme and blocks, and I was in the development handoff meeting. The rest of this page is my own part of that work. The screenshot and the link above are Corrigan Oil, the most recent launch.

Setup

Environments and servers

  • Development environment, 2024. Added development domains for the corporate site and six company sites, set up SSL certificates for them, and mapped four of them into the network.
  • Email. Prepared the sending-domain DNS records (SPF, DKIM, MX and a tracking CNAME) for three of the domains, provided them for the client’s IT team, and re-checked them until they validated.
  • A new server, February 2025. Moved the network’s hosting account, with the whole multisite, to a new server ahead of the first production launch.
  • Staging, March 2025. Moved the corporate site to its new domain across development, staging and production, and set up staging copies of the corporate, Global Logistics and Towing sites.
  • A dedicated server, June 2025. I set it up with the agency’s in-house DevOps person and the hosting provider. I worked with the client and the host’s support team on the server’s specification, then set up the server with backups, configured the sites on it, compiled the DNS changes for all 18 site addresses (5 production, 4 staging, 9 development), and moved every site onto it in a live working session with the client’s team. Afterwards I checked that every site and subdomain resolved and worked, and had the host review the server’s configuration.
  • The rest of the family, June 2025. Set up development sites for eight of the network’s sites, the corporate site among them, from the Towing site’s template, four of them on newly added domains.
  • Upkeep, 2026. Full backups, files and databases, of the five production sites and the development network, and WordPress core and plugin updates across production, staging and development.

Launches

Four sites I launched

  • January and February 2025

    Corrigan Global Logistics

    The one-page site, and the move to production

    I set up the one-page site on the shared theme, starting from the Towing site’s template, and fixed the theme along the way: anchor links now reach the front end for every block, which fixed the main navigation, the header and footer links scroll smoothly to each section, and the mobile menu closes after a tap. Before launch I backed up production and development and moved every site in the network to production, where each could be checked through local DNS overrides before any public DNS changed. At launch I set up the deployment pipelines.

  • April to June 2025

    Corrigan Climate Solutions

    Changes during the client’s beta, then the launch

    During the beta I fixed the network-wide Family of Companies overlay so its logo and close button sit together on one line, and shipped the fix to every Corrigan site, extended the Category Cards block so editors can pick a product category or write the card by hand, and adjusted the Content Cards block. For the launch I set up the production site, worked through the pre-launch checklist, specified the DNS records for the client’s IT team, built the staging copy from production, and added the accessiBe accessibility script.

  • February 2026

    Corrigan Propane

    Launch, reCAPTCHA and a performance audit

    In the internal beta I fixed child blocks that could not be repeated inside their parent blocks. At launch I specified the DNS records, launched the site, set up its staging copy, added it to uptime monitoring, and put invisible reCAPTCHA v3 on every form. After launch I ran GTmetrix and PageSpeed Insights audits on desktop and mobile and wrote up recommended fixes for image sizing, script loading and accessibility.

  • April and May 2026

    Corrigan Oil

    Responsive fixes in the beta, then forms and the launch

    During the client’s beta I fixed heading line breaks, a home page image that did not show on mobile, the footer styles, the mobile navigation breakpoint and card heading backgrounds. For the launch I set up four Gravity Forms admin notifications, for the contact and quote forms split by residential or commercial customers with the contact reason in the subject line, then specified the DNS changes, launched the site and installed accessiBe. After launch I made form confirmations larger and scroll into view across the network, and fixed the photo gallery by excluding its scripts from the JavaScript delay.

Performance and theme

Alongside the launches

  • Lighthouse on Global Logistics, April and May 2025. Turned on JavaScript delay and defer and unused CSS removal in WP Rocket, lazy loaded images in WP Rocket and EWWW with the hero image excluded, fixed a mobile caching bug that kept WP Rocket’s settings from applying, moved the Adobe Typekit fonts into the theme, dropped unused social share scripts and styles, and replaced bare anchor tags with labeled elements. Together those cleared the render-blocking resources finding.
  • One theme across the sites. Carried the pre-launch changes from the Propane site to the Oil, Mechanical Contractors and corporate development sites, and later applied the Oil site’s styles, with its three-panel footer call to action, to Blue Water Industrial Products.
  • The mobile top bar. Restored the light blue top bar on mobile across the live sites and the builds in progress, reworked its responsive layout, and resolved the merge conflicts with a new development branch in the theme repository to deploy it.

Questions about this work?

I am happy to go into the multisite in more detail. nathanpaulgamache@gmail.com

Ask me about it