Template 7 Frames: Documentation Site Layout with Frame Navigation

Template 7 Frames is the documentation-specific evolution of the frame-based layout approach in DFM2HTML. Where Template 4 Frames provides a basic persistent nav frame alongside a content frame, Template 7 Frames is built for sites that need more from the navigation side: organized sections, multi-level entries, and a sidebar structure that can hold a substantial table of contents without becoming visually unmanageable.

Template Concept

The defining characteristic of Template 7 Frames is the sidebar navigation frame designed around documentation conventions. Documentation readers navigate differently from general site visitors. They often arrive at a specific section from a search, then move laterally through related sections rather than following a linear path. They return to the same topics multiple times and use the table of contents as a spatial map, not just a list of links.

Template 7 Frames supports this pattern by giving the sidebar navigation frame enough vertical space and structural organization to function as a proper table of contents. The sidebar can hold section headers, subsection links, and additional tiers of indented entries within each section. A reader can see the whole structure of the documentation site at a glance and jump to any point in it without paging through the content itself.

The content frame on the right handles one page at a time. Because documentation pages are typically focused on a single topic, procedure, or reference item, the content frame works well with a standard single-column layout for each page. The sidebar provides the navigation context; the content frame provides the material.

Layout Anatomy

Template 7 Frames uses a three-region frameset: a thin header frame at the top that stays fixed and displays the site name and possibly a search or version indicator, a left sidebar navigation frame, and a right content frame. The header frame is the feature that distinguishes Template 7 Frames from Template 4 Frames, which uses only a two-region split.

The header frame spans the full window width above both the sidebar and content frames. It loads a single header HTML file that persists through the entire session. This is where you put the product or documentation set name, a version number if relevant, and any site-wide controls.

The sidebar frame sits below the header on the left. It loads the navigation HTML file, which contains the full table of contents for the documentation. Section headings in the nav are typically non-linking labels or collapsible triggers. Subsection links beneath each heading target the content frame.

The content frame fills the remainder of the window to the right of the sidebar. It loads whichever documentation page the reader navigates to. Content pages in this layout are designed to stand independently: each has its own heading structure, body content, and bottom navigation (previous and next page links) appropriate for sequential reading.

Section grouping in the sidebar is a key editing task when setting up Template 7 Frames. You organize all links into their sections, establish the indentation hierarchy, and ensure each link correctly targets the content frame. DFM2HTML provides the structural starting point; the content organization is something you define when populating the template.

Expandable Sections in the Sidebar

Documentation sites with large content sets benefit from a sidebar that can collapse sections the reader is not currently working in. Template 7 Frames supports a basic expandable section pattern in the sidebar nav: sections can be set up with a toggle that shows or hides the subsection links beneath a section heading.

This is implemented in the nav HTML file using simple JavaScript that adds and removes a CSS class on a container element. DFM2HTML's editor does not have a native toggle component, but the generated HTML file can be edited directly to add the expand/collapse script. The pattern is simple: a click on a section heading toggles a class on its subsection list, and a CSS rule sets that list to display:none or display:block based on the class state.

For documentation sets with fewer than thirty total pages, expandable sections add complexity without much benefit. The sidebar can hold that many links at a readable text size without requiring collapse behavior. For larger sets, collapsing inactive sections is worth the implementation effort because it makes the navigation usable rather than overwhelming.

Where Template 7 Frames Works Well

Software documentation is the strongest use case. An application with a user guide, a configuration reference, a troubleshooting section, and an API or command reference has exactly the structure Template 7 Frames was designed for. Each section becomes a sidebar group, each page in the section becomes a sidebar link, and the reader can navigate the entire documentation set without losing orientation.

Internal company knowledge bases that live on a local intranet are a second strong use case. Intranet users typically work on desktop machines in controlled browser environments, which reduces the browser compatibility concerns that apply to frame layouts on the public internet. The persistent navigation and three-region structure of Template 7 Frames performs consistently well in this context.

Technical reference sites, including specification documents, data dictionaries, and procedural guides, fit the Template 7 Frames structure well. These are sites where readers jump between sections non-linearly, return to specific entries repeatedly, and need spatial orientation in a large content set.

Offline HTML packages, such as help files bundled with software installations or reference documents distributed as self-contained archives, are a natural fit. Local HTML files loaded from disk do not face the search engine indexing concerns that apply to public frame-based sites, and they benefit from the persistent navigation that keeps readers oriented in a large document set.

Navigation Pattern

Navigation in Template 7 Frames operates at two levels. The header frame provides site-level orientation: what this documentation covers and where the reader is in the overall structure. The sidebar frame provides section and page-level navigation: which section the reader is in and what the other pages in that section are.

Within content pages, previous and next links at the bottom of each page support linear reading. A reader working through the documentation from beginning to end can follow these links without using the sidebar. A reader who arrived at a specific page from a search can use the sidebar to understand where that page sits in the overall structure and navigate to related sections.

Cross-references within content pages, links from one page to another page in a different section, should target the content frame so the linked page loads in the right panel rather than replacing the frameset. In DFM2HTML, content pages generated from Template 7 Frames have the correct default target behavior for internal links.

Responsive Concerns

Template 7 Frames inherits all of the mobile limitations of frameset layouts. The three-region structure is especially difficult to adapt to small screens because there are two fixed elements, the header frame and the sidebar frame, that consume vertical and horizontal space before the content frame receives any.

On desktop screens at 1024 pixels or wider, Template 7 Frames performs well. The header frame is typically short, the sidebar is wide enough for readable link text, and the content frame has adequate space. Below 768 pixels, the layout becomes problematic.

If your documentation will be consulted on mobile devices, Template 7 Frames is not the right structure. A single-file layout using a collapsible mobile navigation menu and a CSS-based two-column structure at wider widths will serve mobile readers without the frameset limitations. Template 7 Frames is specifically suited to controlled desktop environments where its persistent navigation structure delivers a genuine benefit over single-file alternatives.

Related Templates

For a simpler frame-based layout without the three-region structure, Template 4 Frames provides a two-region split with a persistent left nav and a content frame. It is the right starting point for smaller documentation sites that do not need the added header frame or the hierarchical sidebar organization that Template 7 Frames provides.

For documentation contexts where frame layouts are not appropriate, either because of mobile requirements or because the site is public-facing and search indexing matters, Template 2 provides a sidebar and main content column in a single HTML file. It lacks the persistent frame behavior but works correctly across all browsers and devices.