Edit Studio JSON
Open a page in Website > Studio, then select Source to edit its full revision as JSON, including its composition and settings. Use Page settings for a form to edit the title, group, publication date, access rules and summary image.
For most changes, use Layout. Source is useful when you want to inspect or change several component properties together.
Page composition
Source contains the page’s titles, settings and composition. Keep those settings
when changing the layout. The nested composition has version: 1 and an ordered
sections array. Each section has
an id, an appearance and ordered instances. Each instance has its own
id, a component object and layout.
{
"version": 1,
"titleEn": "Welcome",
"titleFr": "Bienvenue",
"composition": {
"version": 1,
"sections": [
{
"id": "welcome-section",
"appearance": "plain",
"instances": [
{
"id": "welcome-text",
"component": {
"type": "cio-text",
"version": 2,
"heading": {
"en": "Welcome",
"fr": "Bienvenue"
},
"body": {
"en": "Find a program that suits you.",
"fr": "Trouvez une activité qui vous convient."
}
},
"layout": {
"span": 12,
"presentation": "standard"
}
}
]
}
]
},
"published": false,
"publishedOn": null,
"groupId": null,
"slug": "welcome",
"membersOnly": false,
"productIds": [],
"summaryImage": null
}
This is a complete page revision. Use your existing titles, slug, group and
access settings when editing an existing page. Don't wrap it in a filename,
documents or schemaVersion. The agent tool inspectWebsitePageSchema
returns this full schema and the component catalog. Layout changes belong
inside composition; its version is separate from the page revision's version.
Use unique IDs across all sections and instances in the page: 1 to 64 lowercase letters, digits, underscores or hyphens. Keep an instance's ID when moving it; give a copy a new ID. You can use the same component kind more than once.
Sections and widths
Each section is a background change in Layout: its components sit on its
appearance until the next section. appearance accepts plain, surface,
action, muted or inverse, using your theme's colours. Sections don't
contain other sections, columns or split definitions. In Layout, removing a
background change moves its components into the preceding section instead of
deleting them.
Components use a shared 12-column grid. layout.span chooses the desktop width:
| Width in Layout | span |
|---|---|
| Quarter | 3 |
| Third | 4 |
| Half | 6 |
| Two thirds | 8 |
| Three quarters | 9 |
| Full | 12 |
Each component supports only some widths. For example, Hero is full width.
Check the component's width choices in Layout or the
component reference. Components flow in their saved
order; they don't move ahead to fill gaps. Product types spans two rows while narrower than full width. Row height
comes from content, and rowSpan is not an editable field.
At tablet width, anything narrower than full becomes half width. At phone width, everything becomes full width. English and French share these widths, sections and component order.
layout.presentation accepts standard or contained. Standard uses the
component's normal presentation; contained fits it within the assigned area.
Preview the result before publishing.
Component properties
The component object has its exact type, version and supported fields.
See the component reference and
complete examples. Unknown fields and unsupported
versions are refused.
Most text fields accept a shared string or an en/fr object. Supply usable
text in your main language. Missing secondary text falls back to the main
language. Translate headings, body text, button labels, captions and alternative
text; keep field names, component types and record IDs unchanged.
Text version 2 supports page prose with an optional heading and formatted body. Version 1 is short plain text with a required heading. Put embedded components in their own instances. Provider components accept approved URLs or identifiers, not pasted scripts. Studio validates content before it can be saved.
Use an asset ID returned by request_context(media), which lists the club's ready or attached Website media with labels and previews, or the handle of the image the person attached to this chat; the approved save publishes it. An image reference uses media.assetId or media.conversationHandle and useful alt text.
Live components read current club records. Changing their JSON doesn't change products, events or sponsors. Empty live lists keep their place and show an empty-state message. Premium and provider access rules still apply.
Save, check and publish
- Change the source. Use double quotes, commas between entries and no trailing comma. JSON doesn't accept comments.
- Fix any validation error, then select Save for a private version.
- Check Visual in both languages and at each device width.
- Select Publish when ready, or Save and publish for unsaved changes.
Restore in Versions loads older content as unsaved changes. It doesn't save or publish it. Use Back at the bottom left to return to the list; confirming that you want to leave discards unsaved changes.
Site-wide settings
Choose your homepage with the picker beside Navigation on Studio's list. Edit the public menu with Navigation. The menu is a separate JSON array, not part of a page composition. Confirming a homepage or navigation change applies it publicly immediately.
Manage colours under Themes, calendar display under Calendar, and footer policy links under Settings > Policies. These aren't page components or Source documents.