General Community > WebsiteBaker Website Showcase

and now: something completely different...

<< < (2/3) > >>

chio:
Search engines dont have any troubles with iframes, the whole site ist indexed already:
http://www.google.de/search?q=site:room66%2eat

There is no "accessibility problem", except the design doesn't work on older browsers or small screens. The iframes are simple subpages.

There would be more problem with scrollable divs, because they would create "hidden text", if there is more than one "subpage" - which can be a big problem. And there would be lots of troubles with the modules...

I took care to make a "normal" template, it isn't necessary to make any changes in WB to use this template. When you view a single page in the backend, it is shown as a single wall (with its subpages)

I am trying to create a "common useable template" at the moment, here is my "playground":
http://www.beesign.com/WebsiteBaker/rooms/

(Sorry for my poor english )

bgg:
wow.. very good.

I wonder if you could make a step-by-step documentation to achieve a template like yours with all the components used !!!

Thanks

Coops:

--- Quote ---Search engines dont have any troubles with iframes, the whole site ist indexed already:
--- End quote ---

Yes, but when searching on Google, all pages might be indexed but they will bring up a result like this: http://www.room66.at/pages/buchen/preise.php

Your visitors won't see the nav bar and the fancy scrolling, just some text out of context.

Having said that, I LOVE the way the header moves along as you scroll. That's great!

chio:

--- Quote ---Your visitors won't see the nav bar and the fancy scrolling, just some text out of context.
--- End quote ---
Yes. This is the REAL problem with frames.
But: If the page is out of the context, you see a red line with link to the parent page. The content of the frames ist not that much, I think this should not be a big problem for visitors. I have a lot of sites using frames, most visitors dont have any troubles with them.

A Javascript reloader-script is also prepared, but I decided not to use it:
Google has no problem with frame reloaders, when they reload the parent page (=the frameset) with the original (=listed) frame in it. Google sees a framesset as a whole thing - with all its frame-content.
This could make troubles here.
And one thing more: A frame-reloader could make problems when printing a single frame.

Documentation:
yepp, is german only:
http://www.beesign.com/WebsiteBaker/templates/rooms/help.html
As you see, my English is _not_ very good... ;-)

Coops:
each to their own :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page