146: Launching Statamic 3, GitHub Sponsors, Tailwind CSS v1.7, and Preparing for Laracon

What It Covers

Adam Wathan and Jack McDade discuss launching Statamic 3, implementing GitHub Sponsors with sponsorware models, releasing Tailwind CSS v1.7 with gradient utilities, and preparing a Laracon talk about building component libraries with responsive design patterns.

Key Questions Answered

• •GitHub Sponsorware Strategy: Statamic implements tiered sponsorship at $5-$100 monthly, offering free starter kits at threshold levels while keeping premium versions behind sponsorship. This model aligns value with donations without blocking essential features, generating $500-600 monthly to fund designers and developers for open source work.
• •Component Composition Architecture: Build components with minimal responsibility using multiple divs rather than flattening markup. Keep spacing, sizing, and borders in parent containers, not baked into components themselves. This enables reusability across contexts—components should be width 100% by default, letting parent containers control dimensions and spacing.
• •Tailwind v1.7 Gradient System: New gradient utilities use CSS variables for composition, allowing BG-gradient-to-r from-orange-500 to-pink-500 syntax. This approach generates fewer classes than combinatorial alternatives and automatically handles Safari's transparent gradient bug by calculating proper RGBA values, avoiding gray fade issues.
• •Responsive Component Props Pattern: Experimental layout prop system passes screen-size-to-layout mappings as objects (default: stacked, SM: horizontal, XL: stacked), enabling components to adapt without hardcoded breakpoints. Combined with Purge CSS integration using variable syntax, this creates container-query-like behavior without JavaScript polyfills or performance issues.
• •Feature Flag Development Workflow: Implement future and experimental config keys to develop next-major-version features inside current releases. Future flags enable stable breaking changes users can opt into; experimental flags allow unstable features without semantic versioning concerns. This eliminates separate alpha branches while letting users test upcoming functionality.