Content Authors

Welcome. Studio is where you compose pages by dropping Sections onto Templates and swapping content per instance, no code, no deploy per page.

This chapter is written for you: no React jargon, no CLI, no build steps.

Do It With a Skill

Skills run in a developer’s code editor, so they are not part of an author’s day. Everything in this track is done in Studio, in a browser.

If something is missing from your palette or a page will not preview, that is developer-side setup. verify-setup is the skill they should run.

There is one skill written for this track: author-without-code walks the whole authoring path, picking a template through to publishing, on a project a developer has already set up.

Start Here

• 5-minute Quickstart: use a Template your team already built, drop a Section, change a headline, publish. If you have exactly 5 minutes today, do this.
• Glossary: every Studio word (Template, Section, Slot, Repeater, Deploy vs Publish, and 20 more) explained in one line, no engineering jargon. Keep it open in a tab.

Second Worked Walkthrough (~15 Min, Intermediate)

• Compose a seasonal landing page (15 minutes): a full end-to-end second exercise after the 5-min quickstart. Pick a Template, point it at a specific entry, drop Sections, fill a Section Slot, override exposed props, Save + Deploy to preview then production, roll back if needed. This is the walkthrough that turns “I did the quickstart once” into “I can build a real campaign page on my own.”

Then, Day by Day

• Working with Templates: creating new pages by picking a Template, setting the URL, deploying.
• Working with Sections: dropping Sections, filling Section Slots, overriding exposed props.
• Publishing and preview: draft vs live, previewing before publish, rolling back.
• Troubleshooting for authors: the top “something looks wrong” symptoms and how to fix them without escalating to engineering.

What You Won’t Find Here

• How to register components. That’s a developer task: your engineering team ships components you can then use in Studio. If you need one that doesn’t exist yet, they’ll build and register it, then you’ll see it in your palette.
• How to change what a Section looks like. The design of a Section is set once when your team builds it. What you CAN change per Template: values (via exposed props) and regions (via Section Slots). Everything else is intentionally locked.
• How to deploy code changes. Studio publishes composition changes. Code deploys happen separately in your team’s CI. When you Deploy a Template in Studio, that publishes the composition. When your team ships a new component, that’s a code deploy.

Where to Find Developer Content

If you also code, or want to understand the mechanics under the hood, jump to Build your first page in the Tutorials chapter.

Where to Find Business Framing

For evaluation / positioning / speed-to-market conversations: Studio for Business in the For Business chapter.