Some weeks are about planning. This one leaned hard toward shipping—a personal brand site that finally went live, a community-health site getting ready to speak more than one language, and a long list of small refinements that turn “almost done” into “ready for the public.” Here’s where the team landed.
A Personal Brand Site Goes Live
The personal brand half of our dual-site transformation for a wellness practice and its founder launched this week. After months of strategy, design, and development—and one carefully timed final review—we flipped the switch.
A personal brand site sounds simple until you build one. There’s the writing, which has to sound exactly like the person and not at all like marketing copy. There’s the visual identity, which has to feel cohesive with the related practice but distinct enough to stand on its own. And there’s the integration—how does this site point to the practice without competing with it, and how does the practice point back without feeling like an afterthought?
We worked through all of it. The personal site is live now, and the practice site is right behind it, in stakeholder review. More on that next.
Learn about our Complete Website Transformation →
Juggling Stakeholder Priorities and Applying a Whole Lot of Polish
The companion to that personal brand launch is the larger practice site—the one that has to introduce a whole team of health care professionals, not just the founder. This week we completed bio pages for team members and pushed the staging environment to the team for a critical review window.
Bios are deceptively tricky. Each one is a small portrait: who this person is, who they help, how they work, and what specific approaches they bring. Multiply that by nine, get the tone consistent across all of them without flattening anyone’s voice, and then make sure the page design supports both quick scanning and deeper reading. That’s where most of the week went.
We also worked through a long list of design refinements that came out of the last client review—larger body copy, tighter card layouts, a reorganized nav, better contrast on the search interactions, and a new taxonomy treatment for the practitioner directory. None of it is glamorous. All of it adds up to a site that feels finished.
Explore our Complete Website Transformation →
Building a Community Site That Speaks Two Languages
A community health organization we’ve been working with is approaching launch, and this week was about making sure the site is ready for the people who actually need it. That meant two big pieces of work: a Spanish-language layer wired into every page, and a full accessibility audit ahead of go-live.
The translation layer is more than a switcher in the header. It’s a content infrastructure choice—how every page, every form, every navigation label gets served in either language without breaking the layout or the SEO. We wired the language switcher into the site’s translation system and started flowing real content (and real imagery) into the staging build for the service pages: support for moms, support for partners, support for families, and the community programs that connect all three.
On the accessibility side, we ran a full performance-and-accessibility audit across the local build, started the WCAG compliance pass, and flagged the items that need to clear before launch. If your site is built to help families navigate a hard moment, the bar for inclusive design is higher, not lower.
Learn about our Content Operations work →
Quiet Operations Work for an Enterprise Content Client
Not every win is a launch. Some weeks the most valuable thing we do for a client is keep the trains running—triage defects across releases, coordinate cookie-consent infrastructure, plan around team PTO, and make sure nothing important falls between sprints.
That was a meaningful chunk of the week for one of our enterprise content clients. We worked through the defect list with the QA team and split it across the current and next release. We coordinated with their privacy-compliance partner on cookie-preference behavior. We responded to a routine security scan that flagged a handful of items for review. And we mapped out coverage for an upcoming PTO window so the project doesn’t stall while a key person is out.
This is the part of long-running engagements that doesn’t show up in case studies. It’s also the part that determines whether your platform team trusts you when the bigger asks come.
See how our UX Helpdesk supports enterprise teams →
That’s the week: a personal brand site live, a practice site in final review, a multilingual community site approaching launch, and a steady hand on a long-running enterprise project. If you’re getting close to your own launch—or wondering whether you’re closer than you think—let’s talk.
