




















Hospital content needs to be understood as a connected set of public tasks. We review the directories and existing destinations, develop representative journeys and design the templates before building the Webflow site. Content migration and any technical connections are defined against the actual estate.
We review the service directory, specialist information, hospital sites and public resources. Your team identifies the current booking, referral and patient-service destinations, alongside the content owners and material that needs updating before migration.
Design reviews follow representative tasks, such as finding a specialist or planning an arrival. We show department, profile and visitor layouts with actual information, including how the navigation and maps behave on a phone.
We implement the agreed public pages and CMS relationships in Webflow. Service, specialist and location records are connected as specified, while external bookings, portals and other hospital systems retain their defined role in the journey.
We test sample patient, visitor and referrer journeys, including directory links and practical contact details. Mobile navigation, document destinations and the wording around external services are checked alongside your team’s review of the final content.
The handover covers the agreed website, design files and routine directory updates. We explain how staff maintain related records and practical information, with clear guidance about the content each team is responsible for keeping current.


