Top 10 Advanced CSS Responsive Design Concepts You Should Know 

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

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.

#dontdeployanythingtoday

@@sahilaggarwal2004 😂

Make videos #react native

DEVELOP DEVELOP DEVELOP

What's yall? Is it Ecma based?

@@FdWebdesign bruh

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!

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

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.

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 ... 😉

I remember when I first started learning programming I intuitively thought that something like that should work and tried using it and got confused. It actually won't throw errors (at least in JS and Python) but if you do something like 3 > 2 > 1 what happens is that 3 > 2 evaluates to true and then you get true > 1 which coerces the true into a 1 so you end up with 1 > 1 and the whole expression evaluates to false. Just throwing this out there in case anyone else gets curious. I think this is an inherent limitation in how basically all languages are implemented and so operators like AND and OR are required.

This guy actually named his account WDS enjoyer

@@alekkrstic Just fan things