I have a simple 3 column layout inside a wrapper div where my source order is
#content/#sidebar1/#sidebar2, and I am using a negative margin on #sidebar1 to
pull it over so the display order is #sidebar1/#content/#sidebar2. It works
great in the browser, but #sidebar1 disappears in Dreamweaver. Any experience
with this?

jaymcdonald wrote:
> I have a simple 3 column layout inside a wrapper div where my source order is
> #content/#sidebar1/#sidebar2, and I am using a negative margin on #sidebar1 to
> pull it over so the display order is #sidebar1/#content/#sidebar2. It works
> great in the browser, but #sidebar1 disappears in Dreamweaver. Any experience
> with this?
>

Why are you using the <divs> in that order....search spider?

It's simpler just to have

#sidebar 1
#content
#sidebar2

Then float all three left.

Dreamweaver design view has never been and is still not 100% accurate
and using negative margins won't help.

Yes, the source order is for SEO. I know I could just re-arrange the source
order, but that would defeat why I did it in the first place. It seems silly to
have to break that just because Dreamweaver is confused by it. Why can't it
just show it properly?

I've noticed on occasion that a dreamweaver display bug like this is
overcomeable with a little extra css. Anyone have an idea here?

It's called the Holy Grail template. And you're right, it doesn't render
well in Design View. Hit F4 to resize the viewable pane. Or just work in
code view, and keep your browser opened. After making changes, save the
page then refresh browser to view your progress.


--Nancy O.
Alt-Web Design & Publishing
www.alt-web.com

"jaymcdonald" <webforumsuser@macromedia.com> wrote in message
news:g6ac4q$n97$1@forums.macromedia.com...
> I have a simple 3 column layout inside a wrapper div where my source order
is
> #content/#sidebar1/#sidebar2, and I am using a negative margin on
#sidebar1 to
> pull it over so the display order is #sidebar1/#content/#sidebar2. It
works
> great in the browser, but #sidebar1 disappears in Dreamweaver. Any
experience
> with this?
>

.oO(jaymcdonald)

>Yes, the source order is for SEO.

And? Any evidence that it works?

>I know I could just re-arrange the source
>order, but that would defeat why I did it in the first place. It seems silly to
>have to break that just because Dreamweaver is confused by it. Why can't it
>just show it properly?

To me it seems to be silly to use an illogical markup order just for
questionable SEO reasons, even though it's not that bad in this
particular case. Content first is a quite common structure, but not a
necessity.

On my own sites the navigation lists usually come first for technical
reasons - no problems with that. There's enough useful content further
down the pages and enough food for the SE spiders. A good SE ranking is
not a question of "markup order", but of patience, appropriate markup,
patience, usable content and patience.

Keep the markup in a logical order and try to avoid hacks like negative
margins (yes, it's just a hack in most cases). Make sure that it works
even with CSS disabled. Focus on usability and accessibility. Make your
site userfriendly! This will also almost automatically make the site SE-
friendly, because an SE bot is nothing else than a user. A blind user.

Micha

My feeling is that in the list of things that affect SEO, this one would be
so far down, it's not worth the additional effort. Let me state it this
way - if you have done all of the things that would fall above it, then I
guess you will see zero impact of this on your page's rank.

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Michael Fesser" <netizen@gmx.de> wrote in message
news:kkhh84990u92mv3ppogpe1n8a27cpu0bar@4ax.com...
> .oO(jaymcdonald)
>
>>Yes, the source order is for SEO.
>
> And? Any evidence that it works?
>
>>I know I could just re-arrange the source
>>order, but that would defeat why I did it in the first place. It seems
>>silly to
>>have to break that just because Dreamweaver is confused by it. Why can't
>>it
>>just show it properly?
>
> To me it seems to be silly to use an illogical markup order just for
> questionable SEO reasons, even though it's not that bad in this
> particular case. Content first is a quite common structure, but not a
> necessity.
>
> On my own sites the navigation lists usually come first for technical
> reasons - no problems with that. There's enough useful content further
> down the pages and enough food for the SE spiders. A good SE ranking is
> not a question of "markup order", but of patience, appropriate markup,
> patience, usable content and patience.
>
> Keep the markup in a logical order and try to avoid hacks like negative
> margins (yes, it's just a hack in most cases). Make sure that it works
> even with CSS disabled. Focus on usability and accessibility. Make your
> site userfriendly! This will also almost automatically make the site SE-
> friendly, because an SE bot is nothing else than a user. A blind user.
>
> Micha

.oO(Murray *ACE*)

>My feeling is that in the list of things that affect SEO, this one would be
>so far down, it's not worth the additional effort. Let me state it this
>way - if you have done all of the things that would fall above it, then I
>guess you will see zero impact of this on your page's rank.

Yep, something like that. Other things are much more important.

Micha