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

Home

Jump to bottom
Tõnis Tobre edited this page May 8, 2024 · 32 revisions

TEDI (TEHIK Design System) is open source design system used in TEHIK. Its goal is to provide toolkit and building blocks for TEHIK partners, designers, developers, product owners etc. It follows VEERA guidelines. It provides specific components for designers, implements React components for developers. As a result, provided solution saves development time.

TEDI contains two sets of components: community and TEDI (we call them TEDI-READY). Community set is driven by community and resolves special use-cases and TEDI set gives stability and quality therefore implements more basic components.

Usage

npm i @tehik-ee/tedi-design-system

Migration from old Disainipesa component library to TEDI

  1. Remove old dependency from package.json: @tehik/react-components
  2. Install TEDI component library npm i @tehik-ee/tedi-design-system
  3. Find and replace from all files in project: "from '@tehik/react-components'" and replace "from '@tehik-ee/tedi-design-system/community'" (from is important to replace only import statements)
  4. In addition you need to change style location as well: "import '@tehik/react-components/index.css'" and replace "import '@tehik-ee/tedi-design-system/index.css'"
  5. Repeat the steps for every NPM project.

To get into more detail, please see here: https://github.com/TEHIK-EE/tedi-design-system/wiki/Migration-from-Disainipesa

References

Development

Contributor

  1. Fork github repo
  2. Make changes and create pull request against origin rc branch
  3. If you have contributed to TEDI components, you have to setup github pages to your account to provide test environment URL 3.1. How: TBD
  4. For community components, pull request will be reviewd by maintainer and will be merged to rc branch. And feature is ready to use with pre-release version

Maintainer

  1. Create new branch
  2. Make changes and create pull request against rc branch
  3. Pull request will be reviewd by other maintainer and will be merged. And feature is ready to use with pre-release version

Branches and versioning

Gitflow is described here in detail: Gitflow

Clone this wiki locally