heatsynclabs/new-hsl

There is a "fold" between 600 and 700px from the top of the page

zyphlar opened this issue · 10 comments

On all window sizes between ~700 and 800 in height (making the fold between 600 and 700px from the top) a new visitor to the site will not perceive that the website contains any content "below the fold." 50% of our website's visitors have vertical resolutions of 768, 800, or 900.

Further explanation: once I've seen the deadmau5 head in the image, I assume that I've seen the bottom of the image and thus the bottom of the webpage unless I also see the "Calendar / Discussion / Twitter" headings. These are currently positioned between 600 and 900px from the top of the page, meaning that many people (myself included, designer of numerous webpages) will be confused for at least a few seconds and think there is no content on the website.

Suggested fix: ensure that there is no "fold" between 600-700px by reducing the header image size to ~370px, or spanning the left column's content between rows.

http://the.foldisdead.com/
http://www.thinkdesigninteract.com/post/adapt-or-die-and-the-fold-is-dead/
https://www.nuvonium.com/blog/view/stop-the-above-the-fold-web-design-insanity-people-scroll-today
http://www.thinkbrownstone.com/blog/2011/11/22/the-fold-is-dead-long-live-the-fold/
(google "Above the fold is dead")

Favorite quote:
Meanwhile, usability practitioners have been preaching for well over a decade about how scrolling is safe. Furthermore, if you design your page to encourage scrolling and give the user a reason to read, you’ll do even better.

I am not fully against above the fold, but it doesn't ruin the current design because people do scroll.

Old arguments against the fold: "you must put all the content in the first
700px"

Current argument against the fold: "you gotta have content that spans the
~700px area in order to encourage scrolling."

The current design doesn't encourage scrolling, that's what this issue is
about.

On Fri, Jan 18, 2013 at 10:40 PM, Blaine Bublitz
notifications@github.comwrote:

http://the.foldisdead.com/
http://www.thinkdesigninteract.com/post/adapt-or-die-and-the-fold-is-dead/

https://www.nuvonium.com/blog/view/stop-the-above-the-fold-web-design-insanity-people-scroll-today

http://www.thinkbrownstone.com/blog/2011/11/22/the-fold-is-dead-long-live-the-fold/
(google "Above the fold is dead")

Favorite quote:
Meanwhile, usability practitioners have been preaching for well over a
decade about how scrolling is safe. Furthermore, if you design your page to
encourage scrolling and give the user a reason to read, you’ll do even
better.

I am not fully against above the fold, but it doesn't ruin the current
design because people do scroll.


Reply to this email directly or view it on GitHubhttps://github.com//issues/56#issuecomment-12450859.

Paging @blhack this is aligned with your interest in seeing the whole page slimmed up (zoomed out) a bit

I think the version on gh-pages right now is really nice.

People will know that there is more content because they are presented with a scrollbar.

So I guess a little of both.

I disagree but am willing to be proven wrong by installing an analytics
package that shows page scrolling stats.
On Jan 21, 2013 11:14 AM, "Ryan" notifications@github.com wrote:

I think the version on gh-pages right now is really nice.

People will know that there is more content because they are presented
with a scrollbar.

So I guess a little of both.


Reply to this email directly or view it on GitHubhttps://github.com//issues/56#issuecomment-12510155.

Do you have a fork that makes it look the way you think it should? We could set up an AB test on your version of it, I'm sure.

Nah I've got enough to do regarding making this live; I'll just stick in a
line of JS to track stuff so we can fix it if the stats look awful.

On Mon, Jan 21, 2013 at 1:14 PM, Ryan notifications@github.com wrote:

Do you have a fork that makes it look the way you think it should? We
could set up an AB test on your version of it, I'm sure.


Reply to this email directly or view it on GitHubhttps://github.com//issues/56#issuecomment-12515317.

Isn't that kindof pointless unless we're A/B testing against something that is "correct"? Tracking a single point doesn't tell us anything meaningful.

Well it's more pointful than not setting up analytics ;) I just don't
have time to set up A/B testing.

On Mon, Jan 21, 2013 at 1:30 PM, Ryan notifications@github.com wrote:

Isn't that kindof pointless unless we're A/B testing against something
that is "correct". Analytics tracking on a single point doesn't tell us
anything meaningful.


Reply to this email directly or view it on GitHubhttps://github.com//issues/56#issuecomment-12516029.

Closing this due to inactivity