GraFx Experience
The story behind GraFx Experience
It's Thursday afternoon. A store owner in Lyon needs a promotional poster — the sale starts Monday.
There's no designer available. No time to brief one. But the poster needs to be on-brand: the right colors, approved imagery, correct legal text. Getting it wrong isn't an option.
She logs into a portal. Finds the campaign. Picks her layout.

She Updates the headline, swaps in the local offer, and downloads a print-ready file — in minutes, without touching anything she shouldn't.

How is that possible? Because someone at HQ already did the hard work.
A designer built the campaign in GraFx Studio — locking in brand colors, approved imagery, the right fonts, and all the rules that keep things consistent. A Design System is not just a file. It is the brand logic, the guardrails, and the creative framework all in one.
To make that campaign available to store owners like her, HQ sets up a branded portal — their own corner of the web, with access controls and output settings already in place. That portal is GraFx Experience.
The bridge between the Design Systems in GraFx Studio and the portal is the CHILI GraFx extension — where HQ defines which Design Systems are available, who can access them, and how output is produced.
Designers create. HQ publishes. Local teams activate.
In this section
- GraFx Experience — What the portal is and how it works
- CHILI GraFx extension — How Design Systems are made available in the portal
- Configure a Design System — How to link and configure a GraFx Studio Design System for use in GraFx Experience