Creating A Generic Design System
In the last ~10 years of creating, updating, and building Design Systems as a front-end developer I've worked my way through a few possible solutions.
From building a simple component library using PHP, making use of Fractal, to helping build a customised documentation site using Eleventy … I have some thoughts.
The idea of creating a generic Design System that I can take with me for client work has always been something I've wanted to do, ever since working with a client 11 years ago and their pre-built themes for Sitecore CMS.
So, this is a start.
I've an idea on how I want to structure things, what languages I want to use and not use with the hope that I can create something that is useable and adaptable.
Of course, in reality, am I relly building a Design System or am I simply building another component library? We will see. I know I won't be creating anything in a design tool. I'm a front-end developer, I'll play to my strengths.
I do have grandiose ideas of streaming whilst I work on it. That might not come to fruition but I have decided to try and blog my way through it.
Naturally I've got a name for it. Mosaic.
