WebFlow Development
Sites editors can change
We design and build in Webflow: marketing and content sites whose pages, CMS collections, and interactions a non-developer can update, with custom code limited to the spots the Designer cannot cover.
What we build with Webflow
Webflow is a visual builder with a real CMS and a publish model. The work is the content structure and the class system, not a screenshot turned into a single long page.
Marketing and campaign sites
Landing pages, product marketing, and campaign sections are built in the Designer against your brand styles. Components and classes are named so a second page reuses them instead of duplicating a pile of overrides.
Interactions stay purposeful: a state change a visitor can follow, not a chain of timelines nobody can edit later.
CMS collections
Articles, locations, people, or project pages become collections with fields an editor understands. Reference fields connect related items. The template is built once and bound to those fields, including the empty state.
We decide which pages are static and which are CMS items before visual polish, so a new entry does not require a designer.
Forms, embeds, and the edge of the Designer
Native Webflow forms cover the common lead and contact flows. When a form has to talk to a system Webflow does not know, we add a custom embed or a small script and we document what it sends.
Memberships, localization, and ecommerce are used when the project needs them. They are project settings with an editorial consequence, so we set them up with the person who will publish, not only in a preview link.
Publishing and performance
Assets are sized for the layout. Fonts and third-party scripts are listed. We check the published site, not only the Designer canvas, including the CMS template at a phone width.
A Webflow site can sit next to a web development property. We say which URLs belong in Webflow and which belong in an application.
Typical use cases
Webflow is a strong fit when marketers and editors need to publish without a deploy, and the site does not have to behave like a product application.
A company site with a few templates
Home, a handful of product pages, and a CMS for news or resources. Editors add items. Designers change a component. Engineers are not in the loop for a headline.
Campaign pages on a shared style
A launch needs a page this week and another next month. We build the sections as reusable components so the next campaign is an assembly, not a new file.
A content collection with relationships
Authors, categories, and articles, or offices and regions. The collection fields match the way the team files the content, including the fields that are required before publish.
A visual site that still needs one custom behavior
A calculator, a gated asset, or a script from another product. We embed that piece and keep the rest of the page in Webflow, so the custom code has an edge.
How we work
Webflow projects are won or lost in the CMS and the class names. Visual design follows that structure.
Model the collections first
We list the item types, the fields, and who is allowed to edit them. Static pages are named separately. A field that only exists to force a layout is removed before build.
Build components, then pages
Classes and components land before the long pages. A new section reuses them. Overrides are the exception, and they are named so the next editor can see them.
Add custom code in a marked place
Embeds and site-level scripts are written down: what they do, which page they load on, and what breaks if they are removed. The Designer remains the place editors work.
Hand over the Editor
We walk through publishing, CMS items, and the components editors may change. The preview link is not the handover. The handover is an editor publishing a real item.
Bring the pages and who will edit them
We will map those pages onto static layouts and CMS collections, and we will mark anything that needs custom code.
Why OLIANT
Webflow at OLIANT is a site an editor can publish, with custom code kept at the edge.
Collections before decoration
Fields and templates are decided first. A new CMS item fills a page that was built for it.
Classes a second person can read
Components and class names stay consistent, so the next campaign does not fork the design system by accident.
Custom code is listed
Every embed has a reason and a page. Editors are not left to discover a script by breaking a layout.
Frequently asked questions
Questions to settle before a Webflow build.
No. Both let editors publish, and the editing models differ. Webflow designs and content live in Webflow's hosting and CMS. WordPress is PHP, themes, and plugins on a host you control. We use each where it fits, and we do not rebuild one inside the other.
Yes. That is the point of the Editor and the CMS. We set roles, required fields, and components so an editor can publish an item or change a section without opening the full Designer.
We add a bounded embed or connect the form to another system, and we write down the dependency. If the site is becoming an application, with accounts, complex state, and its own data rules, we move that part to custom development instead of stretching the Designer.
We can rebuild the pages and import content into collections when the content maps cleanly onto fields. A pixel-by-pixel copy of a site that depends on a custom application is a different project, and we will separate the marketing pages from the application URLs.
A Webflow site with an editor in mind
Share the page list and who will publish. We will come back with the collections, the components, and the custom code we would avoid.