Unlocking the frontend – a call for standardizing component APIs pt.2

#tldr Why Design Systems, and a more structured approach to frontend engineering in general, might be key to a more shared frontend ecosystem. And how this thought might hit an interesting inflection point rather sooner than later, with the advent of production-ready Web Components as a shared technical standard and foundation for interoperability.

So what are the missing pieces? And how could our latest release, and the accompanying schema tooling open sourced with it, play into this? And what would a blog post be today, without tying it into AI? Buckle in: this will be a long one!

kickstartDS is Open Source now. Let’s start to democratize Design Systems today

Finally, the wait is over … today we are very proud to announce the Open Source release of kickstartDS. It’s been roughly one year since we started to go to market as we published our website, and we are thrilled to share the kickstartDS core with everyone from the Design System community.

Unlocking the frontend – a call for standardizing component APIs pt.1

We’re still wasting massive amounts of valuable development cycles in the frontend world by working in silos, or by to at least some extent reinventing the wheel for every project. Results suffer in the process, impacting real world results for users and content creators alike.
How did we get here, and how could a way forward look like? How we’ve already come a long way, and why still (so far) even Jamstack hasn’t been the sole answer, either…