A single puzzle piece overlaying a completed puzzle

Framework Builder 1.0.2

Solve the hassle of includes and DWTs with a framework that you can easily maintain.

Watch Now

ONLY $99.99

Included in Design Extender

15 day money-back guarantee

Upgrade Now Buy Now

Framework Builder Overview

Use themes and just say no to DWTs

Updating a theme won't require updating associate files.

When you update a Dreamweaver template, all your files associated with that template need updating and uploading. It's a headache - and a huge risk for a large site. With Framework Builder's themes, your templated areas (such as header or footer) on pages using that theme are loaded dynamically. No need to update any other files! Easily convert a DWT to a theme and create pages based on that theme.

Load themes and plugins dynamically

Static or dynamic; it's your choice.

Want to load a theme element (like site's background image) depending on the user's setting? Set your themes to load based on a trigger variable with Framework Builder's simple interface. Want to load different content (such as form fields) depending on what the user selects above it? Just specify what plugin the page should load based on your criteria!

Use plugins to load your page content

Like Includes, except they actually work in Dreamweaver

When you use includes in a site with a sub-folder structure, your paths (to images and such) will either work if the path is correct in the include file or will display in Dreamweaver if the path is correct in the file the include is used in. Not both. With Framework Builder's plugins, paths are detected and dynamically updated to work both in Dreamweaver and in the browser! (This feature replaces ADDT Includes.)

Plugins help you manage your CSS

Solve another problem that Includes introduce.

Say you have separate CSS for each include file. Just manage your include page like a regular page with a CSS file reference. When you include the plugin on a page, Framework Builder (unlike Includes) will detect that CSS reference and move it to the correct location (the <head>) to pick up the correct styles.