Being trusted by a platform you have built your agency around is a different kind of validation. It is also a different kind of responsibility.

Why Webflow called us

In 2021, Eclipse became the first Italian agency to receive official recognition as a Webflow Expert Agency. That milestone was not just a badge. It opened a different kind of relationship with Webflow, one where we were seen as a technical partner rather than just a user of the platform.

When Webflow needed a team to build and maintain an official WordPress plugin, they came to us. The reason was specific: our background.

Before Eclipse was a Webflow agency, we were a WordPress agency. We did not switch platforms because WordPress was unfamiliar or difficult. We switched because Webflow served our clients better. But the years spent building seriously in WordPress, understanding its plugin architecture, its hooks system, its admin UX conventions, the way the ecosystem works at a technical level, meant we were one of the few Webflow partners who could credibly operate on both sides of this project.

What the Webflow Pages plugin does

The Webflow Pages plugin bridges two platforms that millions of teams use separately and often wish they could use together.

The problem it solves is real: many businesses rely on WordPress for content management, editorial workflows, and the plugin ecosystem that surrounds it, but want Webflow's design capabilities for their pages. Before this plugin existed, the only options were compromise on one side or invest in custom development to build the bridge yourself.

The plugin makes it possible to design pages visually in Webflow and publish them directly into a WordPress site, without code, without custom integrations, without choosing one platform over the other.

What we built and how

Webflow entrusted Eclipse with the full scope of the project: technical architecture, plugin development, UX design for the WordPress admin interface, and long-term maintenance.

The architecture work was where our dual-platform background paid off most directly. Building something that needs to work reliably across the enormous variety of WordPress environments, different hosting configurations, different theme setups, different plugin combinations, requires a specific kind of defensive engineering. You cannot assume a clean environment. You build for the messy reality of how WordPress sites actually exist in the world.

The admin interface design was equally important. The users of this plugin are not developers. They are designers, marketers, and content teams who need to authenticate, select pages, and sync content with minimal friction. The interface needed to feel native to WordPress while connecting to Webflow's API in a way that was transparent and trustworthy.

We also handled the submission and compliance review process for the WordPress Plugin Directory, which has its own set of requirements and standards that need to be met before a plugin is publicly listed.

What the collaboration looked like

Working directly with Webflow's internal product and engineering teams was an experience that sharpened how we think about product development.

The Webflow team is precise about requirements and equally precise about user experience standards. Conversations about API usage, feature scope, and edge cases were substantive. We were not handed a spec and left to implement it. We were in an ongoing dialogue about what the right solution looked like, which is the kind of collaboration that produces better work than either side would produce alone.

Our WordPress expertise gave us standing in those conversations. We could push back on assumptions about how WordPress environments behave, advocate for approaches that would work across the full range of real-world deployments, and flag edge cases that might not be visible from inside Webflow's infrastructure.

What this means for Eclipse

The Webflow Pages plugin is publicly available on the WordPress Plugin Directory and continues to grow its user base. We maintain it actively, keeping it compatible as both platforms evolve.

For Eclipse, this project is a concrete answer to a question clients occasionally ask: how do we know you really understand both platforms? We built the official bridge between them. That is the answer.

Read more about our migration services and how we help teams move between platforms.