Skip to content

Commit

Permalink
chore: improve FAQ page
Browse files Browse the repository at this point in the history
  • Loading branch information
sarahgm committed Dec 2, 2022
1 parent c32e686 commit d1dfc0e
Showing 1 changed file with 21 additions and 1 deletion.
22 changes: 21 additions & 1 deletion docs/src/pages/introduction/faq.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,28 @@ In Short:
> "[A design system is ] a set of multidisciplinary shared, integrated principles and patterns that define the overall design of the product"
> [Karri Saarinen ex-Design Systems Lead @ Airbnb](https://www.youtube.com/watch?v=TuLY1cYM57g)
And because markets and customer demands constantly change, a design system is not just an artifact of a design process. It is a living, funded product with a roadmap and backlog, serving an ecosystem.

## What are the benefits of a design system?

So what sets a design system apart from something like a pattern library is that it is build with clear rules, constraints and principles, implemented in design and code. Ideally, it will convey your business identity and philosophy as well as strengthen the relationship of users with your brand.

That said, one of the primary benefits of a design system is the ability to quickly replicate designs, while removing the burden of developers to adhere to design specifications. Your marketers, designers and developers can collaborate quickly to produce the experience your customers wants, while maintaining the consistency your brand needs.

And because markets and customer demands constantly change, a design system is not just an artifact of a design process. It is a living, funded product with a roadmap and backlog, serving an ecosystem.
## Who decide which component is implemented?

We work strongly together with the Reservix UX/UI Team. If the component is in more than in one product the designers will research its use cases, after that we all will discussing the behaviour, the look and feel.
Also we will looking up the technical possibilities - if it all fits the component will be implemented.
The same applies to the improvement of a component.

## Why should I use this Design System?

The goal of Marigold is to build an easy and compelling to use platform, regardless if you are a developer, designer or sales person.

The purpose of this Design System is to create a set of guidelines and components that are scalable and reusable, so that designers and developers can efficiently and comfortably develop Reservix products.

## Can I contribute?

If you work at Reservix and have a design related or technical question, you can head over to our dedicated [slack channel](https://reservix.slack.com/archives/C02727BNZ3J). We try to respond to everyone as quickly as we can and we're always happy to help.

If you have a bug report or feature request you can visit our [github](https://github.com/marigold-ui/marigold) and write an issue. We have templates for feature requests, bugs and component updates.

0 comments on commit d1dfc0e

Please sign in to comment.