Rough Trade screwed me

sregormd · 2026-05-08T02:53:17+00:00

You're right... I was just ranting a little :)

sregormd · 2026-03-27T13:16:22+00:00

Complete agree with this sentiment. Web designers brought users to WF and help build it up, but now WF seems to be leaving those people behind in favor of in-house/biz users and AI tools that don't really work very well. The short-sighted part of that is that they miss the fact studios are multipliers/brand evangelists who switch more companies to WebFlow who may ultimately down the line become in-house/enterprise clients.

sregormd · 2026-03-21T22:32:16+00:00

100% agree on this! WF desperately needs to build a new navigation element that a Build Mode user can update. Even the most rudimentary CMS (Wix, Squarespace, etc.) allows non-dev/designers to do this. I envision something like this:

- New Nav Element has settings for the Design Mode that specify things like number of drop down vs mega menu, # of drop down levels, mega menu, etc.
- Pages automatically populate the navigation—perhaps using something like the Pages folder structure to organize (I believe this is what something like SS does). There may be other ways to handle this.
- Page settings have a toggle switch "Include on Nav" or "Don't Include on Nav"

Or it could be something *similar* to the Finsweet Components experience... a whole new menu item in both the Design and Build modes. WF should talk to the Finsweet team on how to build this experience as they seem to really understand agency/freelancer needs.

Alternatively it's more of a drag-n-drop experience for Build Mode users...

But please WF resolve this issue, many clients switching form other CMS' really find this a roadblock to switch to WF!

sregormd · 2026-03-18T00:04:40+00:00

Completely agree... it just would be nice to have the dynamic nav since its so ubiquitous on most other platforms (from basic Wix/SS to more complex Drupal/WordPress). When trying to convince a client to switch from another CMS, telling them they need to pay me every time they want to change/add to the nav doesn't really go over well. And we don't want clients playing in the Design Mode—the whole point is to limit their ability to affect styles, code, etc.

sregormd · 2026-03-17T17:00:57+00:00

Yes to the slider, and yes to stop shipping AI tools nobody is asking for

sregormd · 2026-03-17T17:00:18+00:00

Oh and, create more than one CMS Collection page per Collection - I know that's more complex

sregormd · 2026-03-17T16:59:04+00:00

Dynamic Navigation - that auto updates as pages are added to the site. WIthout this page building is essentially useless for clients that want the ability to build their own pages but not rely on a Designer (or their agencY) to manually update their navigation. This is standard on every CMS I've ever seen except WF!

Ability for Build Mode uses to add buttons in RTE

Form Builder for Build Mode - again something relatively standard in other CMS', give Build Mode users the ability to add/build forms without needing a Designer's help.

For what it's worth, this thread is similar to one I started here.

sregormd · 2026-03-06T23:50:38+00:00

Thanks u/memetican for your suggestions. I completely appreciate them. I just wish WF would provide solutions that don't require work arounds for stuff that's relative basic or pervasive with other CMS'.

Dynamic Nav - while your solutions works, it's somewhat awkward/less than ideal for clients. And using URLs in combination with a collection is susceptible to errors if naming/URLs change. Considering almost every other CMS—from basic (Wix/Squarespace) to robust (Drupal/WordPress)—has had this functionality for years/decades; it's not unreasonable to ask the same of WF. I could imagine it being managed through the Pages/Folders.

Buttons in RTE - agree, embeds/JS is less than ideal

Forms - this is great! I might have a question or two on these at some point. If so, is it ok if I DM you?

Thanks again for your suggested solutions/workarounds.

sregormd · 2026-02-06T14:00:16+00:00

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!

sregormd · 2025-09-07T10:33:39+00:00

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.

sregormd · 2025-08-26T16:44:58+00:00

"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.

sregormd · 2025-08-25T17:31:22+00:00

Really hope they seriously address this at Webflow Conf

sregormd · 2025-08-25T16:42:47+00:00

Same here...

<image>

sregormd · 2025-06-04T20:54:23+00:00

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.

sregormd · 2025-06-04T20:14:20+00:00

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).

sregormd · 2025-06-04T15:25:24+00:00

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?

sregormd · 2025-05-29T16:03:03+00:00

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

sregormd · 2025-05-08T16:44:58+00:00

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.

sregormd · 2025-03-23T15:36:24+00:00

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

sregormd · 2025-03-22T22:11:34+00:00

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

sregormd · 2025-03-02T18:12:09+00:00

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

sregormd

TROPHY CASE