← Back to post

Revision history

  1. Simon7b403ef

    feat(web): flatten frontmatter — drop slug, flat tags/cats, auto-bump updatedDate [skip ci]

    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
    index 50d7cd2..b804d8b 100644
    --- 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
    @@ -1,17 +1,16 @@
     ---
     title: "Set time strategy: how to program a 12-hour event"
    -slug: 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:
    -  - { name: Guides, slug: guides }
    +  - Guides
     tags:
    -  - { name: curation, slug: curation }
    -  - { name: format-guide, slug: format-guide }
    -  - { name: music, slug: music }
    -  - { name: tone-instructional, slug: tone-instructional }
    +  - 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"
    
  2. Simon8bc867c

    content: rewrite image URLs from slist.net/wp-content to cdn.slist.net/posts/<slug>/

    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
    index d83fcbc..50d7cd2 100644
    --- 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
    @@ -13,7 +13,7 @@ tags:
       - { name: music, slug: music }
       - { name: tone-instructional, slug: tone-instructional }
     featured:
    -  src: https://slist.net/wp-content/uploads/ai_69d2a49e2c4985.96308248.png
    +  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
     ---
    
  3. Simon3c1387f

    fix(web): point upload URLs at slist.net (cdn.slist.net not wired up yet)

    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
    index e73ec63..d83fcbc 100644
    --- 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
    @@ -13,7 +13,7 @@ tags:
       - { name: music, slug: music }
       - { name: tone-instructional, slug: tone-instructional }
     featured:
    -  src: https://cdn.slist.net/ai_69d2a49e2c4985.96308248.png
    +  src: https://slist.net/wp-content/uploads/ai_69d2a49e2c4985.96308248.png
       alt: "DJ equipment with dramatic lighting suggesting long-format event programming"
     legacy_wp_id: 16070
     ---
    
  4. Simon5add954

    feat(web): visually mirror slist.net blog (index + single post)

    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
    index db27db3..e73ec63 100644
    --- 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
    @@ -4,6 +4,17 @@ slug: 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:
    +  - { name: Guides, slug: guides }
    +tags:
    +  - { name: curation, slug: curation }
    +  - { name: format-guide, slug: format-guide }
    +  - { name: music, slug: music }
    +  - { name: tone-instructional, slug: tone-instructional }
    +featured:
    +  src: https://cdn.slist.net/ai_69d2a49e2c4985.96308248.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.
    
  5. Simon30e0ee3

    feat(web): full posts+pages sync, browseable UI, curated pages allowlist

    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..db27db3
    --- /dev/null
    +++ b/content/posts/2026/set-time-strategy-how-to-program-a-12-hour-event/index.md
    @@ -0,0 +1,57 @@
    +---
    +title: "Set time strategy: how to program a 12-hour event"
    +slug: 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
    +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.
    +
    +The practical application: start slower when bar sales matter most. Open the night at 130-140 BPM when the crowd is arriving, buying drinks, and settling in. Peak later at 150-160+ BPM when ticket revenue has already been captured and the energy needs to carry the room through until morning.
    +
    +If your deal with the venue involves a bar minimum, this BPM progression is not optional. It is the difference between clearing a $4,000 bar minimum and falling short. At $25-32 per customer in bar spend, you need roughly 125-160 guests drinking meaningfully. Slower BPMs in the early hours give them reason to stay at the bar instead of the dancefloor.
    +
    +## The three-phase structure
    +
    +A 12-hour event divides naturally into three phases, and each phase serves a different function.
    +
    +Phase one runs from doors opening until roughly midnight. This is the warm-up. Ambient, minimal, deep grooves. The music should not demand the dancefloor — it should reward the people who arrived early with atmosphere. Newcomers and open-deck DJs belong here. The bar does its best business in this window. Book your most melodic DJs for this slot.
    +

    Diff truncated (64 lines total). View full commit on GitHub →

Sign in to SLIST

Pick how you want to enter.