Documents
Welcome
Introducing
Why Misaki Studio
Compare
Start Here
Learn
Workflows
Export & Ship
AI & MCP
Questions & Answers
Reference
Project interface reference
File types
Page file
Component file
Code Component file
Mockup file
Document file
Document Page file
Content file
Database table file
Users file
API file
Storage file
Script file
Image collection file
Colors file
Fonts file
Design-system Images file
Font Weights file
Radius file
Spacing file
Themes file
Audios file
Videos file
Export Settings file
Environment file
Libraries file
Legacy CMS Model file
Legacy CMS Data file
General file
Element types
Design properties
Keyboard shortcuts
MCP capabilities
Export output reference
Dependencies and compatibility
Browser versus desktop
Current limitations
Troubleshooting
Examples

Legacy CMS Model file

Legacy CMS Model stores field schemas separately from data. It remains loadable for old projects but is hidden from current CMS creation; use Content for new work.

  • Property: Identity · Current behavior: untyped file below cms/model/

  • Property: Visibility · Current behavior: hidden by current CMS File Explorer policy

  • Property: Workspace · Current behavior: legacy model editor

  • Property: Features · Current behavior: model add/rename/delete; typed fields; TypeScript definitions

  • Property: MCP · Current behavior: get-cms, model operations, shared field operations

  • Property: Status · Current behavior: compatibility only

Guidance

Existing files can be inspected and maintained through their legacy UI/MCP tools. Their separately stored Data file and model IDs must continue to resolve. Do not change keys/shapes merely to modernize naming and do not create new legacy files as a workaround.

Plan migration to typed Content as a separate, data-preserving workflow. Runtime verification is required before publishing migration instructions.

On this page
Legacy CMS Model file
Guidance