PJ Onori’s blog

Big detailsI’m making a spec for design system documentationTesting agents on design systemsDon’t talk like themDesign system contributions work better when everyone knows your nameDesign systems are today’s cure and tomorrow’s cause of shitty softwareThe many layers of dependencies in design systemsFame, fortune, and podcastingPublic design systems are worth itDesign system ambassadors–the goldilocks of collaborationWhat I learned from making a (second) mobile appWriting about making a writing appPlanning and design systems–how much time you got?Buyer bewareDesign system documentation is essential–as long as it’s goodMaybe this is design technologists’ time to shineNaming things in design systems–and why it’s the worstI don’t want your emailThe existential challenge of design system team moraleOwn what’s yoursCraft and tools and jigsConsistency means nothingWhat I learned from making my own design systemAI doesn’t have to be horribleEverybody readsDesign systems and the never-ending job of buy-inColor is a four letter wordWrite like you designI’m making a mobile appAn over-analytical analysis of styleScrew it, I’m making a typefaceSystems, math and explosions (in no particular order)Simple things make things simpleMeasuring design system “adoption”Tend your gardenThe English language—A guideline for how not to make a design systemAn opinionated guide to designing a photography siteMaking a design system is a people jobWriting is designEverything is a prototypeDesign for speedIn defense of hard