With roughly 150 people on 13 teams in time zones around the world contributing to the design and development of our HighBond product platform, the need for consistency, documented patterns, and a vision for our future has become increasingly important. The Starling Design System is an integral part of accomplishing that and is one of the tools that helps us move as one at Galvanize.
Our design system is a living thing—always evolving and adapting to the ever-changing needs of our users and our product platform. Fellow Galvanites can get in touch on Slack in the #starling-system channel for latest news and updates on all things Starling.
Well, starlings are incredible little birds. They come together in flocks of hundreds or thousands and appear to move as one in a synchronized air ballet; a natural phenomenon known as a murmuration. Many individuals coming together to move as one. Seems like a pretty apt metaphor for a design system, eh?
Practical rules for our most common UX and UI patterns
Guidelines are the high-level principles that help inform every design decision we make at Galvanize.
The foundations of the Starling Design System
Every system needs a foundation built from the basics — typography, color, iconography, and layout.
Our tools for building consistent and efficient interfaces
A toolbox is useless without it's tools. Components are the tools needed for building consistent products.
We have a style guide to ensure that the content used in our in-product messaging is concise, used consistently, and assumes a pattern that is immediately recognizable to users - enabling a seamless UX experience as users travel between the different modules.
Refer to the Design Guidelines, Visual Style, Components, and Writing Style Guide before and during the design process to steer you in the right direction. The Quickstart & Tools section will help you get started with using the UI Kit as well as information on contributing to the design system.
Visual Style and Components sections will provide those implementing designs with the tools and resources they need to be successful. Please also refer to the Quickstart & Tools section to get started with local dev setup as well as information on contributing to the design system.
The Visual Style and Components sections will provide guidance on how we should be implementing the various pieces of our Design System. Please reference them while reviewing Jira stories and Github pull requests.
Well written UI copy and other content is critical to a successful user experience. The Writing Style Guide is the reference to ensure consistency across the platform, while the Visual Style and Components sections will provide contextually relevant information when documenting product functionality.