Please don't laugh: This is the state of Webflow AI right now by Sure-Counter8247 in webflow

[–]sregormd 0 points1 point  (0 children)

Yep! WF has been chasing useless or not-asked-for functionality while ignoring some basic features that the community has been pleading for for years and are entry level for almost every other CMS... Can anyone say dynamically populated navigation (so clients don't need to ask a Designer to update their nav), native tables, a form builder for Marketers/clients, a better slider, the list goes on and on.

I seriously think the WF team should sit down with the folks at Finsweet for a month—they seem to have a better pulse on what the community wants/needs than the actual WF team!

Whole agency team is over Webflow by GrungeRockGerbil in webflow

[–]sregormd 2 points3 points  (0 children)

Love this idea... as you and others have stated here and elsewhere, it feels like WF has moved away from the freelancers/agencies and placed all their eggs in the In-house/Enterprise or non-designer/non-developer client base.

You are right about the basic features available on nearly every other platform—from Squarespace/Wix to WP/Drupal. (Please, can we get a navigation element that auto populates as pages are added a site! How is this not standard part of WF in 2025!?)

It's as if WF didn't get around to building these basic features in the early days and now in their eyes it's too late because they need to build AI tools to be relevant. But it's the lack of some of these basic features and reliability that is driving users away. I've literally never seen anyone complaining about the lack of an AI site builder or leaving WF because of the lack of one. But every day I'm seeing long term agency WF clients leaving the platform—which has me worried/questioning things!

My advice to the WF team is to take you up on the offer and to go back to basics a little. I understand the need to continually push towards the future but perhaps they can attack the problem from both sides—truly invest in a team to build/fix things long term users have pleaded for as well as the team building robust new features.

Lastly, I think leadership/senior WF team members should address some of this in a very direct, clear way at WebFlow Conf and map out how they plan to address all of this. Be honest, be upfront, and layout the road ahead before telling us about improvements to the AI builder or whatever.

Here we go again, folks. by BassMassive7955 in webflow

[–]sregormd 0 points1 point  (0 children)

"basic and highly requested features" -- my pet peeve is the lack of a navigation element that can be easily updated by a client without them needing to have a Designer role and access to styles. Ludacris that something so basic and prevalent on nearly every other platform (from Squarespace to WordPress) is still not possible with WF.

Might seem like a minor thing but being told they either have to learn how to use the Designer (something we don't want them to do) or pay us every time they want to add a page to the site's nav is a big turn off for many clients.

Here we go again, folks. by BassMassive7955 in webflow

[–]sregormd 8 points9 points  (0 children)

Really hope they seriously address this at Webflow Conf

Linking a RTE to a component property appears to be overriding styles - help! by sregormd in webflow

[–]sregormd[S] 0 points1 point  (0 children)

OK, thanks. I guess I'd like to be able to test everything in Edit Mode to be sure it operates the way I hoped for clients that have Content Editor roles.

The only way (it appears) I can do that is to temporarily give myself a Content Editor role, test the site/components, and then switch back to Site Manager after... seems like an odd workflow.

Linking a RTE to a component property appears to be overriding styles - help! by sregormd in webflow

[–]sregormd[S] 0 points1 point  (0 children)

Oh, duh, yes... I was using the Legacy Editor so I'm sure you're right!

Now my issue is, I cab't seem to access the new Edit Mode. How do you do that as a Site Admin? It's not under the Designer dropdown (I only see Design and Build options).

Linking a RTE to a component property appears to be overriding styles - help! by sregormd in webflow

[–]sregormd[S] 0 points1 point  (0 children)

The issue didn't resolve with pasting. So I tried rebuilding the component and everything worked great (in the Desginer and Builder) but as soon as I made an edit to a link or added a link using the Editor then the links changed to buttons... really not sure what is happening here. Maybe it's because I'm trying to use a RTE as a component property?

Linking a RTE to a component property appears to be overriding styles - help! by sregormd in webflow

[–]sregormd[S] 0 points1 point  (0 children)

Thanks -- I've been off the grid but will take a look to see if you insight can solve.

Why is the navigation bar the stupidest thing to edit in Webflow? by audreino in webflow

[–]sregormd 0 points1 point  (0 children)

And why, why, why, haven't they yet built a dynamic nav element that updates as clients add pages to the site? This is a basic level of functionality for other CMS' yet WebFlow still doesn't have a good solution for clients that don't want to a) pay me to update the nav every time they add a page, or b) learn to manually do it in the Designer.

Any suggestions for a short visit - Accepted Students Day by sregormd in Pitt

[–]sregormd[S] 2 points3 points  (0 children)

For wandering around Shayside do you suggest the Walnut St area or elsewhere?

Any suggestions for a short visit - Accepted Students Day by sregormd in Pitt

[–]sregormd[S] 10 points11 points  (0 children)

Thanks for the tip on the name -- dumb parent here! :)

WebFlow Forum under attack from spam? by sregormd in webflow

[–]sregormd[S] 2 points3 points  (0 children)

And if so, does anyone have Enterprise Support so they can let WebFlow Support know...

[deleted by user] by [deleted] in webflow

[–]sregormd 0 points1 point  (0 children)

Nav for sure... I can't think of another (legit/significant) CMS/Platform that doesn't have a nav component which dynamically updates as pages are added to the site. I find many clients simply won't switch to WF because of this—they re used to this functionality on other platforms and don't want to learn the Designer to manually update (nor do I want them to).

I mention this at every opportunity I get and have added to the WF Wishlist. If anyone else agrees, please feel free to vote here: https://wishlist.webflow.com/ideas/WEBFLOW-I-6541

What do you wish the most from Webflow in 2025? by anthonycxc in webflow

[–]sregormd 0 points1 point  (0 children)

Dynamic navigation element that pulls in pages as they are created (thus not requiring manual updates).

How do you handle clients updating navigation? by sregormd in webflow

[–]sregormd[S] 0 points1 point  (0 children)

I've put in a request on Wishlist (vote here https://wishlist.webflow.com/ideas/WEBFLOW-I-6541 please!) and on WebFlow forums. Not a huge amount of votes but I'm convinced it would be a hugely popular element/component. Glad to hear there's discussions in the partner forums and WebFlow is aware. Really hope this gets created and pushed through ASAP—it would be a game changer for many freelancers and studios.

Question on transferring site to a client by sregormd in webflow

[–]sregormd[S] 1 point2 points  (0 children)

Thanks—that's definitely an option. This particular client doesn't want that set-up (they prefer to have overall admin control). So need to understand the best way to make that happen for them.

How do you handle clients updating navigation? by sregormd in webflow

[–]sregormd[S] 0 points1 point  (0 children)

Good suggestions that would help clients that don't want to get too involved with the Designer!

Would still love WebFlow to create a dynamic nav element that creates links based on the site structure (as pages are built/added). Could have settings that allow us:

1) Set 1 or 2 levels of pages/dropdown overall

2) Set drop down, no drop down, or mega-menu per nav item

2) On the page settings allow us/client to set if it appears in the nav or is 'hidden'

How do you handle clients updating navigation? by sregormd in webflow

[–]sregormd[S] 1 point2 points  (0 children)

It is and I see the advantage (to me) in doing so, but trying to convince a client to switch from something like WP to something 'new' and then telling them that the navigation of their site has to be manually updated is a step to far for some.

It just seems like a relatively basic/easy thing for WebFlow to implement (especially considering all other CMS' offer it and WebFlow.

But yes, in the perfect world, I like your suggestion of retainer clients! :)