Block-Based Content Editing for Cross-Format Rendering Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web-based content editors face challenges in editing content due to the need to understand markup languages and account for changes that affect formatting across different browsers and formats, leading to inconsistent user experiences and difficulty in porting content between formats.
Innovation Solution
A system that stores and edits content using output-agnostic root and nested blocks, applying modifications to these blocks to regenerate content in any desired format, avoiding direct manipulation of markup language syntax and using renderers to convert data structures into specific output formats.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If web-based content editors directly manipulate markup language syntax, then content can be edited and rendered, but formatting issues arise across different browsers and formats, and porting content between formats becomes difficult
Solution Approach 1:
The patent introduces an intermediary data structure (JSON-based block structure with root blocks and nested blocks) that sits between the user interface and the final markup output. This intermediary representation allows editors to work with semantic content without directly manipulating markup syntax, while renderers convert the same data structure to different markup formats (HTML, XML, etc.), ensuring formatting consistency across browsers and formats.
Solution Approach 2:
The patent changes the fundamental parameter of content representation from markup syntax (HTML tags, CSS classes) to a format-agnostic data structure (JSON blocks with properties like type, content, style). This parameter change enables the same content to be rendered to multiple formats without loss of fidelity or formatting issues.
2Ease of manufacture
If content is stored in markup languages, then it can be rendered in specific formats, but editing requires understanding of markup languages and scope of changes across multiple sections
Solution Approach 1:
The JSON block structure serves as an intermediary that simplifies content creation by abstracting away markup complexity. Editors interact with intuitive block elements (headings, paragraphs, images) rather than markup syntax, while the system handles the complexity of generating appropriate markup for different output formats.
Solution Approach 2:
The patent segments content into discrete, editable blocks (root blocks and nested blocks) that can be independently manipulated. Each block represents a self-contained unit of content with specific properties, making it easier to edit, reuse, and manage scope of changes compared to monolithic markup files where changes can have cascading effects across multiple sections.
3Productivity
If content is edited in native markup format, then rendering is easier, but porting to other languages or formats risks formatting issues
Solution Approach 1:
The JSON block structure serves as a universal intermediate representation that can be rendered to multiple formats (HTML, XML, other markup languages) without loss of information. This multi-functional data structure enables both efficient rendering to the target format and easy porting to other formats, as the same source data can be converted to any required output format through appropriate renderers.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A content editor for generating content including root blocks and nested blocks is disclosed. The content editor can generate a deployment that includes the content. The content editor can generate user interface code configured to edit the content. The content editor can receive updates to the content and update the root blocks and nested blocks. The updated root blocks and nested blocks can be used to generate updated content for editing and/or can be deployed to end-users.