Skip to content

Commit

Permalink
add draft posts (that i keep tripping over)
Browse files Browse the repository at this point in the history
  • Loading branch information
chantastic committed Aug 25, 2023
1 parent 96f64f1 commit 5ba57a2
Show file tree
Hide file tree
Showing 4 changed files with 95 additions and 0 deletions.
17 changes: 17 additions & 0 deletions chan.dev/src/content/posts/become-who-you-are.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: Become who you are
---

The day after Rock was born, Nellie and I went to a friends graduation party (without Rock).

The first of our friends to get married and have kids, we wanted to prove that we didn't have to change.

Thet belief has palgued every seasonof my life since. I've believed that I could acrete life's experiences without changing.

When Ruby was diagnosed with cancer, I didn't change.
When my dad died, I didn't change.
(planning center, podcast, etc.)

I've always wanted to be "the same guy."

But I'm not. I'm new every day.
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
---
title: Not every exception is a failure
---
45 changes: 45 additions & 0 deletions chan.dev/src/content/posts/stories-without-storybook.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
---
title: Build your own Storybook in Astro, using CSF
date: 2023-08-18
---

You don't need Storybook to write stories.

When I started at Chromatic, I was using Storybook everyday to build a component library.
Today, I mostly just build my website.

No shade on Storybook but I will never install Storybook to do [component driven development] here.
And even if I wanted to, there isn't an Astro integration.

But I reach for stories all the time.

What I want is stories, without the `book`.

## What we're going to build

Storybook is a full development environment.

This is how I think of stories, as a baseline.

1. CSF (Meta, named exports, object syntax, play functions)
1. pages
1. page fragments for linking
1. A formatted name from the named export name
1. interface information
1. a nested container inside

Bonus:

- A default template
- A sidebare

---

Questions:

- How to parse an astro component file and render that using CSF?
- How to test test components using testing-library (vitest?)
-

flowchart LR
id["This ❤ Unicode"]
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
title: The Visual Regression Testing Service I want
date: 2023-08-18
---

I want a visual regression testing service designed for indie developers, not enterprise.

In 2010, I started a career in what would eventually be called design systems.
I did so at a few companies. An e-commerce company, a whitelabel wellness services provider, and a church management software. All became teams large enough to have people dedicated to choosing their own tools and building their own environment.

All that time, I wanted a tool for visual regression testing UI. And in 2018, [Chromatic built it]().
Only problem is that I had to use Storybook.
Storybook is… fine. But it's a lot.

Of course, if you're privileged enough to build UI for an enterprises, chances are your component library it's own package and you don't mind using Storybook as your development environment. I didn't.

But I would never install it for a "normal project".

So for the past 2 years, I've been low-key fixated on what Storybook looks like… without Storybook.
And what the criteria are for a general purpose visual regression testing service would be.

## Component Story format
Component Story Format is the crown jewel of Storybook innovation.
I see it as the "stories" part of Storybook and what I want everything to work on.

CSF is more convention than anything else.

- `default` contains a bunch of metadata about the component you're writing stories for.
- every named export is a "story"
- and stories are written in object syntax

0 comments on commit 5ba57a2

Please sign in to comment.