GoLive to Dreamweaver (gl2dw) Site Conversion Tool

Posted by on Aug 29, 2008 in Technology, Web Development | No Comments

I’ve recently gone through the painful task of using Adobe’s GL2DW extension to convert a very large heavily component-ized, heavily templated GL CS2 site to Dreamweaver CS3. This would have been a much more grizzly experience without the help of Rob Keniger of MenuMachine fame and his revisions to the GL2DW tool found here:


Also Thuy Copeland’s efforts to catalog the issues and solutions with the extension found at her site here:


I’ll summarize her findings. Prior to running the export make sure to:

  1. Rename /Extras/Library to /Extras/Library/Snippets.
  2. Remove all non-component GoLive object tags from components/templates (the GoLive datetime object, older smart rollover objects etc.).

A couple things Thuy doesn’t mention:

  1. gl2dw will not handle editable header items correctly. Beware that after conversion you templates may not have editable headers, and thus any change to the templates would overwrite the head elements of your pages. Make sure and check this and add the editable regions back in if necessary.
  2. Make sure all components and templates are loose in their respective folders, and not nested in subfolders. If you have nested folders, move the components/templates out of their subfolders (renaming if necessary). Example: /Components/interior/header.html could become/Components/interior_header.html

GoLive’s templates, components, and other Extras can be stored in hierarchal folders. Components are in the Components folder, and they can be in subfolder after subfolder after subfolder within. Example:


There doesn’t appear to be a way in Dreamweaver to organize templates and components like this. All components (called library items in DW) apparently live in one big bin (/Library for library items, /Templates for templates) with only alphabetization available to help organize them. Groan.

Behavior appears to be identical in the new DW CS4.

Leave a Reply

You must be logged in to post a comment.