Merged
Conversation
Adds a generalised version of the multi-device documentation testing workflow from Peli's Agent Factory. Builds and serves the project's documentation site locally, then runs Playwright tests across mobile, tablet, and desktop viewports to catch responsive layout issues, broken navigation, and accessibility problems. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…-9da96348e6a1fd84
dsyme
approved these changes
Mar 3, 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.
Phase 1 — Consistency Check
✅ All workflows have matching docs pages. All docs pages are listed in README.md. No inconsistencies found.
Phase 2 — New Workflow: Multi-Device Docs Tester
Source
Original:
daily-multi-device-docs-tester.mdingithub/gh-awMerge Rate
100% merge rate — 2 merged PRs out of 2 proposed (as documented in the Peli's Agent Factory documentation blog series)
Why It's Valuable
Documentation sites that look fine on desktop can break on mobile — overflowing navigation, unreadable text, inaccessible interactive elements. Catching these issues continuously means users on phones and tablets always get a good experience. Any project with an npm-based docs site (Astro Starlight, Docusaurus, VitePress, MkDocs-Material, etc.) benefits from automated multi-device testing.
Generalization Plan
The original is tightly coupled to the
github/gh-awdocumentation structure:shared/docs-server-lifecycle.md(gh-aw-specific Astro Starlight server management) — inlined as configurable bash commands/gh-aw/URL pathworkflow_dispatchinputs fordocs_dir,build_command,serve_command, andserver_port— making the workflow work with any npm-based documentation frameworkshared/reporting.md, and the full device matrix[cookie](gh-aw-specific) to[documentation, testing]Proposed Name
daily-multi-device-docs-testerFiles Changed
workflows/daily-multi-device-docs-tester.md— workflow specificationdocs/daily-multi-device-docs-tester.md— documentation pageREADME.md— entry added under "Code Improvement Workflows (by analysis, producing report)"