Add Creating a Workflow docs page with automated screenshots#21
Merged
Conversation
Detailed design for the first pass: target the updating-blueprints docs page, use a single spec + helper, reuse existing Playwright config, commit screenshots alongside the markdown that references them. Proves the pattern before generalising to other docs pages. Refs #19 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Captures the full Create Workflow flow as walked through interactively with the user. Dual-purpose: source for the real docs page, and script for the Playwright screenshot spec. 14 screenshot markers embedded. Refs #19 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Drop the media picker folder-navigation screenshot in favour of a single capture at the point the PDF is selected. Convert open questions to resolved decisions: pre-populated Destination tab captured first, no PDF preview screenshot needed, fixed workflow name with delete-if-exists for stable screenshot captions. Refs #19 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Docs and spec share filenames only — spec does not read markdown, does not assert against docs prose. Goal is screenshot generation; loose coupling keeps both artefacts independently editable. Keep a standard visibility assertion before each screenshot as normal Playwright practice. Refs #19 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
First attempt at the docs-screenshot pattern. The markdown references screenshots by filename, the spec produces those screenshots, filename convention is the only coupling. Playwright config extended with a 'docs-screenshots' project scoped to *.screenshots.ts files so the screenshot run is separable from the regular E2E suite. Refs #19 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
First working pass of the Playwright-driven screenshot pattern. The spec drives the Create Workflow flow and captures 11 screenshots that the docs page references. Two screenshots that require interacting with UUI select-only cards are deferred — see #20. Docs prose adjusted to describe the skipped steps in words. Spec runs cleanly in ~12 seconds, regenerating all 11 captures on demand. Refs #19, follow-up #20 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced Apr 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #19
Follow-up: #20 (three remaining screenshots that need UUI select-only handling)
Test plan
🤖 Generated with Claude Code