Before you start to think about the technical way building a responsive project, make yourself clear, what responsive basically is and why we do this.
Some basic things worth to mention:
-
A responsive page neither knows width nor height. This is just because a sizes are defined in relative units.
-
Because you can use 100% of device width, you’re able to bump up font-sizes from 13px to min. 16px. Build grids where some parts perhaps take 2/3 others 1/3 or whatever.
-
Webdesign is a matter of semantics. It’ll mean that a page preferably starts with an outline which tells a story for maximum UX.
-
No inner scrolling anymore!!! Yep - it’s redundant at all. Why? A page doesn’t know a height. If you need scrolling - do it, but leave it with the user - and don’t make this a designer’s decision (constraint)
Pull out ol’ Photoshop (or similar) and try to quick setup your page you want to make adaptive in a doc-size of let’s say 320px wide and whatever height). You definitely need to re-arrange and re-size your items, right? Well - something similar you would do in Freeway as well.
But you may recognize that your “design” isn’t really worth to think about making it responsive - this MAY happen.
For best working projects, you anyway need to switch your construction method from “drop&drag” to full inflow (inline aka BoxModel). And there we are:
Wether you choose Backdraft (as a Framework builder) or a template (As Is) - both are helping you getting the gist of the technical requirements.
Review you strategies both way:
Design and Code - literally!
Finally my judge to the OP’s question:
It is NOT possible to convert a project from static to dynamic!!! This judge is from investigating hundreds of Freeway projects.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at: