We’re considering moving away from Webflow for something more AI-friendly. Any recommendations? Our biggest pain point today is the MCP experience: Slow, Browser-dependent, Token-hungry. What I’m looking for is pretty simple: Have an excellent building and editing experience with AI. For me or any person of the team. But I don’t want to spend any time thinking about Core Web Vitals, technical SEO, or infrastructure. Curious to hear what you’re using and what you’d recommend 🙏
A mix of custom and switching to Quarto for documentation/static sites? But that wouldn't do without thinking of technical stuff, yes.
Maybe try to map out core stuff you keep altering, any patterns? If you notice any patterns, it can be a one-time heavy build, but with proper documentation, that build will help the AI build it further without adding overhead on the technical part.
Given it's not a really niche tool and something AI is familiar with and well documented, Claude will help you manage it a lot.
I know tech stuff may sound overwhelming (and it is, even for devs — things keep changing), but if we trace back to common patterns and nail down what helps, the day-to-day overhead becomes really manageable and tweakable with Claude.
Web dev isn't what I do as a main thing, it's research, and I'm taking a break from research right now. I have enough tech to set this up and enough of the non-tech side to know what's sustainable without tech overhead. It's really distracting to manage too much technical stuff when your core remit isn't tech at the moment.
For context: we had a site that was really cool and didn't take much time from core research, but the moment we had a new announcement, blog post, or feature, the whole thing took hours and became a huge chore. We traced back the last month of updates and what we expected to change in the next three, and also needed it to look on-brand, so we couldn't just slap a template on it.
If there's one thing I'd suggest, it's pattern mapping. A site usually has few moving parts, and few that only matter when there's a big decision. Tracing that helps you see what's actually consuming time, so you automate that instead of bending yourself around an existing system.
A few things worth checking regardless, for the first build:
1. When does it break (not every break is a KPI — if it breaks and it matters, fix it).
2. Does it follow DRY, is there a coherent structure, or is it spaghetti?
3. A documentation version for a future AI agent, and a separate one for a future non-technical human — they read very differently.
4. A "repo map" markdown doc, so a future agent doesn't burn tokens figuring out where things are.
5. An authority matrix — what an AI can edit outright, what needs a flag to a human, what needs a technical consult.
6. Tests, so future updates don't quietly break what already worked.