top of page

DocGear

Document Rendering Engine

A high-speed document rendering engine based on HTML, CSS3, and JavaScript, combined with data, templates, and conditional content, produces personalized documents in various formats.

Diverse Output Formats

Generate interactive HTML, PDF, and other format documents simultaneously based on requirements.

High-Speed Processing Capability

Massive Document Storage, Archiving, Search, and Management (Reference Test Data)

Parallel Scaling

Using native containers and Kubernetes for deployment and management, it automatically detects processing loads and provides real-time automatic parallel scaling.

Processing Workflow

Define custom document processing workflows, add layout processing nodes, and monitor progress at each stage.

Multi-Channel Publishing

Publish using various transmission protocols such as FTP, HTTPS, and Webhook.

Compliant with W3C Standards

Document templates use HTML, JavaScript, and CSS3, adhering to W3C standards, and can switch between PDF and interactive HTML.

通過玻璃

DocGear

DocGear is the rendering engine for SSMO Central, rapidly producing personalized documents in formats like PDF and HTML by combining data, templates, and conditional content. Using W3C standard CSS3 for layout, DocGear seamlessly integrates with web applications, allowing a single document to be rendered as both PDF and dynamic HTML without additional development.

​

Employing a microservices architecture and Docker containers, DocGear automatically scales in parallel to handle sudden surges in rendering demands, enhancing speed and performance.

​

Beyond rendering, DocGear supports document assembly and imposition. It allows for customized processing workflows, such as inserting external documents into rendered files or imposing A4 PDFs onto A3 sheets, based on different scenario requirements.

System Features

Content Accuracy Assurance for Diverse Outputs

DocGear supports native HTML templates, ensuring content accuracy during format conversions for diverse output applications. Compared to Microsoft Office, PDF layout tools, and various proprietary technologies, we provide guaranteed content accuracy.

Support for Diverse Styles and Components

Template designers can use the same technology stack as web designers, managing style diversity through CSS and utilizing various web display components. The main limitation lies in the inherent constraints and standards of different output channels or formats.

Flexibility and Scalability

We provide native container and Kubernetes deployment management, making it easy to deploy, scale, and optimize the application system lifecycle based on Kubernetes.

Product Capabilities

The table below presents a real-world test case using an insurance life policy for output. DocGear's rendering performance varies based on the complexity of the content, output format, document parsing, image format, number of images, and optimized processing with external third-party integration.
Template Technology: HTML / CSS / Javascript
Output Format: PDF
Basic Page Count: 27 pages per policy
Output Content: 27 pages of policy content, including 2 images (1487 x 2105), additional variable images, dynamically generated Code39 barcodes, and barcodes.

TuringText DocGear performance table

Application Scenarios

With advanced data processing technology,
we can quickly and accurately handle various data formats and
generate personalized output documents, enhancing your work efficiency.

Rendering Requests

Users can submit corresponding templates, data, or final result documents through the user interface to generate specific document formats via the rendering service. Submission methods are categorized into:

  • Single Rendering Request: Submitting one rendering request at a time.

  • Batch Rendering Request: Submitting multiple rendering requests at once.

Real-Time
Rendering Status

After submitting a rendering request, users can choose to wait online for the resulting document and use it for queries. The system will provide:

  • A real-time status list of 'Pending' rendering requests

  • A real-time status list of 'In Progress' rendering requests

Rendering Query

Once the rendering service completes the related tasks for a rendering request:

  • The instance of the rendering request moves to a 'Historical' status.

  • The system lists completed rendering tasks, allowing users to filter or query historical rendering requests.

  • The system provides a PDF preview of the resulting document.

bottom of page