Something I care a lot about as a template creator: making rebrand-ability actually easy, not jus...Something I care a lot about as a template creator: making rebrand-ability actually easy, not jus...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Something I care a lot about as a template creator: making rebrand-ability actually easy, not just "technically possible."
AETHER runs on tokens one value change updates color, type, and spacing sitewide. No hunting through 40 layers to change a button color.
Curious how other creators here balance flexibility vs. simplicity in their own systems too many exposed variables and it gets overwhelming, too few and it feels locked in. Where do you land?
Post image
Asif's avatar
I expose only the tokens a client will actually touch (brand color, type scale, spacing rhythm) and lock everything else behind those. Semantic names like primary and surface travel far better than raw hex values, since the client edits meaning, not the paint. Component-level variables stay internal.
GHAZI's avatar
Completely agree semantic naming over raw hex is where most systems either scale well or fall apart. Locking component-level variables internally is the right call too.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started