This is exactly where Paminga Brand Kits<\/strong> make a real difference.<\/p>\n The Brand Kit is a centralized brand management feature<\/strong> available in the Marketing Center.<\/p>\n It allows you to define \u2014 once \u2014 the visual rules that will automatically apply to all your marketing assets.<\/p>\n You can create as many Brand Kits as you need<\/strong>:<\/p>\n Once applied, a Brand Kit controls the look & feel of:<\/p>\n In the Brand Kit, you can define:<\/p>\n Instead of working with hex codes everywhere, your teams select colors like:<\/p>\n This may sound like a small detail, but it dramatically improves usability when building pages or emails.<\/p>\n Paminga allows you to define:<\/p>\n For each style, you control:<\/p>\n All of this is managed centrally<\/strong>, meaning one change propagates instantly to every asset using the Brand Kit.<\/p>\n For emails, where font availability is always a constraint, Paminga lets you define safe fallback fonts to ensure consistent rendering across inboxes.<\/p>\n The Brand Kit also lets you define:<\/p>\n This ensures that every CTA behaves and looks the same \u2014 without relying on manual styling or duplicated templates.<\/p>\n Forms are usually the biggest pain point in marketing automation platforms.<\/p>\n Traditionally, teams create global forms<\/strong> just to centralize CSS.<\/p>\n With Paminga, the Brand Kit already does this job.<\/p>\n You can define:<\/p>\n When you update the Brand Kit, all forms update automatically<\/strong>, across the entire platform.<\/p>\n This removes one of the main reasons for maintaining complex global forms.<\/p>\n Every asset (email, LP, CTA, form) lets you:<\/p>\n Before applying changes globally, Paminga requires you to publish<\/strong> the Brand Kit.<\/p>\n You are explicitly warned about the number of assets that will be impacted \u2014 so nothing happens by accident.<\/p>\n Brand Kits are not just a design feature.<\/p>\n They are a governance and scalability feature<\/strong>.<\/p>\n They allow marketing teams to:<\/p>\n In short: fewer manual updates, fewer errors, and much more peace of mind.<\/p>\nWhat is the Brand Kit in Paminga?<\/h2>\n
\n
\n
Centralized colors, with human-friendly names<\/h2>\n
\n
\n
Fonts fully managed at the source<\/h2>\n
\n
\n
Buttons, backgrounds and hover states<\/h2>\n
\n
Forms without global CSS headaches<\/h2>\n
\n
One click to switch\u2026 safely<\/h2>\n
\n
Why it matters<\/h2>\n
\n
Discover our other Paminga Tips<\/h2>\n
![\"Paminga](\"https:\/\/merlinleonard.com\/en\/wp-content\/uploads\/sites\/2\/2025\/11\/Paminga-Tips.png\")
Salesforce integration – finally simple, clean, and manageable with Paminga<\/span><\/a><\/div><\/div>Paminga Permissions: giving the right access to the right people<\/span><\/a><\/div><\/div>The Finder: Bringing Structure to Team Collaboration<\/span><\/a><\/div><\/div>