website redo

Good afternoon,

I would like to announce that I have redone my website.

and would like to share it with you.

I also would love to hear all opinions.

Julie

http://www.grassrootsweb.net


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Loads of fun, much faster loading than your previous outing. One issue
I have (others may as well) is the lack of contrast between the white
type in your navigation menu (cute frog) and the background of that
element. If it were me, I would use a much lower-contrast image,
preferably something blurry, so that the type can be read more easily.
Also, quite a lot more of a hint that these are navigation options
would be a good idea. Perhaps a large block of background color as you
mouse over them. They’re given awfully short shrift as it is.

Walter

On Feb 22, 2011, at 3:49 PM, Julie Maxwell Allen wrote:

Good afternoon,

I would like to announce that I have redone my website.

and would like to share it with you.

I also would love to hear all opinions.

Julie

http://www.grassrootsweb.net


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

Thank you!

I tweaked the frog with advance fade and photo magic.

does that look better?

how would you hint that? arrows before?

I am not using css since there are no submenus. Plus, it throws the lineup off…

J
On Feb 22, 2011, at 4:04 PM, Walter Lee Davis wrote:

Loads of fun, much faster loading than your previous outing. One issue I have (others may as well) is the lack of contrast between the white type in your navigation menu (cute frog) and the background of that element. If it were me, I would use a much lower-contrast image, preferably something blurry, so that the type can be read more easily. Also, quite a lot more of a hint that these are navigation options would be a good idea. Perhaps a large block of background color as you mouse over them. They’re given awfully short shrift as it is.

Walter

On Feb 22, 2011, at 3:49 PM, Julie Maxwell Allen wrote:

Good afternoon,

I would like to announce that I have redone my website.

and would like to share it with you.

I also would love to hear all opinions.

Julie

http://www.grassrootsweb.net


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


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I would style the :hover pseudo-class of the links within that box. If
you’re just adding normal links here, you can do this by clicking on
the outer box and using the Link Style settings in the Inspector. If
you want to get fancy here, the specific settings I use for this sort
of thing are as follows (you’ll need to use Extended for most of these):

#nav a {
	display: block;
	margin: 0;
	padding: 4px 12px;
	color: #fff;
}
#nav a:hover {
	background-color: #ff9;
	color: #000;
}

This gives you white links, and when you mouse over them, a yellow box
behind and black text.

You’ll have to use the Extended interface to add everything except the
font color and the background-color. The key to the effect is
display: block, which forces the navigation element to have a huge
“hot” area around it. This makes the navigation usable on an iPhone or
similar, for one thing, and provides a nice big blotch of color when
you mouse over it.

Walter

Walter

On Feb 22, 2011, at 4:22 PM, Julie Maxwell Allen wrote:

how would you hint that? arrows before?

I am not using css since there are no submenus. Plus, it throws the
lineup off…


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Much nicer, easier to pick out the links.

Walter

On Feb 22, 2011, at 4:22 PM, Julie Maxwell Allen wrote:

I tweaked the frog with advance fade and photo magic.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Hi,

If you click on the About Us link on the nav menu, there’s no nav menu on the about us page. All the others seem fine.

Martin
Signal Mountain, TN

On Feb 22, 2011, at 4:22 PM, Julie Maxwell Allen wrote:

Thank you!

I tweaked the frog with advance fade and photo magic.

does that look better?

how would you hint that? arrows before?

I am not using css since there are no submenus. Plus, it throws the lineup off…

J
On Feb 22, 2011, at 4:04 PM, Walter Lee Davis wrote:

Loads of fun, much faster loading than your previous outing. One issue I have (others may as well) is the lack of contrast between the white type in your navigation menu (cute frog) and the background of that element. If it were me, I would use a much lower-contrast image, preferably something blurry, so that the type can be read more easily. Also, quite a lot more of a hint that these are navigation options would be a good idea. Perhaps a large block of background color as you mouse over them. They’re given awfully short shrift as it is.

Walter

On Feb 22, 2011, at 3:49 PM, Julie Maxwell Allen wrote:

Good afternoon,

I would like to announce that I have redone my website.

and would like to share it with you.

I also would love to hear all opinions.

Julie

http://www.grassrootsweb.net


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


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

Thank you! I will play with this.

On Feb 22, 2011, at 4:32 PM, Walter Lee Davis wrote:

I would style the :hover pseudo-class of the links within that box. If you’re just adding normal links here, you can do this by clicking on the outer box and using the Link Style settings in the Inspector. If you want to get fancy here, the specific settings I use for this sort of thing are as follows (you’ll need to use Extended for most of these):

#nav a {
display: block;
margin: 0;
padding: 4px 12px;
color: #fff;
}
#nav a:hover {
background-color: #ff9;
color: #000;
}

This gives you white links, and when you mouse over them, a yellow box behind and black text.

You’ll have to use the Extended interface to add everything except the font color and the background-color. The key to the effect is display: block, which forces the navigation element to have a huge “hot” area around it. This makes the navigation usable on an iPhone or similar, for one thing, and provides a nice big blotch of color when you mouse over it.

Walter

Walter

On Feb 22, 2011, at 4:22 PM, Julie Maxwell Allen wrote:

how would you hint that? arrows before?

I am not using css since there are no submenus. Plus, it throws the lineup off…


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

Thank you!

J
On Feb 22, 2011, at 4:32 PM, Walter Lee Davis wrote:

Much nicer, easier to pick out the links.

Walter

On Feb 22, 2011, at 4:22 PM, Julie Maxwell Allen wrote:

I tweaked the frog with advance fade and photo magic.


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

Thank you for catching that - It showed on my side.

I re uploaded

J
On Feb 22, 2011, at 4:34 PM, Rice Martin wrote:

Hi,

If you click on the About Us link on the nav menu, there’s no nav menu on the about us page. All the others seem fine.

Martin
Signal Mountain, TN

On Feb 22, 2011, at 4:22 PM, Julie Maxwell Allen wrote:

Thank you!

I tweaked the frog with advance fade and photo magic.

does that look better?

how would you hint that? arrows before?

I am not using css since there are no submenus. Plus, it throws the lineup off…

J
On Feb 22, 2011, at 4:04 PM, Walter Lee Davis wrote:

Loads of fun, much faster loading than your previous outing. One issue I have (others may as well) is the lack of contrast between the white type in your navigation menu (cute frog) and the background of that element. If it were me, I would use a much lower-contrast image, preferably something blurry, so that the type can be read more easily. Also, quite a lot more of a hint that these are navigation options would be a good idea. Perhaps a large block of background color as you mouse over them. They’re given awfully short shrift as it is.

Walter

On Feb 22, 2011, at 3:49 PM, Julie Maxwell Allen wrote:

Good afternoon,

I would like to announce that I have redone my website.

and would like to share it with you.

I also would love to hear all opinions.

Julie

http://www.grassrootsweb.net


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


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


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

How do you put those in extended?

I would like to do this - with the bright green and yellow that i have throughout the site.

another awesome thing to learn…

J

On Feb 22, 2011, at 4:32 PM, Walter Lee Davis wrote:

I would style the :hover pseudo-class of the links within that box. If you’re just adding normal links here, you can do this by clicking on the outer box and using the Link Style settings in the Inspector. If you want to get fancy here, the specific settings I use for this sort of thing are as follows (you’ll need to use Extended for most of these):

#nav a {
display: block;
margin: 0;
padding: 4px 12px;
color: #fff;
}
#nav a:hover {
background-color: #ff9;
color: #000;
}

This gives you white links, and when you mouse over them, a yellow box behind and black text.

You’ll have to use the Extended interface to add everything except the font color and the background-color. The key to the effect is display: block, which forces the navigation element to have a huge “hot” area around it. This makes the navigation usable on an iPhone or similar, for one thing, and provides a nice big blotch of color when you mouse over it.

Walter

Walter

On Feb 22, 2011, at 4:22 PM, Julie Maxwell Allen wrote:

how would you hint that? arrows before?

I am not using css since there are no submenus. Plus, it throws the lineup off…


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

And your Caxton is working fine!

Good job.

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thank you for that happening!!
and all of your help.

how do you like it?

J
On Feb 22, 2011, at 5:38 PM, DeltaDave wrote:

And your Caxton is working fine!

Good job.

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

If you look through the CSS code I posted here, you’ll see two CSS
“rules” one for an a tag, and the other for the :hover pseudo-class of
that a tag. First, some basic terminology. All CSS tags boil down to
these parts:

selector {
	attribute: value;
}

Everything outside of the curly-quotes is the selector – the part of
the rule that does the matching against your document, looking for
things to apply itself to. Everything inside the curly-quotes is
attribute:value pairs, separated by colons and terminated by semicolons.

Selectors have three basic elements: tag names, class names, and IDs.
There’s an additional layer of specificity possible, because you can
have more than one of each separated from the others by a space or a
special character like a + or >. You don’t need to worry about this
part right now, but I mention it because you may see it later. Tag
names are going to be things like p, h1, span, div, td – the basic
building blocks of HTML. Classnames in a selector will be preceded by
a dot, like .foo or .bar. IDs are preceded by an octothorp (#) like
#nav.

Combinations of these selector “nouns” make it possible to make a rule
apply only to very specific elements. For example, you could have a
style called div.foo and another called span.foo. Both have the
classname ‘foo’, but because they are preceded by the exact tag that
they apply to, they can be different rules, with different visual
styles produced.

You might do this in a hand-coded CSS style sheet because you wanted
to cut down on repetition. So you might do this:

.foo { color: blue }
span.foo { text-decoration: underline }
div.foo { font-size: 36px }

And you would end up with both span.foo and div.foo having blue text,
with the other local differences only applying to the div or span
variants of that class. You wouldn’t need to add color:blue to either
of those variants, because it would be covered by the less-specific
classname.

When you’re looking at a CSS rule that you see on the Web or that
someone posts here, you have to do a little bit of translating into
Freeway.

If you’re in the Edit Style dialog, you build up the selector portion
using the Tag and Name fields.

If you’re trying to create a complex selector, such as something you
found on line that was coded long-hand, you would enter the entire
selector into the Tag field, tab into the Name field, delete whatever
was there, and then tab out to leave that field blank. This is
referred to as a tag-only style in Freeway parlance. The other
specific thing about this type of style rule is that you must never
actually apply it to anything. By leaving the name field blank, you
signal to Freeway that it must always publish this rule, and by
building up the selector by hand, you are making the deal with Freeway
that you know what you’re doing and that you are pretty sure that
there are elements in your page that will match.

If you use the Name field, then you’re creating a classname-based
style, and you will need to apply it to something in order for Freeway
to publish it into the page. In that case, you don’t enter the leading
dot in the Name field – Freeway will do that for you. If you choose
or enter a proper name of a tag in the Tag field at the same time,
then you have done something that’s a little bit orthogonal to the way
CSS usually works, but is native to how Freeway works. In Freeway, you
don’t enter the actual HTML tag for a paragraph or a header, you just
type some text and select it and style it. When you create a style
that includes the H3 tag, for example, and you apply it to a block of
text, you’re actually changing that text into an H3, along with
whatever other visual style you add in the process.

Once you’re in the lower half of the Edit Style dialog and are
changing the properties of the style, you are editing the inside part
of the rule – the part found inside the curly braces of any CSS you
find written out. Many of the normal CSS attributes are present in
this dialog, but a few of them are named differently in the interface
than the real CSS attributes. So if you see a rule in CSS that
includes the line-height attribute, you’ll just have to know to
translate that into Leading in Freeway-ese. Space-before in Freeway
equals margin-top, Space-after is margin-bottom.

So if you find yourself unable to locate a particular attribute in the
Freeway interface, you may need to add it yourself (or ask for the
translation).

To use the Extended dialog, simply press the Extended button in the
Edit Style dialog. You’ll see a popup window with a list of existing
attributes (probably none if you’re just starting this process). When
you click New in that window, you’ll get yet another layer of modal
dialog with two fields: Name and Value. You enter the attribute name
(minus the colon) in the Name field, and the value (minus any trailing
semicolon) in the Value field. So if you see a CSS attribute like this:

margin: 0 0 4px 8px;

You would put

margin

in the Name field, and

0 0 4px 8px

in the Value field. Okay out of the stack of dialogs, and preview to
see your new style. Note that you most likely will not see anything
that you entered using Extended within the Design view of Freeway,
only the attributes that you can enter using the normal interface. So
you’ll have to click over to the Preview mode to see them for real.

Now there’s one last wrinkle, getting back to your original question.
I have given you the general case here, which means anything you build
using the Styles palette and its various dialogs and sub-sub-sub-
dialogs.

The Link Style dialog, accessed by clicking on the More… button in
the Link Style segment of the Inspector, presents a subtly different
form of this same Edit Style dialog. Instead of there being the Tag
and Name fields, there’s a list of the cardinal points of a link on
the left, and a cut-down form of the Edit dialog on the right.
Thankfully there is also an Extended button to get you access to the
really tweaky settings.

So to set up the link styles, you’re going in through that door rather
than the general-case Styles palette, and you’re going to choose
a:link, and a:hover from that list on the left, rather than creating
tag-only styles to do the same thing.

Walter

On Feb 22, 2011, at 4:48 PM, Julie Maxwell Allen wrote:

How do you put those in extended?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Wow. Ok - I have to play and learn this.

now when I do the css style sheet - (where would u suggest?) how do I attach it - or is it just writing it and copy / paste into the extended?

Thank you

J
On Feb 22, 2011, at 6:01 PM, Walter Lee Davis wrote:

If you look through the CSS code I posted here, you’ll see two CSS “rules” one for an a tag, and the other for the :hover pseudo-class of that a tag. First, some basic terminology. All CSS tags boil down to these parts:

selector {
attribute: value;
}

Everything outside of the curly-quotes is the selector – the part of the rule that does the matching against your document, looking for things to apply itself to. Everything inside the curly-quotes is attribute:value pairs, separated by colons and terminated by semicolons.

Selectors have three basic elements: tag names, class names, and IDs. There’s an additional layer of specificity possible, because you can have more than one of each separated from the others by a space or a special character like a + or >. You don’t need to worry about this part right now, but I mention it because you may see it later. Tag names are going to be things like p, h1, span, div, td – the basic building blocks of HTML. Classnames in a selector will be preceded by a dot, like .foo or .bar. IDs are preceded by an octothorp (#) like #nav.

Combinations of these selector “nouns” make it possible to make a rule apply only to very specific elements. For example, you could have a style called div.foo and another called span.foo. Both have the classname ‘foo’, but because they are preceded by the exact tag that they apply to, they can be different rules, with different visual styles produced.

You might do this in a hand-coded CSS style sheet because you wanted to cut down on repetition. So you might do this:

.foo { color: blue }
span.foo { text-decoration: underline }
div.foo { font-size: 36px }

And you would end up with both span.foo and div.foo having blue text, with the other local differences only applying to the div or span variants of that class. You wouldn’t need to add color:blue to either of those variants, because it would be covered by the less-specific classname.

When you’re looking at a CSS rule that you see on the Web or that someone posts here, you have to do a little bit of translating into Freeway.

If you’re in the Edit Style dialog, you build up the selector portion using the Tag and Name fields.

If you’re trying to create a complex selector, such as something you found on line that was coded long-hand, you would enter the entire selector into the Tag field, tab into the Name field, delete whatever was there, and then tab out to leave that field blank. This is referred to as a tag-only style in Freeway parlance. The other specific thing about this type of style rule is that you must never actually apply it to anything. By leaving the name field blank, you signal to Freeway that it must always publish this rule, and by building up the selector by hand, you are making the deal with Freeway that you know what you’re doing and that you are pretty sure that there are elements in your page that will match.

If you use the Name field, then you’re creating a classname-based style, and you will need to apply it to something in order for Freeway to publish it into the page. In that case, you don’t enter the leading dot in the Name field – Freeway will do that for you. If you choose or enter a proper name of a tag in the Tag field at the same time, then you have done something that’s a little bit orthogonal to the way CSS usually works, but is native to how Freeway works. In Freeway, you don’t enter the actual HTML tag for a paragraph or a header, you just type some text and select it and style it. When you create a style that includes the H3 tag, for example, and you apply it to a block of text, you’re actually changing that text into an H3, along with whatever other visual style you add in the process.

Once you’re in the lower half of the Edit Style dialog and are changing the properties of the style, you are editing the inside part of the rule – the part found inside the curly braces of any CSS you find written out. Many of the normal CSS attributes are present in this dialog, but a few of them are named differently in the interface than the real CSS attributes. So if you see a rule in CSS that includes the line-height attribute, you’ll just have to know to translate that into Leading in Freeway-ese. Space-before in Freeway equals margin-top, Space-after is margin-bottom.

So if you find yourself unable to locate a particular attribute in the Freeway interface, you may need to add it yourself (or ask for the translation).

To use the Extended dialog, simply press the Extended button in the Edit Style dialog. You’ll see a popup window with a list of existing attributes (probably none if you’re just starting this process). When you click New in that window, you’ll get yet another layer of modal dialog with two fields: Name and Value. You enter the attribute name (minus the colon) in the Name field, and the value (minus any trailing semicolon) in the Value field. So if you see a CSS attribute like this:

margin: 0 0 4px 8px;

You would put

margin

in the Name field, and

0 0 4px 8px

in the Value field. Okay out of the stack of dialogs, and preview to see your new style. Note that you most likely will not see anything that you entered using Extended within the Design view of Freeway, only the attributes that you can enter using the normal interface. So you’ll have to click over to the Preview mode to see them for real.

Now there’s one last wrinkle, getting back to your original question. I have given you the general case here, which means anything you build using the Styles palette and its various dialogs and sub-sub-sub-dialogs.

The Link Style dialog, accessed by clicking on the More… button in the Link Style segment of the Inspector, presents a subtly different form of this same Edit Style dialog. Instead of there being the Tag and Name fields, there’s a list of the cardinal points of a link on the left, and a cut-down form of the Edit dialog on the right. Thankfully there is also an Extended button to get you access to the really tweaky settings.

So to set up the link styles, you’re going in through that door rather than the general-case Styles palette, and you’re going to choose a:link, and a:hover from that list on the left, rather than creating tag-only styles to do the same thing.

Walter

On Feb 22, 2011, at 4:48 PM, Julie Maxwell Allen wrote:

How do you put those in extended?


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

If you do it in the ‘more’ section of the link styling tab then you do not need to use an external style sheet - the styles will be written into the FW doc itself.

External Style Sheets you can leave for another day!

Once you have your head around that lot - can I make a suggestion about Mr Slisz’s site. On the Testimonials page add some space between the Red quote text and the white Quoter text - if you use a series of option-spaces (non-breaking spaces) I think it will look a lot easier on the eye. Use the same amount in each to retain the staggered look. You can just select, copy and paste once you have done the first one the way you like it.

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

The rather long directions I posted were to make the styles directly in Freeway. There’s no particular reason to use an external stylesheet for this.

Walter


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Ok - you had mentioned a style sheet - and I thought you meant external… whew…

J
On Feb 22, 2011, at 8:57 PM, waltd wrote:

The rather long directions I posted were to make the styles directly in Freeway. There’s no particular reason to use an external stylesheet for this.

Walter


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 a few nit-picky things. Here’s my top three:

  1. Your page lengths, height wise, are inconsistent. For example the Why Choose, and Welcome pages have a healthy white gap underneath it but none of the other pages do.
  2. You could really kick it up to XHTML 1.0 Transitional for your DOCTYPE. HTML 4 came out in 1997 so I’m pretty sure browsers can handle XHTML no-uh-days.
  3. I’m sure you’re working on SEO as most, if not all, these pages don’t have any description, keyword, or robots meta tags in them.

Other things I noticed good or bad:

  1. Did you ever try expanding out the brown gradient thus removing the white space from the sides?
  2. I’d consider thinking about someway to show the current page, highlighted in some color, as I see you just have normal and visited states styled. You might want to think of a hover or a current color because I’m not sure what page I am on sometimes unless I re-read the title of the page.
  3. Consider renaming your page names, not page titles, to things like “contact.html” “about.html”. You have some wonky file names and it’s good to keep things simple there instead of just letting Freeway mangle them based off your page title.
  4. Consider creating a styled ‘submit’ button for your form. It looks kind of boring with just the basic browser generated button.
  5. In your drop-down for Type of Business you misspelled Professional.
  6. Consider standardizing your title to text ratio. On your business tools page you have a larger gap underneath the header and then you go to ‘logo creation’ and it’s snug to the bottom of it.
  7. Also the brown used on the logos doesn’t match the actual background. Consider them being PNG format or putting them on a background image and then tiling them neatly across.

These observations are only meant to help and to not hinder the website you’ve created here. It looks like you’ve put a lot of work into it. Best of luck with it.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thank you for you input.

I am working on the SEO… I wanted to get it up before I spent another day with that.
I did try the full brown - too much but I will throw it up and see what you think.
ok, i did not know you could change the name without changing the page titles.

I will look into all of your suggestions.

J
On Feb 23, 2011, at 3:56 AM, Dan J wrote:

Just a few nit-picky things. Here’s my top three:

  1. Your page lengths, height wise, are inconsistent. For example the Why Choose, and Welcome pages have a healthy white gap underneath it but none of the other pages do.
  2. You could really kick it up to XHTML 1.0 Transitional for your DOCTYPE. HTML 4 came out in 1997 so I’m pretty sure browsers can handle XHTML no-uh-days.
  3. I’m sure you’re working on SEO as most, if not all, these pages don’t have any description, keyword, or robots meta tags in them.

Other things I noticed good or bad:

  1. Did you ever try expanding out the brown gradient thus removing the white space from the sides?
  2. I’d consider thinking about someway to show the current page, highlighted in some color, as I see you just have normal and visited states styled. You might want to think of a hover or a current color because I’m not sure what page I am on sometimes unless I re-read the title of the page.
  3. Consider renaming your page names, not page titles, to things like “contact.html” “about.html”. You have some wonky file names and it’s good to keep things simple there instead of just letting Freeway mangle them based off your page title.
  4. Consider creating a styled ‘submit’ button for your form. It looks kind of boring with just the basic browser generated button.
  5. In your drop-down for Type of Business you misspelled Professional.
  6. Consider standardizing your title to text ratio. On your business tools page you have a larger gap underneath the header and then you go to ‘logo creation’ and it’s snug to the bottom of it.
  7. Also the brown used on the logos doesn’t match the actual background. Consider them being PNG format or putting them on a background image and then tiling them neatly across.

These observations are only meant to help and to not hinder the website you’ve created here. It looks like you’ve put a lot of work into it. Best of luck with it.


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

Ok,

I want your opinion, I expanded the brown (really I put brown as background color since the brown you see is a graphic w a star burst.

what do you think of having the brown all the way around?

http://www.grassrootsweb.net/grw

J
On Feb 23, 2011, at 3:56 AM, Dan J wrote:

Just a few nit-picky things. Here’s my top three:

  1. Your page lengths, height wise, are inconsistent. For example the Why Choose, and Welcome pages have a healthy white gap underneath it but none of the other pages do.
  2. You could really kick it up to XHTML 1.0 Transitional for your DOCTYPE. HTML 4 came out in 1997 so I’m pretty sure browsers can handle XHTML no-uh-days.
  3. I’m sure you’re working on SEO as most, if not all, these pages don’t have any description, keyword, or robots meta tags in them.

Other things I noticed good or bad:

  1. Did you ever try expanding out the brown gradient thus removing the white space from the sides?
  2. I’d consider thinking about someway to show the current page, highlighted in some color, as I see you just have normal and visited states styled. You might want to think of a hover or a current color because I’m not sure what page I am on sometimes unless I re-read the title of the page.
  3. Consider renaming your page names, not page titles, to things like “contact.html” “about.html”. You have some wonky file names and it’s good to keep things simple there instead of just letting Freeway mangle them based off your page title.
  4. Consider creating a styled ‘submit’ button for your form. It looks kind of boring with just the basic browser generated button.
  5. In your drop-down for Type of Business you misspelled Professional.
  6. Consider standardizing your title to text ratio. On your business tools page you have a larger gap underneath the header and then you go to ‘logo creation’ and it’s snug to the bottom of it.
  7. Also the brown used on the logos doesn’t match the actual background. Consider them being PNG format or putting them on a background image and then tiling them neatly across.

These observations are only meant to help and to not hinder the website you’ve created here. It looks like you’ve put a lot of work into it. Best of luck with it.


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