Project Pulse
A healthcare-AI website where I worked with more advanced Rive interactions, CMS-driven layouts, motion, and a custom integration that brought the client's Shopify store into the Webflow experience.
Another alias joins the collection. The company name stays offstage; the things I built do not.
Build notes
More advanced Rive interactions
Partner logo marquee
CMS-driven content
Stacking highlighted-work layout
Custom Shopify integration
Dedicated merch experience
The project
Healthcare AI, with a lot happening underneath.
The website is for a healthcare AI platform focused on automating operational workflows, so the site needed to communicate a fairly technical product without feeling overly dense.
My work was on the Webflow implementation and the pieces around it: interactive Rive assets, CMS content, motion, custom layouts, and functionality that needed more than Webflow's native tools.
And then there was the merch page.
The highlight
And then Webflow met Shopify.
The client had a Shopify store. The website had a merch page. Those two things needed to feel like they belonged together.
Instead of treating the merch section as a completely separate experience, I used custom code to integrate the client's Shopify setup with the Webflow site.
That meant working outside the normal Webflow-only workflow and figuring out how the two systems could work together while keeping the experience visually connected to the rest of the website.
This was less “find the right Webflow element” and more “okay, these two systems need to talk now.”
Webflow
The website experience
Layout, styling, interaction, and the surrounding merch experience.
Shopify
The commerce side
The client's existing store and product infrastructure.
Rive, round two
This time, the interactions got more involved.
I'd already worked with Rive before this project, but here the interactions were more complex.
By this point, I was getting more comfortable working with Rive inside Webflow and thinking about the animations as functional pieces of the interface rather than something that simply plays on the page.
Less “how do I put this in Webflow?” and more “how should this actually behave?”
CMS + layout
CMS, but make it editorial.
The highlighted work section was CMS-driven, but I didn't want it to read like a normal repeating grid.
I built it with mixed image heights, overlay text, and an intentionally uneven rhythm so the content feels more like a curated gallery wall than a standard collection list.
Structured underneath. A little chaotic on purpose on top.
Highlighted work
CMS item
Story
Another highlight
Feature
CMS item
Elsewhere in the build
Not everything needed to be the main character.
Rive, round two
Worked with more involved Rive interactions and got more comfortable treating animation as part of the interface rather than a decorative extra.
Partner marquee
Built a continuously moving logo marquee for the partnership section while keeping the motion clean and secondary to the content.
CMS-driven content
Used Webflow CMS for content that needed to stay manageable and reusable instead of hard-coding every entry into the page.
Stacking grid
Built the highlighted-work section with a stacked visual treatment, giving CMS-driven content a more designed and interactive presentation.
What I took from it
Sometimes the website is only one piece of the system.
This project pushed me further into thinking beyond the Webflow canvas itself.
Between more involved Rive interactions, CMS-driven layouts, and connecting Shopify through custom code, I was working with several different pieces that still had to feel like one website to the person using it.
Webflow was still home base. It just had neighbors now.
End note