I want to know if it is possible to style H tags to match your P tag? I.E less bold
When you style your font with a H tag, it Bolds it!
I have gone into the Extended part of the edit styles of my H tag, & tried editing to match my op tag. However it still looks bolder obviously.
Is their a way to use a H tag, but style is teh same as your P tag style whilst carrying the H tag, but so they BOTH look the same in browser (yes i know look may vary on brower)
Just want it to match really, or is this fundamental in web fonts & how the H tag Hierarchy works H1 being boldest as deemed most important!!! etc etc…
By default, browsers make headers bold unless told otherwise. Freeway Pro’s user interface currently has no intuitive way to achieve this result. But there is an easy CSS way to achieve it.
In the Extended style of your h tag, create a new attribute name ‘font-weight’ with the value ‘normal’. Your header text will now appear un-bold.
Of course you can style your h tags to appear the same as your p tags. However, they are both block elements so you will have a great lot of difficulty in having them appear together on the same line. Otherwise, no problem.
–
Ernie Simpson
On Oct 29, 2012, at 8:50 AM, “Mr worm” email@hidden wrote:
Hi all,
I want to know if it is possible to style H tags to match your P tag? I.E less bold
When you style your font with a H tag, it Bolds it!
I have gone into the Extended part of the edit styles of my H tag, & tried editing to match my op tag. However it still looks bolder obviously.
Is their a way to use a H tag, but style is teh same as your P tag style whilst carrying the H tag, but so they BOTH look the same in browser (yes i know look may vary on brower)
Just want it to match really, or is this fundamental in web fonts & how the H tag Hierarchy works H1 being boldest as deemed most important!!! etc etc…
There’s another clever CSS trick for giving different elements the same styling attributes, and it is easy to do in Freeway Pro.
Previously, I showed you how to disable the default bold style of header text. But you would have to repeat that process for each header style. What a waste of time, not to mention the boatload of redundant code you’d be generating. If only you could combine those shared style attributes…
With CSS it’s easy.
To make all your header elements unbold, open the Edit Styles window and create a new style. Type the name for your new style in the Tag window, like this:
h1, h2, h3, h4, h5
Then tab to the Name window, delete the FWP auto-generated name. Then set whatever attributes you want them all to have. Make sure that other instances of these tags don’t have conflicting attributes - as in h1 is set to bold while this new style is unbold… this will just confuse the browser and give you bad results.
If you want to style h1 and p elements the same, then delete both styles, make a new Tag Style, and name it
h1, p
FWP will NOT display these multiple styles correctly in the working page, but the browser will. Most Freeway design experts are used to this by now. There are many clever ways to use CSS like this in Freeway Pro, and still more ways to achieve this same result. I like that it results in cleaner, more efficient code – which is all the browser cares about in the first place.
I was styling the attribute name ‘font-style’ with the value ‘normal’. So it wasn’t displaying!!!
All sorted now, & yeah FW doesn’t display 100% accurate until uploaded to server.
Also the clever CSS styling was very helpful!!!
One last question, is it bad practice to have more than one H1 tag on your page? Or should you have just one instance on the page e.g. (Main page heading)
On Mon, Oct 29, 2012 at 7:30 PM, DeltaDave email@hidden wrote:
is it bad practice to have more than one H1 tag on your page?
Yes
There should only be 1 ‘most important’ piece of Text - otherwise it loses
its meaning.
In the recent past, I would have agreed with Dave… think of your content in
outline form – main topic, sub-topics, etc. Multiple h1 tags would create
competing main topics. Also, starting your topic tree at h2 or h3 is bad
form too.
However, with the advent of HTML5 there seems to be a semantic shift in how
content can be organized and cataloged. Articles that can stand alone have
their own main topics that require identification within their relevant
structures. Grokking the outline structure is not as simple as it was.
Still, important to keep in mind that your page should follow an outline
structure for the content to be semantically available.
Freeway Pro, with Walter’s HTML5 actions does indeed output html5
content. I’ve been using them for quite a while now, and am super pleased
with the results.
Your link has good information - advice that I say is still good to
follow. But it’s a year out-of-date and has been overtaken with regard to
work on HTML5 semantics. So, important info… but decreasingly relevant.
Here’s a link to what Google software engineer Matt Cutts has to say
about it.
Again, things are changing so it’s good to embrace best practices - just
not too tightly maybe.
Some great info as usual, but if Matt Cutts himself says its ok to have multiple H1 tags as headers for multiple sections on a page (used sparingly) then Google must be ok with it.
I do have a logical reason to have more than one on a page, 4 max so even if CSS was turned off my page would still look ok, & the H1’s define different sections on my index, so it seems logical to have almost small tree like structures H1, H2, H3… etc wrapped inside the overall page tree structure ranging from H1 (most important) - H6 (deemed least important)
It is used for all my headers on my page, which is what the intent of H1 is!
In short, use sparingly, where it makes sense & don’t abuse it!
Guess everything changes at some point, evolving to keep up with the change & to stay on top is key.
My point was that FW doesn’t output HTML5 on its own - yet. And yes I did see that piece from MC but I think it is really too early to jump on multiple H1 usage as other browser/search engines may not look on them as kindly.
Besides surely logic dictates that there should only be 1 ‘Main Heading’ and if you have 2 equally important topics then they each deserve their own page.
To be clear, I’m not advocating any jumping – or trashing even, of
time-tested good practices. The tools are allowing us more flexibility, and
I am acknowledging that we should allow ourselves to be more flexible,
while remaining semantic. Loosen our grip, but not let go.
–
Ernie Simpson
On Tue, Oct 30, 2012 at 12:49 PM, DeltaDave email@hidden wrote:
My point was that FW doesn’t output HTML5 on its own - yet. And yes I did
see that piece from MC but I think it is really too early to jump on
multiple H1 usage as other browser/search engines may not look on them as
kindly.
Besides surely logic dictates that there should only be 1 ‘Main Heading’
and if you have 2 equally important topics then they each deserve their own
page.
