Maintaining shared page elements in one place reduces repeated editing while allowing each page’s content to suit its subject. The server combines the selected record with the maintained navigation and other common elements before sending the page to the browser.
Share the structure that should stay shared.
If an organization's menu appears in fifty documents, a change can leave a handful of pages behind. Assembling that menu from one maintained source gives every page the same navigation before it reaches the reader. Each article keeps its own content while using the same maintained menu. The illustration sends one header into a project page, an article, and a contact form. Their main content has different shapes because their jobs differ. The shared header helps people find their way while allowing each page to choose its own introduction and layout.
Maintaining these elements together reduces the chance that pages will develop inconsistent menus or headers. Keep the article's voice and content in its own record, then apply the common shell consistently. The shared elements should leave each article room for its individual explanation. Assembly also makes it possible to apply a common rule consistently, such as using one approved header asset or one source for navigation destinations. A necessary change can then reach every page while preserving the content and layout that make each one useful.
Put it into practice.
Identify the elements whose meaning and behavior should remain shared. Maintain each in one place, assemble them with the selected record, and return a usable page. Keep page-specific content in its owning record instead of filling the common shell with generic introductory copy.
Which repeated element should be maintained in one place?