Owned development of the agency-designed Lorandus website, proposing Webflow and converting the responsive implementation into a WordPress site with a functioning CMS and blog.
Project Overview
Context and purpose.
Lorandus needed a contemporary responsive website for its meetings and communications business while retaining WordPress as the client’s long-term publishing environment. Another designer supplied the high-fidelity visual direction. I owned the technical path from that static concept through responsive Webflow implementation and into a functioning WordPress CMS and blog.
Objectives
What the project needed to achieve.
Preserve the supplied creative direction while defining how typography, imagery, navigation and branded motion should behave across screen sizes. Build an editable content model and blog, solve the cross-platform delivery path, and ensure the final implementation could be maintained in the client’s required WordPress environment.
The Complexity
The problem, constraints and competing priorities.
The Photoshop composition defined appearance but not responsive behaviour, interactions or CMS structure. I also had to account for the differences between the Webflow implementation environment and the required WordPress/PHP destination. The original Webflow workspace verifies 14 pages and five Blog records. These counts describe implementation scope; they are not traffic, conversion or engagement metrics.


My Role
My responsibilities, ownership and collaboration.
I owned the responsive design translation and development, built the layouts and interactions in Webflow, and resolved the technical issues involved in converting the implementation into WordPress. I used Udesly for the conversion step, then addressed CMS, blog and front-end behaviour so the delivered experience remained editable and usable in the client’s preferred platform. The original visual design remained the work of the supplying designer.

The Pivotal Decision
The options, trade-offs and reasoning behind the key choice.
I proposed using Webflow as the implementation environment before the required WordPress delivery. That gave the project a clearer bridge for responsive design translation: I could resolve layout and interaction behaviour in a visual front-end environment first, then carry the working structure into the client’s CMS instead of interpreting a static composition directly inside WordPress. The trade-off was additional conversion QA, but it produced a stronger path from design intent to WordPress and CMS delivery.
The Outcome
What was delivered and the impact it made.
The delivered work combined responsive presentation, branded interactions and an editable WordPress CMS and blog. The original Webflow source verifies the breadth of the implementation, but a trustworthy numerical measure of traffic, conversion or engagement has not been recovered. This case is therefore strongest as evidence of cross-platform engineering, responsive judgement and CMS delivery rather than as a metrics story.


Reflection & Next Steps
How this work shaped my product design approach.
Lorandus strengthened my judgement about when the delivery platform should shape design and implementation decisions. Reproducing a composition was only part of the work; the more important challenge was preserving the creative direction while making it responsive, editable and technically viable in a different production environment. If I revisited the project today, I would validate the content model and conversion path earlier, add automated visual-regression checks across breakpoints, and document CMS editing tasks so maintainability could be evaluated as deliberately as the front-end experience.

