HTML5 and C5
Permalink
So with all the buzz seeming to surround HTML5, I'm curious… is it possible to start creating websites using HTML5 in concrete?
And then, if it's possible, would there be any caveats or things to consider before jumping in headlong?
I'm just curious. It seems like you could simply code the theme and blocks you want to use in HTML5, and everything should be good.
I know a lot of folks around here probably stick to XHTML Transitional (as I do too) just for consistency and practicality, but it's never a bad thing to consider the future (or am I wrong? ;)).
And then, if it's possible, would there be any caveats or things to consider before jumping in headlong?
I'm just curious. It seems like you could simply code the theme and blocks you want to use in HTML5, and everything should be good.
I know a lot of folks around here probably stick to XHTML Transitional (as I do too) just for consistency and practicality, but it's never a bad thing to consider the future (or am I wrong? ;)).
the customizer won't work with html5 what i've tested so far, but the theme in general does.
--ron
--ron
well, i think it would be nice, a few things though,
HTML5 is NOT finished and many things can change
HTML5 is NOT supported by majority of the browsers in the world (all IEs some FF's etc)
C5 would need to up its system requirements, or include a dumbed down version (current i guess) so that it works with older browsers
Mike
HTML5 is NOT finished and many things can change
HTML5 is NOT supported by majority of the browsers in the world (all IEs some FF's etc)
C5 would need to up its system requirements, or include a dumbed down version (current i guess) so that it works with older browsers
Mike
The thing about HTML5 these days, it seems, is that even though it's not "finished" the latest browser versions are already implementing it—for better or worse, maybe.
I think it was Tim-Berners Lee that said the spec would be finished in some crazy date—2020, or something like that.
To me it makes more sense to be using progressive enhancement, like Scott C said. I don't think it's a good idea to be using the bleeding edge of HTML5 as the *only* option for users, but I feel like it's worth the while to start implementing some of the features, including canvas, video, and SVG support. I believe it's YouTube that offers both HTML5-based video and the traditional Flash-based video.
A good layout of the browser support for it is this site:http://html5readiness.com/
Of course the lagger is IE, but I'm thinking about moving up the ladder for version support. Recently Statcounter announced that IE6 usage had dropped below 5% for the US and Europe (http://bit.ly/dBY34B). As much as I tend to wish for backward-compatibility, that made me start thinking about dropping IE6 support for clients (unless specifically asked for it).
Even though IE7 is still around, if users are finally updating like this, to me it makes sense to start moving upwards a bit in terms of what I use as a designer.
EDIT: As for C5 though, I guess what I was asking was if there are any deep system conflicts that would cause C5 to "break" if it was styled with an HTML5-based theme. It sounds like there *mostly* isn't.
I think it was Tim-Berners Lee that said the spec would be finished in some crazy date—2020, or something like that.
To me it makes more sense to be using progressive enhancement, like Scott C said. I don't think it's a good idea to be using the bleeding edge of HTML5 as the *only* option for users, but I feel like it's worth the while to start implementing some of the features, including canvas, video, and SVG support. I believe it's YouTube that offers both HTML5-based video and the traditional Flash-based video.
A good layout of the browser support for it is this site:http://html5readiness.com/
Of course the lagger is IE, but I'm thinking about moving up the ladder for version support. Recently Statcounter announced that IE6 usage had dropped below 5% for the US and Europe (http://bit.ly/dBY34B). As much as I tend to wish for backward-compatibility, that made me start thinking about dropping IE6 support for clients (unless specifically asked for it).
Even though IE7 is still around, if users are finally updating like this, to me it makes sense to start moving upwards a bit in terms of what I use as a designer.
EDIT: As for C5 though, I guess what I was asking was if there are any deep system conflicts that would cause C5 to "break" if it was styled with an HTML5-based theme. It sounds like there *mostly* isn't.
yes but a simple link to a javascript file allows ie7 etc to understand the new semantic tags <section> etc etc
see:
http://remysharp.com/2009/01/07/html5-enabling-script/... - I have tested this and it does work :)
see:
http://remysharp.com/2009/01/07/html5-enabling-script/... - I have tested this and it does work :)
I realise this topic is a bit old...but I was wondering if anyone has worked out how to change the editor so that it can output the newer html5 semantic tags - ie so that within a content block someone can add <section> <article> <aside> etc as well as just <p> tags & co?
I tried editing the TinyMCE config to get it to accept the new HTML5 semantic tags with little success.
I think somebody suggested creating a new block type to use a HTML5 compatible editor something like Aloha Editor (http://aloha-editor.org/) perhaps?
I think somebody suggested creating a new block type to use a HTML5 compatible editor something like Aloha Editor (http://aloha-editor.org/) perhaps?
I think for the vast majority of sites, you don't want <section>, <article> or <aside> being added by the user when editing content -- rather those would surround the areas that you define in your template, for example:
The whole point of using a CMS is to isolate the user's content to within those sections of the page, so having them put those tags into the content block would not really be what you as the designer would want.
(Although I suppose an exception to this would be if you did want the users to be able to set the <article> tag around chunks of content -- let's say there's a content block and an image block and they belong together in the same "article" -- you wouldn't want each surrounded by a separate <area> tag.)
<section> <?php $a = new Area('Main'); $a->setBlockWrapperStart('<article>'); $a->setBlockWrapperEnd('</article>'); $a->display($c); ?> </section> <aside> <?php $a = new Area('Sidebar'); $a->display($c); ?> </aside>
The whole point of using a CMS is to isolate the user's content to within those sections of the page, so having them put those tags into the content block would not really be what you as the designer would want.
(Although I suppose an exception to this would be if you did want the users to be able to set the <article> tag around chunks of content -- let's say there's a content block and an image block and they belong together in the same "article" -- you wouldn't want each surrounded by a separate <area> tag.)
I did think about doing it that way but this would not account for the fact that sections can have a number of articles, and indeed articles can have sections nested inside them.
So this means you would just be wrapping a section around everything which is not fully utilising the new semantics (although I take your point re the users, but I guess I am talking about a 'best case' scenario where the content editor understands the proper structure that should be applied to a page)
So this means you would just be wrapping a section around everything which is not fully utilising the new semantics (although I take your point re the users, but I guess I am talking about a 'best case' scenario where the content editor understands the proper structure that should be applied to a page)
Another approach would be to create custom templates for the content block type for different semantic elements e.g.
However, it would mean separating a piece of content into lots of individual blocks in order to fully use the semantic markup elements in HTML5. It makes more sense to use a different editor which supports elements like section, hgroup figure, figcaption etc.
However, it would mean separating a piece of content into lots of individual blocks in order to fully use the semantic markup elements in HTML5. It makes more sense to use a different editor which supports elements like section, hgroup figure, figcaption etc.
I'm only using it for progressive enhancement of themes and whatnot using -moz and -webkit etc.
I builthttp://www.quantiv.com in HTML5 it currently doesn't use much in the way of new features but that will change over time.
Nice Techn0tic! It's great to see sites being built with Concrete5 and HTML5.
Have you noticed anything strange when editing your site due to the (W3C Valid) HTML5 Doctype? Since HTML5 is supposed to be backward compatible, I suppose probably not.
Anyone else got any HTML5 & Concrete5 sites to show?
Have you noticed anything strange when editing your site due to the (W3C Valid) HTML5 Doctype? Since HTML5 is supposed to be backward compatible, I suppose probably not.
Anyone else got any HTML5 & Concrete5 sites to show?
As far as validation, you have to use a separate HTML5 validator. HTML5 is backward compatible only in the sense that if you took code from another HTML site (imagine a bunch of divs), it would still work.
My site was redone in HTML5 and CSS3 this summer.http://www.proteuscreative.com
I later packaged the theme I built for it and put it on the marketplace (Obsidian). At the moment it's waiting approval.
My site was redone in HTML5 and CSS3 this summer.http://www.proteuscreative.com
I later packaged the theme I built for it and put it on the marketplace (Obsidian). At the moment it's waiting approval.
I'm using HTML5 since the beginning on my site and there has never been a problem.
http://www.fif-moebel.de/
I'm not using advanced html5 features on this site though.
No html5 validation errors btw ;)
http://validator.w3.org/check?uri=www.fif-moebel.de&charset=(de...
http://www.fif-moebel.de/
I'm not using advanced html5 features on this site though.
No html5 validation errors btw ;)
http://validator.w3.org/check?uri=www.fif-moebel.de&charset=(de...
I am trying to figure out how to modify the video player block to play html5 so our HUNDREDS of videos on our site can be seen on Ipads and Iphones. Can you help me do this.
I noticed JW player came out with 5.3 that supports HTML5 but cannot figure out how to modify the code to make it work with this CMS. Please help me
- coding novice, btw.
I noticed JW player came out with 5.3 that supports HTML5 but cannot figure out how to modify the code to make it work with this CMS. Please help me
- coding novice, btw.
How soon do you need this? I can do this for you, but probably wont be ready till end of Monday / Tuesday, as I have a few things on. That ok?
Jon
Jon
As long as the editing toolbar doesn't get confused if you specify your document as html5 things should work fine.
I did use the canvas tag in one of my addons (not published) and there was no problem at all.
And yes, I'm mostly working with XHTML