Volf-000

I've just started working with GSAP, and so far have been managing timelines by "waterfalling" -- which is not 100% ideal for OA Banners that need a strict runtime of 15 seconds. (Going over that means a lot of manual re-refining, yuck). I'm assuming that waterfalling could be good in other instances of web/graphics animation? (e.g. something short or really simple, something that will only happen once). I'm sure it has it's place somewhere. Can it be possible to "stitch" together parts of an already-made timeline? I just want to know if there is a preferred timeline-algorithm for specific types of projects.

Hi @Rodrigo, Thanks for the quick answer! I totally agree with your perspective. Regarding moving the post, yes--you may move this post over to the Banner Animation forum. Please excuse my newness 😅

Apologies for the (dumb) question. I have a background in Frontend Web development, so when I first began investigating OA Banner code I was a bit puzzled to find divs everywhere. (For headings, for frames, for everything). I'm aware that the screen reader situation is taken out of the equation, and I doubt search engines have any use to crawl through OA Banners. But isn't it a bit trickier to work through, if everything is a div? Don't elements look the same if they're all written as divs? Is there a specific reason why everything in OA Banners are divs? (I've even noticed headings and paragraphs written as divs). I'm just genuinely curious.