All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.
4.10.0 (2022-03-16)
Note: Version bump only for package gatsby-design-tokens
4.9.0 (2022-03-01)
- Format changelog files (088f23b)
4.8.0 (2022-02-22)
Note: Version bump only for package gatsby-design-tokens
4.7.0 (2022-02-08)
Note: Version bump only for package gatsby-design-tokens
4.6.0 (2022-01-25)
Note: Version bump only for package gatsby-design-tokens
4.5.0 (2022-01-11)
Note: Version bump only for package gatsby-design-tokens
4.4.0 (2021-12-14)
4.3.0 (2021-12-01)
Note: Version bump only for package gatsby-design-tokens
4.2.0 (2021-11-16)
4.1.0 (2021-11-02)
Note: Version bump only for package gatsby-design-tokens
4.0.0 (2021-10-21)
3.14.0 (2021-09-18)
3.13.0 (2021-09-01)
3.12.0 (2021-08-18)
3.11.0 (2021-08-04)
Note: Version bump only for package gatsby-design-tokens
3.10.0 (2021-07-20)
3.9.0 (2021-07-07)
3.8.0 (2021-06-23)
3.7.0 (2021-06-09)
Note: Version bump only for package gatsby-design-tokens
3.6.0 (2021-05-25)
Note: Version bump only for package gatsby-design-tokens
3.5.0 (2021-05-12)
Note: Version bump only for package gatsby-design-tokens
3.4.0 (2021-04-28)
Note: Version bump only for package gatsby-design-tokens
3.3.0 (2021-04-14)
Note: Version bump only for package gatsby-design-tokens
3.2.0 (2021-03-30)
Note: Version bump only for package gatsby-design-tokens
3.1.0 (2021-03-16)
3.0.0 (2021-03-02)
2.7.0 (2021-02-02)
Note: Version bump only for package gatsby-design-tokens
2.6.0 (2021-01-20)
2.5.0 (2021-01-06)
Note: Version bump only for package gatsby-design-tokens
2.4.0 (2020-12-15)
2.3.0 (2020-12-02)
Note: Version bump only for package gatsby-design-tokens
2.2.0 (2020-11-20)
Note: Version bump only for package gatsby-design-tokens
2.1.0 (2020-11-12)
Note: Version bump only for package gatsby-design-tokens
2.0.13 (2020-10-01)
Note: Version bump only for package gatsby-design-tokens
2.0.12 (2020-09-28)
Note: Version bump only for package gatsby-design-tokens
2.0.11 (2020-08-26)
Note: Version bump only for package gatsby-design-tokens
2.0.10 (2020-07-03)
2.0.9 (2020-06-29)
2.0.8 (2020-06-24)
Note: Version bump only for package gatsby-design-tokens
2.0.7 (2020-06-22)
2.0.6 (2020-05-20)
Note: Version bump only for package gatsby-design-tokens
2.0.5 (2020-04-18)
Note: Version bump only for package gatsby-design-tokens
2.0.4 (2020-03-23)
Note: Version bump only for package gatsby-design-tokens
2.0.3 (2020-03-16)
Note: Version bump only for package gatsby-design-tokens
2.0.2 (2020-02-20)
- gatsby-design-tokens:
fonts.sans
now delivers the "Inter" font stack, not thesystem
font stack anymore fix:fonts.sans
and.brand
aliases
2.0.1 (2020-02-11)
Note: Version bump only for package gatsby-design-tokens
- fix(gatsby-design-tokens): Fix
files
field inpackage.json
:dist
now includesindex.esm.js
and the twodist/theme
s; before it only offered the main CommonJS module (8c0d55c)
2.0.0 (2020-02-10)
This update moves the rudimentary tokens even closer to our current sole target, CSS. This e.g. means that instead of exporting an array of integers for fontSizes
or space
, we now provide rem
values instead (while still making the v1 variants available — but we do have "soft" preferences regarding default units for CSS, which are emphasized by these breaking changes).
We currently only consume these tokens in the context of CSS, so let's make things a bit easier there:
fontsSizes
exportsrem
values now; old values available atfontSizesRaw
space
exportsrem
values now, too; old stuff available atspaceRaw
fonts
exports a string now, ready to be used with thefont-family
CSS prop; old array of font family names available asfontsLists
radii
now contains thepx
unit
The update also embraces theme-ui
a bit more directly by partially adopting and/or inheriting its naming conventions for a bunch of tokens, making "theme composition using token groups" even easier than before.
Regarding the discussion in https://github.com/gatsby-inc/gatsby-interface/issues/181, everything but the space
scale has been adjusted to hopefully "just work", or work easier than before. The update to v2 of gatsby-design-tokens
should require almost no refactoring of values in gatsby-interface
—
- the
transition
properties partially follow a different naming convention fonts.header
changed tofonts.heading
radii
values now come with thepx
unit, so the latter is not needed anymore in template literals
— and apart from that should be solved by removing the transformation of fontSizes
and spaces
to
rem, and the
joinof
fonts` stacks.
Here's all changes listed by "token group":
- BREAKING CHANGE: Remove
breakpoints.xxs
- All tokens started as only being consumed via
styled-system
. In its context, and using an object to define breakpoints,breakpoints.xxs
made sense/was required. Since we switched totheme-ui
, it doesn't anymore.gatsby-interface
defines its own set ofbreakpoints
; thewww
source already adjusted this when composing itstheme-ui
theme, so this shouldn't hurt at all.
- All tokens started as only being consumed via
- feat: add export
breakpointsArray
, ready fortheme-ui
's responsive styles feature
- feat: add missing steps in
colors.blackFade
andcolors.whiteFade
:- add
colors.blackFade[90]
- add
colors.blackFade[40]
- add
colors.blackFade[20]
- add
colors.blackFade[5]
- add
colors.whiteFade[90]
- add
colors.whiteFade[40]
- add
colors.whiteFade[20]
- add
colors.whiteFade[5]
- add
- BREAKING CHANGE: fix
colors.blackFade[80]
,colors.whiteFade[80]
- both were set to an opacity of
.85
, adjusted to.8
- TODO: Adjust a couple of values for gatsbyjs.org; no clue about where we currently might use this in
gatsby-interface
and related (.com/Cloud dashboard).
- both were set to an opacity of
- feat: port
colors.code
from the gatsbyjs.orgtheme-ui
theme to thecolors
tokens- 💚 This improves compliance with WCAG 2.0 AA color contrasts.
- feat: add
colors.code.copyButton
- feat: add
colors.code.lineHighlightBackground
- feat: add
colors.code.scrollbarTrack
- feat: Add aliases
body
andsans
forfonts.system
- BREAKING CHANGE: rename
fonts.header
tofonts.heading
- Comply with
theme-ui
requirements: https://theme-ui.com/theme-spec#typography.
- Comply with
- feat: Add alias
brand
forfonts.heading
- BREAKING CHANGE:
fonts
exports a string now, ready to be used with thefont-family
CSS prop; the array of font family names is still available asfontsLists
- BREAKING CHANGE:
fontSizes
does now containrem
values; old scale (integers) still available asfontSizesRaw
- feat: add export
fontSizesPx
- BREAKING CHANGE: Name
fontWeights
— switch from array to object- Include the required theme-ui defaults
body
,heading
, andbold
(https://theme-ui.com/theme-spec#typography). body: 400
semiBold: 600
bold: 700
heading: 700
extraBold: 800
- Include the required theme-ui defaults
- feat: Add line heights
heading
(equivalent to the existingdense
) andbody
(equivalent to the existingdefault
) to satisfytheme-ui
's "Typography" theme requirements
- BREAKING CHANGE: Add
px
unit to radii scale values.
- BREAKING CHANGE: removed
- As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.org-centric
sizes
tokens totheme-gatsbyjs-org
for clarity, until a clear pattern emerges.
- As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.org-centric
- BREAKING CHANGE:
space
does now containrem
values; old scale (integers) still available asspaceRaw
- feat: add export
spacePx
- feat: Add
transition.default
shortcut - feat: Add
transition.curve.fastOutLinearIn
fromgatsby-interface
- feat: Add
transition.speed.faster
(50ms
), matchinggatsby-interface
'sblink
- feat: Add
transition.speed.slower
(1000ms
), matchinggatsby-interface
'ssnail
- BREAKING CHANGE: change
transition.speed.slow
from350ms
to500ms
, now matchinggatsby-interface
- BREAKING CHANGE: removed
- As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.org-centric
zIndices
tokens totheme-gatsbyjs-org
for clarity, until a clear pattern emerges.
- As discussed in https://github.com/gatsby-inc/gatsby-interface/issues/181, this moves the current gatsbyjs.org-centric
- feat: add base
theme-ui
Gatsby theme, gatsbyjs.orgtheme-ui
theme- Both themes don't tree-shake yet, so no
agadoo
yet in the correspondinggatsby-design-tokens/package.json
scripts. - Both export the
theme-ui
theme astheme
and also provide individual token group exports (because we require them inwww
for usage outside of thetheme-ui
context). - Example usage:
export { theme as default } from "gatsby-design-tokens/dist/theme-gatsbyjs-org"
inwww/src/gatsby-plugin-theme-ui/index
- Directly import individual token groups with
import { mediaQueries } from "gatsby-design-tokens/dist/theme-gatsbyjs-org"
.
- Both themes don't tree-shake yet, so no
1.0.10 (2019-10-14)
Note: Version bump only for package gatsby-design-tokens
1.0.9 (2019-10-04)
Note: Version bump only for package gatsby-design-tokens
1.0.8 (2019-09-26)
Note: Version bump only for package gatsby-design-tokens
1.0.7 (2019-09-26)
Note: Version bump only for package gatsby-design-tokens
1.0.6 (2019-09-20)
Note: Version bump only for package gatsby-design-tokens
1.0.5 (2019-09-18)
Note: Version bump only for package gatsby-design-tokens
1.0.4 (2019-09-09)
Note: Version bump only for package gatsby-design-tokens
1.0.3 (2019-09-01)
1.0.2 (2019-08-23)
Note: Version bump only for package gatsby-design-tokens
1.0.1 (2019-08-20)
Note: Version bump only for package gatsby-design-tokens
1.0.0 (2019-07-17)
Note: Version bump only for package gatsby-design-tokens
0.0.2 (2019-07-16)
Note: Version bump only for package gatsby-design-tokens