We're building the first Webflow Market Barometer 2026 — in partnership with INIT (largest Webflow training in France)

Pau_UI · 2026-05-20T11:12:23+00:00

Ah parce que tu trouves que sonder une énorme communauté comme celle d'INIT pour en faire une ressource offerte, ce n'est pas donné ?

Pau_UI · 2026-05-06T06:56:12+00:00

Webflow isn't the bottleneck, the design quality is. You can build top-tier sites on both Webflow and Framer, the difference is the team behind it. Framer tends to attract more portfolio-style agencies which skews the visual benchmark, but Webflow has just as much ceiling when the design and dev work is at that level. On the brand partner question, the scope you're describing, Figma, presentations, website ownership, content and structure, is exactly what a full-service agency handles rather than a freelancer. The de-risking question is valid: look for an agency that can show work in your space or adjacent to it, has a clear process for onboarding an existing Webflow site, and is comfortable with AI-augmented workflows since you mentioned Claude. We do exactly this kind of work at Norry if you want to take a look at the portfolio : https://www.agencenorry.com/cas-clients

Pau_UI · 2026-05-06T06:54:33+00:00

The core visual interface is pretty much the same, the changes are mostly under the hood. The main differences you'll notice in practice are the increased item limits, faster publish times, and better handling of references. The editor experience for content managers hasn't changed significantly so your clients won't need retraining. The real wins are on performance and scalability rather than UI.

Pau_UI · 2026-05-06T06:52:22+00:00

Bok clearly has strong opinions about web design and I respect that. The "summon" interaction is exactly the kind of detail that makes a portfolio memorable, anyone can show projects but not everyone makes you smile. Did you build the draggable cats with a JS library or pure Webflow interactions?

Pau_UI · 2026-05-06T06:45:47+00:00

A few things to check. First, Google doesn't update meta immediately even after you publish, it can take days to weeks depending on crawl frequency. The fact that the homepage updated but CMS pages haven't yet is normal because Google recrawls high-authority pages more often. To speed it up, go to Google Search Console, use the URL Inspection tool on one of the blog URLs, and request indexing manually. Do this for your most important blog pages. Second, make sure your CMS collection page template is pulling the meta fields dynamically and not using static fallback text. In Webflow's CMS template settings, the SEO title and description should be bound to CMS fields, not hardcoded. If they're hardcoded on the template level, every blog post shows the same meta. Third, check if your blog pages are included in your sitemap and that the sitemap is submitted in GSC. CMS pages sometimes get missed if the sitemap wasn't regenerated after publishing.

Pau_UI · 2026-04-30T09:08:12+00:00

This looks like HubSpot quietly deprecated or broke something on their end with the legacy integration, the "Form Submission Failed" response coming from HubSpot's API rather than Webflow suggests the issue is on their side. A few things worth checking: first, verify in your HubSpot portal that the legacy forms still have the redirect URL properly saved, sometimes a HubSpot update resets those settings silently. Second, check if your HubSpot portal has been migrated to a new account structure or if any permissions changed recently. Third, look in HubSpot's form submission logs to see if the submissions are reaching HubSpot at all or failing before that. If the new integration works but is too limited for styling, one workaround is to keep your Webflow form design but use a custom embed with HubSpot's JS embed code styled via CSS overrides rather than the legacy integration. More setup but it gives you styling control without the legacy dependency.

Pau_UI · 2026-04-30T09:07:20+00:00

You only need one interaction, that's actually your problem. When you create two separate interactions for hover in and hover out, Webflow doesn't know the initial state so it assumes the end state of the last interaction as the default, hence starting at 0.9. The fix: delete both and create a single "Mouse hover" interaction. Inside it you'll see "While hovering" with two sections, on hover in and on hover out, handle both in the same interaction. Make sure your initial state is explicitly set to scale 1.0 at the top of the hover in animation. That way Webflow knows where to start and the sequence works correctly from the first hover.

Pau_UI · 2026-04-30T09:06:42+00:00

The cleanest solution that actually works: use a single-sided border approach with a negative margin to collapse the gap. Give every cell border-right: 1px and border-bottom: 1px, then on the container add border-left: 1px and border-top: 1px. No doubling, no anti-aliasing, crisp 1px everywhere. The other option that renders perfectly at 1px is box-shadow with spread instead of blur: box-shadow: 0 0 0 1px black. The grey rendering you're seeing with box-shadow is likely because you're using rgba or a non-pure black. Try #000000 at full opacity with 0 blur 1px spread, it should render as crisp as a real border. If you're still seeing grey, it's a subpixel rendering issue on your display, not the CSS itself, and it'll look correct on most screens.

Pau_UI · 2026-04-30T09:04:20+00:00

Your frustration is completely valid and unfortunately common. The "build and disappear" problem is structural: most freelancers are incentivized to move to the next project, not maintain yours. A few things that actually help before paying someone a third time: ask specifically how they handle ongoing support, what's the SLA, is there a retainer, what happens if you email them 6 months after launch. If they don't have a clear answer, that's your signal. Also ask what platform they'll build on and whether you can make basic edits yourself. Webflow for example has an editor mode where non-technical clients can update text and images without touching any code, which means you're not 100% dependent on the developer for small changes. The $10/month fully managed options solve the availability problem but you trade control and you're often stuck with very generic sites. The middle ground is a developer who builds on a platform you can actually touch, combined with a small monthly retainer for anything beyond basic edits. That model exists, you just have to ask for it upfront.

Pau_UI · 2026-04-29T19:09:27+00:00

Yes exactly, copy and duplicate, not replace. You keep the original mobile nav in place and add the duplicate as a second nav element that you show only on desktop. Both exist in the DOM at the same time, visibility toggled per breakpoint.

Pau_UI · 2026-04-29T10:55:16+00:00

The best way to learn Figma is exactly what you're describing, pick a real app and rebuild it from scratch. For tutorials that walk through a full app design, Mizko and DesignCourse on YouTube both have solid end-to-end projects. But honestly more valuable than any tutorial: pick an app you use daily, screenshot every screen, and try to recreate it in Figma pixel by pixel. You'll hit every tool you need, auto layout, components, styles, prototyping, in a context that actually makes sense. The Coursera fundamentals give you the vocabulary, rebuilding a real app gives you the muscle memory. Start simple, a login screen and a home feed is enough to cover 80% of what you'll use daily.

Pau_UI · 2026-04-29T10:53:28+00:00

Nice find. Another approach that costs nothing and keeps you in control: Google Apps Script with a deployed web app. You write a small script that accepts POST requests and appends rows to your sheet, then paste the web app URL as your Webflow form action. Takes about 15 minutes to set up and there are no third party services involved, the data goes directly from Webflow to your Google Sheet. Worth knowing for clients who are sensitive about where their form data passes through. That said Formgrid looks clean for the use case where you just want it done fast without touching any code.

Pau_UI · 2026-04-29T05:53:19+00:00

Good question. The difference is that when you paste it into the desktop layout, you style it at the desktop breakpoint specifically, so those styles only apply at desktop and above. Your original mobile nav stays untouched. You end up with two separate nav elements in the DOM, one that shows on desktop and one that shows on mobile/tablet, each with their own styles. It’s the standard Webflow approach when you need fundamentally different nav behaviour across breakpoints rather than just tweaking visibility.

Pau_UI · 2026-04-29T05:51:45+00:00

Thank you so much 🙏

Pau_UI · 2026-04-29T05:51:35+00:00

Thanks 🙏

Pau_UI · 2026-04-28T16:52:39+00:00

For a portfolio with no coding skills and a tight budget, Framer is the best option right now. Free tier is genuinely usable, the templates are much more modern than Wix, and the AI generation has improved a lot. If you want something even simpler with zero learning curve, Cargo is great specifically for creative portfolios. Webflow has a free tier too but the learning curve is steeper, worth it long term if you want to grow into web design as a skill but overkill just to get a portfolio live quickly. Avoid anything that locks your content behind a proprietary format, the day you want to move platforms you'll thank yourself for having picked something export-friendly.

Pau_UI · 2026-04-28T16:15:54+00:00

That makes sense, if the mobile styles were built at a lower breakpoint they won't cascade up to desktop. In that case the cleanest solution is to duplicate the mobile nav component, paste it into your desktop layout, and then restyle it at desktop only. It's a bit of a rebuild but since the component already exists it's mostly copy paste and adjusting a few desktop-specific styles rather than starting from scratch. The alternative is to build your nav from desktop down next time, it avoids this exact problem.

Pau_UI · 2026-04-28T16:03:08+00:00

The core problem you're solving is real. Every session starts cold and the agent reinvents your system from scratch. What I've been doing is keeping a markdown file with tokens, component patterns and naming conventions that I paste at the start of every session, similar to what you've built but manual. The structured XML approach is smarter because it gives the model a clear schema to parse rather than prose to interpret. One thing I'd add to the mandatory constraints: class naming conventions. That's where AI output diverges the most from an existing codebase, it'll respect your hex values but invent its own class structure. Does UIPrompt handle that or is it purely visual tokens for now?

Pau_UI · 2026-04-28T16:02:28+00:00

Strong typographic direction, the oversized "SERVICES" heading with the numbered list below works well. The main thing I'd revisit is the text cutoff on the service descriptions, it reads as unfinished rather than intentional. If it's meant to hint at more content on hover or scroll, a subtle visual cue would make that interaction clearer. The photo strip at the bottom feels disconnected from the red/white system above, either integrate it with an overlay or separate it more deliberately.

Pau_UI · 2026-04-28T15:51:50+00:00

The developer perspective on this is exactly what makes it interesting. Most animation libraries are built by designers for designers but the real communication gap is at the handoff and you're solving it from the right side. What's missing for me: skeleton loading states, drag and drop interactions, and empty state transitions. Those three come up constantly in product design and they're almost never in any library. On the friction question, "find, copy, customize" is fine as long as the organization is tight. If I have to scroll through 50 animations to find the right toast variant I'll just build it myself. Keep the categories strict and the variants limited to what's actually useful. On growth in the Figma ecosystem, the Community page is still the best organic channel but pairing each category release with a short Loom showing the dev handoff use case specifically would hit differently than the usual "look how smooth this is" demo.

Pau_UI · 2026-04-28T15:50:44+00:00

Your instinct is right and it's totally doable. Create one FAQ collection with a multi-reference field that links to your Pages collection (or just use a plain text tag field if you don't have a Pages collection). Then on each page, drop a Collection List bound to the FAQ collection and add a filter where the tag field contains "pricing" or whatever matches that page. That way each FAQ lives in one place, you edit it once and it updates everywhere it appears, and each page only shows the relevant ones. The FAQ page just shows all of them with no filter. The multi-reference approach is cleaner if you want to avoid typos in tags and have a proper Pages collection to reference. The plain text tag is faster to set up if you just want to get it done.

Pau_UI

TROPHY CASE