feat(web): flatten frontmatter — drop slug, flat tags/cats, auto-bump updatedDate [skip ci]
diff --git a/content/posts/2026/ticketing-platform-showdown/index.md b/content/posts/2026/ticketing-platform-showdown/index.md index 8f9f4ab..4e81f34 100644 --- a/content/posts/2026/ticketing-platform-showdown/index.md +++ b/content/posts/2026/ticketing-platform-showdown/index.md @@ -1,17 +1,16 @@ --- title: "Ticketing platform showdown" -slug: ticketing-platform-showdown pubDate: 2026-04-05T20:04:48.000Z updatedDate: 2026-04-05T20:04:48.000Z draft: false excerpt: "We have used four ticketing platforms across 37+ events. Each one taught us something about conversion rates, data ownership, audience trust, and the hidden costs that eat into margins. Here … Read more" categories: - - { name: Guides, slug: guides } + - Guides tags: - - { name: financial, slug: financial } - - { name: format-case-study, slug: format-case-study } - - { name: tech, slug: tech } - - { name: tone-instructional, slug: tone-instructional } + - financial + - format-case-study + - tech + - tone-instructional featured: src: https://cdn.slist.net/posts/ticketing-platform-showdown/cover.png alt: "Multiple event tickets scattered for comparison"content: rewrite image URLs from slist.net/wp-content to cdn.slist.net/posts/<slug>/
diff --git a/content/posts/2026/ticketing-platform-showdown/index.md b/content/posts/2026/ticketing-platform-showdown/index.md index f309029..8f9f4ab 100644 --- a/content/posts/2026/ticketing-platform-showdown/index.md +++ b/content/posts/2026/ticketing-platform-showdown/index.md @@ -13,7 +13,7 @@ tags: - { name: tech, slug: tech } - { name: tone-instructional, slug: tone-instructional } featured: - src: https://slist.net/wp-content/uploads/ai_69d2a7a34cebe1.03929102.png + src: https://cdn.slist.net/posts/ticketing-platform-showdown/cover.png alt: "Multiple event tickets scattered for comparison" legacy_wp_id: 16005 ---fix(web): point upload URLs at slist.net (cdn.slist.net not wired up yet)
diff --git a/content/posts/2026/ticketing-platform-showdown/index.md b/content/posts/2026/ticketing-platform-showdown/index.md index 024d751..f309029 100644 --- a/content/posts/2026/ticketing-platform-showdown/index.md +++ b/content/posts/2026/ticketing-platform-showdown/index.md @@ -13,7 +13,7 @@ tags: - { name: tech, slug: tech } - { name: tone-instructional, slug: tone-instructional } featured: - src: https://cdn.slist.net/ai_69d2a7a34cebe1.03929102.png + src: https://slist.net/wp-content/uploads/ai_69d2a7a34cebe1.03929102.png alt: "Multiple event tickets scattered for comparison" legacy_wp_id: 16005 ---feat(web): visually mirror slist.net blog (index + single post)
diff --git a/content/posts/2026/ticketing-platform-showdown/index.md b/content/posts/2026/ticketing-platform-showdown/index.md index 0420126..024d751 100644 --- a/content/posts/2026/ticketing-platform-showdown/index.md +++ b/content/posts/2026/ticketing-platform-showdown/index.md @@ -4,6 +4,17 @@ slug: ticketing-platform-showdown pubDate: 2026-04-05T20:04:48.000Z updatedDate: 2026-04-05T20:04:48.000Z draft: false +excerpt: "We have used four ticketing platforms across 37+ events. Each one taught us something about conversion rates, data ownership, audience trust, and the hidden costs that eat into margins. Here … Read more" +categories: + - { name: Guides, slug: guides } +tags: + - { name: financial, slug: financial } + - { name: format-case-study, slug: format-case-study } + - { name: tech, slug: tech } + - { name: tone-instructional, slug: tone-instructional } +featured: + src: https://cdn.slist.net/ai_69d2a7a34cebe1.03929102.png + alt: "Multiple event tickets scattered for comparison" legacy_wp_id: 16005 --- We have used four ticketing platforms across 37+ events. Each one taught us something about conversion rates, data ownership, audience trust, and the hidden costs that eat into margins. Here is the honest breakdown of every platform we tested and why we ultimately decided to build our own.feat(web): full posts+pages sync, browseable UI, curated pages allowlist
diff --git a/content/posts/2026/ticketing-platform-showdown/index.md b/content/posts/2026/ticketing-platform-showdown/index.md new file mode 100644 index 0000000..0420126 --- /dev/null +++ b/content/posts/2026/ticketing-platform-showdown/index.md @@ -0,0 +1,53 @@ +--- +title: "Ticketing platform showdown" +slug: ticketing-platform-showdown +pubDate: 2026-04-05T20:04:48.000Z +updatedDate: 2026-04-05T20:04:48.000Z +draft: false +legacy_wp_id: 16005 +--- +We have used four ticketing platforms across 37+ events. Each one taught us something about conversion rates, data ownership, audience trust, and the hidden costs that eat into margins. Here is the honest breakdown of every platform we tested and why we ultimately decided to build our own. + +## Resident Advisor + +RA was our first platform. It has the best built-in audience for electronic music — people actively browsing RA for events in their city represent a warm audience you do not have to create from scratch. Our Silo debut sold 122 tickets through RA for $749.70 in revenue. + +The problems: the app had bugs that frustrated buyers, the platform controls the customer data, and the fees take a meaningful cut. When a buyer purchases through RA, that customer belongs to RA’s ecosystem, not yours. You cannot retarget them with your own ads. You cannot add them to your SMS list. You are renting access to your own audience. + +## Dice + +Dice was used for specific events, including our Silo debut where 33 Dice tickets brought in $495. The platform has a clean buyer experience and strong brand recognition. Some venues require Dice or RA specifically in their contracts. + +The same data ownership problem applies. You are building someone else’s customer base. And Dice’s discovery algorithm favors larger promoters, making it harder for underground events to surface organically on the platform. + +## Shotgun +Diff truncated (60 lines total). View full commit on GitHub →
