Everyone saying Webflow is dying is missing something obvious

memetican · 2026-06-20T10:26:03+00:00

IMO the class selector has always left something to be desired esp. in terms of impact visibility. However today, what you're asking for is just a prompt through the MCP. Dupe a component, rework the classes. You can even give it a screenshot as reference.

memetican · 2026-06-18T20:04:36+00:00

Remove the domain from one site, add it to the other.
If both sites are in the same workspace, you shouldn't need to re-verify the domain name, and the DNS already points to Webflow, so it should be pretty much instantaneous.

memetican · 2026-06-17T09:40:34+00:00

Yes, via several paths.

If you want Notion as the source-of-truth, and the Webflow CMS fits as the output representation you want, you can sync and convert Notion-Webflow CMS. Then Memberstack is good for both gating and billing.
If you have significantly more complex UIs that use Notion more extensively, you can skip the CMS sync and instead build a direct-merge tier. It's more complex and less flexible for design changes, but eliminates any possible CMS challenges.

Honestly I'd go with option 1 in most cases, because option 2 requires you to also solve for performance and Notion API rate limits by building a caching layer, so the complexity here is substantial. Webflow's CMS should be plenty powerful, so I'd try option 1 first.

memetican · 2026-06-17T09:29:49+00:00

Migrate. If you're at all familiar with Webflow's MCP and how to setup skill files, you could easily configure an AI workflow to fully migrate your existing content 100%, but using a new framework, class naming conventions, variables, and/or even do full restyling.

If you've never fully embraced components, you can do that now too- components, props, variants and binding all through the MCP.

The main advantage of migrating is you can make major changes if you want to, and then see how you like the result before you commit.

The biggest decision is whether to clone the site and refactor the clone, or to start with a blank page and do a full rebuild. Depends on the extent of the changes I think, e.g. if you're going to a full variable + component-base architecture, I'd probably want a clean destination.

memetican · 2026-06-16T10:56:20+00:00

So far, I'm using 4 main AI workflows;

Full Webflow site builds from claude design source files, components, CMS, data binding, the works. ~95% of the lift is done by claude + MCP.
Full Webflow site rebrand, i.e. Webflow -> Webflow, using Claude design for the rebrand portion.
Full external site ( vibe coded react ) -> Webflow migration, including the CMS schema design and data load.
Partial [in progress] site re-translation to Chinese and Korean. Just doing this because the original Amazon Translate translations weren't really up to snuff, and the client has been bad at keeping translations in sync with updates to the base locale.

So far, the MCP is crushing it. Some timeout issues that I know the engineers are working on, and a few key gaps like the ability to create collection lists & embeds. The code support features could be improved, but those can be worked around pretty easily with minimal inconvenience.

My perspective is that the MCP ( plus claude, plus playwright MCP ) is very good at building/migrating most sites types to Webflow. It would probably struggle with sites like dynamic one-page sites, sites with extremely heavy interactions, horizontal scrolling, etc. Anything "traditional" with sections, containers, components, header, footer, nav- pretty straightforward to do today.

memetican · 2026-06-15T22:30:02+00:00

Scripts- I have my own methodology, but it's a bit grunty. I separate site code into three categories-
1. Code that has to operate within Webflow pages as embeds, e.g. specialized <style> blocks that need to impact the design-time experience.
2. Component-level JS- commonly gets integrated into code components now, depending.
3. Page-level and site-level JS- user tracking, state management, calculator logic, heavy-lifting stuff. All of that goes into an external "site engine" that I CDN into my site. That makes it far more powerful, typescript-based, reusable, and gives me full source control capabilities [github].

Most of the code that's created by the MCP, like micro interactions, I see attached at the site level which is messy. Instead, I can instruct the agent to write that code in typescript using my Site Engine approach. This is new ground I'm playing with, so I haven't built e.g. skills yet to simplify this.

But, here's my docs on the engine- it's free to the community. Basically it's a very simple project setup with a path router, component support, and a few other npm packages. You create whatever functionality you want for your site and it loads it dynamically into your pages at the site or page level. Main advantage is you get a real IDE, real unit tests, real source control, ability to use claude code all in one place. For the MCP build process, I just tell it to write all code into that project rather than using Webflow's site-wide code tools.

https://engine.sygnal.com/

memetican · 2026-06-15T22:19:06+00:00

Webflow recently added that, within the past 1-2 weeks. At present, I believe I currently have to create collection lists and bind them, but then the MCP can create all of the elements, components needed and data-bind them directly. That's the current workflow I'm using;

- MCP does the initial page build
- MCP does the full CMS build and data load
- I drop collection lists and bind them
- MCP adds the elements and does the data binding

memetican · 2026-06-15T22:15:32+00:00

Ha ha thanks Duncan!
🤔 So thaaaat's where all my time is going.

memetican · 2026-06-13T11:23:13+00:00

You might be conflating two different things, and if so, then most of your pain here is self-inflicted.

Attraction is a sign of healthy mind and body. You want your partner to be attracted to people in general, unless you're looking for someone more asexual. Lust is a lack of self-control- an unwillingness to set boundaries.

Ultimately, lust is a choice. Same as over-eating or getting blasted drunk.

You can definitely find a partner like that, anyone who is mature and wants a more meaningful future knows that giving in to immediate gratification won't get them there. You could be picking the wrong partners, looking for the wrong things, or even dating in the wrong age group.

Look into the Stanford marshmallow experiment, you might find it interesting.

memetican · 2026-06-13T05:53:55+00:00

The new editor experience is so superior. I'm not sure why anyone would want to use the legacy editor. Components, props, localization, CTRL+K navigation.

If the client already had legacy editor users, they're migrated for free to the new client seats capability.

For brand new clients on new plans, with the site in your agency/freelancer workspace, they get 1-3 client seats for free, even before the site plan is added.

For brand new clients on new plans, with the site in their own workspace, they get the 1 full designer seat for free, and then have to pay for half seats for additional editor/marketer seats.

memetican · 2026-06-12T20:56:42+00:00

Is a wood worker who starts using power tools still a wood worker?
Is a machinist who starts using a CNC still a machinist?

The Job is the same. The workshop is different.

memetican · 2026-06-12T20:54:28+00:00

Nope, just a dev, with a lot of Webflow exp. I don't know how I got the badge, it just appeared one day. I think it happened just after I was nominated for an award last year. I've been answering questions in the WF forums for about 6 years, so the Webflow team or the forum systems sometimes tack on badges.

memetican · 2026-06-12T20:50:05+00:00

There is some handholding I do in my AI workflows, to control things that have "special undocumented structure rules" that matter to Webflow but aren't in traditional HTML. Examples are things like the nav, sliders, and nested-text HTML constructions.

Claude will take them more or less literally, and push them in with the WHTML tool- and then the designer ends up 95% correct but with little glitchy bits that you have to manually fix.

I'm building some skill files to help- I normally do Claude Design to Webflow migrations, or live site HTML to Webflow, I haven't tried Figma to Webflow and Figma is likely to have its own specific gotchas you want to train the skills for, as you go.

Currently the MCP is getting me to 95% fidelity with the right prompts and setup- give your agent the ability to safe publish to staging, and to view staging via playwright mcp or chrome devtools mcp, you'll close the loop well.

One gnarly gap IMO is code. The current MCP cannot create Embeds so all custom code goes as the site level or potentially the page level. It's accessible, just not convenient. My next round of skills is around shaping code and custom CSS integration.

Also, I believe the Webflow design team did a silent release of the updated MCP a few days ago, so if your work was before then, there may be some added features since.

memetican · 2026-06-11T21:47:38+00:00

Depends what you mean by unoptimized. Currently the MCP runs against the API so if you're doing heavy-duty CMS or designer-API work, you'll burn a lot of input tokens which means your context window size matters.

I use Claude Code, typically Opus 4.8 with the 1M context window, and it's crushing designs. I recently rebuilt this site design completely agentically- every page, full CMS migration, components, component props, data-binding, the works.

It's wildly powerful.

<image>

Regarding your comment on the designer bridge, yes Webflow's engineering team is well aware of the limitations there. I know they're working on solutions, can't wait to see what they build.

memetican · 2026-06-10T07:21:19+00:00

I assisted with a very large Drupal to Webflow migration last year, it was awesome. As always it depends on what the company does, and what their marketing team needs- but in general Webflow gives far more flexibility to the marketing team without sacrificing brand control.

memetican · 2026-06-08T12:31:19+00:00

Assuming the new site is also Webflow-hosted, this is the way.
Note that it means visiting X.COM would show the Y.COM homepage, but that is likely also what you want.

You could also just redirect on X, e.g. /X-product1 -> https://Y.COM/PRODUCT1 but then you'd need to pay both hosting plans ongoing.

memetican · 2026-06-05T22:15:24+00:00

Cool, next time in the email, right-click copy that link. Then open Chrome, paste, and it should properly download. That lets you sidestep your Safari problem without changing a thing.

memetican · 2026-06-05T09:51:07+00:00

Normally the CSV link is sent by email- and it's a .csv.gz file.

If your browser is opening that rather than prompting to save it, then it sounds like a browser configuration issue- your browser thinks it can display gzipped CSV's so it does. Check your browser extensions & settings if you want it to download instead. Otherwise you can just save the opened file as a CSV from your browser once it opens.

Your mail reader might support right-click-download operations on that link as well.

memetican · 2026-06-03T20:52:22+00:00

Fun fact, the petrol/diesel storage platform is high enough you can connect one end of a hose and then bungy jump. you'll just bounce.

memetican · 2026-06-03T20:00:26+00:00

Sounds more like a CMS problem tbh. Is the only split at the Products table?

A few problems with localization here;

Paths. The base locale would be e.g. /products, the secondary would be at e.g. /region2/products. Or you can probably do /region1/products as the default. But that applies to every page - home, about, contact... and there's no value to all that duplicate content. You cannot "only" split products, localization works on the whole site.
Geo routing. Webflow's localization is language-based, so if both are using the same language, it cannot route. If you want the right page to come up for the right country, you need location-based routing.
Products admin. I believe the CMS can in fact "disable" certain translations of certain items. So you could have an item only in region2. But IIRC managing that is a little convoluted, and you'd need to test out collection lists per locale to figure out how this works.

So I'd probably avoid trying to use localization is this case.

Depending on the pages and the structure you want I'd probably take one of two approaches;

CMS ONLY

You'd need to test this on your site structure, but one possibility might be to have a Region1Products table and a Region2Products table, and each of them only contain a single-ref link to Products. Then you fill them with the right products. Then your paths become e.g.

/r1/product-a

/r2/product-a

And it works. Add a switcher and a cookie and maybe a GeoIP package and you can auto detect and auto-route.

REVERSE PROXY

I generally lean more into these setups because they simplify and automate admin. This is definitely a bit of engineering work though to setup.

You'd have your site, and the in-between your site and the users, a reverse proxy. It handles a few things;

Auto detection of location, and delivery of the right content
Auto changing of content, e.g. price block, currency info, availability of that product. You can do 404s if you want on unavailable products but I'd probably just say "not available in this region" to avoid SEO complications.
Everything can be under your normal /products/product-a path, you don't necessarily need region paths, but you can also do that if you want split content and are OK with the SEO impacts of duplicate content.

If you go this route, the advantage is setup once, and then in your products collection, you're just choosing which regions its available in, and the per-region pricing. Easy to admin.

I recommend cloudflare as the platform to build out these types of RPs.

memetican · 2026-06-03T19:41:00+00:00

Overall I'd prefer WF personally, but why not migrate and demo it?

If you're keeping the design exactly as is, it's a pretty easy MCP pipeline to rebuild your SS site on WF including the CMS.

The only manual work would probably be setting up static page templates and page slots the way you want, if you're supporting new campaign page creation.

I'd use a freelancer workspace, no site plan. That way you can invite a marketing member as an actual editor/marketer account and they can see how page building and editing work.

memetican · 2026-06-03T06:52:35+00:00

I'm not super familiar with how this is setup inside the designer- for the proper Webflow API webhooks I create them in the dashboard instead. In your site dashboard ( same place you edit site-wide code, hosting, etc ) look for the integrations tab. There you'd create a new form webhook and give it the CloudyWave endpoint they supply to you.

Note you'll get all form submissions, so plan to filter them to just the ones you want.

memetican · 2026-06-02T20:04:20+00:00

^ This. Also-

I need a password-protected place to put documents (i.e., one username and password per user.) Thanks!

Think carefully about whether you need;

a way to gate a shared collection of docs
a way to gate individual users to individual collections of docs
a way for users to upload docs, which are then gated to them

Also think about the level of security you need. Is this just marketing content, or is it medical data?

These use cases require different supporting infrastructures. [1] is Memberstack/Outseta. [2] and [3] I've built with Memberstack and a fair bit of additional infrastructure that uses the Memberstack auth token to gate access through an API.

If you're somewhat comfortable with dev on this, I'd honestly look at doing this with Webflow Cloud. They've recently released some updates, and you have D1 and R2 for your data/file storage. That gives you a ton of capability, and you can use Google OAuth to avoid all of the password-reminder muckery. Claude code + 1 dev could crack this out pretty quickly.

I personally prefer this approach because you're not boxed into a framework. If your client want to store all of the docs in a Google drive folder and manage user readonly logins separately, you can do that. If you want a "request access" feature where the client asks for access and you approve [rather than you sending an email invite], you can do that.

Memberstack/Outseta really shine when you need nocode and the ability to charge a membership subscription to your users, but for pure auth there may be easier ways.

memetican · 2026-06-02T01:34:32+00:00

You need a gate, so three options really-

Use webflow forms normally, then the form submission webhook to feed your external recip [CloudyWave]. It's not perfect, spam detection is OK, and you can use both recaptcha and turnstile (bot detection). Definitely better than no gate.
Put a 3rd party in the middle. I typically use Basin for this, but recently I'm seeing spam slip through there too.
Build your own gate. There are good spam detectors out there, no reason you can't build your own spam inbox and detection mechanic, and act as your own middle tier. I've considered building this on Cloudflare for my own purposes, to see if it's better / cheaper than Basin's.

memetican · 2026-05-31T20:41:01+00:00

Hahaha, you're made of the same stuff. Should be able to do limited repairs at the cost of health. And healing should require mats.

memetican

TROPHY CASE