Skip to content
Telescope

AboutWarning: Draft

Sharing is not always caring. It's a delicate balance, but complexities added to the foundation of our system can become difficult to change once users get accustomed to them.

To ensure that Telescope remains useful, design elements in our system should be:

Frequently used

Design elements in Telescope should be used across multiple products and features. Frequently used entails a higher need for consistency, ease of use, and overall quality of implementation.

Context agnostic

We only adopt design elements that can be used in multiple situations. This makes our system more flexible and adaptable to changing needs across different products and features.

Uniquely purposed

We want to avoid new design elements that solve the same problems as existing ones. By avoiding duplication, resources can be focused on developing and improving existing element, resulting in a streamlined and optimised system.

Opinionated

We embed design decisions into our design elements. We aim to guide usage rather than leaving this up to the user. By doing so, our design elements help ensure consistency and clarity in our products by providing a clear visual language that users can rely on.

Common

We favour design elements and patterns that are common across design systems. This allow us to take advantage of the collective knowledge and expertise of the design systems community, while also providing our users with familiar and intuitive user interfaces.

This page is a draft. Its content is likely to change.