exist GenerateBlocks With Pro version 1.7, the plugin introduces a more powerful and flexible global style system. Compared to the old version, which could only assign a single style to each element, the new system supports the use of multiple styles on top of each other and allows for clearer management of design components such as buttons and containers.
If you have used older styles in 1.6 or earlier (Legacy Global Styles), this article will show you step-by-step how to migrate these styles to the new version of the structure.
![Image [1]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520104517331-image.png)
I. Review of the old global style
In the old system, only one global style could be bound to each block type (e.g. button or container). Each style could be controlled:
- Button color, insidemargin, corners, etc.
- Top, bottom, left and right margins of the container
- Style switching between background and hover state
These styles, while basic, become progressively more difficult to maintain as the program grows.
Second, upgrade the plugin and enter the new version of the style panel
First, make sure GenerateBlocks Pro has been upgraded to version 1.7 or later.
- show (a ticket) WordPress Backstage, go to GenerateBlocks → Global Styles
- You will see a new entry on the page Legacy Global Styles
![Image [2]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520104714730-image.png)
- Clicking on this will take you to the old style management screen, where you can select the items you want to migrate.
![Image [3]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520104727881-image.png)
Three, the button style migration example
Step 1: Select the old style
Take the button style for example, click on one of the items in the list of old styles to enter the edit page.
![Image [4]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520104847630-image.png)
Step 2: Name the new style class
To enter a name for the new style, a uniform format with a prefix is recommended, for example:abc-button
![Image [5]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520105017697-image.png)
included among these abc
It can be coded for a company, project or team for easy sorting and calling at a later stage.
Step 3: Copy the old style content
By clicking the "Copy this region block style" option, the system will automatically copy all the values set in the original style (including thehoverstatus) is copied to the new version of the style system.
![Image [6]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520105054393-image.png)
Step 4: Check for style integrity
Open the new style of Spacing
,Background
,Hover
and other areas to ensure that colors, inner margins, and interaction states have migrated correctly.
![Image [7]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520105140239-image.png)
Click "Save" when you are done.
IV. Migrating container styles
The migration process for containers is exactly the same as for buttons:
- Selecting the Old Container Style
- named after
abc-container
![Image [8]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520105255768-image.png)
- Again copy the style attributes and save
![Image [9]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520105314947-image.png)
V. Calling new styles in the page
Once the migration is complete, you can use the new style classes in any page:
- stick GenerateBlocks Container Block → Add Class Name
abc-container
- Insert button block → Add class name
abc-button
![Image [10]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520110625938-image.png)
If the button style is not displayed correctly, check to see if the local style is still retained. You can remove the default style by clicking on the "X" icon to ensure that the new style takes effect.
![Image [11]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520110657902-image.png)
VI. Cleaning up old styles
When you have confirmed that all styles have been successfully migrated:
- Back to Legacy Global Styles panel
- Remove old styles that are no longer used
![Image [12]-GenerateBlocks Pro Styles Migration Tutorial: Upgrading to the New Global Styles System](http://gqxi.cn/wp-content/uploads/2025/05/20250520110733407-image.png)
- Next all pages will use the new style system, the interface is also more refreshing!
VII. Summary of advantages of the new system
The new style system offers a higher degree of freedom with a modular structure:
- Multiple style classes can be added to the element, freely combinable
- Clearer style settings, including pseudo-states (e.g. hover)
- Modify one place and automatically apply to all references
Compared to the old structure, the new system is more suitable for building a componentized and maintainable design system.
concluding remarks
If you are still using GenerateBlocks Now is a good time to migrate from the old style of Pro. The new system is not only more flexible, but also better suited for future site expansion and team collaboration.
The migration operation does not require complex setup, just a few clicks to give your design system a full upgrade.
Recent Updates
Link to this article:http://gqxi.cn/en/55310The article is copyrighted and must be reproduced with attribution.
No comments