87

GitHub - seek-oss/playroom: Design with code, powered by your own component libr...

 5 years ago
source link: https://github.com/seek-oss/playroom
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

README.md

Playroom

Simultaneously design across a variety of themes and screen sizes, powered by JSX and your own component library.

Playroom allows you to create a zero-install code-oriented design environment, built into a standalone bundle that can be deployed alongside your existing design system documentation.

  • Iterate on your designs in the final medium.
  • Create quick mock-ups and interactive prototypes with real code.
  • Exercise and evaluate the flexibility of your design system.
  • Share your work with others by simply copying the URL.

Setup

$ npm install --save-dev playroom

Add the following scripts to your package.json:

{
  "scripts": {
    "playroom:start": "playroom start",
    "playroom:build": "playroom build"
  }
}

Add a playroom.config.js file to the root of your project:

module.exports = {
  title: 'Playroom',
  outputPath: './dist/playroom',
  components: './src/components',
  themes: './src/themes',
  frameComponent: './playroom/FrameComponent.js',
  widths: [320, 375, 768, 1024],
  exampleCode: `
    <Button>
      Hello World!
    </Button>
  `,
  webpackConfig: () => ({
    // Custom webpack config goes here...
  })
};

Your components and themes files are expected to export a single object or a series of named exports. For example, your components file might look like this:

module.exports = {
  Text: require('./Text/Text'),
  Button: require('./Button/Button'),
  // etc...
};

When providing themes, your themes file might look something like this:

module.exports = {
  themeA: require('./themeA'),
  themeB: require('./themeB'),
  // etc...
};

If your components need to be nested within custom provider components, you can provide a custom React component file via the frameComponent option, which is a path to a file that might look something like this:

import React from 'react';
import ThemeProvider from '../path/to/your/ThemeProvider';

export default ({ theme, children }) => (
  <ThemeProvider theme={theme}>
    {children}
  </ThemeProvider>
);

If you're using a CSS-in-JS library that generates styles dynamically, you might need to configure it to insert them into the iframe. For example, when using styled-components:

import React from 'react';
import { StyleSheetManager } from 'styled-components';
import ThemeProvider from '../path/to/ThemeProvider';

export default ({ theme, children, frameWindow }) => (
  <StyleSheetManager target={frameWindow.document.head}>
    <ThemeProvider theme={theme}>
      {children}
    </ThemeProvider>
  </StyleSheetManager>
);

Now that your project is configured, you can start a local development server:

$ npm run playroom:start

To build your assets for production:

$ npm run playroom:build

License

MIT.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK