# Companion video: Build the Cedar & Form business website

**Manuscript:** [Build a business website people can explore and contact](../appmint-build-a-business-website.md). **Continuity:** Jordan Morgan, Cedar & Form, local organisation `cedar-local-mu8892bk`, site `cedsite`; pages `cedar-and-form` and `services`. **Build:** Studio Manager 0.6.2, 19 September 2026. The [local evidence directory](../../learner-review-records/assets/website-local-20260919/) contains real browser stills and readbacks. Two complete HTML starters are in `../assets/first-page/`. These are stills, not completed video recordings.

## Open with the result

Show Home → Services → Home in the anonymous visitor window. “Give customers a clear promise, services they understand and a way to contact you. Then prove that the saved website works outside the editor.” Reveal the finished page before opening the editing surface.

Suggested cut: three chapters, 15–20 minutes total. Make the homepage, connect the two pages, then check metadata and recovery. Keep domain connection an optional chapter with its own genuine capture requirements below. Leave pauses for importing the starter and entering the learner's own contact address.

## Capture continuity

Use one training organisation throughout. Capture Studio at 1440×1000 or larger, plus separate anonymous visits at 430 and 320 pixels. The narrow public website is mobile web, not the native Appmint Mobile application. Never show credentials or private fixture files. The rehearsal's local renderer reads this learner's saved pages through the actual base-app source; do not narrate its machine-local address as a public hosting address.

The screenshots are from actual UI operations. Some starter text was entered through the real Monaco editor model, followed by the visible apply and save controls. Film normal human copy/paste for the video; these captures do not prove an uninterrupted manual recording.

## Shot list

Numbers below refer to the local evidence directory, not the older production capture set.

| Scene | Stills | Action to record | Explanation |
| --- | --- | --- | --- |
| Finished result | 20–24 | Anonymous Home → Services → Home at desktop and phone widths | A customer can understand the offer and navigate |
| Choose the site | 01–02 | Active Site → Build Studio → New Web Page | Site contains pages; verify the selected site |
| Import the design | 03 | Open starter as plain text, copy all, HTML → paste → Save | HTML Save applies to canvas |
| Understand selection | 04-heading-selected | Close code panel; select headline and its tree entry | Heading versus containing section |
| Change the promise | 05 | Double-click headline, replace words, Tab | Say what the customer gains |
| Correct contact destination | 06 | HTML → Sync, change email, apply | Sync protects the visual edit; mailto is not a CRM form |
| Narrow preview | 07–08 | Phone View, scroll, Desktop View | Actual 446px internal content / 448px frame |
| Save the record | 09–10 | Toolbar Save → Page fields → Save | Distinguish canvas apply from persistent record save |
| Reopen and practise | 11–13 | All Pages → Edit; change service heading; save/reopen | Specific readback proves persistence |
| Add Services | 14–16 | New Web Page → second starter → fields → Save | Same site, separate `/services` page |
| Connect navigation | 17 | Sync, change both Services hrefs, apply/save | `#services` is a section; `/services` is another page |
| Choose the homepage | 18–19 | Site Config → Pages → Home page → Save changes → reopen | Current UI uses Pages, not the older Info tab |
| Visitor journey | 20–26 | Home/Services/return, contact destination inspection | Independent visitor found the services and contact action; no email sent |
| Metadata | 27–30 | Page Config Information Description; SEO Keywords; toolbar Save; reopen | Show exact field placement and persistence |
| History | 31, 33 | History → View; inspect snapshot; leave and reopen current page | View loads a snapshot on canvas; do not save merely to leave it |
| Domain preparation | 36 | Enter fictional hostname only | Field entry is not a DNS connection |

Final metadata readback is in `final-public-metadata.json`: title `Cedar & Form — Interior Design | cedsite`, exact description and keywords. Explain using the company name as the site title if its technical name is still displayed. Phone overflow measurements and route checks are in `mobile-readback.json`.

## Domain footage still required

No Connect submission, DNS edit or custom-domain HTTPS success was performed. For a complete optional domain chapter, use a domain the filming organisation controls and record:

1. Its working supplied Appmint address.
2. Actual hostname entry, Connect response and Show DNS Settings.
3. The exact values for that site, followed by the real provider's record editor.
4. DNS readback and successful anonymous HTTPS access.
5. Home → Services → Home on the new domain.

Keep unrelated email records intact. Do not use static fallback targets from source as verified infrastructure. Never cut from the fictional `.example` field to someone else's connected site.

## Restore footage still required

The rehearsal inspected History and View; it did not restore over the finished website. On a disposable page, save headline A, then B, view A, deliberately restore it and read back the saved and anonymous result. Capture the actual confirmation, not an invented success card. Return the training page to its intended final state.

## Editorial checks

- Use 07-phone-preview, not the older broad two-column image labelled phone preview.
- Use 19-homepage-readback after choices load; current path is Pages → Home page.
- Exclude 04-html-close-blocked and 34-current-editor-position from clean instructional scenes. The latter is a transient blank page during a coordinated local server restart.
- Keep the HTML Save, toolbar Save and first-save Page form distinct in narration.
- History View is a snapshot loaded into the editor. Return through All Pages/Edit before ordinary editing or inspecting another version.
- No email, lead, booking, chat conversation or purchase was created by this website lesson. The next chosen action is a consultation enquiry creating a CRM lead, covered in the linked enquiry course.

Deliver source recordings, edited chapters, captions, transcript, chapter timestamps and a ledger tying each shot to this build, date and fixture. Mark optional domain/restore footage complete only after filming the actual actions.