HTML to Bricks
HTML to Bricks converts generated or uploaded HTML into Bricks elements.
The same shared pipeline is used by:
- project Handoff to Bricks
- home workspace composer HTML to Bricks
- floating panel
@HTML to Bricks
Inputs
Section titled “Inputs”Pixflow can work from:
- an HTML file
- a prompt
- a brief file such as
brief.md - screenshots or image references
Files-only runs should work when the provided files contain enough context. In the floating panel, include @HTML to Bricks so Pixflow knows which workflow to start.
Pipeline stages
Section titled “Pipeline stages”- Stage A produces or receives the HTML.
- Pre-stage B maps HTML and CSS to Bricks JSON.
- The converted structure is inserted into the Bricks canvas.
- Stage B uses Bricks skills to refine the result.
- The final message explains what was changed.
Quality expectations
Section titled “Quality expectations”Pixflow should preserve visual parity with the original HTML while moving as much styling as possible into Bricks-native controls:
- section top and bottom padding
- container width and horizontal padding
- button style options
- heading and text typography
- Google font installation
- icon set installation and icon dimensions
- SVG elements when SVG support is enabled
- responsive breakpoints
- hover and active states
CSS that does not map cleanly to Bricks controls should stay in scoped custom CSS.
Learn