Template Merging for Web Page Content Editing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques for creating and editing web page templates are complex, developer-centric, and expensive, limiting non-developer users' ability to create or modify templates, and requiring recreation of templates for even minor changes, leading to inefficiencies and excessive template data.
Innovation Solution
A template system that allows users to edit template content via a user interface, with edits automatically propagated to bound web pages, using a tree structure with separate nodes for structural content and policies, enabling merging of template and web page elements during rendering, and allowing intelligent reapplication of initial content.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If conventional template creation techniques are used, then template structure and control are maintained, but user accessibility and ease of editing are severely restricted
Solution Approach 1:
The template is segmented into two distinct nodes: a structural content node containing HTML markup and a policies node containing control logic and scripting elements. This segmentation allows non-developer users to safely edit only the structural content without accidentally modifying complex policies, thereby improving ease of operation while maintaining the integrity of the overall template structure.
Solution Approach 2:
The patent introduces an intermediary merging process that combines user-edited structural content with the underlying template policies during web page generation. This intermediary layer allows users to work with simplified content while the system automatically integrates it with the complex policy structure, resolving the contradiction between user accessibility and structural complexity.
2Productivity
If template changes are made using conventional techniques, then template functionality is updated, but template recreation is required and data volume increases
Solution Approach 1:
The template structure is prepared in advance with distinct separable nodes for structural content and policies. This preliminary organization enables incremental updates where only the structural content node needs to be modified for content changes, eliminating the need to recreate entire templates and significantly reducing update time and data proliferation.
Solution Approach 2:
The patent implements a merging mechanism that combines the static template policies with dynamically edited structural content during web page generation. This allowing templates to be updated by modifying only the structural content node while preserving the policy node, enabling efficient incremental updates without full template recreation.
3Productivity
If non-developer users are given template editing access, then user productivity increases, but template integrity and policy consistency may be compromised
Solution Approach 1:
By segmenting the template into structural content and policies nodes with different permission levels, the system allows non-developer users to edit only the structural content node while protecting the policies node from unauthorized modification. This segmentation maintains template integrity and policy consistency while enabling user productivity.
Solution Approach 2:
The merging process acts as an intermediary that validates and integrates user-edited structural content with the protected policy structure. This intermediary layer ensures that user edits maintain policy consistency and template integrity while still allowing substantial user content creation capability.
Data Source
AI summary
Techniques for combining aspects of a template into multiple pages are described. In implementations, a request is received to generate a web page having digital content (e.g., text, images, videos, and so on) for display. In response to receiving the request, a template to which the web page is bound is selected. The template includes a tree structure having structural content in a first node and policies in a second node. Properties of the structural content of the template are then merged with the digital content of the web page by applying the digital content of the web page on top of the structural content of the template. The web page is then generated based on the merging.