Frequently Asked Questions
Have some questions? You may find it here.
Generic
A “Design System” is a collection of reusable components and tools, guided by clear standards, that can be assembled together to build digital products and experiences. Design systems solve the easy problems, so that products can solve hard problems more easily.
The goal of a design system is to improve user interface consistency and quality, while making software design and development processes more efficient. A design system also helps to establish a common vocabulary between everyone in the organization and ease collaboration between different teams and disciplines. See our goals for more.
Public documentation makes sharing and collaboration between different teams and third party vendors much easier as it increases the system’s visibility and accountability. This also makes us push towards higher quality content and enables us to be more transparent. Finally, this also serves as an amazing tool that we can leverage in recruiting.
See our Roadmap page for up to date plans.
Kesko Design System is built and supported by a core team of designers and developers who work at Kesko. The team is currently being lead by Ariel Salminen.
Usage
See the Quick start section in the documentation.
First of all, please note that it is still early days and we haven’t published any modules for usage just yet. Nevertheless, the short answer to the question is yes, you should use it as soon as possible. Kesko Design System improves UI consistency and quality, while making our software design and development processes more efficient.
Our contribution model will allow product teams to add new features based on their product requirements. At the same time, it will allow us to keep an eye on the quality and consistency of the user experience.
Draft status badges indicate that the feature is in active development and not yet ready for production use. APIs documented may change without notice.
Stable status badges indicate that the feature is ready to be used in production. The releases will follow semantic versioning to convey meaning about the underlying features and what has been modified from one version to the next.
Pre-release status badges indicate that the feature is ready for testing in development environments.
Kesko Design System is meant for building digital products and experiences for Kesko Oyj. Our terms of use don’t allow usage outside of this context.
No, but feel free to browse our documentation to learn how we approach design and development at Kesko.
Technical
Kesko Design System is tested in the latest two versions of Chrome, Safari, Edge, Firefox and Opera. Our team addresses critical bug fixes in earlier versions based on their severity and impact. If you need to support IE11 or pre-Chromium Edge, this library isn’t for you.
Our team is committed to providing tools that are accessible by all people, regardless of their abilities or technology used. We’re also continuously working towards improving the accessibility of Kesko Design System to ensure this. See the dedicated accessibility section and A11Y checklist for more details.
Yes. All selectors and similar are prefixed with k- to prevent collisions.
Kesko’s component library ships React components for React and Next.js applications. Every component is also available as a Progressive Web Component, or as plain HTML styled with our CSS framework compatible with any framework, or no framework at all.
We follow “Semantic Versioning.” Under this scheme, version numbers and the way they change convey meaning about the underlying features and what has been modified from one version to the next. For more details, please see the documentation.