Skip to main content

4 posts tagged with "Storybook"

Posts to do with configuring or using Storybook

View All Tags

Another Catch-Up Post

· 8 min read
Iain Davis
Iain Davis
Software Engineer, Principal @ IainDavis.dev
TL;DR

There have been a lot of uncommunicated changes in my codebases.

  • I've split off a separate component library called [Docodylus][github-docodylus]
  • I've built a custom internationalization layer for Docodylus on top of Polyglot
  • refactored it into a monorepo (a couple times, actually), and am now preparing to release it into the wild as an open-source project on NPM (just as soon as get the quality-check-and-release pipeline in place)

It's been a long while. I haven't been posting, and virtually nothing has changed here at IainDavis.dev. But I haven't been idle either. Since I last was regularly updating, I made several decisions that have taken a good long while to carry out, and I abandoned some structure and communication while I was doing it. In retrospect, it was maybe unwise, but at the time it felt like quite enough to be dealing with all the things I was dealing with and also be doing the learning I needed to do to implement the changes I wanted.

Challenges Getting Docusaurus Styles Into Storybook

· 3 min read

I thought it would be a good idea to have a central location to showcase whatever components I add to the Docusaurus repertoire.

I'd worked with Storybook before, and found it pretty handy. During development, it gives you a way to interact with a component-in-progress and see that it works as intended. It can serve as a beginning basis for unit and component tests, and it can be a really handy tool for communicating with non-technical stakeholders... clicking on a component and seeing immediately how it responds is much easier to grasp than an engineer trying to explain something to you in non-engineer-speak as best they can. The proof is in the pudding, as they say.