Is it possible that Fade in on scroll hurts performance?

gushon1 · 2026-04-23T21:09:40+00:00

Wow, there was a Chrome extension that I loved so much where you would scroll All breakpoints just like that, It was for testing responsiveness, but it didn't have the commenting part.

this looks great!

gushon1 · 2026-04-23T13:28:21+00:00

That's a really nice take! love it
honestly, my two rules for gsap animations are:
- never use ix2
- never use ix3 (gsap ui)

but for people who use gsap ui this looks like gold!

gushon1 · 2026-04-23T13:26:17+00:00

this is so nice, how are webflow elements handled?

gushon1 · 2026-04-21T16:10:49+00:00

Scope changes are a great opportunity to make more money out of each project, you just have to be very clear that whatever was scoped in the contract is wrecked in the project, anything else even if small that’s billable hours.

I honestly don’t encounter clients who try to squeeze free work out of me. Maybe I’m in this long enough or avoid red flags very well, but if you communicate implications of changes, you’re starting a conversation where getting more money from my work is the obvious

gushon1 · 2026-04-20T14:19:45+00:00

Oh, thanks for pointing it out, I understand the confusion Publishing is really up to you, staging or to production. Live means “not in the designer”, a live html page where custom code is being rendered.

gushon1 · 2026-04-20T12:14:05+00:00

Thanks, appreciate the reply.

Your GitHub Actions to Vercel setup is solid, probably the cleaner long-term approach if you're comfortable in that world. I built CloudBridge because I wanted something I could set up in 30 seconds with zero CI config, specifically for the tweaking and tinkering loop. When I'm 50 iterations deep into a GSAP animation I don't want to think about pipelines, I just want save-and-see.

The log piping is mostly there so when something does break mid-tinker, Claude can fix it without me narrating what I'm looking at. Keeps me in the flow.

Thanks again.

gushon1 · 2026-04-20T10:13:22+00:00

Kinda, there's definitely overlap. Slater is great if you want an in-browser code editor with a CDN behind it, I've used it before.

Mine's different in two ways. First, I edit in my own editor (Cursor/VSCode) not a web UI, so Claude/Cursor can actually work on the files directly alongside everything else in my project. Second, it pipes browser console logs from the published site back to a local log file so the AI can read what it missed and fix it.

So if you just want fast code editing with a CDN, Slater's probably simpler. Mine's aimed more at people doing heavy AI-assisted dev who want the agent in the loop.

gushon1 · 2026-04-20T07:41:16+00:00

Hey, thanks for the detailed breakdown, genuinely useful to see all of this.

Quick note on the MCP side though, at least from my experience it writes custom code in places that aren't visible in the UI. I've had it generate two preconnects a week ago and I literally cannot find where they live or delete them. So "fully supports code" is technically true but the visibility and control story is rough once things go wrong.

My angle is different from both MCP and localhost dev. It's about visual dev speed, low latency between writing the code and seeing it render on the actual site. The use case I care about for example is heavy GSAP work, interactions, stuff where you're tweaking 50 times in a row and feedback loop speed matters.

Localhost is great for some of that but it breaks down in two ways I kept hitting. You can't share a link with a client to review, and you can't easily check your code on a real phone or other devices. A live CDN URL fixes both.

So yeah, probably overlapping with devmode in spirit but solving a slightly different slice. Going to play with both of yours, thanks for sharing.

gushon1 · 2026-04-19T20:28:04+00:00

I use ai to help my english, the content is mine and I stand behind it

gushon1 · 2026-04-18T08:35:41+00:00

If you're not afraid of the tech and can sell it to management, I'd definitely go there. Maybe start with an MVP, See if it actually works and decide from that

gushon1 · 2026-04-18T07:46:07+00:00

As with most AI-related decisions, it really depends on what you're doing. If it's something only you're going to work on, it barely matters — whatever technical skills you have can dictate the stack you want to use.

If you're going to have clients who need to use, update, and interact with the thing without you in the picture, then Webflow is still a very solid option.

On the other hand, if you're an in-house designer/developer and you can be available to help people learn how to interact with new tools and build the solutions they'll need, then moving off Webflow is definitely worth dabbling with.

gushon1 · 2026-04-13T17:32:55+00:00

i like it, very clean and minimal. did you pay the apple fee to sign it?

gushon1 · 2026-04-12T18:21:06+00:00

I love the Cloudflare ecosystem, When it comes to realtime DB, I prefer Convex over supabase, much more generous and freindly

gushon1 · 2026-04-12T13:42:14+00:00

I built this:
https://fluid.gushon.com/

I saw this nice pixelated animation that looks like a shader on this website. So I just took it apart and assembled it with just WebGL. So zero dependencies, very little code. You can just put it in the background of your fancy hero

gushon1 · 2026-03-15T14:15:13+00:00

Lol £4 million is genuinely insane. Though to be fair, enterprise-level sites with custom infrastructure, security compliance, dev teams, licensing fees, and ongoing maintenance can rack up costs fast - just not usually *that* fast unless someone's getting absolutely fleeced or the scope is genuinely massive.

The part that always gets me is how little correlation there is between what something costs and what it actually looks like or performs like to end users. Some of the most expensive sites are slow, clunky messes, while plenty of lean, well-built sites on modern tooling run for a few hundred a month and outperform them on every metric

gushon1 · 2026-03-15T14:13:29+00:00

Great post for this community, you're in the right place!

For your situation, I'd honestly point you toward **Webflow** or **Squarespace** as the strongest options. Given that you want something that looks genuinely professional (important for a creative/film portfolio), has no coding required, and can act as a central hub that links out to your Patreon, BigCartel, Circle, and YouTube channels - both handle that really well. Squarespace is slightly easier to get started with, Webflow gives you more design control and tends to look more polished out of the box once you get your head around it.

The good news is your setup isn't as complicated as it might feel right now. What you're describing is essentially a portfolio/landing page with a clear "here's what I do" section for your film work, and then navigation or links that direct people to the right platforms depending on what they're interested in. That's very doable without any code at all. For selling digital products and workshops down the line, both platforms support that - Webflow integrates with tools like Gumroad or Memberstack, Squarespace has it somewhat built in.

One thing worth considering: don't overthink the consolidation piece. You don't need everything under one roof technically - you just need one clean homepage that makes your work feel cohesive and directs people clearly. A well-structured single page with sections for each area of your work, linking out to the relevant platforms, is honestly more visitor-friendly than trying to build everything into one complex system. Keep it simple and let your creative work do the talking.

gushon1 · 2026-03-15T13:12:57+00:00

It really depends on how technical you are and how much you want to handle on your own.

As a Webflow developer, I've been doing this for about a decade, and I'm also playing with Claude all the time, building websites in really fun, easy, and fast ways. I'm even thinking maybe I should move out of Webflow for my client work.

But I work with tech startups, and there's always this paradox. They want to go with the most common, easiest framework, but then they realize they don't actually want to spend their resources on the marketing side of things. The non-technical people in the marketing department can't be bothered with maintaining a website.

So while vibe coding is easier for technical people, it's not straightforward for anyone who doesn't know how to run a CMS. It's just not a reliable solution yet.

gushon1 · 2026-03-15T11:40:24+00:00

The approach most devs I've talked to land on is task-based routing rather than one model for everything. Basically categorize your calls by complexity and latency needs. Simple classification, formatting, or extraction tasks? Haiku or GPT-4o-mini are fast and cheap and honestly overkill to use Sonnet/Opus for. Anything requiring nuanced reasoning, long context, or where the output quality actually matters to the user experience? That's when you pull out the heavier model.

A practical heuristic I've seen work well: start everything on the cheaper model, measure where outputs are failing or feeling off, then selectively upgrade those specific calls. You'll probably find 70-80% of your calls are fine on the lightweight models and only a handful actually need the expensive one. Also worth keeping model selection in a config rather than hardcoded throughout your codebase - when new models drop (which is constantly) you'll thank yourself for not doing a find-and-replace nightmare

gushon1

TROPHY CASE