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.
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.
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.
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.