DESOSA 2022

Storybook

Storybook

Storybook is a development environment for UI components. Storybook eases front-end development by allowing fast prototyping through a quick and interactive process of developing front-end components and testing in isolation. It allows you to browse a component library, view the different states of each component, and interactively develop and test components.

Storybook can be used in combination normal HTML but also with other popular web building frameworks such as React, Vue and Angular. It has even been extended to support React Native, Android, iOS, and Flutter development for mobile. Storybook has an active developer community with at the time of writing over 100 open pull requests and almost 8000 closed pull requests.

Find out more at https://storybook.js.org.

Authors

Frank Bredius

MSc Student Computer Science following Information Architecture Track.

Luca Cras

MSc Student Computer Science, with a special interest in AI, Machine Learning and Data Science.

Jan-Mark Dannenberg

Double Master Student Data Science & Management of Technology.

Pepijn Klop

MSc Student Computer Science, with a special interest in AI and Software Architecture.

Storybook - Scalability

Scalability for Storybook In this post, we will discuss the notion of scalability concerning the StoryBook project. As scalability is an aspect where software architecture plays a particularly important role, this had to be analyzed in our series of posts about the project. Scalability challenges Fortunately for the Storybook project, most known scalability challenges do not apply to it. Examples of these challenges are database scaling and insufficient caching 1. Storybook is used locally on the machine of the developer, where each developer has his own copy of Storybook as a node module dependency.

Storybook - Quality and Evolution

Storybook is the addition to your web front-end project, which allows you to easily build reusable UI components. In the previous essays12, we have already discussed some of the key qualities of Storybook that makes it the convenient, unmissable, and easy to use tool it is today. We will re-visit some of the key qualities and see to what extent they are currently satisfied by the system. Qualities & processes First of all, the main key quality of Storybook is of course reusability.

Storybook - Architecture

In our second essay about Storybook, we will focus on the way Storybook works under the hood, and how the large software project is structured to ensure maintainability, testing, and performance. We will take a look at some overarching motifs, and then we will keep zooming in onto the different views (Container, Component, etc.) that are specified in the C4 model1. Finally, we will look at how this all relates to Storybook achieving their key quality attributes as outlined in our first essay2.

Storybook - Product Vision

If you are anything like us, you will have come across the urge to be able to focus on developing your UI components by building and testing them in an isolated environment. This is exactly what Storybook1 allows us to do! In this essay, we will describe what Storybook aims to do and the vision that they have laid out. In addition, we will present a short product analysis of Storybook.

Contributions