DFM2HTML Version History and Capability Notes

The history of DFM2HTML is the history of desktop web design tools trying to stay relevant as the web changed around them. This page covers the capability milestones and observable evolution of the software, from early releases focused on basic page layout and table-based structure through the periods of CSS maturation, JavaScript menu integration, and the eventual shift to responsive design considerations. Where specific release dates are confirmed by visible documentation, they are noted precisely. Where the timing is approximate, the language reflects that. This is not a fabricated timeline. It is an honest account of how the tool developed based on available evidence and the broader context of what was happening in desktop web authoring during each period. For the ongoing maintenance log, see the changelog. For the broader software evolution overview, see the history section.

Early Releases and the Table Layout Era

The earliest versions of DFM2HTML appeared during the era when table-based HTML layout was the standard approach to page composition. Before CSS had reliable cross-browser support for layout, the practical method for placing page elements predictably was to use HTML tables as invisible structural grids. Visual editors of that period generated complex nested table markup to achieve the column and row structures that their canvas represented.

DFM2HTML followed this pattern in early versions. The template set reflected the constraints of table-based layout: fixed column widths, header and footer regions defined by row spans, and navigation bars positioned through table cell alignment. The output was technically correct for its time and worked predictably in the browsers of that period.

The templates from this era have a characteristic directness. They make the page structure obvious because the structure is the table. Later versions maintained compatibility with this generation of templates while adding the ability to produce CSS-based alternatives for users who wanted cleaner markup.

The DHTML and JavaScript Menu Period

As browser JavaScript implementations stabilized across Internet Explorer and Netscape Navigator, visual editors gained the ability to add scripted behaviors to exported pages. For DFM2HTML, this meant JavaScript menu support became a significant feature. The menu system allowed sites built with the editor to have dropdown navigation without requiring server-side scripting or frame-based navigation structures.

The JavaScript menus were significant because they solved a real structural problem in static site publishing. A site with ten sections and nested subsections needs navigation that scales. A flat list of links in a sidebar becomes unusable past a certain size. Dropdown menus gave DFM2HTML sites a navigational model that could grow with the site without requiring a restructuring of the page layout.

The JavaScript menus page covers the current implementation of the menu system in detail. The underlying approach has evolved but the core principle remains the same: lightweight, self-contained scripts that attach to the HTML structure the editor produces, without requiring a build pipeline or external dependencies.

CSS and Structural Markup

When CSS layout support became reliably usable across major browsers, DFM2HTML updated its output approach. The shift away from table-based layout was gradual. Early CSS templates maintained similar visual results to the table versions while using properly structured HTML with CSS for presentation. The templates in this generation introduced class naming conventions, external stylesheets, and a cleaner separation between the structural markup and the visual rules that styled it.

The significance for users was that CSS-based pages were easier to maintain after export. Changing the color scheme of a table-based site required hunting through inline styles embedded in individual table cells. A CSS-based site allowed the same change in a single external stylesheet. For the kinds of small business sites and documentation collections that DFM2HTML targeted, this was a meaningful practical improvement.

Frame-Based Templates

Frame-based HTML layouts were a distinct feature category in desktop web design tools for a period when they were the standard mechanism for persistent navigation. DFM2HTML included frame-based templates that used HTML framesets to keep navigation visible while the content area scrolled or loaded new pages. This matched how a significant portion of corporate intranets, documentation sites, and tool-driven interfaces were built at the time.

Frame templates remain in the DFM2HTML template set because they serve legitimate use cases and because preserving the template structure allows users to work with existing frame-based sites. The documentation for Template 4 and Template 7 includes current guidance on when a frameset approach is still appropriate and how to handle the modern browser considerations that frame layouts introduce.

Responsive Design Considerations

The emergence of smartphones as primary browsing devices created pressure on all desktop-first web design tools. DFM2HTML's design model is rooted in the fixed-width desktop canvas, which does not automatically translate to fluid, responsive layouts. Later documentation and template updates addressed this honestly rather than overclaiming flexibility that the core editing model does not fully support.

For the kind of sites DFM2HTML is designed for, particularly structured pages for small businesses, documentation collections, utility tools, and compact brochure sites, a well-built fixed-width layout with a sensible maximum width is still a practical choice. The layout demo explores the range of fluid layout behavior the tool can produce.

The Wikipedia article on WYSIWYG editors provides broader context for how visual HTML editing tools have developed over time and the industry dynamics that shaped the tools in this category.

Current Status and Ongoing Development

DFM2HTML continues to be maintained as a practical desktop HTML editor for Windows. The software runs on current Windows 10 and Windows 11 builds, the template library covers common site structure patterns, and the JavaScript menu system handles modern browser requirements including keyboard accessibility and touch device behavior.

The download page has current installer packages for both 32-bit and 64-bit Windows systems. The features page covers the current capability set. The changelog tracks recent maintenance updates and documentation improvements.