> Markdown version of [/events/world-congress-2024/sessions/81-5-tips-to-know](https://www.wearedevelopers.com/events/world-congress-2024/sessions/81-5-tips-to-know). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# 5 tips to know before building a design system


- **Date:** Thursday, Jul 18, 2024
- **Time:** 11:45–11:55 (10 min)
- **Room:** Airstream (120)
- **Event:** World Congress 2024

## Description

As a main developer or occasional contributor to several design systems, open source or internal, I've made some mistakes in the way. Let's help frontend developers planning to start a design system or contribute to it not to fall into the same errors.
Building your own design system sounds like a great idea, but keeping it alive, maintained & useful is a challenge. 

Main content points:
1: Do we really need a design system?
2: Audit your codebase
3: Make product agnostic components
4: Document, plug & play
5: Adoption


## Speaker

### [Dani Coll](https://www.wearedevelopers.com/@dani-coll)

Senior Frontend Engineer at Dynatrace


## Related talks at this congress

- [Write once, use anywhere: Framework agnostic Design Systems with Web Components](https://www.wearedevelopers.com/events/world-congress-2024/sessions/354-write-once-use) — Sascha Lehmann
- [Why is technical design a crucial aspect of development?](https://www.wearedevelopers.com/events/world-congress-2024/sessions/95-why-is-technical) — Angelika Shvets
- [Atomic Design - Frontend's Clean Architecture](https://www.wearedevelopers.com/events/world-congress-2024/sessions/279-atomic-design) — ritamcastro
- [Bridging the gap between design and development](https://www.wearedevelopers.com/events/world-congress-2024/sessions/452-bridging-the-gap) — Jade Jiang, Noga Mann