Dynamic Page Assembly via Device-Specific Style Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content management systems face inefficiencies in generating pages for multiple target devices and sites, as existing solutions require writing multiple source files and rely on guesswork for post-processing, leading to inconsistent and costly results.

Innovation Solution

Implementing target objects that dynamically assemble page content based on the requesting device or site, allowing for consistent and efficient page generation without the need for rewriting source files, using a what-you-see-is-what-you-get (WYSIWYG) tool that requires no coding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple sets of source files are written for each target site, then the page can be customized for each target, but the time and cost increase significantly

Engineering Contradiction:
Improvecustomization for each target siteVSAvoidtime to write and maintain multiple source files
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the page generation process into a template component and a content component. The template defines the structure and layout, while content provides the actual data. This segmentation allows a single template to serve multiple target sites by dynamically injecting different content, eliminating the need to write separate source files for each target while maintaining customization capabilities.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If post-processing is used to dynamically assemble content, then the same source file can serve multiple targets, but the results rely on guesswork and are not reliable

Engineering Contradiction:
Improvereduction in source file managementVSAvoidaccuracy of post-processing assembly
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent introduces a template as an intermediary between the content and the target site requirements. The template acts as a mediator that receives content and transforms it into target-specific pages through defined placeholders and rendering instructions. This intermediary approach replaces unreliable post-processing guesswork with a systematic template-based transformation process that reliably generates consistent results across different target sites.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple source files are maintained for different devices, then each device can be optimized, but the system complexity and maintenance burden increase

Engineering Contradiction:
Improvedevice-specific optimizationVSAvoidnumber of source files to manage
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal template that can serve multiple device types and target sites. The template is designed with device-agnostic placeholders and rendering instructions that automatically adapt to different devices through content injection. This universal template performs the function of multiple device-specific source files simultaneously, reducing management complexity while maintaining device optimization through selective content rendering.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9635090B2Device abstraction for page generation
Publication Date: 2017.04.25 SALESFORCE INC
  • US9635090B2 patent drawing
  • US9635090B2 patent drawing
  • US9635090B2 patent drawing

AI summary

A request for information to be provided as a page of content is received. The page is provided by a server device communicatively coupled to receive the request from a remote requesting device. A requesting physical device class corresponding to the remote requesting device is determined. The server device is configurable to utilize a plurality of styles to be selected by device class. The page of content is constructed with the server device in response to the request based on the device class by dynamically assembling a response by providing device-specific styles that are compatible with the requesting device are selected from the plurality of styles that can be used to provide the content. The dynamically constructed page of content is transmitted to the requesting device.