Responsive Design Magazine

The Responsive Design Magazine

The magazine's website is also a shining example of integrative design. magazine. Everything started with Responsive Web Design, an article by Ethan Marcotte on A List Apart.

Limitless downloads: 500.000+ HTML5 templates, fonts, photos & design assets (ad)>

After all, it's virtually indispensable: one design for the BlackBerry, another for the iPhone, iPad, Nettbook, Kindle - and all display resolution must also be compliant. Over the next five years we will probably have to plan a number of other invention. After all, it's virtually indispensable: one design for the BlackBerry, another for the iPhone, iPad, Nettbook, Kindle - and all display resolution must also be compliant.

Over the next five years we will probably have to plan a number of other invention. When it comes to web design and web design, we quickly reach the point where we can't keep up with the never-ending new resolution and device. Which is Responsive Webdesign? Responsible Web Design is the concept that proposes that design and engineering should be responsive to the user's behaviour and surroundings according to display area, platforms and alignments.

Practical experience includes a mixture of flexibly arranged grid and layout, pictures and an intelligently use of appropriate content management. When users move from their laptops to iPads, the website should change itself to adjust screen resolutions, picture sizes, and scripts. This means that the website should have the necessary technologies to react spontaneously to the user's preference.

As a result, there is no need for a different design and engineering stage for each new product on the shelves. Meet Smashing Book 6 - our latest edition, which focuses on true front-end experiences in the field: from design tools and barrier-free applications to CSS Custom Properties, CSS Grid, Service Workers, Performances, AR/VR and responsive Arts Management.

Marcotte Ethan has written an opening paper on the Responsive Web Design for A List Apart concept. The concept is based on the concept of fast-reacting Architecture, in which a room or room adapts itself to the number and flux of human beings in it: "Recently, an emerging field known as responsive architecture has started to ask how bodily environments can react to the human being' s being there.

" Translate this disciplin to web design, and we have a similar but completely new notion. After all, don't architect designs a single edifice for every group and every kind of person that walks through it? Just like the reactive architechture, the web design should also adapt itself as well.

Responsible web design demands a more abstraction way of thought. A few basic concepts are already being practiced: flowing layout, querying your press, and scripting that can easily re-format and (or automatically) highlight web pages. However, responsive web design isn't just about customizable display resolution and automatic scalability of pictures, it's also about a whole new way of designing.

And with more equipment, different display resolution, definition and orientation are added. Every single day, there are new machines being designed with new display screens, and each one can cope with fluctuations in terms of scale, function and even colour. What is the best way to deal with these kinds of situation? Besides the design for vertical and horizontal format (and the possibility that these orientation can change in no time when loading the page), we have to take into account the hundred different display heights.

Yes, it is possible to divide them into main catagories, to design for each of them and to make each design as adaptable as necessary. In addition, many people don't maximise their browser, which in turn allows far too much room for the diversity of display heights. Some years ago, when flexibility in website design was almost a "luxury" for a website, the only things flexibility in design was the structure and text.

Pictures could crack open laidouts with ease, and even rigid structure items cracked the shape of a page if they were pressed sufficiently. They were not really that agile; they could give or take a few hundred pixel, but they often couldn't get from a large computer monitor to a laptop. We can now make things more agile.

Pictures can be adapted and we have work-arounds so that layout never breaks (although it can get crushed and unreadable). It' great for a device that can instantly change from vertical to horizontal format, or when a user switches from a large computer display to an iPad.

Take a look at the design of the logotype, for example: Choosing a too small file will result in a poor picture but it was important to keep the website name in view rather than cutting it off. Thus the picture is split into two parts: one (of the illustration) as wallpaper to be trimmed and retain its original dimensions, and the other (of the name) proportionately enlarged.

" "At the top, item hr1 keeps the artwork as the backdrop, and the picture is oriented according to the backdrop of the box (heading). These are just a few examples of the kind of thought that makes responsive web design really work. Even with such intelligent corrections, a lay-out can be too tight or too brief to look right.

A big issue that needs to be resolved with reactive web design is working with pictures. A number of different methods exist to proportionally change the sizes of pictures, and many of them are simple to realize. One of the most favorite options mentioned in Ethan Marcotte's essay on liquid pictures, which Richard Rutter first explored, is to use the maximum width of the CSS for a simple correction:: ; As long as no other width-based picture style overrides this rules, each picture will be loaded at its initial magnification, unless the view area becomes smaller than the initial width of the picture.

Sets the maximal width of the picture to 100% of the width of the monitor or web page, so that if it becomes 100% smaller, the picture will be as well. In essence, as Jason Grigsby remarked: "The concept behind liquid pictures is that you provide pictures at the maximal scale in which they are used.

Instead of declaring the width and width in your HTML file, you let the web-browser adjust the image sizes as needed, while using CSS to determine their respective sizes. It is a great and easy way to change the image sizes nicely. Notice that the maximum width is not allowed in IE, but a good use of the width: 100% would properly resolve the issue in an IE custom stylesheet.

Another problem is that if an picture is scaled too small in some older Windows browser's, the display is not as clear as it should be. Although the above points are a great fast fix and a good starting point for responsive pictures, picture definition and downloading time should be the most important consideration.

Whilst changing the picture sizes can be very easy for portable equipment when the initial picture sizes are intended for large equipment, they can significantly reduce downloading time and take up unnecessary diskspace. The technology introduced by the filament group addresses this problem by not only proportionally adjusting the pictures, but also reducing the picture definition on smaller equipment so that very large pictures do not take up unnecessary screen area.

First a JavaScript executable (rwd-images.js), the . chtaccess executable and an executable (rwd.gif). Then we can only use a little HTML to refer to both the higher and lower resolutions images: first to the small one with the suffix. r to make it clear that it should react, and then to the large one with data-fullsrc.

Every monitor that is broader than 480 pixel loads the picture with higher resolutions (largeRes. jpg); smaller monitors do not have to loads the large picture, so the smaller picture (smallRes. jpg) is loaded. A JavaScript filename adds a basic feature that allows the page to split appealing pictures and redirect them as needed.

If the page is uploaded, all data is written back to its initial form, and only the large or small pictures are uploaded on demand. Using other technologies, all pictures would have had to be download at a higher definition, even if the bigger version was never used. Especially for web sites with many pictures this technology can save a great deal of bandwith and load times.

The older browser and Firefox are deteriorating well and are still adapting to the size one would want from an appealing picture, except that both resolution are downloading together, so that the end use of this technology's savings in terms of size are eliminated. A great thing about the iPhone and iPod Touch is that web themes are scaled to match the small display.

Unless otherwise stated, a full-size design would only contract proportionately for the miniscule web browsers, without requiring a scroll or portable one. As the responsive web design began, many realized that the pictures were still in proportion to the page, even if they were made specifically for the small display (or could otherwise fit).

Due to Think Vitamin's articles about changing the size of pictures we have the meetatag below: "If you set the start dial to 1, the defaults will be overridden to change the size of the pictures proportionately, while keeping them as they are if their width matches the width of the unit (either landscape or portrait).

In case of large changes in sizes we can completely modify the lay-out, either through a seperate stylesheet or, more efficient, through a media request. It doesn't have to be tedious; most Styles can stay the same, while certain Stylesheets can come into those Stiles and move items with floating point numbers, latitudes, highs, and so on.

We could, for example, have a master stylesheet (which would be the default) that defines all important structure items, such as #wrapper, #content, #sidebar, #nav, along with color, background, and type. As standard, you can also specify floating-point numbers and variable lengths. When a stylesheet made the outline too small, too brief, too broad or too high, we could see that and change to a new stylesheet.

The new subordinate stylesheet would take everything from the standard stylesheet and then simply re-define the look and feel of the layouts. This is the standard format. Contents: ..... ... ...:::::::::::::::::::::::::::::: ; ; Here is the cell phone.

CSS content::::::::::::::::::::::::: ; ; CSS3 works with all the same type of files as 2. 1, like screens, printers and handhelds, but has added tens of new functions, such as maximum width, equipment width, orientation and colour.

Novel CSS3 manufactured peripherals (such as iPad and Android peripherals) will definitely provide full coverage of CSS3 hardware. Thus, invoking a request for access using CSS3 control mechanisms to control these gadgets would work well, and will be ignored if invoked from an older computer webbrowser that doesn't have CSS3 capabilities.

Ethan Marcotte's articles provide an example of a request from the press in action: "Getting this information is pretty self-explanatory: if the web browsers display this page on a monitor (and not printed, etc.), and if the width of the monitor (not necessarily the viewport) is 480 pixel or less, then download shetland.css.

For more information about adjusting and limiting bandwidths using these functions of the Orientation Matrix, see The Orientation Matrix Viewer. It is possible to make several stylesheets, as well as fundamental changes to the layouts, adapted to the width range - also for horizontal and vertical orientation. See the section of Ethan Marcotte's Meet the Media Queries for more samples and a more detailed discussion.

You can also store more than one query directly in a stylesheet, which is the most effective when used: you can also store them in a stylesheet: Below are some samples of how query functions might work for both 2.1 and 3. Let's now look at some special instructions on how to use CSS3 quizzes to build compelling web themes.

mind-width specifies a minimal width of the web page or monitor for which a certain range of different types of page widths (or a different stylesheet) would work. When something is below this boundary, the links or stylesheets are ignored. Everything that exceeds the specified max. width of the web page or monitor does not count for the corresponding medium request.

In the following samples, notice that we use the query language for medium requests, which can all be used in a stylesheet. Like I said before, the most effective way to use your requests for information is to place them all in a single stylesheet, with the remainder of the website styling.

In this way you don't have to set several requirements for more than one stylesheet.:::: ;: ; The category specified in the above medium request (hereIsMyClass) only works if the width of the web page or monitor is over 600 pixel. Meaning that this request will only be executed if the minimal width is 600 pixel (600 pixel or more).::::::: ; ; Now, using the maximal width, this request will only be executed for browsers or screens with a maximal width of 600 pixel or less.

Whilst the above minimum width and maximum width can be either the monitor width or the web width, we sometimes want a medium request that is specifically related to the width of the equipment. That means that even if a web browsing or other display area is reduced to something smaller, the retrieval still applies to the current unit area.

Minimum width and maximum width are excellent for retrieving certain units with preset measurements, without having to apply the same style to other display screens in a web browsing application that imitates the unit's own measurements.::::::::::::: ; For the iPad, there is also a retrieval feature named Orienti.

And there are also many press inquiries that are useful in combination. As an example, the minimum width and maximum width searches are constantly merged to define a unique styles for a particular area.:::::::::::::::::: The above access codes in this search apply only to screens and browsers between 800 and 1200 dots.

One good application of this technology is to display certain contents or whole side bars in a single format, according to how much room is available in the landscape. However, some design professionals would rather refer to a different stylesheet for specific types of press requests, which is okay if the organisational advantages are greater than the efficiencies wasted.

The use of a seperate stylesheet should be okay for those that do not change the alignment or for those that cannot change the width of their browsers by hand. For example, you can place container requests for iPad in a stylesheet (as above). Since such a gadget can quickly change from vertical to horizontal format when these two requests are placed in different stylesheets, the Web site would need to access each stylesheet every times the direction of the users changes.

It would be much more effective to place a request for both the iPad's portrait and landscape orientation in the same stylesheet would. A further example is a design for a default computer monitor with a size-adjustable web browsing interface. The best thing to do if the size of the web page can be adjusted by hand is to place all your variables in a stylesheet.

However, organisation can be the buzzword, and a Designer may want to specify requests for information in a default HTML links tag: "Another way that can be used is JavaScript, especially as a backup on a device that does not fully understand CSS3 polling capabilities.

Luckily, there is already a pre-built JavaScript libraries that allows older web browser (IE 5+, Firefox 1+, Safari 2) to handle CSS3 requests. When you are already using these prompts, simply get a copy of the libraries and add it to the markup: css3-mediaqueries.js. Below is also an example of a jQuery slice that recognizes the width of the web brower and changes the stylesheet accordingly - if you prefer a more practical approach:

: "it is possible to resize things proportionately and reorder items as needed to make everything fitting (reasonably well) as a display gets smaller. It' s great that this is possible, but it's not always the best response to make every item of large display available on a smaller display or portable devices.

An appealing web design shouldn't just be about how to make a custom look and feel on a variety of different plattforms and screens. Luckily, since many years now, using the CSS allows us to show and show contents with great simplicity!:: ; Either you define the display: none for the HTML blocks that have to be faded out in a certain stylesheet, or you recognize the width of the browsers and do this via JavaScript.

As well as concealing contents on smaller monitors, we can also conceal contents in our standard stylesheet (for larger monitors), which should only be available in portable version or on smaller equipment. With smaller units it is not necessary to keep the impact on the page - it only uses resource and can even lead to unneccessary scroll or change the format.

" "In our standard stylesheet below, we have faded out the link to the contents of the side bar. Since our monitor is large enough, we can show this contents when loading the page. This is the styling. Here is how it works. Standard contents:::::::::::::::::::::::: ; Now we fade out the two side bars (below) and show the link to these contents.

This is the handy one. Contents:::::::::::::: ; With the possibility to show and show contents simply, arrange layoutelements and adjust pictures, forms and more in size automaticly, a design can be converted into a multitude of screens in size and devices.

When your display gets smaller, reorder items to conform to your portable policies; for example, use a skript or alternative stylesheet to enlarge the whitespace, or substitute picture navigators on portable equipment for better ease of use (icons would be more convenient on smaller displays). Touchcreens obviously have different design rules than pure cursor-based interactions, and the two also have different abilities.

Luckily, it doesn't take much trouble to develop a design for both. Touch screens have no way to show CSS hover because there is no curser; as soon as the touch ing operator touch the monitor, they click. You can find more information in the section "Designing for Touchscreen". Much of the design proposals contained therein are best suited for touch screens, but would not necessarily affect cursor-based operability.

Doing so would make no distinction for the user of the cursors, so in this case we can also comply with the touchscreen design policy. In the following, we have some samples of responsive web design in today's world. Many of these sites have more differences in texture and styling than the two offered screen shots.

At the bottom of the first screenshots is a default size of the computer monitor. Website is adaptable with browsing sizes compared to conventional standards, but as soon as the web browsing becomes too small or otherwise moved to a smaller display unit, the page changes to a more legible and user-friendly design.

On a smaller display or web page, removing the side and top bars makes navigating easier and allows you to move directly across the contents, as well as the brand. The 8 Faces website design is versatile enough to work with a typical web book or chart recorder, and extends the amount of contents and width of layouts when displayed on larger displays or extended web browser displays.

Viewing on smaller monitors, the topic shown on the right is cropped, and the contents below are truncated and reordered in the design so that only the essentials are retained. Hicksdesign's website consists of three pillars when seen on a traditional computer monitor with a maximised web browsing experience. The third right hand side of the design is arranged above the second, and the logotype is moved next to the introduction text.

Therefore no contents must be deleted with the smaller area. With even smaller displays and browsers, the page contents are fully deleted and a streamlined view is pushed up. Eventually, the text will change with the width of the monitor and your browsers; if the browsers gets smaller, the text will become smaller throughout and remain proportionate.

This is a great example of a great picture. In this design, the picture changes size according to certain "breakpoints" but only the page borders and the surplus whitespace are changed between these width changes. The smallest design makes navigating to a drop-down list easy, perfectly suited to save room without compromising navigational cues.

Garret Keizer's website is completely adaptable in broader web widths and on bigger screens: the photograph, logotype and other pictures are enlarged proportionately, as are the headlines and text blocks. In some places, some text parts might be resized and become smaller as the monitor or web page becomes thinner.

At a certain breakpoint, the design turns into what we see in the second image below, with a plain logotype, opening text, and a plain vertically structured text for the rest of the work. By minimizing the size of the web page, or by placing the web page on a smaller machine, the column will be merged into two and then into one.

Similarly, the width of the line for breakpoints changes without affecting the width or styling of the caption text of each line. The CSS Tricks website, like many other foldable web design sites, has page bars with surplus contents that are the first to drop when the display or web page becomes too small.

In this particular site, the center row or first page row on the right was the first one to go missing; and the page row with the site's advertisements and tools did the same thing when the web browsers got even thinner. Finally, the design exits the post, consumes less whitespace around the nav and log, and shifts the seek toolbar below the nav.

Because of its ease of use, the rest of the design and lay-out is as adaptable as possible. You can see that the primary navigational feature here is the easy lay-out of t-shirt themes that extend both vertical and horizontal across the canvas. When your web browsers or screens get smaller, the column collapses and moves down.

At each breakpoint this happens when the layouts are loaded, but between breakpoints the pictures only resize proportionately. It keeps the design in equilibrium and at the same time ensures that the pictures (which are important for the website) do not become so small that they become inoperable. Another design that doesn't rely on altering the design tree according to specific breakpoints, Ten by Twenty facilitates responsive web design by making everything completely customizable and automatic in terms of scale, regardless of the width of the monitor or webbwser.

The design emphasizes a little after a while and could profit from a reorganization of the contents. However, overall, picture size adjustment and flexibility in contents allow for a relatively easy resolution that allows for a variety of display thicknesses. In widescreens and widebrowsers, all the contents of this easy website are well organised in column, side bar and easy to navigate at the top.

It is a fairly standardized and effective lay-out. This design retains its important hierarchical structure because room is at a premium. While we would look from right to left while on a broader display, we would look from top to bottom on a thinner one. The contents on the right side are shifted below the contents that would appear on a larger display on the other side.

The design is characterised by a sophisticated lay-out based on a printing technique. If you view it on a default widescreen, more portfolio items are displayed and stretched across the page in a horizontal direction. In a smaller display, the part of the product range is reduced to one and then completely omitted in very small displays and small browser sizes.

The design shows a imaginative and smart way to create an unusual lay-out with fast reactions. The design consists of three major steps, in which the design and lay-out change into a more user-friendly format according to how broad the display or webrowser is. Using a variable imaging technique, the size of the primary picture (with type) is proportional.

Every "layout structure" is fully bendable until it arrives at a breakpoint where the design changes to something more useful with less room horizontally. On the slimmest level of the design, navigating is super-simplified, and some non-essential contents are completely cropped. There is no modification of this lay-out at all, no deletion or rearrangement of contents, and no text resizing.

Instead, this design retains its initial shape, regardless of the variation in horizontally and vertically area. Instead, the size of the head picture and the pictures is adjusted to fit the navigational needs of the user. Whites, edges and upholstery are also flexibel and give more room as the design enlarges and diminishes. Perhaps the easiest example of a responsive web design in this case, but also one of the most diverse.

And the only part of the page that changes with the width of the web is the date of the posting that crosses the heading of the posting or goes to the page, according to how much room is available horizontally. All is centred to maintain a feeling of equilibrium regardless of the width of the monitor and your webcam.

Due to the ease of design, changing between web browsing and display width is fast and simple. Roberts shows that responsive design can also have quite modest applications. And Harry has also written an extensive essay about the style of style he added to the style sheet in his essay "Media Queries, handdier than you think".

Mehr zum Thema