As a general comment I would strongly advise against building such a complex arrangement with 3 of everything for different screen sizes. Everything gets downloaded for every screen size and so your page is a lot larger and more complex than it needs to be.
Sections content control (as per the Learn Sections demos) is designed to avoid this by allowing a full browser height section to automatically change to be the height of its content when the content overflows - this addresses the key point from earlier in the thread about content clipping.
Just noticed you asked to get a support ticket: Will do, but where can I do so?
You can open a ticket by emailing but please try and simplify things first. Break the problem down to smaller and more manageable pieces. Details of how to raise a support ticket are on the BWD website support page here. I am currently in the process of moving house and living in an AirBNB with almost no internet connection (poor 3G at best) so please bear with me with the increased support times that this means. Thanks.
@Jimmy sounds like your headed in the right direction. Don’t be discouraged (doesn’t sound like you are) you’re learning some great skills that will help you on your next project. While I don’t have your project file and a complete appreciation for your content and needs…you mentioned that you essentially made a section for each “device” (mobile, tablet, desktop). I’ve certainly taken this route before and it may be your best solution for your needs. However, I wanted to mention that Sections Pro, combined with sections box has awesome (in my opinion) responsive settings where one can create drastically different layouts based on device all within one “section stack block” (i.e. you might not need the sections in triplicate). Don’t wish to overwhelm you as I know there is a process to the learning curve.
LOL As I was typing this I see @tav response. Anyway the point being after you get a functioning site it might be worth going back duplicating your project file and start to work towards responsive sections and content vs. multiple sections for each device. Regardless best of luck.
Just as an addendum to my last point about complexity. Even if you do need to swap content for different screen sizes then you don’t need to do the same for the main structure of the page - i.e. just swap the content within the sections and not replicate the sections themselves with their scroll links.
I love this forum and I really appreciate your helping me crawl up that learning curve!
I started out by trying to do this page the simple way and just could not get it to look good so that’s why I built three versions of each section. Now, with more knowledge and your input I will study Section Box and try again.
One thing I am not sure about - despite reasoned your input and the Sections Pro descriptions - is how this overflow thing works. It looks to me as Section Pro, when there is an overflow of content, simply goes beyond the screen size, ‘forcing’ the web page visitor to scroll down. Is that correct?
@tav Do not worry about giving me speedy input. I know what it is like to have a spotty internet connection whilst at an AIrB&B: I have goed thru my share of moves over the last 4 years. Also, as @danhmill seemed to intuit already, I am not in a great hurry here. My Q&A page is up in an acceptable manner. Indeed, I am trying to learn how to do these things for a website overhaul I am planning. Good luck with your move.
Now having said all that, does either of you have any clue why my set up is not working? I.e., why are the links going all over the place? Yes, I am stubborn.
@Jimmy I don’t want to pour cold water on you, but early-ish in this conversation you mentioned you were using this area for a question and answer page. Unless there’s a really really really specific reason for doing it the particular way you want it seems like you are wasting a lot of energy.
There are several accordion stacks, several FAQ stacks, and several “other named” stacks that allow you to hide and show answers (question visible, answer unfolds). All these other options are much easier to implement, do not have problems with adjusting to various screen sizes, and are much easier to edit.
So is there some very specific reason you are taking this approach? At first glance it seems barmy and a waste of time. But, of course, there may be very good reasons for doing so that are not obvious.
Thank you and, no, not experiencing your comments as cold water. On the contrary, I appreciate your taking the time to share your mind. And, yes, I have specific reasons for doing it this way.
I like the look of it, even for a Q&A.
More importantly, I am ‘practicing’ for the overhaul of a bunch of my websites.
Been thinking over what you said and for this Q&A I may indeed change the set up. To that end, what Accordion stack would you recommend, taking into account I work in Foundry? Thanks!
@Jimmy First, I can see a use for your original approach. If I were developing a website for a pop star or actor or similar then I might use the same approach. The key is in this case the user is already “sold” on the product before coming to the site. And, in this case, the Q&A is more of a novelty or entertainment experience. Something for fun like: did you know these things about the pop star?
On the other hand if the user coming to the website is not already “sold” on whatever is being presented then your original approach would probably drive me bonkers. After all my questions might only be 4 and 5: and I can’t even see them as questions until I get to the end of the screens. And, well frankly, I wouldn’t even get to the end of the screens. I just want to find the info relevant to me as soon as possible. In this case I want to be able to see all the questions at a glance, and then explore the ones I’m interested in.
You know better than me what kind of website you have, it’s purpose, and the mindset of users coming to it.
As much as it pains me, I agree with @TemplateRepo ( ). Start with Foundry’s accordion. You can style it in a variety of ways. If it doesn’t meet your needs for some reason, then let us know. But in general a good starting point is to begin with what you already have.
If most of your answers have longer text explanations then you may want to use Glide. It provides that sideways reveal somewhat similar to the example TemplateRepo provided. (It’s really not the same, but similar enough that it’s worth a look.) And Glide comes with Foundry.
Thank you for your awesome input. I agree that for this Q&A it is better to go with an Accordion like approach for all the reasons you mentioned. You and the others convinced me. I think I will use the Full Page Scrolling approach for the a bunch of the regular web pages of my website as that fits the rock star high-end product we have.
I am in the middle of rebuilding the page with Accordion as we speak and it looks almost too easy in comparison.
I have said it before and I will say it again: I love this forum and really appreciate all your advise.
Lastly, please allow me a little plugging… I would like to mention that Foundry is super and that, as ever, @Elixir has been very helpful, both through this forum and by email.
Yes, I am stubborn.
