Hi guys,
did a lil setup and wonder what you think (link below):
It’s about placing items “absolute the Freeway way”. In this case: The Navigation.
Two questions:
####1.
Doing so, absolute positioned items are generally printed in code AFTER the relative positioned one. Do you see this a semantical foul or is it something to ignore?
####2.
The concept is, running two identical navigations - one for desktop the other one for mobile. As well here the concerns:
Foul or not?
Am excited what you think!
Cheers
Thomas
https://dl.dropboxusercontent.com/u/8231701/cdn-digitalmedia-themes/theGridMaterialz/menutest.html
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
Hi Thomas,
I think where I would start is with semantic structures… the only one in this example is section… you might do well to further outline your page structure with header, footer, main (if you are so inclined), and of course, nav.
I don’t think there is a semantic problem with more than one navigation solution, but if you identify more than one nav element in your layout that would be sowing seeds of confusion. I think the same would be true if the nav element did not contain both navigational solutions. Just my view on it.
There is also a view that the nav element is (or should be) a part of the header content as they relate to Page or Site themes… which I agree for the most part. However, not inflexibly so as I think cases can be made for splitting them.
Absolute positioned items need a Relative positioned item-- from which it descends– to orient to… this is simply a matter of mechanics, not semantics. So it’s not so much where the absolute-positioned item goes-- first or last-- as much as its descendance. If #PageDiv is your position:relative; reference then your element position:absolute; can be anywhere from the first to last child of #PageDiv.
Perhaps I answered these in reverse order… but I hope that I’ve helped clarify something.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
HI Ernie,
thanks for your comments, appreciated. Yep - you’re right, semantic discussions require semantic structure.
It is common practice wrapping the into a -item, however I’m pretty sure that this isn’t necessary at all. In my case it’s even impossible. The nav is basically fixed, the header not.
I’m usually place absolute/fixed items relative and declare position within extended dialogue. In this case I’d like to go more back to the roots. Kind of templating, making things more obvious in Freeway’s workspace. Making it a header would even cover the entire workspace.
I tried to do the semantic quick’n dirty, but for sure I have even more questions (I even thought about contacting you some days ago). So if you stalk this occasionally I always appreciate your words as ever.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
It is common practice wrapping the into a -item, however I’m pretty sure that this isn’t necessary at all. In my case it’s even impossible. The nav is basically fixed, the header not.
I agree, that it isn’t mandatory to place the nav element in the header. However, I must also say that I think it’s still quite possible for you to include it, if you want.
Ultimately, the header element is a container… a semantic container, but a container nonetheless. The key is that it doesn’t have to look like a header to function as one…
<div id="PageDiv"> <!-- position:relative -->
<header> <!-- container, no visual appearance, no position -->
<div> <-- visual "header" -->
<div content> <!-- h1, header stuff -->
</div>
<nav> <!-- position:fixed -->
<nav content>
</nav>
</header>
<!-- everything within the header element is semantically grouped -->
Make the PageDiv position:relative and adjust space for the nav with margin or padding on the header. The nav can be first. middle, last… order isn’t important. This is just a way to do it, and while I like the idea of the header as a home for such things as site navigation, I still strongly agree that it isn’t mandatory.
Please contact me if you like… I spend a lot of time thinking about this stuff-- but I also spend a lot of time trying to figure out my coffee machine, so that doesn’t make me much of an expert 
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
Hi Ernie,
apologize for not coming back to you earlier. There is a simple reason for: “I had to mind about (which sometimes takes me a couple of approaches)”
The basic thoughts were: “How to best construct it in Freeway, Relative or Absolute?” I decided to do it relative, cause absolute doesn’t make any sense at all.
This is what I did:
https://dl.dropboxusercontent.com/u/8231701/cdn-digitalmedia-themes/theGridMaterialz/themenu-newappro.html
This approach comes up to my expectations - semantic included (and I hope yours too).
But the real reason for my question was indeed:
The Freeway CSS-Menu approach is, let’s say “OK”. It is OK cause it works. On the other hand, it is strangely limited. A bit too limited if to say so. So I tried to do a menu of my own. I never did this before, but as far as I know, you do your own Navigations, too?
So I started to built my own (based on the materials library this entire project is built on). Whenever I do “Freestyle”, I have only one expectation:
“No MarkUp - the content needs to be build natively in Freeway!!!”
What’s your strategy in this?
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options