I am inviting the community to have a look and am inviting comments.
Stunning. Simple, elegant, clean.
I like it. How easy, though, is it to edit in Freeway? So many templates are fabulous to look at but a complete PITA to edit if you want to add or remove anything to the basic structure.
Cheers
Heather
Imagic Design * Good Design - No Compromise
email@hidden http://www.imagic-design.co.uk
Twitter @Imagic-Design
T: 01634 864017
Exactly. Without the reasoning and knowledge as to why things are done in a certain way the whole template can crumble to dust rapidly. Typically why a CMS is incorporated in the real world for ordinary users.
David
On 22 Jul 2012, at 07:50, Heather Kavanagh email@hidden wrote:
So many templates are fabulous to look at but a complete PITA to edit if you want to add or remove anything to the basic structure.
Helps with anything other than your document declaration
My HTML5 Element Action inserts that link, and also allows you to convert an HTML element into most of the “new” elements. you are correct about what it does, though. It makes older browsers (mostly IE) understand how to display those new elements, and makes them print correctly, too.
You’re right – I am using Walter’s spiffy new HTML5 Action… you are also
correct in reasoning my div naming conventions. However, I have not yet
applied the action to create those specific elements… as doing so creates
some difficulties when combined with other actions. I am creating
alternative strategies.
–
Ernie Simpson
On Sun, Jul 22, 2012 at 9:37 AM, David Owen <
email@hidden> wrote:
Didn’t know about this. Just looking at Ernie’s code and could not spot
any HTML5 elements.
Ernie did you plan to mark the code sections up using HTML5 divisions
(elements)?
I am finding this a lot harder than it looks. The first seemingly
impossible task is how to simplify the use of the file – I cannot imagine
supporting users who are not at any level of learning page-code. IMO, it is
an un-winnable strategy. Right now I am aiming to keep it uncomplicated as
possible – which conforms to my own personal aesthetic – and think of it as
a teaching tool. So I am contemplating ways to release the Freeway Pro file
for evaluation as well.
Second, I am still feeling unclear about HTML5 implementation –
specifically, what are the value of HTML5 container structures as opposed
to divs? Is it a semantic advantage? What then are the roles of div
containers? I have not found much clarification on that concept or what the
intended use of some of these structures are.
All of this is giving me great ideas, like building responsiveness into
this or resurrecting some of my past layouts like Son of Satin.
You guys wanna look at this and tell me if this gal has the structure
right? It makes sense to me, but I want to be sure it represents a good
practical interpretation of how html5 should look.
–
Ernie Simpson
On Sun, Jul 22, 2012 at 5:45 PM, Todd email@hidden wrote:
Ernie Simpson wrote:
I am still feeling unclear about HTML5 implementation
On Jul 22, 2012, at 23:39, Ernie Simpson email@hidden wrote:
Thanks Todd, that’s very helpful.
You guys wanna look at this and tell me if this gal has the structure
right? It makes sense to me, but I want to be sure it represents a good
practical interpretation of how html5 should look.
–
Ernie Simpson
On Sun, Jul 22, 2012 at 5:45 PM, Todd email@hidden wrote:
Ernie Simpson wrote:
I am still feeling unclear about HTML5 implementation
You guys wanna look at this and tell me if this gal has the structure
right? It makes sense to me, but I want to be sure it represents a good
practical interpretation of how html5 should look.
How 'bout an example of the humble and oft forgotten definition list?
Poor little guy always gets picked last.
am not sure if this is a list discussing look and design of a template or a HTML5 Elements and its usage one.
So if Template:
Nice and well done, however I prefer colors :-). Templates should be seen as an “it is as it is”. If it doesn’t match my requirements, so there is nothing to fiddle in, it is simply the wrong template.
If HTML5:
Basically I’m dumb 'cause I haven’t yet understood the entire theme but there is something that makes me wonder if we really can use HTML5 elements in Freeway - or better said in the expected and dedicated way. So let’s have a look into my dangerous superficial knowledge:
Inline styles or not?
Up to my definition, a “HTML5 page” contains divs with ids and(or) classes.
Not more?
No. The appearance of those divs are steered by the style-sheet(s). Not one single line needs to be in the before end head tag or within the open/close div-tag - all is part of external resources.
So what is a DIV?
A content and style(s) containing element.
And HTML5 elements?
Structuring divs in a semantic way. So prefixing divs in order to declare what is to be expected giving them a direct (eg. header) or global (eg. section) meaning. The purpose is an easier way to SEO a webpage.
But what’s then the problem within Freeway?
Good point. Inline styles probably? But this can be solved by externalizing them. That’s what I thought and tried.
But unfortunately, Walter’s action is stopping the externalizing-tools (such as Tim’s externalize or Max’s advanced inline style (re)mover) for whatever reason to do their jobs.
It may be the fact, that an HTML5 attribute is not dedicated for “styling” so there is nothing for externalize (that’s the job of the divs) - but as I said in the entry:
It may be the fact, that an HTML5 attribute is not dedicated for “styling” so there is nothing for externalize (that’s the job of the divs)
HTML5 elements can be targeted for styling. The problem I’ve found with
doing that is you will lose the styling info in non-HTML5-ready browsers
because they will simply ignore those elements and by extension any
styling associated with them. That’s assuming you’re not using js to
force those browsers to understand HTML5 elements in which case it might
work fine.