running html5 and responsive with CC5
Permalink
ok. I suggest the major problem are the add ons who bring a lot of html on the page,
for example pro events…
but let start:
how can I add the artical tag around the basic block?
how to bring the lang tag to contents?
1) to a each block, the user can select kt from a list
2) automaticly by page, detected by the path. For example /en/ /fr/ /de/.
going responsive:
how can I use the data-fullsrc option of html5 to get an Image (path and source) in two resolutions. For this I have 3 suggestions: the User can enter both sizes, the user defines the max size and the low res is a percentage of this and the third is I predefine both sizes (maybe just the with)…
Thanks for any help and suggestions
for example pro events…
but let start:
how can I add the artical tag around the basic block?
how to bring the lang tag to contents?
1) to a each block, the user can select kt from a list
2) automaticly by page, detected by the path. For example /en/ /fr/ /de/.
going responsive:
how can I use the data-fullsrc option of html5 to get an Image (path and source) in two resolutions. For this I have 3 suggestions: the User can enter both sizes, the user defines the max size and the low res is a percentage of this and the third is I predefine both sizes (maybe just the with)…
Thanks for any help and suggestions
Yes the internationalization I alway use, a very good (not perfect) add-on.
I think I can build the thing to degrade gracefully… article and for example nav are not a problem IE stays in the IE8 mode.
For example the article can wrap in a div for older browsers. And of course the is the modernizer.js and other options.
Thats all fine for me. I just think of the code that is generated by the CC5 blocks.
To edit the default blocks is always the problem with updates, but with a custom template – thanks for this idea – it is much better.
The other way is maybe to catch the tree or four standard blocks and make them to my own custom blocks, so the don't will get lost by the next update.
The two image sizes low-res and highres (data-fullsrc option) is much better than any JS or CSS solution, because I can save bandwidth for mobile devices!
I think I can build the thing to degrade gracefully… article and for example nav are not a problem IE stays in the IE8 mode.
For example the article can wrap in a div for older browsers. And of course the is the modernizer.js and other options.
Thats all fine for me. I just think of the code that is generated by the CC5 blocks.
To edit the default blocks is always the problem with updates, but with a custom template – thanks for this idea – it is much better.
The other way is maybe to catch the tree or four standard blocks and make them to my own custom blocks, so the don't will get lost by the next update.
The two image sizes low-res and highres (data-fullsrc option) is much better than any JS or CSS solution, because I can save bandwidth for mobile devices!
BTW, there are some responsive themes in the addons.
And, beginning with 5.7, all new C5 themes will be responsive.
And, beginning with 5.7, all new C5 themes will be responsive.
I always create my own themes…
tryhttp://adaptive-images.com/ for the image part.
I will try! Thanks!
C5 has a good discussion of the current state of architecture, C5 approach, etc.:http://www.concrete5.org/documentation/installation/installing_c5_i...
HTML5 support is patchy among the current crop of browsers. If you want to use those features, you'll likely want to incorporate some fixes for IE.
For example, the article tag isn't supported in IE through 8, I believe. You'll want to use the the HTML5shiv (http://code.google.com/p/html5shiv/) to provide some very basic support for HTML5 features in IE.
For a comprehensive solution, you'll want to incorporate modernizer.js -- which does feature detection at the browser level. It doesn't provide those missing features, but allows you to either provide an alternative or to degrade gracefully.
To implement this in C5 blocks, you'll want to identify the source file which generates the output. Often, in addons, this is view.php, but then there may be different templates, or other files which serve the same purpose. You'll just need to dig in.
As for displaying thumbnail/larger image, a contemporary javascript approach might be simpler -- you'd need a fallback for HTML5 anyway.
HTH