Friesland Beweegt organises up to six events a year. Every event needs it own site, to hold al the information of the event and stuff like registration. Up until now, every event had is own domain. There are some big disadvantages to this appraoch, so we've managed to incorporate them with some tricks in and around X5.

The main site http://www.frieslandbeweegt.nl has it's own project and is uploaded into the root of the webserver. This shows the general information of the foundation. Every event has it's own project too, with distinct template and sitemap. This is uploaded into a subfolder of the main sites webserver, eg. /E5D or /11S In the filestructure of the root-site. The E5D option in the main site's menu points to an empty page, without template. In .htaccess there is a redirect 301 from /E5D.html to /E5D/index.html. Selecting the E5D menu-option in the main site, takes you to the event-website with it's own destinct look and feel. Of course there's a link back from the eventsite to the foundation-site.

What are the advantages for us:

• No need for seperate domainhosting per event
• The team organizing the event can work on their own piece of the website
• Google doesn't penalize you for a 301 redirect and in the webmaster tools you can specify multiple sitemaps in one domain
• Google value of the site goes up, for there is more information and it's updated more often. The time the visitor is on the site increases as well, for he doesn't leave it when looking at one or more of the events.
• A Dutch advantage: You are only allowed to use iDeal from one domain, integrating all events into the main domain solves this problem.
• Bandwith is spread over the year more evenly. With events it usually peaks for a month and dies out the rest of the year.

Disadvantages? None as we found out now, but maybe you can name one or have a better option?