At the beginning many people surprise about Responsive Web Design is of course the simplicity of syntax. As the Rich Quick said at its recent conference in Front Row intended to present the basic concepts: Obviously, it would be unthinkable for any self-respecting geek to hear such a statement, and he did not want to handle the extreme this famous line magic! What most of us discovers, beyond the technical introduction, there is an ocean of good practices to understand. They are covered very effectively in the now classic book "Responsive Web Design" by Ethan Marcotte, and many other online resources, including the excellent "Love your devices: adaptive web design with media queries, viewport and more" ( English) by Chris Mills, also available on the blog Dev Opera.
It is here that many stops. After all, much of the technical challenges of Responsive Web Design is more or less similar, regardless of the size and budget of the project. However, there are additional issues to consider on larger projects, which are only rarely discussed, and this article aims to present!
These challenges are primarily their origins in how roles and profiles typical of a web project mix on projects responsive heavier with graphic designers to understand the flow HTML and HTML integrators to make design choices graph. These problems will find their solution by reconsidering the roles that are assigned to each member of the project team, and adapting methods of communication within the team. But before detailing all this, let us ask some questions about our project!
Firstly, is it relevant that my project Responsive?
After your first experiments with media-queries, after which you will be convinced by their simplicity, it may be that you begin to imagine some of your favorite websites responsive version. It may also be that you surpreniez to think that everything should be responsive, you'd think maybe make your friends and family responsive if you could!
Unfortunately you will have to take a step back: depending on the context and purpose of a project, it may be preferable not to consider the option of all responsive. There is no simple and universal able to give you an obvious answer. Several points should be taken into consideration. Here are some questions you should ask yourself before you record a decision with your client.
Each of my versions will she the same content and the same functionality?
For accessibility reasons, try to limit the masking features between the different versions. Assume that each of your features should be available, and even if some of them are highlighted in either of your versions, none of should be concealed.
In responsive, users do not choose the mobile version of a site, it is you who are imposing. But what happens when he want to use a feature version of the "Desktop"? You can play with the visual hierarchy of your components on the page, but do not try to hide them. If you are asked to integrate a feature only for mobiles, then it may be time to consider creating a mobile version of your website.
If you choose to still hide some features, then consider a switch to "desktop version" / "Smartphone Version", which can deactivate / reactivate the media-queries, using javascript.
Some pages on a version they will have to be divided into multiple pages on one another?
There are some requirements for which can not responsive much to you, for example in cases where you have a page on a version that would be more affordable if split into multiple pages on a smaller version. Take the Facebook home page, for example, which contains among other things a detailed navigation, two data streams live, and instant messaging. Are you sure you want to appear these on your home phone? Hm, it would be clearer to separate these features on multiple pages, do not you think? For heavy content sites, make responsive single can make your page overloaded and completely unusable! If the rule "one page page = 1" does not work (and you can not simulate it in JavaScript), then responsive does not help you much, and it may be more appropriate to create a separate site.
Read Responsive Web Design from the perspective of the project manager Part 02
It is here that many stops. After all, much of the technical challenges of Responsive Web Design is more or less similar, regardless of the size and budget of the project. However, there are additional issues to consider on larger projects, which are only rarely discussed, and this article aims to present!
These challenges are primarily their origins in how roles and profiles typical of a web project mix on projects responsive heavier with graphic designers to understand the flow HTML and HTML integrators to make design choices graph. These problems will find their solution by reconsidering the roles that are assigned to each member of the project team, and adapting methods of communication within the team. But before detailing all this, let us ask some questions about our project!
Firstly, is it relevant that my project Responsive?
After your first experiments with media-queries, after which you will be convinced by their simplicity, it may be that you begin to imagine some of your favorite websites responsive version. It may also be that you surpreniez to think that everything should be responsive, you'd think maybe make your friends and family responsive if you could!
Unfortunately you will have to take a step back: depending on the context and purpose of a project, it may be preferable not to consider the option of all responsive. There is no simple and universal able to give you an obvious answer. Several points should be taken into consideration. Here are some questions you should ask yourself before you record a decision with your client.
Each of my versions will she the same content and the same functionality?
For accessibility reasons, try to limit the masking features between the different versions. Assume that each of your features should be available, and even if some of them are highlighted in either of your versions, none of should be concealed.
In responsive, users do not choose the mobile version of a site, it is you who are imposing. But what happens when he want to use a feature version of the "Desktop"? You can play with the visual hierarchy of your components on the page, but do not try to hide them. If you are asked to integrate a feature only for mobiles, then it may be time to consider creating a mobile version of your website.
If you choose to still hide some features, then consider a switch to "desktop version" / "Smartphone Version", which can deactivate / reactivate the media-queries, using javascript.
Some pages on a version they will have to be divided into multiple pages on one another?
There are some requirements for which can not responsive much to you, for example in cases where you have a page on a version that would be more affordable if split into multiple pages on a smaller version. Take the Facebook home page, for example, which contains among other things a detailed navigation, two data streams live, and instant messaging. Are you sure you want to appear these on your home phone? Hm, it would be clearer to separate these features on multiple pages, do not you think? For heavy content sites, make responsive single can make your page overloaded and completely unusable! If the rule "one page page = 1" does not work (and you can not simulate it in JavaScript), then responsive does not help you much, and it may be more appropriate to create a separate site.
Read Responsive Web Design from the perspective of the project manager Part 02
আপনার জন্য আরও ভয়েস
Ads by Tech Voice
Do not use HTML in your comments. Thanks for comments........... ConversionConversion EmoticonEmoticon