Extend the nested section recipe by creating a separate Stay Summary shell. It should start with a heading and paragraph, allow those two children to change order, and preserve that starting child count through normal editor controls.

Your task

Work in src/blocks/StaySummary.tsx and keep the recipe's Content Section block too.

Configure:

• Registered name stay-summary and title Stay Summary.
• Allowed direct children: core/heading and core/paragraph.
• A starting h2 reading Your stay at a glance and a paragraph reading A comfortable base for exploring the coast.
• templateLock: "insert".
• A vertical arrangement with a bordered, padded shell.

Choose the right lock

These describe the shell's structural lock. Check them in your site's editor context: roles, surrounding templates, and other block locks can add restrictions. allowedBlocks controls eligible direct child types; templateLock controls structural operations on the nested composition.

Acceptance criteria

1. A fresh Stay Summary starts with exactly the configured heading and paragraph.
2. Editors can change both children's text, save, and reload those edits.
3. Normal child insertion and removal controls are restricted by the "insert" lock.
4. Editors can reorder the two children where other editor settings permit it.
5. The visitor sees the saved text and order inside the shell.
6. Content Section from the recipe remains flexible and can still accept images.
7. Two Stay Summary instances keep independent text.

Use List View to distinguish the selected child from its parent. The inner lock applies to the children; configure Page-level restrictions separately if you also want to control moving or removing the whole parent section.

Hints

Hint 1: Define the starting children

Each template row is [blockName, initialAttributes]. Give the heading level: 2 and set each child's initial content. This supplies a new instance's starting composition.

Hint 2: Preserve content editing

Use "insert" for the main task. It preserves the nested structure while allowing movement and editing of the existing children. The child blocks supply their usual text controls.

Hint 3: Test one layer at a time

Test Stay Summary on a Page where the surrounding template allows normal editing. Then repeat with the client's role and intended Page configuration to see the combined editing experience.

Verify and compare

Update the theme and insert a fresh Stay Summary. Test the acceptance criteria on that instance, save, reload the editor, and inspect the visitor page.

Compare your implementation with Solution: Structured Stay Summary.

Extension: preserve the order too

Change the lock to "all", export, and test a fresh instance. Confirm that text editing still works while child reordering is restricted. Compare all three lock modes deliberately; choose the editing contract that fits your client.