← 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/the-wordpress-tech-stack/index.md b/content/posts/2026/the-wordpress-tech-stack/index.md
    index d3826e3..1ccb6bd 100644
    --- a/content/posts/2026/the-wordpress-tech-stack/index.md
    +++ b/content/posts/2026/the-wordpress-tech-stack/index.md
    @@ -1,17 +1,16 @@
     ---
     title: "The WordPress tech stack"
    -slug: the-wordpress-tech-stack
     pubDate: 2026-04-05T20:04:48.000Z
     updatedDate: 2026-04-05T20:04:48.000Z
     draft: false
     excerpt: "Running an event brand on WordPress sounds like bringing a knife to a gunfight. Every other promoter is on Squarespace, Wix, or just an Instagram link tree. But WordPress plus … Read more"
     categories:
    -  - { name: Guides, slug: guides }
    +  - Guides
     tags:
    -  - { name: format-guide, slug: format-guide }
    -  - { name: marketing, slug: marketing }
    -  - { name: tech, slug: tech }
    -  - { name: tone-instructional, slug: tone-instructional }
    +  - format-guide
    +  - marketing
    +  - tech
    +  - tone-instructional
     featured:
       src: https://cdn.slist.net/posts/the-wordpress-tech-stack/cover.png
       alt: "Laptop showing WordPress dashboard in dark studio"
    
  2. Simon8bc867c

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

    diff --git a/content/posts/2026/the-wordpress-tech-stack/index.md b/content/posts/2026/the-wordpress-tech-stack/index.md
    index 6da0708..d3826e3 100644
    --- a/content/posts/2026/the-wordpress-tech-stack/index.md
    +++ b/content/posts/2026/the-wordpress-tech-stack/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_69d2a78b2b5432.60620863.png
    +  src: https://cdn.slist.net/posts/the-wordpress-tech-stack/cover.png
       alt: "Laptop showing WordPress dashboard in dark studio"
     legacy_wp_id: 16002
     ---
    
  3. Simon3c1387f

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

    diff --git a/content/posts/2026/the-wordpress-tech-stack/index.md b/content/posts/2026/the-wordpress-tech-stack/index.md
    index 891a70f..6da0708 100644
    --- a/content/posts/2026/the-wordpress-tech-stack/index.md
    +++ b/content/posts/2026/the-wordpress-tech-stack/index.md
    @@ -13,7 +13,7 @@ tags:
       - { name: tech, slug: tech }
       - { name: tone-instructional, slug: tone-instructional }
     featured:
    -  src: https://cdn.slist.net/ai_69d2a78b2b5432.60620863.png
    +  src: https://slist.net/wp-content/uploads/ai_69d2a78b2b5432.60620863.png
       alt: "Laptop showing WordPress dashboard in dark studio"
     legacy_wp_id: 16002
     ---
    
  4. Simon5add954

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

    diff --git a/content/posts/2026/the-wordpress-tech-stack/index.md b/content/posts/2026/the-wordpress-tech-stack/index.md
    index bbcf998..891a70f 100644
    --- a/content/posts/2026/the-wordpress-tech-stack/index.md
    +++ b/content/posts/2026/the-wordpress-tech-stack/index.md
    @@ -4,6 +4,17 @@ slug: the-wordpress-tech-stack
     pubDate: 2026-04-05T20:04:48.000Z
     updatedDate: 2026-04-05T20:04:48.000Z
     draft: false
    +excerpt: "Running an event brand on WordPress sounds like bringing a knife to a gunfight. Every other promoter is on Squarespace, Wix, or just an Instagram link tree. But WordPress plus … Read more"
    +categories:
    +  - { name: Guides, slug: guides }
    +tags:
    +  - { name: format-guide, slug: format-guide }
    +  - { name: marketing, slug: marketing }
    +  - { name: tech, slug: tech }
    +  - { name: tone-instructional, slug: tone-instructional }
    +featured:
    +  src: https://cdn.slist.net/ai_69d2a78b2b5432.60620863.png
    +  alt: "Laptop showing WordPress dashboard in dark studio"
     legacy_wp_id: 16002
     ---
     Running an event brand on WordPress sounds like bringing a knife to a gunfight. Every other promoter is on Squarespace, Wix, or just an Instagram link tree. But WordPress plus WooCommerce gives you something none of those platforms offer: complete ownership of your data, your customer relationships, and your marketing infrastructure.
    
  5. Simon30e0ee3

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

    diff --git a/content/posts/2026/the-wordpress-tech-stack/index.md b/content/posts/2026/the-wordpress-tech-stack/index.md
    new file mode 100644
    index 0000000..bbcf998
    --- /dev/null
    +++ b/content/posts/2026/the-wordpress-tech-stack/index.md
    @@ -0,0 +1,53 @@
    +---
    +title: "The WordPress tech stack"
    +slug: the-wordpress-tech-stack
    +pubDate: 2026-04-05T20:04:48.000Z
    +updatedDate: 2026-04-05T20:04:48.000Z
    +draft: false
    +legacy_wp_id: 16002
    +---
    +Running an event brand on WordPress sounds like bringing a knife to a gunfight. Every other promoter is on Squarespace, Wix, or just an Instagram link tree. But WordPress plus WooCommerce gives you something none of those platforms offer: complete ownership of your data, your customer relationships, and your marketing infrastructure.
    +
    +Here is the tech stack we built and why each piece matters.
    +
    +## Why WordPress over everything else
    +
    +The core advantage is data ownership. When you sell tickets through Posh, RA, or Dice, those platforms own the customer data. They control the email list. They decide what analytics you can see. They can change their terms, raise their fees, or shut down your account with no recourse.
    +
    +WordPress gives you the customer database directly. Everyone who buys a ticket or signs up for guest list becomes a user in your system. You own their email, their purchase history, their engagement data. With that data, you can buy Instagram ads served directly to those people and their lookalike friends. That capability alone justifies the infrastructure investment.
    +
    +## The ticketing stack
    +
    +We evaluated seven ticketing plugins over 20+ research sessions before settling on a stack. The requirements were specific: WooCommerce checkout for affiliate tracking compatibility, multiple ticket tiers per event, QR code scanning via mobile app, external ticket link support during the transition from Posh, and artist profile integration.
    +
    +The Events Calendar with Tickets Plus was the initial choice for its robust ecosystem and WooCommerce integration. It crashed the site due to a conflict with Greenshift’s full site editing. The lesson: always test plugin combinations in staging before production, especially when mixing page builders with event plugins.
    +

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

Sign in to SLIST

Pick how you want to enter.