Locking Static Site Layout with Dreamweaver .dwt Templates

Desired outcome

Updating a navigation link or a footer address across a twenty-page static site normally means opening every HTML file and repeating the same edit. Adobe Dreamweaver Templates (.dwt) eliminate that repetition by separating shared layout from page-specific content. The goal is one master template that locks headers, navigation, and footers, while exposing designated editable regions so content authors can change only the text inside those regions.

Prerequisites

• A local site defined in Dreamweaver with a root folder and a default images folder. Templates live in a Templates subfolder that Dreamweaver creates inside the site root.
• At least one representative HTML page that already contains the shared structure you want to reuse.
• Write permission to the site root folder on your local file system. No elevated operating-system permissions are required.
• A backup or version-control snapshot of the site folder before you create the first template, because saving a page as a template and later running batch updates changes many files.

Procedure

Save a representative page as a template

Open the source HTML page in Dreamweaver. Choose File > Save as Template. In the dialog, enter a name such as <template-name>.dwt (for example, site-shell.dwt). Dreamweaver stores the file in the site's Templates folder. The original HTML page remains unchanged; the new .dwt file becomes the master.

Risk: Moving or renaming the .dwt file outside Dreamweaver—such as through your operating system's file manager—can break the link between the template and its child pages.

Lock shared markup and insert editable regions

Any template content that sits outside an editable region is locked by default. Leave your header, navigation, and footer markup outside editable regions so authors cannot alter them accidentally.

Place the cursor where page-specific content should appear. Choose Insert > Template > Editable Region (in some releases the path is Insert > Template Objects > Editable Region). Name the region descriptively, for example main-content or sidebar. Repeat for each area that authors need to change.

Limitation: Editable regions cannot be nested inside one another. If you need a repeating list inside a region, use a separate repeating region rather than nesting editable regions.

Create child pages from the template

Choose File > New, select the Page from Template category, pick your site, and choose the .dwt file. Save the new page inside the site root. Populate only the editable regions; locked areas remain read-only in Design view.

Propagate structural changes with Update Pages

When you need to change navigation, a footer, or any other locked markup, open the .dwt file, make the edit, and save. Dreamweaver prompts you to update pages that use the template. Choose Update Pages, select Entire Site and your site name, then confirm.

Expected check: After the update finishes, open two or more child pages in a browser preview or Live View. Each page should show the new locked markup while retaining its own editable content.

Expected checks

1. Open a child page and try to type inside the header or footer. Dreamweaver should block the edit and show the region as non-editable.
2. Click inside an editable region and type. The region should accept input normally.
3. Preview the page in a browser to confirm the template-generated HTML renders correctly.
4. Run File > Validate > Markup on a child page to ensure the HTML remains well-formed after a template update.

Recovery options

If a batch update corrupts pages or produces unwanted markup, restore the affected files from your local backup or version-control snapshot. Do not attempt to hand-edit the template comment markers that Dreamweaver inserts into child pages.

When a single page must diverge permanently from the template, open that child page and choose Modify > Templates > Detach from Template (in some versions, Tools > Templates > Detach from Template). This converts locked regions into ordinary editable HTML. The page will no longer receive future template updates, so use it only when necessary.

Limitations and version notes

Menu paths and dialog labels vary between Dreamweaver releases and localizations. Confirm the exact wording in your installed version before following the steps above.

Deleting an editable region from a template may leave orphaned content in child pages that no longer matches the new structure. Review child pages after removing a region.

Large sites with many linked assets can experience slower update cycles. Close unused documents before running Update Pages to reduce memory pressure.

Practical verification example

Create a two-page test site from one template. Generate index.html and about.html from site-shell.dwt. Edit the navigation markup in the template—for example, change a link label—save, and run Update Pages for the entire site. Open both pages in a browser preview. If both display the new navigation while keeping their own main content, the template workflow is functioning as intended.