content(community): migrate sunset Meetup links to luma.com/pulumi

[dirien]

Summary

Pulumi has sunset its Meetup presence; the community's new home is luma.com/pulumi. This PR retargets every link to a Pulumi-owned Meetup property (the pro/pugs hub, all city PUG groups, pulumi-seattle) — 43 link instances across 13 files.

Changes

• Blog (6 posts, 35 links): join-pulumi-user-group-community (24 links, plus a migration announcement info box at the top and an updated: 2026-07-25 stamp), pulumi-year-in-review (5), platform-engineering-devops-event-meetup-community (2), pulumi-meetup-recap-apis-custom-resources-and-github-webhooks (2), platform-engineering-cncf-maturity-model (1), ai-predictions-2026-devops-guide (1)
• Site surfaces: /pugs/ redirect page now redirects to Luma; the "Pulumi User Groups" button on /community/ (layouts/community/section.html) links to Luma
• Events: retargeted url_slug click-throughs for the three Pulumi-hosted external event cards (PUG Seattle, PUG Tel Aviv, Dagger codefest)
• Team page: the two talk entries on engin-diri.md that pointed at Pulumi PUG event pages
• README: the "Join a Local PUG" bullet

Deliberately not changed: 10 links to third-party meetup.com groups (9 external talk venues on the team page, plus the Cloud Native London group) — those communities still live on Meetup.

Testing

• make lint passes (markdown lint + Prettier clean)
• Verified with make serve: all touched pages return 200; the join post renders the info box and 26 Luma links; /pugs/ redirects to luma.com/pulumi; /community/ button points at Luma; third-party talk links untouched

[pulumi-bot]

Your site preview for commit 749f784 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-20521-749f7841.s3-website.us-west-2.amazonaws.com

Changed pages:

• /blog/ai-predictions-2026-devops-guide/
• /blog/join-pulumi-user-group-community/
• /blog/platform-engineering-cncf-maturity-model/
• /blog/platform-engineering-devops-event-meetup-community/
• /blog/pulumi-meetup-recap-apis-custom-resources-and-github-webhooks/
• /blog/pulumi-year-in-review/
• /community/team/engin-diri/
• /events/build-dagger-module-pulumi-chainguard/
• /events/pug-meetup-seattle/
• /events/pug-meetup-tel-aviv/
• /pugs/

[pulumi-bot]

Lighthouse Performance Report

Commit: 749f784 | Metric definitions

Page	Device	Score	FCP	LCP	TBT	CLS	SI
Homepage	Mobile	🔴 42	3.1s	4.7s	1963ms	0.072	7.6s
Homepage	Desktop	🟡 85	0.8s	1.0s	284ms	0.017	1.4s
Install Pulumi	Mobile	🟡 59	6.1s	10.1s	107ms	0.053	6.1s
Install Pulumi	Desktop	🟡 85	1.4s	2.0s	0ms	0.015	1.6s
AWS Get Started	Mobile	🟡 59	6.0s	10.0s	56ms	0.071	6.0s
AWS Get Started	Desktop	🟡 85	1.3s	2.0s	0ms	0.019	1.6s

[github-actions]

Pre-merge Review — Last updated 2026-07-26T14:48:14Z

Tip

Summary: This is a maintenance PR that migrates the community's sunset Meetup.com links to the new Luma calendar (https://luma.com/pulumi) across a README bullet, six blog posts, a team bio's talk entries, three event bundles, the /pugs redirect, and one community-page button — plus a new announcement banner atop the "Join a PUG" post explaining the move. The changes are mechanical URL/text swaps, so the main reader-facing risk is prose that now reads oddly against its new link target: one sentence still says the groups were created "on Meetup" while linking to Luma (flagged below), and the new banner's "38 groups / 14 countries / nearly 10,000 members" figures don't line up with the same post's older "23 … in 10 countries" heading and 22-group list (they describe different scopes, so no hard error). Most other links now point every specific meetup/event reference at the single general Luma calendar, which is an intentional trade-off of sunsetting Meetup — historical posts lose their event-specific destinations, and that generic page can't be scraped to re-confirm a specific past event, which is why many claims land as unverifiable rather than wrong. Passes run: link/URL verification, frontmatter sweep, editorial-balance, and a temporal-trigger sweep; Hugo build was skipped (content-only, no templating changes).

Review confidence:

Dimension	Level	Notes
mechanics	HIGH	Pure URL/text swaps plus one template href; frontmatter parses with no alias/URL collisions; build skipped as content-only.
facts	MEDIUM	Key facts (destination resolves; 38 groups/14 countries; PulumiUP & workshop numbers) check out; the "unverifiable" items are historical/event-specific references that now point at the general Luma calendar, inherent to sunsetting Meetup — not signs of error.
coherence	MEDIUM	One sentence reads "created … on Meetup" while linking to Luma; the new banner's counts don't reconcile with the post's older heading/list (different scopes).
editorial balance	HIGH	The one section-depth outlier is the intentionally long user-group link list; no steering concerns.

Investigation log

• Cross-sibling reads: not run (not in a templated section)
• External claim verification: 33 of 54 claims verified (15 unverifiable, 1 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 16 Pass 1, 24 Pass 2 (verified 11, contradicted 1, unverifiable 12), 14 Pass 3 (verified 11, contradicted 0, unverifiable 3).
• Cited-claim spot-checks: 24 of 24 cited claims fetched and compared
• Frontmatter sweep: ran on body + meta_desc + social.{linkedin, twitter}
• Temporal-trigger sweep: ran (recency words present in diff; spot-check in-review)
• Code execution: not run (no static/programs/ change)
• Code-examples checks: not run (no fenced code blocks in content files)
• Editorial-balance pass: ran (12 H2 sections, 0 flags fired)

🚨 Outstanding	⚠️ Low-confidence	💡 Pre-existing	✅ Resolved
1	13	0	0

🔍 Verification trail

55 claims extracted · 33 verified · 15 unverifiable · 1 contradicted

• L306 in README.md "* Join a Local Pulumi User Groups (PUGs) - Attend tech-packed meetups and hands-on virtual or in-person workshops." → 🤷 unverifiable (evidence: Web search confirms Pulumi hosts community events on Luma (e.g., a Pulumi-affiliated "Seattle AI in Production Series" event page at luma.com), consistent with PUGs using Luma as an events platform, but I could not directly fetch or confir…; source: WebSearch ran query "luma.com/pulumi"; top results showed a Pulumi-related event on Luma but not the pulumi calendar page itself; intuition: Pulumi's own blog post on PUGs references Meetup.com as the platform, not Luma, so this URL may reflect a newer/differe…)
• L151 in content/blog/ai-predictions-2026-devops-guide/index.md "Qodo builds agentic development tools that let users trust output without necessarily reviewing every line of code." → ✅ verified (evidence: The blog post itself states: "Qodo is doing fascinating work in this space with their agentic development tools, building systems that let you trust the output without necessarily reviewing every line." The claim is…; source: repo:content/blog/ai-predictions-2026-devops-guide/index.md)
• L151 in content/blog/ai-predictions-2026-devops-guide/index.md "The author demonstrated at the Tel Aviv Pulumi User Group meetup how Pulumi Neo's autonomous decision-making capabilities can handle infrastructure tasks that…" → 🤷 unverifiable (evidence: The cited URL (https://luma.com/pulumi) returns a generic events calendar listing page with no content mentioning Tel Aviv Pulumi User Group meetup, Pulumi Neo, or any specific demonstration; the truncated body shows only page styling/menu…; source: https://luma.com/pulumi)
• L153 in content/blog/ai-predictions-2026-devops-guide/index.md "Pulumi Neo creates pull requests with clear documentation of changes." → ✅ verified (evidence: Multiple Pulumi sources confirm Neo delivers work as pull requests with visible plans: "Pulumi Neo can now run any task on a cadence you set, opening a pull request for each run" (neo-automations), and Neo "creates a task plan outlining th…; source: pulumi/docs:content/blog/neo-automations/index.md; content/blog/ai-predictions-2026-devops-guide/index.md L91)
• L153 in content/blog/ai-predictions-2026-devops-guide/index.md "Pulumi Neo provides the transparency needed to ship infrastructure changes with confidence." → 🤝 matches (evidence: The same blog post already describes Neo's transparency in detail: "When you give Neo a complex request, it creates a task plan outlining the steps it will take to accomplish your goal. This plan provides transparency into Neo's approach a…; source: repo:content/blog/ai-predictions-2026-devops-guide/index.md (line 91))
• L4 in content/blog/join-pulumi-user-group-community/index.md "updated: 2026-07-25" → ➖ not-a-claim (evidence: This is a frontmatter 'updated' metadata timestamp for the blog post, not a falsifiable factual assertion that can be externally verified.; source: content/blog/join-pulumi-user-group-community/index.md)
• L4 in content/blog/join-pulumi-user-group-community/index.md "This blog post about joining a Pulumi User Group was updated on 2026-07-25." → ✅ verified (evidence: Frontmatter of content/blog/join-pulumi-user-group-community/index.md contains updated: 2026-07-25, matching the claim exactly.; source: repo:content/blog/join-pulumi-user-group-community/index.md)
• L5 in content/blog/join-pulumi-user-group-community/index.md "The PUGs feature in-person meetups, in-person and virtual workshops, and other events to help members stay up-to-date with the latest developments (stated iden…" (also L29) → ✅ verified (evidence: The file's own meta_desc reads "The PUGs will feature in-person meetups, in-person and virtual workshops, and other events to help members stay up-to-date with the latest developments" and the body states "The PUGs will also feature regula…; source: repo:content/blog/join-pulumi-user-group-community/index.md)
• L5 in content/blog/join-pulumi-user-group-community/index.md "PUGs feature in-person meetups, in-person and virtual workshops, and other events to help members stay up-to-date with the latest developments." → ✅ verified (evidence: The document's own meta_desc and body text state: "The PUGs will also feature regular in-person meetups, webinars, in-person and virtual workshops, and other events to help members stay up-to-date with the latest cloud infrastructure and P…; source: repo:content/blog/join-pulumi-user-group-community/index.md)
• L18 in content/blog/join-pulumi-user-group-community/index.md "The Pulumi Community is moving from Meetup to a new home on Luma (luma.com/pulumi)." → ✅ verified (evidence: The cited URL https://luma.com/pulumi returns HTTP 200 and resolves to "Pulumi · Events Calendar", confirming Pulumi has an active presence on Luma as claimed, though the page content itself doesn't explicitly state the migration from Meet…; source: https://luma.com/pulumi)
• L20 in content/blog/join-pulumi-user-group-community/index.md "The Pulumi Community has built 38 Pulumi User Groups across 14 countries." → ✅ verified (evidence: Meetup's official Pulumi User Group hub page states "14 Countries · 38 Groups · 8,451 Members", matching the claim's "38 Pulumi User Groups across 14 countries."; source: https://www.meetup.com/pro/pugs/)
• L22 in content/blog/join-pulumi-user-group-community/index.md "All upcoming Pulumi User Group events and workshops will be published on Luma going forward." → ➖ not-a-claim (evidence: The blog post itself states: "We want to make it as easy as possible for you to show up. All upcoming events and workshops will be published on Luma going forward." This is the author's own announcement about their own community program's…; source: repo:content/blog/join-pulumi-user-group-community/index.md)
• L24 in content/blog/join-pulumi-user-group-community/index.md "Follow us at luma.com/pulumi so you don't miss out." → ✅ verified (evidence: The cited URL https://luma.com/pulumi returns HTTP 200 and resolves to a "Pulumi · Events Calendar" page on Luma, consistent with the claim that users can follow Pulumi there.; source: https://luma.com/pulumi)
• L27 in content/blog/join-pulumi-user-group-community/index.md "Pulumi created the Pulumi User Groups (PUGs) on Meetup." → ❌ contradicted (framing: shifted — claim says "on Meetup" but the cited source (luma.com/pulumi) is Luma, a different platform than Meetup; evidence: The claim asserts PUGs are on "Meetup," but the cited source is luma.com/pulumi (Luma events calendar), not Meetup. The fetched page shows Pulumi's events are hosted on Luma, contradicting the claim's platform reference — this is a target/…; source: https://luma.com/pulumi)
• L29 in content/blog/join-pulumi-user-group-community/index.md "Members of PUGs have access to a global network of experts who can offer help, advice, and support on using Pulumi effectively." → ➖ not-a-claim (evidence: This is a general marketing/descriptive statement about the value of Pulumi User Groups (a community networking benefit), not a falsifiable technical or product claim that can be verified against a source.; source: content/blog/join-pulumi-user-group-community/index.md)
• L31 in content/blog/join-pulumi-user-group-community/index.md "The count of Pulumi User Groups listed on the page (12 US + 1 South America + 5 European + 1 Middle East + 1 Asia + 2 Oceania = 22 groups across 6 regions) is…" (also L37-73) → 🤷 unverifiable (evidence: The pre-fetched luma.com/pulumi page returned only a generic calendar shell with no list of user groups or countries, so it cannot confirm or refute the internal count discrepancy (12 US + 1 SA + 5 EU + 1 ME + 1 Asia + 2 Oceania = 22 vs. c…; source: https://luma.com/pulumi; intuition: The claim is a self-consistency arithmetic check against the article's own list (22 vs 23 groups, 6 vs 10 regions/count…)
• L31 in content/blog/join-pulumi-user-group-community/index.md "There are 23 Pulumi User Groups (PUGs) Meetups in 10 countries." → 🤷 unverifiable (evidence: Pulumi's own 2024 Year in Review blog states "With 20 groups across 9 countries" as of end of 2024, while the current Meetup Pro page for Pulumi User Group shows "more than 8451 members across 38 Meetups worldwide" — neither matches the cl…; source: https://www.pulumi.com/blog/pulumi-year-in-review/; https://www.meetup.com/pro/pugs/; intuition: Figure sits between two verified data points (20/9 in Dec 2024, 38 total currently) — plausible as a point-in-time coun… (WebSearch dispatched but verification did not converge within the turn budget))
• L33 in content/blog/join-pulumi-user-group-community/index.md "PUGs are led by Pulumi employees and Puluminaries, who are community members with expertise in cloud infrastructure, Pulumi Cloud, and cloud-native software de…" → ✅ verified (evidence: The source file states verbatim: "PUGs are led by Pulumi employees and Puluminaries, who are passionate community members that are experts in topics related to cloud infrastructure, Pulumi Cloud, cloud-native so…; source: repo:content/blog/join-pulumi-user-group-community/index.md)
• L52 in content/blog/join-pulumi-user-group-community/index.md "There is a São Paulo Pulumi User Group, listed under South America Pulumi User Groups." → 🤷 unverifiable (evidence: The pre-fetched body for https://luma.com/pulumi is just page chrome/CSS (menu wrapper styles) with no visible list of user groups, so the São Paulo / South America listing claim cannot be confirmed from the fetched content.; source: https://luma.com/pulumi)
• L56-60 in content/blog/join-pulumi-user-group-community/index.md "There are 5 named European Pulumi User Groups: London, Oslo, Berlin, Munich, and Prague." → 🤷 unverifiable (evidence: The pre-fetched body of https://luma.com/pulumi is just page scaffolding/CSS metadata with no event or group listing content, so the specific claim of "5 named European Pulumi User Groups: London, Oslo, Berlin, Munich, and Prague" cannot b…; source: https://luma.com/pulumi)
• L64 in content/blog/join-pulumi-user-group-community/index.md "There is a Tel Aviv Pulumi User Group, listed under Middle East Pulumi User Groups." → 🤷 unverifiable (evidence: The pre-fetched luma.com/pulumi page body is truncated/obfuscated CSS/JS content with no visible list of user groups or mention of Tel Aviv, so the claim cannot be confirmed or denied from this source.; source: https://luma.com/pulumi)
• L68 in content/blog/join-pulumi-user-group-community/index.md "There is a Singapore Pulumi User Group, listed under Asia Pulumi User Groups." → 🤷 unverifiable (evidence: The pre-fetched page body is only rendered CSS/JS boilerplate from the luma.com/pulumi calendar page (a JS-rendered SPA); no textual content listing Singapore or Asia Pulumi User Groups is present in the fetched body to confirm or deny the…; source: https://luma.com/pulumi)
• L72-73 in content/blog/join-pulumi-user-group-community/index.md "There are Australia and Auckland Pulumi User Groups, listed under Oceania Pulumi User Groups." → 🤷 unverifiable (evidence: The pre-fetched body for https://luma.com/pulumi is truncated to page styling/menu metadata and does not contain any list of Pulumi User Groups or region names like Oceania, Australia, or Auckland, so the claim cannot be confirmed from thi…; source: https://luma.com/pulumi)
• L77 in content/blog/join-pulumi-user-group-community/index.md "The first in-person PUG meetup was well-attended by developers, cloud architects, and other infrastructure enthusiasts." → ➖ not-a-claim (evidence: The blog post itself states: "The event was well-attended by developers, cloud architects, and other infrastructure enthusiasts." This is the author's own first-party narrative description of their own past event (Pulumi's own PUG meetup r…; source: repo:content/blog/join-pulumi-user-group-community/index.md L77)
• L79 in content/blog/join-pulumi-user-group-community/index.md "Joe Duffy spoke at the first in-person PUG meetup about Infrastructure as Code that writes itself, following the release of Pulumi Insights, which happened the…" → ➖ not-a-claim (evidence: Line 79 itself reads: "During the meetup, attendees heard from several speakers, including Joe Duffy... who was there to speak about Infrastructure as Code that writes itself after the release of Pulumi Insights... which happened that same…; source: repo:content/blog/join-pulumi-user-group-community/index.md)
• L83 in content/blog/join-pulumi-user-group-community/index.md "Liam Hampton is Sr. Regional Cloud Advocate at Microsoft." → ✅ verified (evidence: Microsoft's own DevOps blog author page states: "Sr. Regional Cloud Advocate, Microsoft Cloud Advocacy · Liam is a Senior Regional Cloud Advocate at Microsoft and an Auth0 Ambassador, passionate about DevOps, automation and Go."; source: https://devblogs.microsoft.com/devops/author/lhampton/)
• L83 in content/blog/join-pulumi-user-group-community/index.md "Sam Cogan is Director of Solution Architecture at Willis Towers Watson." → ✅ verified (evidence: The Pulumi blog post itself states: "Sam Cogan, Director of Solution Architecture at Willis Towers Watson, who spoke about building a library of reusable modules you can repeatedly reuse in your IaC projects."; source: https://www.pulumi.com/blog/join-pulumi-user-group-community/)
• L83 in content/blog/join-pulumi-user-group-community/index.md "Sam Cogan spoke about building a library of reusable modules you can repeatedly reuse in your IaC projects at the first PUG meetup in London." → ✅ verified (evidence: The blog post itself states: "Sam Cogan, Director of Solution Architecture at Willis Towers Watson, who spoke about building a library of reusable modules you can repeatedly reuse in your IaC projects" at "the first PUG meetup" in London,…; source: repo:content/blog/join-pulumi-user-group-community/index.md)
• L87 in content/blog/join-pulumi-user-group-community/index.md "The first PUG meetup was a huge success, with attendees leaving inspired and energized about Pulumi's tools and community possibilities." → ✅ verified (evidence: The published blog post states: "Overall, the first PUG meetup was a huge success, and attendees left feeling inspired and energized about Pulumi's tools and the community's possibilities."; source: https://www.pulumi.com/blog/join-pulumi-user-group-community/)
• L93 in content/blog/join-pulumi-user-group-community/index.md "There is a Pulumi Slack community accessible at slack.pulumi.com." → 🤷 unverifiable (evidence: The claim's source_hint (https://luma.com/pulumi) is a Luma events calendar page, not related to the Slack community claim at slack.pulumi.com. The pre-fetched body only shows generic Luma calendar page content and does not mention Slack a…; source: https://luma.com/pulumi)
• L62 in content/blog/platform-engineering-cncf-maturity-model/index.md "The Pulumi User Groups (PUGs) meetup listings can be found at https://luma.com/pulumi." → ✅ verified (evidence: The URL https://luma.com/pulumi returns HTTP 200 and displays "Pulumi · Events Calendar", consistent with it being the Pulumi User Groups meetup listings page.; source: https://luma.com/pulumi)
• L74 in content/blog/platform-engineering-devops-event-meetup-community/index.md "Dominik Kress will present a talk titled 'What the Heck is the CNCF Platform Working Group? Answers from a Member!' and details/RSVP for this event are availab…" (also L77) → 🤷 unverifiable (evidence: The pre-fetched page returns HTTP 200 and is the Pulumi events calendar on Luma, but the truncated body content (mostly CSS/menu markup) does not surface the specific talk title or speaker name to confirm the claim's details.; source: https://luma.com/pulumi)
• L79 in content/blog/platform-engineering-devops-event-meetup-community/index.md "RSVP for the Boston meetup launch event on July 24 is required due to limited capacity, and RSVP can be completed at https://luma.com/pulumi." (also L83) → 🤷 unverifiable (evidence: The cited URL returns HTTP 200 and loads Pulumi's Luma events calendar page, but the pre-fetched body is a truncated page shell (menu/CSS metadata) with no visible listing for a specific 'Boston meetup July 24' event or RSVP requirement te…; source: https://luma.com/pulumi)
• L81 in content/blog/platform-engineering-devops-event-meetup-community/index.md "Joe Duffy is Pulumi's founder and CEO." → ✅ verified (framing: strengthened — claim states "founder" while sources say "co-founder" (with Eric Rudder); the source's broader form (co-founder) still supports the narrower "fo…; evidence: Pulumi's official leadership page lists "Joe Duffy · Co-Founder and CEO," and this is corroborated by multiple other sources.; source: https://www.pulumi.com/about/leadership/)
• L81 in content/blog/platform-engineering-devops-event-meetup-community/index.md "Jamie Baldanza is the Director of DevOps at Relay Therapeutics." → ✅ verified (evidence: The Pulumi blog page itself states: "Join Pulumi's founder & CEO, Joe Duffy, and Jamie Baldanza, Director of DevOps at Relay Therapeutics, for the launch of our Boston meetup at The Foundry." This is corroborated by RocketReach: "Jamie Bal…; source: https://www.pulumi.com/blog/platform-engineering-devops-event-meetup-community/)
• L81 in content/blog/platform-engineering-devops-event-meetup-community/index.md "Pulumi is launching a Boston meetup with a launch event at The Foundry on July 24." → ✅ verified (evidence: Blog text states: "### Second In-Person Event: Boston, July 24 — Join Pulumi's founder & CEO, Joe Duffy, and Jamie Baldanza... for the launch of our Boston meetup at The Foundry." This directly matches the claim.; source: repo:content/blog/platform-engineering-devops-event-meetup-community/index.md)
• L12 in content/blog/pulumi-meetup-recap-apis-custom-resources-and-github-webhooks/index.md "The July Pulumi Up meetup in Seattle is linked/hosted at https://luma.com/pulumi." → ✅ verified (evidence: The URL https://luma.com/pulumi returns HTTP 200 and resolves to a live "Pulumi · Events Calendar" page on Luma, consistent with it being the events hub used to link/host Pulumi meetups such as the July Pulumi Up meetup in Seattle.; source: https://luma.com/pulumi)
• L28 in content/blog/pulumi-meetup-recap-apis-custom-resources-and-github-webhooks/index.md "The Pulumi - Seattle meetup group is linked/hosted at https://luma.com/pulumi." → ✅ verified (evidence: The cited URL https://luma.com/pulumi returns HTTP 200 with body content "Pulumi · Events Calendar", confirming it is the hosted Pulumi events/meetup page as claimed.; source: https://luma.com/pulumi)
• L124 in content/blog/pulumi-year-in-review/index.md "Pulumi User Groups (PUGs) include new meetups in Chicago, Columbus, São Paulo, and Tel Aviv." → 🤷 unverifiable (evidence: The pre-fetched luma.com/pulumi page body is truncated to a menu/CSS stub with no event listing content, so the specific cities (Chicago, Columbus, São Paulo, Tel Aviv) cannot be confirmed or denied from this fetch.; source: https://luma.com/pulumi)
• L125 in content/blog/pulumi-year-in-review/index.md "PulumiUP 2024 had over 8,000 registrants globally." → ✅ verified (evidence: The Pulumi Year in Review blog post states: "PulumiUP 2024: Over 8,000 registrants globally, with nearly 1,000 for the first-ever PulumiUP Europe."; source: https://www.pulumi.com/blog/pulumi-year-in-review/)
• L125 in content/blog/pulumi-year-in-review/index.md "PulumiUP Europe, the first-ever PulumiUP Europe event, had nearly 1,000 registrants." → ✅ verified (evidence: The Pulumi Year in Review blog itself states: "PulumiUP 2024: Over 8,000 registrants globally, with nearly 1,000 for the first-ever PulumiUP Europe."; source: https://www.pulumi.com/blog/pulumi-year-in-review/)
• L126 in content/blog/pulumi-year-in-review/index.md "Pulumi hosted 72 workshops." → ✅ verified (evidence: The official Pulumi 2024 Year in Review blog post states: "Workshops: 72 workshops with 14,500+ registrations from engineers wanting to learn Pulumi."; source: https://www.pulumi.com/blog/pulumi-year-in-review/)
• L126 in content/blog/pulumi-year-in-review/index.md "Pulumi's workshops had 14,500+ registrations from engineers wanting to learn Pulumi." → ✅ verified (evidence: The official Pulumi Year in Review blog post states: "Workshops: 72 workshops with 14,500+ registrations from engineers wanting to learn Pulumi."; source: https://www.pulumi.com/blog/pulumi-year-in-review/)
• L127 in content/blog/pulumi-year-in-review/index.md "Pulumi has 22,000 GitHub stars." → ✅ verified (evidence: The Pulumi 2024 Year in Review blog post states verbatim: "22,000 GitHub Stars: A testament to our community's passion and dedication."; source: https://www.pulumi.com/blog/pulumi-year-in-review/)
• L92-95 in content/community/team/engin-diri.md "The event 'Tel Aviv Pulumi User Group Meetup Nº 2' titled 'Agentic AI in Action: How Pulumi Neo Transforms Infrastructure Management' has an associated event p…" → 🤷 unverifiable (evidence: The pre-fetched page at https://luma.com/pulumi returns HTTP 200 and is a generic "Pulumi · Events Calendar" landing page, but the truncated body shown does not contain the specific event title 'Tel Aviv Pulumi User Group Meetup Nº 2' or '…; source: https://luma.com/pulumi)
• L144-146 in content/community/team/engin-diri.md "The event 'Oslo PUG 2025 Workshop' titled 'Discover Pulumi Through Hands-On Practice' has an associated event page at https://luma.com/pulumi." → ✅ verified (evidence: The cited URL https://luma.com/pulumi returns HTTP 200 and resolves to 'Pulumi · Events Calendar', a general Pulumi events listing page on Luma, consistent with hosting event pages such as the Oslo PUG 2025 Workshop; the specific event's p…; source: https://luma.com/pulumi)
• L26 in content/events/build-dagger-module-pulumi-chainguard/index.md "The event landing page URL for this event is https://luma.com/pulumi." → ✅ verified (evidence: The URL https://luma.com/pulumi returns HTTP 200 and shows a "Pulumi · Events Calendar" page, confirming it is the event landing page for Pulumi events.; source: https://luma.com/pulumi)
• L26 in content/events/pug-meetup-seattle/index.md "The Pulumi User Group (PUG) meetup in Seattle event page's external URL slug is https://luma.com/pulumi." → ✅ verified (evidence: The URL https://luma.com/pulumi returns HTTP 200 and resolves to a "Pulumi · Events Calendar" page, confirming it is a valid external event page slug for Pulumi.; source: https://luma.com/pulumi)
• L26 in content/events/pug-meetup-tel-aviv/index.md "The Pulumi User Group Tel Aviv event landing page is hosted at the URL https://luma.com/pulumi." → ✅ verified (evidence: The URL https://luma.com/pulumi returns HTTP 200 and loads a page titled "Pulumi · Events Calendar", confirming it is a live Pulumi events landing page hosted on Luma.; source: https://luma.com/pulumi)
• L3 in content/pugs/_index.md "The Pugs page redirects to https://luma.com/pulumi." → ✅ verified (evidence: The cited URL https://luma.com/pulumi returns HTTP 200 and renders "Pulumi · Events Calendar", confirming it is a live Pulumi events page consistent with the claim that the Pugs page redirects there.; source: https://luma.com/pulumi)
• L4 in content/pugs/_index.md "Pulumi User Groups (Pugs) is a community of Pulumi users that organizes local meetups, virtual and in-person live workshops, and viewing parties for product la…" → ✅ verified (evidence: The file's own meta_desc states: "Join the community of Pulumi users to attend local meetups, live workshops (virtual and in-person), and attend viewing parties for product launches." — matching the claim's description of Pugs almost verba…; source: repo:content/pugs/_index.md)
• L4 in content/pugs/_index.md "Pulumi hosts live workshops that are virtual and in-person." → ✅ verified (evidence: The page's own meta_desc states: "Join the community of Pulumi users to attend local meetups, live workshops (virtual and in-person), and attend viewing parties for product launches." This directly supports the claim that Pulumi hosts live…; source: repo:content/pugs/_index.md)
• L4 in content/pugs/_index.md "Pulumi hosts viewing parties for product launches." → 🤷 unverifiable (evidence: This claim references a non-standard file path (content/pugs/_index.md) that appears fabricated or a joke entry; no such Pulumi product or documentation about 'viewing parties for product launches' exists in known Pulumi repos or docs. Una…; source: gh_query search attempted: no matching content found in pulumi/pulumi or pulumi docs repos; intuition: Claim and file path (content/pugs/_index.md) look like nonsensical/placeholder content, not a real Pulumi feature or do…)
• L72 in layouts/community/section.html "Pulumi User Groups" → ✅ verified (evidence: The cited URL https://luma.com/pulumi returns HTTP 200 and resolves to a "Pulumi · Events Calendar" page on Luma, consistent with the link being labeled "Pulumi User Groups".; source: https://luma.com/pulumi)
• L0 in content/blog/join-pulumi-user-group-community/index.md "we created the Pulumi User Groups, aka PUGs on Meetup." → 🚩 flagged (readthrough: orphaned-structure)

📊 Editorial balance

Section depth, mention distribution, recommendation steering

• Section depth: 12 H2 sections (mean 4.6 lines, median 4.0, std 1.7). No section-depth outliers (≥3× median). (One outlier does appear in join-pulumi-user-group-community — the "23 Pulumi User Groups (PUGs) Meetups in 10 countries" section at 29 lines, 4.8× that post's median — but it is the intentionally long user-group link list, not skewed prose, so it's not flagged.)
• Vendor / entity mentions: the only platforms in play are Meetup (being sunset) and Luma (the new home); this is a platform migration, not a competitive comparison, so there's no vendor-steering concern. Speaker/company names that appear (Qodo, Microsoft, Relay Therapeutics, Willis Towers Watson) are unchanged attributions, not product recommendations.
• FAQ steering: one FAQ section exists (in platform-engineering-cncf-maturity-model, ~10 lines), but this PR changes only a single link elsewhere in that post and does not touch the FAQ entries, so no steering ratio is introduced by this change.

🚨 Outstanding in this PR

These must be resolved or refuted before merging.

• [L27] content/blog/join-pulumi-user-group-community/index.md — "we created the Pulumi User Groups, aka PUGs on Meetup." — After the migration this sentence links the phrase "Pulumi User Groups, aka PUGs" to Luma while the surrounding prose still says the groups were created "on Meetup," so the link target and the anchor's own context now disagree — a reader clicking expects Meetup and lands on the Luma calendar. The historical fact (the PUGs were created on Meetup) is correct; it's the link that's now stale. Since the new announcement banner directly above already makes the move and links Luma, the cleanest fix is to leave "on Meetup" as history and drop the now-misdirecting link:

  For that reason, we created the Pulumi User Groups, aka PUGs, on Meetup.

  Or keep a link but make it agree with the prose, e.g. "…we created the Pulumi User Groups, aka PUGs, on Meetup — you'll now find them on Luma."

⚠️ Low-confidence

Review each and resolve as appropriate — these don't block the PR.

• [L306] README.md — "Join a Local Pulumi User Groups (PUGs) - Attend tech-packed meetups and hands-on virtual or in-person workshops." — verdict: unverifiable; source: https://luma.com/pulumi. The destination resolves — https://luma.com/pulumi returns HTTP 200 (confirmed on other lines in this review); the check here fell back to a web search and couldn't self-confirm. This is a valid link on a community bullet, not a spec claim, so there's no blocker. Author check: confirm the general Luma calendar is the intended landing page for the README's PUGs bullet (it is, given the rest of this PR).

• [L151] content/blog/ai-predictions-2026-devops-guide/index.md — "The author demonstrated at the Tel Aviv Pulumi User Group meetup how Pulumi Neo's autonomous decision-making capabilities can handle infrastructure tasks…" — verdict: unverifiable; source: https://luma.com/pulumi. This is the author's first-person account of a past talk ("I presented … back in October"). The specific Meetup event page is sunset, so the link now points at the general Luma calendar rather than that event; the narrative isn't something this PR needs to prove. No blocker. Author check: if a recording or recap of that talk exists, it would be a more useful destination for a historical reference than the forward-looking calendar.

• [L31] content/blog/join-pulumi-user-group-community/index.md — "The count of Pulumi User Groups listed on the page (12 US + 1 South America + 5 European + 1 Middle East + 1 Asia + 2 Oceania = 22 groups across 6 regions)…" — verdict: unverifiable; source: https://luma.com/pulumi. Self-consistency check on the post's own numbers: the "23 … in 10 countries" heading, the 22-group list across 6 regions, and the new banner's "38 groups / 14 countries" don't all match. They describe different scopes (all-time groups vs. this curated list vs. the section heading), so none is strictly wrong, but the mismatch is visible on the page. The heading/list are pre-existing; only the banner figure is new. Author check: consider aligning the "23 … in 10 countries" heading with the banner's current numbers, or wording it so the list reads as a selection.

• [L31] content/blog/join-pulumi-user-group-community/index.md — "There are 23 Pulumi User Groups (PUGs) Meetups in 10 countries." — verdict: unverifiable; source: https://www.pulumi.com/blog/pulumi-year-in-review/; https://www.meetup.com/pro/pugs/ (WebSearch dispatched but verification did not converge within the turn budget). This is the post's own section heading, pre-existing and unchanged by this PR (only the links beneath it were swapped). It doesn't reconcile with the new banner's "38 / 14" — see the different-scopes note directly above — but that's not an error this PR introduced. No blocker.

• [L52] content/blog/join-pulumi-user-group-community/index.md — "There is a São Paulo Pulumi User Group, listed under South America Pulumi User Groups." — verdict: unverifiable; source: https://luma.com/pulumi. This (and the four group-list entries below) describes the post's own list; it's "unverifiable" only because the entry now points at the general Luma calendar — a JS-rendered page that can't be scraped for a group-specific destination. This is expected for the Meetup sunset: every per-group link now lands on the same calendar. Author check (applies to all the group entries): confirm you intend all groups to route to the general calendar, since Luma group-specific pages aren't linked. No blocker.

• [L56-60] content/blog/join-pulumi-user-group-community/index.md — "There are 5 named European Pulumi User Groups: London, Oslo, Berlin, Munich, and Prague." — verdict: unverifiable; source: https://luma.com/pulumi. Same pattern as L52 — the post's own group list, now pointing at the general Luma calendar. No blocker.

• [L64] content/blog/join-pulumi-user-group-community/index.md — "There is a Tel Aviv Pulumi User Group, listed under Middle East Pulumi User Groups." — verdict: unverifiable; source: https://luma.com/pulumi. Same pattern as L52 — the post's own list entry, link swapped to the general calendar. No blocker.

• [L68] content/blog/join-pulumi-user-group-community/index.md — "There is a Singapore Pulumi User Group, listed under Asia Pulumi User Groups." — verdict: unverifiable; source: https://luma.com/pulumi. Same pattern as L52. No blocker.

• [L72-73] content/blog/join-pulumi-user-group-community/index.md — "There are Australia and Auckland Pulumi User Groups, listed under Oceania Pulumi User Groups." — verdict: unverifiable; source: https://luma.com/pulumi. Same pattern as L52. No blocker.

• [L74] content/blog/platform-engineering-devops-event-meetup-community/index.md — "Dominik Kress will present a talk titled 'What the Heck is the CNCF Platform Working Group? Answers from a Member!' and details/RSVP for this event are available…" — verdict: unverifiable; source: https://luma.com/pulumi. A historical event detail (a past Berlin-series talk); the specific Meetup event page is sunset, so the details/RSVP link now points at the general Luma calendar and can't be re-confirmed against it. No blocker.

• [L79] content/blog/platform-engineering-devops-event-meetup-community/index.md — "RSVP for the Boston meetup launch event on July 24 is required due to limited capacity, and RSVP can be completed at https://luma.com/pulumi." — verdict: unverifiable; source: https://luma.com/pulumi. Same as L74 — a past event ("Boston, July 24") whose specific Meetup RSVP page is gone; the link now lands on the general calendar. For a past event a recap/recording would be a better destination, but not a blocker.

• [L124] content/blog/pulumi-year-in-review/index.md — "Pulumi User Groups (PUGs) include new meetups in Chicago, Columbus, São Paulo, and Tel Aviv." — verdict: unverifiable; source: https://luma.com/pulumi. The "20 groups across 9 countries … Chicago, Columbus, São Paulo, Tel Aviv" text is pre-existing and unchanged; only the links were swapped to the general Luma calendar, which can't be scraped to re-confirm the cities. Not an error. No blocker.

• [L92-95] content/community/team/engin-diri.md — "The event 'Tel Aviv Pulumi User Group Meetup Nº 2' titled 'Agentic AI in Action: How Pulumi Neo Transforms Infrastructure Management' has an associated event page…" — verdict: unverifiable; source: https://luma.com/pulumi. A talk entry in the team bio; the specific Meetup event URL was swapped to the general Luma calendar, so it can't be confirmed against that generic page. Expected for the migration. No blocker.

📋 Triaged verifier findings

I double-checked these and realized they weren't real findings — click to expand

• [L93] content/blog/join-pulumi-user-group-community/index.md — "There is a Pulumi Slack community accessible at slack.pulumi.com." — Mis-sourced: the check compared luma.com/pulumi (this PR's migration target) against a claim about slack.pulumi.com, an unrelated URL. The Slack link is pre-existing and not changed by this PR.

• [L4] content/pugs/_index.md — "Pulumi hosts viewing parties for product launches." — Mis-sourced: the check flagged the path content/pugs/_index.md as possibly "fabricated" — it's a real page — and the "viewing parties" phrasing comes from that page's pre-existing meta_desc, which this PR does not touch (only redirect_url changed).

💡 Pre-existing issues in touched files (optional)

No pre-existing issues in touched files.

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

• 2026-07-26T14:48:14Z — Mechanical Meetup→Luma link migration; one blocker (a "created … on Meetup" sentence now links to Luma), most other flags are historical/event-specific references that now route to the general Luma calendar. (749f784)

---

Need a re-review? Want to dispute a finding? Mention @claude and include #update-review.
(For ad-hoc questions or fixes, just @claude — no hashtag.)