B2C
Headless CMS
AI Prototyping
Mobile/Web
Shipped
Sollis Health is a concierge healthcare company offering premium medical care to its members. I designed the reusable components behind its new website, built on the Directus headless CMS.
Role
Research, Designing, AI prototyping, QA
Team
• Lead Designer (me)
• Lead Analyst x1
• Engineers x2
• Product Manager x1
• Content Specialist x2
Platforms
Directus CMS,
Desktop & Mobile Web
Impact
• Publishing times slashed from 3 weeks to 10 minutes
• 17.5% increase in blog engagement
• 165.6% increase in average engagement time for Locations page
DESIGN PREVIEW
Locations page
Blog homepage
BACKGROUND
The website was due for a massive overhaul
Sollis Health’s website had grown over the years and outgrown the platform it was built on. To support a push for organic growth and engagement, three bottlenecks needed to be solved:
🗓️
Any website updates required engineer assistance, often taking up to 3 weeks.
🧩
Blog articles were standalone pages with no proper metadata and no supporting architecture.
🔍
Locations page was highly-trafficked but lacked strong conversion points relative to that volume.
In early 2026, Sollis greenlit a major rebuild of the website, including a move from WordPress to Directus, a modern headless CMS. As lead designer, my objective was to:
OBJECTIVE
Create flexible, robust components that elevate the site’s visual design, support engagement, and let content teams move quickly and independently.
BLOG REDESIGN
A blog that wasn't really a blog
The old blog homepage (left) and the old blog article page (right).
Sollis’s articles were built as standalone pages, without consistent authors, dates, categories, or a blog-specific URL structure. That limited SEO and search, and every change went through an engineering queue that could take up to three weeks. A visual refresh wouldn’t fix that, so we rebuilt the blog on a structured content model.
Together with engineering, analytics and content, we defined the fields every article needs and the type of components that would be most useful. Taking those considerations into account, I designed and iterated on the components until they were ready to be built and loaded into the CMS.
By incorporating the components into the new blog architecture, articles are given proper room to shine across both web and mobile, and new content can easily be added through the CMS.
Writers used to be limited to plain text and headings. Now they can build richer articles from 9 components, including embedded images, callouts, and mid-page CTAs, all without needing to create an engineering ticket.
LOCATIONS PAGE
Mapping a better Locations page
The old Locations page.
The Locations page is the second most visited page on the site, a directory of Sollis’s 14 clinics across the U.S. It had the same dependency on engineering as the blog, and its design didn’t show what made each location worth visiting.
Working with Analytics and Customer Success, we defined and prioritized the information each location needed to show. I then designed reusable, customizable components that adapt across desktop and mobile.
LOCATIONS PAGE
Prototyping with Claude Code
I used Claude Code to build a live prototype that combined my Figma components with the Google Maps API. After configuring the map in Google Cloud Console, I added features one at a time:
Brand-matched map colors
Hiding unnecessary map details (restaurants, landmarks, etc.)
A custom Sollis location pin
Clustering for nearby locations (especially in Manhattan)
Linked interactions between the list and the map
With 85% of traffic coming from mobile, the experience needed to be designed for phones, not shrunk down from desktop. On mobile, visitors switch between a list view and a map view instead of seeing both side by side.
By the end of the design process, I handed engineering the working prototype as a reference, along with the map style JSON. They modeled the production build on the prototype and shipped the map styling unchanged.
OUTCOMES
Impact
In the months after launch, the redesigned sections showed clear gains:
• Publishing times slashed from 3 weeks to 10 minutes
• 17.5% increase in blog engagement
• 165.6% increase in average engagement time for Locations page
Balancing flexibility with constraints
Testing components with different configurations and real content showed that more customization isn’t always better. Without limits, a long title could break the layout on small screens, or an oversized image could crowd the elements around it. I refined these limits through testing and conversations with stakeholders about what they actually needed, and compromised where it made sense. On future CMS work, I’d define constraints earlier to keep projects on track and catch edge cases sooner.
