I swear to God, I've been doing web development for 20 years, and this is the first time I truly understand the difference between these property values...
I think I’m falling hopelessly in love with Webflow. This is the second Webflow employee in as many days that I have been given no choice, but to refer to as delightful. It used to be that the only viable way to learn something about Webflow was to watch Ran Segal over at Flux. Webflow university existed, but the content often felt like a chore. But now, now!? Webflow University is fully accredited and this man (what’s his name?) is the headmaster. Ran’s still awesome, too.
First, I'm blown away by the power of Webflow. Second, [changes z-index to make it first] your teaching is so brillant. It is exactly what's needed to make learning this complex subject fun!
As a developer understanding css position properties took me an entire day, as a designer I learnt it in 17 minutes watching this video! Thanks a lot! 👍
I've been trying to learn CSS properly for over 3 years now and I haven't heard a more simple and understandable explanation for positioning in CSS until this video
Man, You taught me which my University could not. You speak like scientists with confidenceand clear explanation without any off topic. Keep doing that, you have a new follower today. Thanks.
Where were you when I was at school? This is the way how teachers supposed to teach at schools. He just literally make learning so sophisticated-fun simple and no painful at all. Thank you!
Excellent content and presentation. Well planned script, wry comments. Far better than the previous video I watched, with a guy seemingly winging it by demonstrating technique with no explanation. When/if I get through all this, I can get back to ST Insurrection.
Really well explained with great examples. Very straight faced delivery had me confused until the very straight faced jokes were introduced which I loved. Informative, intelligent AND Funny. Loved it 🤩🤩
I'm enjoying and learning from these videos, but I have to say you guys run through the content REALLY fast. I know it's a "Crash Course" but it's faster than I can even take notes and comprehend fully at the same time. I have to go back over and over again to re-listen to the same info to make sure I'm taking accurate and relevant notes. Slowing down via the playback speed settings in RU-vid helps a little, but it's more an effect of how the videos were devised to be paced in the first place. Very little "white space" to use a design term.
4:25 Why? Why must a parent section be set to 'relative' in order to get its child element (that's set to 'absolute') to stay within its bounds? He seemed to have given what _he_ thought was a solid explanation for this maneuver's logic, but my head is still spinning. Yes, I understand what relative positioning is/does. I don't see why a section must be positioned relatively (within the body) simply in order to "trap" an absolutely positioned child element within itself. What's the logic? Thanks!
i get nervous changing a bunch of things to relative, but now i'm wonder why isn't everything just relative by default for more control. typically things are built relative to one another so the exception is when they ignore their surroundings.
There are a few reasons why static is the default position value for HTML elements: Simplicity and predictability: Setting elements to static ensures that they follow the natural flow of the HTML document. This makes it easier for developers to build web pages without needing to explicitly define positioning for every element. Performance: The static position doesn't require any calculations or rendering adjustments, so it can be rendered more efficiently by the browser. This is particularly important for performance-sensitive scenarios, such as when rendering large web pages or complex layouts. Accessibility: The default static positioning helps ensure that web pages remain accessible to assistive technologies, such as screen readers. These technologies rely on the document flow to provide a meaningful reading experience, so altering the default positioning could potentially disrupt that experience. While static is the default position value, developers have the flexibility to change it to other values such as relative, absolute, fixed, or sticky. These alternative position values allow elements to be positioned in different ways, enabling more complex and customized layouts on web pages.
The fixed position sometimes doesn't work on elements,,,when i set some elements to fixed position, they tend to move to the top of the page and scroll out of view,,,i don't know what I'm doing wrong,,please i need assistance
@@shubhamparekh9808 You can check the video channel suggested above, since it also shows you how to display stuff that is saved in Firebase database. I have a programmer that connected my project to Firebase, a little complicated if you don't know coding. At the beginning we used glitch.com did all the configuration there and then pasted a javascript file inside Webflow custom code. Now we are using webpack
This is so cool. On my blog, I have a LOT of absolute and relative positioning, and I have been told not to use it often. I'm so stuck on this, and not sure what else to do. It's a 3 column layout blog. Any advice?
@Webflow @9:33 When i place the child dive block inside 80% of dark opacity dive block , the child element also inherit the 80% opacity so how to fix the child element opacity to 100%? In the Opacity effect the child opacity is 100% but visually its opacity is also 80% means all the body is shown behind both the parent and child element.
How has Webflow managed to teach something that had potential of becoming dreadfully boring & dry, but instead has turned it into a comical, educational and interesting piece...!!!