Branch: refs/heads/okf-doc-image-size-checker-prerelease Home: https://github.com/xwiki/xwiki-dev-llm Commit: c0638ef9889fc1bbf55512075eb1d8c4bc72043f https://github.com/xwiki/xwiki-dev-llm/commit/c0638ef9889fc1bbf55512075eb1d8... Author: Vincent Massol <[email protected]> Date: 2026-07-28 (Tue, 28 Jul 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json M xwiki/instructions/xwiki-org.md M xwiki/okf/conventions/documentation-mechanics.md M xwiki/okf/conventions/documentation.md M xwiki/okf/index.md M xwiki/skills/xwiki-knowledge/SKILL.md Log Message: ----------- [Misc] Record the mandatory image size, the invisible checker findings and pre-release documenting Three facts established while rebuilding the BlockNote user documentation, each one a gap or a contradiction in what the OKF said: - documentation.md presented `size` as optional on the `{{image}}` macro. In the `documentation` space the quality checker requires it and rejects `width`, so a screenshot can never render at its natural width. That moves the constraint onto capture: take it at exactly the pixel width of the size it will be shown at, or it is rescaled — an undersized original is upscaled and blurred. - documentation-mechanics.md said the checker's findings are stored as DocumentationViolationClass objects. Some are not: the image-size one is an inline error box in the rendered page and creates no object at all, so a check that lists objects only reports a broken page as clean. Both surfaces have to be looked at, the second by grepping the rendered HTML for "Best practice:". - The versioning section said to write from the perspective of the latest version, which reads as a ban on documenting anything unreleased. Documenting a feature ahead of its release is accepted and even desirable, so the page is ready on release day, provided the new content carries `{{version since="…"}}`. It also settles the case the rule left open — the newest UI is unreleased and no screenshot can show it: the released version stays the baseline prose and the additions are badged. The xwiki-knowledge skill also told the reader to bump four version fields. There are five: opencode.jsonc carries the version in a comment, and validate.mjs fails the run when it is left behind. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications