blog: add Pulumi Cloud passkey support announcement

[djgrove]

Summary

New blog post announcing passkey sign-in for Pulumi Cloud. Scheduled to publish on 2026-07-01.

• Post lives at content/blog/passkey-support-in-pulumi-cloud/.
• Author: devon-grove (solo).
• Meta + feature images rendered with the Shield template via /blog-meta-image.
• Social copy (X / LinkedIn / Bluesky) drafted via /draft-social-post, all passed the social-media critic on the first round.

Pre-merge review notes

Already ran /docs-review and /seo-analyze locally and applied the suggestions:

• Definition-first opening (passkey defined before the password-problem framing).
• MFA cross-link to /docs/administration/organizations-teams/accounts/#setting-up-mfa.
• Numbered enrollment steps under Setting up a passkey.
• Replaced the strongest-available-today superlative with a concrete phishing-resistance claim.
• Added a 3-question FAQ before Try it out.
• Fixed the closing GitHub link (pulumi/pulumi-service 404'd publicly → pulumi/pulumi/issues).

Open for human review

• The two remaining FAQ answers (lost-device recovery, hardware-key compatibility) make specific product claims I'd like a security eng confirmation on before this goes live.
• A /docs/ page covering passkey enrollment doesn't exist yet — recommended to land alongside or before the 2026-07-01 publish date.
• SEO pass suggested an enrollment-flow screenshot once the feature ships; not included here.

Test plan

• make serve and verify the post renders at http://localhost:1313/blog/passkey-support-in-pulumi-cloud/
• Confirm meta.png looks right in a LinkedIn / X OpenGraph preview
• Engineering sign-off on the FAQ product claims
• make lint clean

🤖 Generated with Claude Code

[github-actions]

Social Media Review

content/blog/passkey-support-in-pulumi-cloud/index.md

X — PASS

LinkedIn — PASS

Bluesky — PASS

---

Suggestions (advisory)

These are stylistic notes — they don't block the post.

X

• "That ends today" closes the curiosity gap before the reader clicks; replace with a partial reveal ("Here's what replaces it") to preserve pull
• "no extra cost" is generic filler that could appear in any vendor announcement; drop it or replace with a specific reason passkeys cost nothing to add

LinkedIn

• "Today we're rolling out" is press-release phrasing; reframe around the user problem to lead with consequence instead of announcement
• The technical explanation (public-key credential, private half, challenge-signing) delivers the full mechanism, closing the curiosity gap; cut to one sentence and let the article deliver the rest

Updated for commit fb115bd7bfdadffe3d9625ff64b3ade92c941794 (short: fb115bd) at 2026-06-26 19:28 UTC.

[pulumi-bot]

Your site preview for commit fb115bd is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-19895-fb115bd7.s3-website.us-west-2.amazonaws.com