feat(web): Wave 4 — prose layouts + /policies on Tailwind typography
diff --git a/content/posts/2026/set-time-strategy-how-to-program-a-12-hour-event/index.md b/content/posts/2026/set-time-strategy-how-to-program-a-12-hour-event/index.md new file mode 100644 index 0000000..b804d8b --- /dev/null +++ b/content/posts/2026/set-time-strategy-how-to-program-a-12-hour-event/index.md @@ -0,0 +1,67 @@ +--- +title: "Set time strategy: how to program a 12-hour event" +pubDate: 2026-04-05T20:04:45.000Z +updatedDate: 2026-04-05T20:04:45.000Z +draft: false +excerpt: "Programming a 12-hour event is not the same as programming a 4-hour club night stretched out. The energy arc, the BPM progression, the bar revenue implications, and the DJ scheduling … Read more" +categories: + - Guides +tags: + - curation + - format-guide + - music + - tone-instructional +featured: + src: https://cdn.slist.net/posts/set-time-strategy-how-to-program-a-12-hour-event/cover.png + alt: "DJ equipment with dramatic lighting suggesting long-format event programming" +legacy_wp_id: 16070 +--- +Programming a 12-hour event is not the same as programming a 4-hour club night stretched out. The energy arc, the BPM progression, the bar revenue implications, and the DJ scheduling all operate on different principles. We have run events from 9pm to 9am and learned the hard way what works. + +## The BPM-to-revenue connection + +This is the single most important insight for long-format programming: slower beats mean more drinks sold. The correlation has been confirmed across our events and validated by DJs who have been in the scene for decades. Hard techno and hardcore are ticket-driven, not bar-driven. Venues reject hardcore specifically because it kills drink sales. +Diff truncated (74 lines total). View full commit on GitHub →
