Legacy Web Workflow

Pixflow Design is now the recommended way to use Pixflow on a WordPress site.

This section is for the older web-based workflow, where you work from the Pixflow website, choose a framework output, copy a layout or component, and paste it into Bricks manually.

Use these docs when you intentionally want to:

• copy from the Pixflow website instead of using the plugin
• choose a framework before copying
• use copy-time mapping for ACSS, Advanced Themer, Core Framework, or Raw CSS
• use Quick Copy or Rename and Copy
• maintain an older Pixflow project
• manually import Pixflow Framework files

If you are starting a new site, begin with the Pixflow Design docs instead.

Pixflow Design vs legacy web workflow Choose the right workflow before you start.

Manual workflow Follow the legacy copy-and-paste workflow from framework choice to Bricks.

Frameworks Choose Pixflow Framework, ACSS, Advanced Themer, Core Framework, or Raw CSS.

Copy-time mapping Understand how Pixflow rewrites variables before the copied output reaches Bricks.

What this section covers

• how the legacy web workflow differs from the plugin workflow
• how website copy and paste works
• when to use Quick Copy or Rename and Copy
• how framework selection affects copied output
• when Pixflow Framework imports are required
• what one-time web-based mapping does and does not do

Main rule

The web workflow is copy-and-paste only and manual by design.

It does not automatically configure the destination site, validate Pixflow Design setup, manage ongoing site-specific mappings, or run Pixflow Design AI workflows.

Custom mapping in the web workflow can only be set up once. If you need to change custom mapping later, use Pixflow Design instead.

If you want Pixflow to behave like a site-level tool inside WordPress and Bricks, use Pixflow Design.