feat(web): flatten frontmatter — drop slug, flat tags/cats, auto-bump updatedDate [skip ci]
diff --git a/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md index 9f9d3ac..827ae7e 100644 --- a/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md +++ b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md @@ -1,18 +1,17 @@ --- title: "The WhatsApp architecture behind the brand" -slug: the-whatsapp-architecture-behind-the-brand pubDate: 2026-04-05T20:04:49.000Z updatedDate: 2026-04-05T20:04:49.000Z draft: false excerpt: "Before SMS lists, before email CRM, before any ticketing platform, the entire SLIST operation ran on WhatsApp. The community architecture was designed from the ground up to convert casual followers … Read more" categories: - - { name: BTS, slug: bts } + - BTS tags: - - { name: community, slug: community } - - { name: format-case-study, slug: format-case-study } - - { name: tech, slug: tech } - - { name: tone-instructional, slug: tone-instructional } - - { name: whatsapp, slug: whatsapp } + - community + - format-case-study + - tech + - tone-instructional + - whatsapp featured: src: https://cdn.slist.net/posts/the-whatsapp-architecture-behind-the-brand/cover.png alt: "Abstract dark tiered chat architecture visualization in red and black"content: rewrite image URLs from slist.net/wp-content to cdn.slist.net/posts/<slug>/
diff --git a/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md index a56d34d..9f9d3ac 100644 --- a/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md +++ b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md @@ -14,7 +14,7 @@ tags: - { name: tone-instructional, slug: tone-instructional } - { name: whatsapp, slug: whatsapp } featured: - src: https://slist.net/wp-content/uploads/ai_69d2a79a228da8.81591576.png + src: https://cdn.slist.net/posts/the-whatsapp-architecture-behind-the-brand/cover.png alt: "Abstract dark tiered chat architecture visualization in red and black" legacy_wp_id: 16011 ---fix(web): point upload URLs at slist.net (cdn.slist.net not wired up yet)
diff --git a/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md index 460d652..a56d34d 100644 --- a/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md +++ b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md @@ -14,7 +14,7 @@ tags: - { name: tone-instructional, slug: tone-instructional } - { name: whatsapp, slug: whatsapp } featured: - src: https://cdn.slist.net/ai_69d2a79a228da8.81591576.png + src: https://slist.net/wp-content/uploads/ai_69d2a79a228da8.81591576.png alt: "Abstract dark tiered chat architecture visualization in red and black" legacy_wp_id: 16011 ---feat(web): visually mirror slist.net blog (index + single post)
diff --git a/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md index bb8416c..460d652 100644 --- a/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md +++ b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md @@ -4,6 +4,18 @@ slug: the-whatsapp-architecture-behind-the-brand pubDate: 2026-04-05T20:04:49.000Z updatedDate: 2026-04-05T20:04:49.000Z draft: false +excerpt: "Before SMS lists, before email CRM, before any ticketing platform, the entire SLIST operation ran on WhatsApp. The community architecture was designed from the ground up to convert casual followers … Read more" +categories: + - { name: BTS, slug: bts } +tags: + - { name: community, slug: community } + - { name: format-case-study, slug: format-case-study } + - { name: tech, slug: tech } + - { name: tone-instructional, slug: tone-instructional } + - { name: whatsapp, slug: whatsapp } +featured: + src: https://cdn.slist.net/ai_69d2a79a228da8.81591576.png + alt: "Abstract dark tiered chat architecture visualization in red and black" legacy_wp_id: 16011 --- Before SMS lists, before email CRM, before any ticketing platform, the entire SLIST operation ran on WhatsApp. The community architecture was designed from the ground up to convert casual followers into committed attendees, and it worked well enough to build the foundation for everything that came after.feat(web): full posts+pages sync, browseable UI, curated pages allowlist
diff --git a/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md new file mode 100644 index 0000000..bb8416c --- /dev/null +++ b/content/posts/2026/the-whatsapp-architecture-behind-the-brand/index.md @@ -0,0 +1,35 @@ +--- +title: "The WhatsApp architecture behind the brand" +slug: the-whatsapp-architecture-behind-the-brand +pubDate: 2026-04-05T20:04:49.000Z +updatedDate: 2026-04-05T20:04:49.000Z +draft: false +legacy_wp_id: 16011 +--- +Before SMS lists, before email CRM, before any ticketing platform, the entire SLIST operation ran on WhatsApp. The community architecture was designed from the ground up to convert casual followers into committed attendees, and it worked well enough to build the foundation for everything that came after. + +## The tiered distribution system + +The WhatsApp community in Mexico City was deliberately tiered to create scarcity and social proof. The inner circle was a roughly 100-person group with first access to guest lists and discount codes. The second tier was an 800-person engaged community chat that received announcements after the inner circle. The third tier was an 1,800-person broadcast-only announcement group. Instagram stories came last, the lowest priority channel for information that had already cascaded through three layers of increasingly exclusive access. + +Each tier earned access through engagement, not just following. There was a certain investigation before guest list access reached completely random people. The tiers functioned like concentric circles of trust, each one filtering for a higher level of commitment. + +## Topic-based splitting + +At 500 members, the main chat got too noisy to be useful. The solution was topic-based subgroups: psy techno, disco house, genre-specific channels that kept engagement high and prevented the main chat from becoming a feed of unrelated content. Ban first and ask questions later was the moderation philosophy. No porn, no spam, mute and remove rule-breakers including promoters who broke community guidelines. + +The splitting strategy preserved the intimacy of a small group chat while scaling to thousands. Each subgroup maintained its own culture and energy. The main announcement channel became a funnel, not a conversation. + +## The cortesia exchange +Diff truncated (42 lines total). View full commit on GitHub →
