Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

topcoder-archive/topcoder-platform-topcoder-react-ui-kit

Folders and files

NameName
Last commit message
Last commit date
Aug 18, 2020
Sep 14, 2020
Jun 26, 2018
Sep 6, 2018
Sep 13, 2020
Jan 30, 2018
Feb 2, 2018
Jan 30, 2018
Sep 6, 2018
Jun 26, 2018
Apr 4, 2018
Feb 1, 2018
Sep 6, 2018
Sep 6, 2018
Jun 26, 2018
Aug 5, 2019
Sep 15, 2020
Apr 4, 2018

Repository files navigation

Dev Build Status Master Build Status Latest NPM Release NPM Downloads

Topcoder React UI Kit

The Topcoder UI Kit for internal ReactJS projects.

Installation

Install the package via NPM:

$ npm install --save topcoder-react-ui-kit

Import its global stylesheet into the root ReactJS component of your app:

import 'topcoder-react-ui-kit/dist/style.css';

NOTE: This will automatically import all global styles from topcoder-react-utils — no need do include those separately!

Global Styles

The import of topcoder-react-ui-kit/dist/style.css stylesheet provides you with (assuming that your Webpack config properly parses that stylesheet, and bundles all assets referenced from there into your bundle):

Style Mixins

To use any of the style mixins in your SCSS code you should import them as

@import "~topcoder-react-ui-kit/src/styles/mixins";

NOTE: It will automatically include all SCSS mixins from topcoder-react-utils — no need to include those separately!

Themed Components

Note that most of these components are inherited from their topcoder-react-utils counterparts, and topcoder-react-ui-kit just takes care about their proper theming according to the TC UI Kit design specs.

  • Avatar — Themed avatar;
  • Buttons — Themed buttons;
  • ErrorMessage — Standard error message;
  • Modal — Standard modal component;
  • Tags — Small tags for technologies, event types, etc. Technically, they are buttons styled in a different way.

Development

To develop inside a host package just $ npm link it.

CI/CD with CircleCI 2.0 is set up. Commits to the protected master branch will do testing and release to NPM (be sure to properly bump the version with $ npm version TYPE, where TYPE is one of major/minor/patch; and keep in mind that patch updates should never break backward compatibility; if your minor or major updates includes breaking changes, don't forget to document those in the CHANGELOG).

To be written in a better way

License

UNLICENSED — for internal Topcoder projects only.