i'm been coding web for about 14 years. But i keep watching videos like this because you never know what you might learn... your font size clamp() is an amazing tip, thank you very much
I started building websites in 1995. We had HTML 1. CSS didn't exist yet etc. I was one of the pioneers of what is now called "responsive web design" in the CSS 2 era. We called it "Fluid Design" and we used tables and parts of tables etc with sizes in percentages of screen width, and some used tons of "simple" (if you called 30000 characters of javascript to detect a screen size simple). to detect screensizes and re-sized elements in the DOM and/or serve different layouts to different devices. Thank goodness it's not like that still. But it was cool being able to do what "couldn't" be done.
Same as you. Started in 1995 and used Tables and tables in tables plus s. The advent of mobile devices destroyed pure website design. Desktops are different from mobile screens so we now have to jump through hoops to get something which is barely okay but not outstanding. Before mobile I could make a page be whatever with little effort and I enjoyed the process making literally many thousands of webpages in few years.
I started somewhere around 2002. CSS was a thing. I loved development back then, and loved it into 2015 or so while responsive took over. Then came the dark era of javascript frameworks and intentionally making everything more difficult for job security. What a horrible phase we went through. Thank god things are moving back to sanity.
@@WyzrdCat I hear you! Like compiled Javascript. Like javascript (react, vue, etc) wasn't complicated enough. And most of the time there's just no benefit to using it unless your project is huge.
I created a 4 hour course on Tailwindcss on my channel - I have to admit that to know CSS is not that easy and even after years of coding! CSS is so wide. Thanks for this video!
I wish I could have some AI that would just completely delete the content of absolutely everything that ever mentions Tailwind so I never have to see or think about that abomination
Hi Kyle, just in case you are finding a topic for your next videos, please talk about product filter (and filter by multiple categories including price, brand, time) using javascript
Great content, as always. I'd just like to point out that having a different (simplified) html for a mobile device shall not be recommended ever. It's due to accessibility. All the content should be available regardless on the device type of it's properties. We should not think on terms of desktop and smartphone. The smartphone view is sometimes just highly zoomed site, or split screen view. You don't want users to lose the content on those cases. This is actually in WCAG
I'm intrigued and fascinated by your school of thought. Why? Because I am constantly saying the opposite to what you said above. I believe the contrary. That you MUST factor in the device and its screen size constraints. Its common sense that the user-experience and online-shopping experience you get on beautifully designed fashion eCommerce webstore website that you view on that huge 27 inch 16:9 ratio monitor, will not be replicated on a tiny little screen. That is simply impossible. Bigger canvas to play around with, so you can show more of the dom on a screen as opposed to on a tiny screen. This is one of the core reasons for responsive design - you have to 'optimise' a web layout for the particular device as to ensure the user experience is still great and the user end goals are still achieved with considerable ease. I could go into more detail but I won't. I will say that web layouts and web software UI's will naturally need to be scaled/watered down in terms of detail when it comes to devices with smaller screen sizes.
@@The-Great-Brindian This is the difference between responsive and adaptive design. Responsive design should be strived for - that is, having the same DOM elements on both views and making them act differently on different screen sizes as opposed to adaptive design which would mean having two completely separated layouts and conditionally showing/hiding them based on screen size. The latter is bad because when a change is requested it means updating two layouts rather than one which is why responsive is the preferred approach. However, I've had many situations where certain elements are desktop or mobile only. I think it's fine as long as you're not replicating large portions of your UI to have a mobile and desktop specific markup.
I think this CSS Grid concept is more stable and better than flex wrap cuz it adjusts the element size as well besides the number of items per row. Amazing.
And great to customize the cell to be the width and height you want that cells’ contents to be. And grid is animatable! I’m still struggling a bit with learning grid but I’m definitely coveting all its features and will master it one day!
Thanks for helping me change my life. I watch your videos every day and I wouldn't be anywhere near where I'm at right now, as basic as that is, if it wasn't for you. Happy New year and best wishes
The Grid method with auto-fit is such an insanely powerful technique and basically negates any media queries for MOST of the reasons you need them for, which is usually going down in column-count as the screen narrows.
Your content is teaching me a lot, on point and well done. I do want to mention that although you later added a note to correct the "siderbar" typo, your tutorial was displaying the red and purple boxes incorrectly. I wrestled with this and could not figure it out until I walked away and later it came to me that your display wasn't matching mine because I didn't have the "siderbar" typo. Without the "siderbar" typo, only the red box displays over 600px because it is in a separate div on the html page. Thanks...; )
Just yesterday I posted a video about the Top 10 CSS Features you should know and use in 2023 and clamp() is also a part of it... I explained it a little bit more in detail => maybe this will help you ... 😉
ปีที่แล้ว
Just tried working with dvh on a project, and alas, Safari on iPhone XS does not like it. But this was an immensely informative video, thank you!
Omg I am first one viewer it seems 😎😎😀. This is great channel which I followed recently . A worthy channel to subscribe with great content. Love from India🇮🇳🇮🇳🇮🇳
Thanks to things like grid, flex, and clamp there is barely a reason to touch media queries outside of things like dark/light mode and the like. There are still uses when you have to make something pixel perfect (equals seems nice for pixel perfect) or to change a grid system based on current width. PS: If you have to make something pixel-perfect, it is not worth anyone's time due to it just adds extra development time that is not needed.
The most frustrated thing for FE dev is supporting for old browsers and devices. Looking at these new amazing features and having to wait for years to use it.
Maybe once iOS 18/19 is out it'll be OK to drop support for iOS 15 and use container queries, but it'll be a couple of years until then, I don't think earlier than that is reasonable for production.
Great Video!. Please do I need a viewport for react, If yes how do I do it? I am a beginner and my web-page is responsive on my desktop chrome browser but not on different mobile screens when I inspect the page. Thank you.
Thanks Kyle. Not sure if you have addressed this before but can you do a video on the best way to jump to a location on a webpage. One thing that affects the jump destination location is a fixed top menu or header. What is the best method for making the scroll to / anchors work reliably every time.
The id you're using for your anchor can be selected in CSS and then you can implement a property called scroll-margin-top. Give it the right number of pixels and voila, it looks immaculate.
Most of those defy the *cascade* style sheet (aka css) principles. You should define the main rule then define the exceptions, instead of defining a bunch of different rules.
i'm been coding web for about 14 years. But i keep watching videos like this because you never know what you might learn... your font size clamp() is an amazing tip, thank you very much
What is your package as web developer. Can i know..?
same, there is always a new trick to learn
@@indiancuriousvoice8773 I started on Dreamweaver so I got used to it
@@indiancuriousvoice8773 You mean what's his stack?
I started building websites in 1995. We had HTML 1. CSS didn't exist yet etc. I was one of the pioneers of what is now called "responsive web design" in the CSS 2 era. We called it "Fluid Design" and we used tables and parts of tables etc with sizes in percentages of screen width, and some used tons of "simple" (if you called 30000 characters of javascript to detect a screen size simple). to detect screensizes and re-sized elements in the DOM and/or serve different layouts to different devices.
Thank goodness it's not like that still. But it was cool being able to do what "couldn't" be done.
Same as you. Started in 1995 and used Tables and tables in tables plus s. The advent of mobile devices destroyed pure website design. Desktops are different from mobile screens so we now have to jump through hoops to get something which is barely okay but not outstanding. Before mobile I could make a page be whatever with little effort and I enjoyed the process making literally many thousands of webpages in few years.
@@homevids Personally I think the biggest negative influence on the design side of web design is google.
@@texxs01 Absolutely 100%
I started somewhere around 2002. CSS was a thing. I loved development back then, and loved it into 2015 or so while responsive took over. Then came the dark era of javascript frameworks and intentionally making everything more difficult for job security. What a horrible phase we went through. Thank god things are moving back to sanity.
@@WyzrdCat I hear you! Like compiled Javascript. Like javascript (react, vue, etc) wasn't complicated enough. And most of the time there's just no benefit to using it unless your project is huge.
Happy new year to yall developers out there
#dontdeployanythingtoday
@@sahilaggarwal2004 😂
Make videos #react native
DEVELOP DEVELOP DEVELOP
What's yall? Is it Ecma based?
I created a 4 hour course on Tailwindcss on my channel - I have to admit that to know CSS is not that easy and even after years of coding! CSS is so wide.
Thanks for this video!
I wish I could have some AI that would just completely delete the content of absolutely everything that ever mentions Tailwind so I never have to see or think about that abomination
More of these videos about responsiveness! This is my weakest point.
@@FdWebdesign bruh
Thank you for including the bit about the meta tag, nobody else seems to mention that and it wasn't working for me until I put that in !!
grabe, ibang klase ka tlaga mag explain kyle.. magaling ka talaga.. maraming salamat
Hi Kyle, just in case you are finding a topic for your next videos, please talk about product filter (and filter by multiple categories including price, brand, time) using javascript
Great content, as always. I'd just like to point out that having a different (simplified) html for a mobile device shall not be recommended ever. It's due to accessibility. All the content should be available regardless on the device type of it's properties. We should not think on terms of desktop and smartphone. The smartphone view is sometimes just highly zoomed site, or split screen view. You don't want users to lose the content on those cases. This is actually in WCAG
I'm intrigued and fascinated by your school of thought. Why? Because I am constantly saying the opposite to what you said above. I believe the contrary. That you MUST factor in the device and its screen size constraints. Its common sense that the user-experience and online-shopping experience you get on beautifully designed fashion eCommerce webstore website that you view on that huge 27 inch 16:9 ratio monitor, will not be replicated on a tiny little screen. That is simply impossible. Bigger canvas to play around with, so you can show more of the dom on a screen as opposed to on a tiny screen. This is one of the core reasons for responsive design - you have to 'optimise' a web layout for the particular device as to ensure the user experience is still great and the user end goals are still achieved with considerable ease.
I could go into more detail but I won't. I will say that web layouts and web software UI's will naturally need to be scaled/watered down in terms of detail when it comes to devices with smaller screen sizes.
@@The-Great-Brindian This is the difference between responsive and adaptive design. Responsive design should be strived for - that is, having the same DOM elements on both views and making them act differently on different screen sizes as opposed to adaptive design which would mean having two completely separated layouts and conditionally showing/hiding them based on screen size. The latter is bad because when a change is requested it means updating two layouts rather than one which is why responsive is the preferred approach. However, I've had many situations where certain elements are desktop or mobile only. I think it's fine as long as you're not replicating large portions of your UI to have a mobile and desktop specific markup.
I think this CSS Grid concept is more stable and better than flex wrap cuz it adjusts the element size as well besides the number of items per row. Amazing.
Agreed! Grid is more stable and predictable than flexwrap. It's just really easy to get into trouble with flexwrap.
And great to customize the cell to be the width and height you want that cells’ contents to be. And grid is animatable! I’m still struggling a bit with learning grid but I’m definitely coveting all its features and will master it one day!
You are frikken brilliant! Everything is always overly complicated when its actually straight forward. Thank you!!
This chan has become my favorite waterhole for the daily brushup on CSS and HTML, super cool !
Every video of yours is on another level. hats off to you bro..
Thanks for helping me change my life. I watch your videos every day and I wouldn't be anywhere near where I'm at right now, as basic as that is, if it wasn't for you. Happy New year and best wishes
The Grid method with auto-fit is such an insanely powerful technique and basically negates any media queries for MOST of the reasons you need them for, which is usually going down in column-count as the screen narrows.
I used the media method, but after I tried the viewport, it was much better and saved a lot of effort
Thanks for the vid. When writing stylesheets SASS is still king when it comes to simplifying css. @container is something I've prayed for for years.
As always a great video with tons of new(er) stuff. BTW is there a reason you don't use and tags in the container section?
thanks a lot for this very useful video, it's absolutely incredible how CSS has been changing...
This is great. I found this just on-time when I was asked to convert the web site I'm working on to mobile friendly. Thank you. 🙂🙂
Thx a lot u have been contributing many things into front end development.
I LOVE YOUR WAY OF EXPLANATION
Your content is teaching me a lot, on point and well done. I do want to mention that although you later added a note to correct the "siderbar" typo, your tutorial was displaying the red and purple boxes incorrectly. I wrestled with this and could not figure it out until I walked away and later it came to me that your display wasn't matching mine because I didn't have the "siderbar" typo. Without the "siderbar" typo, only the red box displays over 600px because it is in a separate div on the html page. Thanks...; )
Really it was something new for me as jr. Front-end developer.. thank you 😊 please explain clamp() in depth specially for font size if its possible.
Just yesterday I posted a video about the Top 10 CSS Features you should know and use in 2023 and clamp() is also a part of it...
I explained it a little bit more in detail => maybe this will help you ... 😉
Just tried working with dvh on a project, and alas, Safari on iPhone XS does not like it. But this was an immensely informative video, thank you!
this video is really amazing and knowledgeable thank you very much
Wow. I wish, you could write an in depth book about this. That would definitely be the Responsive Design Bible for at least a decade.
Great video, thanks for this! I've been battling mentally what is the best approach to mobile responsiveness - seems you answered my questions!
Really awesome approach. I will use it when the support is there for it!
this information about responsive css kind of advanced. thank you for sharing this valuable info🙂
Love ur content, brother from 🇮🇳. Your videos are really helpful in becoming a full stack web developer.
1st time I watch your video Now I am happy to see your content your content was amazing & very useful Thank you so much
Loved the grid and the font-size clamp()! This just saved me a lot of time.
Just found this video. The grid is exactly what I needed! 👍
Thank you for the video!!! We learn a lot with you! Thank you!
im learning and wating for some good resource to solidify my knowledge about responsive design and then I got this video wow
First 2 mins. and you helped me solved my problem already.
Happy new year, Kyle! Excited to see what 2023 has for us! ❤
Thanks, bro. Some real problem solutions from this video
Very helpful. Clear presentation style. Simplifying the complex. Good job.
Is that a Jackson Dinky back there? I like your style; one of the most prolific metal strats, juxtaposition to a family throw pillow. 🤘
You are so fast, I am amazed! Thumbs up.
I can't get @container query working in VS. such as Firefox or Chrome testing environment. Kevin showed a similar video using container Queries.
Thank you!!! Just Amazing and so helpful!!!!
Another good concept and great explanation. One topic we're interested in is on designing flexible layout which works with ads and content.
Muchas gracias. Qué buenos conceptos. Many thanks. 💯👍
Please make a course on responsiveness 😭
I didn't know about auto-fill, Thanks!
I’m always blown by your videos
Love your content bro ❤❤
Thank You
Happy New Year
Thx for your videos bro really helpful
Thank you.. i will helps me alot... Thanks 🙏
This dude is a champ.
Very useful, so I subbed! Thanks!
How do you get the screen size numbers in the top of your website preview? It looks so practical
Muy interesante y actual... lo que no te enseñan los profes...
Incredible work
Omg I am first one viewer it seems 😎😎😀.
This is great channel which I followed recently .
A worthy channel to subscribe with great content.
Love from India🇮🇳🇮🇳🇮🇳
Thanks to things like grid, flex, and clamp there is barely a reason to touch media queries outside of things like dark/light mode and the like.
There are still uses when you have to make something pixel perfect (equals seems nice for pixel perfect) or to change a grid system based on current width.
PS: If you have to make something pixel-perfect, it is not worth anyone's time due to it just adds extra development time that is not needed.
The most frustrated thing for FE dev is supporting for old browsers and devices. Looking at these new amazing features and having to wait for years to use it.
(Safari)
@@johanneskingma and then monopolize their engine on IOS and PadOS 🙃
Shoutout to Kyle for getting some furniture in his room
Happy new year 💚🇳🇵
what browser are you using.
your customizable width controls are very nice
how can i get those?
When does media query range added? Also, where can I see updates about CSS?
You’re a great teacher man 🫂
HOLLY COW!!!😳😳😳😳
This video opened my eyes wide which were like buttonholes!!
Assalomu aleikum. usefull video. thank u bro. subscribed :)
You are really awesome man , keep going
Gold content, as always, especially that grid part.
Excellent content 🙏🏻❤️ Thanks!
Happy new year
Random Question.. What keyboard is being used in these videos? The typing sounds very satisfying 😅
Кайл, спасибо за ролики!
Great insights!
Maybe once iOS 18/19 is out it'll be OK to drop support for iOS 15 and use container queries, but it'll be a couple of years until then, I don't think earlier than that is reasonable for production.
Great Video!. Please do I need a viewport for react, If yes how do I do it? I am a beginner and my web-page is responsive on my desktop chrome browser but not on different mobile screens when I inspect the page. Thank you.
All your videos are so nice
18:41 - font-size clamp
Thanks Kyle. Not sure if you have addressed this before but can you do a video on the best way to jump to a location on a webpage. One thing that affects the jump destination location is a fixed top menu or header. What is the best method for making the scroll to / anchors work reliably every time.
The id you're using for your anchor can be selected in CSS and then you can implement a property called scroll-margin-top. Give it the right number of pixels and voila, it looks immaculate.
How many different background setups did you go through before you settled on an electric guitar and family-pillow?
It's a real eyeopener
Would clamping using the 3vw allow the zoom to work?
Thanks for share!
Happy new year!
Thank you so much🎉
Happy new year 🎉
Bro please create a responsive website I Love Your Teaching
best explanation
ohh, clamp is fr cool thing
Most of those defy the *cascade* style sheet (aka css) principles.
You should define the main rule then define the exceptions, instead of defining a bunch of different rules.
Brave is as same as chrome (expect that it blocks ads in youtube) right? so if Chrome gets support Brave too will do right?
did you miss the card for container queries? I don't see it on my device
I didn't see it either, but check out his video called "Responsive CSS Will Never Be The Same" for a deeper dive on container queries!
Bro how are your videos this good
I remembered Clamp not working well in Safari ?
Should be working without any problems by now... 😉
You are the best!
Thanks for the informations
You can usually get a site to be like 95% responsive by just not setting hard widths
Hello my friend! Happy new year!
Do you allow me to record reacts from your videos IN PORTUGUESE?
Always mentioning your channel.
Can the @custom-media be defined outside of the css file but still apply to it? Juste like css variables.