Case study
Compounding Content Feed
A subscription library of patient education content that compounding pharmacies embed on their own websites, whatever those sites are built on.
- My role
- Designed and built it solo in 2018. It has been licensed to pharmacy websites ever since.
- Built with
- Headless WordPress, WordPress REST API, JavaScript, PHP
- Status
- In production since 2018
The problem
Compounding pharmacies need clear education content on their websites, but few have anyone to write and maintain it. Their sites also run on different platforms, so anything shared had to work on plain HTML as well as WordPress.
What I decided
Keep one central library of about 20 content sections and let any website embed a section with a two-line snippet. The script pulls the content over the REST API, splits it into tabs, and takes on the host site's fonts so it looks native.
Licensing is checked by domain, so an unlicensed site shows a subscription notice instead of the content. US, Australian and Canadian editions localize medical spelling automatically.
Where it stands
One update to the library reaches every licensed pharmacy at once. The domain licensing check later became the starting point for the agency's licensing platform.