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 Data file

Legacy CMS Data stores datasets whose shapes come from a separate legacy Model file. It remains for old projects; use typed Content for new work.

Property: Identity · Current behavior: untyped file below cms/data/
Property: Visibility · Current behavior: hidden and unavailable for current UI creation
Property: Workspace · Current behavior: legacy dataset/row editor
Property: Features · Current behavior: dataset add/delete; row add/edit/reorder/delete
Property: MCP · Current behavior: get-cms, legacy dataset and row operations
Property: Status · Current behavior: compatibility only

Guidance

The referenced Model file and model ID must exist for rows to resolve. Dataset definitions and values persist; content changes can be offered to Preview through Update rather than forcibly resetting every current session.

Do not create new legacy data or rewrite rows into a guessed modern schema. Plan and verify any migration together with its Model definitions.

On this page

Legacy CMS Data file

Guidance