Fictional demonstration · selected recorded evidence
From an inventory to specific decisions.
Larkhaven is a fictional council website built for this demonstration. Its recorded WordPress migration shows the shape of an inventory, feature review and acceptance record.
The entries below summarize the public recording. They also show which questions need their own evidence before a production launch.
Start with what the site contains.
- Posts & pages
- 70
- Comments
- 19
- Forms
- 3
- Legacy user records
- 4
The inventory identified WordPress, a custom theme, Contact Form 7, Yoast SEO and Advanced Custom Fields. It also reported 2,347 PHP files containing 339,710 lines, and 615 upload files totalling 114 MB. These figures describe the source inventory; the recording shows selected report lines and checks.
Give each feature a destination and a check.
| Feature | Migration decision | Evidence or still to verify |
|---|---|---|
| Content & comments | Import the selected records into the Motoko backend. | Recorded The backend reports 70 content items and 19 comments. The transcript says these match WordPress; the WordPress comparison is not shown on screen. |
| Custom theme & old links | Rebuild the frontend at the existing public paths. | Recorded One /events/ page comparison has 0 differing pixels. An old ?p=92 bookmark reaches its article. Other pages and accessibility need their own checks. |
| Contact forms | Rebuild the selected form behavior in Motoko. | Recorded Three forms and 34 form rules are imported; one form accepts a submission. Email delivery, failure cases and abuse controls still need evidence. |
| Search | Rebuild search against the imported content. | Recorded The backend reports 70 search documents. A search for “bins” returns seven results on the live demo. |
| Yoast SEO & custom fields | Decision still required Map the metadata and custom-field behavior the service needs. | The inventory lists Yoast SEO and ACF. The public recording does not demonstrate each SEO field or custom-field mapping; those require explicit acceptance checks. |
| Staff access & operation | Decision still required Agree sign-in, permissions, integrations and cutover before launch. | Four legacy user records are imported. Sign-in, the admin area, email delivery, integrations, a production-domain cutover and retiring the old host are not demonstrated in this recording. |
Read the URL result in full.
987 old URLs checked: 808 matched at HTTP level, 176 query-string links were resolved in the browser, and three endpoints were retired intentionally: /wp-admin/, /wp-login.php and /xmlrpc.php.
The pixel comparison covers /events/ only. The recording shows selected pages and checks; it does not establish that every feature or production requirement has been verified.
Start with the inventory
Start with your
PHP project.
Open your codebase, copy the brief and review the migration plan.