---
# System prepended metadata

title: Orbit update

---

# Orbit update
First, happy new year, and best wishes from the Orbit team! It's been a while since we communicated about the state of the Design System. So let's give you a heads-up about what we have been cooking for the past few months. 


## Changes in Orbit 1
### Example components
Some of you noticed it already; we unpublished the section examples from our documentation (randstad.design). All the example components are still available, but Orbit's ambitions are to become more agnostic and focus on our core components. So, together with the RXP UX team, we decided that design decisions and support would fall under their jurisdiction. 

Of course, the core components remain under the Orbit team for support and updates.

Nevertheless, we are still committed to supporting the development and updates of the example components based on the UX team input and, of course, the feedback we receive from RXP stakeholders and OpCo's.

### Deprecation
As you may already know, we have been working for quite some time on Orbit 2 (more on this below). Therefore we would like to inform you that we will slowly start deprecating Orbit 1 in favor of the new version. We don't have an end date yet. But we expect that 2023 will be the year where we transition from our old (and beloved) Orbit 1 to our new (and amazing) Orbit 2.

## What about Orbit 2?
### The 2022 summary
Looking back to the past year, we hit a few bumps along the road: roadmap shifting at the beginning of Q3, Monster decoupling end of Q4. But they say that what doesn't kill you makes you stronger. And here we are. 

### A new architecture
Currently we are working on transitioning the architecture, that was previously hosted on the Monster side, fully to Randstad. This means not only the code base needs to be moved, but also all the CI/CD pipelines needs to be optimized and rewritten. We see this as an opportunity to tailor it completely to our needs, and at the end Orbit 2.0 will be easier to consume and faster deployed. As we have demonstrated in our previous presentations Orbit 2.0 heavily relies on automation. Figma will be our source of truth and the driver for the styling of our components. Development and Design will work closely together and finally, we'll deliver a multi-brand design system fully fledged in React.

### Collaboration model
We want to offer our users a better and easier way to collaborate and participate in building the design system. Therefore, we are working hard to prepare an open collaboration model that allows designers and developers to participate seamlessly.

## Team composition
As from mid-january, the team will be composed by 2 developers, 3 designers, 1 solution architect and 1 product owner. 

## Release of email templates
We also release a set of tool-agnostic