147: Surviving GitHub Issues, the Statamic 3 Launch Aftermath, Tailwind 1.8, and Headless UI

What It Covers

Adam Wathan and Jack McDade discuss managing GitHub issues for Statamic CMS after receiving critical feedback from users, explore naming strategies for Tailwind's new Headless UI component library, review Tailwind CSS 1.8 features including dark mode and font-variant-numeric utilities, and share approaches to balancing bug fixes with feature development.

Key Questions Answered

• •GitHub Issue Management Strategy: Statamic created a triage team with four volunteer community members who have labeling and PR review access. This helps prioritize the right 20 issues per week from 300 total issues, recognizing that fixing the correct bugs matters more than volume. The team releases three bug-fix updates weekly while managing perception that they focus on new features instead of stability.
• •CSS Variable Empty String Technique: Tailwind implements font-variant-numeric utilities using CSS custom properties where empty strings require specific syntax. The solution uses var(--tailwind-empty, /* */ /* */) with comments containing exclamation marks to prevent minifiers from stripping the space between comments. This workaround tricks minifiers into preserving the default value space until PostCSS 8 fixes the underlying bug.
• •Product Naming and Brand Architecture: Headless UI uses a separate domain (headlessui.dev) rather than subdomain to avoid confusion with Tailwind UI commercial product. The approach mirrors Panic and Rogue Amoeba's strategy of maintaining distinct product sites with consistent design elements. Footer cross-promotion and ecosystem pages connect products without persistent navigation bars that dilute individual product focus.
• •Tailwind 1.8 Feature Flag System: Building Tailwind 2.0 features inside version 1.8 using experimental flags eliminates maintaining separate code branches. Dark mode and other v2 features exist in production code but remain disabled by default. This approach reduces technical debt and allows early adopter testing while maintaining stable releases for mainstream users without complex merge conflicts.
• •Purge CSS HTML Element Preservation: Tailwind 1.8 automatically preserves all basic HTML element styles during purging, solving markdown integration problems. Previously, PurgeCSS removed rules like .prose h1 because it found the prose class but not h1 elements in source files. The system now tricks PurgeCSS into believing HTML elements always exist, requiring only class detection for rule preservation.
• •Community Feedback Response Framework: When receiving coordinated negative feedback, distinguish between perception problems and actual performance issues. Statamic releases 20-30 bug fixes weekly but users perceived focus on new features due to public roadmap visibility. Recording transparent video updates in Discord and creating contributor triage teams addresses both communication gaps and actual prioritization needs without defensive reactions.