Uzo Okafor — Webflow Development Partner

Slack message from project manager asking about potential scope increase for team photo edits and bios not included in original project scope

PM sent this last week. Client wanted team photo edits mid-project - wasn’t in scope.

PM flagged it right away. Just checking, no drama.

That’s the move. Scope creep happens. Address it immediately.

Flag new work clearly. Clients appreciate transparency over surprises.

Slack message from client thanking team for bringing vision to life in 2 weeks, noting positive reviews at the event.

Full rebrand in 2 weeks. New domain, design, messaging across site + socials.

Client had an event deadline. Team executed: designer + CD on visuals, PM coordinating, dev.

Launched on time. Already getting positive feedback.

Tight timelines work when everyone’s aligned.

#WebflowDevelopment

Client had a project video they wanted visitors to see immediately.

Built it so the video takes over the full screen on page load, then transitions smoothly into the hero section. GSAP for the animation, matchMedia to handle mobile.

Clean way to give the video attention.

#WebflowDevelopment #GSAP

Designers put careful thought into grid systems and spacing. Matching that precision in development isn't optional for me.

One thing I do that clients don't always see: I use a grid overlay during builds.

#WebflowDevelopment #WebDesign #FrontendDevelopment

Everything shipped on schedule. Both clients were happy with how it went.

The key wasn't juggling faster. It was being upfront about the timeline so no one was wondering where their project stood.

I messaged both teams as soon as I realised it. Told the first agency's founder I'd have their build wrapped by thursday, then move to the second project's revisions. Let the second agency's designer know exactly when I'd start addressing their feedback.

Had two projects overlap last week. Different agencies, different clients.

One was finishing up the build phase, the other was in revisions. Timelines were going to overlap no matter what.

Let me check alignment as I build instead of eyeballing spacing or going back and forth between Figma and the browser.

Small tool, but it makes a difference. Matching design intent exactly is how you build trust with design teams.

Single-element, CSS background trick. It creates a visual grid that mirrors the Figma layout so I can see exactly where elements should sit.

I toggle it on and off with Shift+G.

Designers put careful thought into grid systems and spacing. Matching that precision in development isn't optional for me.

One thing I do that clients don't always see: I use a grid overlay during builds.

#WebflowDevelopment #WebDesign #FrontendDevelopment

First thing I tried: adjusting grid settings. Then column widths. Then checked if it was a CMS limit issue. Nothing worked. With fewer items, the grid was perfect.

Turns out it wasn't Webflow. It was a CSS Grid sizing behaviour.

The fix: min-width: 0 on the grid children.

Then I increased the CMS limit from 9 items to 40+. The grid completely broke. Columns were no longer of equal width. Some items stretched wider than others. The whole layout felt random.

Code snippet showing CSS fix for Webflow CMS grid layout issue: grid child selector with min-width property set to 0

Hit a weird grid bug last week while building a blog page in Webflow. Looked like a platform issue, but it wasn't.

Set up a CMS Collection List as a 3-column grid. Everything looked fine at first. Grid items were evenly spaced, and columns stayed consistent.

Code snippet showing CSS solution for modal layout shift: html selector with scrollbar-gutter set to stable, and body.modal-open selector with overflow set to hidden

Ran into an annoying bug last week while building a modal for a client site.

Every time the modal opened, the page would shift horizontally by about 15px. The navbar especially. It would visibly jump left whenever the modal appeared.

Yeah, max-width: 100vw is solid for horizontal overflow issues. This case was about locking scroll for modals without causing the page to shift when the scrollbar disappears. Different fix for a different problem.

Yeah, scrollbar-width: none works if you want to hide it entirely.

A client I built a site for last year reached out in December during the holidays.

Their users were getting frustrated with some of the scroll animations. People wanted more control over the navigation instead of being forced through scroll-triggered interactions.

Small thing I do on every Webflow project: add help text to CMS fields.

It's a feature most people skip, but it makes a big difference for clients. When they're adding a blog post or uploading an image, they see instructions right there in the field. No guessing, no reaching out to ask.

Code in the screenshot. Simple fix, makes modals feel way more polished.

#WebflowDevelopment #FrontendDevelopment #WebDevelopment

Worked sometimes, but was inconsistent across browsers and viewports.

Then I found scrollbar-gutter: stable. One line of CSS. Reserves the space for the scrollbar at all times, even when it's hidden. No shift, no JavaScript needed.

The cause: when you add overflow: hidden to lock scroll, the scrollbar disappears. That frees up the space it was taking, and everything shifts to fill it.

Tried a few JavaScript fixes to calculate the scrollbar width and compensate with padding.

Code snippet showing CSS solution for modal layout shift: html selector with scrollbar-gutter set to stable, and body.modal-open selector with overflow set to hidden

Ran into an annoying bug last week while building a modal for a client site.

Every time the modal opened, the page would shift horizontally by about 15px. The navbar especially. It would visibly jump left whenever the modal appeared.

For images, I'll add notes about file size and format. For text fields, I'll explain heading structure or character limits.

A client once mentioned how helpful their marketing team found it. Made the CMS feel accessible instead of confusing.

#webflowdeveloper #webflowpartner #marketingteam

Small thing I do on every Webflow project: add help text to CMS fields.

It's a feature most people skip, but it makes a big difference for clients. When they're adding a blog post or uploading an image, they see instructions right there in the field. No guessing, no reaching out to ask.

Took less than two hours to get everything working. They were happy with the turnaround.

Sites evolve based on how people actually use them. Being available to make those adjustments when they come up just makes sense

#webflowdeveloper #webflowpartner #designservices

So we simplified it. I removed the scroll triggers causing problems and turned the Build Process section into something clickable (video attached). Now users can move through at their own pace instead of scrolling to advance.

A client I built a site for last year reached out in December during the holidays.

Their users were getting frustrated with some of the scroll animations. People wanted more control over the navigation instead of being forced through scroll-triggered interactions.

Worked with an agency last year where we had to pause development three times because content wasn't ready. The build itself took four days. But the project stretched to six weeks.

The build quality is the same either way. But one finishes on time and the other doesn't.

#webflowdeveloper #agency

Other projects take longer not because the work is harder, but because I'm waiting on answers. Designs are across multiple files. Content's scattered between Slack threads and Google Docs. No one's quite sure which version is final.

Best projects I've worked on all have one thing in common.

The agency sends over everything organized before I start building. Figma files labeled. Content in one place. Style guide included.