I started my first piece of the Q4 roadmap yesterday. It might not look like much yet, but I am very excited about the following screenshot:
Why am I excited? Three reasons:
- That is not a screenshot of the app, but of Storybook, which I use for rapid testing & scaffolding. I've experimented with building atomic components and even some modals in Storybook, but this is the first time I am creating an entire screen within it. It is glorious. Iteration time is much, much faster — and it means that there's a clean separation between the component itself and all of the state management & router management wiring that ties it to the broader app.
- This is all, to butcher a term that is in vogue, design-systemic. Nothing in this screenshot is an ad-hoc component: it is implementing against a new
<list-view />component, which itself contains a<filter-widget />and a<data-table />(both of which are already live throughout the app, albeit in a slightly different style) and so on. The goal here is consistency: I want to get to a point this year where I have one main way to create a list of items, and to next quarter have one main way to create a detail page for an item, and so on. None of this is novel, but Buttondown's finally at the stage where it makes sense to invest here. Plus, it's just fun to program. - Right before starting to write this, I stumbled upon a reasonable way of showing the various multiplicities of what subset of folks an email has been sent out to. There's 'public' and 'premium', sure, as you can see above — but also "public to folks tagged
foo" and "was premium-only then moved to free as a lead magnet", that sort of thing. It's that pill paradigm with the unsightly green — and, like I led off with, it doesn't look like much, but I'm excited at being able to collapse a fairly complex state space into a terse, readable badge.