Add in my various hand crafts and its many directions to follow. The fact that the program is sold as one where html knowledge is not necessary (but often really is) is something I have to deal with, but it doesn’t mean I’ll develop an encyclopedic knowledge of code or the best contexts for its variations. Our being at different levels for different things is not so bad. We all contribute what we have and keep up with what we can. I’ll bet not many will curl up with a good book on code too often.
Did you HAVE to remind me about that crud that built up in Typositors and stat machines!? But I didn’t mind pasteups, mechanicals and specing type.
The key to make modern rock solid layouts is to nest HTML-items (which could be also called DIVs). Such a DIV could be seen as singular table-cell but with way more opportunities to control them (position, width, height, margin, padding, float …)
While this sounds super strange and code cracking, in fact it isn’t. Especially Freeway offers all necessary tools to keep this construction method WYSIWIG with NO coding knowledge required. All the above mentioned terms (or properties) are available in the INSPECTOR.
Why nesting them?
You already said it:
Super busy pages with unexpected heights (content) require items that can react on each other.
This aka Freeways’ Box-in-Box Model has only one downside:
It requires a certain amount of practice to get in.
Ruby is Chinese and Less/Sass is greek - compared using Freeway as it is:
Super solid.
And the biggest mistake:
Never use the final web coding app (whatever name) for layout purposes. Whether start in mind or on a piece of paper what you want to achieve.
A very short and incomplete compilation of increasing your productivity you can find on:
It is work indeed. I actually had html boxes in boxes before I knew a thing about tables with mixed results. I did and do prefer them before resorting to tables on this site. But too often, they just didn’t behave when things grew. Thanks for the article. The learning continues, as always.
