system-ui/system-ui.com

Standards for creating consistent, interoperable user interfaces

System UI

Standards for creating consistent, interoperable user interfaces

https://system-ui.com

system-ui.com's Issues

Logo on website is broken

Suggestion for reducing redundancy and arriving toward pure JSON

Consider the following example:

colors: {
  blue: '#07c',
  blues: [
    '#004170',
    '#006fbe',
    '#2d8fd5',
    '#5aa7de',
  ]
}

One then has to then assign color names:

theme.colors.blues.regalBlue = theme.colors.blues[0]

But because object literals in JSON and JavaScript are already ordered, one could perhaps use instead:

colors: {
  blue: '#07c',
  blues: {
    regalBlue: '#004170',
    lochmara: '#006fbe',
    curiousBlue: '#2d8fd5',
    havelockBlue: '#5aa7de',
  }
}

Something like styled-system could then transform blues to be available as an array, e.g. blues[0] or blues.0. Keys in JavaScript are already ordered.

It'd be perhaps nice if theme objects could be in JSON? Then we could use a JSON schema to validate theme objects.

Broken link to Rebass

Hey!

Cool project! However, while reading through I found that the link to Rebass was broken here. If you're open to contributions, I'll open a PR.

Add an example implementation

Hey @jxnblk,

Really liking what I've been reading in the spec so far, as well as following the conversation over in system-ui/theme-specification#1.

I was wondering if you could add an example of the specification, as you imagine it, to the site?

I think it would be helpful for readers to see the specification in action, and being able to see the implementation would make it simpler for people to follow along.

Would also be great to see the example specification being used in a couple of framework examples too.

Perhaps having the spec pulled into some Emotion/Styled Components/Glamour/etc example projects would help solidify the real world applications.

Website down

The system-ui.com website seems to be incorrectly configured or down: