Footer should be viewable #15322
Replies: 49 comments
-
|
Thanks for the issue! We'll take your request into consideration and follow up if we decide to tackle this issue. To our amazing contributors: issues labeled To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @thepracticaldev/oss and we will follow up within 3 business days. For full info on how to contribute, please check out our contributors guide. |
Beta Was this translation helpful? Give feedback.
-
|
@ludwiczakpawel I know you've talked about infinite scroll, do you want to weigh in on this issue? |
Beta Was this translation helpful? Give feedback.
-
|
By 'weigh in', you mean contribute? |
Beta Was this translation helpful? Give feedback.
-
|
@Gbahdeyboh I would like Paweł's opinion on how we should fix this issue, he is one of our designers and may want to give feedback before we make start implementing something! I don't want to suggest that we write code for this right away because dev.to is undergoing a lot of design work and this might already be something our design team is thinking about. |
Beta Was this translation helpful? Give feedback.
-
|
I'm pretty sure @ludwiczakpawel has something in the works. |
Beta Was this translation helpful? Give feedback.
-
|
@jacobherrington I totally understand, such decisions are to be made by the design team. |
Beta Was this translation helpful? Give feedback.
-
|
Linking this issue which is related #5670 |
Beta Was this translation helpful? Give feedback.
-
|
That is correct, we've been thinking about footer and infinite scroll and we came up to conclusion that probably the best scenario would be to stop loading feed items automatically at certain point. Probably one of those two solutions: One
Two
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @ludwiczakpawel, both look great. I get that you're trying to reduce the number of
I'm more concerned at people being able to access the footer whenever they want rather than just once. |
Beta Was this translation helpful? Give feedback.
-
|
I think having this button only once makes more sense because when you scroll down to the bottom of the page you have one of the two intentions:
I don't think users would be interested in seeing a footer after loading feed items 2 or 3 or 4 times. We have quite a lot of feed items in our initial batch so I think it would be just enough to see "load more" button but I have nothing against increasing that number a little bit more. Honestly, the "infinite scroll" experience should be seamless enough to not make anyone think that something has been loaded in the background. |
Beta Was this translation helpful? Give feedback.
-
|
I landed myself here after a few frustrating infinite scroll because I want to reach footer but never managed.... maybe I'm old-fashioned but I don't like infinite scroll. I want to take control of my time and what I choose to see. I prefer "load more" button always, and perhaps a progress bar indicating how many are loaded already and how many left. Of course I understand it is impossible if you want to load in an infinite way. How about this: the first time you will see load more button, and infinite scroll button, and footer. If people click on infinite scroll, they will enter the current mode that dev.to has... if they click on load more, they will always have load more and always can access footer. |
Beta Was this translation helpful? Give feedback.
-
|
@AnnieTaylorCHEN yeap, that's pretty much the approach we want to take (see other comments in this issue) 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Sorry to barge in @ludwiczakpawel. How about keeping the footer hidden but allowing the user to show it?
Since the feed does not cover the entire page's width, it will not interfere with anything that needs to be visible. 1- Footer never shows on its own:
2- Footer is shown before the first "load more" click:
Also, it is possible to turn off the "Show Footer" toggle any time it was on and the user scrolled down again or loaded some more feed (assuming the user showed the footer after at least 1 feed batch loading). |
Beta Was this translation helpful? Give feedback.
-
@JulianBroudy All good, I really appreciate all suggestions and ideas :) It's open source world! Anyway, I think any of these two proposed ideas would be nice addition (I'm probably leaning towards 1st idea more). But we still have to figure out stopping the infinite scroll part AND resuming it with "load more" button. But yea, the "show footer" idea is overall pretty neat. I'd personally make some different UI choices here but the concept is good :) Is this something you'd like to work on? |
Beta Was this translation helpful? Give feedback.
-
Of course! I would love to.
Absolutely, this was just to illustrate my point as I was short on time.
Could you elaborate please? |
Beta Was this translation helpful? Give feedback.
-
@perpetual-education what do you mean here? Listings appear on the top of the right sidebar (as its own "widget") as well as link in the main navigation in the left sidebar.
We're actually working on a proof of concept that would kinda remove the footer on views with infinite scroll and put its content somewhere else... But that's still pretty far on roadmap :) |
Beta Was this translation helpful? Give feedback.
-
|
Our feedback would be that we couldn't find it. (It's there) - but we couldn't find it / and there isn't much of a story told about the things in that widget. So, throughout or time surfing around - we've found pages and resource types that we didn't know existed and didn't seem to be in any menus. Things are folded up / and maybe they just blend in with the 'tag's and stuff. In cases like that, it seem to be a go-to/convention to look for a footer with a site-map to help explain how things are organized. In our case - we couldn't get to a footer. We're not trying to be argumentative. We just want to share our 'experience' as users. Besides the main feed and some filtering, the goals of the other things are a little unclear for us. Carry on! : ) |
Beta Was this translation helpful? Give feedback.
-
|
@perpetual-education gotcha, that makes perfect sense and thank you for that feedback - I really appreciate it! We definitely gonna address that issue in one way or another we just don't know exactly how yet. Information Architecture as well as how we present our navigation and things you can do on Forem/DEV is pretty important - no doubts about that. So please bear with us and keep sharing the feedback :) We just haven't had enough time and resources to put enough attention to these things. YET. :) |
Beta Was this translation helpful? Give feedback.
-
|
so this is being hold, right? for later visitors, I'll sum up above debates. Problem : User can't see footer on main page because infinite scroll feature keeps bringing older contents in. Solutions until now :
Current status : holding because internal design team are debating about this issue (of course this is heavily design stuff). Besides, some other tasks are so poured that the conclusions keep postponed. -- Just my two cents : if user keeps scrolling down without a single glimpse -- for example, keep pressing So, this makes sense in some way : "If 5 'load content events' are fired in 5 seconds, stop the events and show User a 'load more' button. If the User clicked the button, no more restriction. just... leave them do that, all day." This only one chance to see footer feels like easter-egg, fun, but not intuitive.... Just my flash idea :) |
Beta Was this translation helpful? Give feedback.
-
|
@roeniss everything you mentioned above is correct! Thanks for summary. We will get back to this when we have better solution in house and more resources :) |
Beta Was this translation helpful? Give feedback.
-
|
I like the idea of the "show footer" button... but I feel like it could be stylized a lot better with the label as "∞ scrolling" with a material switch. Or maybe instead, the ∞ could be crossed out with a universal no when infinite scrolling is turned off. Might be a little more elegant. I don't have a mock-up so I'm not quite sure. Note that I was trying to find the github repo to suggest this (since I know dev.to is open source), and I was trying to get to the footer, only to be frustrated by the fact that I couldn't get to the footer because of the infinite scrolling.
I really like this idea too. |
Beta Was this translation helpful? Give feedback.
-
|
Dropping in to say that I ran into this issue today (I was actually looking to find my way to this GitHub to browse issues). Reading through the earlier comments, I don't believe I've seen this proposal:
This would let the user get to the footer in the expected way, and get additional content in the expected way, however, I think this requires the footer to be pretty minimal to prevent this behavior from being annoying. |
Beta Was this translation helpful? Give feedback.
-
|
@dev-dull let's see a prototype. |
Beta Was this translation helpful? Give feedback.
-
|
@sheriffderek Ah! That was a good exercise. It revealed to me the issue of the footer that's constantly trying to pop up and disappear as I scroll. I'll go sit in my backend dev corner now 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Add API link to footer Right now the user has to go to settings->account->docs to access the API docs but we can save a couple of clicks when a user is trying to access the API docs by placing the link at the footer. Although the footer cannot be accessed while scrolling the feed (infinite scrolling) but it is accessible at every other page. Also these links https://docs.dev.to/api/ and https://docs.forem.com/api are identical and may confuse when taking to another domain name so we could redirect users to use the right documentation link. |
Beta Was this translation helpful? Give feedback.
-
|
I quite like the twitter way of doing it. The footer is on the right hand side which scrolls with the main body but when it reaches an end (top or bottom) it freezer in place)
|
Beta Was this translation helpful? Give feedback.
-
|
I just came across this issue today as I was trying to get to the github link in the footer, but was unable to do so as more posts kept loading. Would replacing the infinite scrolling with a standard pagination be an option? Many sites allow the user to select the number of results per page, and I could envisage having 'infinite' be an option alongside several different numbers. |
Beta Was this translation helpful? Give feedback.
-
How does that work on mobile and for screen-readers? It seems like quite a nice solution for desktop users with a mouse, but might not work so well for smaller screens and keyboard navigation. |
Beta Was this translation helpful? Give feedback.
-
For Twitter, it seems to only be used as the footer of the "Help Center" which can be accessed from the main menu. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
-
dev.touses an infinite scroll to render more articles as a user scrolls through the page, this makes it almost impossible to ever get to the footer of the page. When the navigation bar is dragged down to the footer, it takes only a few milliseconds before new articles are loaded and the footer is no longer in view.The footer contains some relevant information and hence should be viewable and interactable.
Beta Was this translation helpful? Give feedback.
All reactions