Thanks Mariena,
I have a design for workspace default headers/footers, and I think our templates project is going to help address this as well. Sorry we don’t offer it right now.
Putting headers/footers in theme felt like the wrong approach for use for a few reasons:
- 1.
It’s content, not styling, and it would be easy to accidentally change multiple gammas at once
- 2.
We want themes to be reusable across artifacts, and it doesn’t support eg. “presentation defaults”, “social defaults” etc—you’d have to make multiple duplicate themes
- 3.
It opens the door to three levels of inheritance if we wanted to ever support card-level headers, which felt overwhelming
- a.
Theme > overriden at gamma-level > overridden at card-level