Decoupled Website Composition and Layout for Secure Dynamic Rendering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies tightly couple webpage content and layout, making it challenging to publish customized HTML content due to security constraints and regulatory compliance, especially when using custom JavaScript and external libraries.

Innovation Solution

Implementing dynamic HTML and CSS content that is uploaded to a server and rendered instantly, while maintaining compliance with security regulations, by decoupling website composition, layout, and processing through a method that includes generating event-specific welcome pages and configuration files, hashing identifiers, and using JSON files for customization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom JavaScript and external libraries are included in a webpage, then webpage functionality and customization are improved, but security constraints and regulatory compliance are violated

Engineering Contradiction:
Improvewebpage customizationVSAvoidsecurity compliance
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the webpage into static template components and dynamic content components. The static templates (HTML/CSS) are pre-approved and stored securely, while only the dynamic content (JSON data) is customizable and uploaded through approved pipelines. This segmentation allows customization without compromising security, as the executable code remains controlled and auditable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a configuration file (JSON) as an intermediary between the static template and dynamic content. This intermediary layer allows customization of webpage behavior and appearance through data configuration rather than code modification, maintaining security compliance while achieving versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If customized HTML content is uploaded through the standard deploy pipeline, then security constraints are maintained, but the deployment process becomes complex and time-consuming

Engineering Contradiction:
Improvesecurity complianceVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent separates content upload from code deployment. Customized HTML content is segmented into static templates (uploaded once through security-approved pipelines) and dynamic content (uploaded independently as JSON data). This segmentation eliminates the need for complex deploy pipelines for every content update, reducing deployment time while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses template copying where approved static templates serve as reusable patterns. Instead of deploying custom HTML code each time, the system copies approved templates and populates them with dynamic content from JSON configuration files, dramatically simplifying and accelerating the deployment process.

Inventive Principle:
Principle #26Copying

3Reliability

If static HTML and CSS files are used, then security and compliance are maintained, but webpage flexibility and dynamic content capability are limited

Engineering Contradiction:
Improvesecurity complianceVSAvoiddynamic content capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces dynamic JSON configuration files that allow webpage content and behavior to be modified without changing the static HTML/CSS templates. This dynamic layer enables flexible content updates, personalized attendee experiences, and real-time configuration changes while the static templates maintain security compliance.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables webpage customization through parameter changes in JSON configuration files rather than code modifications. By changing parameters (content, layout, behavior) in the data layer, the system achieves versatility while the static template layer maintains security and compliance.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If a single deploy pipeline is used for all webpage content, then security control is centralized, but the complexity of the deployment process increases

Engineering Contradiction:
Improvesecurity controlVSAvoiddeployment process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the deployment process into two independent pipelines: one for static templates (security-critical, low frequency) and one for dynamic content (flexible, high frequency). This segmentation reduces overall deployment complexity by allowing parallel, independent processing of different content types with appropriate security measures for each.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11734380B2Systems and methods for decoupling website composition, layout, and processing
Publication Date: 2023.08.22 JPMORGAN CHASE BANK NA
  • US11734380B2 patent drawing
  • US11734380B2 patent drawing
  • US11734380B2 patent drawing

AI summary

Systems and methods for generating a website having a decoupled composition, layout, and processing are disclosed. A method may include an event creator computer program: (1) creating an event having a plurality of attendees; (2) creating a plurality of attendee types for the plurality of attendees; (3) generating a communication template for each of the plurality of attendee types; (4) receiving an event specific welcome page for each of the plurality of attendee types; (5) receiving a website configuration file for each of the plurality of the attendee types; and (6) uploading the event specific welcome page and the website configuration file for each attendee type to a library, wherein a web site host computer program links one of the plurality of welcome pages and the website configuration file to each of the attendee types.