Branch: refs/heads/doc-convert-multi-session-plan Home: https://github.com/xwiki/xwiki-dev-llm Commit: 3ce1455232b8bdd0a8d52b9fa8235728b566bb1b https://github.com/xwiki/xwiki-dev-llm/commit/3ce1455232b8bdd0a8d52b9fa82357... Author: Vincent Massol <[email protected]> Date: 2026-08-29 (Sat, 29 Aug 2026) Changed paths: M xwiki/okf/conventions/documentation-migration.md M xwiki/okf/index.md M xwiki/skills/xwiki-doc-convert/SKILL.md M xwiki/skills/xwiki-doc-convert/references/conversion-plan.md Log Message: ----------- [Misc] Publish a documentation conversion once, at the end, instead of page by page * xwiki.org is public and a conversion runs for weeks, so a page saved the moment it is drafted is live with red links to the siblings and hubs that do not exist yet, usually under a missing parent, carrying any defect until someone happens to look. Observed on a real conversion in flight. * Make the `page-*` tasks preparation tasks: they draft into `pages.py`, capture screenshots and lint offline, and no longer call `docpages.py save`. * Add a single `publish` task at the end of the standard task set. It saves the whole set in one pass, parents before children, then runs `verify` and absorbs the live doc checker's findings. * Say that a Change Request stays the preferred vehicle and why, and that choosing to save direct changes nothing about the timing. * Spell out the two consequences for the drafting tasks: the offline lint becomes their only gate, so what the live checker would have caught has to move into it; and the publish task reads back what it wrote rather than assuming the syntax rendered. * Record the rule in the OKF, in documentation-migration, so it survives the skill. 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