I have an old FWP website that I designed with XHTML 1.0 Strict markup. If I upgrade the FWP document to HMTL 5 will that present any problems?
If I’m now using HTML 5 markup, should I also be using Section tags, such as Header. Footer, and Article, and why is that important?
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
As for the second part of my question, I just discovered this article which helps explain HTML 5 sections and what they’re used for.
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
That’s probably a nice resource for anyone working with html5. I already
like and use the other links at the bottom.
I have an old FWP website that I designed with XHTML 1.0 Strict markup. If
I upgrade the FWP document to HMTL 5 will that present any problems?
I don’t think so - Freeway Pro will adjust the code for you as required.
The biggest issue will be markup code that you’ve inserted in into your FWP
document… however, HTML5 is more “forgiving” than a Strict doctype, so no
harm expected.
If I’m now using HTML 5 markup, should I also be using Section tags, such
as Header. Footer, and Article, and why is that important?
My advice, beyond what you are already doing with immersive education, is
to NOT use any HTML5 elements unless you can defend why you would use
them in a specific document. DIVs work just fine – the same as they always
have – and there is no shame in using them. I’ve been making HTML5 sites
for a couple years now, and I’m still not 100% comfortable with my
sectioning strategies. More like 90% comfortable though. If you can justify
using an element, then go for it. This is good because you’ll spend more
time thinking about the structure of your content, and that will affect how
you see your layout. Good stuff.
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
As for the “why” it provides more meaningful (richer) semantic structure to a page. Of course, as Ernie mentioned you need to have a reasonable understanding of how to use the new elements which is an ongoing process for many of us. And it doesn’t always help when the spec changes midstream.
Todd
If I’m now using HTML 5 markup, should I also be using Section tags, such as Header. Footer, and Article, and why is that important?
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 17 Feb 2014, 7:32 pm, The Big Erns wrote:
My advice, beyond what you are already doing with immersive education, is
to NOT use any HTML5 elements unless you can defend why you would use
them in a specific document. DIVs work just fine – the same as they always
have – and there is no shame in using them. I’ve been making HTML5 sites
for a couple years now, and I’m still not 100% comfortable with my
sectioning strategies. More like 90% comfortable though. If you can justify
using an element, then go for it. This is good because you’ll spend more
time thinking about the structure of your content, and that will affect how
you see your layout. Good stuff.
Yes, that’s what I thought. Some HTML sections are easy, like header and footer, but others require a little more thought. For instance, what do you do with navigation menus, most of which are technically within the header section of the site?
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
The can now contain elements.
I’ve mentioned it time and again but HTML5 Doctor is a great resource to keep open.
Todd
For instance, what do you do with navigation menus, most of which are technically within the header section of the site?
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Where do I find that resource Todd?
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
http://html5doctor.com. Bookmark it … now. Preferably always keep it open in a browser tab.
Todd
Where do I find that resource Todd?
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I’m a big fan of putting the last in source order, but using absolute positioning to pull it up to the top of the page. Leave a space for it with padding, and you’re set. The content comes first, hopefully in semantic order, and the next steps after you’ve read that are at the end.
Walter
On Feb 19, 2014, at 12:12 PM, Todd wrote:
The can now contain elements.
I’ve mentioned it time and again but HTML5 Doctor is a great resource to keep open.
Todd
http://xiiro.comFor instance, what do you do with navigation menus, most of which are technically within the header section of the site?
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 19 Feb 2014, 4:21 pm, Todd wrote:
http://html5doctor.com. Bookmark it now. Preferably always keep it open in a browser tab.
Okay, will do.
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 19 Feb 2014, 4:35 pm, waltd wrote:
I’m a big fan of putting the last in source order, but using absolute positioning to pull it up to the top of the page. Leave a space for it with padding, and you’re set. The content comes first, hopefully in semantic order, and the next steps after you’ve read that are at the end.
Walter
That’s a GREAT idea.
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yes, that’s what I thought. Some HTML sections are easy, like header and
footer, but others require a little more thought. For instance, what do you
do with navigation menus, most of which are technically within the header
section of the site?
We have a traditional context for headers and footers - though I think you
could push back against that convention and try to justify their use in
your projects.
For me, I think semantics isn’t just a concept for individual page content,
but extends to the entire site. So I see the traditional header/footer
combo as the site overlap of the page - site name, brand, authors and
contacts - and site navigation. So for the most part I like the nav element
within the main header element which I see more as prelude to page content.
In that light, the footer becomes a site-wide footnote.
Then what about in-page navigation? Where should that go?
Overall, I think that you want to avoid too much absolute rule-making (no
white before Labor Day or whatever). Treat all this like the Pirate’s Code
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options