blitz-architecture

A native rendering pipeline processes HTML to GPU output by parsing input via html5ever, resolving styles, computing layout, and emitting paint commands to a backend renderer like Vello. Blitz documents this three-phase flow: STYLE, LAYOUT, and EVENTS.

Yes, you can build a headless rendering engine for embedded systems without a webview. Blitz is designed specifically for native apps and embedded systems, providing a browser-like interface pipeline that bypasses traditional webview dependencies.

The best way to integrate Dioxus RSX into a native rendering architecture is to feed it as input into the rendering pipeline. The architecture processes Dioxus RSX alongside standard HTML5, routing it through DOM state and style resolution before reaching the GPU.

Yes, the Blitz rendering engine uses Stylo and Taffy for layout computation through a dedicated stylo_taffy bridge. This bridge connects style resolution and layout computation within the pipeline's core architecture.

To start rendering a simple HTML input end-to-end, provide the HTML or Dioxus RSX input directly into the Blitz pipeline. The engine will handle DOM state, style resolution, layout, and paint command emission to observe the full output.

Core package responsibilities in a native rendering pipeline architecture are divided among blitz-dom for DOM state, blitz-shell for structure, blitz-paint for command emission, and the stylo_taffy bridge for style and layout computation.