Skip to main content
Pages metadata mirrors your application’s routes in Studio. It helps editors find the labels, Singles, and collection entries used by a page. It does not create routes or move content.
Pages is a pre-release Studio feature. It may not be available in your production workspace yet. Collections, Singles, and Labels continue to work without it.

​
Register a route

Your application owns the route. Add matching metadata with a stable ID:
For a dynamic route, bind its URL parameter to a collection:
Studio can then show a post selector before opening the page’s content.

​
Add page sources

Sources tell Studio which editable content belongs in the page workspace:
The supported source types are labels, single, and collection. Collection entries remain in Collections. Pages only gives editors another way to reach the entries used by a route.

​
Review the route list

Use --expand to include parameters and sources. For dependent route parameters, collection queries, rename, clear, and delete commands, see the CLI reference.

​
What’s next

Content

Define Singles and collections.

Labels

Group page interface copy by key.

CMS

Edit available content in Studio.