[TASK] Add screenshot capture guidance: viewport and iframe - #539
Merged
linawolf merged 1 commit intoAug 15, 2026
Merged
Conversation
CybotTM
marked this pull request as draft
August 14, 2026 12:47
The screenshot guidelines state the 1400 x 1050 px target but nothing about capturing it. Two additions from practice: size the window to at least 1440 x 1050 before capturing (narrow viewports collapse the module menu and truncate tables), and backend module content lives in an internally scrolling iframe, so full-page screenshots capture only the outer frame - a taller viewport is the way to capture tall module views. Assisted-by: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
CybotTM
force-pushed
the
docs/screenshot-capture-guidance
branch
from
August 14, 2026 13:22
29ca32e to
6bcb580
Compare
CybotTM
changed the title
CybotTM
marked this pull request as ready for review
August 14, 2026 13:30
linawolf
approved these changes
Aug 15, 2026
CybotTM
added a commit
to netresearch/typo3-docs-skill
that referenced
this pull request
Aug 15, 2026
TYPO3-Documentation/TYPO3CMS-Guide-HowToDocument#539 and TYPO3-Documentation/TYPO3CMS-Guide-HowToDocument#543 were merged on 2026-08-15, so the screenshot viewport and iframe rules and the "no symlinks in Documentation/" rule now live in the official manual. Verified against the rendered pages, not only against the merge: GuidelinesForImages carries the 1440 and iframe wording and FileStructure carries the symbolic-link note. A copy kept past that point is no longer a stopgap. It is a second source that drifts while the checkpoints hold it green, which is the failure this skill's own authority rules describe, so both copies shrink to a reference plus the part that is genuinely ours. Review then showed the first pass stopped too early. Upstream also states the necessity rule, the formats and the 1400 x 1050 target, and even the capture-wider-then-crop advice I had kept as local value — so those go too, leaving a labelled pointer, the NR format deviation, the two lists of what earns a screenshot at all, and the Playwright recipe. The verification tell stays, with its number corrected: it cited a 1440x900 file, a height no recipe in the file produces. The real signature is a file exactly as tall as the viewport that was set. For rendering it leaves the distinction upstream does not draw: a regular Documentation/AGENTS.md file is fine because unknown .md files are ignored, so agent-rules tooling has to exclude the folder from linking, not from having such a file. canonical-sources.md gains the rule that made this a same-day action rather than a someday one, with the date both facts became upstream — and its own charter is corrected: it illustrated "knowledge that legitimately stays local" with the fullPage trap, sixteen lines above the paragraph retiring that very fact. A reader applying the charter would have restored what this commit removes. The example is now the tell, which upstream genuinely does not carry. Assisted-by: claude-code:claude-fable-5 Agent-Session: https://claude.ai/code/session_012NiLDH3iWw8CVdAnimJbF8 host=32116e Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
CybotTM
added a commit
to netresearch/typo3-docs-skill
that referenced
this pull request
Aug 15, 2026
…s accepted today (#81) [TYPO3-Documentation/TYPO3CMS-Guide-HowToDocument#539](TYPO3-Documentation/TYPO3CMS-Guide-HowToDocument#539) and [TYPO3-Documentation/TYPO3CMS-Guide-HowToDocument#543](TYPO3-Documentation/TYPO3CMS-Guide-HowToDocument#543) merged on 2026-08-15, so the screenshot viewport and iframe rules and the "no symlinks inside `Documentation/`" rule now live in the official manual. Checked against the rendered pages rather than only against the merge: [Guidelines for images](https://docs.typo3.org/permalink/h2document:guidelines-for-images) carries the 1440 and iframe wording, [File structure](https://docs.typo3.org/permalink/h2document:file-structure) carries the symbolic-link note, and both permalink identifiers resolve. A copy kept past that point stops being a stopgap and becomes a second source that drifts while the checkpoints hold it green — the failure this skill's own authority rules describe. **Review showed the first pass stopped too early.** Fetching the canonical page and comparing it line by line against `screenshots.md` found that upstream also states the necessity rule, the formats, the 1400 × 1050 target, and even the capture-wider-then-crop advice I had kept as local value. Those were duplications before today and stayed duplications after the first prune, while the header claimed the file now kept "only the executable recipe and the verification tell". They are gone; what remains is a labelled pointer, the NR format deviation, the two lists of which subjects earn a screenshot at all, and the Playwright recipe. The verification tell stays, with its number corrected. It cited a 1440×900 file — a height no recipe in this file produces. The real signature is a file exactly as tall as the viewport that was set. `rendering.md` keeps the distinction upstream does not draw: a regular `Documentation/AGENTS.md` *file* is fine, because unknown `.md` files are ignored, so agent-rules tooling must exclude the folder from **linking**, not from having such a file at all. `canonical-sources.md` gains the rule that made this a same-day action rather than a someday one — and its own charter needed correcting. It illustrated "knowledge that legitimately stays local" with the `fullPage` trap, sixteen lines above the new paragraph retiring that very fact; a reader applying the charter would have restored exactly what this PR removes. The example is now the tell, which upstream genuinely does not carry. No checkpoint referenced either fact, so nothing in `checkpoints.yaml` changes. _Assisted by claude-code:claude-fable-5 — [Session](https://claude.ai/code/session_012NiLDH3iWw8CVdAnimJbF8)_
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
2 participants
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.
The screenshot guidelines state the 1400 x 1050 px target but nothing about capturing it. Two additions from practice: size the window to at least 1440 x 1050 before capturing (narrow viewports collapse the module menu and truncate tables), and backend module content lives in an internally scrolling iframe, so full-page screenshots capture only the outer frame — a taller viewport is the way to capture tall module views.