SF Hackathon Stacks
Hackathon session: redesign card UI to visually differentiate between the new capsule types — image, doc, PDF, video — vs plain links. Improve scannability across stacks.
Card Type UI — The Problem
Stacklist supports multiple capsule types—Link, Image, Doc, PDF, and Video—but the current UI renders them identically, creating friction because users cannot distinguish content types at a glance. Solving this matters for setting expectations before interaction, making stacks feel richer, differentiating Stacklist from plain bookmarking tools, and visually reinforcing the capsule paradigm.
Card Type UI — Design Direction
Card type UI design direction outlines a system of type badges for cards—covering Link, Image, Doc, PDF, and Video—with specific icon and color pairings for each. Five visual treatment options are explored, with the recommended approach combining an icon and subtle color tint to enable quick differentiation without overwhelming card content.
Card Type UI — Work Division
Martina handles adding card type detection logic based on MIME type and content metadata, updating the card data model and API response across two hours. Kyle designs and builds the `<CardTypeBadge>` visual component with per-type color tokens, integrates it into the card UI across views, and both collaborate in a final hour for QA and shipping.
Card Type UI — Definition of Done
Card Type UI completion criteria require five visually distinct card types with badges/icons working across grid view, list view, mobile, and embedded stacks, while ensuring correct detection for new capsule types (image, doc, PDF, video) without affecting existing link cards or causing layout issues. Bonus goals include hover tooltips showing type names, filtering stacks by card type, and displaying the type in the card detail/sidebar view.
Hackathon — The Blind Build
A co-founder night hackathon format. You each build something secretly for the other person. No hints, no questions, headphones on. Reveal over dinner. 🙈
The Blind Build — Concept
The Blind Build is a hackathon format for two people who know each other well, where each secretly builds something for the other person without any communication, relying entirely on how well they understand each other's needs. Rules enforce zero peeking or questions during a 3-4 hour window, with the reveal at the end serving as both a gift exchange and a test of mutual knowledge.
The Blind Build — Schedule
The Blind Build hackdate follows a structured five-hour schedule where two people share an opening drink, then separate into silent solo building sessions with no communication for 3.5 hours, followed by a demo-day-style reveal of what they made. Each person builds something real with the other in mind, and both projects get shipped and logged after the presentations and a celebratory dinner.
The Blind Build — Ideas for Each Other
Martina and Kyle each propose four small tools they could build for the other—ranging from a PM metrics dashboard and Linear digest to a Claude Code UI and Substack draft helper—as part of a "Blind Build" exchange. A meta-rule suggests logging every project as a card in a Hackdate log stack, aiming for 24 shipped things and a narrative arc over 12 sessions.
The Hackdate Log
The Hackdate Log is a structured journal tracking paired build sessions between Martina and Kyle, using a standardized entry format that records the session format, what each person built and for whom, their reveal reactions, and whether both projects shipped. Hackdate #1 is planned but not yet completed, designated as "The Blind Build" format with all fields still pending.