[lycos]

When it does load it looks like this could've just be a static site, so it's interesting to see it being a serverless function that crashes the whole time.

But yes, the idea of designing for the fold is from early 2000s (or i guess I should say pre-2010 in my experience) and should stay there.

[busterarm]

> But yes, the idea of designing for the fold is from early 2000s (or i guess I should say pre-2010 in my experience) and should stay there.

    /signed lycos

Oh the irony.

As much I agree with you, you're talking about the collision of content and eyeballs and advertising. Brands insist on getting their juice.

[wodenokoto]

It needs a dynamic, server side component, regardless of how you choose to design the site.

And if it was to serve a static page, it would also need a client side dynamic component.

So I would probably also have gone with full server side rendering.

[1-more]

My first pro web development gig was at an agency that only did pharma. All pharma websites need to have the FDA's black box warning above the fold. So in some cases the fold is a regulatory concern, not one of vanity for designers.

https://en.wikipedia.org/wiki/Boxed_warning

[Levitz]

Shouldn't it be fixed to a point in the screen then? Very much like cookie notices?

[1-more]

What we'd do for a bunch of them is put the indication and black box warning in a position:fixed element. That text would be the start of the full fine-print on the drug. When you scroll the fine print section into view the now redundant fixed warning would hide. e.g. https://www.botoxchronicmigraine.com/ https://www.skyrizi.com/

Also the FDA won't let you dismiss a box warning. It needs to be visible on the page at all times. A cookie warning can be more annoying because it can be dismissed.

Here's an example using the fold https://alexiononesource.com/soliris

Really this was a print agency that thought of web developers as an unfortunate cost center necessary to make their photoshop follies into web pages. It was a really tough case of no one knowing their audience too:

- html email designs with complicated 9 slice borders that are impossible to render consistently

- the real audience for the web site is the client's internal network, who are on IE8 or even 7 (9 had been out for a long time) and you want features I need to hand code in JS or 9 slice.

- the real real audience is the legal review, so it's worth it to develop a tool to capture the whole site to a PDF they can mark up including drawing a "fold" line on the page

None of the sites I'm linking here are ones I wrote, just examples.