James Edmonds

The components package could probably benefit from a `useVariant` hook. ```ts import { useVariant, Button, PropsWithVariant } from 'theme-ui' type AwesomeButtonProps = { somethingAwesome?: string } export const AwesomeButton =...

Waiting on https://github.com/netlify/edge-bundler/pull/109 to be merged, and I think some upstream changes to `@netlify/build`. But this would mean we can support Netlify edge functions, with very little effort.

Well, that PR has been merged, waiting on `@netlify/build` now, and this should be all thats needed, and some testing obviously...

I'll get the ball rolling with an initial benchmark for transform!

I guess it would be like our e2e tests, as we would like to test the whole stack?

Linting should surely be picking all this up. Not sure about the return types though, as they're probably inferred by default. Maybe something we need to configure in the lint...

linter PR #119

I personally think we should follow all the above. Would like to know how others feel about it @mashaal @dburles

> What about -- as a start -- to just minify the static CSS before it is deployed to prod. Use something like https://github.com/postcss/postcss-deno with a minification utility. Yeah this...

I'd like to see 'examples' instead of one big 'workspace' much like NextJS and others