Skip to main content
Using Studio

Studio for WebApp and Module Items

Edit WebApp and Module items in Studio, and give single items a custom layout with slots.

Written By Luke Wakefield

Last updated About 4 hours ago

Until now you could edit Pages, Templates and Detail Layouts in Studio, but not the items themselves. With Studio v2.18 you can open any WebApp or Module item (a blog post, a project, an event) in Studio and edit it visually. You can also give a single item its own custom layout, while the detail layout still controls the overall structure.

Watch the demo (8 min):

Before you start

  • Update the Studio module to v2.18 or later from the Marketplace.

  • Set up the WebApp or Module detail page for Studio. Build the detail layout in Studio's detail view editor. The Studio tab only appears on items once this is done.

  • eCommerce Products and CMS Categories are not supported yet. Both are in QC and coming soon.

Where to find it

Open the item in Admin. You'll see a Studio tab next to the item's other tabs. It shows the item's detail page in the Studio editor, with that item's own content.

You set up the shared structure in the detail layout. You edit a single item in its Studio tab.

The four ways content behaves in an item

1. Static content in the detail layout (read-only)

Static content in the detail layout is global. There is only one version of it, so every item shows the same content. In an item's Studio tab these sections are read-only. To change them, edit the detail layout.

2. Fields mapped to the item itself (editable)

Make a section dynamic by mapping its fields to the item's own fields, for example a heading mapped to the item's Name. Each item then shows its own value, and you can edit it in the item's Studio tab. You are editing the real item field, so the change also shows in Admin, and the other way round.

The slug is the one exception. You can't edit it in Studio, because a slug change can affect SEO. Change it on the item's Detail tab (next to the Studio tab).

3. Slots (per-item sections)

Slots make each item unique. Add a slot anywhere in the detail layout, and add as many as you need. Any section inside a slot belongs to that one item. In the item's Studio tab you have full control of it, the same as on a page: edit static content, change field mapping, add cards and add more sections.

4. Data from other WebApps and Modules (editable)

A section can pull in items from another WebApp or Module, the same way it does on pages. For example, a blog post can show a card list mapped to an Authors WebApp. Click an author in the preview to edit their content right there. The change saves to the source item, so you don't need to go back to Admin.

How slots work with new and existing items

Sections you put inside a slot in the detail layout act as starting content for new items.

  • New items: the slot's sections are added when the item is created. You can then change them for that item only.

  • Existing items: sections added to a slot are not pushed to items that already exist. This stops a layout change from updating items you didn't want to touch.

  • Sections outside a slot: these are part of the detail layout, so they appear on every item, new and existing.

A slot can also be left empty, as a place to add sections to an item when needed.

Copying items

Copy Item copies the item's Studio content too. Build one great item, then copy it as a starting point for the next.

Example: a custom blog post

  1. Open the Blog detail layout in Studio. Map the hero heading to the item's Name.

  2. Add a slot below the hero. Put a card showcase section in it as starting content. Save.

  3. Create a new blog post, give it a name and save. Open its Studio tab.

  4. The hero shows the post's name, and you can edit it. The card showcase in the slot belongs to this post, so change its text, mapping and cards as you like.

  5. Add a card list mapped to your Authors WebApp. Click an author in the preview to update their details.

When to use it

Your content stays structured and reusable in WebApps and Modules, and your clients still get a page builder for each item. Good uses include case studies, portfolio projects, landing-style blog posts, rich product or service stories, and sites that link several WebApps together.

Keep using the structured detail layout when every item should look the same. Use slots when some items need extra freedom.