Visual documentation pass — 2026-10-27

Use MassForge 0.3.0's current local documentation as the AshenForge style reference. Keep its typography, navigation, image borders and keyboard-accessible image enlargement. UIForge retains its own icon, content and development status. No documentation is published by this task.

Every teaching step should give an exact editor/asset location, an action, a readable actual editor image and an expected result. Show the relevant hierarchy, property names, class defaults and graph pins; a finished gameplay image alone cannot teach authoring. Place images beside the step they explain. Captions must state what is selected and what the reader should notice.

Capture the current source project in UE 5.8.3. Runtime captures temporarily hide the player cursor and restore it immediately afterwards; editor captures use Slate's window renderer. Never erase/inpaint a pointer, fabricate a Blueprint graph or replace an actual property with an illustration. Reject and retake obstructed, cursor-bearing, clipped or unreadable images. Record source asset/action, dimensions, hash and individual review in one small manifest.

Priority routes:

1. Find/enable the plugin and configure CommonUI; locate the learning assets.
2. Build a local root, main screen, HUD entry, pause and settings flow in Blueprint.
3. Build four-tab settings from Designer widgets, definitions and custom providers.
4. Customize themes, button states, HUD layout, entries and cooldown presentation.
5. Review current playable MMO/RTS menus, settings, dialogs, HUD and theme variants.

Reuse the existing DocumentationSite. Keep historical evidence labelled as historical; current guides/gallery should show the latest source presentation. Preserve user assets, gameplay saves and other projects. Bounded work files live in ../Workspace/Documentation20261027; no new project hosts or cooked copies are needed for a documentation pass.

Delivered in this pass

• Three illustrated authoring routes: game integration (9 steps), tabbed settings (9 steps), and customization (6 steps). Linked from the home page, top navigation and existing detailed references.
• A refreshed source-only MMO/RTS gallery covering main/load/confirmation/HUD/pause, all settings pages, ability browser, journal and live theme variation.
• 58 actual engine captures recorded; 57 individually approved for their stated teaching/gallery purpose. One distant provider overview is rejected for teaching and replaced by two readable details. No cursor removal, image generation or compositing. The manifest stores the reviewed image hash; site synchronization rejects new/changed guide images until reviewed.
• MassForge 0.3.0's local current documentation inspected for navigation, typography, image presentation and step-by-step teaching. The shared style is retained with UIForge identity and its own status. Enlargement keeps keyboard access and descriptive alternatives, and adds an actual-pixel view with scrolling for small Blueprint text.
• Native IFButton labels and definition-backed settings rows now preview in Designer. Blueprint-owned button trees keep their own layout and receive appearance callbacks after references bind; opening a definition-backed row does not start/save a settings session.

Verification and boundaries

The UE 5.8.3 Editor target builds. All 95 saved UI/example Blueprints compile. The real learning-map flow passes 20 observations: main → HUD/entry action → pause → settings scale preview/tab change/Cancel → modal Back → confirmation → main, including model quantity change, paused-world state and HUD cleanup. These are software Slate interactions, not physical-device certification.

Seven teaching Blueprints have identical graph node/pin/link/default signatures after spacing changes (coordinates excluded). All five existing gameplay/profile SaveGames retain their original hashes. No reference project, gameplay rules or inventory system was changed. Work files and bounded source backup remain in ../Workspace/Documentation20261027; images total about 45 MiB. No new cooked project copy was made.

Build/link/image-alt checks and local browser navigation/image-enlargement checks are kept with this pass's verification receipt. An editor shutdown failure while a simple asset editor was open was preserved locally; the capture shutdown now closes asset editors before editor teardown. It is not hidden as a passing runtime test.

This pass does not certify a refreshed package, independent-host installation of the Designer-preview changes, physical controller/touch, performance, or the whole plugin's release readiness. Older packaged and functional receipts retain their historical scope. The three new routes cover the principal authoring workflows; advanced reference pages are not all converted into illustrated click-by-click tutorials yet.