A Page is a responsive visual file that exports as a routable website/application screen.
Property: Identity · Current behavior: any file below pages/
Property: Creation · Current behavior: Create File in permitted Pages folders
Property: Fixed file · Current behavior: pages/index is the protected home page
Property: Workspace · Current behavior: Files/Elements, canvas, Design/Animate/Logic, bottom timeline
Property: Result · Current behavior: generated Page React/SCSS, route and SEO output
Property: MCP · Current behavior: extensive Component-file families plus set-page-seo
shared Body/element hierarchy across responsive screens;
canvas drawing, hierarchy, styles, variants, interaction states, logic, data mounts, and timelines;
Page-sized screen defaults and generated container-responsive behavior;
SEO title, description, social image, canonical URL, crawler indexing, and structured data;
executable Preview, test cases, themes, variants, and safe Preview identity selection;
Page-oriented default export and route path.
Use Design a Component, responsive design, and Preview/debug; the visual mechanics are shared with Components.
Discover the Page with list-design-files, then use screen, element, style, data-structure, logic, timeline, Preview, and export operations. Set Page metadata with set-page-seo. MCP changes stored content without reproducing open tabs or canvas navigation.
Page content exports with its styles and route-facing metadata. Inspect generated imports and build it in the intended website shell. The protected home Page cannot be renamed, moved, duplicated, or deleted through ordinary File Explorer actions.
Eligible Page content uses the shared design-file UI/MCP history. Whole-file operations and deployed routes are outside that history. A Page cannot be moved across file families without explicit conversion.