David Hund

There are so many good resources I believe simply mentioning 'Mobile First' would help people out. A quick google: - http://www.html5rocks.com/en/mobile/responsivedesign/ - https://adactio.com/journal/4494/ - http://www.smashingmagazine.com/2011/08/10/techniques-for-gracefully-degrading-media-queries/

@jaimerod Sure: some clients will not accept a mobile layout for IE8 but this does _not_ mean you should build desktop-first… Build a mobile-first app to keep things lightweight and...

I see where you are coming from, @israelidanny, but disagree with your assumptions. You mention that _"Most people would expect desktop design on a desktop screen, be it whichever browser."_...

I guess something like: > "No support for Media Queries. CSS in Media Queries will not have any effect." and then below you could mention PE/Mobile-first together with the polyfills...

Yup, I'll see what I can do.

Another thing re:fallbacks would be to check for known polyfills. You warn against the HTML5 sectioning elements, but many pages include e.g. Modernizr. These elements are no issue then.

Yeah, checking for polyfills can get cumbersome. However, some of these—such as Modernizr and html5shiv (even the h5BP `.oldIE` classname)— are so widespread it would be less of a hassle...

That would help. The thing is that the page quickly gets quite large and in all this text it's hard to scan. With 'in-/exclude' I simply meant a filter in...

@dkniffin What do you think, should we add _libraries_ such as [Just](https://github.com/angus-c/just) or [AlpineJS](https://github.com/alpinejs/alpine) (and _many_ others) or keep this focussed more on _util_ scripts?

True. My thought was that explicitely 'Vanilla' libraries could be helpful. Stand-alone modules are probably overkill