The next version will have a new skinning system. Not that the code is going to be completely different, but I'm moving everything that has anything to do with the visual appearance to its own project. This way it will be way easier to change the look and feel of the site, including the menu system. 
For a long time I thought we didn't need a fancy skinning system but the last upgrade of this site (with some SQL hacking to change the templates) and the fact that people actually start using Cuyahoga for their sites convinced me that this has to be improved.

Also on the list is a menu system that allows you to create pages outside the node hierarchy. This can be useful for pages or modules that are more or less 'global' like the search page or a sitemap. These menus will be attached to a placeholder in the template just like the sections.

I haven't started coding yet and I'm not completely sure about the design, so feel free to drop any suggestions!

Oh btw, for all NHibernate enthousiasts out there, the development version is now using version 0.7.0.0 of NHibernate. It had to do 2 little modifications related to the change in the NHibernate types en ISession.Find(). Everything runs fine, or even better now. The new ISession.Lock() feature works perfectly for re-attaching cached objects. I've got a slight feeling that the performance also has improved with the change (but that's pretty hard to measure because building a page from cached objects is too fast for the resolution of a .NET Timespan ;)).

It took a little longer than the previous releases, but here it is: Cuyahoga 0.6.0.

Highlights of this release are:

• Search
  You can now index and search content. Currently the content of the Articles module and the StaticHtml module is indexed by default. A more technical explanation of how the search works can be found here.
  
• LanguageSwitcher
  From the first release, Cuyahoga supported content localization but it was not so obvious how to achieve it. Content for a different language or culture has to have its own root node (within an existing site). You have to build a structure of nodes and sections for each language.
  The LanguageSwitcher module enables easy navigation between the localized site structures.
• New template and navigation control
  Customizing and skinning of Cuyahoga is not very easy for non-ASP.NET developers. The new template is set up in such a way that most customizing can be done by only modifying the stylesheet.
  
  

You can now check out the Cuyahoga sources with anonymous svn. The repository is at http://tijnthuus.demon.nl/svn/repos/cuyahoga/trunk.

You can now search the Cuyahoga website. Before releasing it with the new version, this site temporarily serves as a test environment  for the search to see how it behaves in a production environment. Just give it a try!

The search functionality is build with DotLucene. This is a very nice indexer and search engine. It doesn't take care of gathering the content, so you have to build that yourself. Therefore the modules that are searchable have to implement the ISearchable interface. When done, all indexing happens automagically (after adding, updating or deleting content). You can also rebuild the entire search index from the administration site.

Searching will be included in the next version (0.6.0). This version will be released in a few days. I just have to fix some little bugs and I'll add a language switcher module to show how Cuyahoga handles multi-lingual websites.

To give the Cuyahoga web site a less IBuySpy-like appearance, I changed the design a little bit ;). This implied creating a new Template User Control, a new stylesheet and a new navigation User Control.
When doing the last one I figured out that there are quite some things that can be improved. For example, the navigation control has a code-behind class that  requires recompiling the Cuyahoga.Web .dll. This makes customization a bit harder then it should.

Oh yeah, one thing: the forum still has the old template because it has tables with a specified width of 100% and that messes up the new layout in IE.

I'd appreciate any feedback!