Super Tech Hero logoSuper Tech Hero

Untangling a web of websites

FVTA certifies veterinary technicians across Florida, and its online presence was spread across a WordPress site, a Wild Apricot member portal, payment pages, standalone conference pages and leftover copies, with no one owning the whole thing. Super Tech Hero mapped it, put together an A-Team that knows every piece, and gave each site one clear job.

Tech partner and team lead, on an ongoing retainer

Meet the client

A credentialing body where every broken link has a cost

The Florida Veterinary Technician Association (FVTA) is a volunteer-run nonprofit that credentials Certified Veterinary Technicians and represents more than 2,500 technicians. Florida doesn’t regulate the credential, so there are two credentialing bodies, and technicians choose which one to go through.

That makes the website more than a brochure. Applications, renewals, late renewals and amnesty all run through it. As FVTA’s certification co-chair put it when members kept finding the wrong information online: “It could also mean we lose members entirely as they have the choice to choose which association they want to credential with.”

1 of 2credentialing bodies in Florida, so friction sends members elsewhere
5+ placesa member could land, each with its own login, text and rules
1 teamthat now owns every one of them
How it came together

From five sites and no owner to one team that owns them all

  • Map
  • Team
  • Settle in
  • Untangle
  • Continuity
  1. MapEvery place a member could land, mapped
  2. TeamA Wild Apricot specialist, hand-picked
  3. TeamA playbook and a quality bar
  4. Settle inBackups, access and the real host found
  5. MapFix now, rebuild later, on purpose
  6. UntangleEach site gets one clear job
  7. UntangleThe iPhone loop on every application, fixed
  8. ContinuityReady for the next board, on a retainer
Discovery · The real problem

Not one website, but a web of them

On the kickoff call, the picture came into focus fast. As Jennifer put it to the team: “We kind of have this weird two-website straddle here.” And it was more than two.

The previous developer had built a WordPress site because he couldn’t make Wild Apricot look modern, then linked it to Wild Apricot for anything involving members. When he couldn’t get new certification events to connect, he copied old ones and changed the dates, so applicants saw the wrong year in the headings. A renewal link stayed open past its deadline. The Donate link had been turned into conference registration. The same text lived on the Wild Apricot homepage, the WordPress pages and each program page, so one change meant three edits.

The people running it were volunteers with day jobs. The real problem wasn’t any single bug. It was that nobody owned the whole map.

Most of the breakage lived in the gaps between sites.

  • thefvta.net · WordPressBefore20+ pages locked inside the theme’s code, so “Edit page” showed a blank screen. An outdated PHP version, untested backups, and an events calendar left untouched.NowThe public front door: backed up daily and weekly with a tested restore, upgraded to PHP 8.2, 20 plugins inventoried, a new Career Center.
  • Wild Apricot · member portalBeforeCertification “events” copied year to year with old dates, a renewal link open past its deadline, an expired New Graduate link, and a button that dumped people on every registration at once.NowMembers and certifications only, with evergreen copy, links that stay open by the rules, and the catch-all page hidden.
  • Embedded forms · the bridgeBeforeWild Apricot forms framed inside WordPress pages, which Apple’s browsers quietly block, trapping iPhone and iPad users in a loop.NowA clear button on every application page and the member login that opens the secure form directly.
  • AffiniPay · conference pagesBeforeConference registration run through a repurposed Donate link and an image used as a button.NowDedicated sponsorship and attendee pages that take payment directly, with no accounts for sponsors to create.
  • Leftover copiesBeforeAn old /sponsors page with no payment button, so every edit had to be made twice.NowCaught and flagged for retirement, with a redirect so old links still land on the current page.
  • Hosting, domain and emailBeforeThe site sat on the previous developer’s account, sold under another name, with shared passwords.NowGoDaddy hosting FVTA owns, delegate access instead of shared passwords, and every login documented.
  • Search and word of mouthBeforeThe site didn’t come up unless you typed the full address, live CE events lived only on Facebook, and inaccurate information filled the gap.NowGoogle Analytics in place, a homepage search cleanup scoped, and a Google Business Profile underway.
Every place a member could land, what was wrong with it, and the one job it does now.
Team · Expertise

Putting the A-Team together

A web of sites needs people who understand every piece and the seams between them. Wild Apricot is a niche platform, and the last developer’s unfamiliarity with it was the root of most of the workarounds. So before taking on the work, Jennifer went looking for the right partner. Her note to him: “I’m taking over a WildApricot + WordPress site and want to put the right team in place for support.”

She found Peter, a longtime Wild Apricot partner who also knows WordPress well. She ran a second round of interviews with one other strong candidate, and chose Peter for the fit, including working hours that line up with Florida.

The split is deliberate. Jennifer owns strategy, the client relationship and quality. Peter builds on both platforms. And there are always two people who know the account, so nothing depends on one person.

The right specialist, chosen on purpose, not whoever is available.

Team · Standards

Prepping the team before day one, and holding the bar

Before Peter touched anything, Jennifer gave him the recordings of every call and the full task list, and walked him through how Super Tech Hero works, so FVTA would get one standard from everyone on the team.

The playbook held up in practice. When an announcement banner covered the menu on phones, Jennifer caught it and flagged that issues should be found before the client hears “all set.” When an email went out under another company’s name, she corrected it: everything FVTA sees carries the Super Tech Hero name. Hours came to her first, so the board got one clear summary each month instead of a stream of invoices.

One standard, one voice, whoever is doing the work.

  • Client owns itHosting, files and the work belong to FVTA.
  • Simple firstMaintainable fixes over custom builds.
  • Checked before it shipsIssues are caught before the client hears “all set.”
  • On the recordRecorded calls and a running log of decisions.
  • A steady rhythmA monthly summary for the board and a quarterly checklist.
  • One voiceEvery email, invite and guide comes from Super Tech Hero.
The playbook Jennifer set before the work began.
Handoff · Security

Getting settled in, safely

The handoff with the previous developer confirmed what the team suspected: no test copy of the site, plugins no one could explain, a member sync that was a black box even to him, and documentation that never arrived. So the team stopped waiting and planned around it.

The work was laid out in four phases, starting with what everything else depends on. A full backup came first, then a schedule of daily database backups and weekly file backups to FVTA’s own Google Drive, with a restore tested to prove they work. Reading the backup logs revealed the site’s real host. The “separate” hosting account was actually GoDaddy, which FVTA already owned. Access moved to delegate logins instead of shared passwords, and the old developer came off every form.

Before anything new, make sure nothing can be lost.

  1. FoundationBackups, a site audit, analytics and Search Console
  2. Quick winsClean up forms, buttons, sponsor logos and links
  3. InfrastructureHosting, PHP and plugin updates, the job board
  4. ContentEvents, board page, nominations, a quarterly checklist
Judgment · Strategy

Fix the toilet, or redo the bathroom?

With two platforms causing so much friction, there was a real case for collapsing everything into one. The specialist’s instinct was to move it all onto Wild Apricot. Jennifer’s question was about timing: “When do you want to keep fixing your toilet instead of redoing the bathroom?”

Her call was to understand the site before choosing a path, avoid pouring money into something that might be replaced, and not rebuild anything in the middle of a conference season. So the team stabilized what FVTA had, and laid the bigger choice out for the board to make with real information, timed for after the conference.

Fix what’s urgent now. Make the big decision once, with the facts in hand.

  • 1 · New designA full redesign and rebuild of the public site.
  • 2 · Same look, modern codeKeep the design, move every page into the editor, and run on current PHP.
  • 3 · One platformConsolidate membership, events and the website into a single system.
Three scoped paths for the board, after the conference, with no pressure to choose mid-season.
Systems · Cost

Giving each site one clear job

Instead of two platforms doing overlapping work, each one got a clear role. Wild Apricot keeps what it’s built for: members, certifications and renewals. WordPress is the public front door.

The conference was the test. The first draft put sponsorship inside Wild Apricot, and FVTA’s conference lead raised a fair concern: sponsor contacts change every year, and making them create accounts would add friction and fill the member database with inactive contacts. So the sponsorship and attendee pages were built on the public site in the brochure’s look, with payment through the AffiniPay account FVTA already used. That kept the conference outside FVTA’s Wild Apricot plan and its contact limits.

The job board followed the same logic. FVTA wanted it on the main site, on brand and in the menu. The new Career Center lets employers post for free with no account, holds every listing for approval, removes listings after 90 days, and has built-in spam protection.

Two platforms are fine when each one has a clear job.

Wild ApricotMembers and certifications
  • Member database and login
  • Applications, renewals, late renewals and amnesty
  • Newsletters
thefvta.netThe public front door
  • Pages, board and news
  • Conference sponsorship and attendee registration, paid through AffiniPay
  • Career Center job board
A clear line between the two platforms, so each one does what it does best.
Members · Results

The seam members could feel

From the first call, the team had described members getting bounced back and forth when they tried to log in or renew. Then one applicant’s report finally pinned it down. The application pages showed the Wild Apricot form inside a frame on the WordPress site, and Apple’s browsers block what that form needs to work. Anyone on an iPhone or iPad got stuck in a loop.

It turned out to be every application page (New to Florida, Recent Graduate, Renewal, Late Renewal, Student Membership and Amnesty) plus the member login. Each now opens the secure form directly, on every device. FVTA’s response: “What a relief… It [was] an awful experience during the previous renewal.”

The worst problems hide in the seams between systems.

Continuity · Governance

Ready for the next board

A volunteer board turns over, and FVTA’s president was preparing to hand off leadership. His goal was simple: make sure the next team has what it needs. With the systems mapped, that was possible.

Every login across the website, hosting and plugins was gathered for the president’s handoff document, along with a plugin list noting what each one does and which carry licenses. New officers were added with the right level of access, and the corresponding secretary was set up to approve job postings himself. A board transition kit, with an access review across Wild Apricot, WordPress, GoDaddy and Microsoft 365, has been scoped for the next handoff.

The site shouldn’t depend on who happens to be on the board.

Partnership · Retainer

A retainer built around a team, not hours

Getting settled in took more monthly hours, and the board approved a temporary increase as long as it got a short monthly report of how the hours were used. Once the big projects shipped (sponsorship, conference registration, the homepage banner, the Career Center and the board portraits), the retainer was right-sized to a smaller monthly minimum.

When the board later asked about cost, Jennifer reframed it: “You’re not paying for hours; you’re paying to retain a carefully curated team built around FVTA’s specific needs.” Instead of chasing developers or working out whether an issue belongs in WordPress or Wild Apricot, FVTA has one team that already knows the setup. FVTA’s president called it “exactly what I needed to help facilitate a conversation with the rest of the board.”

Next up is getting found, the same gap that let misinformation spread: a homepage search cleanup and a Google Business Profile.

You’re not paying for hours. You’re retaining a team.