Directory Platform / Enterprise Webflow CMS
BALAM required more than designing individual pages.
I worked on the product as a scalable travel platform where destinations, listings, editorial content and multilingual experiences needed to live inside one consistent system.
THE CHALLENGE
Travel platforms contain very different kinds of content. A visitor may move between destination information, restaurants, experiences, editorial articles and other local recommendations while still expecting the product to feel like one coherent experience. Behind that interface is another challenge: the client needs to keep publishing and managing that content without rebuilding pages manually every time something changes. BALAM therefore couldn't be approached as a collection of static marketing pages. The design and the CMS architecture had to work together.
DESIGNING A SYSTEM, NOT INDIVIDUAL PAGES
I approached BALAM as a reusable product system. Instead of designing every content type independently, I established a consistent visual and interaction language that could extend across different parts of the platform. Hierarchy, navigation, content structures and reusable UI patterns were designed around the way users explore a destination. That allowed the product to grow while still feeling visually connected.
CMS ARCHITECTURE
A major part of the development work was structuring content so the site could scale without requiring new static pages for every addition. Webflow CMS became the content layer behind the platform. Reusable templates allow structured content to be published consistently while giving editors control over individual entries. Relationships between content also make it possible to connect relevant places and editorial material instead of treating every page as an isolated endpoint. This was especially important for a travel platform, where discovery depends on moving naturally between related content.
EDITORIAL CONTENT
BALAM also includes an editorial layer designed to support deeper destination discovery. Articles can combine structured metadata, imagery, long-form content, relevant listings and supporting sections while remaining manageable through the CMS. Rather than building each article manually in Webflow, the system was designed so new editorial content can use the existing content structure. That creates a publishing workflow rather than another page-building task.
MULTILINGUAL EXPERIENCE
The platform needed to work across languages while maintaining the same content hierarchy and visual experience. Localization therefore had to be considered as part of the CMS and development architecture rather than added as an afterthought. Content structures, metadata and page relationships were built with multilingual publishing in mind. The goal was for localized content to remain part of the same product system rather than becoming a collection of disconnected duplicate pages.
DESIGN + DEVELOPMENT IN ONE PROCESS
Because I handled both design and Webflow development, decisions weren't made in isolation. The interface could be designed around the actual CMS structure, and the CMS structure could be adapted around the content experience. That reduced the gap that often appears when a design is handed to development without considering how real content will behave. Responsive behavior, reusable components, content templates and CMS relationships were considered as parts of the same system.
BUILT FOR CONTINUED GROWTH
The architecture was created around the assumption that BALAM would continue changing after launch. New listings can be added. New editorial content can be published. Existing content can be updated. The platform can expand without redesigning the underlying experience every time the content library grows. That was one of the central goals of the project: build something the client can continue operating rather than a site that remains dependent on its original designer for every update.
ONGOING PRODUCT DEVELOPMENT
BALAM continued evolving after the initial launch. As new content, SEO requirements and product ideas appeared, I worked on extending the existing system rather than rebuilding it around every new request. That required understanding how changes affect the broader CMS, navigation and user experience instead of treating each request as an isolated page edit. The project became an example of long-term product thinking inside Webflow.
THE RESULT
BALAM became a scalable CMS-driven platform rather than a collection of static travel pages. The final system combines: Product and UX design Responsive Webflow development Reusable components Structured CMS content Editorial publishing Content relationships Localization SEO-ready content structures The project shows the other side of my development work. Not every complex system needs to become a custom application. Sometimes the right solution is designing the architecture carefully enough that a platform can remain flexible, manageable and scalable inside Webflow.