Würth goes WB

albatros

That's right -  a very professional site! I like it too!

Hi Chio,

one question: on the pages of the footer-menu I don´t have any other navigation (top, breadcrumbs and left). Did you whant to have it this way?

Best regards

Uwe

أنا لست إرهابيا. ليس لدى أي ورشة عمل القنبلة في الطابق السفلي. ليس لدى أي مرض الجمرة الخبيثة أيضا. أريد شراء لا مادة الريسين. أنا سوف ابدأ السفر إلى الولايات المتحدة الأمريكية

Argos

Quote from: chio on July 03, 2009, 03:21:19 PM
Yep,
www.orsy.at
Yep, very profi site! I like it a lot.
Jurgen Nijhuis
Argos Media
Heiloo, The Netherlands
----------------------------------------------------------------
Please don't request personal support, use the forums!

chio

No, it isn't cached. Maybe in the future.

Its like Mathias said with changed options (extension: html) and html parsed as php. But its not with the included .htaccess.

I mostly use html-extension, for a simple reason:
In a bad case (hacker...) or some technical reasons I might be forced to make the complete site static. I can download the complete site (as is) with GetLeft and keep it as a full backup. In worst case I can upload the complete static pages and the URLs are not changing.
This will not happen - I know.

Another simple reason: If I decide to make caching (by use of full static pages) the urls are also not changed.

mr-fan

Quote from: ruebenwurzel on July 04, 2009, 02:45:01 PM
Hello,

how did you the .html stuff? With changing it in the WB options and using the in WB included .htaccess or in another way?

Matthias

http://www.beesign.com/WebsiteBaker/pages/posts/caching-mit-websitebaker33.php

:-D

martin

chio

Yo, its the number of menu-items, that makes the backend slower and confusing, when a site is getting bigger.

If you use modules like News, Bakery, Topics.. you have less menu-items.

And if you use frontend-admin ("edit this page") to jump directly from the frontend to the backend it doesn bother you.

At orsy.at I have a lot of hidden WYSIWYG-pages; with a picture menue made with Members, and on the part
Fahrzeugeinrichtung we use the "Topics"-module, which makes a "build in" picture menue.

The html-stuff?  I have no access to the .htaccess, the provider arranged this.

ruebenwurzel

Hello,

how did you the .html stuff? With changing it in the WB options and using the in WB included .htaccess or in another way?

Matthias

erpe0812

Hi Vincent

the AMASP Project has about 500 pages and no problems. Maybe it depends on kind of sections. I suppose the more wysiwyg the slower the site in the backend. I don't think that you will see it in the frontend.

Quotesome short phone calls instead of a thick manual
This is the real advantage for the companies.

rgds

erpe

chio

Yes, I think its important, that also bigger companies use WB; as a model role. WB is well established on private or smaller business sites, but not so for bigger companies.

Its not the problem with the number of pages. orsy.at has ca. 70 pages; I have some much bigger sites (At the moment I am working on a site with over 200 pages - at the start)

Even the main Würth site - wuerth.de - doesnt have very much pages, if you exclude the masses of product pages - which come out of a product database. You could handle this with WB also. But I guess, they wont do ;-)

Why we choosed WB for orsy.at:
The site is merged from some other domains - wuerth.at, wuerth.de and some more. Of course one can take the pages as they are, but how put them together? There is lot of double or unfitting content,  other contact persons, phone...
An employee has to check everything and directly change it - easy and without training, by the way.

I also administer the site wuerth.at, and I know well, how difficult this is for people without training. WB is much easier, the Würth people had no problems at all; some short phone calls instead of a thick manual.

Vincent

Well done, Chio.
Great to see a major company using WB. We should get to a level of market penetration where we don't consider it remarkable but logical. But it needs to start somwhere, so I agree: remarkable choice.

Can you tell us how many pages the site consists of currently? And do you encounter problems with so many menu-items?

You managed to keep the look and feel of Wurth company, so compliments about that.

Regards,
Vincent

chio

Yep,
www.orsy.at

The most remarkable thing is: Würth Austria decided to use WebsiteBaker for a site about its major product.
"Could it be, that this CMS is 10 times better than ours?" - "Oh no, only 5 times better" ;-)

My job was to make the site look and feel exactly like the Würth-CI and combine lots of different contens to one site.
The biggest problem was the masses of menu-links. I made a special funktion to change the links to the "real" links.
The second thing: The subheadings in the left menue. These are also made with menu-links.

Its not fully finished yet, but its online at last. Phew!