As a front-end developer, I found that very difficult to create a UI that considers various variables, inconsistent styles. Sometimes, unexpectable component design made exhausts me.

With this experience in the background, I created localize-component. The advantage of localize-component is that you can make new style UI by overriding localize props. But, All colors come from theme context. So localize UI is changed by key and value of theme.

If you use this, can customize and experience UI extensively by chaning theme you want.

• A theme based styling.
• Overriding localize props styling.

• TypeScript
• Babel 7
• Lerna
• RollupJS
• React
• EmotionJS
• Storybook

• @seolhun/localize-components-docs

• @seolhun/localize-components
• @seolhun/localize-components-atomic
• @seolhun/localize-components-icon
• @seolhun/localize-components-grid
• @seolhun/localize-components-table

• @seolhun/localize-components-hooks
• @seolhun/localize-components-utils

• @seolhun/localize-components-styled-types

# NPM
$ npm install --save @seolhun/localize-components @seolhun/localize-components-atomic

# Yarn
$ yarn add @seolhun/localize-components @seolhun/localize-components-atomic

import { LocalizeAlert } from '@seolhun/localize-components';
import { LocalizeButton } from '@seolhun/localize-components-atomic';
import { LocalizeInput } from '@seolhun/localize-components-forms';
import { LocalizeIcon } from '@seolhun/localize-components-icon';
import { LocalizeTable } from '@seolhun/localize-components-table';
import { LocalizeRow, LocalizeCol } from '@seolhun/localize-components-grid';

• Docs - Storybook : localize-components-docs.surge.sh

• Docs - Storybook : dev.localize-components-docs.surge.sh