chore(website): add workflow launch post image

[NicholasKissel]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[railway-app]

🚅 Deployed to the rivet-pr-4286 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
website	✅ Success (View Logs)	Web	Feb 24, 2026 at 9:48 am
frontend-inspector	😴 Sleeping (View Logs)	Web	Feb 24, 2026 at 7:44 am
frontend-cloud	😴 Sleeping (View Logs)	Web	Feb 24, 2026 at 7:43 am
ladle	❌ Build Failed (View Logs)	Web	Feb 24, 2026 at 7:34 am
mcp-hub	✅ Success (View Logs)	Web	Feb 24, 2026 at 7:34 am

[NicholasKissel]

• chore(website): add workflow launch post image #4286 👈 (View in Graphite)
• chore: workflows launch post #4272
• chore(rivetkit): fix sqlite-vfs for next-js & cf workers #4271 : 1 other dependent PR (#4275 )
• chore(rivetkit): fix run engine config #4268 : 1 other dependent PR (#4273 )
• chore: multiplayer cookbook patterns #4261 : 1 other dependent PR (#4266 )
• docs: document queue with interval pattern #4265
• chore(rivetkit): migrate to sqlite instance per-actor for concurrency optimizations #4264
• docs: workflows #4256
• chore(rivetkit): update conns to be hibernatable #4260
• chore(inspector): add back database tab #4255
• chore: impl canInvoke for matchmaker #4253
• chore: multiplayer cookbook #4200 : 1 other dependent PR (#4201 )
• feat(dashboard): bring new tabs back #4249
• fix(rivetkit): fix sqlite teardown logic #4259
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review: chore(website): add workflow launch post image

This PR adds a single PNG image to the 2026-02-24-introducing-rivet-workflows blog post directory. The image is automatically picked up by the build system via import.meta.glob in [...slug].astro and used as both the hero image and OG image for the post.

The Change

The addition is correct — image.png at the post directory root is exactly the expected filename and path for the blog's image loading convention (/src/content/posts/*/image.{png,jpg,gif}).

Observations on the Associated page.mdx

The page.mdx for this post already exists on main. A few things worth addressing before publishing:

Incomplete section: The post contains an unfilled placeholder:

## Inspector

TODO

This will render as literal "TODO" for readers. Either the Inspector section should be written out or the heading should be removed before this goes live.

Category: The frontmatter uses category: changelog. The blog's [...slug].astro filters out changelog posts from the /blog/ route — they only appear under /changelog/. For a launch announcement of this scope, launch-week or technical might be a better fit if the intent is for it to appear on the blog. If changelog is intentional, no change needed.

Summary

The image addition itself is correct. The main items to resolve are in the existing page.mdx content (the TODO section and category choice) before merging and publishing.