Frameworks overview

In the legacy web workflow, the framework target is chosen before copying from the Pixflow website.

That choice controls what gets copied into Bricks:

• Pixflow variables
• mapped framework variables
• or static Raw CSS values

If you are using the plugin, choose your framework route in the plugin setup wizard instead. This section is only for the manual website copy workflow.

Pixflow Framework Use Pixflow's own variables and complete the manual framework imports.

ACSS Copy layouts using ACSS variables.

Advanced Themer Copy layouts for an existing Advanced Themer setup.

Core Framework Copy layouts for an existing Core Framework setup.

Raw CSS Copy static CSS values when no framework is being used.

Copy-time mapping Understand what mapping changes before the output reaches your clipboard.

How to choose

Choose Pixflow Framework when:

• you want Pixflow’s own design system
• you are willing to import the required Pixflow Framework files manually

Choose a mapped framework when:

• the destination site already uses ACSS, Advanced Themer, or Core Framework
• you want copied Pixflow layouts to use that framework’s variables
• you do not want to import or maintain Pixflow Framework styles

Choose Raw CSS only when:

• the destination site does not use a framework or token system
• you want static values
• you accept that global design changes will be harder later

Important rule

Pick the framework that matches the destination site.

Do not choose Pixflow Framework unless you will also complete the Pixflow Framework imports. Do not choose ACSS, Advanced Themer, or Core Framework unless that framework is already installed and configured on the site.

If you use a custom mapping from the Pixflow website, set it up before copying. The legacy web workflow does not let you keep changing mapping during the project like the plugin does.