Our existing website uses Dreamweaver templates and libraries.  It was converted from ASP to ASP.NET v1 in the days before Master Pages, so it uses some pretty complicated nested Dreamweaver templates which map to ASP.NET pages.  Dreamweaver often struggles with the nested templates.  I really won’t miss Dreamweasel one bit – shame, it was a nice bit of software in its day.

Anyway, the Dreamweasel templates will go, to be replaced by Master Pages which Umbraco lets me used in a nested way.

The library files hold the sub-menus for each section (which I won’t need in Umbraco as the navigation will be automatically rendered via XSLT macros.  They also hold some cross-page content – for example, cross-selling panels (e.g. If you like X, you might want to link to Y).  To retain this functionality, I created a Folder document type in Umbraco, created a library folder (just for old time Dreamweaver sake), then created a Library Item document type, with a bodyText rich text editor field to hold the content.  Then I created some Library Item documents before the Library folder.  Then I created a XLST macro to display the Library Items, using a Content picker as a property to select the relevant Library Item and popped the macro into a template.  Should work fine.