Repository navigation
Document optional visual UI authoring - #74
Merged
Merged
Conversation
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
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.
Explain how to opt into visual HTML/CSS authoring from the native Explorer, edit elements through Properties and transform handles, manage layers, and explicitly save or undo UI changes.
Includes a copyable HUD example, stylesheet document selection, external-edit conflict recovery, read-only/Play behavior, and the layout preview's CSS and runtime rendering limits. The guide is reachable through the existing HTML/CSS navigation entry.
Validation: documentation build, ESLint with zero warnings, TypeScript check, and npm audit at moderate severity all passed (zero vulnerabilities).