I have just uploaded a new website http://dairydiary.co.uk
Actions I have used: site mapper, Google anaylytics, anti spam.
Are there any actions you regularly use that I have missed?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Very nice site you made Gaham, congrats! Totally prepaired for the future,
even in the footer 
2014-08-07 9:58 GMT+02:00 Graham Meigh email@hidden:
I have just uploaded a new website http://dairydiary.co.uk
Actions I have used: site mapper, Google anaylytics, anti spam.
Are there any actions you regularly use that I have missed?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Just one comment Graham
Your Google Font links should really be After - you have them before
David
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
you have them before
Dont know what happened there should have read ‘you have them before < html>’
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Like the site, one question in normal desktop mode you have two menus on each page, when you go into responsive and at Mobile screen width you have condensed the menu’s into one, how did you do that please?
John
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
DeltaDave. Does that make a difference? I’m loath to start ‘fiddling’ too much at this stage!
ejw. The two menus are hidden in mobile mode and the Navigation Popup Default action is deployed - you can add menu items as you like.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Does that make a difference?
Well I dont think that it is valid html and might throw a wobbly in some browsers and not display your Google fonts.
There are errors in your style declarations as well some font names with spaces in them dont have quotes round them
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
ejw. The two menus are hidden in mobile mode and the Navigation Popup Default action is deployed - you can add menu items as you like.
Thank You
John
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Your Google Font links should really be After - you have them
before
I saw that too Dave - though I’m thinking I’d like the Font links to come
before the end of the Head section (before /head) so the google css code
will over-ride any inadvertent font css generated by the FWP file in the
cascade order. Just my two cents.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
The Big Erns. Whoosh! Straight over my head there, didn’t even have to duck!
I get the gist of what you are saying but will it compromise the website performance?
In other words should I rectify this and if so how?
Thanks.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I’d like the Font links to come before the end of the Head section (before /head) so the google css code will over-ride any inadvertent font css generated by the FWP file in the cascade order. Just my two cents.
I would normally agree but my understanding is that it really is loading the font as a Resource so that any style code that comes later has something to work with - but what do I know?
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I get the gist of what you are saying but will it compromise the website performance?
It may mean that your fonts wont display in some browsers.
In other words should I rectify this and if so how?
Yes
Instead of the code being added ‘before < html>’ it should be added in the section
either After or Before end
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hey Graham,
My suggestion is for you to put your Google font code in the Before /head
(before the end of the head section) in your master page markup. Here’s why…
CSS code is “stackable” - that is, every call to CSS code meshes with every
previous call to CSS code… it’s something known as the CSS Cascade. If you
look just in the head area of your page code, you will see several CSS
calls (which are similar in appearance to your Google font code). This is
fairly normal in page code and absolutely normal in FWP page code. Now,
browsers read this code from top to bottom - in order - so the browser gets
style information from the first CSS style link, then adds the information
from the second, third, and so forth until it builds up all the information
needed to display the page.
What can happen is, if any of these CSS stylesheets contain conflicting
style codes, the browser uses the information from the last one loaded.
If you or an action inadvertently place font information into a stylesheet
that loads after the Google CSS link, then the browser will simply ignore
the Google code. Placing the Font code just before the end of the Head
section (before /head in the markup) give it the best chance to avoid
mishap.
As to whether it compromises web performance - browsers are pretty
forgiving. I would give you an F for it, but Chrome and Safari can still
figure it out. However, it’s not a guarantee that it will always slide, nor
that building websites like a Jenga tower is a very smart thing to do -
especially as the fix is just so very simple and quick.
As a bonus, you might go back to Google fonts and load all those fonts and
styles at the same time, producing one line of code to paste into your
markup instead of three. I’d give A+ for that
–
Ernie Simpson
On Thu, Aug 7, 2014 at 12:41 PM, Graham Meigh email@hidden
wrote:
The Big Erns. Whoosh! Straight over my head there, didn’t even have to
duck!I get the gist of what you are saying but will it compromise the website
performance?In other words should I rectify this and if so how?
Thanks.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
but what do I know?
I think you know a lot, Dave… I appreciate your input. As the proverb says,
iron sharpens iron and one man sharpens another. 
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
As the proverb says, iron sharpens iron and one man sharpens another.
Hadn’t heard that one!
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Just found this:
Google recommends that the code be added right after the tag, i.e. make it the first element in the head section of a page. Why? Google says1:
Note: For best display in IE, make the stylesheet tag the first element in the HTML section. In IE, if the tag is placed after tags, the entire page will block and not display anything until the web font is loaded.
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks Guys. I’ll try and get my head round this! And I thought I would have an A by following Google’s instructionS.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yes, I’m familiar with the Google recommend, but question it as
tags generally come at the end of a document - so of course not there and
first in the section seems wrong to me. Theirs is just a suggestion
as is mine.
Graham, you certainly get high marks for the effort and the desire to
exceed at something few people may ever notice. You’ve gone an extra mile
and I can see you really care about this site - very well done.
Best to both you gents,
–
Ernie Simpson
On Thu, Aug 7, 2014 at 1:35 PM, DeltaDave email@hidden wrote:
Just found this:
Google recommends that the code be added right after the tag, i.e.
make it the first element in the head section of a page. Why? Google says1:
Note: For best display in IE, make the stylesheet tag the first
element in the HTML section. In IE, if the tag is placed
after tags, the entire page will block and not display anything
until the web font is loaded.D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
True, they’re only suggestions. Though there are situations when a script may need to load sooner (/head) rather than later (/body). I tend to add mine in the head (after the CSS) but I’m also using a lot of dependencies so I collate them all into one file and minify the !*@# of it.
Todd
Yes, I’m familiar with the Google recommend, but question it as
tags generally come at the end of a document - so of course not there and
first in the section seems wrong to me. Theirs is just a suggestion
as is mine.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yeah, I guess what we’re talking about essentially is the difference
between best coding practices and best FWP coding practices. Either way,
it’s not like the Ten Commandments - though I’m taking no chances in case
Judgement Day turns out not as expected.
–
Ernie Simpson
On Thu, Aug 7, 2014 at 2:20 PM, Todd email@hidden wrote:
True, they’re only suggestions. Though there are situations when a script
may need to load sooner (/head) rather than later (/body). I tend to add
mine in the head (after the CSS) but I’m also using a lot of dependencies
so I collate them all into one file and minify the !*@# of it.Todd
http://xiiro.comYes, I’m familiar with the Google recommend, but question it as
tags generally come at the end of a document - so of course not there and
first in the section seems wrong to me. Theirs is just a
suggestion
as is mine.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options