This is a web design method directed at crafting sites to produce a viewing that is ideal reading and navigation with a minimum of resizing, panning, and scrolling—across many products (from cellphones to computer screens).
A website designed with RWD adapts the design to the watching environment by utilizing liquid, proportion-based grids, flexible images, and CSS3 media queries, an expansion associated with @media rule.
The substance grid concept calls for web page element sizing to stay in relative devices like percentages, and not absolute units like pixels or things.
Flexible images are also sized in general units, to prevent them from showing outside their containing element.
Media queries allow the page to use CSS that is different style based on attributes for the unit your website is being displayed on, mostly the width of the browser.
Mobile first, unobtrusive JavaScript, and enhancement that is progressive
“Mobile first”, unobtrusive JavaScript, and enhancement that is progressive strategies for when an innovative new web site design is being considered) tend to be related ideas that predated RWD: browsers of fundamental smartphones don’t realize JavaScript or media inquiries, so the advised practice is to create a basic internet site, and enhance it for wise phones and PCs—and not try graceful degradation which will make a complex, image-heavy web site focus on the standard mobile phones.
Progressive improvement according to browser-, feature-detection or device
Where an internet site must help standard mobile phones that lack JavaScript, browser (“user agent”) recognition (also called “browser sniffing”), and device that is mobile are a couple of methods for deducing if certain HTML and CSS features are supported (as a basis for modern enhancement)—however, these methods are not totally dependable unless used in conjunction with a device abilities database.
For lots more capable phones that are mobile PCs, JavaScript frameworks like Modernizr, jQuery, and jQuery Cellphone that may directly test browser support for HTML/CSS features (or figure out the device or user agent) are popular. Polyfills could be used to include help for features—e.g. to guide media queries (necessary for RWD), and enhance HTML5 assistance, on Internet Explorer. Feature recognition also may not be totally reliable: some may report that a feature is available, if it is either lacking or so badly implemented it is successfully nonfunctional.